You are trying to diagnose a connection issue with a Linux instance. The instance is assigned a public IP and is in the public subnet. You can also see that the Internet gateway is attached, and the route tables are in place. You SSH into the instance from a bastion host. You then do an ifconfig and see that the interface does not display the public IP address. What should be done next to check the issue?

Answer options:

A.Assign the public IP to the Interface.
B.Assign an Elastic IP to the interface.
C.Check the metadata for the instance.
D.Assign a private IP to the interface.

Answer – C
The public IPv4 address is displayed as a property of the network interface in the console. But it`s mapped to the primary private IPv4 address. Therefore, if you inspect the properties of your network interface on your instance, for example, through ifconfig (Linux) or ipconfig (Windows), the public IPv4 address is not displayed. To determine your instance`s public IPv4 address from within the instance, you can use instance metadata.
In such a scenario, all other options become invalid.
For more information on using Instance addressing, please refer to the "Note" section on page 715 on below URL
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-ug.pdf