200-201 Host-Based Analysis Practice Question
An analyst suspects a Windows workstation is beaconing to a command-and-control server. The host's DNS cache contains an entry for a domain that resolves to an IP address, but the analyst cannot find any active network connection or process associated with that domain. Which Windows artifact should the analyst examine to determine whether a process previously resolved this domain and when?
⚠ Common exam trap
The trap here is assuming that the DNS cache or firewall log provides process attribution and timestamps for domain resolution, when only the DNS Client operational log records that level of detail.
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
✓
The DNS Client event log (Microsoft-Windows-DNS-Client/Operational)
The Microsoft-Windows-DNS-Client/Operational log is designed to record DNS client query events, including the query name, query type, timestamp, and the process that initiated the query. When a host is beaconing, the DNS cache may only show the resolved IP, but the operational log can show which process resolved the domain and when, enabling the analyst to link the beaconing behavior to a specific executable.
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 Windows Firewall log at %systemroot%\system32\LogFiles\Firewall\pfirewall.log
Why it's wrong here
The Windows Firewall log records allowed and blocked connection attempts with source and destination IP addresses and ports, but it does not log DNS query names or the process that performed the resolution. It would show IP-based connections, not the domain-to-process mapping needed here. Thus it cannot identify which process resolved the domain or when.
- ✓
The DNS Client event log (Microsoft-Windows-DNS-Client/Operational)
Why this is correct
The Microsoft-Windows-DNS-Client/Operational log records DNS query events, including the process name, query name, query type, and timestamp. In this scenario, it can reveal which process resolved the suspicious domain and when, even if the connection is no longer active. This directly addresses the need to correlate a domain with a process and time.
- ✗
The Application event log
Why it's wrong here
The Application event log stores events generated by applications, such as application crashes or custom application logging. It does not capture DNS client queries or the process responsible for resolving a domain. Consequently, it cannot help correlate the suspicious domain with a process or a specific time.
- ✗
The System event log
Why it's wrong here
The System event log contains events from Windows components and drivers, such as service start failures and hardware errors. It does not record DNS client query activity or process-level domain resolution. Therefore, it would not show which process resolved the suspicious domain or provide the timestamp of the query.
Visual reference
Go deeper
Related to this question
About these practice questions
Courseiva writes every 200-201 question from scratch — 968 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 and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Cisco exam blueprint
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.