Bird
0
0

You launched an EC2 instance but cannot connect via SSH using your key pair. Which of the following is NOT a likely cause?

medium📝 Debug Q7 of 15
AWS - EC2 Fundamentals
You launched an EC2 instance but cannot connect via SSH using your key pair. Which of the following is NOT a likely cause?
AThe security group does not allow inbound SSH (port 22) traffic
BThe instance is in a private subnet without internet access
CThe instance type does not support SSH connections
DThe key pair was deleted after instance launch
Step-by-Step Solution
Solution:

  1. Step 1: Evaluate common SSH connection issues

    Security group rules, subnet configuration, and key pair availability affect SSH access.

  2. Step 2: Identify incorrect statement

    Instance type does not restrict SSH; all support it if configured properly.

  3. Final Answer:

    The instance type does not support SSH connections -> Option C

  4. Quick Check:

    Instance type does not block SSH [OK]
Quick Trick: SSH issues usually relate to security groups or network, not instance type [OK]
Common Mistakes:
MISTAKES
  • Blaming instance type for SSH connection failures
  • Ignoring security group inbound rules
  • Not checking subnet internet access

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More AWS Quizzes
AWS Account and Billing - AWS Cost Explorer basics - Quiz 2easy AWS Account and Billing - Root user vs IAM user - Quiz 5medium AWS CLI - Basic CLI commands (s3, ec2) - Quiz 10hard AWS CLI - Configuring credentials - Quiz 12easy AWS CLI - Why CLI matters for automation - Quiz 3easy Cloud Computing Fundamentals - AWS Management Console walkthrough - Quiz 1easy EC2 Fundamentals - Connecting to EC2 instances - Quiz 8hard S3 Fundamentals - S3 storage classes (Standard, IA, Glacier) - Quiz 12easy Security Groups and Network ACLs - Inbound and outbound rules - Quiz 14medium Security Groups and Network ACLs - Network ACLs overview - Quiz 14medium