Examkin

Soru

Zorluk: OrtaConfigure Azure Monitor Autoscale Rules and Metrics

An organization runs a web application on an Azure App Service plan that currently has a capacity of 22 instances. You need to configure autoscale rules with a minimum of 22 instances and a maximum of 1010 instances. You configure a scale-out rule to increase the instance count by 11 when the Average CPU percentage is greater than 75%75\%. You want to configure a scale-in rule that decreases the instance count by 11 when the CPU percentage is lower than a specific threshold. Which configuration should you use to prevent flapping when scaling out from 22 to 33 instances?

  1. Set the scale-in threshold to CPU percentage less than 45%45\% using the Average metric aggregationCevap
  2. B
    Set the scale-in threshold to CPU percentage less than 55%55\% using the Average metric aggregation
  3. C
    Set the scale-in threshold to CPU percentage less than 70%70\% using the Maximum metric aggregation
  4. D
    Set the scale-in threshold to CPU percentage less than 45%45\% and downgrade the App Service plan to the Basic tier

Cevap

Set the scale-in threshold to CPU percentage less than 45%45\% using the Average metric aggregation.
The correct option sets the scale-in threshold to 45%45\% with the Average aggregation. At the point of scaling out from 22 to 33 instances, the average CPU percentage is just above 75%75\%, representing a total load of 150%150\%. Upon adding a third instance, the average CPU per instance drops to 50%50\% (150%/3150\% / 3). Setting the scale-in threshold below 50%50\% (such as 45%45\%) ensures the scale-in rule is not immediately triggered, thereby preventing flapping.

Adım Adım Çözüm

1
Calculate the total CPU percentage load at the scale-out threshold.
Total CPU workload is 150%150\%.
To determine the aggregate workload required to trigger the scale-out rule.
2
Calculate the post-scale-out average CPU percentage per instance.
New average CPU percentage per instance is 50%50\%.
To find the target CPU utilization immediately after the scale-out action completes.
3
Determine the maximum scale-in threshold to avoid flapping.
The threshold must be less than 50%50\%, so 45%45\% with Average metric aggregation is the correct configuration.
If the scale-in threshold were 50%50\% or higher, the newly scaled scale set would immediately trigger a scale-in rule, causing a flapping loop.

Anahtar Kavram

Prevention of flapping in autoscale rules by ensuring the scale-in threshold is set sufficiently lower than the post-scaling-out average metric utilization.
Bu soruyu puanla

Konular

Configure Azure Monitor Autoscale Rules and Metrics

Bu konudan daha fazla soru