{
    "id": "ab9a1064-7a8f-4959-9e3e-30b929501eb9",
    "name": "Deploy Highly Available Virtual Machines",
    "slug": "deploy-highly-available-virtual-machines",
    "status": "published",
    "lab_type": "pta",
    "is_sample": false,
    "duration_in_seconds": 1800,
    "metadata": {
        "courses": [
            "1a20bc1a-9d44-4503-95f2-3de135097a2e"
        ],
        "pta_sdn": "142",
        "pta_namespace": "my.ine",
        "learning_paths": [],
        "has_published_parent": true
    },
    "session": null,
    "company": "a491bc32-c056-4946-9169-cc053387bada",
    "created": "2022-08-01T21:06:10.716003Z",
    "modified": "2024-06-12T12:36:22.316699Z",
    "is_beta": false,
    "lab_objectives": [],
    "main_learning_area": "d3f82c70-f4e7-428e-afd7-4b1d28988e18",
    "learning_areas": [
        {
            "id": "d3f82c70-f4e7-428e-afd7-4b1d28988e18",
            "name": "Cloud",
            "slug": "cloud"
        }
    ],
    "categories": [],
    "tags": [],
    "difficulty": null,
    "is_web_access": true,
    "is_lab_experience": false,
    "is_featured": false,
    "cve": null,
    "severity": null,
    "year": null,
    "classification": null,
    "is_trackable": false,
    "cpe_credits": null,
    "is_skill_check": false,
    "external_url": "",
    "solution_video": null,
    "explanation_video": null,
    "description": "Learn how to deploy virtual machines for high availability, achieve a 99.99% availability SLA, and configure load balancing.",
    "description_html": "<p>Learn how to deploy virtual machines for high availability, achieve a 99.99% availability SLA, and configure load balancing.</p>",
    "tasks": "The goal of this task is to modify an existing ARM template to achieve a 99.99% availability SLA. This includes configuring the deployment to use availability zones for the two virtual machines that are deployed, as well as adding a load balancer to provide HTTP access to the virtual machines.\n\n**Note:** The template deploys two virtual machines with a custom script extension that installs a simple HTTP workload.",
    "tasks_html": "<p>The goal of this task is to modify an existing ARM template to achieve a 99.99% availability SLA. This includes configuring the deployment to use availability zones for the two virtual machines that are deployed, as well as adding a load balancer to provide HTTP access to the virtual machines.</p>\n<p><strong>Note:</strong> The template deploys two virtual machines with a custom script extension that installs a simple HTTP workload.</p>",
    "published_date": "2020-04-07T18:00:00Z",
    "solutions": "# Solution\n\n# Provision virtual machines in multiple availability zones\n\nFirst of all login to your azure portal with the generated credentials. You have to accept the terms and click continue to generate the credentials.\n\n![](https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/1.png)\n\n**Note:** Your credentials will be different from the one shown in the figure.\n\nAfter logging in to portal using the credentials. You will see an empty resource group, where you can create some resources.\n\n![](https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/2.png)\n\nSearch for *Deploy* and click on **Deploy a custom template** as highlighted below.\n\n![](https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/3.png)\n\nClick on the **Build your own template in the editor** to start creating your own template.\n\n![](https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/4.png)\n\nGo to your browser and download this json file:\n\n```\nhttps://inedemoassets.blob.core.windows.net/taskfiles/azure_admin/deploy-web-servers.json\n```\n\nNow you are at the editor, click on **Load file** to load the downloaded file into the editor..\n\n![](https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/5.png)\n\nThe json file will be loaded to the editor.\n\n![](https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/6.png)\n\nAdd the following variable element as highlighted in the image below.\n\n```\n\"zones\":[\"1\",\"2\",\"3\"]\n```\n\n![](https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/7.png)\n\nAdd the following element to the virtual machine element as highlighted in the image below.\n\n```\n\"zones\":[\"[Variables('zones')[copyIndex()]]\"],\n```\n\n![](https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/8.png)\n\nAdd the following element to the public ip element as highlighted in the image below.\n\n```\n\"zones\":[\"[Variables('zones')[copyIndex()]]\"],\n```\n\n![](https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/9.png)\n\nYou will see that there are two subnets given, you can let them be or can remove one subnet. See image below.\n\n![](https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/10.png)\n\nIf you intend to remove the subnet, name the one remaining subnet as **default**.\n\n![](https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/11.png)\n\nIf you check the property element of the NIC, subnet name is **server**.\n\n![](https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/12.png)\n\nChange it to **default**.\n\n![](https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/13.png)\n\nChange the vmSize to **Standard_D2S_V4**.\n\n\n![](https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/14.png)\n\nAfter all the changes click on **Save** to start deploying the resources.\n\nYou can also go ahead and download the arm script from the **Download** option.\n\nEnter a strong admin password for our webservers. Then click on **Review+Create** to create the resources.\n\n![](https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/15.png)\n\nNow *Azure* will verify your template. After sometime you will see *Validation Passed* that means everything is fine. Click on **Create** to create the resources.\n\n\n![](https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/16.png)\n\nAfter few minutes you will see **Your deployment is complete**, it means everything is deployed correctly.\n\nYou can click on **Go to resource group** to go and check the resources you just deployed.\n\n![](https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/17.png)\n\nSearch for *nsg* and click on **Network security groups** as highlighted below.\n\n![](https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/18.png)\n\nClick on **Create** to start creating a network security group.\n\n![](https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/19.png)\n\n* Use the resource group assigned to you\n* Give the network security group a name as **azone-nsg**\n* Use the same region we used in earlier task\n\nThen click on **Review+Create** to create the network security group.\n\n![](https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/20.png)\n\nAzure will validate your configurations and you will see something like the below image. Click on **Create** after you see *Validation passed*\n\n![](https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/21.png)\n\nAfter some time the deployment will be done and you will see something like the below image.\n\nYou can click on **Go to resource**\n\n![](https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/22.png)\n\nGo to **Inbound security rules** of your network security group and click on **Add** to add new security rule.\n\n![](https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/23.png)\n\nUse the service type as **HTTP** and give it a name of your choice. Then click on **Add** to add the rule.\n\n![](https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/24.png)\n\nGo to your resource group and you can see all the resource there. Click on the **webservers-VNET** virtual network to configure it.\n\n![](https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/25.png)\n\nIf you go to the subnets of our virutal network. You can see the default subnet. Click on it to start configuring it.\n\n![](https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/26.png)\n\nLet everthing be untouched, just change the network security group to the one we just created.\n\nSave the subnet configuration.\n\n![](https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/27.png)\n\n# Provision and configure a load balancer\n\nSearch for *load balancer* and click on **Load balancers** as highlighted below.\n\n![](https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/28.png)\n\nClick on create as highlighted below to create a new load balancer.\n\n![](https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/29.png)\n\n* Use the same resource group which is assigned to you\n* Name the load balancer as **azone-lb** \n* For that use the SKU as **Standard** \n* Type of balancer as **Public**\n\nThen click on **Next** to configure the frontend IP.\n\n![](https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/30.png)\n\nHere click on *Add a frontend IP config*\n\n![](https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/31.png)\n\nClick on **Create new** under the public IP address. Give it a name **azone-lb-pip** and make it *Zone-reduntant*.\n\nGive your config a name and add it.\n\n![](https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/32.png)\n\nYou can see that the configuration is added.\n\nYou can either choose to configure the backend pools and load balancing rules from here also, or you can create the load balancer and then configure them.\n\n![](https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/33.png)\n\nI am going to create the load balancer now and then configure it.\n\nClick on **Review + create** to create the load balancer.\n\n![](https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/34.png)\n\nAzure will check if everything is fine. After a few second you will see *Validation passed*. Now click on **Create** to finally deploy the load balancer.\n\n![](https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/35.png)\n\nWhen the load balancer is deployed click on **Go to resources**.\n\n![](https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/36.png)\n\nNow go to the backend pools of your load balancer. Click on **Add** to add a new backend pool.\n\n![](https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/37.png)\n\nGive your backend pool a name and select the virtual network which is used for our Virtual Machines.\n\nYou will see one option of **Add** will pop up in the page, click on it.\n\n![](https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/38.png)\n\nAdd both the virutal machine to our backend pool by checking the checkboxes in front of them.\n\n![](https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/39.png)\n\nYou can see that we have both our VMs to our backend pool. \n\nSave the backend pool.\n\n![](https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/40.png)\n\nNow go to the load balancing rules of your load balancer and click on **Add** to add load balancing rules.\n\n![](https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/41.png)\n\nFirst of all create a *Health Proble*, you can see an option **Create new**. \n\n* Give the health probe a name **websvr-probe**\n* Use the protocol as **HTTP**\n\nAdd the health probe to our load balancing rule.\n\n![](https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/42.png)\n\n* Give your load balancing rule a name as **azone-lbr**\n* Use the frontend IP config as the one we created earlier.\n* Select the backend port which you created in last task\n* Use the port and backend port as **80**\n\nClick on **Add** to add the load balancing rule to your load balancer.\n\n![](https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/43.png)\n\n# Verify the workload\n\nGo to your primary virtual machine.\n\nYou can see that the virtual machine is in **Zone 1** of your respective location.\n\n![](https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/44.png)\n\nNow go to your secondary virtual machine.\n\nYou can see that the virtual machine is in **Zone 2** of your respective location.\n\n![](https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/45.png)\n\nYou can get the public IP of your load balancer from the virtual machine itself. Even though these virtual machines had their own public IPs, but after configuring with the load balancer. Public IP shown to you will be the public IP of the load balancer.\n\n![](https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/46.png)\n\nYou can go to your load balancer and cross check that the public IP shown in both the VMs and load balancer is the same.\n\n![](https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/46a.png)\n\nBrowse this public IP address on to your browser.\n\nIf you reload it some times, you will see two different outputs. Just like the below images.\n\n![](https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/47.png)\n\n![](https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/48.png)\n\nThe output is just the name of virutal machines. \n\nThis means that our workload is working fine. The lab is now complete.",
    "solutions_html": "<h1>Solution</h1>\n<h1>Provision virtual machines in multiple availability zones</h1>\n<p>First of all login to your azure portal with the generated credentials. You have to accept the terms and click continue to generate the credentials.</p>\n<p><img alt=\"\" src=\"https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/1.png\" /></p>\n<p><strong>Note:</strong> Your credentials will be different from the one shown in the figure.</p>\n<p>After logging in to portal using the credentials. You will see an empty resource group, where you can create some resources.</p>\n<p><img alt=\"\" src=\"https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/2.png\" /></p>\n<p>Search for <em>Deploy</em> and click on <strong>Deploy a custom template</strong> as highlighted below.</p>\n<p><img alt=\"\" src=\"https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/3.png\" /></p>\n<p>Click on the <strong>Build your own template in the editor</strong> to start creating your own template.</p>\n<p><img alt=\"\" src=\"https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/4.png\" /></p>\n<p>Go to your browser and download this json file:</p>\n<pre class=\"codehilite\"><code>https://inedemoassets.blob.core.windows.net/taskfiles/azure_admin/deploy-web-servers.json</code></pre>\n\n<p>Now you are at the editor, click on <strong>Load file</strong> to load the downloaded file into the editor..</p>\n<p><img alt=\"\" src=\"https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/5.png\" /></p>\n<p>The json file will be loaded to the editor.</p>\n<p><img alt=\"\" src=\"https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/6.png\" /></p>\n<p>Add the following variable element as highlighted in the image below.</p>\n<pre class=\"codehilite\"><code>\"zones\":[\"1\",\"2\",\"3\"]</code></pre>\n\n<p><img alt=\"\" src=\"https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/7.png\" /></p>\n<p>Add the following element to the virtual machine element as highlighted in the image below.</p>\n<pre class=\"codehilite\"><code>\"zones\":[\"[Variables('zones')[copyIndex()]]\"],</code></pre>\n\n<p><img alt=\"\" src=\"https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/8.png\" /></p>\n<p>Add the following element to the public ip element as highlighted in the image below.</p>\n<pre class=\"codehilite\"><code>\"zones\":[\"[Variables('zones')[copyIndex()]]\"],</code></pre>\n\n<p><img alt=\"\" src=\"https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/9.png\" /></p>\n<p>You will see that there are two subnets given, you can let them be or can remove one subnet. See image below.</p>\n<p><img alt=\"\" src=\"https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/10.png\" /></p>\n<p>If you intend to remove the subnet, name the one remaining subnet as <strong>default</strong>.</p>\n<p><img alt=\"\" src=\"https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/11.png\" /></p>\n<p>If you check the property element of the NIC, subnet name is <strong>server</strong>.</p>\n<p><img alt=\"\" src=\"https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/12.png\" /></p>\n<p>Change it to <strong>default</strong>.</p>\n<p><img alt=\"\" src=\"https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/13.png\" /></p>\n<p>Change the vmSize to <strong>Standard_D2S_V4</strong>.</p>\n<p><img alt=\"\" src=\"https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/14.png\" /></p>\n<p>After all the changes click on <strong>Save</strong> to start deploying the resources.</p>\n<p>You can also go ahead and download the arm script from the <strong>Download</strong> option.</p>\n<p>Enter a strong admin password for our webservers. Then click on <strong>Review+Create</strong> to create the resources.</p>\n<p><img alt=\"\" src=\"https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/15.png\" /></p>\n<p>Now <em>Azure</em> will verify your template. After sometime you will see <em>Validation Passed</em> that means everything is fine. Click on <strong>Create</strong> to create the resources.</p>\n<p><img alt=\"\" src=\"https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/16.png\" /></p>\n<p>After few minutes you will see <strong>Your deployment is complete</strong>, it means everything is deployed correctly.</p>\n<p>You can click on <strong>Go to resource group</strong> to go and check the resources you just deployed.</p>\n<p><img alt=\"\" src=\"https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/17.png\" /></p>\n<p>Search for <em>nsg</em> and click on <strong>Network security groups</strong> as highlighted below.</p>\n<p><img alt=\"\" src=\"https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/18.png\" /></p>\n<p>Click on <strong>Create</strong> to start creating a network security group.</p>\n<p><img alt=\"\" src=\"https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/19.png\" /></p>\n<ul>\n<li>Use the resource group assigned to you</li>\n<li>Give the network security group a name as <strong>azone-nsg</strong></li>\n<li>Use the same region we used in earlier task</li>\n</ul>\n<p>Then click on <strong>Review+Create</strong> to create the network security group.</p>\n<p><img alt=\"\" src=\"https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/20.png\" /></p>\n<p>Azure will validate your configurations and you will see something like the below image. Click on <strong>Create</strong> after you see <em>Validation passed</em></p>\n<p><img alt=\"\" src=\"https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/21.png\" /></p>\n<p>After some time the deployment will be done and you will see something like the below image.</p>\n<p>You can click on <strong>Go to resource</strong></p>\n<p><img alt=\"\" src=\"https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/22.png\" /></p>\n<p>Go to <strong>Inbound security rules</strong> of your network security group and click on <strong>Add</strong> to add new security rule.</p>\n<p><img alt=\"\" src=\"https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/23.png\" /></p>\n<p>Use the service type as <strong>HTTP</strong> and give it a name of your choice. Then click on <strong>Add</strong> to add the rule.</p>\n<p><img alt=\"\" src=\"https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/24.png\" /></p>\n<p>Go to your resource group and you can see all the resource there. Click on the <strong>webservers-VNET</strong> virtual network to configure it.</p>\n<p><img alt=\"\" src=\"https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/25.png\" /></p>\n<p>If you go to the subnets of our virutal network. You can see the default subnet. Click on it to start configuring it.</p>\n<p><img alt=\"\" src=\"https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/26.png\" /></p>\n<p>Let everthing be untouched, just change the network security group to the one we just created.</p>\n<p>Save the subnet configuration.</p>\n<p><img alt=\"\" src=\"https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/27.png\" /></p>\n<h1>Provision and configure a load balancer</h1>\n<p>Search for <em>load balancer</em> and click on <strong>Load balancers</strong> as highlighted below.</p>\n<p><img alt=\"\" src=\"https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/28.png\" /></p>\n<p>Click on create as highlighted below to create a new load balancer.</p>\n<p><img alt=\"\" src=\"https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/29.png\" /></p>\n<ul>\n<li>Use the same resource group which is assigned to you</li>\n<li>Name the load balancer as <strong>azone-lb</strong> </li>\n<li>For that use the SKU as <strong>Standard</strong> </li>\n<li>Type of balancer as <strong>Public</strong></li>\n</ul>\n<p>Then click on <strong>Next</strong> to configure the frontend IP.</p>\n<p><img alt=\"\" src=\"https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/30.png\" /></p>\n<p>Here click on <em>Add a frontend IP config</em></p>\n<p><img alt=\"\" src=\"https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/31.png\" /></p>\n<p>Click on <strong>Create new</strong> under the public IP address. Give it a name <strong>azone-lb-pip</strong> and make it <em>Zone-reduntant</em>.</p>\n<p>Give your config a name and add it.</p>\n<p><img alt=\"\" src=\"https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/32.png\" /></p>\n<p>You can see that the configuration is added.</p>\n<p>You can either choose to configure the backend pools and load balancing rules from here also, or you can create the load balancer and then configure them.</p>\n<p><img alt=\"\" src=\"https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/33.png\" /></p>\n<p>I am going to create the load balancer now and then configure it.</p>\n<p>Click on <strong>Review + create</strong> to create the load balancer.</p>\n<p><img alt=\"\" src=\"https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/34.png\" /></p>\n<p>Azure will check if everything is fine. After a few second you will see <em>Validation passed</em>. Now click on <strong>Create</strong> to finally deploy the load balancer.</p>\n<p><img alt=\"\" src=\"https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/35.png\" /></p>\n<p>When the load balancer is deployed click on <strong>Go to resources</strong>.</p>\n<p><img alt=\"\" src=\"https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/36.png\" /></p>\n<p>Now go to the backend pools of your load balancer. Click on <strong>Add</strong> to add a new backend pool.</p>\n<p><img alt=\"\" src=\"https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/37.png\" /></p>\n<p>Give your backend pool a name and select the virtual network which is used for our Virtual Machines.</p>\n<p>You will see one option of <strong>Add</strong> will pop up in the page, click on it.</p>\n<p><img alt=\"\" src=\"https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/38.png\" /></p>\n<p>Add both the virutal machine to our backend pool by checking the checkboxes in front of them.</p>\n<p><img alt=\"\" src=\"https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/39.png\" /></p>\n<p>You can see that we have both our VMs to our backend pool. </p>\n<p>Save the backend pool.</p>\n<p><img alt=\"\" src=\"https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/40.png\" /></p>\n<p>Now go to the load balancing rules of your load balancer and click on <strong>Add</strong> to add load balancing rules.</p>\n<p><img alt=\"\" src=\"https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/41.png\" /></p>\n<p>First of all create a <em>Health Proble</em>, you can see an option <strong>Create new</strong>. </p>\n<ul>\n<li>Give the health probe a name <strong>websvr-probe</strong></li>\n<li>Use the protocol as <strong>HTTP</strong></li>\n</ul>\n<p>Add the health probe to our load balancing rule.</p>\n<p><img alt=\"\" src=\"https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/42.png\" /></p>\n<ul>\n<li>Give your load balancing rule a name as <strong>azone-lbr</strong></li>\n<li>Use the frontend IP config as the one we created earlier.</li>\n<li>Select the backend port which you created in last task</li>\n<li>Use the port and backend port as <strong>80</strong></li>\n</ul>\n<p>Click on <strong>Add</strong> to add the load balancing rule to your load balancer.</p>\n<p><img alt=\"\" src=\"https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/43.png\" /></p>\n<h1>Verify the workload</h1>\n<p>Go to your primary virtual machine.</p>\n<p>You can see that the virtual machine is in <strong>Zone 1</strong> of your respective location.</p>\n<p><img alt=\"\" src=\"https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/44.png\" /></p>\n<p>Now go to your secondary virtual machine.</p>\n<p>You can see that the virtual machine is in <strong>Zone 2</strong> of your respective location.</p>\n<p><img alt=\"\" src=\"https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/45.png\" /></p>\n<p>You can get the public IP of your load balancer from the virtual machine itself. Even though these virtual machines had their own public IPs, but after configuring with the load balancer. Public IP shown to you will be the public IP of the load balancer.</p>\n<p><img alt=\"\" src=\"https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/46.png\" /></p>\n<p>You can go to your load balancer and cross check that the public IP shown in both the VMs and load balancer is the same.</p>\n<p><img alt=\"\" src=\"https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/46a.png\" /></p>\n<p>Browse this public IP address on to your browser.</p>\n<p>If you reload it some times, you will see two different outputs. Just like the below images.</p>\n<p><img alt=\"\" src=\"https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/47.png\" /></p>\n<p><img alt=\"\" src=\"https://assets.ine.com/content/labs/azure-course-labs/deploy-highly-available-virtual-machines/48.png\" /></p>\n<p>The output is just the name of virutal machines. </p>\n<p>This means that our workload is working fine. The lab is now complete.</p>",
    "flags": [],
    "min_points_to_pass": null,
    "access_type": "web",
    "user_status": "unstarted",
    "user_lab_status": null,
    "user_status_modified": null,
    "user_flags": [],
    "global_running_session": null
}