NSE7 Advanced Networking and SD-WAN Practice Question
An administrator is configuring an SD-WAN rule to prefer a specific overlay tunnel for VoIP traffic. The rule uses the 'SLA' strategy with a performance SLA that measures jitter and latency. After applying the rule, the administrator notices that VoIP traffic is still being routed over a different member that does not meet the SLA. What is the most likely cause?
⚠ Common exam trap
The trap here is assuming that the SD-WAN rule automatically uses any performance SLA configured on the same members without explicit association.
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
✓
The performance SLA is not assigned to the SD-WAN rule, so the rule cannot use SLA status for member selection.
An SD-WAN rule with the SLA strategy must explicitly reference a performance SLA to use its measurements for member selection. If the SLA is not linked, the rule cannot determine which members meet the SLA and may fall back to other criteria, causing traffic to use a non-compliant member. Ensuring the correct SLA is attached to the rule resolves the issue.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
The performance SLA is not assigned to the SD-WAN rule, so the rule cannot use SLA status for member selection.
Why this is correct
For an SD-WAN rule using the SLA strategy to select members based on performance, the performance SLA must be referenced in the rule's configuration. Without it, the rule cannot evaluate SLA status and may default to other criteria. This is the most likely cause of the observed behavior.
- ✗
The SD-WAN rule is placed below a static route in the routing table, so it is not evaluated.
Why it's wrong here
SD-WAN rules are evaluated before the routing table, so their position relative to static routes does not affect their evaluation. The issue is not about routing table order. The rule's sequence number within the SD-WAN configuration determines priority, not the routing table. Therefore, this is not the cause.
- ✗
The performance SLA is configured with the wrong protocol; it must use HTTP to measure jitter and latency.
Why it's wrong here
Performance SLAs can use various protocols such as ping, HTTP, or TCP echo to measure jitter and latency. HTTP is not mandatory. Using a different protocol might affect the accuracy but would not cause the rule to ignore the SLA status. The problem is more likely related to the SLA action or member configuration.
- ✗
The SD-WAN rule is configured with the 'load-balance' strategy instead of 'SLA', so it does not consider SLA status.
Why it's wrong here
If the rule were using load-balance, it would distribute traffic without regard to SLA, but the scenario states the rule uses the 'SLA' strategy. Therefore, this is not the cause. The issue likely lies in the SLA action or member settings. The strategy is already correct.
Visual reference
About these practice questions
Courseiva writes every NSE7 question from scratch — 718 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Fortinet exam blueprint
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.