You work for a construction company that has their production environment in AWS. The production
environment consists of 3 identical web servers that are launched from a standard Amazon linux AMI using
Auto Scaling. The web servers are launched in to the same public subnet and belong to the same security
group. They also sit behind the same ELB. You decide to do some test and dev and you launch a 4th EC2
instance in to the same subnet and same security group. Annoyingly your 4th instance does not appear to have
internet connectivity. What could be the cause of this?
A.
You need to update your routing table so as to provide a route out for this instance.
B.
Assign an elastic IP address to the fourth instance.
C.
You have not configured a NAT in the public subnet.
D.
You have not configured a routable IP address in the host OS of the fourth instance.
Answer B !Assign an elastic IP address to the fourth instance.
I agree, answer B.
Agree, correct answer – B.
Ref – https://acloud.guru/forums/aws-certified-solutions-architect-associate/discussion/-KGHG-asPXkgK11gu1mk/why-does-this-need-an-eip
B
I don’t know. But this problem is asking for the cause rather than a solution!
Unless the B changes to “You have not assigned an elastic IP address to this instance”
B
B
Thanks everyone, B is the correct answer. phew!
FYI, here the fourth instance is also launched in public instance (similar to other 3 instances)
Option C is wrong because NAT(an public instance) is used for providing internet access to instances in private subnet.
Option B looks more appropriate.
This is wrong, answer is B.