SOA-C02 · Question #25
A company has deployed a web application in a VPC that has subnets in three Availability Zones. The company launches three Amazon EC2 instances from an EC2 Auto Scaling group behind an Application…
The correct answer is C. The Auto Scaling group was configured for only two Availability Zones. The autoscaling group is responsable to add the instances in the subnets.
Question
A company has deployed a web application in a VPC that has subnets in three Availability Zones. The company launches three Amazon EC2 instances from an EC2 Auto Scaling group behind an Application Load Balancer (ALB). A SysOps administrator notices that two of the EC2 instances are in the same Availability Zone, rather than being distributed evenly across all three Availability Zones. There are no errors in the Auto Scaling group's activity history. What is the MOST likely reason for the unexpected placement of EC2 instances?
Options
- AOne Availability Zone did not have sufficient capacity for the requested EC2 instance type.
- BThe ALB was configured for only two Availability Zones.
- CThe Auto Scaling group was configured for only two Availability Zones.
- DAmazon EC2 Auto Scaling randomly placed the instances in Availability Zones.
How the community answered
(23 responses)- A4% (1)
- B9% (2)
- C74% (17)
- D13% (3)
Explanation
The autoscaling group is responsable to add the instances in the subnets.
Topics
Community Discussion
No community discussion yet for this question.