NSE7 Troubleshooting and Diagnostics Practice Question
An administrator wants to troubleshoot why specific traffic is not matching a configured firewall policy. Which debug command should be used?
⚠ Common exam trap
Test-takers frequently confuse session listing commands with flow debugging, assuming that viewing existing sessions ('diagnose sys session list') will reveal why new traffic fails to match a policy, when in fact it only shows already-established sessions and not the real-time policy evaluation path.
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
✓
diagnose debug flow
The 'diagnose debug flow' command is the correct tool for tracing traffic through the firewall policy engine in FortiOS. It captures the packet flow in real time, showing which policy is evaluated, why a match or no-match occurs, and any drop reasons. This directly addresses the administrator's need to troubleshoot why specific traffic is not matching a configured firewall policy.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
diagnose sys session list
Why it's wrong here
This command dumps the session table, showing established sessions and their matching policy, but not the policy lookup decision for traffic that never matched. It is tempting because session inspection is central to firewall troubleshooting, making it correct when verifying existing sessions rather than diagnosing non-matching traffic.
- ✗
get firewall policy <id>
Why it's wrong here
This command retrieves a policy's configuration by ID, confirming what the policy contains but not why traffic bypassed it. It is tempting because verifying policy contents is a natural troubleshooting step, making it the right choice when the question concerns a policy's defined parameters rather than live traffic matching.
- ✗
diagnose netlink interface list
Why it's wrong here
This command lists network interfaces and their link state, revealing nothing about why a session failed to match a policy. It is tempting because interface faults do block traffic, making it the right diagnostic when the symptom is a down or misconfigured link rather than a policy mismatch.
- ✓
diagnose debug flow
Why this is correct
The diagnose debug flow command traces packet processing through the FortiGate's policy engine, showing which policy each packet matches or why it is dropped. This directly satisfies the troubleshooting constraint by revealing the specific policy lookup and denial reason for the traffic in question.
Go deeper
Related to this question
About these practice questions
This NSE7 question is part of Courseiva's 718-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 NSE7 practice question is part of Courseiva's free Fortinet 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 NSE7 exam.