Study/AZ-104-MicrosoftAzureAdministrator
1
0
Fork 0
mirror of https://github.com/MicrosoftLearning/AZ-104-MicrosoftAzureAdministrator.git synced 2026-02-04 23:59: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:
garjen55 2022-04-05 21:16:55 -05:00 committed by GitHub
parent dd61587ee5
commit 9a75b56b27
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -56,10 +56,12 @@ In this task, you will deploy four virtual machines into the same Azure region.
```powershell
$location = '[Azure_region]'
```
Now the resource group name:
```powershell
$rgName = 'az104-06-rg1'
```
And finally create the resource group in your desired location:
```powershell
New-AzResourceGroup -Name $rgName -Location $location
@ -384,7 +386,7 @@ In this task, you will configure and test routing between the two spoke virtual
| Protocol | **TCP** |
| Destination Port | **3389** |
1. Click **Check** and wait until results of the connectivity check are returned. Verify that the status is **Reachable**. Review the network path and note that the traffic was routed via **10.60.0.4**, assigned to the **az104-06-nic0** network adapter. If status is **Unreachable**, you should restart az104-06-vm0.
1. Click **Check** and wait until results of the connectivity check are returned. Verify that the status is **Reachable**. Review the network path and note that the traffic was routed via **10.60.0.4**, assigned to the **az104-06-nic0** network adapter. If status is **Unreachable**, you should stop and then start az104-06-vm0.
> **Note**: This is expected, since the traffic between spoke virtual networks is now routed via the virtual machine located in the hub virtual network, which functions as a router.