- A
PowerShell was launched with encoded, hidden execution arguments from a document process.
Encoded and hidden PowerShell launched from a document process is a strong fileless malware indicator. The attack uses built-in scripting rather than dropping a traditional executable, which helps evade file-based detections. In combination with a user-facing process like Word, this pattern commonly suggests initial execution through malicious content or macro abuse.
- B
A WMI permanent event subscription was created under the root\subscription namespace.
A WMI permanent event subscription is a well-known persistence technique because it can survive reboots without requiring a visible startup entry or common scheduled task. Attackers often use WMI to keep a foothold while remaining difficult to notice in routine file-system checks. It strongly supports a stealthy, script-based compromise.
- C
A new executable named updater.exe was copied into Program Files by an administrator.
Why wrong: A new executable in Program Files could be legitimate software maintenance, especially if installed by an administrator through a normal process. Without additional suspicious behavior such as odd parent processes, malicious signatures, or unusual network traffic, this is not strong evidence of a fileless compromise.
- D
The browser cache was cleared after a routine user sign-out.
Why wrong: Browser cache clearing is a common user or system action and does not indicate malware on its own. It has no direct relationship to fileless execution or persistence. This detail is operationally ordinary and would not be prioritized as a compromise indicator during endpoint triage.
- E
A signed video driver updated successfully through Windows Update.
Why wrong: A signed driver update through Windows Update is typically legitimate maintenance and usually lowers risk rather than increasing it. Although drivers can be abused in some attacks, this scenario lacks the hallmarks of malicious persistence, script staging, or fileless execution that the other correct choices provide.
Quick Answer
The answer is the WMI permanent event subscription under root\subscription, paired with the encoded PowerShell launch from winword.exe. This is correct because fileless malware persistence via WMI uses permanent event subscriptions to trigger malicious scripts without writing a traditional executable to disk; the encoded PowerShell command runs entirely in memory, while the WMI subscription ensures re-execution on system events like startup or logon. On the Security+ SY0-701 exam, this scenario tests your ability to distinguish fileless techniques from file-based malware—a common trap is assuming persistence always requires a new .exe file, when WMI subscriptions and registry run keys can achieve it without one. Remember the mnemonic “No File, No Fear”: if no executable appears in Downloads or Program Files, look for WMI subscriptions or PowerShell memory execution as the persistence mechanism.
SY0-701 Threats, Vulnerabilities, and Mitigations Practice Question
This SY0-701 practice question tests your understanding of threats, vulnerabilities, and mitigations. 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.
An endpoint investigation shows winword.exe launching powershell.exe with -nop -w hidden -enc arguments. The same host also has a newly created WMI permanent event subscription, and no new executable has appeared in Downloads or Program Files. Which two findings are most consistent with a fileless compromise and persistence mechanism? Select two.
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
PowerShell was launched with encoded, hidden execution arguments from a document process.
Option A is correct because the use of winword.exe to launch powershell.exe with `-nop -w hidden -enc` arguments is a classic fileless execution technique. The encoded command runs entirely in memory without writing a payload to disk, and the launch from a document process (winword.exe) indicates a macro or exploit-based initial access, consistent with a fileless compromise.
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.
- ✓
PowerShell was launched with encoded, hidden execution arguments from a document process.
Why this is correct
Encoded and hidden PowerShell launched from a document process is a strong fileless malware indicator. The attack uses built-in scripting rather than dropping a traditional executable, which helps evade file-based detections. In combination with a user-facing process like Word, this pattern commonly suggests initial execution through malicious content or macro abuse.
Related concept
Read the scenario before looking for a memorised answer.
- ✓
A WMI permanent event subscription was created under the root\subscription namespace.
Why this is correct
A WMI permanent event subscription is a well-known persistence technique because it can survive reboots without requiring a visible startup entry or common scheduled task. Attackers often use WMI to keep a foothold while remaining difficult to notice in routine file-system checks. It strongly supports a stealthy, script-based compromise.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
A new executable named updater.exe was copied into Program Files by an administrator.
Why it's wrong here
A new executable in Program Files could be legitimate software maintenance, especially if installed by an administrator through a normal process. Without additional suspicious behavior such as odd parent processes, malicious signatures, or unusual network traffic, this is not strong evidence of a fileless compromise.
- ✗
The browser cache was cleared after a routine user sign-out.
Why it's wrong here
Browser cache clearing is a common user or system action and does not indicate malware on its own. It has no direct relationship to fileless execution or persistence. This detail is operationally ordinary and would not be prioritized as a compromise indicator during endpoint triage.
- ✗
A signed video driver updated successfully through Windows Update.
Why it's wrong here
A signed driver update through Windows Update is typically legitimate maintenance and usually lowers risk rather than increasing it. Although drivers can be abused in some attacks, this scenario lacks the hallmarks of malicious persistence, script staging, or fileless execution that the other correct choices provide.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may think any persistence mechanism (like a new executable in Program Files) is fileless, but fileless specifically means no executable written to disk, and WMI subscriptions are a common fileless persistence vector.
Trap categories for this question
Scenario analysis trap
A signed driver update through Windows Update is typically legitimate maintenance and usually lowers risk rather than increasing it. Although drivers can be abused in some attacks, this scenario lacks the hallmarks of malicious persistence, script staging, or fileless execution that the other correct choices provide.
Detailed technical explanation
How to think about this question
Fileless malware leverages living-off-the-land binaries (LOLBins) like PowerShell to execute malicious code in memory, often using encoded commands to evade signature-based detection. WMI permanent event subscriptions can trigger arbitrary scripts or executables in response to system events (e.g., startup, logon), providing stealthy persistence without writing a traditional executable to disk. The combination of in-memory execution and WMI-based persistence is a hallmark of advanced fileless attacks.
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 security team runs a vulnerability scan on a web application and discovers an unpatched SQL injection flaw. The team prioritises remediation by CVSS score — critical flaws are patched within 24 hours, high within 7 days. Questions like this test whether you understand vulnerability management processes, scanning tools, and remediation prioritisation.
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.
- →
Threats, Vulnerabilities, and Mitigations — study guide chapter
Learn the concepts, then practise the questions
- →
Threats, Vulnerabilities, and Mitigations practice questions
Targeted practice on this topic area only
- →
All SY0-701 questions
1,152 questions across all exam domains
- →
Security+ SY0-701 study guide
Full concept coverage aligned to exam objectives
- →
SY0-701 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related SY0-701 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
General Security Concepts practice questions
Practise SY0-701 questions linked to General Security Concepts.
Threats, Vulnerabilities, and Mitigations practice questions
Practise SY0-701 questions linked to Threats, Vulnerabilities, and Mitigations.
Security Architecture practice questions
Practise SY0-701 questions linked to Security Architecture.
Security Operations practice questions
Practise SY0-701 questions linked to Security Operations.
Security Program Management and Oversight practice questions
Practise SY0-701 questions linked to Security Program Management and Oversight.
Security+ social engineering questions
Practise SY0-701 questions linked to Security+ social engineering questions.
Security+ cryptography practice questions
Practise SY0-701 questions linked to Security+ cryptography.
Security+ IAM questions
Practise SY0-701 questions linked to Security+ IAM questions.
Security+ risk management questions
Practise SY0-701 questions linked to Security+ risk management questions.
Security+ incident response questions
Practise SY0-701 questions linked to Security+ incident response questions.
Security+ malware questions
Practise SY0-701 questions linked to Security+ malware questions.
Security+ vulnerability management questions
Practise SY0-701 questions linked to Security+ vulnerability management questions.
Practice this exam
Start a free SY0-701 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 SY0-701 question test?
Threats, Vulnerabilities, and Mitigations — This question tests Threats, Vulnerabilities, and Mitigations — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: PowerShell was launched with encoded, hidden execution arguments from a document process. — Option A is correct because the use of winword.exe to launch powershell.exe with `-nop -w hidden -enc` arguments is a classic fileless execution technique. The encoded command runs entirely in memory without writing a payload to disk, and the launch from a document process (winword.exe) indicates a macro or exploit-based initial access, consistent with a fileless compromise.
What should I do if I get this SY0-701 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
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 SY0-701 practice question is part of Courseiva's free CompTIA 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 SY0-701 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.