The DevOps team deploys five virtual machines (VMs) to Azure that host a web application in Internet Information Services (IIS). The team wants you to create a load balancer that routes traffic to the VMs that are available.
The development team creates a web page named HealthCheck.aspx that, when responding with a 200 request, indicates that the VM is available for servicing web requests. If a VM fails to respond after four consecutive checks, the VM should be considered unavailable.
You need to use PowerShell to create a Load Balancer configuration that checks the health of the VMs.
How should you complete the cmdlet?
-PLACEHOLDER 2 healthcheck.aspx
-PLACEHOLDER 3 4
You should use the following PowerShell cmdlet:
The New-AzureRmLoadBalancerProbeConfig cmdlet creates a health probe. A health probe is a configuration that specifies how Azure Load Balancer determines whether or not a VM is available. The -RequestPath parameter specifies the path to an HTTP resource that determines availability, which is HealthCheck.aspx in this scenario. The -ProbeCount parameter specifies the number of consecutive failures that must occur before the VM is considered unavailable, which is four in this scenario.
You should not use the New-AzureRmLoadBalancerFrontendIpConfig cmdlet. This cmdlet creates a front-end IP configuration, which simply specifies the public IP address of the Load Balancer. It does not perform a health check.
You should not specify the WhatIf parameter. This parameter is part of the New-AzureRmLoadBalancer cmdlet. It simply displays what would happen if the cmdlet is run successfully.
You should not specify the Confirm parameter. This parameter is part of the New-AzureRmLoadBalancer cmdlet. It simply prompts for confirmation before creating a Load Balancer.