SAP-C02 Continuous Improvement for Existing Solutions Practice Question
Network Topology
Refer to the exhibit. A solutions architect runs the AWS CLI command to check the state of an EC2 instance. The output shows the instance is running. However, the application team reports that the instance is unreachable over SSH. What is the MOST likely cause?
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
A security group rule blocks inbound SSH traffic
The instance state is 'running', so it is not stopped or terminated. The most likely cause for being unreachable over SSH is that a security group rule blocks inbound SSH traffic (port 22). Option B is correct. Option A is wrong because the query is for the correct instance. Option C is wrong because the instance is running. Option D is wrong because EBS optimization does not affect network connectivity.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The CLI command is querying the wrong instance
Why it's wrong here
The exhibit shows the queried instance running, so a wrong instance identifier would not explain the SSH failure while that state persists. It is tempting because mistyped instance IDs do cause confusing CLI output, and verifying the identifier would be the correct step when the returned state contradicts expectations.
- ✓
A security group rule blocks inbound SSH traffic
Why this is correct
The instance state and SSH reachability are independent: a running instance with no inbound TCP/22 allowance silently drops connection attempts. A security group rule blocking port 22 explains the unreachable symptom while the instance remains running, unlike host-level or key-pair issues.
- ✗
The instance is in a 'stopped' state
Why it's wrong here
The exhibit already shows the instance in a running state, directly contradicting a stopped state, so this cannot be the cause. It is tempting because a stopped instance genuinely is unreachable over SSH, and that would be the correct diagnosis if the CLI output had reported stopped rather than running.
- ✗
The instance does not have EBS optimization enabled
Why it's wrong here
EBS optimisation affects storage throughput only; it has no bearing on whether SSH traffic reaches the instance. It is tempting because it is a genuine per-instance setting that can be enabled or disabled, and it would be the correct answer if the symptom were degraded disk performance rather than connectivity.
Go deeper
Related to this question
About these practice questions
Courseiva writes every SAP-C02 question from scratch — 984 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This SAP-C02 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SAP-C02 exam.