Azure VM Scale Set Health Check Recommendations | AZ-400 Exam | Microsoft
Question
You have an Azure DevOps organization named Contoso and an Azure subscription. The subscription contains an Azure virtual machine scale set named VMSS1 and an Azure Standard Load Balancer named LB1. LB1 distributes incoming requests across VMSS1 instances.
You use Azure DevOps to build a web app named App1 and deploy App1 to VMSS1. App1 is accessible via HTTPS only and configured to require mutual authentication by using a client certificate.
You need to recommend a solution for implementing a health check of App1. The solution must meet the following requirements:
-> Identify whether individual instances of VMSS1 are eligible for an upgrade operation.
-> Minimize administrative effort.
What should you include in the recommendation?
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D.D
Monitoring your application health is an important signal for managing and upgrading your deployment. Azure virtual machine scale sets provide support for rolling upgrades including automatic OS-image upgrades, which rely on health monitoring of the individual instances to upgrade your deployment. You can also use health extension to monitor the application health of each instance in your scale set and perform instance repairs using automatic instance repairs.
https://docs.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-health-extensionThe recommended solution for implementing a health check of App1 that meets the stated requirements of identifying eligible VMSS1 instances for an upgrade operation and minimizing administrative effort would be to use an Azure Load Balancer health probe.
A health probe is a mechanism used to determine the health of an application or service running on an Azure virtual machine. In this scenario, a health probe can be configured on the Azure Load Balancer (LB1) to monitor the health of App1 instances running on VMSS1. The health probe can be set up to check whether App1 is responding to HTTPS requests and verify the mutual authentication configuration by using a client certificate.
By configuring the health probe on LB1, it becomes responsible for monitoring the health of the App1 instances running on VMSS1. If an instance fails the health probe test, LB1 can automatically stop routing traffic to that instance and route traffic to a healthy instance instead. Additionally, Azure Load Balancer provides an easy-to-use dashboard to visualize the health of each backend instance.
This solution addresses the first requirement of identifying whether individual instances of VMSS1 are eligible for an upgrade operation. If an instance fails the health probe test, LB1 will stop routing traffic to it, which can indicate that it may not be eligible for an upgrade operation. This information can be used to inform the upgrade decision-making process.
Using an Azure Load Balancer health probe also minimizes administrative effort since it provides an automated way to monitor the health of App1 instances. There is no need for manual monitoring or scripting.
Option B, Azure Monitor autoscale, could also be a valid solution, but it may not be as effective in identifying the health of individual App1 instances. Autoscale allows for automatic scaling of VMSS1 based on predefined metrics, but it does not provide detailed information on the health of each instance.
Option C, the Custom Script Extension, is not an appropriate solution for this scenario since it is used to run custom scripts on Azure virtual machines. This solution would require additional scripting to monitor the health of App1 instances and may not provide the same level of automated monitoring as using a health probe.
Option D, the Application Health extension, is not a valid solution since it is not an Azure service or feature.
