SY0-701 Security Operations Practice Question
A laptop is suspected of being used in a malware incident. It is still powered on and connected to Wi-Fi. What should the responder do before shutting it down?
⚠ Common exam trap
The trap here is that candidates mistakenly think immediate containment (e.g., deleting files or rebooting) is the priority, but the SY0-701 exam emphasizes preserving volatile evidence first to support forensic analysis and legal proceedings.
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
✓
Capture volatile evidence such as running processes and memory contents.
Volatile evidence, such as running processes, network connections, and memory contents, is lost when the system is powered off. Capturing this data first preserves critical forensic artifacts that can reveal the malware's behavior, persistence mechanisms, and indicators of compromise (IOCs). In a live incident, the responder must follow the order of volatility (RFC 3227) to collect the most ephemeral data before it disappears.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Install endpoint protection updates on the laptop right away.
Why it's wrong here
Installing endpoint protection updates modifies the live system by writing new files, altering registry keys, and running update processes, all of which can overwrite or destroy volatile evidence that is critical to the investigation. It also requires network activity and may trigger the malware to change its behavior or delete its traces, reducing the chances of recovering an accurate picture of the infection. Furthermore, signature-based updates are unlikely to detect a novel or polymorphic threat and do nothing to preserve the running processes, memory contents, and network connections that are needed for analysis.
- ✓
Capture volatile evidence such as running processes and memory contents.
Why this is correct
This is the best action because volatile data can disappear when the system is powered off or rebooted. Running processes, network connections, logged-on users, and memory contents may contain the strongest clues about active malware and attacker activity. Preserving this information first supports later investigation and helps responders understand what happened before they take more disruptive containment steps.
- ✗
Delete suspicious files so the malware can no longer spread.
Why it's wrong here
Deleting suspicious files removes the primary physical evidence needed for static analysis (e.g., binary reverse engineering, string extraction, hash correlation) and can permanently destroy the only copy of the malware. Your action may also miss persistence mechanisms—such as registry Run keys, scheduled tasks, services, or WMI subscriptions—so the malware could re-infect the host immediately after the deletion. Additionally, in a live system, deleting files alters file system metadata (timestamps, journal entries) and could trigger the malware's anti-forensics routines that erase logs or corrupt other artifacts, making the overall incident analysis less complete and less defensible.
- ✗
Reboot the laptop immediately to clear the suspected malware.
Why it's wrong here
Rebooting the laptop forcibly terminates all running processes and clears volatile memory (RAM), which is often the richest source of evidence about active malware, including injected code, decrypted payloads, and command-and-control communication details. This action also drops live network connections, loses the contents of temporary files and open handles, and may trigger the malware's persistence or cleanup routines to execute during shutdown—all of which can destroy evidence that would otherwise be captured. Rebooting should be postponed until after memory and other volatile data have been collected; otherwise, the investigator permanently loses the most time-sensitive artifacts, making it much harder to determine the scope and impact of the incident.
Go deeper
Related to this question
Learn chapter
Incident Response Process
Key term
Malware
Malware is any software intentionally designed to cause damage, disrupt operations, steal data, or gain unauthorized access to computer systems.
Key term
Incident
An incident is a security event that violates an organization's policies or threatens its data, systems, or operations, requiring a structured response.
About these practice questions
One of 1,013 original SY0-701 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.