Option D is the best answer because the system has already been shut down , meaning volatile evidence is likely lost and the remaining priority is to preserve and acquire non-volatile data in the most forensically sound manner possible. CHFI v11 emphasizes data acquisition methodology , choosing the best acquisition method , preserving evidence integrity, and using controlled procedures to avoid altering the source media. In this situation, removing the hard drive and attaching it to a forensic workstation is the safest and most standard approach for acquiring a reliable disk image.
Booting the suspect computer, whether with a forensic boot disk or the normal operating system, introduces risk because any boot process can change file system metadata, logs, temporary files, or other artifacts. Using the normal OS is especially unsafe. Network-based acquisition is also not appropriate here because the machine is already isolated and powered down.
A direct forensic acquisition from the removed drive minimizes unnecessary changes to the evidence source and aligns with CHFI principles of preservation, controlled handling, and repeatable imaging . Therefore, the correct next step for non-volatile data acquisition is to remove the drive and image it from a forensic workstation.

This question aligns with CHFI v11 objectives under Network and Web Attacks and Network Log Analysis . In digital forensics, network infrastructure logs are critical sources of evidence for detecting, analyzing, and reconstructing network-based attacks. CHFI v11 specifically emphasizes the forensic value of logs generated by network devices such as Cisco switches, VPN gateways, and DNS servers .
Cisco switch logs provide information about device connections, port activity, MAC address mappings, VLAN assignments, and potential unauthorized access within the internal network. VPN logs reveal details about remote connections, including authentication attempts, user identities, IP addresses, session durations, and encrypted tunnel activity-crucial for identifying compromised credentials or unauthorized remote access. DNS server logs record domain name queries and responses, which help investigators detect command-and-control communication, data exfiltration attempts, malware beaconing, and access to malicious domains.
Together, these logs allow investigators to correlate events across the network, trace attacker movement, identify affected systems, and establish timelines of security incidents. The other options are incorrect because browser history is host-based evidence, and these logs are highly relevant to forensic investigations.
Therefore, consistent with CHFI v11 network forensics principles, these logs provide insights into network traffic, device connections, and security incidents.

Under the CHFI v11 objectives related to Cloud Forensics and AWS Forensics , log preservation is a critical requirement for effective investigation and legal admissibility. In Amazon Web Services, CloudWatch Logs retention policies allow investigators to control how long log data is stored before it is automatically deleted.
Modifying retention policies for individual log groups ensures that relevant forensic artifacts-such as authentication logs, API activity records, and system events-remain available for analysis throughout the investigation lifecycle.
In this scenario, the investigator's goal is not to analyze or query logs immediately, but to extend or manage the lifespan of log data so that it is not lost due to default retention limits. This aligns precisely with the feature that allows investigators to modify retention policies for individual log groups . CHFI v11 highlights the importance of preserving cloud-based evidence early, as cloud logs may be ephemeral and subject to automatic deletion if not properly configured.
Option A refers to general monitoring capabilities, while Option B focuses on querying and searching log data using Logs Insights-both are analytical functions, not retention management. Option D involves alerting mechanisms and does not control log storage duration.
The CHFI Exam Blueprint v4 explicitly includes logs in AWS and cloud evidence acquisition , emphasizing retention configuration as a key forensic readiness and investigation task, making Option C the correct and exam-aligned answer

According to the CHFI v11 objectives and the Electronic Discovery Reference Model (EDRM) framework, the activity described in this scenario corresponds to the Information Governance stage. Information governance is the foundational phase of the EDRM cycle and focuses on establishing policies, procedures, controls, and standards to manage electronic information throughout its lifecycle. This includes defining data retention schedules, access control policies, compliance requirements, preservation rules, and audit readiness.
In CHFI v11, information governance is emphasized as a proactive and strategic function that ensures an organization is prepared for future investigations, audits, litigation, or regulatory inquiries. By implementing governance controls after an investigation, organizations strengthen forensic readiness, reduce legal risk, and ensure that electronic data remains reliable, authentic, and admissible as evidence.
The other options do not accurately match the described activity. Disposal (Option A) refers to defensible deletion after legal hold requirements expire. Collection (Option C) involves acquiring data for analysis, while Identification (Option D) focuses on locating potentially relevant data sources. None of these address long- term policy creation or enterprise-wide data control.
The CHFI v11 Exam Blueprint explicitly includes Information Governance within the eDiscovery process, highlighting its role in compliance, risk mitigation, and evidence integrity management, making Option B the correct and exam-aligned answer

Option A. strace is the best answer because the question asks for a tool that can intercept and record system calls in real time on a Linux system. That is exactly what strace is designed to do. CHFI v11 includes Linux forensics , Linux memory forensics , and also references system behavior analysis and system calls monitoring when examining malware behavior on systems.
Monitoring system calls is important because it shows how a suspicious process interacts with the operating system kernel, including file access, network activity, process creation, permissions use, and other low-level behavior. That makes strace especially useful when investigating malware on Linux.
The other options do not fit the requirement. Wireshark and tcpdump are network traffic analysis tools, so they observe packets rather than kernel system calls. Process Explorer is associated with Windows process investigation, not Linux syscall tracing. Since the question is specifically about real-time observation of process-to-kernel interactions on Linux, strace is the most accurate and CHFI-aligned tool choice.