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

Fix file paths and formatting in lab instructions

Browse Source 
Updated file paths and formatting for consistency in the lab instructions.
This commit is contained in:
Kacper Bąk 2025-10-21 14:39:25 +02:00 committed by GitHub
parent 61606f6289
commit 7e70af1b10
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 13 additions and 13 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

@ -38,11 +38,11 @@ In this task, you will use a template to deploy one virtual network, one network
1. On the edit template page, select **Load file**. 1. On the edit template page, select **Load file**.
1. Locate and select the **\\Allfiles\\Lab06\\az104-06-vms-template.json** file and select **Open**. 1. Locate and select the **\\Allfiles\\Labs\\06\\az104-06-vms-template.json** file and select **Open**.
1. Select **Save**. 1. Select **Save**.
1. Select **Edit parameters** and load the **\\Allfiles\\Lab06\\az104-06-vms-parameters.json** file. 1. Select **Edit parameters** and load the **\\Allfiles\\Labs\\06\\az104-06-vms-parameters.json** file.
1. Select **Save**. 1. Select **Save**.
@ -56,7 +56,7 @@ In this task, you will use a template to deploy one virtual network, one network
>**Note**: If you receive an error that the VM size is unavailable, select a SKU that is available in your subscription and has at least 2 cores. >**Note**: If you receive an error that the VM size is unavailable, select a SKU that is available in your subscription and has at least 2 cores.
1. Select **Review + Create** and then select **Create**. 1. Select **Review + create** and then select **Create**.
>**Note**: Wait for the deployment to complete before moving to the next task. The deployment should take approximately 5 minutes. >**Note**: Wait for the deployment to complete before moving to the next task. The deployment should take approximately 5 minutes.
@ -74,7 +74,7 @@ In this task, you implement an Azure Load Balancer in front of the two Azure vir
1. In the Azure portal, search for and select `Load balancers` and, on the **Load balancers** blade, click **+ Create**. 1. In the Azure portal, search for 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) then click **Next: Frontend IP configuration**: 1. Create a load balancer with the following settings (leave others with their default values) then click **Next : Frontend IP configuration**:
| Setting | Value | | Setting | Value |
| --- | --- | | --- | --- |
@ -94,10 +94,10 @@ In this task, you implement an Azure Load Balancer in front of the two Azure vir
| --- | --- | | --- | --- |
| Name | `az104-fe` | | Name | `az104-fe` |
| IP type | IP address | | IP type | IP address |
| Gateway Load Balancer | None | | Gateway Load balancer | None |
| Public IP address | Select **Create new** (use the instructions in the next step) | | Public IP address | Select **Create new** (use the instructions in the next step) |
1. On the **Add a public IP address** popup, use the following settings before clicking **Save** twice. When completed click **Next: Backend pools**. 1. On the **Add a public IP address** popup, use the following settings before clicking **Save** twice. When completed click **Next : Backend pools >**.
| Setting | Value | | Setting | Value |
| --- | --- | | --- | --- |
@ -109,12 +109,12 @@ In this task, you implement an Azure Load Balancer in front of the two Azure vir
>**Note:** The Standard SKU provides a static IP address. Static IP addresses are assigned with the resource is created and released when the resource is deleted. >**Note:** The Standard SKU provides a static IP address. Static IP addresses are assigned with the resource is created and released when the resource is deleted.
1. On the **Backend pools** tab, click **Add a backend pool** with the following settings (leave others with their default values). Click **Add** and then **Save**. Click **Next: Inbound rules**. 1. On the **Backend pools** tab, click **Add a backend pool** with the following settings (leave others with their default values). Click **Add** and then **Save**. Click **Next : Inbound rules >**.
| Setting | Value | | Setting | Value |
| --- | --- | | --- | --- |
| Name | `az104-be` | | Name | `az104-be` |
| Virtual network | **az104-06-vnet1** | | Virtual network | **az104-06-vnet1 (az104-rg6)** |
| Backend Pool Configuration | **NIC** | | Backend Pool Configuration | **NIC** |
| Click **Add** to add a virtual machine | | | Click **Add** to add a virtual machine | |
| az104-06-vm0 | **check the box** | | az104-06-vm0 | **check the box** |
@ -147,8 +147,8 @@ In this task, you implement an Azure Load Balancer in front of the two Azure vir
| Close the create health probe window | **Save** | | Close the create health probe window | **Save** |
| Session persistence | **None** | | Session persistence | **None** |
| Idle timeout (minutes) | `4` | | Idle timeout (minutes) | `4` |
| TCP reset | **Disabled** | | Enable TCP reset | **Disabled** |
| Floating IP | **Disabled** | | Enable Floating IP | **Disabled** |
| Outbound source network address translation (SNAT) | **Recommended** | | Outbound source network address translation (SNAT) | **Recommended** |
1. Select **Frontend IP configuration** from the Load Balancer page. Copy the public IP address. 1. Select **Frontend IP configuration** from the Load Balancer page. Copy the public IP address.
@ -187,7 +187,7 @@ In this task, you implement an Azure Application Gateway in front of two Azure v
> **Note**: This subnet will be used by the Azure Application Gateway. The Application Gateway requires a dedicated subnet of /27 or larger size. > **Note**: This subnet will be used by the Azure Application Gateway. The Application Gateway requires a dedicated subnet of /27 or larger size.
1. In the Azure portal, search and select `Application gateways` and, on the **Application Gateways** blade, click **+ Create**. 1. In the Azure portal, search and select `Application gateways` and, on the **Application gateways** blade, click **+ Create**.
1. On the **Basics** tab, specify the following settings (leave others with their default values): 1. On the **Basics** tab, specify the following settings (leave others with their default values):
@ -204,7 +204,7 @@ In this task, you implement an Azure Application Gateway in front of two Azure v
| Virtual network | **az104-06-vnet1** | | Virtual network | **az104-06-vnet1** |
| Subnet | **subnet-appgw (10.60.3.224/27)** | | Subnet | **subnet-appgw (10.60.3.224/27)** |
1. Click **Next: Frontends >** and specify the following settings (leave others with their default values). When complete, click **OK**. 1. Click **Next : Frontends >** and specify the following settings (leave others with their default values). When complete, click **OK**.
| Setting | Value | | Setting | Value |
| --- | --- | | --- | --- |
@ -289,7 +289,7 @@ In this task, you implement an Azure Application Gateway in front of two Azure v
1. After the application gateway deploys, search for and select **az104-appgw**. 1. After the application gateway deploys, search for and select **az104-appgw**.
1. In the **Application Gateway** resource, in the **Monitoring** section, select **Backend health**. 1. In the **Application gateway** resource, in the **Monitoring** section, select **Backend health**.
1. Ensure both servers in the backend pool display **Healthy**. 1. Ensure both servers in the backend pool display **Healthy**.