NSE5_SSE_AD-7.6 Premium File
- 54 Questions & Answers
- Last Update: Nov 5, 2026
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.
A network administrator must explain the underlying control. A regional fiber link normally measures 35 ms but an engineer sets a 10 ms latency requirement, making all members appear below target. Which statement is correct?
An SLA target determines eligibility by comparing observed latency to the configured limit. This explains SLA latency threshold too strict in the given environment. The implementation decision is: Calibrate thresholds to application tolerance and real path baseline instead of arbitrary low figures. Confirm it with: Normally healthy paths satisfy the chosen target, while injected excessive delay still causes intended steering.
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 SLA latency threshold too strict. The relevant principle is: An SLA target determines eligibility by comparing observed latency to the configured limit.
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 SLA latency threshold too strict. The relevant principle is: An SLA target determines eligibility by comparing observed latency to the configured limit.
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 SLA latency threshold too strict. The relevant principle is: An SLA target determines eligibility by comparing observed latency to the configured limit.
An incident team needs to isolate the root cause. A regional fiber link normally measures 35 ms but an engineer sets a 10 ms latency requirement, making all members appear below target. Which investigation should be prioritized?
Inspect historical latency trends, threshold, service results and route decisions. This inspection targets SLA latency threshold too strict rather than a different configuration issue. The corrective action is: Calibrate thresholds to application tolerance and real path baseline instead of arbitrary low figures. Expected evidence: Normally healthy paths satisfy the chosen target, while injected excessive delay still causes intended steering.
Inspect member cost, priority, health-check status and rule's selected member. This is useful when diagnosing Lowest cost in-SLA selection. Instead, inspect historical latency trends, threshold, service results and route decisions.
Review DNS server config, name lookup, probe logs and route response. This is useful when diagnosing SLA probe blackhole after DNS failure. Instead, inspect historical latency trends, threshold, service results and route decisions.
Inspect configured minimum, member SLA map and matched SD-WAN service status. This is useful when diagnosing Minimum members meeting SLA. Instead, inspect historical latency trends, threshold, service results and route decisions.
A network engineer faces the following FortiSASE or SD-WAN condition. Two healthy WAN interfaces remain physically up, but the primary drops a large percentage of probe packets. What should the engineer do?
Set an appropriate packet-loss performance SLA criterion for affected traffic and validate traffic steering. SLA health measurement uses observed packet loss in addition to link carrier status. Expected evidence: Eligible new sessions choose a member that meets the reviewed loss target during a controlled loss event. Key limit: A high loss threshold is a business tolerance, not a means of recovering lost packets.
Choose a target reachable by each member or correct the per-member probe route for the intended endpoint. This could apply to the separate issue Health-check server behind wrong route: A performance SLA for a backup carrier uses a server reachable only through the primary carrier, so backup checks fail despite working general internet reachability. For Loss-driven link failover, the directly relevant action is: Set an appropriate packet-loss performance SLA criterion for affected traffic and validate traffic steering.
Calibrate thresholds to application tolerance and real path baseline instead of arbitrary low figures. This could apply to the separate issue SLA latency threshold too strict: A regional fiber link normally measures 35 ms but an engineer sets a 10 ms latency requirement, making all members appear below target. For Loss-driven link failover, the directly relevant action is: Set an appropriate packet-loss performance SLA criterion for affected traffic and validate traffic steering.
Select a meaningful reachable external probe target through the intended members and test failure detection. This could apply to the separate issue Wrong performance SLA probe destination: A branch's SLA probes a server inside its own LAN and reports both carriers healthy even during an upstream internet outage. For Loss-driven link failover, the directly relevant action is: Set an appropriate packet-loss performance SLA criterion for affected traffic and validate traffic steering.
A pilot is validating the implementation. Two healthy WAN interfaces remain physically up, but the primary drops a large percentage of probe packets. Which finding proves that the intended fix works?
Eligible new sessions choose a member that meets the reviewed loss target during a controlled loss event. This is the directly relevant check for Loss-driven link failover. It confirms the required step: Set an appropriate packet-loss performance SLA criterion for affected traffic and validate traffic steering. The operating principle is: SLA health measurement uses observed packet loss in addition to link carrier status.
With upstream connectivity withdrawn, the relevant member becomes unhealthy despite its physical link remaining up. This would validate a different scenario, Wrong performance SLA probe destination, where A branch's SLA probes a server inside its own LAN and reports both carriers healthy even during an upstream internet outage. The current case needs evidence for Loss-driven link failover.
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 Loss-driven link failover.
Each member independently reaches its designated health target and reports meaningful path status. This would validate a different scenario, Health-check server behind wrong route, where A performance SLA for a backup carrier uses a server reachable only through the primary carrier, so backup checks fail despite working general internet reachability. The current case needs evidence for Loss-driven link failover.
A technical lead asks why the recommended approach works. Two healthy WAN interfaces remain physically up, but the primary drops a large percentage of probe packets. Which mechanism is most relevant?
SLA health measurement uses observed packet loss in addition to link carrier status. This explains Loss-driven link failover in the given environment. The implementation decision is: Set an appropriate packet-loss performance SLA criterion for affected traffic and validate traffic steering. Confirm it with: Eligible new sessions choose a member that meets the reviewed loss target during a controlled loss event.
Link-up state indicates local interface carrier, not complete path availability or valid forwarding policy. That concept concerns Basic SD-WAN availability test, not the mechanism needed for Loss-driven link failover. The relevant principle is: SLA health measurement uses observed packet loss in addition to link carrier status.
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 Loss-driven link failover. The relevant principle is: SLA health measurement uses observed packet loss in addition to link carrier status.
Active performance SLA probes test reachability to a configured server over a member path. That concept concerns Wrong performance SLA probe destination, not the mechanism needed for Loss-driven link failover. The relevant principle is: SLA health measurement uses observed packet loss in addition to link carrier status.
Before changing production settings, an engineer reviews the symptoms. Two healthy WAN interfaces remain physically up, but the primary drops a large percentage of probe packets. Which evidence is most useful?
Inspect per-member loss counters, probes, rule health map and session selection. This inspection targets Loss-driven link failover rather than a different configuration issue. The corrective action is: Set an appropriate packet-loss performance SLA criterion for affected traffic and validate traffic steering. Expected evidence: Eligible new sessions choose a member that meets the reviewed loss target during a controlled loss event.
Review health-check method, session sample volume and link measurement timestamps. This is useful when diagnosing Passive health measurement idle link. Instead, inspect per-member loss counters, probes, rule health map and session selection.
Inspect historical latency trends, threshold, service results and route decisions. This is useful when diagnosing SLA latency threshold too strict. Instead, inspect per-member loss counters, probes, rule health map and session selection.
Inspect probe target route, packet capture and health status during an upstream outage. This is useful when diagnosing Wrong performance SLA probe destination. Instead, inspect per-member loss counters, probes, rule health map and session selection.
A deployment review finds this gap. A named cloud health-check target changes address, but a FortiGate with stale DNS cannot resolve it and all internet members show failed probes. What is the most targeted next configuration step?
Restore supported FortiGate DNS reachability or use a suitable stable probe target, then verify health checks. SLA DNS-name probes depend on the firewall resolving the configured target as well as transporting packets. Expected evidence: Target resolution succeeds and viable members return to their intended health states. Key limit: Changing user browsing DNS alone may not repair the firewall's local-out resolution.
Select a meaningful reachable external probe target through the intended members and test failure detection. This could apply to the separate issue Wrong performance SLA probe destination: A branch's SLA probes a server inside its own LAN and reports both carriers healthy even during an upstream internet outage. For SLA probe blackhole after DNS failure, the directly relevant action is: Restore supported FortiGate DNS reachability or use a suitable stable probe target, then verify health checks.
Choose a target reachable by each member or correct the per-member probe route for the intended endpoint. This could apply to the separate issue Health-check server behind wrong route: A performance SLA for a backup carrier uses a server reachable only through the primary carrier, so backup checks fail despite working general internet reachability. For SLA probe blackhole after DNS failure, the directly relevant action is: Restore supported FortiGate DNS reachability or use a suitable stable probe target, then verify health checks.
Configure the supported outgoing source NAT behavior for the approved LAN-to-underlay policy and verify the carrier egress address. This could apply to the separate issue Internet SNAT after SD-WAN migration: A branch upgrades to SD-WAN and permitted outbound sessions leave the selected carrier with private RFC1918 source addresses that the provider drops. For SLA probe blackhole after DNS failure, the directly relevant action is: Restore supported FortiGate DNS reachability or use a suitable stable probe target, then verify health checks.
The recommended change has been applied. A named cloud health-check target changes address, but a FortiGate with stale DNS cannot resolve it and all internet members show failed probes. Which observation best verifies the intended outcome?
Target resolution succeeds and viable members return to their intended health states. This is the directly relevant check for SLA probe blackhole after DNS failure. It confirms the required step: Restore supported FortiGate DNS reachability or use a suitable stable probe target, then verify health checks. The operating principle is: SLA DNS-name probes depend on the firewall resolving the configured target as well as transporting packets.
Each member independently reaches its designated health target and reports meaningful path status. This would validate a different scenario, Health-check server behind wrong route, where A performance SLA for a backup carrier uses a server reachable only through the primary carrier, so backup checks fail despite working general internet reachability. The current case needs evidence for SLA probe blackhole after DNS failure.
Normally healthy paths satisfy the chosen target, while injected excessive delay still causes intended steering. This would validate a different scenario, SLA latency threshold too strict, where A regional fiber link normally measures 35 ms but an engineer sets a 10 ms latency requirement, making all members appear below target. The current case needs evidence for SLA probe blackhole after DNS failure.
With upstream connectivity withdrawn, the relevant member becomes unhealthy despite its physical link remaining up. This would validate a different scenario, Wrong performance SLA probe destination, where A branch's SLA probes a server inside its own LAN and reports both carriers healthy even during an upstream internet outage. The current case needs evidence for SLA probe blackhole after DNS failure.
An architect reviews the platform behavior behind this incident. A named cloud health-check target changes address, but a FortiGate with stale DNS cannot resolve it and all internet members show failed probes. Which explanation applies?
SLA DNS-name probes depend on the firewall resolving the configured target as well as transporting packets. This explains SLA probe blackhole after DNS failure in the given environment. The implementation decision is: Restore supported FortiGate DNS reachability or use a suitable stable probe target, then verify health checks. Confirm it with: Target resolution succeeds and viable members return to their intended health states.
Active performance SLA probes test reachability to a configured server over a member path. That concept concerns Wrong performance SLA probe destination, not the mechanism needed for SLA probe blackhole after DNS failure. The relevant principle is: SLA DNS-name probes depend on the firewall resolving the configured target as well as transporting packets.
Active SLA quality depends on probes traversing the member whose health is being measured. That concept concerns Health-check server behind wrong route, not the mechanism needed for SLA probe blackhole after DNS failure. The relevant principle is: SLA DNS-name probes depend on the firewall resolving the configured target as well as transporting packets.
An SLA target determines eligibility by comparing observed latency to the configured limit. That concept concerns SLA latency threshold too strict, not the mechanism needed for SLA probe blackhole after DNS failure. The relevant principle is: SLA DNS-name probes depend on the firewall resolving the configured target as well as transporting packets.
A support analyst is collecting data for this scenario. A named cloud health-check target changes address, but a FortiGate with stale DNS cannot resolve it and all internet members show failed probes. Which diagnostic check is most targeted?
Review DNS server config, name lookup, probe logs and route response. This inspection targets SLA probe blackhole after DNS failure rather than a different configuration issue. The corrective action is: Restore supported FortiGate DNS reachability or use a suitable stable probe target, then verify health checks. Expected evidence: Target resolution succeeds and viable members return to their intended health states.
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 dns server config, name lookup, probe logs and route response.
Inspect probe target route, packet capture and health status during an upstream outage. This is useful when diagnosing Wrong performance SLA probe destination, but not the best first investigation here. Instead, review dns server config, name lookup, probe logs and route response.
Compare measurement mode, probe frequency, traffic volume and last update time. This is useful when diagnosing SLA logging gaps after passive mode change, but not the best first investigation here. Instead, review dns server config, name lookup, probe logs and route response.
Please check your mailbox for a message from support@examlabs.com and follow the directions.