A firewall is experiencing high CPU utilization. The engineer suspects a denial-of-service attack. Which command should be used to identify the source of the attack?
This command lists all sessions and can be filtered to see if a single source has many sessions.
Why this answer
The 'show session all' command displays all active sessions on the firewall, and piping the output to 'match <source IP>' filters for sessions originating from a specific IP address. In a high CPU scenario suspected to be a DoS attack, this allows the engineer to quickly identify if a single source IP is generating an excessive number of sessions, which is a common indicator of a flood-based attack.
Exam trap
The trap here is that candidates often choose 'debug flow basic' (option D) because they think deep packet inspection is needed to find the attack source, but this command is too resource-intensive and does not directly identify the source IP; instead, the session table query is the correct first step.
How to eliminate wrong answers
Option A is wrong because 'show counter global | match drop' shows global packet drop counters (e.g., for policy denies, TCP errors), not the source IP of traffic causing high CPU; it can indicate drops but does not identify the attacker. Option C is wrong because 'request high-availability state' is used to manage HA failover or state synchronization, not to diagnose high CPU or identify attack sources. Option D is wrong because 'debug flow basic' enables verbose packet flow debugging, which can overwhelm the CPU further and is not a targeted command for identifying a DoS source; it is a troubleshooting tool for flow issues, not for source identification.