Study/AZ-104-MicrosoftAzureAdministrator
1
0
Fork 0
mirror of https://github.com/MicrosoftLearning/AZ-104-MicrosoftAzureAdministrator.git synced 2026-02-06 00:29:08 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update LAB_06-Implement_Network_Traffic_Management.md

Browse Source
This commit is contained in:
staleycyn 2023-09-02 06:28:09 -07:00 committed by GitHub
parent bc56752062
commit 6b1917afb5
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 10 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

27
Instructions/Labs/LAB_06-Implement_Network_Traffic_Management.md
View File

@ -148,23 +148,19 @@ In this task, you will configure local peering between the virtual networks you
| Setting | Value |
| --- | --- |
| This virtual network: Peering link name | **az104-06-vnet01_to_az104-06-vnet2** |
| Traffic to remote virtual network | **Allow (default)** |
| Traffic forwarded from remote virtual network | **Block traffic that originates from outside this virtual network** |
| Virtual network gateway | **None (default)** |
| Allow access to remote virtual network | **Ensure the box is checked (default)** |
| Remote virtual network: Peering link name | **az104-06-vnet2_to_az104-06-vnet01** |
| Virtual network deployment model | **Resource manager** |
| I know my resource ID | enabled |
| Resource ID | the value of resourceID parameter of **az104-06-vnet2** you recorded earlier in this task |
| Traffic to remote virtual network | **Allow (default)** |
| Traffic forwarded from remote virtual network | **Allow (default)** |
| Virtual network gateway | **None (default)** |
| Resource ID | The value of resourceID parameter of **az104-06-vnet2** you recorded earlier in this task. |
| Allow access to current virtual network | **Ensure the box is checked (default)** |
| Allow traffic to remote virtual network | **Ensure the box is checked (default)** |
>**Note**: Wait for the operation to complete.
>**Note**: This step establishes two local peerings - one from az104-06-vnet01 to az104-06-vnet2 and the other from az104-06-vnet2 to az104-06-vnet01.
>**Note**: **Allow forwarded traffic** needs to be enabled in order to facilitate routing between spoke virtual networks, which you will implement later in this lab.
1. On the **az104-06-vnet01** virtual network blade, in the **Settings** section, click **Peerings** and then click **+ Add**.
1. Add a peering with the following settings (leave others with their default values) and click **Add**:
@ -172,21 +168,18 @@ In this task, you will configure local peering between the virtual networks you
| Setting | Value |
| --- | --- |
| This virtual network: Peering link name | **az104-06-vnet01_to_az104-06-vnet3** |
| Traffic to remote virtual network | **Allow (default)** |
| Traffic forwarded from remote virtual network | **Block traffic that originates from outside this virtual network** |
| Virtual network gateway | **None (default)** |
| Allow access to remote virtual network | **Ensure the box is checked (default)** |
| Remote virtual network: Peering link name | **az104-06-vnet3_to_az104-06-vnet01** |
| Virtual network deployment model | **Resource manager** |
| I know my resource ID | enabled |
| Resource ID | the value of resourceID parameter of **az104-06-vnet3** you recorded earlier in this task |
| Traffic to remote virtual network | **Allow (default)** |
| Traffic forwarded from remote virtual network | **Allow (default)** |
| Virtual network gateway | **None (default)** |
| Allow access to current virtual network | **Ensure the box is checked (default)** |
| Allow traffic to remote virtual network | **Ensure the box is checked (default)** |
>**Note**: Wait for the operation to complete.
>**Note**: This step establishes two local peerings - one from az104-06-vnet01 to az104-06-vnet3 and the other from az104-06-vnet3 to az104-06-vnet01. This completes setting up the hub and spoke topology (with two spoke virtual networks).
>**Note**: **Allow forwarded traffic** needs to be enabled in order to facilitate routing between spoke virtual networks, which you will implement later in this lab.
## Task 3: Test transitivity of virtual network peering
In this task, you will test transitivity of virtual network peering by using Network Watcher.