In this task, you will use a template to deploy one virtual network, one network security group, and three virtual machines.

1. Download the \Labfiles\03 lab files (template and parameters).
2. Sign in to the Azure portal.
3. Search for and select Deploy a custom template.
4. On the custom deployment page, select Build your own template in the editor.
5. On the edit template page, select Load file.
6. Locate and select the \Labfiles\03\clo800-03-vms-template.json file and select Open.
7. Select Save.
8. Select Edit parameters and load the \Labfiles\03\clo800-03-vms-parameters.json file.
9. Select Save.
10. Use the following information to complete the fields on the custom deployment page, leaving all other fields with the default value:

    Setting	Value
    Subscription	your Azure subscription
    Resource group	<yourName>-clo800-F67-rg
    Password	Provide a secure password

11. Select Review + Create and then select Create.
12. Note: Wait for the deployment to complete before moving to the next task. The deployment should take approximately 5 minutes.
13. Note: Review the resources being deployed. There will be one virtual network with three subnets. Each subnet will have a virtual machine. Screenshot must show your Odl_user account, the deployed resources: one virtual network (clo800-F67-vnet1) with three subnets, each subnet with a virtual machine

In this task, you implement an Azure Load Balancer in front of the two Azure virtual machines in the virtual network. Load Balancers in Azure provide layer 4 connectivity across resources, such as virtual machines. Load Balancer configuration includes a front-end IP address to accept connections, a backend pool, and rules that define how connections should traverse the load balancer.

Note: Notice the Load Balancer is distributing across two virtual machines in the same virtual network.

1. In the Azure portal, search for and select Load balancers and, on the Load balancers blade, click + Create.
2. Create a load balancer with the following settings (leave others with their default values) then click Next: Frontend IP configuration:

   Setting	Value
   Subscription	your Azure subscription
   Resource group	<yourName>-clo800-F67-rg
   Name	<yourName>-clo800-F67-lb
   Region	The same region that you deployed the VMs
   SKU	Standard
   Type	Public
   Tier	Regional

3. On the Frontend IP configuration tab, click Add a frontend IP configuration and use the following settings:

   Setting	Value
   Name	<yourName>-clo800-F67-fe
   IP type	IP address
   Gateway Load Balancer	None
   Public IP address	Select Create new (use the instructions in the next step)

4. On the Add a public IP address popup, use the following settings before clicking OK and then Add. When completed click Next: Backend pools:

   Setting	Value
   Name	<yourName>-clo800-F67-lbpip
   SKU	Standard
   Tier	Regional
   Assignment	Static
   Routing Preference	Microsoft network

5. Note: The Standard SKU provides a static IP address. Static IP addresses are assigned when the resource is created and released when the resource is deleted.
6. On the Backend pools tab, click Add a backend pool with the following settings (leave others with their default values). Click + Add (twice) and then click Next: Inbound rules:

   Setting	Value
   Name	<yourName>-clo800-F67-be
   Virtual network	clo800-F67-vnet1
   Backend Pool Configuration	NIC
   clo800-F67-vm0	check the box
   clo800-F67-vm1	check the box

7. As you have time, review the other tabs, then click Review + create. Ensure there are no validation errors, then click Create.
8. Wait for the load balancer to deploy then click Go to resource.
9. Add a rule to determine how incoming traffic is distributed.
10. In the Settings blade, select Load balancing rules.
11. Select + Add. Add a load balancing rule with the following settings (leave others with their default values). As you configure the rule use the informational icons to learn about each setting. When finished click Save:

    Setting	Value
    Name	<yourName>-clo800-F67-lbrule
    IP Version	IPv4
    Frontend IP Address	<yourName>-clo800-F67-fe
    Backend pool	<yourName>-clo800-F67-be
    Protocol	TCP
    Port	80
    Backend port	80
    Health probe	Create new
    Name	<yourName>-clo800-F67-hp
    Protocol	TCP
    Port	80
    Interval	5
    Close the create health probe window	—
    Save	—
    Session persistence	None
    Idle timeout (minutes)	4
    TCP reset	Disabled
    Floating IP	Disabled
    Outbound source network address translation (SNAT)	Recommended

12. Select Frontend IP configuration from the Load Balancer page. Copy the public IP address.
13. Open another browser tab and navigate to the IP address. Verify that the browser window displays the message Hello World from clo800-F67-vm0 or Hello World from clo800-F67-vm1.
14. Refresh the window to verify the message changes to the other virtual machine. This demonstrates the load balancer rotating through the virtual machines.
15. Note: You may need to refresh more than once or open a new browser window in InPrivate mode. Screenshot must show your Odl_user account, the browser displaying "Hello World from clo800-F67-vm0" or "Hello World from clo800-F67-vm1" (load balancer frontend)

In this task, you implement an Azure Application Gateway in front of two Azure virtual machines. An Application Gateway provides layer 7 load balancing, Web Application Firewall (WAF), SSL termination, and end-to-end encryption to the resources defined in the backend pool. The Application Gateway routes images to one virtual machine and videos to the other virtual machine.

Note: This Application Gateway is working in the same virtual network as the Load Balancer. This may not be typical in a production environment. Refer to the lab architecture diagram.

