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 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 -
Click on the arrows to vote for the correct answer
A. B. C. D.C
In-guest VM metrics with the Azure diagnostics extension
The Azure diagnostics extension is an agent that runs inside a VM instance. The agent monitors and saves performance metrics to Azure storage. These performance metrics contain more detailed information about the status of the VM, such as AverageReadTime for disks or PercentIdleTime for CPU. You can create autoscale rules based on a more detailed awareness of the VM performance, not just the percentage of CPU usage or memory consumption.
https://docs.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-autoscale-overviewTo implement a virtual machine scale set instance for a stateless third-party website that is being migrated from on-premises to Azure, you need to choose the correct autoscaling settings to ensure that the website can handle varying numbers of visitors throughout the year.
Option A: Using a webhook to log autoscale failures is not the correct solution for scaling a virtual machine scale set instance. Webhooks are used to trigger actions or events in external systems, and logging autoscale failures would not help to scale the instance.
Option B: Using an autoscale setting to scale instances vertically is also not the correct solution. Vertical scaling involves adding more resources to a single instance, such as adding more memory or CPU, and it is not an effective solution for handling varying levels of traffic.
Option C: Using only default diagnostics metrics to trigger autoscaling is not the best solution either. While default metrics can be used to trigger autoscaling, they may not always be sufficient to handle the varying traffic levels of a website. Using custom metrics or adding more metrics to the default metrics can help provide a more accurate picture of the website's traffic patterns.
Option D: The correct solution is to use an autoscale setting to define more profiles that have one or more autoscale rules. This allows for more granular control over how the virtual machine scale set instance is scaled based on varying traffic levels. Each profile can have different rules based on different metrics, allowing the instance to scale up or down as needed. This can help ensure that the website is always available and responsive to users, while also minimizing costs by only using the necessary resources.
Overall, option D is the best solution for implementing a virtual machine scale set instance for a stateless third-party website that is being migrated to Azure.