After launching an instance that you intend to serve as a NAT (Network Address Translation) device in a public
subnet you modify your route tables to have the NAT device be the target of internet bound traffic of your
private subnet. When you try and make an outbound connection to the Internet from an instance in the private
subnet, you are not successful.
Which of the following steps could resolve the issue?
Attaching a second Elastic Network interface (ENI) to the NAT instance, and placing it in the private subnet
Attaching a second Elastic Network Interface (ENI) to the instance in the private subnet, and placing it in the
Disabling the Source/Destination Check attribute on the NAT instance
Attaching an Elastic IP address to the instance in the private subnet