Courseiva
mediumMultiple SelectObjective-mapped

CS0-003 Practice Question: During a security incident, a digital forensics…

During a security incident, a digital forensics investigator must preserve evidence according to best practices. Which three of the following actions align with proper forensic procedures? (Choose three.)

⚠ Common exam trap

CompTIA often tests the misconception that booting a system to check processes is acceptable, but in forensic procedures, any live interaction with the original evidence is prohibited to avoid altering the state.

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

Calculate and document cryptographic hashes of acquired images.

Calculating and documenting cryptographic hashes (e.g., SHA-256) of acquired images ensures data integrity by providing a verifiable fingerprint that can prove the image has not been altered since acquisition. Maintaining a documented chain of custody tracks every person who handled the evidence, preserving its admissibility in legal proceedings. Using a write blocker when creating disk images prevents any accidental writes to the original media, which is critical to avoid altering the evidence.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • Calculate and document cryptographic hashes of acquired images.

    Why this is correct

    Calculating a cryptographic hash (e.g., SHA-256) of an acquired disk image immediately after creation generates a unique digital fingerprint that can later be re-computed to verify the image has not been modified or corrupted. This integrity verification is a fundamental forensic requirement and must be documented in the case notes, along with the exact hash value, so that courts can substantiate that the evidence is authentic and unaltered since acquisition. Without this step, any subsequent analysis could be called into question, and the entire evidentiary foundation would be vulnerable to challenges.

  • Boot the suspect system to check for running processes.

    Why it's wrong here

    Booting the suspect system, particularly in normal mode, initiates the operating system and writes data to the disk—changing file access times, creating temporary files, and potentially altering user data or logs. This violates the core forensic principle of preserving evidence in its original state, as any modification can destroy or contaminate proof. Even if the system is booted from a live CD, the system's devices may still generate write activity, and performing a live boot is only justified in specific, carefully controlled scenarios where volatile data must be captured before powering down. In a routine forensic acquisition, the correct procedure is to keep the system powered off and use static imaging techniques.

  • Maintain a documented chain of custody for all evidence.

    Why this is correct

    Maintaining a documented chain of custody is essential because it provides a chronological, auditable record of every person who handled the evidence, the times and dates of transfers, and the conditions under which it was stored. This documentation demonstrates that the evidence has not been tampered with, lost, or substituted, which is a prerequisite for admissibility in legal proceedings. Even with perfect acquisition techniques, a gap or inconsistency in the chain of custody can render the evidence worthless in court. Therefore, the investigator must meticulously log every action—from collection, through storage, to analysis—and ensure that any transfer is signed for and witnessed to maintain the integrity of the case.

  • Use a write blocker when creating disk images.

    Why this is correct

    A write blocker is a specialized hardware or software device that intercepts and blocks write commands from being sent to a suspect drive during the imaging process. By allowing only read operations, it guarantees that the original evidence disk remains absolutely untouched, preserving its exact state, metadata, timestamps, and all data. Without a write blocker, the mere act of connecting the drive to a forensic workstation could cause the operating system to alter the drive—for instance, by updating access times, creating system restore points, or writing journal data—thereby compromising the evidence's integrity. Hardware write blockers are preferred in high-stakes investigations because they act at the physical layer and are not reliant on the host operating system's software, whereas software write blockers can be bypassed by malicious code.

  • Store original evidence on the same network as the investigation.

    Why it's wrong here

    Storing original evidence on the same network as the investigation introduces a severe risk of corruption, accidental modification, or unauthorized access. For example, if the network is compromised by malware, the evidence files or the forensic images could be infected or altered, breaking their integrity and making them inadmissible in court. Additionally, network storage may have automated backup or indexing processes that modify file timestamps, and it can be accessible to other users, which creates a chain-of-custody violation. Original evidence should be stored on write-protected media in a physically secured, isolated evidence locker, ensuring that it is never exposed to a network environment that could change or contaminate it.

  • Reinstall the operating system before imaging to ensure stability.

    Why it's wrong here

    Reinstalling the operating system before imaging would completely obliterate the original evidence—the process overwrites the disk's contents, destroys user files, deletes logs, and replaces system artifacts—thereby defeating the entire purpose of forensic preservation. The goal of digital forensics is to recover and analyze the evidence exactly as it existed at the time of the incident, not to create a clean or stable environment for the investigator. An unstable system does not justify such a destructive action; if a system is unstable, the investigator should still follow proper procedures for imaging the original media, even if it requires additional care or specialized tools. Reinstalling the OS would be tantamount to destroying evidence and could lead to criminal charges for obstruction of justice or evidence tampering.

About these practice questions

This CS0-004 question is part of Courseiva's 236-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 →

How Courseiva writes practice questions · Editorial policy

JA

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

This CS0-004 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 CS0-004 exam.