1. In the Azure portal, search and select Virtual networks.
2. On the Virtual networks blade, in the list of virtual networks, click clo800-F67-vnet1.
3. In the Settings section, click Subnets, and then click + Subnet.
4. Add a subnet with the following settings (leave others with their default values):

   Setting	Value
   Name	subnet-appgw
   Starting address	10.60.3.224
   Size	/27

5. Click Save.
6. Note: This subnet will be used by the Azure Application Gateway. The Application Gateway requires a dedicated subnet of /27 or larger size.
7. In the Azure portal, search and select Application gateways and, on the Application gateways blade, click + Create.
8. On the Basics tab, specify the following settings (leave others with their default values):

   Setting	Value
   Subscription	your Azure subscription
   Resource group	<yourName>-clo800-F67-rg
   Application gateway name	<yourName>-clo800-F67-appgw
   Region	The same Azure region that you used in Task 1
   Tier	Standard V2
   Enable autoscaling	No
   Instance count	2
   Availability zone	1
   HTTP2	Disabled
   Virtual network	clo800-F67-vnet1
   Subnet	subnet-appgw (10.60.3.224/27)

9. Click Next: Frontends > and specify the following settings (leave others with their default values). When complete, click OK:

   Setting	Value
   Frontend IP address type	Public
   Public IP address	Add new
   Name	<yourName>-clo800-F67-gwpip
   Availability zone	default

10. Note: The Application Gateway can have both a public and private IP address.
11. Click Next : Backends > and then Add a backend pool. Specify the following settings (leave others with their default values). When completed click Add:

    Setting	Value
    Name	<yourName>-clo800-F67-appgwbe
    Add backend pool without targets	No
    Virtual machine	clo800-F67-nic1 (10.60.1.4)
    Virtual machine	clo800-F67-nic2 (10.60.2.4)

12. Click Add a backend pool. This is the backend pool for images. Specify the following settings (leave others with their default values). When completed click Add:

    Setting	Value
    Name	<yourName>-clo800-F67-imagebe
    Add backend pool without targets	No
    Virtual machine	clo800-F67-nic1 (10.60.1.4)

13. Click Add a backend pool. This is the backend pool for video. Specify the following settings (leave others with their default values). When completed click Add:

    Setting	Value
    Name	<yourName>-clo800-F67-videobe
    Add backend pool without targets	No
    Virtual machine	clo800-F67-nic2 (10.60.2.4)

14. Select Next : Configuration > and then Add a routing rule. Complete the information:

    Setting	Value
    Rule name	<yourName>-clo800-F67-gwrule
    Priority	10
    Listener name	clo800-F67-listener
    Frontend IP	Public IPv4
    Protocol	HTTP
    Port	80
    Listener type	Basic

15. Move to the Backend targets tab. Select Add after completing the basic information:

    Setting	Value
    Backend target	<yourName>-clo800-F67-appgwbe
    Backend settings	<yourName>-clo800-F67-http (create new)

16. Note: Take a minute to read the information about Cookie-based affinity and Connection draining.
17. In the Path-based routing section, select Add multiple targets to create a path-based rule. You will create two rules. Click Add after the first rule and then Add after the second rule.
18. Rule — routing to the images backend:

    Setting	Value
    Path	/image/*
    Target name	images
    Backend settings	<yourName>-clo800-F67-http
    Backend target	<yourName>-clo800-F67-imagebe

19. Rule — routing to the videos backend:

    Setting	Value
    Path	/video/*
    Target name	videos
    Backend settings	<yourName>-clo800-F67-http
    Backend target	<yourName>-clo800-F67-videobe

20. Be sure to Save and check your changes, then select Next : Tags >. No changes are needed.
21. Select Next : Review + create > and then click Create.
22. Note: Wait for the Application Gateway instance to be created. This will take approximately 5-10 minutes.
23. After the application gateway deploys, search for and select <yourName>-clo800-F67-appgw.
24. In the Application Gateway resource, in the Monitoring section, select Backend health.
25. Ensure both servers in the backend pool display Healthy.
26. On the Overview blade, copy the value of the Frontend public IP address.
27. Start another browser window and test this URL - http://<frontend ip address>/image/.
28. Verify you are directed to the image server (vm1).
29. Start another browser window and test this URL - http://<frontend ip address>/video/.
30. Verify you are directed to the video server (vm2).
31. Note: You may need to refresh more than once or open a new browser window in InPrivate mode. Screenshot must show your Odl_user account, the Application Gateway overview (frontend public IP) and the browser tests — /image/ showing "Image from clo800-F67-vm1" and /video/ showing "Video from clo800-F67-vm2"

Minimum 2-3 sentences each — original thinking, your own words!

1. Describe the main focus of this lab and outline the new skills or concepts you learned during this Azure lab session.
2. What challenges did you encounter during this lab, and how did you overcome them?
3. How do the tasks performed in this lab enhance your understanding of Azure networking?
4. In what ways can you apply the knowledge gained from this lab to real-world scenarios? Please provide specific examples.

Screenshots you attach above and your Task 4 answers appear here. This is exactly what prints/exported as your PDF.

1. All screenshots attached in task order, each with your Odl_user account visible (underlined or highlighted).
2. A brief explanation added for each screenshot.
3. Export the PDF with Print / Save as PDF and upload it to the Blackboard assignment.