According to the CHFI v11 objectives under Web Application Forensics and Log Analysis , investigators must know the default log storage locations of commonly used web servers. On Windows-based systems , Internet Information Services (IIS) stores its web server logs within the inetpub directory, which resides on the system drive by default. The standard path used by IIS for logging HTTP and HTTPS requests is:

%SystemDrive%\inetpub\logs\LogFiles

In this question, the option %SystemDrive%\inetpub correctly points to the parent directory that contains IIS-related content, including the LogFiles directory where forensic-relevant web access logs are stored. These logs record critical details such as client IP addresses, request methods, requested URLs, HTTP status codes, timestamps, and user agents—key artifacts for reconstructing web-based attacks such as SQL injection, directory traversal, brute-force attempts, and malicious file uploads.

The other options are incorrect because they reference Apache web server configuration files used on Linux or UNIX systems, not IIS. Since the server in question is Windows-based and running IIS, those paths are irrelevant to the investigation.

The CHFI Exam Blueprint v4 explicitly includes IIS web server architecture and log analysis , emphasizing familiarity with default IIS log locations as essential for effective web attack investigations and evidence collection, making Option D the correct and exam-aligned answer

According to the CHFI v11 Computer Forensics Fundamentals and Investigation Process , one of the most critical steps in forming a specialized cybercrime investigation team is clearly assigning roles and responsibilities to team members . This step ensures that every aspect of the investigation is handled efficiently, lawfully, and without overlap or conflict.

CHFI v11 emphasizes that cybercrime investigations are multidisciplinary by nature and require role-based coordination . Typical roles include first responders, incident responders, forensic examiners, evidence handlers, photographers, documentation specialists, and legal advisors. Clearly defining these roles at the outset ensures proper evidence handling, adherence to legal procedures, and effective incident response . It also supports maintaining the chain of custody , minimizing contamination of evidence, and ensuring accountability throughout the investigation lifecycle.

While legal advice and external support are important, they are supplementary functions that support the investigation after the core team structure is established. Conducting digital forensics analysis is an operational activity that occurs later in the forensic process, not during team formation.

CHFI v11 explicitly highlights building the investigation team and assigning responsibilities as foundational steps before evidence collection and analysis begin. Without clearly defined roles, investigations risk procedural errors, legal challenges, and inefficiencies.

Therefore, the most crucial step in forming a specialized cybercrime investigation team—fully aligned with CHFI v11 objectives—is assigning roles to team members , making Option D the correct answer.

Option D. Sniff and analyze packets is the best answer because the scenario states that Liam captured network traffic specifically to examine the activity associated with the suspicious transaction. In CHFI v11, network and wireless forensic work includes identifying access points, discovering active connections, and performing packet capture and analysis to reconstruct events and detect suspicious communications.

Once the investigator is actually collecting and examining traffic content, he has moved beyond discovery into the packet-sniffing and analysis phase . This is where the examiner looks for suspicious sessions, authentication attempts, remote-access behavior, protocol anomalies, and other evidence that may show how the transaction was performed remotely.

Option A is narrower and would focus more on enumerating current sessions. Options B and C are earlier wireless-network investigative activities related to locating infrastructure. Since Liam is already capturing and analyzing the actual traffic, the most accurate phase is sniff and analyze packets . That aligns best with CHFI’s traffic-analysis and network-forensics objectives.

Event correlation in CHFI v11 is a critical investigative technique used to reconstruct attack timelines by analyzing and correlating events from multiple log sources. The CHFI blueprint clearly distinguishes between Same-Platform Correlation and Cross-Platform Correlation under the domain of Image/Evidence Examination and Event Correlation .

Cross-Platform Correlation applies when an investigation involves heterogeneous environments , meaning different operating systems, hardware platforms, or network devices are involved in the incident. A common real-world example—explicitly referenced in CHFI training—is an enterprise environment where Windows-based client systems or servers interact with Linux-based infrastructure components such as firewalls, IDS/IPS devices, or proxies . In such cases, investigators must correlate Windows Event Logs with Linux syslogs, firewall logs, and network device records to build a unified timeline of attacker activity.

Option B correctly reflects this scenario by describing the use of Windows servers alongside Linux-based firewalls , which is a textbook example of Cross-Platform Correlation. Option A relates to standardization, not correlation. Option C represents a single-platform environment, and Option D refers to security tooling diversity rather than operating system or platform diversity.

CHFI v11 emphasizes Cross-Platform Correlation as essential for detecting multi-stage attacks , lateral movement, and perimeter breaches in modern hybrid infrastructures, making Option B the correct and exam-aligned answer

This question aligns with CHFI v11 objectives under Data Acquisition and Duplication , specifically image validation and forensic integrity verification . After acquiring a forensic image, it is a mandatory best practice to verify that the image is an exact bit-for-bit replica of the original evidence source. CHFI v11 stresses that verification protects evidence integrity and supports legal admissibility by proving that no data was altered during acquisition.

The dcfldd tool—an enhanced version of the Unix dd utility—supports forensic features such as hashing, logging, splitting, and image verification . The vf (verify file) parameter in the command

dcfldd if=/dev/sda vf=image.dd

directly compares the original input device (/dev/sda) with the previously created image file (image.dd). This ensures that both sources match exactly, sector by sector.

