(An administrator successfully accesses an EC2 instance via SSH from a local computer then stops it and starts it. Following the restart, the EC2 instance is no longer accessible. Which solution should be used to resolve the issue?)
A.
Add a rule to the security group associated with the NIC of the EC2 instance
B.
Change the port used to connect to EC2 instance
C.
Add a route to the route table associated with the EC2 instance subnet
D.
Change the IP address used to connect to the EC2 instance
Comprehensive and Detailed Explanation From Exact Extract:
After stopping and starting an EC2 instance, the public IP address may change (unless an Elastic IP is attached), but the security group rules remain intact. If the instance is no longer accessible via SSH, it’s likely due to an inbound rule (e.g., for port 22) not being correctly configured or applied. Adding or verifying a rule in the security group associated with the network interface (NIC) to allow SSH (port 22) from the administrator’s IP resolves this. The WGU Cloud Deployment and Operations Study Guide (Section 3.2, Security Groups) states, "Stopping and starting an EC2 instance may require verifying or adding an inbound SSH rule (port 22) in the security group if connectivity is lost due to IP or rule misconfiguration." Route table or IP changes are not the primary issue here.
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit