A company is using an Amazon EC2 Auto Scaling group to support a workload. A SysOps administrator finds that the Auto Scaling group is configured with two similar scaling policies. One scaling…

Question

Options

• AAmazon EC2 Auto Scaling will add 5 instances.
• BAmazon EC2 Auto Scaling will add 10 instances.
• CAmazon EC2 Auto Scaling will add 15 instances.
• DThe Auto Scaling group will not scale because of conflicting policies.

• A
  8% (2)
• B
  88% (23)
• D
  4% (1)

Explanation

When two simple scaling policies trigger at the same threshold, Amazon EC2 Auto Scaling executes both policies - but applies only the one that results in the greatest capacity change, which is 10 instances (option B). Options A and C are wrong because Auto Scaling doesn't arbitrarily pick the smaller policy, nor does it sum both policies (5 + 10 = 15); summing would only apply to step scaling adjustments within a single policy. Option D is wrong because conflicting policies don't cause a failure - AWS resolves the conflict by favoring the most impactful action, a behavior called the "largest result" rule. Memory tip: Think of Auto Scaling as a "more is safer" system - when in doubt, it scales out more aggressively to protect your workload, so it always picks the policy that adds the most instances.

No community discussion yet for this question.