Migrating a Stateless Third-Party Website to Azure: Virtual Machine Scale Set Implementation

Implementing a Virtual Machine Scale Set Instance

Question

A company is migrating an existing on-premises third-party website to Azure. The website is stateless.

The company does not have access to the source code for the website. They do not have the original installer.

The number of visitors at the website varies throughout the year. The on-premises infrastructure was resized to accommodate peaks but the extra capacity was not used.

You need to implement a virtual machine scale set instance.

What should you do?

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D. E. F.

D

https://docs.microsoft.com/en-us/azure/azure-monitor/platform/autoscale-custom-metric

To implement a virtual machine scale set instance for a stateless third-party website, you should use Azure Autoscale. Autoscale is a feature in Azure that automatically adjusts the number of instances in a virtual machine scale set to meet changing demand.

The autoscale feature can be configured to monitor the average CPU usage of the instances in the virtual machine scale set. When the average CPU usage exceeds a certain threshold (e.g., 80 percent), Autoscale can scale out the number of instances in the virtual machine scale set to handle the increased demand.

Answer C: Scale out by one instance when the average CPU usage of one of the instances is over 80 percent is a correct option.

To configure Autoscale, you can use Azure Monitor to create custom metrics that track the performance of your website. These custom metrics can include measures such as response time, network traffic, and other relevant indicators of website performance. When you configure Autoscale to use these custom metrics, it can adjust the number of instances in the virtual machine scale set to meet changing demand based on the performance of the website.

Answer D: Use Azure Monitor to create autoscale settings using custom metrics is also a correct option.

When configuring Autoscale, you should also consider the maximum number of instances that should be allowed in the virtual machine scale set. Answer E: Use an autoscale setting with unlimited maximum number of instances is a possible option, but it may result in higher costs and potential performance issues. It is recommended to set a maximum number of instances based on the expected peak demand for the website.

Answer A: Use an autoscale setting to scale instances vertically is incorrect because vertical scaling refers to increasing the resources (e.g., CPU, memory) of an existing instance, whereas Autoscale adjusts the number of instances in a scale set.

Answer B: Create 100 autoscale settings per resource is incorrect because creating multiple Autoscale settings for the same resource can be confusing and difficult to manage.

Answer F: Use a webhook to log autoscale failures is also incorrect because a webhook is a way to trigger an action when an event occurs in Azure, but it is not relevant to configuring Autoscale for a virtual machine scale set.