Option B performs imaging with hashing but does not verify an existing image against the original drive. Option C simply creates an image without validation, and Option D uses dd with file splitting, which lacks forensic verification features. Therefore, consistent with CHFI v11 acquisition validation standards, Option A is the correct command to verify the forensic image against the original medium.

According to CHFI v11 objectives under Computer Forensics Fundamentals and Regulations, Policies, and Ethics , a forensic investigator must ensure that technical investigation activities align with applicable legal and regulatory requirements. The Gramm-Leach-Bliley Act (GLBA) mandates that financial institutions protect customers’ nonpublic personal information (NPI) and respond appropriately to any unauthorized access or disclosure.

When a breach involving GLBA-protected data is identified, the organization must follow a structured incident response and forensic investigation process while maintaining compliance with privacy laws. CHFI v11 emphasizes forensic readiness, legal compliance, and ethical handling of digital evidence. Notifying affected customers of their opt-out rights and implementing safeguards to protect compromised data are core requirements of GLBA’s Privacy Rule and Safeguards Rule.

Ignoring the incident violates forensic and legal responsibilities, while sharing sensitive data with third parties risks further disclosure. Informing law enforcement alone is insufficient if customer notification obligations are not met. Proper customer notification demonstrates due diligence, supports transparency, and reduces legal risk. From a CHFI perspective, this approach ensures lawful evidence handling, regulatory compliance, and preservation of organizational credibility during forensic investigations.

Under the CHFI v11 Mobile and IoT Forensics domain, investigators are required to extract and analyze application-level artifacts from mobile devices to reconstruct user activity. Web browsers such as Google Chrome store valuable forensic data on Android devices, including browsing history, cookies, cached files, saved form data, session tokens, and timestamps , which can be critical in cybercrime investigations.

Magnet AXIOM is a comprehensive digital forensics platform explicitly supported and referenced in CHFI v11 for mobile device forensic analysis . It is capable of performing logical and file system extractions from Android devices and includes built-in parsers for Chrome artifacts . Magnet AXIOM can automatically locate Chrome databases (such as History, Cookies, and cache directories), decode SQLite databases, and present the extracted data in a forensically structured and timeline-based view. This makes it highly effective for correlating browser activity with other evidence.

The other tools listed are not suitable for this task. LOIC is a network stress-testing/DoS tool, Orbot Proxy is used to route traffic through the Tor network, and DroidSheep is a network sniffing tool for session hijacking. None of these tools are designed for forensic extraction or analysis of browser artifacts from Android devices.

Therefore, in alignment with CHFI v11 Mobile and IoT Forensics objectives , the correct and most suitable tool for extracting Chrome artifacts from an Android device is Magnet AXIOM , making Option D the correct answer.

The best answer is A because the scenario emphasizes timely evidence sharing and coordinated action across more than one jurisdiction. In CHFI v11, the role of local and international agencies in cybercrime investigation is tied closely to cooperation, coordination, and cross-border support. International cybercrime cases often involve different legal systems, different evidence holders, and separate law enforcement or regulatory bodies. Because of that, the most critical function is collaboration between agencies so requests can be aligned, evidence can be preserved quickly, and investigative actions can be coordinated without duplication or delay. Option D sounds plausible, but investigation is a broad activity performed by many parties and does not specifically capture the cross-jurisdiction function highlighted by the question. Option C relates more to governance than operational evidence handling. Option B is not the standard function being tested here. In CHFI-style reasoning, when the issue is multinational evidence coordination and synchronized action, collaboration is the central capability that makes the rest of the process possible. That is why collaboration is the strongest answer.

The best answer is D because Serial Attached SCSI is designed for enterprise environments where reliability, throughput, and path redundancy matter. The scenario describes dual-controller style resilience and continued availability if one path fails, which points to multipath-capable storage connectivity rather than a simpler desktop-oriented interface. CHFI v11 includes disk interfaces and storage concepts under digital evidence fundamentals, so candidates are expected to distinguish enterprise forensic workstation and server storage characteristics from ordinary consumer storage. SATA is common and cost-effective, but it does not match the same level of enterprise redundancy and controller-path resilience suggested here. PCIe is a bus architecture used by devices such as NVMe storage, but it is not the disk interface concept being tested in this option set. Traditional parallel SCSI is older and less aligned with the modern rack-mounted, high-availability context described. SAS supports robust enterprise drive connectivity, simultaneous communication behavior, and high-availability storage designs, which makes it the strongest fit for a forensic recovery workstation that must maintain dependable access even when one path or controller encounters a problem.

The correct answer is D because a histogram is the view designed to show how response times are distributed across ranges, making it ideal for spotting clusters, skew, long tails, or intermittent delay bands that averages can hide. Sumo Logic’s IIS Log Analyzer documentation explicitly lists “Response times in histogram form” as one of the available views in the app. That makes it the most appropriate choice when analysts need to determine whether delays are concentrated in specific intervals rather than simply looking at aggregate throughput or server counts. Requests by server would help compare load across hosts, slowest pages would identify particular endpoints with high latency, and response throughputs would focus on volume over time. None of those directly answers the distribution question posed in the scenario. CHFI v11 includes IIS log analysis and web-application attack investigation, so candidates should be able to select the visualization that best supports a given forensic question. When the goal is to reveal response-time frequency patterns across the whole dataset, the correct analytic view is response times in histogram form.