You have an environment that consists of a public subnet using Amazon VPC and 3 instances that are running
in this subnet. These three instances can successfully communicate with other hosts on the Internet. You
launch a fourth instance in the same subnet, using the same AMI and security group configuration you used for
the others, but find that this instance cannot be accessed from the internet. What should you do to enable
Internet access?
A.
Deploy a NAT instance into the public subnet.
B.
Assign an Elastic IP address to the fourth instance.
C.
Configure a publically routable IP Address in the host OS of the fourth instance.
D.
Modify the routing table for the public subnet.
C, probably
http://www.aiotestking.com/amazon/what-should-you-do-to-enable-internet-access-2/
I don’t think it is B and the others aren’t right.
I’m changing to B
Seems strange that you would launch an instance in public subnet and it still need an elastic IP assigned.
Nothing in the question about a managed service so you do have access to the console of the instance. Could be EC2 instances. As screwed up as the terminology is in the AWS questions, I can’t see them getting guest/host right in terms of virtualization where the host is the hypervisor.
B. C is wrong, since one can’t even access the HOST os.
Its B