ExamTopics Logo
Mail Us[email protected]
Menu
Microsoft Discussions
exam questions

Exam AZ-104 All Questions

View all questions & answers for the AZ-104 exam
Go to Exam

Exam AZ-104 topic 4 question 87 discussion

Actual exam question from Microsoft's AZ-104
Question #: 87
Topic #: 4
[All AZ-104 Questions]

HOTSPOT
-

You have an Azure App Service web app named app1.

You configure autoscaling as shown in following exhibit.



You configure the autoscale rule criteria as shown in the following exhibit.



Use the drop-down menus to select the answer choice that answers each question based on the information presented in the graphic.

NOTE: Each correct selection is worth one point.

Show Suggested Answer Hide Answer
Suggested Answer:
by sandorh at Jan. 4, 2023, 7:04 p.m.

Comments

Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
Submit Cancel
sss123412
Highly Voted 2 years, 3 months ago
2, 15 Initial instance is 1 as specified in first figure. 80% for 15 minutes reaches 10 minutes duration, but haven't reached second turn of scale out, so only one new instance is created. Since cool down time is 5 minutes, which means after one scale happens, it will count 5 minutes before counting a new 10 minutes, so 15 minutes total.
upvoted 95 times
zellck
2 years, 2 months ago
The counting of 10 mins starts from last scale out, not from after cool down timer. https://learn.microsoft.com/en-us/azure/azure-monitor/autoscale/autoscale-understanding-settings#autoscale-setting-schema Cool down (minutes) - The amount of time to wait after a scale operation before scaling again. For example, if cooldown = “PT10M”, autoscale doesn't attempt to scale again for another 10 minutes. The cooldown is to allow the metrics to stabilize after the addition or removal of instances.
upvoted 5 times
SimonSM178
2 years, 1 month ago
but the trigger to scale out says "if CPU use is greater than 75% for 10 minutes". shouldn't you interpret it is as 5 minutes cooldown = 5 minutes for which no scaling action will be performed. after 5 minutes, Azure can scale again, but it needs 10 minutes of CPU higher than 75% to perform another scale out, right? so 5 cooldown + 10 minutes (according to the rule) should be 15 minutes. please correct me if I'm wrong
upvoted 4 times
Rams_84zO6n
2 years ago
shouldn't the second answer be 5 minutes? First time the stats are not available, so it has to wait 10 min for stats, increase instance count, cool down for 5 minutes. Now it has stats that goes back to 10 minutes, so there is no need to wait for another 10 minutes to compute stats. So min. time to wait before additional instance creation must be 5 minutes. Do you agree?
upvoted 8 times
SimonSM178
2 years ago
I don't think so, the action trigger is CPU usage greater than 70% for 10 minutes. It doesn't say "as soon as CPU usage is greater than 70%". In my opinion, there are 5 minutes cooldown since the last scale-out, if after the scale-out CPU still is at 70%, then you need 10 minutes more.
upvoted 3 times
...
...
...
...
755aa96
6 months, 1 week ago
No, it is 3, 5. This guy tested it: "Remember, the cooldown period only temporarily pauses scaling operations, but under the hood the time and metrics are still being analysed and recorded."
upvoted 5 times
...
KpiTalisTTT
1 year, 9 months ago
This is not how it works, after 5min of CD Azure doesn't need to wait another 10 min...after 5 min CD if the CPU is still greater than 70% it will increment another instance.
upvoted 16 times
KpiTalisTTT
1 year, 9 months ago
BTW my answers are 2 and 5
upvoted 9 times
KpiTalisTTT
1 year, 8 months ago
NVM it is 2-15
upvoted 5 times
GoldenDisciple2
1 year, 7 months ago
I appreciate your commitment to correcting your comment. lol I was a little confused at first. Very much appreciated.
upvoted 5 times
...
...
...
...
...
Spooky7
Highly Voted 2 years ago
I don't know why but it seems that majority of people commenting here don't know exactly how autoscaling works. So let me explain few things. Duration value is only used for data range - how much data autoscaling system has to aggregate to determine if rule applies or not. Cooldown - how much time has to pass before next autoscale operation to trigger. So once you start you app the first autoscale may happen not earlier than after duration value (because you need specific data range). Each next will happen every cooldown value. So: - first scale out will happen after 10 minutes (duration value) - next scale out will happen after 15 minutes (+5 minutes of cooldown) Therefore answer for first question is 3 instances Second one is simpler. Scaling operation just happened. So next scaling may happen after cooldown time which is 5 minutes.
upvoted 90 times
RanPo
7 months, 2 weeks ago
Savior
upvoted 1 times
...
pasangawa
7 months, 3 weeks ago
agree. the 10 is the condition only but when it needs to scale up again, it will be after 5min
upvoted 1 times
...
CheMetto
9 months ago
Correct. 3 and 5
upvoted 2 times
...
rfxavier
11 months, 4 weeks ago
I agree with this answer, 3 and 5. Let me rewrite some words on the comment for better understanding. When it's said "Cooldown - how much time has to pass before next autoscale operation to trigger", the correct term is: "Cooldown - how much time has to pass before next RULE CHECK to DETERMINE IF ANOTHER AUTOSCALE OPERATION WILL trigger". Imagine the scenario that it's 80% cpu for 14 minutes and 69% for 1 minute. There will be 1 check for rule that results in scale out in minute 10, 5 min cooldown, then on minute 15 there will be another check for the rule, which will consider data range from minute 5 up to minute 15. In this time range will eventually result in an average CPU still greater than 70% (9 minutes 80% + 1 minute 69%). So the core point to observe is that there are checking for rules on a set time range, scaling out operation happening (or not) is a result of the checking of the rule.
upvoted 2 times
...
Load full discussion...
...
Mitko_V_Milkov
Most Recent 4 months, 1 week ago
Run this question in ChatGPT to understand why the answer is correct: 2 and 15 "App1 is configured to auto scaling as such: Scale Out when CPU over 70% increase by 1 instance. Instances limit min 1, max 5, default 1. Autoscale rule criteria is: if CPU is more than 70%, for duration of 10 minutes, increase instances by 1. Cool down period is 5 minutes. The questions are: 1. How many instances of the app1 will be running if the CPU is 80% for 15 minutes? 2. After how many minutes another instance will be created after the first scale-out?"
upvoted 2 times
...
[Removed]
5 months, 2 weeks ago
WRONG 3 5 https://learn.microsoft.com/en-us/azure/azure-monitor/autoscale/autoscale-get-started#cool-down-period-effects
upvoted 4 times
...
zeuge
5 months, 4 weeks ago
Due to the lack of a clear answer, I created a lab. Here are the conditions: default VM count - 1, minimum VM - 1, maximum VM count - 5. VM size - Standard_B2s. If the CPU load exceeds 80% for 10 minutes, increase the count by 1; if it falls below 40% for 10 minutes, decrease the count by 1. Cooldown is set to 5 minutes in both cases. On the first instance, a script was run using PowerShell at 11:57, and the CPU load reached 95-100%. The first scaling occurred at 12:06, the second at 12:11, and the third at 12:17.
upvoted 3 times
...
Stunomatic
5 months, 4 weeks ago
in first cycle - 10 minutes in second cycle - duration + cool downtime =15 mins
upvoted 1 times
...
[Removed]
7 months, 1 week ago
CORRECT
upvoted 1 times
[Removed]
5 months, 2 weeks ago
after some researches, 3 & 5 are correct
upvoted 2 times
...
...
pasangawa
7 months, 3 weeks ago
BOX1: 3 instances. CPU went up for 15min. it will meet the condition of greater than 75 for duration of 10min so 1initial +1. then Cooldown is 5min so after 5min it adds another instance since condition still 75. BOX2: 5 min many are confused here. after the scale out instance of 10min is met, it will rely on cool down time to increase the instance again and not the duration. 10min is just a condition. Since it's asking for the minimum time after the first scale out, 5min.
upvoted 1 times
...
OpOmOp
8 months, 3 weeks ago
It seems to be 3 and 5 Answer (and test case as well) is here https://cloudbuild.co.uk/azure-virtual-machine-scale-set-duration-and-cool-down-explained/
upvoted 5 times
...
Ni22
10 months, 2 weeks ago
6/13/24 on exam
upvoted 2 times
...
1828b9d
1 year, 1 month ago
This question was in exam 01/03/2024
upvoted 6 times
...
Amir1909
1 year, 1 month ago
Correct
upvoted 1 times
...
SDiwan
1 year, 2 months ago
First answer is 3 . After 10 mins, first scale out happens (+1), then after 5 mins of cooling the system checks if last 10 mins usage was above thresold, then 2nd scale out (+1). So total, 3 instances after 15 mins. 2. 5 , cooling period is 5 mins, so after first scale out, wait for 5 mins and then check again the usage.
upvoted 7 times
bobothewiseman
1 year ago
wrong! after 10mins , +1 instance only. Then 5 minutes cool down. So answer is 1 (default) + 1 (scale out) = 2. The question states "for 15minutes" not after 15minutes. box 2 answer is 15 after scaleout = 5 mins cool down + 10mins duration = 15mins
upvoted 3 times
...
...
amsioso
1 year, 4 months ago
2, 15 "The cooldown period for each rule dictates how long after the previous scale action (whatever rule [..] was [triggered]), the rule can be applied [again]." Source: https://github.com/MicrosoftDocs/azure-docs/issues/17169
upvoted 1 times
amsioso
1 year, 4 months ago
Sorry 3, 5 https://www.youtube.com/watch?app=desktop&v=EbiID16PDuk https://www.linkedin.com/pulse/miss-configuration-azure-auto-scaling-feature-radu-vunvulea/ https://learn.microsoft.com/en-us/azure/azure-monitor/autoscale/autoscale-get-started#cool-down-period-effects
upvoted 10 times
...
...
SgtDumitru
1 year, 4 months ago
In order to answer the question, is important to understand how Azure scale actions are triggered. Lets have same params as in question: 10 minutes duration of scale out verification and 5 minutes of cool down Once action meets criteria for 10 minutes, action is triggered. After that, 5 minutes is reserved for scale out action to take in place and App to rebalance the load. Next, if load is still meet the auto-scale rule, it will start counting another 10 minutes to see if even after previous scale-out load is high. If yes, only than a new instance will start running and another 5 minutes of cool down will be started. Therefore, answer for this questions are: 1) 2 instances; 2) 15 minutes.
upvoted 2 times
...
Batiste2023
1 year, 6 months ago
The answers are 3 and 5. "The cooldown period for each rule dictates how long after the previous scale action (whatever rule [..] was [triggered]), the rule can be applied [again]." Source: https://github.com/MicrosoftDocs/azure-docs/issues/17169 The first question is a bit theoretical: it makes it appear that the load stays constant at 80% for 15 minutes - which would mean that after the seconde instance is created after 10 minutes, demand increases accordingly so that even then 80% load is maintained, with no load decrease. Anyway, were that to happen, then after another 5 minutes of cooling down, the rule would be allowed to be triggered again, after 15 minutes in total - to create a third instance.
upvoted 8 times
mark55665
1 year, 5 months ago
agree this answer
upvoted 2 times
...
...
[Removed]
1 year, 6 months ago
3,5 As it mentioned by https://learn.microsoft.com/en-us/azure/app-service/environment/app-service-environment-auto-scale
upvoted 6 times
...
Load full discussion...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel
exam
Someone Bought Contributor Access for:
SY0-701
London, 1 minute ago