NSE5_SSE_AD-7.6 Premium File
- 54 Questions & Answers
- Last Update: Nov 5, 2026
The recommended change has been applied. A less expensive backup link and a costly premium link both pass voice SLA, but the engineer wants the cheaper path while maintaining quality. Which observation best verifies the intended outcome?
Both links in SLA lead new traffic to the cheaper member; degrading the cheaper path causes a healthy alternate to be selected. This is the directly relevant check for Lowest cost in-SLA selection. It confirms the required step: Use Lowest Cost (SLA) with reviewed per-member costs and the required jitter/latency targets. The operating principle is: Lowest Cost (SLA) selects low-cost eligible links after evaluating monitored service constraints.
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 Lowest cost in-SLA selection.
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 Lowest cost in-SLA selection.
New conferencing sessions favor the measured higher-quality eligible path during test intervals. This would validate a different scenario, Best-quality strategy for video meetings, where A branch has two similarly priced carriers but video jitter differs each hour and policy owners want selection based on measured quality rather than cost. The current case needs evidence for Lowest cost in-SLA selection.
An architect reviews the platform behavior behind this incident. A less expensive backup link and a costly premium link both pass voice SLA, but the engineer wants the cheaper path while maintaining quality. Which explanation applies?
Lowest Cost (SLA) selects low-cost eligible links after evaluating monitored service constraints. This explains Lowest cost in-SLA selection in the given environment. The implementation decision is: Use Lowest Cost (SLA) with reviewed per-member costs and the required jitter/latency targets. Confirm it with: Both links in SLA lead new traffic to the cheaper member; degrading the cheaper path causes a healthy alternate to be selected.
Best-quality SD-WAN steering ranks members using monitored performance, not simply a static unit price. That concept concerns Best-quality strategy for video meetings, not the mechanism needed for Lowest cost in-SLA selection. The relevant principle is: Lowest Cost (SLA) selects low-cost eligible links after evaluating monitored service constraints.
Passive WAN health derives measurements from eligible observed sessions; active health checks generate probes independently. That concept concerns Passive health measurement idle link, not the mechanism needed for Lowest cost in-SLA selection. The relevant principle is: Lowest Cost (SLA) selects low-cost eligible links after evaluating monitored service constraints.
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 Lowest cost in-SLA selection. The relevant principle is: Lowest Cost (SLA) selects low-cost eligible links after evaluating monitored service constraints.
A support analyst is collecting data for this scenario. A less expensive backup link and a costly premium link both pass voice SLA, but the engineer wants the cheaper path while maintaining quality. Which diagnostic check is most targeted?
Inspect member cost, priority, health-check status and rule's selected member. This inspection targets Lowest cost in-SLA selection rather than a different configuration issue. The corrective action is: Use Lowest Cost (SLA) with reviewed per-member costs and the required jitter/latency targets. Expected evidence: Both links in SLA lead new traffic to the cheaper member; degrading the cheaper path causes a healthy alternate to be selected.
Review health-check method, session sample volume and link measurement timestamps. This is useful when diagnosing Passive health measurement idle link. Instead, inspect member cost, priority, health-check status and rule's selected member.
Inspect health-check latency/jitter/loss, selected rule and new voice sessions. This is useful when diagnosing VoIP jitter performance SLA. Instead, inspect member cost, priority, health-check status and rule's selected member.
Inspect app match, quality score inputs, live health and selected member. This is useful when diagnosing Best-quality strategy for video meetings. Instead, inspect member cost, priority, health-check status and rule's selected member.
A Fortinet administrator must address this operational problem. A branch has two similarly priced carriers but video jitter differs each hour and policy owners want selection based on measured quality rather than cost. Which response best resolves it?
Apply a best-quality strategy with a relevant performance SLA measurement and suitable application match. Best-quality SD-WAN steering ranks members using monitored performance, not simply a static unit price. Expected evidence: New conferencing sessions favor the measured higher-quality eligible path during test intervals. Key limit: A best-quality score relies on meaningful, current measurements of the application path.
Separate underlay and overlay memberships into logical SD-WAN zones and attach routes and policies to their intended purposes. This could apply to the separate issue Underlay and overlay path purpose: A branch has two internet circuits and two IPsec tunnels, but an engineer groups all four interfaces into one policy zone and loses control of which paths reach private destinations. For Best-quality strategy for video meetings, the directly relevant action is: Apply a best-quality strategy with a relevant performance SLA measurement and suitable application match.
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 Best-quality strategy for video meetings, the directly relevant action is: Apply a best-quality strategy with a relevant performance SLA measurement and suitable application match.
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 Best-quality strategy for video meetings, the directly relevant action is: Apply a best-quality strategy with a relevant performance SLA measurement and suitable application match.
For this situation, a reviewer needs acceptance evidence. A branch has two similarly priced carriers but video jitter differs each hour and policy owners want selection based on measured quality rather than cost. Which result most directly demonstrates success?
New conferencing sessions favor the measured higher-quality eligible path during test intervals. This is the directly relevant check for Best-quality strategy for video meetings. It confirms the required step: Apply a best-quality strategy with a relevant performance SLA measurement and suitable application match. The operating principle is: Best-quality SD-WAN steering ranks members using monitored performance, not simply a static unit price.
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 Best-quality strategy for video meetings.
Direct internet sessions take approved underlay members and private-datacenter sessions use their permitted tunnels. This would validate a different scenario, Underlay and overlay path purpose, where A branch has two internet circuits and two IPsec tunnels, but an engineer groups all four interfaces into one policy zone and loses control of which paths reach private destinations. The current case needs evidence for Best-quality strategy for video meetings.
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 Best-quality strategy for video meetings.
A network administrator must explain the underlying control. A branch has two similarly priced carriers but video jitter differs each hour and policy owners want selection based on measured quality rather than cost. Which statement is correct?
Best-quality SD-WAN steering ranks members using monitored performance, not simply a static unit price. This explains Best-quality strategy for video meetings in the given environment. The implementation decision is: Apply a best-quality strategy with a relevant performance SLA measurement and suitable application match. Confirm it with: New conferencing sessions favor the measured higher-quality eligible path during test intervals.
Central management reduces drift but site-specific values must be substituted before deploying SD-WAN configuration. That concept concerns FortiManager baseline with branch variables, not the mechanism needed for Best-quality strategy for video meetings. The relevant principle is: Best-quality SD-WAN steering ranks members using monitored performance, not simply a static unit price.
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 Best-quality strategy for video meetings. The relevant principle is: Best-quality SD-WAN steering ranks members using monitored performance, not simply a static unit price.
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 Best-quality strategy for video meetings. The relevant principle is: Best-quality SD-WAN steering ranks members using monitored performance, not simply a static unit price.
An incident team needs to isolate the root cause. A branch has two similarly priced carriers but video jitter differs each hour and policy owners want selection based on measured quality rather than cost. Which investigation should be prioritized?
Inspect app match, quality score inputs, live health and selected member. This inspection targets Best-quality strategy for video meetings rather than a different configuration issue. The corrective action is: Apply a best-quality strategy with a relevant performance SLA measurement and suitable application match. Expected evidence: New conferencing sessions favor the measured higher-quality eligible path during test intervals.
Inspect member cost, priority, health-check status and rule's selected member. This is useful when diagnosing Lowest cost in-SLA selection. Instead, inspect app match, quality score inputs, live health and selected member.
Review health-check method, session sample volume and link measurement timestamps. This is useful when diagnosing Passive health measurement idle link. Instead, inspect app match, quality score inputs, live health and selected member.
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 app match, quality score inputs, live health and selected member.
A network engineer faces the following FortiSASE or SD-WAN condition. Monitoring switched to passive WAN health and now a scheduled dashboard has sparse measurements for a rarely used partner tunnel. What should the engineer do?
Restore active probing for that tunnel if round-the-clock quality history is required, using an approved endpoint. Active probes provide periodic measurements independently of user-session sample availability. Expected evidence: Even during idle hours, sufficient health-check history exists to detect upstream degradation. Key limit: More probe traffic has overhead and should be tuned to monitoring needs.
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 logging gaps after passive mode change, the directly relevant action is: Restore active probing for that tunnel if round-the-clock quality history is required, using an approved endpoint.
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 logging gaps after passive mode change, the directly relevant action is: Restore active probing for that tunnel if round-the-clock quality history is required, using an approved endpoint.
Map the session's SD-WAN member identifier back to its configured interface and overlay tunnel association. This could apply to the separate issue Overlay member versus physical port logging: An engineer sees traffic egress from a numbered SD-WAN member but cannot tell which IPsec tunnel underlay provides that member's path. For SLA logging gaps after passive mode change, the directly relevant action is: Restore active probing for that tunnel if round-the-clock quality history is required, using an approved endpoint.
A pilot is validating the implementation. Monitoring switched to passive WAN health and now a scheduled dashboard has sparse measurements for a rarely used partner tunnel. Which finding proves that the intended fix works?
Even during idle hours, sufficient health-check history exists to detect upstream degradation. This is the directly relevant check for SLA logging gaps after passive mode change. It confirms the required step: Restore active probing for that tunnel if round-the-clock quality history is required, using an approved endpoint. The operating principle is: Active probes provide periodic measurements independently of user-session sample availability.
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 logging gaps after passive mode change.
The selected service and member ID resolve to the expected tunnel interface and underlay path. This would validate a different scenario, Overlay member versus physical port logging, where An engineer sees traffic egress from a numbered SD-WAN member but cannot tell which IPsec tunnel underlay provides that member's path. The current case needs evidence for SLA logging gaps after passive mode change.
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 logging gaps after passive mode change.
A technical lead asks why the recommended approach works. Monitoring switched to passive WAN health and now a scheduled dashboard has sparse measurements for a rarely used partner tunnel. Which mechanism is most relevant?
Active probes provide periodic measurements independently of user-session sample availability. This explains SLA logging gaps after passive mode change in the given environment. The implementation decision is: Restore active probing for that tunnel if round-the-clock quality history is required, using an approved endpoint. Confirm it with: Even during idle hours, sufficient health-check history exists to detect upstream degradation.
Zone segmentation constrains which member families may participate in routes and policies. That concept concerns Mixed purpose underlay separation, not the mechanism needed for SLA logging gaps after passive mode change. The relevant principle is: Active probes provide periodic measurements independently of user-session sample availability.
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 logging gaps after passive mode change. The relevant principle is: Active probes provide periodic measurements independently of user-session sample availability.
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 logging gaps after passive mode change. The relevant principle is: Active probes provide periodic measurements independently of user-session sample availability.
Before changing production settings, an engineer reviews the symptoms. Monitoring switched to passive WAN health and now a scheduled dashboard has sparse measurements for a rarely used partner tunnel. Which evidence is most useful?
Compare measurement mode, probe frequency, traffic volume and last update time. This inspection targets SLA logging gaps after passive mode change rather than a different configuration issue. The corrective action is: Restore active probing for that tunnel if round-the-clock quality history is required, using an approved endpoint. Expected evidence: Even during idle hours, sufficient health-check history exists to detect upstream degradation.
Review DNS server config, name lookup, probe logs and route response. This is useful when diagnosing SLA probe blackhole after DNS failure, but not the best first investigation here. Instead, compare measurement mode, probe frequency, traffic volume and last update time.
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, compare measurement mode, probe frequency, traffic volume and last update time.
Inspect member sequence ID, interface binding, tunnel monitor and session output. This is useful when diagnosing Overlay member versus physical port logging, but not the best first investigation here. Instead, compare measurement mode, probe frequency, traffic volume and last update time.
Please check your mailbox for a message from support@examlabs.com and follow the directions.