NSE5_SSE_AD-7.6 Premium File
- 54 Questions & Answers
- Last Update: Nov 5, 2026
An incident team needs to isolate the root cause. The primary ISP has low packet loss but occasional severe jitter, and voice calls degrade while a backup link is stable. Which investigation should be prioritized?
Inspect health-check latency/jitter/loss, selected rule and new voice sessions. This inspection targets VoIP jitter performance SLA rather than a different configuration issue. The corrective action is: Create a voice-appropriate performance SLA measuring jitter, latency and loss and reference it in the matching SD-WAN rule. Expected evidence: A controlled jitter increase makes new eligible voice sessions favor the in-SLA backup path.
Review health-check method, session sample volume and link measurement timestamps. This is useful when diagnosing Passive health measurement idle link. Instead, inspect health-check latency/jitter/loss, selected rule and new voice sessions.
Inspect probe source interface, route lookup to the target and health-check replies. This is useful when diagnosing Health-check server behind wrong route. Instead, inspect health-check latency/jitter/loss, selected rule and new voice sessions.
Inspect member cost, priority, health-check status and rule's selected member. This is useful when diagnosing Lowest cost in-SLA selection. Instead, inspect health-check latency/jitter/loss, selected rule and new voice sessions.
A network engineer faces the following FortiSASE or SD-WAN condition. A branch's SLA probes a server inside its own LAN and reports both carriers healthy even during an upstream internet outage. What should the engineer do?
Select a meaningful reachable external probe target through the intended members and test failure detection. Active performance SLA probes test reachability to a configured server over a member path. Expected evidence: With upstream connectivity withdrawn, the relevant member becomes unhealthy despite its physical link remaining up. Key limit: No single internet probe target can certify reachability of every SaaS service.
Restore supported FortiGate DNS reachability or use a suitable stable probe target, then verify health checks. This could apply to the separate issue SLA probe blackhole after DNS failure: A named cloud health-check target changes address, but a FortiGate with stale DNS cannot resolve it and all internet members show failed probes. For Wrong performance SLA probe destination, the directly relevant action is: Select a meaningful reachable external probe target through the intended members and test failure detection.
Set an appropriate packet-loss performance SLA criterion for affected traffic and validate traffic steering. This could apply to the separate issue Loss-driven link failover: Two healthy WAN interfaces remain physically up, but the primary drops a large percentage of probe packets. For Wrong performance SLA probe destination, the directly relevant action is: Select a meaningful reachable external probe target through the intended members and test failure detection.
Verify that a valid default static route toward the configured SD-WAN zone or equivalent supported route exists and that security policies allow the flow. This could apply to the separate issue SD-WAN quick-start wizard route omission: An administrator runs the SD-WAN setup wizard successfully, but no branch clients can reach the internet despite both member ports appearing healthy. For Wrong performance SLA probe destination, the directly relevant action is: Select a meaningful reachable external probe target through the intended members and test failure detection.
A pilot is validating the implementation. A branch's SLA probes a server inside its own LAN and reports both carriers healthy even during an upstream internet outage. Which finding proves that the intended fix works?
With upstream connectivity withdrawn, the relevant member becomes unhealthy despite its physical link remaining up. This is the directly relevant check for Wrong performance SLA probe destination. It confirms the required step: Select a meaningful reachable external probe target through the intended members and test failure detection. The operating principle is: Active performance SLA probes test reachability to a configured server over a member path.
Eligible new sessions choose a member that meets the reviewed loss target during a controlled loss event. This would validate a different scenario, Loss-driven link failover, where Two healthy WAN interfaces remain physically up, but the primary drops a large percentage of probe packets. The current case needs evidence for Wrong performance SLA probe destination.
Target resolution succeeds and viable members return to their intended health states. This would validate a different scenario, SLA probe blackhole after DNS failure, where A named cloud health-check target changes address, but a FortiGate with stale DNS cannot resolve it and all internet members show failed probes. The current case needs evidence for Wrong performance SLA probe destination.
A representative new client session has a reachable default path and establishes internet access through a selected member. This would validate a different scenario, SD-WAN quick-start wizard route omission, where An administrator runs the SD-WAN setup wizard successfully, but no branch clients can reach the internet despite both member ports appearing healthy. The current case needs evidence for Wrong performance SLA probe destination.
A technical lead asks why the recommended approach works. A branch's SLA probes a server inside its own LAN and reports both carriers healthy even during an upstream internet outage. Which mechanism is most relevant?
Active performance SLA probes test reachability to a configured server over a member path. This explains Wrong performance SLA probe destination in the given environment. The implementation decision is: Select a meaningful reachable external probe target through the intended members and test failure detection. Confirm it with: With upstream connectivity withdrawn, the relevant member becomes unhealthy despite its physical link remaining up.
SLA DNS-name probes depend on the firewall resolving the configured target as well as transporting packets. That concept concerns SLA probe blackhole after DNS failure, not the mechanism needed for Wrong performance SLA probe destination. The relevant principle is: Active performance SLA probes test reachability to a configured server over a member path.
SLA health measurement uses observed packet loss in addition to link carrier status. That concept concerns Loss-driven link failover, not the mechanism needed for Wrong performance SLA probe destination. The relevant principle is: Active performance SLA probes test reachability to a configured server over a member path.
Interface membership and rule creation do not eliminate the separate requirement for a usable forwarding route. That concept concerns SD-WAN quick-start wizard route omission, not the mechanism needed for Wrong performance SLA probe destination. The relevant principle is: Active performance SLA probes test reachability to a configured server over a member path.
Before changing production settings, an engineer reviews the symptoms. A branch's SLA probes a server inside its own LAN and reports both carriers healthy even during an upstream internet outage. Which evidence is most useful?
Inspect probe target route, packet capture and health status during an upstream outage. This inspection targets Wrong performance SLA probe destination rather than a different configuration issue. The corrective action is: Select a meaningful reachable external probe target through the intended members and test failure detection. Expected evidence: With upstream connectivity withdrawn, the relevant member becomes unhealthy despite its physical link remaining up.
Inspect routing table, SD-WAN zone, member gateway, policy and forward-session diagnostic. This is useful when diagnosing SD-WAN quick-start wizard route omission. Instead, inspect probe target route, packet capture and health status during an upstream outage.
Inspect per-member loss counters, probes, rule health map and session selection. This is useful when diagnosing Loss-driven link failover. Instead, inspect probe target route, packet capture and health status during an upstream outage.
Review DNS server config, name lookup, probe logs and route response. This is useful when diagnosing SLA probe blackhole after DNS failure. Instead, inspect probe target route, packet capture and health status during an upstream outage.
A deployment review finds this gap. A newly commissioned backup WAN reports little passive quality data because hardly any user sessions have used it. What is the most targeted next configuration step?
Use an appropriately configured active probe when continuous idle-link measurement is required, or generate controlled representative traffic. Passive WAN health derives measurements from eligible observed sessions; active health checks generate probes independently. Expected evidence: The backup link shows ongoing measurements before production traffic is shifted. Key limit: Passive measurement is traffic-dependent and should not be expected to generate its own packets.
Set reviewed member costs and eligible interface preference to express the intended price ordering. This could apply to the separate issue Wrong SD-WAN member cost expectation: A help desk expects the cheap metered backup link to be idle, but both links have identical cost under a Lowest Cost (SLA) rule. For Passive health measurement idle link, the directly relevant action is: Use an appropriately configured active probe when continuous idle-link measurement is required, or generate controlled representative traffic.
Create a voice-appropriate performance SLA measuring jitter, latency and loss and reference it in the matching SD-WAN rule. This could apply to the separate issue VoIP jitter performance SLA: The primary ISP has low packet loss but occasional severe jitter, and voice calls degrade while a backup link is stable. For Passive health measurement idle link, the directly relevant action is: Use an appropriately configured active probe when continuous idle-link measurement is required, or generate controlled representative traffic.
Use Lowest Cost (SLA) with reviewed per-member costs and the required jitter/latency targets. This could apply to the separate issue Lowest cost in-SLA selection: A less expensive backup link and a costly premium link both pass voice SLA, but the engineer wants the cheaper path while maintaining quality. For Passive health measurement idle link, the directly relevant action is: Use an appropriately configured active probe when continuous idle-link measurement is required, or generate controlled representative traffic.
The recommended change has been applied. A newly commissioned backup WAN reports little passive quality data because hardly any user sessions have used it. Which observation best verifies the intended outcome?
The backup link shows ongoing measurements before production traffic is shifted. This is the directly relevant check for Passive health measurement idle link. It confirms the required step: Use an appropriately configured active probe when continuous idle-link measurement is required, or generate controlled representative traffic. The operating principle is: Passive WAN health derives measurements from eligible observed sessions; active health checks generate probes independently.
Both links in SLA lead new traffic to the cheaper member; degrading the cheaper path causes a healthy alternate to be selected. This would validate a different scenario, Lowest cost in-SLA selection, where A less expensive backup link and a costly premium link both pass voice SLA, but the engineer wants the cheaper path while maintaining quality. The current case needs evidence for Passive health measurement idle link.
A controlled jitter increase makes new eligible voice sessions favor the in-SLA backup path. This would validate a different scenario, VoIP jitter performance SLA, where The primary ISP has low packet loss but occasional severe jitter, and voice calls degrade while a backup link is stable. The current case needs evidence for Passive health measurement idle link.
When both links satisfy SLA, new matching sessions select the lower-cost approved path. This would validate a different scenario, Wrong SD-WAN member cost expectation, where A help desk expects the cheap metered backup link to be idle, but both links have identical cost under a Lowest Cost (SLA) rule. The current case needs evidence for Passive health measurement idle link.
An architect reviews the platform behavior behind this incident. A newly commissioned backup WAN reports little passive quality data because hardly any user sessions have used it. Which explanation applies?
Passive WAN health derives measurements from eligible observed sessions; active health checks generate probes independently. This explains Passive health measurement idle link in the given environment. The implementation decision is: Use an appropriately configured active probe when continuous idle-link measurement is required, or generate controlled representative traffic. Confirm it with: The backup link shows ongoing measurements before production traffic is shifted.
FortiGate performance SLAs compare measured path quality to configured thresholds for application-aware steering. That concept concerns VoIP jitter performance SLA, not the mechanism needed for Passive health measurement idle link. The relevant principle is: Passive WAN health derives measurements from eligible observed sessions; active health checks generate probes independently.
Lowest Cost (SLA) considers qualifying links' configured costs before choosing the preferred candidate. That concept concerns Wrong SD-WAN member cost expectation, not the mechanism needed for Passive health measurement idle link. The relevant principle is: Passive WAN health derives measurements from eligible observed sessions; active health checks generate probes independently.
Lowest Cost (SLA) selects low-cost eligible links after evaluating monitored service constraints. That concept concerns Lowest cost in-SLA selection, not the mechanism needed for Passive health measurement idle link. The relevant principle is: Passive WAN health derives measurements from eligible observed sessions; active health checks generate probes independently.
A support analyst is collecting data for this scenario. A newly commissioned backup WAN reports little passive quality data because hardly any user sessions have used it. Which diagnostic check is most targeted?
Review health-check method, session sample volume and link measurement timestamps. This inspection targets Passive health measurement idle link rather than a different configuration issue. The corrective action is: Use an appropriately configured active probe when continuous idle-link measurement is required, or generate controlled representative traffic. Expected evidence: The backup link shows ongoing measurements before production traffic is shifted.
Inspect member cost, matching service mode, SLA status and selected member. This is useful when diagnosing Wrong SD-WAN member cost expectation, but not the best first investigation here. Instead, review health-check method, session sample volume and link measurement timestamps.
Inspect probe source interface, route lookup to the target and health-check replies. This is useful when diagnosing Health-check server behind wrong route, but not the best first investigation here. Instead, review health-check method, session sample volume and link measurement timestamps.
Inspect member cost, priority, health-check status and rule's selected member. This is useful when diagnosing Lowest cost in-SLA selection, but not the best first investigation here. Instead, review health-check method, session sample volume and link measurement timestamps.
A Fortinet administrator must address this operational problem. A regional fiber link normally measures 35 ms but an engineer sets a 10 ms latency requirement, making all members appear below target. Which response best resolves it?
Calibrate thresholds to application tolerance and real path baseline instead of arbitrary low figures. An SLA target determines eligibility by comparing observed latency to the configured limit. Expected evidence: Normally healthy paths satisfy the chosen target, while injected excessive delay still causes intended steering. Key limit: Relaxing a target cannot make a carrier faster or fix an actual application performance problem.
Use Lowest Cost (SLA) with reviewed per-member costs and the required jitter/latency targets. This could apply to the separate issue Lowest cost in-SLA selection: A less expensive backup link and a costly premium link both pass voice SLA, but the engineer wants the cheaper path while maintaining quality. For SLA latency threshold too strict, the directly relevant action is: Calibrate thresholds to application tolerance and real path baseline instead of arbitrary low figures.
Set an appropriate packet-loss performance SLA criterion for affected traffic and validate traffic steering. This could apply to the separate issue Loss-driven link failover: Two healthy WAN interfaces remain physically up, but the primary drops a large percentage of probe packets. For SLA latency threshold too strict, the directly relevant action is: Calibrate thresholds to application tolerance and real path baseline instead of arbitrary low figures.
Restore supported FortiGate DNS reachability or use a suitable stable probe target, then verify health checks. This could apply to the separate issue SLA probe blackhole after DNS failure: A named cloud health-check target changes address, but a FortiGate with stale DNS cannot resolve it and all internet members show failed probes. For SLA latency threshold too strict, the directly relevant action is: Calibrate thresholds to application tolerance and real path baseline instead of arbitrary low figures.
For this situation, a reviewer needs acceptance evidence. A regional fiber link normally measures 35 ms but an engineer sets a 10 ms latency requirement, making all members appear below target. Which result most directly demonstrates success?
Normally healthy paths satisfy the chosen target, while injected excessive delay still causes intended steering. This is the directly relevant check for SLA latency threshold too strict. It confirms the required step: Calibrate thresholds to application tolerance and real path baseline instead of arbitrary low figures. The operating principle is: An SLA target determines eligibility by comparing observed latency to the configured limit.
The backup link shows ongoing measurements before production traffic is shifted. This would validate a different scenario, Passive health measurement idle link, where A newly commissioned backup WAN reports little passive quality data because hardly any user sessions have used it. The current case needs evidence for SLA latency threshold too strict.
Both links in SLA lead new traffic to the cheaper member; degrading the cheaper path causes a healthy alternate to be selected. This would validate a different scenario, Lowest cost in-SLA selection, where A less expensive backup link and a costly premium link both pass voice SLA, but the engineer wants the cheaper path while maintaining quality. The current case needs evidence for SLA latency threshold too strict.
Target resolution succeeds and viable members return to their intended health states. This would validate a different scenario, SLA probe blackhole after DNS failure, where A named cloud health-check target changes address, but a FortiGate with stale DNS cannot resolve it and all internet members show failed probes. The current case needs evidence for SLA latency threshold too strict.
Please check your mailbox for a message from support@examlabs.com and follow the directions.