This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
You've defined an autoscale condition with four autoscale rules. The first rule scales out when the CPU utilization reaches 70 percent. The second rule scales back in when the CPU utilization drops below 50 percent. The third rule scales out if memory occupancy exceeds 75 percent. The fourth rule scales back in when memory occupancy falls below 50 percent. When will the system scale out?
When CPU utilization reaches 70 percent, or memory occupancy exceeds 75 percent
When CPU utilization reaches 70 percent, and memory occupancy exceeds 75 percent
You can't do this with a single autoscale condition. An autoscale condition can only contain autoscale rules that use the same metric
An autoscale rule defines a scale-out action that increases the instance count when the disk queue length exceeds 10. The system scaled out two minutes ago, but the disk queue length is still over 10. When will the system scale-out again?
The autoscale rule will trigger another autoscale action immediately, and will continue doing so until the disk queue length drops below 10, or the maximum number of instances have been created.
The autoscale rule won't run again until the system has scaled back in.
The autoscale rule won't trigger the action again until the cool down period for the rule has expired. If the disk queue length is still over 10 at this time, the action will be performed.
You must answer all questions before checking your work.
Continue
Was this page helpful?