HOTSPOT
You have an Azure web app named App1 that contains the following autoscale conditions: The default auto created scale condition has a scale mode that has Scale to a specific instance count set to 2.
Scale condition 1 has the following configurations:
– Scale mode: Scale to a specific instance count
– Instance count: 3
– Schedule: Specify start/end dates
– Start date: August 1, 2019, 06:00
– End date: September 1, 2019, 18:00
Scale condition 2 has the following configurations:
– Scale mode: Scale to a specific instance count
– Instance count: 4
– Schedule: Repeat specific days
– Repeat every: Monday
– Start time: 06:00
– End time: 18:00
Scale condition 3 has the following configurations:
– Scale mode: Scale to a specific instance count
– Instance count: 5
– Schedule: Repeat specific days
– Repeat every: Monday
– Start time: 15:00
– End time: 20:00
You need to identify the number of running App1 instances.
What should you identify? To answer, select the appropriate options in the answer area.
Answer: 
Explanation:
Box 1: 5
Scale condition 1, Scale condition 2, and Scale condition 3 applies.
Scale condition 3 takes precedence as it the largest increase in the number of instances.
Box 2: 5
Scale condition 1 does not apply as its end date is exceeded.
Scale condition 2 and Scale condition 3 applies.
Scale condition 3 takes precedence as it the largest increase in the number of instances.
When you configure multiple policies and rules, they could conflict with each other.
Autoscale uses the following conflict resolution rules to ensure that there is always a sufficient number of instances running:
– Scale-out operations always take precedence over scale-in operations.
– When scale-out operations conflict, the rule that initiates the largest increase in the number of instances takes precedence.
– When scale in operations conflict, the rule that initiates the smallest decrease in the number of instances takes precedence.
References:
https://docs.microsoft.com/en-us/azure/architecture/best-practices/auto-scaling