200-201 Host-Based Analysis Practice Question
An analyst is using Volatility to analyze a memory dump. Which TWO plugins are most effective for detecting code injection?
⚠ Common exam trap
200-201 often tests the specific Volatility plugins for different forensic tasks; candidates may confuse pslist/pstree (process listing) with malfind/ldrmodules (injection detection).
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
✓
ldrmodules
Option A, ldrmodules, is correct because it compares the three DLL/module lists maintained in the PEB (InLoad, InInit, InMem) and flags modules that appear in memory but are absent from the loader list, a classic sign of injected or unlinked DLLs. Option C, malfind, is correct because it scans process memory for pages with MZ/PE headers that are not backed by a file on disk and have suspicious protection flags such as PAGE_EXECUTE_READWRITE, which is the standard indicator of injected code. The unmarked options do not belong: pslist merely walks the doubly linked process list to enumerate running processes, pstree shows parent-child process relationships, and netscan lists network connections and sockets; none of these inspect module lists or memory pages for injected code.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
ldrmodules
Why this is correct
ldrmodules enumerates loaded modules via three linked lists (InLoad, InInit, InMem) and flags discrepancies, exposing injected DLLs unlinked from the loader's lists. This directly satisfies the scenario's requirement to detect code injection in the memory dump.
- ✗
pslist
Why it's wrong here
pslist walks the active process list via pool tagging, so injected code running outside a registered process, such as in an unlinked or hollowed region, is invisible to it. It is the right starting point for enumerating live processes before pivoting to memory-scanning plugins.
- ✓
malfind
Why this is correct
Malfind scans process memory for injected code by locating pages marked executable and writable that lack a mapped file backing, then dumping suspicious regions for inspection. This directly satisfies the stem's requirement to detect code injection within the memory dump, exposing hidden payloads that legitimate modules would not contain.
- ✗
pstree
Why it's wrong here
pstree renders parent-child relationships from the same process list pslist uses, so it inherits the identical blind spot for injected code in unbacked memory. It suits visualising process hierarchy during triage, not detecting code injection.
- ✗
netscan
Why it's wrong here
netscan enumerates network connections and listening sockets from pool tags, so injected code in unlinked memory regions leaves no socket to list. It is tempting because netscan genuinely suits live-connection triage, such as identifying beaconing processes during incident response.
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.