AZ-204 Practice Question: Monitor, troubleshoot, and optimize Azure solutions

Answer analysis

Option-by-option breakdown

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

• ✓

  Navigate to App Service, then scale out, then enable autoscale, then configure rules, then set limits.

  Why this is correct

  To configure autoscale for an Azure App Service, the correct sequence involves first navigating to the specific App Service resource. From there, you access the 'Scale out (App Service plan)' blade, which is where the autoscale feature resides. Within this blade, you enable autoscale, then proceed to define the specific scaling rules based on metrics like CPU or HTTP queue length, and finally, set the minimum and maximum instance limits to control the scaling boundaries.

• ✗

  Navigate to App Service, then enable autoscale, then scale out, then configure rules, then set limits.

  Why it's wrong here

  This order is incorrect because the 'Autoscale' configuration option is not directly available at the top level of the App Service blade. Instead, it is nested within the 'Scale out (App Service plan)' section, which must be accessed first. Attempting to enable autoscale before navigating to the dedicated scaling blade would not be possible within the Azure portal's user interface, as the option would not be presented.

• ✗

  Navigate to App Service, then scale out, then configure rules, then enable autoscale, then set limits.

  Why it's wrong here

  This sequence is incorrect because scaling rules, which dictate when and how instances are added or removed, are a direct component of the autoscale profile. Autoscale must first be explicitly enabled within the 'Scale out' blade before any specific rules can be defined or configured. Attempting to configure rules prior to enabling the autoscale feature would result in an unavailable or unconfigurable state for those settings, as the underlying scaling mechanism isn't active.

• ✗

  Navigate to App Service, then scale out, then enable autoscale, then set limits, then configure rules.

  Why it's wrong here

  This order is incorrect because the purpose of autoscale limits is to define the minimum and maximum number of instances that the App Service can scale to. These limits are typically set *after* the scaling rules have been established, as the rules determine the conditions under which scaling actions occur. Setting limits before defining the operational rules would be premature and could lead to an incomplete or illogical scaling configuration, as the system wouldn't know *when* to scale within those boundaries.

Go deeper

Related to this question