NSE5_SSE_AD-7.6 Premium File
- 54 Questions & Answers
- Last Update: Nov 5, 2026
A pilot is validating the implementation. A branch wants to repurpose its second internet interface for private overlay-only traffic while policies still target its original public zone. Which finding proves that the intended fix works?
Public internet flows no longer select the repurposed member and approved overlay traffic behaves as designed. This is the directly relevant check for Moving a member between zones. It confirms the required step: Plan the authorized member-zone reassignment and update dependent route and firewall-zone rules coherently. The operating principle is: Changing zone membership alters which policies and route groups can reference the member.
Private connections select a healthy authorized tunnel and have the intended secondary path on failure. This would validate a different scenario, IPsec overlay member zone, where A regional hub has two IPsec tunnels to the same branch, but private-app failover is not coordinated because the tunnels are absent from the overlay SD-WAN design. The current case needs evidence for Moving a member between zones.
The interface becomes eligible for membership while intended LAN connectivity and management remain intact. This would validate a different scenario, Interface still bound to conflicting config, where A WAN interface is already referenced as a hardware-switch member, so the operator cannot enroll it as a normal SD-WAN member. The current case needs evidence for Moving a member between zones.
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 Moving a member between zones.
A technical lead asks why the recommended approach works. A branch wants to repurpose its second internet interface for private overlay-only traffic while policies still target its original public zone. Which mechanism is most relevant?
Changing zone membership alters which policies and route groups can reference the member. This explains Moving a member between zones in the given environment. The implementation decision is: Plan the authorized member-zone reassignment and update dependent route and firewall-zone rules coherently. Confirm it with: Public internet flows no longer select the repurposed member and approved overlay traffic behaves as designed.
A FortiOS SD-WAN zone can contain one member when isolation or policy scope requires it. That concept concerns Single-member zone for special transport, not the mechanism needed for Moving a member between zones. The relevant principle is: Changing zone membership alters which policies and route groups can reference the member.
FortiOS can treat eligible IPsec interfaces as SD-WAN members alongside physical underlays. That concept concerns IPsec overlay member zone, not the mechanism needed for Moving a member between zones. The relevant principle is: Changing zone membership alters which policies and route groups can reference the member.
SD-WAN zones group member interfaces by operational role so security and routing treat distinct transport families appropriately. That concept concerns Underlay and overlay path purpose, not the mechanism needed for Moving a member between zones. The relevant principle is: Changing zone membership alters which policies and route groups can reference the member.
Before changing production settings, an engineer reviews the symptoms. A branch wants to repurpose its second internet interface for private overlay-only traffic while policies still target its original public zone. Which evidence is most useful?
Inspect old and new zones, dependent service rules, routes and configuration diff. This inspection targets Moving a member between zones rather than a different configuration issue. The corrective action is: Plan the authorized member-zone reassignment and update dependent route and firewall-zone rules coherently. Expected evidence: Public internet flows no longer select the repurposed member and approved overlay traffic behaves as designed.
Inspect zone membership, destination route, tunnel state, firewall interface match and session egress. This is useful when diagnosing Underlay and overlay path purpose. Instead, inspect old and new zones, dependent service rules, routes and configuration diff.
Inspect tunnel interface state, member association, overlay routing and actual session path. This is useful when diagnosing IPsec overlay member zone. Instead, inspect old and new zones, dependent service rules, routes and configuration diff.
Review interface references, switch membership, policy use and rollback before reassignment. This is useful when diagnosing Interface still bound to conflicting config. Instead, inspect old and new zones, dependent service rules, routes and configuration diff.
A deployment review finds this gap. A remote branch assigns a high-bandwidth fiber circuit and slow cellular circuit to one SD-WAN zone and assumes membership alone guarantees fiber preference. What is the most targeted next configuration step?
Specify appropriate eligible member selection strategy, costs, SLA thresholds and preference rather than relying on zone order alone. Zones group member interfaces; steering priorities and SLA rules decide which member a session uses. Expected evidence: Representative new sessions prefer fiber while a failed fiber path allows controlled LTE fallback. Key limit: Zone membership does not inherently encode available throughput or a mandatory primary link.
Configure the supported preferred source and member route behavior for probes and verify ISP reachability. This could apply to the separate issue Member routing source interface ambiguity: Two WAN members have equally reachable upstream gateways, but remote monitoring probes use an unexpected source and are filtered by an ISP. For Interface bandwidth versus logical zone, the directly relevant action is: Specify appropriate eligible member selection strategy, costs, SLA thresholds and preference rather than relying on zone order alone.
Verify its actual assignment to the default virtual-wan-link zone and deliberately move it to the required custom zone if necessary. This could apply to the separate issue WAN member default-zone misconception: An administrator adds a new Ethernet WAN member without explicitly choosing a custom zone and assumes it is isolated from the existing internet policy. For Interface bandwidth versus logical zone, the directly relevant action is: Specify appropriate eligible member selection strategy, costs, SLA thresholds and preference rather than relying on zone order alone.
Plan the authorized member-zone reassignment and update dependent route and firewall-zone rules coherently. This could apply to the separate issue Moving a member between zones: A branch wants to repurpose its second internet interface for private overlay-only traffic while policies still target its original public zone. For Interface bandwidth versus logical zone, the directly relevant action is: Specify appropriate eligible member selection strategy, costs, SLA thresholds and preference rather than relying on zone order alone.
The recommended change has been applied. A remote branch assigns a high-bandwidth fiber circuit and slow cellular circuit to one SD-WAN zone and assumes membership alone guarantees fiber preference. Which observation best verifies the intended outcome?
Representative new sessions prefer fiber while a failed fiber path allows controlled LTE fallback. This is the directly relevant check for Interface bandwidth versus logical zone. It confirms the required step: Specify appropriate eligible member selection strategy, costs, SLA thresholds and preference rather than relying on zone order alone. The operating principle is: Zones group member interfaces; steering priorities and SLA rules decide which member a session uses.
The member appears only in the intended logical zone and test policies match that zone. This would validate a different scenario, WAN member default-zone misconception, where An administrator adds a new Ethernet WAN member without explicitly choosing a custom zone and assumes it is isolated from the existing internet policy. The current case needs evidence for Interface bandwidth versus logical zone.
Public internet flows no longer select the repurposed member and approved overlay traffic behaves as designed. This would validate a different scenario, Moving a member between zones, where A branch wants to repurpose its second internet interface for private overlay-only traffic while policies still target its original public zone. The current case needs evidence for Interface bandwidth versus logical zone.
The health probe reaches the intended target with an accepted source address on each link. This would validate a different scenario, Member routing source interface ambiguity, where Two WAN members have equally reachable upstream gateways, but remote monitoring probes use an unexpected source and are filtered by an ISP. The current case needs evidence for Interface bandwidth versus logical zone.
An architect reviews the platform behavior behind this incident. A remote branch assigns a high-bandwidth fiber circuit and slow cellular circuit to one SD-WAN zone and assumes membership alone guarantees fiber preference. Which explanation applies?
Zones group member interfaces; steering priorities and SLA rules decide which member a session uses. This explains Interface bandwidth versus logical zone in the given environment. The implementation decision is: Specify appropriate eligible member selection strategy, costs, SLA thresholds and preference rather than relying on zone order alone. Confirm it with: Representative new sessions prefer fiber while a failed fiber path allows controlled LTE fallback.
Changing zone membership alters which policies and route groups can reference the member. That concept concerns Moving a member between zones, not the mechanism needed for Interface bandwidth versus logical zone. The relevant principle is: Zones group member interfaces; steering priorities and SLA rules decide which member a session uses.
Member interface source selection can affect locally originated monitoring even when forwarded user sessions work. That concept concerns Member routing source interface ambiguity, not the mechanism needed for Interface bandwidth versus logical zone. The relevant principle is: Zones group member interfaces; steering priorities and SLA rules decide which member a session uses.
A FortiOS SD-WAN zone can contain one member when isolation or policy scope requires it. That concept concerns Single-member zone for special transport, not the mechanism needed for Interface bandwidth versus logical zone. The relevant principle is: Zones group member interfaces; steering priorities and SLA rules decide which member a session uses.
A support analyst is collecting data for this scenario. A remote branch assigns a high-bandwidth fiber circuit and slow cellular circuit to one SD-WAN zone and assumes membership alone guarantees fiber preference. Which diagnostic check is most targeted?
Inspect interface preference, member costs, SLA and session distribution. This inspection targets Interface bandwidth versus logical zone rather than a different configuration issue. The corrective action is: Specify appropriate eligible member selection strategy, costs, SLA thresholds and preference rather than relying on zone order alone. Expected evidence: Representative new sessions prefer fiber while a failed fiber path allows controlled LTE fallback.
Inspect zone membership, eligible services, policy references and LTE session count. This is useful when diagnosing Single-member zone for special transport. Instead, inspect interface preference, member costs, sla and session distribution.
Inspect old and new zones, dependent service rules, routes and configuration diff. This is useful when diagnosing Moving a member between zones. Instead, inspect interface preference, member costs, sla and session distribution.
Inspect default-zone member list, service rules and effective firewall policies. This is useful when diagnosing WAN member default-zone misconception. Instead, inspect interface preference, member costs, sla and session distribution.
A Fortinet administrator must address this operational problem. The primary ISP has low packet loss but occasional severe jitter, and voice calls degrade while a backup link is stable. Which response best resolves it?
Create a voice-appropriate performance SLA measuring jitter, latency and loss and reference it in the matching SD-WAN rule. FortiGate performance SLAs compare measured path quality to configured thresholds for application-aware steering. Expected evidence: A controlled jitter increase makes new eligible voice sessions favor the in-SLA backup path. Key limit: A health monitor does not correct the underlying carrier impairment or guarantee live-session migration.
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 VoIP jitter performance SLA, the directly relevant action is: Create a voice-appropriate performance SLA measuring jitter, latency and loss and reference it in the matching SD-WAN rule.
Use an appropriately configured active probe when continuous idle-link measurement is required, or generate controlled representative traffic. This could apply to the separate issue Passive health measurement idle link: A newly commissioned backup WAN reports little passive quality data because hardly any user sessions have used it. For VoIP jitter performance SLA, the directly relevant action is: Create a voice-appropriate performance SLA measuring jitter, latency and loss and reference it in the matching SD-WAN rule.
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 VoIP jitter performance SLA, the directly relevant action is: Create a voice-appropriate performance SLA measuring jitter, latency and loss and reference it in the matching SD-WAN rule.
For this situation, a reviewer needs acceptance evidence. The primary ISP has low packet loss but occasional severe jitter, and voice calls degrade while a backup link is stable. Which result most directly demonstrates success?
A controlled jitter increase makes new eligible voice sessions favor the in-SLA backup path. This is the directly relevant check for VoIP jitter performance SLA. It confirms the required step: Create a voice-appropriate performance SLA measuring jitter, latency and loss and reference it in the matching SD-WAN rule. The operating principle is: FortiGate performance SLAs compare measured path quality to configured thresholds for application-aware steering.
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 VoIP jitter performance SLA.
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 VoIP jitter performance SLA.
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 VoIP jitter performance SLA.
A network administrator must explain the underlying control. The primary ISP has low packet loss but occasional severe jitter, and voice calls degrade while a backup link is stable. Which statement is correct?
FortiGate performance SLAs compare measured path quality to configured thresholds for application-aware steering. This explains VoIP jitter performance SLA in the given environment. The implementation decision is: Create a voice-appropriate performance SLA measuring jitter, latency and loss and reference it in the matching SD-WAN rule. Confirm it with: A controlled jitter increase makes new eligible voice sessions favor the in-SLA backup path.
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 VoIP jitter performance SLA. The relevant principle is: FortiGate performance SLAs compare measured path quality to configured thresholds for application-aware steering.
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 VoIP jitter performance SLA. The relevant principle is: FortiGate performance SLAs compare measured path quality to configured thresholds for application-aware steering.
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 VoIP jitter performance SLA. The relevant principle is: FortiGate performance SLAs compare measured path quality to configured thresholds for application-aware steering.
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.
Please check your mailbox for a message from support@examlabs.com and follow the directions.