Question 80
Within an IT team managing both BYOD browsers and corporate FortiClient installations, the administrator must authenticate a limited lab user when no central identity source has yet been connected without redesigning unrelated services. Which option addresses the goal?
- Maintain FortiClient tenant registration
- Configure agentless proxy SSO
- Configure SAML single sign-on
- Distribute proxy autoconfiguration settings
- Create a local FortiSASE test user
Explanation
Correct Answer
E:Local user records and groups can be configured for a small controlled FortiSASE rollout; that scope directly serves the goal to authenticate a limited lab user when no central identity source has yet been connected in an IT team managing both BYOD browsers and corporate FortiClient installations. During implementation, local credentials are less desirable than an enterprise identity source at scale rather than treating the configuration label as proof of working service.
Incorrect Answers
A:Registered FortiClient maintains connectivity with FortiSASE endpoint management and supplies identity or posture data, a mechanism intended to preserve endpoint identification and posture exchange for protected access rather than the requested ‘Create a local FortiSASE test user’ control. The stated task instead is to authenticate a limited lab user when no central identity source has yet been connected, and adjusting ‘Maintain FortiClient tenant registration’ would not deliver ‘Create a local FortiSASE test user’. For the ‘Maintain FortiClient tenant registration’ alternative to ‘Create a local FortiSASE test user’, ZTNA decisions may depend on fresh registration and endpoint state.
B:SWG SSO authenticates a web proxy session using the configured identity provider, a mechanism intended to associate proxied browser traffic with enterprise user identity during secure web gateway inspection rather than the requested ‘Create a local FortiSASE test user’ control. The stated task instead is to authenticate a limited lab user when no central identity source has yet been connected, and adjusting ‘Configure agentless proxy SSO’ would not deliver ‘Create a local FortiSASE test user’. For the ‘Configure agentless proxy SSO’ alternative to ‘Create a local FortiSASE test user’, proxy SSO often depends on compatible deep inspection and IdP reachability.
C:FortiSASE acts as a SAML service provider while the configured IdP issues assertions for authenticated users, a mechanism intended to let staff authenticate to FortiSASE through the corporate identity provider rather than the requested ‘Create a local FortiSASE test user’ control. The stated task instead is to authenticate a limited lab user when no central identity source has yet been connected, and adjusting ‘Configure SAML single sign-on’ would not deliver ‘Create a local FortiSASE test user’. For the ‘Configure SAML single sign-on’ alternative to ‘Create a local FortiSASE test user’, the client browser must reach the IdP and the SP metadata and certificates must agree.
D:A PAC-based proxy configuration tells supported browsers which web requests should use the cloud proxy, a mechanism intended to direct selected browser destinations to the FortiSASE secure web gateway rather than the requested ‘Create a local FortiSASE test user’ control. The stated task instead is to authenticate a limited lab user when no central identity source has yet been connected, and adjusting ‘Distribute proxy autoconfiguration settings’ would not deliver ‘Create a local FortiSASE test user’. For the ‘Distribute proxy autoconfiguration settings’ alternative to ‘Create a local FortiSASE test user’, PAC logic and browser support should be tested for exceptions and split behavior.
Question 81
During an authorized lab exercise for a financial services branch where forwarding decisions disagree with interface health, a reviewer needs proof the deployment can confirm the FortiGate has installed a usable next hop for a destination. Which observation most directly validates it?
- Private prefixes resolve to overlays while public prefixes use an approved DIA path.
- Policy-route diagnostics and the matched service show the actual selection chain.
- The hub's public endpoint resolves through a valid ISP underlay route.
- A route lookup shows the expected egress interface and reachable next hop.
Explanation
Correct Answer
D:This checks ‘Verify the forwarding information base’ at the correct operational boundary: the FIB holds selected forwarding entries and is essential to actual packet delivery. It demonstrates the specific capability to confirm the FortiGate has installed a usable next hop for a destination in a financial services branch where forwarding decisions disagree with interface health; deployment should additionally respect the constraint: The SD-WAN rule must be reconciled with actual route installation.
Incorrect Answers
A:That observation belongs to ‘Use split routing for private and internet destinations’, not ‘Verify the forwarding information base’; its purpose is to send corporate destinations over overlay but ordinary internet traffic via local DIA, the underlying behavior is that destination-specific private routes and a general internet default route allow distinct traffic paths. The reviewer is instead verifying ‘Verify the forwarding information base’ for a financial services branch where forwarding decisions disagree with interface health, not the evidence produced by ‘Use split routing for private and internet destinations’.
B:That observation belongs to ‘Validate policy routing and SD-WAN interaction’, not ‘Verify the forwarding information base’; its purpose is to identify why a matching policy-route decision changes normal egress selection, the underlying behavior is that policy route and SD-WAN service rules can influence forwarding decisions beyond basic destination-table lookup. The reviewer is instead verifying ‘Verify the forwarding information base’ for a financial services branch where forwarding decisions disagree with interface health, not the evidence produced by ‘Validate policy routing and SD-WAN interaction’.
C:That observation belongs to ‘Keep underlay route for tunnel peer’, not ‘Verify the forwarding information base’; its purpose is to preserve transport reachability to an IPsec hub before private overlay traffic is steered, the underlying behavior is that an overlay tunnel requires the public peer endpoint to remain reachable through an underlay path. The reviewer is instead verifying ‘Verify the forwarding information base’ for a financial services branch where forwarding decisions disagree with interface health, not the evidence produced by ‘Keep underlay route for tunnel peer’.
Question 82
At a remote access monthly review for the SASE operations team, the change request is to find which authenticated population caused a sustained increase in cloud egress. Which configuration is the most direct fit?
- Use report time filters for incident scoping
- Review application usage reports
- Correlate policy action with destination risk
- Compare user traffic volume trends
Explanation
Correct Answer
D:User traffic analytics aggregate bytes and sessions by identity and time for usage investigation; that scope directly serves the goal to find which authenticated population caused a sustained increase in cloud egress in a remote access monthly review for the SASE operations team. During implementation, traffic volume alone is not evidence that a session is malicious rather than treating the configuration label as proof of working service.
Incorrect Answers
A:Time-bound analytics separate incident-period activity from unrelated historical traffic, a mechanism intended to limit an investigation to the period in which an employee reported a cloud access failure rather than the requested ‘Compare user traffic volume trends’ control. The stated task instead is to find which authenticated population caused a sustained increase in cloud egress, and adjusting ‘Use report time filters for incident scoping’ would not deliver ‘Compare user traffic volume trends’. For the ‘Use report time filters for incident scoping’ alternative to ‘Compare user traffic volume trends’, correlate device and timezone timestamps before drawing incident chronology conclusions.
B:Application analytics classify observed traffic into recognizable applications for reporting, a mechanism intended to identify which SaaS or application class dominates inspected remote traffic rather than the requested ‘Compare user traffic volume trends’ control. The stated task instead is to find which authenticated population caused a sustained increase in cloud egress, and adjusting ‘Review application usage reports’ would not deliver ‘Compare user traffic volume trends’. For the ‘Review application usage reports’ alternative to ‘Compare user traffic volume trends’, app recognition depends on available inspection and classification signals.
C:Security analytics can group blocked traffic by destination or policy to reveal recurring patterns, a mechanism intended to identify repeated attempts to reach restricted destinations across remote users rather than the requested ‘Compare user traffic volume trends’ control. The stated task instead is to find which authenticated population caused a sustained increase in cloud egress, and adjusting ‘Correlate policy action with destination risk’ would not deliver ‘Compare user traffic volume trends’. For the ‘Correlate policy action with destination risk’ alternative to ‘Compare user traffic volume trends’, an event count requires context to distinguish mistakes from an actual threat campaign.
Question 83
During an authorized lab exercise for a cloud security migration with independent web and private-app policies, a reviewer needs proof the deployment can confirm a modified SASE security policy is active before concluding a remediation is complete. Which observation most directly validates it?
- Location-aware policy evaluation blocks the disallowed source geography.
- The design documents and logs show separate SIA and SPA traffic paths.
- Test flows and logs show the new intended policy match and enforcement action.
- Client connectivity shows active SASE steering to a security PoP.
Explanation
Correct Answer
C:This checks ‘Manage policy change verification’ at the correct operational boundary: policy edits require verification of the selected rule, security profiles, and resulting traffic logs. It demonstrates the specific capability to confirm a modified SASE security policy is active before concluding a remediation is complete in a cloud security migration with independent web and private-app policies; deployment should additionally respect the constraint: Validation should use an authorized test identity and representative destination.
Incorrect Answers
A:That observation belongs to ‘Use geolocation-aware access restrictions’, not ‘Manage policy change verification’; its purpose is to restrict access from locations outside an organization-approved geographic footprint, the underlying behavior is that geographic policy criteria can help distinguish traffic by geolocation where FortiSASE policy supports that selection. The reviewer is instead verifying ‘Manage policy change verification’ for a cloud security migration with independent web and private-app policies, not the evidence produced by ‘Use geolocation-aware access restrictions’.
B:That observation belongs to ‘Separate internet and private access policies’, not ‘Manage policy change verification’; its purpose is to apply different controls to cloud web traffic and protected data-center applications, the underlying behavior is that SIA and SPA use distinct routing and policy constructs despite sharing the FortiSASE service. The reviewer is instead verifying ‘Manage policy change verification’ for a cloud security migration with independent web and private-app policies, not the evidence produced by ‘Separate internet and private access policies’.
D:That observation belongs to ‘Choose an appropriate security PoP path’, not ‘Manage policy change verification’; its purpose is to bring roaming clients to cloud enforcement rather than hairpin every connection through headquarters, the underlying behavior is that FortiSASE steers supported client traffic toward its security points of presence for consistent remote policy enforcement. The reviewer is instead verifying ‘Manage policy change verification’ for a cloud security migration with independent web and private-app policies, not the evidence produced by ‘Choose an appropriate security PoP path’.
Question 84
During an authorized lab exercise for a branch experiencing intermittent packet loss during video meetings, the deployment standard specifies the control ‘Use probe loss to trigger failover’ to remove a genuinely unreachable transport from eligible load-balancing routes. Which functional description matches it?
- Failed health checks can withdraw the broken member's routes from the SD-WAN eligible path group.
- A jitter target compares delay variation with an allowed maximum to qualify or reject a member.
- An SD-WAN health check monitors the configured member interfaces instead of automatically representing every interface.
- The SLA target defines tolerated delay, loss, or jitter against measured health-check values.
Explanation
Correct Answer
A:‘Use probe loss to trigger failover’ is used to remove a genuinely unreachable transport from eligible load-balancing routes in a branch experiencing intermittent packet loss during video meetings; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that the failed member becomes ineligible while a healthy route is preferred; the rollout must also respect this constraint: Healthy alternate routing must exist for traffic to continue.
Incorrect Answers
B:The described behavior is part of ‘Set jitter SLA threshold’, used to avoid a circuit whose packet-delay variation damages live audio instead of the role of ‘Use probe loss to trigger failover’. In contrast to ‘Set jitter SLA threshold’, ‘Use probe loss to trigger failover’ follows a different mechanism: failed health checks can withdraw the broken member's routes from the SD-WAN eligible path group. Treating ‘Set jitter SLA threshold’ as equivalent would not address new sessions keep selecting an uplink that no longer reaches monitored destinations in a branch experiencing intermittent packet loss during video meetings.
C:The described behavior is part of ‘Assign the relevant member set to a health check’, used to compare only the transport members serving a given application class instead of the role of ‘Use probe loss to trigger failover’. In contrast to ‘Assign the relevant member set to a health check’, ‘Use probe loss to trigger failover’ follows a different mechanism: failed health checks can withdraw the broken member's routes from the SD-WAN eligible path group. Treating ‘Assign the relevant member set to a health check’ as equivalent would not address new sessions keep selecting an uplink that no longer reaches monitored destinations in a branch experiencing intermittent packet loss during video meetings.
D:The described behavior is part of ‘Configure an SLA target for a health check’, used to turn observed quality metrics into a pass-or-fail objective for rule selection instead of the role of ‘Use probe loss to trigger failover’. In contrast to ‘Configure an SLA target for a health check’, ‘Use probe loss to trigger failover’ follows a different mechanism: failed health checks can withdraw the broken member's routes from the SD-WAN eligible path group. Treating ‘Configure an SLA target for a health check’ as equivalent would not address new sessions keep selecting an uplink that no longer reaches monitored destinations in a branch experiencing intermittent packet loss during video meetings.
Question 85
During an authorized lab exercise for a hub-and-spoke network with internet breakout and private IPsec overlays, the incident notes state that an SD-WAN service names wan2 first but forwarding still excludes wan2. Which change is most relevant to this symptom?
- Investigate: Review route priority
- Investigate: Compare routing table and SD-WAN rule decision
- Investigate: Validate policy routing and SD-WAN interaction
- Investigate: Configure a static partner route through overlay zone
Explanation
Correct Answer
B:The symptom identifies the missing operational behavior: SD-WAN candidate preference works only after routing makes a compatible egress path available. For a hub-and-spoke network with internet breakout and private IPsec overlays, a direct diagnostic confirmation would be that routing diagnostics and service diagnostics together reveal the incompatible candidate; during repair, changing a preference list alone cannot repair a missing route.
Incorrect Answers
A:Route priority can provide an additional selection differentiator when distance and prefix do not distinguish alternatives, which serves the different requirement to resolve preference among otherwise comparable FortiGate route candidates instead of the behavior delivered by ‘Compare routing table and SD-WAN rule decision’. If that component were misconfigured, a more characteristic finding would be that two identical-prefix static routes with matching distance choose an unexpected member; the actual report concerns an SD-WAN service names wan2 first but forwarding still excludes wan2 at a hub-and-spoke network with internet breakout and private IPsec overlays.
C:Policy route and SD-WAN service rules can influence forwarding decisions beyond basic destination-table lookup, which serves the different requirement to identify why a matching policy-route decision changes normal egress selection instead of the behavior delivered by ‘Compare routing table and SD-WAN rule decision’. If that component were misconfigured, a more characteristic finding would be that a destination has a correct static route but a separate steering or policy route sends it elsewhere; the actual report concerns an SD-WAN service names wan2 first but forwarding still excludes wan2 at a hub-and-spoke network with internet breakout and private IPsec overlays.
D:A destination-specific static route referencing the overlay zone makes private routes accessible to SD-WAN selection, which serves the different requirement to reach an on-premises network across an IPsec overlay SD-WAN group instead of the behavior delivered by ‘Compare routing table and SD-WAN rule decision’. If that component were misconfigured, a more characteristic finding would be that the overlay tunnels are healthy but the remote private prefix lacks a usable route; the actual report concerns an SD-WAN service names wan2 first but forwarding still excludes wan2 at a hub-and-spoke network with internet breakout and private IPsec overlays.
Question 86
In a change-control meeting for a coastal retail branch with two internet providers and a FortiGate running FortiOS 7.6, a colleague challenges the proposed control ‘Use DHCP-provided WAN gateway’ for the requirement to keep a dynamically assigned ISP next hop aligned with lease changes. Which explanation accurately describes its behavior?
- A zone groups SD-WAN members for firewall policies, static routes, and service rules without merging the physical circuits.
- Distinct SD-WAN zones make underlay internet circuits and overlay tunnels separate logical choices.
- SD-WAN creates selectable member objects while retaining each interface's underlying addressing and link state.
- An SD-WAN member on a DHCP WAN can inherit the gateway learned from the DHCP interface.
Explanation
Correct Answer
D:‘Use DHCP-provided WAN gateway’ is used to keep a dynamically assigned ISP next hop aligned with lease changes in a coastal retail branch with two internet providers and a FortiGate running FortiOS 7.6; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that the member reflects the currently leased gateway and remains reachable after renewal; the rollout must also respect this constraint: A DHCP-derived gateway should not be confused with the SD-WAN zone route itself.
Incorrect Answers
A:The described behavior is part of ‘Configure an SD-WAN zone’, used to use a common logical outgoing interface for two alternate WAN circuits instead of the role of ‘Use DHCP-provided WAN gateway’. In contrast to ‘Configure an SD-WAN zone’, ‘Use DHCP-provided WAN gateway’ follows a different mechanism: an SD-WAN member on a DHCP WAN can inherit the gateway learned from the DHCP interface. Treating ‘Configure an SD-WAN zone’ as equivalent would not address the dynamic WAN lease renews but a hard-coded obsolete gateway is still being used in a coastal retail branch with two internet providers and a FortiGate running FortiOS 7.6.
B:The described behavior is part of ‘Separate underlay and overlay SD-WAN zones’, used to keep ISP transports and IPsec private overlays independently selectable in policy instead of the role of ‘Use DHCP-provided WAN gateway’. In contrast to ‘Separate underlay and overlay SD-WAN zones’, ‘Use DHCP-provided WAN gateway’ follows a different mechanism: an SD-WAN member on a DHCP WAN can inherit the gateway learned from the DHCP interface. Treating ‘Separate underlay and overlay SD-WAN zones’ as equivalent would not address the dynamic WAN lease renews but a hard-coded obsolete gateway is still being used in a coastal retail branch with two internet providers and a FortiGate running FortiOS 7.6.
C:The described behavior is part of ‘Enable SD-WAN member selection’, used to place two independently addressed internet interfaces under centralized path selection instead of the role of ‘Use DHCP-provided WAN gateway’. In contrast to ‘Enable SD-WAN member selection’, ‘Use DHCP-provided WAN gateway’ follows a different mechanism: an SD-WAN member on a DHCP WAN can inherit the gateway learned from the DHCP interface. Treating ‘Enable SD-WAN member selection’ as equivalent would not address the dynamic WAN lease renews but a hard-coded obsolete gateway is still being used in a coastal retail branch with two internet providers and a FortiGate running FortiOS 7.6.
Question 87
During an authorized lab exercise for a FortiSASE security investigation following a blocked user action, the incident notes state that clients cannot resolve a dangerous domain while normal internet connectivity still works. Which change is most relevant to this symptom?
- Investigate: Inspect DNS-filter threat events
- Investigate: Inspect web-filter category logs
- Investigate: Correlate endpoint posture and access events
- Investigate: Inspect DLP matches
Explanation
Correct Answer
A:The symptom identifies the missing operational behavior: DNS security logs record affected domain requests and configured malicious-domain actions. For a FortiSASE security investigation following a blocked user action, a direct diagnostic confirmation would be that a filtered query event shows the domain and DNS-policy enforcement result; during repair, DNS filtering operates at name resolution, not by scanning file payloads.
Incorrect Answers
B:Web-filter logs associate an HTTP or HTTPS destination with category evaluation and action, which serves the different requirement to determine whether a website was blocked by category policy rather than by transport failure instead of the behavior delivered by ‘Inspect DNS-filter threat events’. If that component were misconfigured, a more characteristic finding would be that a marketing site fails and the team incorrectly assumes the SASE tunnel is down; the actual report concerns clients cannot resolve a dangerous domain while normal internet connectivity still works at a FortiSASE security investigation following a blocked user action.
C:Endpoint and access records can show that a posture tag triggered a conditional denial, which serves the different requirement to identify an endpoint denied for noncompliance rather than for missing network reachability instead of the behavior delivered by ‘Inspect DNS-filter threat events’. If that component were misconfigured, a more characteristic finding would be that a valid user is blocked from private access while another managed device succeeds; the actual report concerns clients cannot resolve a dangerous domain while normal internet connectivity still works at a FortiSASE security investigation following a blocked user action.
D:DLP logs record content-rule matches and the action taken for an inspected transfer, which serves the different requirement to explain which sensitive-content pattern caused a SaaS upload to be denied instead of the behavior delivered by ‘Inspect DNS-filter threat events’. If that component were misconfigured, a more characteristic finding would be that upload traffic is blocked although the SaaS application is otherwise approved; the actual report concerns clients cannot resolve a dangerous domain while normal internet connectivity still works at a FortiSASE security investigation following a blocked user action.
Question 88
At a regional hub where live transport measurements do not agree with the user complaint, the rollout includes the control ‘Set latency SLA threshold’ to exclude paths whose round-trip delay exceeds a real-time application's bound. Which observed mechanism is consistent with this configuration?
- A latency target makes a member fail that SLA when measured delay exceeds the configured limit.
- Best Quality uses configured quality criteria derived from a health check to prioritize the most suitable available member.
- Historical SLA samples and logs help distinguish transient degradation from a persistent member failure.
- Separate health checks can reveal that a circuit reaches one remote service well but another poorly.
Explanation
Correct Answer
A:‘Set latency SLA threshold’ is used to exclude paths whose round-trip delay exceeds a real-time application's bound in a regional hub where live transport measurements do not agree with the user complaint; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that the SLA target status marks the high-latency member noncompliant; the rollout must also respect this constraint: Thresholds must be realistic for the probe destination and business application.
Incorrect Answers
B:The described behavior is part of ‘Use SLA measurements for best-quality steering’, used to feed measured latency, jitter, or loss into a dynamic path-selection rule instead of the role of ‘Set latency SLA threshold’. In contrast to ‘Use SLA measurements for best-quality steering’, ‘Set latency SLA threshold’ follows a different mechanism: a latency target makes a member fail that SLA when measured delay exceeds the configured limit. Treating ‘Use SLA measurements for best-quality steering’ as equivalent would not address an uplink with excessive round-trip delay is still treated as meeting the application's target in a regional hub where live transport measurements do not agree with the user complaint.
C:The described behavior is part of ‘Review SLA historical changes’, used to establish whether a brief performance decline coincides with a reported outage instead of the role of ‘Set latency SLA threshold’. In contrast to ‘Review SLA historical changes’, ‘Set latency SLA threshold’ follows a different mechanism: a latency target makes a member fail that SLA when measured delay exceeds the configured limit. Treating ‘Review SLA historical changes’ as equivalent would not address an uplink with excessive round-trip delay is still treated as meeting the application's target in a regional hub where live transport measurements do not agree with the user complaint.
D:The described behavior is part of ‘Compare health across multiple SLAs’, used to measure distinct service destinations separately rather than treating the internet as one uniform path instead of the role of ‘Set latency SLA threshold’. In contrast to ‘Compare health across multiple SLAs’, ‘Set latency SLA threshold’ follows a different mechanism: a latency target makes a member fail that SLA when measured delay exceeds the configured limit. Treating ‘Compare health across multiple SLAs’ as equivalent would not address an uplink with excessive round-trip delay is still treated as meeting the application's target in a regional hub where live transport measurements do not agree with the user complaint.
Question 89
In a change-control meeting for a regional hub where live transport measurements do not agree with the user complaint, acceptance testing shows that a best-quality rule has no meaningful measured quality input for its preferred links. Which control should be investigated first?
- Investigate: Check probe-path asymmetry
- Investigate: Review SLA historical changes
- Investigate: Use SLA measurements for best-quality steering
- Investigate: Create an active probe health check
Explanation
Correct Answer
C:The symptom identifies the missing operational behavior: Best Quality uses configured quality criteria derived from a health check to prioritize the most suitable available member. For a regional hub where live transport measurements do not agree with the user complaint, a direct diagnostic confirmation would be that the rule references a populated health check and shows candidate quality values; during repair, choosing best quality differs from deciding which member has the smallest monetary cost.
Incorrect Answers
A:Health tests depend on packets reaching the target and return traffic finding a valid response path, which serves the different requirement to confirm health responses return correctly when transport routes are asymmetric instead of the behavior delivered by ‘Use SLA measurements for best-quality steering’. If that component were misconfigured, a more characteristic finding would be that the monitored target responds to other locations but one member records full probe loss; the actual report concerns a best-quality rule has no meaningful measured quality input for its preferred links at a regional hub where live transport measurements do not agree with the user complaint.
B:Historical SLA samples and logs help distinguish transient degradation from a persistent member failure, which serves the different requirement to establish whether a brief performance decline coincides with a reported outage instead of the behavior delivered by ‘Use SLA measurements for best-quality steering’. If that component were misconfigured, a more characteristic finding would be that a link is healthy now but the outage timeline is unexplained; the actual report concerns a best-quality rule has no meaningful measured quality input for its preferred links at a regional hub where live transport measurements do not agree with the user complaint.
D:Active SD-WAN health checks send periodic probes to a designated target over monitored members, which serves the different requirement to measure reachability and delay even when no user sessions traverse a circuit instead of the behavior delivered by ‘Use SLA measurements for best-quality steering’. If that component were misconfigured, a more characteristic finding would be that the firewall has no latency samples during idle periods despite the need for proactive measurements; the actual report concerns a best-quality rule has no meaningful measured quality input for its preferred links at a regional hub where live transport measurements do not agree with the user complaint.
Question 90
Within a retail campus where underlay and overlay paths require distinct treatment, the configuration has been applied. Which measurement or record best confirms the goal to treat an LAG upstream handoff as a selectable SD-WAN transport?
- Both IPsec tunnel members appear in the overlay zone and match the private route.
- The physical WAN device is an enabled member with a valid gateway.
- The tunnel interface is listed as an SD-WAN overlay member.
- The LAG interface, not its individual component ports, is the member.
- The preferred member has the lower configured cost in the SLA-qualified candidates.
Explanation
Correct Answer
D:This checks ‘Use an aggregate interface as a member’ at the correct operational boundary: a link aggregation interface can be an SD-WAN member while LAG distributes frames across its constituent ports. It demonstrates the specific capability to treat an LAG upstream handoff as a selectable SD-WAN transport in a retail campus where underlay and overlay paths require distinct treatment; deployment should additionally respect the constraint: LAG redundancy and SD-WAN multi-carrier path selection solve different failure domains.
Incorrect Answers
A:That observation belongs to ‘Create a dedicated overlay zone’, not ‘Use an aggregate interface as a member’; its purpose is to group IPsec tunnel interfaces separately from physical WAN underlays, the underlying behavior is that overlay zones provide distinct policy and route targets for tunnel traffic bound for private networks. The reviewer is instead verifying ‘Use an aggregate interface as a member’ for a retail campus where underlay and overlay paths require distinct treatment, not the evidence produced by ‘Create a dedicated overlay zone’.
B:That observation belongs to ‘Use a physical interface as a member’, not ‘Use an aggregate interface as a member’; its purpose is to bring a directly connected broadband circuit under SD-WAN decisions, the underlying behavior is that physical WAN ports can act as members with their own connectivity, next hops, costs, and measured health. The reviewer is instead verifying ‘Use an aggregate interface as a member’ for a retail campus where underlay and overlay paths require distinct treatment, not the evidence produced by ‘Use a physical interface as a member’.
C:That observation belongs to ‘Use an IPsec interface as a member’, not ‘Use an aggregate interface as a member’; its purpose is to apply SD-WAN selection to redundant encrypted site-to-site paths, the underlying behavior is that route-based IPsec tunnel interfaces can be members whose quality is measured and selected for overlay routing. The reviewer is instead verifying ‘Use an aggregate interface as a member’ for a retail campus where underlay and overlay paths require distinct treatment, not the evidence produced by ‘Use an IPsec interface as a member’.
E:That observation belongs to ‘Set member cost’, not ‘Use an aggregate interface as a member’; its purpose is to favor a lower-priced uplink only when eligible under lowest-cost SLA rules, the underlying behavior is that the cost field ranks SLA-qualified members for the Lowest Cost strategy, with smaller values preferred. The reviewer is instead verifying ‘Use an aggregate interface as a member’ for a retail campus where underlay and overlay paths require distinct treatment, not the evidence produced by ‘Set member cost’.