112-57 ECCouncil EC-Council Digital Forensics Essentials (DFE) Free Practice Exam Questions (2026 Updated)

In the NTFS file system, theMaster File Table (MFT)is the core metadata structure that tracksevery file and directoryon the volume. NTFS implements this as a special system file named$MFT(shown here as$mft). Each file or folder on an NTFS partition is represented by at least oneMFT record entry, which stores essential metadata such as file name(s), timestamps, security identifiers/ACL references, file size, attributes, and pointers to the file’s data runs (or, for very small files, the content can be stored resident inside the record). Because it is the authoritative “index” of file objects, forensic examiners rely heavily on $MFT to reconstruct user activity and file history, including evidence of deleted files (when records are marked unused but remnants of attributes may remain) and timeline building from timestamp attributes.

The other options are different NTFS metadata files with narrower purposes:$LogFilerecords NTFS transaction logs to support recovery,$Volumestores volume-level information (like version/label), and$Quotamanages disk quota tracking. None of these contain a record for every file on the system. Therefore, the NTFS system file that contains a record of every file present is$mft (B).

In classic hard-disk geometry, total capacity is computed fromCHS parameters(Cylinders × Heads × Sectors per track) multiplied bybytes per sector. Forensic examiners learn this because it helps validate whether an image acquisition size is consistent with the physical disk geometry and to spot anomalies caused by misreported device geometry or capture errors.

First compute total addressable sectors:

16,384 cylinders × 80 heads = 1,310,720 tracks(because each head provides a track per cylinder).

Then multiply by sectors per track:

1,310,720 × 63 = 82,575,360 sectors.

Convert sectors to bytes using the sector size:

82,575,360 sectors × 512 bytes/sector = 42,278,584,320 bytes.

This matches optionAexactly. In practice, modern drives often use LBA and may report different logical geometries, but the forensic principle remains the same: capacity equals the number of logical blocks times the logical block size, and CHS-style values are a structured way to perform that verification.

In Windows forensics, recovering deleted or corrupted files typically requires afile-system aware data recovery toolthat can interpret NTFS/FAT metadata and scan disk structures for lost file records and residual content.R-Studiois designed specifically for data recovery: it can locate and rebuild deleted files by analyzing file system metadata (such as NTFS MFT entries and directory records), recover data from formatted or damaged partitions, and perform raw “signature-based” scans to carve files when metadata is missing. This aligns directly with Kelvin’s need for an automated method to restoredamaged, corrupted, or deletedfiles from a Windows system.

The other options do not match the stated recovery objective.OphcrackandCain & Abelare password recovery/auditing tools used to obtain credentials (e.g., cracking hashes), not to restore deleted files.Rohos Mini Driveis primarily an encryption/secure storage utility for creating encrypted containers, which may protect data but does not function as a forensic recovery tool for deleted or corrupted files. Therefore, among the listed tools,R-Studio (C)is the correct choice for automated recovery of deleted files in a Windows forensic investigation.

The technique described—taking a snapshot of the baseline state of the forensic workstation before executing malware—aligns withMonitoring host integrity. In malware forensics, investigators often perform controlled execution (dynamic analysis) and need a reliable way to identifywhat changed on the systemas a direct result of the malware run. Host integrity monitoring is a structured approach where the examiner first captures aknown-good baselineof critical system elements such as file system state (key directories, system binaries), registry/configuration state, running services, installed drivers, scheduled tasks, and sometimes hash inventories of important files. After malware execution, the investigator captures a second snapshot and performsdifferential comparisonto determine newly created/modified files, persistence mechanisms, configuration changes, dropped payloads, and tampering attempts.

This baseline-before/after comparison is fundamental for attributing changes to the sample, supporting repeatability, and documenting evidence in a defensible manner. The other options do not require a workstation baseline snapshot in this sense:online malware scanningchecks a file against signatures/reputation services;string searchextracts readable strings from binaries; andfile fingerprintingtypically refers to hashing to uniquely identify a file, not system-wide state comparison. Therefore, the correct answer isMonitoring host integrity (B).

The role described—being responsible for evidence gathered at the crime scene and maintaining a record that makes the evidence admissible in court—matches the duties of anEvidence manager. In digital forensics practice, admissibility depends heavily on provingintegrity, authenticity, and continuity of possession. The evidence manager ensures these requirements by implementing and documenting thechain of custody, which is the formal, chronological record of who collected the evidence, when and where it was collected, how it was packaged and labeled, how it was transported, where it was stored, and every time it was accessed or transferred. This role also enforces evidence handling procedures such as tamper-evident sealing, secure storage controls, access logging, and verification steps (for example, ensuring hashes are recorded and preserved for forensic images).

Anincident responderfocuses on containment and immediate actions during an incident; anincident analyzerperforms technical analysis and correlation of artifacts; and anevidence examinerconducts detailed forensic examinations on acquired data. While these roles interact with evidence, the specific responsibility for maintaining custody documentation and evidence records to support legal admissibility belongs to theEvidence manager, makingDthe correct answer.

