ExamGecko
Question list
Search
Search

List of questions

Search

Related questions











Question 295 - SOA-C02 discussion

Report
Export

ASysOps administrator configures an application to run on Amazon EC2 instances behind an Application Load Balancer (ALB) in a simple scaling Auto Scaling group with the default settings. The Auto Scaling group is configured to use the RequestCountPerTarget metric for scaling. The SysOps administrator notices that the RequestCountPerTarget metric exceeded the specified limit twice in 180 seconds.

How will the number of EC2 instances in this Auto Scaling group be affected in this scenario?

A.
The Auto Scaling group will launch an additional EC2 instance every time the RequestCountPerTarget metric exceeds the predefined limit.
Answers
A.
The Auto Scaling group will launch an additional EC2 instance every time the RequestCountPerTarget metric exceeds the predefined limit.
B.
The Auto Scaling group will launch one EC2 instance and will wait for the default cooldown period before launching another instance.
Answers
B.
The Auto Scaling group will launch one EC2 instance and will wait for the default cooldown period before launching another instance.
C.
The Auto Scaling group will send an alert to the ALB to rebalance the traffic and not add new EC2 instances until the load is normalized.
Answers
C.
The Auto Scaling group will send an alert to the ALB to rebalance the traffic and not add new EC2 instances until the load is normalized.
D.
The Auto Scaling group will try to distribute the traffic among all EC2 instances before launching another instance.
Answers
D.
The Auto Scaling group will try to distribute the traffic among all EC2 instances before launching another instance.
Suggested answer: B

Explanation:

When using the RequestCountPerTarget metric for scaling in an Auto Scaling group, the behavior of instance scaling follows specific rules set by Auto Scaling policies and cooldown periods:

Scaling Trigger: The Auto Scaling group triggers a scaling action whenever the RequestCountPerTarget exceeds the predefined limit set in the scaling policy.

Cooldown Period: After launching an EC2 instance due to a scaling action, the Auto Scaling group enters a cooldown period. During this period, despite further breaches of the threshold, no additional instances will be launched. This is designed to give the newly launched instance time to start and begin handling traffic, preventing the Auto Scaling group from launching too many instances too quickly.

This mechanism helps maintain efficient use of resources by adapting to changes in load while avoiding rapid, unnecessary scaling actions.

asked 16/09/2024
Robert Hernady
31 questions
User
Your answer:
0 comments
Sorted by

Leave a comment first