A SysOps administrator migrates NAT instances to NAT gateways. After the migration, an application that is hosted on Amazon EC2 instances in a private subnet cannot access the internet. Which of the following are possible reasons for this problem? (Choose two.)
Select an option, then click Submit answer.
Reference / correct answer:
The NAT gateway is not in the Available state.
Most accepted answer: D. The NAT gateway is not in the Available state.
Community votes: A=7, C=3, D=9, E=1
Selected Answer: AD A - NAT gateway does not support IPv6 D - NAT gateway itself has issues or not yet ready upvoted 7 times
A and D Causes The cause of this problem might be one of the following: The NAT gateway is not ready to serve traffic. Your route tables are not configured correctly. Your security groups or network ACLs are blocking inbound or outbound traffic. You're using an unsupported protocol. upvoted 1 times
A - TCP, UDP & ICMP only D - Must be in available state https://docs.aws.amazon.com/vpc/latest/userguide/nat-gateway-troubleshooting.html#nat-gateway-troubleshooting-no-internet-connection upvoted 2 times
Selected Answer: CD https://docs.aws.amazon.com/vpc/latest/userguide/nat-gateway-troubleshooting.html#nat-gateway-troubleshooting-unsupported-az From the doc above: - AZ is unsupported - C - Must be in Available state - D upvoted 1 times kret 2 years, 4 months ago Your link points to article to troubleshoot NATGW creation errors. Question clearly says that NATGW was created, but is not working. So it can't be Unsupported AZ. upvoted 1 times ...
Your link points to article to troubleshoot NATGW creation errors. Question clearly says that NATGW was created, but is not working. So it can't be Unsupported AZ. upvoted 1 times