Bird
0
0

You try to connect to your EC2 instance but get a timeout error. Which of the following is the MOST likely cause?

medium📝 Debug Q14 of 15
AWS - EC2 Fundamentals
You try to connect to your EC2 instance but get a timeout error. Which of the following is the MOST likely cause?
AYour private key file is missing
BThe instance is running Windows OS
CYou used the wrong username for the instance
DYour security group does not allow inbound SSH (port 22) traffic
Step-by-Step Solution
Solution:

  1. Step 1: Analyze timeout error causes

    Timeout usually means network traffic is blocked or unreachable, not authentication issues.

  2. Step 2: Check security group rules

    If inbound SSH (port 22) is not allowed, connection attempts will time out.

  3. Final Answer:

    Your security group does not allow inbound SSH (port 22) traffic -> Option D

  4. Quick Check:

    Timeout = blocked port 22 in security group [OK]
Quick Trick: Check security group allows port 22 inbound [OK]
Common Mistakes:
  • Confusing timeout with wrong username errors
  • Assuming missing key causes timeout instead of auth failure
  • Thinking OS type causes timeout

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More AWS Quizzes
AWS CLI - CLI output formats (json, table, text) - Quiz 12easy Cloud Computing Fundamentals - Cloud deployment models (public, private, hybrid) - Quiz 2easy EC2 Fundamentals - EC2 pricing models (on-demand, reserved, spot) - Quiz 5medium Identity and Access Management - Why IAM is foundational - Quiz 5medium Identity and Access Management - IAM policies (JSON structure) - Quiz 1easy Identity and Access Management - Policy evaluation logic - Quiz 12easy S3 Fundamentals - S3 storage classes (Standard, IA, Glacier) - Quiz 8hard S3 Fundamentals - Bucket policies for access control - Quiz 3easy VPC Fundamentals - Route tables configuration - Quiz 3easy VPC Fundamentals - Why VPC provides network isolation - Quiz 3easy