Topic 1 Question 39
2 つ選択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?
The application is using a protocol that the NAT gateway does not support.
The NAT gateway is not in a security group.
The NAT gateway is in an unsupported Availability Zone.
The NAT gateway is not in the Available state.
The port forwarding settings do not allow access to internal services from the internet.
ユーザの投票
コメント(14)
- 正解だと思う選択肢: AD
I think this one is AD according to https://docs.aws.amazon.com/vpc/latest/userguide/nat-gateway-troubleshooting.html#nat-gateway-troubleshooting-no-internet-connection
👍 4haxaffee2022/08/31 - 正解だと思う選択肢: AD
You created a public NAT gateway and followed the steps to test it, but the ping command fails, or your instances in the private subnet cannot access the internet.
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. (Ensure that your connection is using a TCP, UDP, or ICMP protocol only.)
👍 4princajen2022/09/01 no need for security group with NAT GATEWAY. Port forwarding does not exist with NAT GATEWAY but yes with NAT instance. There had to be port forwarding on the NAT INSTANCE. So for me D , and A by default
👍 2Gorille692022/09/20
シャッフルモード