Quick Answer
The answer is erasing tracks, the final phase of the hacking methodology. Clearing Windows Event Logs and creating gaps in the Security log is a deliberate post-exploitation step to remove forensic evidence of an attacker’s actions, which directly aligns with the goal of covering tracks. On the Certified Ethical Hacker CEH exam, this phase tests your understanding of post-exploitation cleanup, often paired with rootkit detection questions because rootkits commonly include log-wiping capabilities to hide persistence. A common trap is confusing this with the “maintaining access” phase, but remember: erasing tracks is about hiding evidence, not keeping the door open. For a quick memory tip, think of the phrase “clean up after the break-in”—if logs are cleared or show gaps, you are looking at the erasing tracks phase.
This CEH practice question tests your understanding of enumeration and system hacking. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
An incident responder finds that the Windows Event Logs on a compromised server have been cleared, and the Security log shows gaps in coverage. Additionally, a rootkit is suspected. Which phase of the hacking methodology does the clearing of logs represent?
Privilege escalation
Why wrong: Privilege escalation occurs earlier; log clearing is post-exploitation.
Cracking passwords
Why wrong: Password cracking is separate from covering tracks.
Erasing tracks
Clearing logs is a classic covering tracks technique.
Executing applications
Why wrong: Executing applications is about running payloads, not hiding evidence.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Erasing tracks
Clearing Windows Event Logs and creating gaps in the Security log is a classic post-exploitation step to remove forensic evidence of the attacker's actions. In the CEH hacking methodology, this falls under 'Erasing tracks' (also known as covering tracks), which is the final phase after maintaining access. The rootkit suspicion further supports this, as rootkits often include log-wiping or log-modification capabilities to hide their presence.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
Privilege escalation
Why it's wrong here
Privilege escalation occurs earlier; log clearing is post-exploitation.
Cracking passwords
Why it's wrong here
Password cracking is separate from covering tracks.
Erasing tracks
Why this is correct
Clearing logs is a classic covering tracks technique.
Related concept
Read the scenario before looking for a memorised answer.
Executing applications
Why it's wrong here
Executing applications is about running payloads, not hiding evidence.
Common exam traps
The trap here is that candidates confuse 'Erasing tracks' with 'Privilege escalation' because clearing logs often requires administrative privileges, but the phase is defined by the intent to hide evidence, not the permission level used.
Detailed technical explanation
Windows Event Logs are stored as .evtx files in C:\Windows\System32\winevt\Logs, and clearing them via wevtutil cl Security or the Event Viewer GUI removes all entries, leaving a gap that a forensic analyst can detect by checking the Event Log creation timestamps or using tools like Log Parser. Rootkits often hook system APIs (e.g., NtClearEventLog) to selectively delete or modify log entries in real time, making detection harder. In a real-world incident, the attacker might also disable logging via registry keys (e.g., HKLM\SYSTEM\CurrentControlSet\Services\EventLog\Security) before clearing logs.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
A junior network technician can log in to a core router but cannot reach the enable prompt or configuration mode. The AAA server is authenticating the login — but the authorisation policy only grants privilege level 1, not 15. Authentication (who you are) is working; authorisation (what you can do) is not.
What to study next
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Enumeration and System Hacking — study guide chapter
Learn the concepts, then practise the questions
Enumeration and System Hacking practice questions
Targeted practice on this topic area only
All CEH questions
1,010 questions across all exam domains
Certified Ethical Hacker CEH study guide
Full concept coverage aligned to exam objectives
CEH practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise CEH questions linked to Footprinting, Reconnaissance and Scanning.
Practise CEH questions linked to Enumeration and System Hacking.
Practise CEH questions linked to Malware, Social Engineering and Network Attacks.
Practise CEH questions linked to Web Application and Injection Attacks.
Practise CEH questions linked to Introduction to Ethical Hacking.
Practise CEH questions linked to Scanning Networks and Enumeration.
Practise CEH questions linked to Vulnerability Analysis and System Hacking.
Practise CEH questions linked to Advanced Topics: Wireless, Cloud, IoT, Cryptography.
Practise CEH questions linked to Footprinting and Reconnaissance.
Practise CEH questions linked to Network and Web Application Attacks.
Practise CEH questions linked to Wireless, IoT and Cloud Security.
Practise CEH questions linked to Cryptography and Malware Analysis.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Enumeration and System Hacking — This question tests Enumeration and System Hacking — Read the scenario before looking for a memorised answer..
The correct answer is: Erasing tracks — Clearing Windows Event Logs and creating gaps in the Security log is a classic post-exploitation step to remove forensic evidence of the attacker's actions. In the CEH hacking methodology, this falls under 'Erasing tracks' (also known as covering tracks), which is the final phase after maintaining access. The rootkit suspicion further supports this, as rootkits often include log-wiping or log-modification capabilities to hide their presence.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Keep practising
Last reviewed: Jun 24, 2026
This CEH 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 CEH exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.