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

Merge pull request #425 from MOC-Labs-Review/MOC-Labs-Review-patch-4

Browse Source 
Update LAB_06-Implement_Network_Traffic_Management.md
This commit is contained in:
staleycyn 2021-12-10 13:26:17 -08:00 committed by GitHub
commit 7003ebf352
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 16 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -128,7 +128,7 @@ In this task, you will configure local peering between the virtual networks you
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:
1. Add a peering with the following settings (leave others with their default values) and click **Add**:
| Setting | Value |
| --- | --- |
@ -152,7 +152,7 @@ In this task, you will configure local peering between the virtual networks you
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:
1. Add a peering with the following settings (leave others with their default values) and click **Add**:
| Setting | Value |
| --- | --- |
@ -299,11 +299,11 @@ In this task, you will configure and test routing between the two spoke virtual
> **Note**: Wait for the route table to be created. This should take about 3 minutes.
1. Back on the **Route tables** blade, click **Refresh** and then click **az104-06-rt23**.
1. Click **Go to resource**.
1. On the **az104-06-rt23** route table blade, in the **Settings** section, click **Routes**, and then click **+ Add**.
1. Add a new route with the following settings (leave others with their default values):
1. Add a new route with the following settings:
| Setting | Value |
| --- | --- |
@ -341,7 +341,7 @@ In this task, you will configure and test routing between the two spoke virtual
> **Note**: Wait for the route table to be created. This should take about 3 minutes.
1. Back on the **Route tables** blade, click **Refresh** and then click **az104-06-rt32**.
1. Click **Go to resource**.
1. On the **az104-06-rt32** route table blade, in the **Settings** section, click **Routes**, and then click **+ Add**.
@ -394,22 +394,28 @@ In this task, you will implement an Azure Load Balancer in front of the two Azur
1. In the Azure portal, search and select **Load balancers** and, on the **Load balancers** blade, click **+ Create**.
1. Create a load balancer with the following settings (leave others with their default values):
1. Create a load balancer with the following settings (leave others with their default values) then click **Next : Frontend IP configuration**:
| Setting | Value |
| --- | --- |
| Subscription | the name of the Azure subscription you are using in this lab |
| Resource group | the name of a new resource group **az104-06-rg1** |
| Resource group | **az104-06-rg1** |
| Name | **az104-06-lb4** |
| Region| name of the Azure region into which you deployed all other resources in this lab |
| Type | **Public** |
| SKU | **Standard** |
| Type | **Public** |
1. On the **Frontend IP configuration** tab, click **Add a frontend IP configuration** and use the following setting before clicking **Add**.
| Setting | Value |
| --- | --- |
| Name | any unique name |
| Public IP address | **Create new** |
| Public IP address name | **az104-06-pip4** |
| Availability zone | **No Zone** |
| Add a public IPv6 address | **No** |
1. Click Review and Create. Let validation occur, and hit Create to submit your deployment.
1. Click **Review and Create**. Let validation occur, and hit **Create** to submit your deployment.
> **Note**: Wait for the Azure load balancer to be provisioned. This should take about 2 minutes.
@ -504,7 +510,7 @@ In this task, you will implement an Azure Application Gateway in front of the tw
| Setting | Value |
| --- | --- |
| Subscription | the name of the Azure subscription you are using in this lab |
| Resource group | the name of a new resource group **az104-06-rg1** |
| Resource group | **az104-06-rg1** |
| Application gateway name | **az104-06-appgw5** |
| Region | name of the Azure region into which you deployed all other resources in this lab |
| Tier | **Standard V2** |