You have a Linux EC2 web server instance running inside a VPC The instance is in a public subnet and has an EIP associated
with it so you can connect to It over the Internet via HTTP or SSH The instance was also fully accessible when you last logged in
via SSH. and was also serving web requests on port 80. Now you are not able to SSH into the host nor does it respond to web
requests on port 80 that were working fine last time you checked You have double-checked that all networking configuration
parameters (security groups route tables, IGWEIP. NACLs etc.) are properly configured (and you haven’t made any changes to
those anyway since you were last able to reach the instance). You look at the EC2 console and notice that system status checks
show “impaired”. Which should be your next step in troubleshooting and attempting to get the instance back to a healthy state so
that you can log in again?

A.
Stop and start the instance so that it will be able to be redeployed on a healthy host system that most likely will fix the
“impaired” system status

B.
Reboot your instance so that the operating system will have a chance to boot in a clean healthy state that most likely will fix
the ‘impaired” system status

C.
Add another dynamic private IP address to me instance and try to connect via mat new path, since the networking stack of
the OS may be locked up causing the “impaired” system status

D.
Add another Elastic Network Interface to the instance and try to connect via that new path since the networking stack of the
OS may be locked up causing the “impaired” system status

E.
Un-map and then re-map the EIP to the instance, since the IGWVNAT gateway may not be working properly, causing the
“impaired” system status