easyMultiple Choice
200-201 Practice Question: An analyst notices repeated failed SSH attempts…
An analyst notices repeated failed SSH attempts from an external IP to a server. The analyst wants to quickly see all SSH-related events from that IP in the last hour. Which approach is most efficient?
⚠ Common exam trap
Cisco often tests the distinction between centralized log analysis (SIEM) and raw data inspection (packet capture or manual log review), trapping candidates who overlook the efficiency of indexed search versus unfiltered data retrieval.
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
✓
Search the SIEM for events with destination port 22 and source IP.
A SIEM indexes and correlates log data from multiple sources, allowing an analyst to quickly filter events by destination port 22 (SSH) and source IP without manually sifting through raw logs. This approach leverages the SIEM's search capabilities to retrieve only relevant events from the past hour, making it the most efficient method for targeted threat hunting.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Search the SIEM for events with destination port 22 and source IP.
Why this is correct
Filtering the SIEM by destination port 22 and the source IP returns exactly the SSH-related events from that address within the last hour. This is the most efficient approach, avoiding manual log review across multiple servers.
- ✗
Review all firewall logs for the past hour.
Why it's wrong here
Firewall logs record connection metadata such as source IP, port and action, not SSH authentication events, so failed logins would not appear. It is tempting because firewall logs are centralised and quick to query, but they would be the right source for identifying blocked connections rather than authentication activity.
- ✗
Run a packet capture on the server's network interface.
Why it's wrong here
A packet capture only observes traffic from the moment it starts, so it cannot show events from the previous hour, and it captures encrypted SSH payloads that reveal no authentication detail. It is tempting because captures give raw traffic visibility, but they suit live troubleshooting rather than retrospective log review.
- ✗
Check the server's auth.log file manually.
Why it's wrong here
Reading auth.log manually on one host is slow, unscalable and offers no correlation with the external IP across other systems. It is tempting because auth.log does record SSH authentication failures, but a centralised SIEM query would be the correct approach for rapidly filtering events by source IP and time window.
Go deeper
Related to this question
About these practice questions
One of 968 original 200-201 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This 200-201 practice question is part of Courseiva's free Cisco 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 200-201 exam.