200-201 Host-Based Analysis Practice Question
A security analyst is examining a Windows 10 endpoint suspected of compromise. The analyst runs `wmic process get name,processid,executablepath,parentprocessid` and observes a process named `lsass.exe` with PID 1234 and executable path `C:\Windows\Temp\lsass.exe`. The legitimate lsass.exe should reside in `C:\Windows\System32`. Which of the following is the MOST likely explanation?
⚠ Common exam trap
The trap here is assuming that a process named lsass.exe is always the legitimate Windows process, without verifying its executable path.
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 malware sample is masquerading as lsass.exe to evade detection by name-based monitoring.
Legitimate Windows system processes run from specific system directories, such as System32. When a process named lsass.exe is found in a non-standard location like C:\Windows\Temp, it is almost certainly malware attempting to hide by using a trusted process name. The analyst should treat this as a compromise, isolate the host, and perform further forensics including file hash analysis and persistence checks.
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 output is a false positive because wmic sometimes reports incorrect executable paths for system processes.
Why it's wrong here
WMI accurately reports the executable path from the process's image path. While there can be edge cases with permissions, it does not arbitrarily report incorrect paths for system processes. Assuming a false positive without further verification is dangerous and could allow a compromise to go unchecked.
- ✓
A malware sample is masquerading as lsass.exe to evade detection by name-based monitoring.
Why this is correct
Attackers commonly name malicious executables after legitimate system processes like lsass.exe to blend in. Placing the binary in a non-standard location such as C:\Windows\Temp is a strong indicator of compromise. The analyst should immediately collect the file, hash it, and investigate its origin and behavior, as this is a classic masquerading technique.
- ✗
The system is experiencing a file system corruption that moved lsass.exe to a temporary folder.
Why it's wrong here
File system corruption typically causes errors or system instability, not the relocation of a critical system process to a Temp folder. Windows would fail to boot or log errors if lsass.exe were missing from System32. This scenario is highly unlikely and not the primary concern when a security analyst sees a process with a suspicious path.
- ✗
The process is a legitimate instance of lsass.exe that was moved by a Windows Update.
Why it's wrong here
Windows Update never relocates core system binaries like lsass.exe from System32 to Temp. Such a move would break authentication and security policies. Legitimate lsass.exe always runs from System32. Seeing it in Temp indicates malicious activity, not a benign update process.
Go deeper
Related to this question
About these practice questions
This 200-201 question is part of Courseiva's 968-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam 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.