A Network Engineer is troubleshooting a network connectivity issue for an instance within a public subnet that cannot connect to the internet. The first step the Engineer takes is to SSH to the instance via a local bastion within the VPC and runs an ifconfig command to inspect the IP addresses configured on the instance. The output is as follows:

[ec2-user@ip-172-31-8-24 ~]$ ifconfig etho
etho Link encap:Ethernet HWaddr 0A:A9:4A:21:41:BE
inet addr:172.31.8.24 Bcast:172.31.15.255 Mask:255.255.240.0
inet6 addr: fe80::8a9:4aff:fe21:41lbe/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:9001 Metric:1
RX packets:557703 errors:0 dropped:0 overruns:0 frame:0
TX packets:542300 errors:0 dropped:0 overrun: carrier:0
collisions:0 txqueuelen:1000
RX bytes:59639585 (56.8 MiB) TX bytes:101633146 (96.9 MiB)

The Engineer notices that the command output does not contain a public IP address. In the AWS Management Console, the public subnet has a route to the internet gateway. The instance also has a public IP address associated with it.
What should the Engineer do next to troubleshoot this situation?

A. Configure the public IP on the interface.
B. Disable source/destination checking for the instance.
C. Associate an Elastic IP address to the interface.
D. Evaluate the security groups and the network access control list.