An engineer is troubleshooting traffic drops on a Cisco Firepower Threat Defense (FTD) device. The traffic is allowed by the access control policy but is being dropped. Which feature should the engineer check to identify the cause of the drop?
Captures packets and shows the disposition, including drops.
Why this answer
The 'capture' command with the 'trace' option on Cisco FTD provides a detailed, packet-level analysis of how traffic is processed through the firewall pipeline. It shows each step (e.g., ingress, routing, access control, NAT, egress) and explicitly states the drop reason, such as 'action-drop' due to intrusion prevention, URL filtering, or security intelligence, even when the access control policy appears to allow the traffic. This is the only option that directly identifies the specific cause of a drop in the data path.
Exam trap
Cisco often tests the misconception that 'show access-list hit counts' or 'show conn' can diagnose drops, but the trap here is that FTD has multiple inspection layers (prefilter, SSL, intrusion, file, etc.) beyond the basic access control policy, and only a packet trace can pinpoint which layer caused the drop.
How to eliminate wrong answers
Option A is wrong because 'show access-list' hit counts only indicate whether an access control entry (ACE) was matched, not why traffic is dropped after matching; a hit count does not reveal drops due to deeper inspection features like SSL decryption, file policy, or intrusion policy. Option B is wrong because 'show route' checks routing table entries for destination reachability, but traffic drops on FTD often occur after routing decisions (e.g., at the application layer) and routing issues would typically cause a 'no route' drop, not a silent drop when the policy allows traffic. Option D is wrong because 'show conn' displays the state of established connections (e.g., established, time_wait) but does not show why a new packet was dropped before a connection was created; it is useful for connection state but not for identifying drop reasons in the pre-filter or inspection pipeline.