NSE7 Advanced Networking and SD-WAN Practice Question
Which SD-WAN load balancing algorithm distributes traffic based on the number of active sessions per interface?
⚠ Common exam trap
A common mix-up: candidates confuse 'Sessions' with 'Volume' because both involve traffic distribution, but Volume measures bytes while Sessions measures connection counts, and the exam expects you to distinguish between these two distinct load-balancing metrics.
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
✓
Sessions
The Sessions algorithm in Fortinet SD-WAN distributes new sessions by selecting the interface with the fewest currently active sessions. This ensures balanced session distribution across WAN links, preventing any single interface from becoming overloaded with connections while others remain underutilized.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Sessions
Why this is correct
The Sessions algorithm selects the interface carrying the fewest active sessions, spreading load by session count rather than bandwidth, latency or packet volume. This directly matches the stem's constraint of distributing traffic based on the number of active sessions per interface, unlike throughput- or quality-based methods.
- ✗
Volume
Why it's wrong here
Volume measures bytes or bandwidth consumed per interface, not the number of active sessions, so a link with few large transfers could appear busier than one with many small sessions. It suits throughput-based distribution. The algorithm counting active sessions per interface is session-based balancing.
- ✗
Source-destination IP
Why it's wrong here
Source-destination IP hashing pins each flow to one link based on address pairs, so session counts per interface are never measured. It suits stable per-flow path selection, not dynamic balancing by active session load. The algorithm tracking session counts is session-based load balancing.
- ✗
Spillover
Why it's wrong here
Spillover sends traffic to a secondary link only once the primary exceeds a configured bandwidth threshold, ignoring session counts entirely. It fits designs needing a standby link for peak overflow, not per-session distribution. The algorithm counting active sessions per interface is session-based balancing.
Go deeper
Related to this question
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 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.