AZ-204 Develop Azure compute solutions Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Configure scheduled scaling in the app

  Why it's wrong here

  Scheduled scaling allows you to define specific times of day or days of the week when your App Service plan should automatically scale out or in. While useful for predictable traffic patterns, this time-based approach cannot react dynamically to unexpected spikes in load or sudden increases in slow response times that occur outside of predefined schedules. Therefore, it would not automatically address an immediate issue of slow response times caused by unpredictable demand.

• ✗

  Manually increase instance count

  Why it's wrong here

  Manually increasing the instance count requires an administrator to actively monitor the web app's performance metrics and then intervene to add more instances. This approach is entirely reactive and not automated, meaning there will be a significant delay between the onset of slow response times and the administrator's action, leading to continued poor user experience during that period. Furthermore, it doesn't automatically scale down when demand decreases, potentially leading to unnecessary operational costs.

• ✗

  Configure scale up in the App Service plan

  Why it's wrong here

  Scaling up, also known as vertical scaling, involves increasing the resources of existing instances, such as CPU, memory, or disk space, by moving to a higher App Service plan tier or instance size. While a single, more powerful instance can handle more load, it does not distribute the workload across multiple servers, which is often more effective for web apps experiencing slow response times due to a high volume of concurrent requests. If the bottleneck is concurrency rather than individual instance capacity, scaling up may not provide the necessary performance improvement or redundancy.

• ✓

  Configure autoscale rules in the App Service plan

  Why this is correct

  Autoscale rules in an App Service plan enable the system to automatically adjust the number of instances (scale out or in) based on predefined performance metrics, such as CPU utilization, memory usage, or HTTP queue length. By configuring rules to scale out when metrics like CPU usage exceed a threshold, the web app can dynamically add more instances to distribute the load and improve response times. This ensures the application maintains optimal performance and availability even during unpredictable traffic spikes, without requiring manual intervention.

Go deeper

Related to this question