SY0-701 Security Operations Practice Question
A file server in the accounting department begins renaming documents and dropping ransom notes. The SOC confirms encryption is still in progress, and the server hosts a share used by several finance teams. What should the incident response team do first?
⚠ Common exam trap
The trap here is that candidates may prioritize data recovery (Option B) or user notification (Option D) over containment, failing to recognize that the immediate priority is stopping active encryption to limit damage.
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
✓
Disconnect the server from the network to contain the spread.
Disconnecting the server from the network is the immediate containment step to prevent the ransomware from encrypting additional files on the share or spreading laterally to other systems. Since encryption is still in progress, isolating the server stops the attacker's process from accessing more files and blocks any command-and-control (C2) communication. This aligns with the NIST incident response framework's containment phase, prioritizing stopping the spread over recovery or notification.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Disconnect the server from the network to contain the spread.
Why this is correct
Immediately disconnecting the server from the network (unplugging the NIC, disabling the switch port, or isolating the VLAN) contains the active ransomware by stopping it from encrypting additional network shares, communicating with its command-and-control server, or moving laterally to other hosts. This network cutover is the first-priority containment action after active encryption is confirmed because it minimizes blast radius while preserving the machine's volatile memory and running processes for forensic triage. Unlike a hard shutdown, it keeps the host in a state where investigators can later image the disk and extract indicators of compromise.
- ✗
Restore the file share from backup immediately while the server is still connected.
Why it's wrong here
Restoring the file share from backup while the server is still connected is counterproductive because the active encryptor is still running in memory and on disk, so it will likely re-encrypt the restored files almost immediately, or the restore job itself could be corrupted by the malware. This action also overwrites critical forensic evidence, such as NTFS timestamps, USN journal entries, and log files, making incident analysis and attribution nearly impossible. Restoring before containment can even spread encrypted or malicious files back into the backup infrastructure if the restore is pointed at the wrong share, so proper IR order requires isolating the host and capturing evidence before any recovery step.
- ✗
Power off the server immediately without any other action.
Why it's wrong here
A hard power-off (pulling the plug or forcing shutdown) without first isolating the host destroys volatile forensic evidence, including memory-resident encryption keys, open network connections, and the ransomware process itself, which can hamper attribution and decryption efforts. Some ransomware variants use anti-forensic tricks to wipe data or corrupt the volume on an unclean shutdown, and a power-off does not actively contain the spread because other hosts may still be communicating with the same C2 server or holding encrypted files in memory. Controlled network isolation is less disruptive than a hard shutdown, preserves more forensic value, and should always precede authoritative shutdown decisions in an incident response.
- ✗
Notify users to change their passwords before any technical action is taken.
Why it's wrong here
Asking users to change passwords before taking any technical action delays containment while the ransomware continues encrypting files and potentially exfiltrating sensitive data to an external server. Password resets do not stop an active encryption process that is already running with system or user privileges, and the malware may have already harvested credentials or created persistence mechanisms that would survive the password change. Credential rotation belongs in the eradication phase—after the host is isolated and the attacker's access has been severed—because performing it first wastes time and may even lock out legitimate recovery staff without protecting any assets.
Go deeper
Related to this question
Learn chapter
Incident Response Process
Key term
Encryption
Encryption is the process of converting readable data into a secret code to prevent unauthorized access.
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
This SY0-701 question is part of Courseiva's 1,013-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 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.