A common requirement in macOS-focused forensic labs is the ability to runmultiple operating systemson a single Mac for controlled testing, malware detonation in a sandbox, reproduction of user activity, and validation of artifacts across platforms. This is typically achieved throughdesktop virtualization, where a hypervisor hosts guest operating systems (such as Windows and various Linux distributions) inside virtual machines.Parallels Desktop 16is a Mac virtualization solution built specifically to run Windows on macOS with strong integration features (such as shared clipboard, folder sharing, and “coherence” modes that allow Windows applications to appear alongside Mac applications). This capability aligns with the question’s description: developing and testing across multiple OSs in VMs on a Mac and enabling use ofMicrosoft Office for Windowswithin that Windows guest environment.

The other tools do not fit.Riverbed ModelerandNetSimare primarilynetwork modeling/simulationtools used for network design and training, not desktop virtualization.Camtasiais used forscreen recording and video editing, which can support documentation but does not provide a VM environment. Therefore, the only option that directly provides cross-OS virtual machines on macOS and supports running Windows applications like Microsoft Office isParallels Desktop 16 (B).

SSH (Secure Shell)is specifically designed to provide anencrypted channelover an untrusted network. In digital forensics and incident response, SSH is well known for supportingtunneling/port forwarding, where traffic for another protocol (for example, HTTP, database connections, or remote desktop) is encapsulated inside an SSH session. Because the SSH session encrypts payload data (and can also protect authentication and command content), the tunneled traffic becomesobfuscated to network monitoring toolsthat can only see metadata such as source/destination IPs, port numbers (often TCP/22), timing, and byte counts. This capability is frequently discussed in forensic references as a mechanism that can hinder content inspection and complicate attribution of user actions purely from packet payload analysis.

By contrast,SNMPis primarily for network management and monitoring, not secure tunneling.ARPresolves IP-to-MAC addresses on local networks and does not provide encryption or tunneling.UDPis a transport protocol that can carry data for many applications but provides no built-in security or tunneling features by itself. Therefore, the protocol that creates secure tunneling enabling content obfuscation isSSH (C).

event logs) to establish user intent and sequence of actions. Therefore, the correct option isBrowsingHistoryView (B).

The key detail is that Sarah’simaging softwarecould not acquire the device because the drive wasvery old and incompatiblewith the software-based approach. In such situations, forensic practice recommends switching to an acquisition method that isless dependent on the operating system or specific imaging application compatibility, while still producing a forensic-accurate duplicate.Bit-stream disk-to-diskacquisition (also called forensic cloning) creates asector-by-sectorcopy of the entire source drive directly onto another physical drive. This method is commonly performed using dedicated duplicators or hardware-assisted workflows that can interface with legacy media more reliably than certain disk-to-image software utilities.

Sparse acquisition would intentionally capture only selected portions of a disk (used to reduce time/storage), which does not fit the goal of “succeeded in imaging the data” after a failure due to incompatibility. Logical acquisition captures only active files/folders through the file system and is not the preferred alternative when full forensic imaging is required, especially in criminal cases. Bit-stream disk-to-image-file is still software/container dependent and is essentially what failed initially. Therefore, the most appropriate alternative that explains success with an older incompatible drive isBit-stream disk-to-disk (D).

Apache error logs record key metadata about server-side events in a structured format that is widely used in web attack investigations. In the provided entry, each bracketed field represents a specific attribute: the first bracket contains the timestamp, the next contains the module and severity (e.g.,core:error), then the process/thread identifiers (pidandtid), followed by the client identifier. The client field is explicitly labeled[client …], and it captures thesource IP address(or sometimes hostname) that initiated the HTTP request which resulted in the logged error.

Here,[client 10.0.0.8]indicates that the request originated from IP address10.0.0.8. This is the critical element investigators use to attribute suspicious activity (such as probing for missing files, scanning directories, or exploitation attempts) to a specific network source. The other values are not the client IP:13:35:38.878945is the time component of the timestamp,12356is the Apache process ID, and8689896234is the thread ID handling the request. Therefore, the IP address from which the request was made is10.0.0.8 (C).

In the Apache Combined/Custom access log format, the value immediately after the quoted request (here,"GET ... HTTP/1.0") is theHTTP status codereturned by the server. In the provided entry, that field is500. From a forensic analysis standpoint, recognizing field positions matters because investigators correlate client IPs, timestamps, requested resources, and server outcomes to reconstruct attack timelines and identify failed exploitation attempts or misconfigurations.

It is important to note thatsuccessful HTTP responses are typically in the 2xx range, most commonly200 (OK), while3xxindicates redirects,4xxindicates client-side errors (such as 404 Not Found), and5xxindicates server-side failures. Specifically,500represents anInternal Server Error, meaning the server encountered an unexpected condition and could not fulfill the request successfully.

The other options are not HTTP status codes in this entry:+0300is the timezone offset in the timestamp,1.0is the HTTP protocol version, and2019is part of the date. Therefore, the only HTTP status code present—and the correct choice among the options—is500 (B), even though it reflects an error rather than success.