CHFI Application, Email and Cloud Forensics Practice Question
In MySQL forensics, which log file is most commonly used to detect unauthorized data exfiltration or changes to database records?
⚠ Common exam trap
A common misconception is that the general query log (Option C) is the best for detecting data changes because it logs all queries, but the trap is that it logs both reads and writes without the granular, replayable change tracking of the binary log, and it is frequently turned off in production, making the binary log the actual forensic goldmine.
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
✓
Binary log
The binary log is the correct choice because it records all changes to database data and structure (e.g., INSERT, UPDATE, DELETE, CREATE, ALTER) in a binary format that can be replayed for point-in-time recovery. In MySQL forensics, this log is the primary source for detecting unauthorized data exfiltration or modifications, as it captures the exact SQL statements or row changes that altered the database, along with timestamps and server IDs. Unlike other logs, the binary log is specifically designed to track every write operation, making it indispensable for reconstructing malicious activity.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Binary log
Why this is correct
The binary log records all data-modifying statements and row-level changes in chronological order, making it the primary source for reconstructing unauthorised record alterations or exfiltration activity. Unlike the error log or general query log, it captures committed transactions with before-and-after values, directly satisfying the requirement to detect changes to database records.
- ✗
Slow query log
Why it's wrong here
The slow query log records statements exceeding long_query_time for performance tuning, so it omits the fast SELECT and INSERT operations exfiltration and record tampering generate. It is tempting because it captures SQL text, but it would be the right source only when diagnosing sluggish query performance.
- ✗
General query log
Why it's wrong here
The general query log records every statement received, so it captures reads as well as writes, yet it lacks the row-level before/after values needed to prove record changes or exfiltration. It is tempting because it offers full statement visibility, and it would suit auditing which queries ran, but the binary log is the change-tracking artefact.
- ✗
Error log
Why it's wrong here
The error log captures server startup, shutdown, and runtime faults such as aborted connections or corrupted tables, not the SELECT and UPDATE statements exfiltration or tampering produces. It is tempting because it is enabled by default, but it would be the right source when diagnosing server crashes or failed restarts.
Go deeper
Related to this question
About these practice questions
This CHFI question is part of Courseiva's 745-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 CHFI practice question is part of Courseiva's free EC-Council 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 CHFI exam.