- A
Process hollowing
Why wrong: Process hollowing replaces the legitimate process's code, not injection.
- B
Reflective DLL injection
Why wrong: Reflective DLL injection is a variant but not the most common; DLL injection is broader.
- C
Token stealing
Why wrong: Token stealing is used for privilege escalation, not code injection.
- D
DLL injection
DLL injection loads a malicious DLL into a target process.
Quick Answer
The answer is DLL injection, as this technique directly enables a process to load a malicious DLL into the address space of a legitimate system process like svchost.exe. This is accomplished using Windows API calls such as CreateRemoteThread and LoadLibrary, which force the target process to execute the injected code within its trusted context, thereby blending malicious activity with normal system operations and evading standard detection. On the Systems Security Certified Practitioner SSCP exam, this scenario tests your understanding of process injection methods and their role in privilege escalation or persistence, often appearing in incident response questions where memory forensics reveals abnormal code execution within critical Windows services. A common trap is confusing DLL injection with process hollowing or APC injection, but remember that DLL injection specifically relies on loading a library into an existing process’s memory space. Memory tip: think “DLL = Dynamic Link Library, injected into a trusted host to hide in plain sight.”
SSCP Incident Response and Recovery Practice Question
This SSCP practice question tests your understanding of incident response and recovery. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
During a security incident, the IR team collects memory dumps from an infected workstation. The analysis reveals a process injecting code into 'svchost.exe'. Which technique is most likely being used?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue:
"most likely"Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
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
DLL injection
DLL injection is the most likely technique because it involves a process loading a malicious DLL into the address space of a legitimate process like svchost.exe. This is typically achieved using Windows API calls such as CreateRemoteThread and LoadLibrary, allowing the attacker to execute code within the trusted svchost.exe context, evading detection by blending in with legitimate system processes.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Process hollowing
Why it's wrong here
Process hollowing replaces the legitimate process's code, not injection.
- ✗
Reflective DLL injection
Why it's wrong here
Reflective DLL injection is a variant but not the most common; DLL injection is broader.
- ✗
Token stealing
Why it's wrong here
Token stealing is used for privilege escalation, not code injection.
- ✓
DLL injection
Why this is correct
DLL injection loads a malicious DLL into a target process.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse DLL injection with process hollowing, but process hollowing replaces the process's code entirely, whereas the question describes injecting code into an already running svchost.exe, which aligns with DLL injection.
Detailed technical explanation
How to think about this question
DLL injection via CreateRemoteThread and LoadLibrary works by allocating memory in the target process (VirtualAllocEx), writing the DLL path (WriteProcessMemory), and then creating a remote thread that calls LoadLibrary, which loads the DLL from disk. In contrast, reflective DLL injection loads the DLL entirely from memory, avoiding disk writes and standard API hooks, but it requires more complex implementation and is less common in basic attacks. Real-world malware like Emotet has used DLL injection into svchost.exe to maintain persistence and evade detection by security tools that monitor for anomalous process creation.
KKey Concepts to Remember
- Read the scenario before looking for a memorised answer.
- Find the constraint that changes the correct option.
- Eliminate answers that are true in general but not in this case.
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A SOC analyst notices unusual lateral movement in the network at 2 AM. The IR playbook dictates: identify and contain (isolate the affected machine), then eradicate (remove the malware), then recover (restore from backup), then document. Skipping containment before eradication risks the attacker regaining access. Questions like this test the sequence and rationale of incident response phases.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Incident Response and Recovery — study guide chapter
Learn the concepts, then practise the questions
- →
Incident Response and Recovery practice questions
Targeted practice on this topic area only
- →
All SSCP questions
504 questions across all exam domains
- →
Systems Security Certified Practitioner SSCP study guide
Full concept coverage aligned to exam objectives
- →
SSCP practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related SSCP practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Risk Identification, Monitoring and Analysis practice questions
Practise SSCP questions linked to Risk Identification, Monitoring and Analysis.
Network and Communications Security practice questions
Practise SSCP questions linked to Network and Communications Security.
Systems and Application Security practice questions
Practise SSCP questions linked to Systems and Application Security.
Security Operations and Administration practice questions
Practise SSCP questions linked to Security Operations and Administration.
Incident Response and Recovery practice questions
Practise SSCP questions linked to Incident Response and Recovery.
Access Controls practice questions
Practise SSCP questions linked to Access Controls.
Cryptography practice questions
Practise SSCP questions linked to Cryptography.
SSCP fundamentals practice questions
Practise SSCP questions linked to SSCP fundamentals.
SSCP scenario practice questions
Practise SSCP questions linked to SSCP scenario.
SSCP troubleshooting practice questions
Practise SSCP questions linked to SSCP troubleshooting.
Practice this exam
Start a free SSCP practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this SSCP question test?
Incident Response and Recovery — This question tests Incident Response and Recovery — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: DLL injection — DLL injection is the most likely technique because it involves a process loading a malicious DLL into the address space of a legitimate process like svchost.exe. This is typically achieved using Windows API calls such as CreateRemoteThread and LoadLibrary, allowing the attacker to execute code within the trusted svchost.exe context, evading detection by blending in with legitimate system processes.
What should I do if I get this SSCP question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Are there clue words in this question I should notice?
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Last reviewed: Jun 11, 2026
This SSCP practice question is part of Courseiva's free ISC2 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 SSCP exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.