Answer - A, C and D
This scenario`s configuration includes a virtual private cloud (VPC) with a single public subnet and an internet gateway to enable communication over the internet.
An internet gateway. This connects the VPC to the internet and other AWS services.
A custom route table is associated with the subnet. The route table entries enable instances in the subnet to use IPv4 to communicate with other instances in the VPC, and communicate directly over the internet. A subnet, that is associated with a route table and that has a route to an internet gateway, is known as a public subnet.
Instances receive a Public IP address so that it is reachable from outside the VPC. This IP address might change if the instance stops and starts. Alternatively, you can use an Elastic IP Address that remains static.
Only use a Public IP/Elastic IP address when communicating with the instance from outside the VPC.Option B is incorrect since this should be used to communicate instances in the private subnet to the Internet.
For more information on public subnets and the VPC, please visit the below URL-
https://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_Scenario1.html