You have started a new job and are reviewing your company’s infrastructure on AWS You notice one web
application where they have an Elastic Load Balancer (&B) in front of web instances in an Auto Scaling Group
When you check the metrics for the ELB in CloudWatch you see four healthy instances In Availability Zone (AZ)
A and zero in AZ B There are zero unhealthy instances.
What do you need to fix to balance the instances across AZs?
A.
Set the ELB to only be attached to another AZ
B.
Make sure Auto Scaling is configured to launch in both AZs
C.
Make sure your AMI is available in both AZs
D.
Make sure the maximum size of the Auto Scaling Group is greater than 4
B
1
0
B.
0
0
B – zero unhealthy instances, and zero healthy == 0 instances. Which means ensure auto-scaling is set to launch in both AZs.
0
0
B
0
0
Still couldn’t understand it, can somebody give any reasonable explanation
0
0
We need to balance AZs
A is wrong because in this case Auto scaling will work in 1 AZ only
C is wrong because AMI is available across the region
D is wrong because there is no need/Logoc to increase the instance count.
Only B makes sense.
1
0
B
We need to balance AZs
A is wrong because in this case Auto scaling will work in 1 AZ only
C is wrong because AMI is available across the region
D is wrong because there is no need/Logoc to increase the instance count.
Only B makes sense.
0
0