Question 560
In a change-control meeting for a video collaboration office using two simultaneously healthy circuits, the team is closing the change after testing a design to prefer the circuit losing fewer packets for interactive services. Which result supports closure?
- Separate old and new session entries reveal their actual selected interfaces.
- The narrow rule appears ahead of the broad rule and receives matching hits.
- The rule's loss criterion ranks the measured low-loss member first.
- The application-control internet-service list contains the learned application destination tuple.
Explanation
Correct Answer
C:This checks ‘Use Best Quality with packet loss’ at the correct operational boundary: Best Quality supports loss-oriented link comparison using measured health data. It demonstrates the specific capability to prefer the circuit losing fewer packets for interactive services in a video collaboration office using two simultaneously healthy circuits; deployment should additionally respect the constraint: A low loss figure does not necessarily imply better latency or lower cost.
Incorrect Answers
A:That observation belongs to ‘Treat existing sessions differently from new flows’, not ‘Use Best Quality with packet loss’; its purpose is to troubleshoot a session that remains associated with an earlier selection after an SD-WAN change, the underlying behavior is that session state and configured failover behavior affect when path changes apply; newly created flows are evaluated against current steering. The reviewer is instead verifying ‘Use Best Quality with packet loss’ for a video collaboration office using two simultaneously healthy circuits, not the evidence produced by ‘Treat existing sessions differently from new flows’.
B:That observation belongs to ‘Order specific SD-WAN rules above general matches’, not ‘Use Best Quality with packet loss’; its purpose is to ensure a narrow high-priority policy wins instead of a catch-all service rule, the underlying behavior is that SD-WAN service rules are evaluated in configured order, so earlier matching entries can take precedence. The reviewer is instead verifying ‘Use Best Quality with packet loss’ for a video collaboration office using two simultaneously healthy circuits, not the evidence produced by ‘Order specific SD-WAN rules above general matches’.
D:That observation belongs to ‘Consider first-flow application recognition’, not ‘Use Best Quality with packet loss’; its purpose is to explain why the first newly observed app session may not match application-based steering immediately, the underlying behavior is that FortiOS learns application signatures and destination tuples from inspected sessions for subsequent application-based matches. The reviewer is instead verifying ‘Use Best Quality with packet loss’ for a video collaboration office using two simultaneously healthy circuits, not the evidence produced by ‘Consider first-flow application recognition’.
Question 561
At a hub-and-spoke network with internet breakout and private IPsec overlays, an engineer is preparing ‘Configure a static partner route through overlay zone’ to reach an on-premises network across an IPsec overlay SD-WAN group. Which TWO statements identify a pertinent deployment safeguard and a direct post-change validation result? Choose TWO.
- Priority has meaning within the relevant route-selection context, not across unrelated prefixes.
- The remote peer must also know a return path to the local subnet.
- Specificity is considered before comparing administrative distance on different prefix lengths.
- Routing diagnostics and service diagnostics together reveal the incompatible candidate.
- The target private CIDR resolves through the overlay SD-WAN zone.
Explanation
Correct Answers
B:This safeguard applies to ‘Configure a static partner route through overlay zone’, which works because a destination-specific static route referencing the overlay zone makes private routes accessible to SD-WAN selection. Without the correct deployment condition, operators may see that the overlay tunnels are healthy but the remote private prefix lacks a usable route in a hub-and-spoke network with internet breakout and private IPsec overlays.
E:The observation follows from the operation of ‘Configure a static partner route through overlay zone’: a destination-specific static route referencing the overlay zone makes private routes accessible to SD-WAN selection. It directly tests the requested ability to reach an on-premises network across an IPsec overlay SD-WAN group in a hub-and-spoke network with internet breakout and private IPsec overlays, rather than another policy or network layer.
Incorrect Answers
A:The planning point is associated with ‘Review route priority’, not ‘Configure a static partner route through overlay zone’; its real role is to resolve preference among otherwise comparable FortiGate route candidates. The required deployment instead centers on ‘Configure a static partner route through overlay zone’, rather than ‘Review route priority’; the distinct symptom to guard against is that the overlay tunnels are healthy but the remote private prefix lacks a usable route.
C:The planning point is associated with ‘Review administrative distance’, not ‘Configure a static partner route through overlay zone’; its real role is to choose between competing routes learned from different sources for the same prefix. The required deployment instead centers on ‘Configure a static partner route through overlay zone’, rather than ‘Review administrative distance’; the distinct symptom to guard against is that the overlay tunnels are healthy but the remote private prefix lacks a usable route.
D:This result would validate ‘Compare routing table and SD-WAN rule decision’, not ‘Configure a static partner route through overlay zone’, because SD-WAN candidate preference works only after routing makes a compatible egress path available. That separate implementation serves find which stage prevents a preferred member from being used, whereas the audit needs evidence specifically of ‘Configure a static partner route through overlay zone’ at a hub-and-spoke network with internet breakout and private IPsec overlays.
Question 562
For a medical office prioritizing stable response times to a hosted patient system, a review of the current state finds that the ISP is repaired yet the member remains marked failed due to probe failure. Which configuration area most directly addresses this?
- Investigate: Configure an SLA target for a health check
- Investigate: Set packet-loss SLA threshold
- Investigate: Observe recovery of a monitored member
- Investigate: Create an active probe health check
- Investigate: Review SLA historical changes
- Investigate: Use SLA measurements for best-quality steering
Explanation
Correct Answer
C:The symptom identifies the missing operational behavior: when a previously failed link passes the required health check, its SD-WAN route eligibility can be restored. For a medical office prioritizing stable response times to a hosted patient system, a direct diagnostic confirmation would be that the recovered member reports current successful checks and eligible routing state; during repair, restoring health does not necessarily make the recovered member the rule's first choice.
Incorrect Answers
A:The SLA target defines tolerated delay, loss, or jitter against measured health-check values, which serves the different requirement to turn observed quality metrics into a pass-or-fail objective for rule selection instead of the behavior delivered by ‘Observe recovery of a monitored member’. If that component were misconfigured, a more characteristic finding would be that probe numbers are visible but the rule cannot distinguish qualifying and nonqualifying links; the actual report concerns the ISP is repaired yet the member remains marked failed due to probe failure at a medical office prioritizing stable response times to a hosted patient system.
B:A loss target evaluates the fraction of missing probes or measured packets before declaring SLA compliance, which serves the different requirement to protect application sessions from a link that intermittently drops packets instead of the behavior delivered by ‘Observe recovery of a monitored member’. If that component were misconfigured, a more characteristic finding would be that voice quality degrades on a path with normal latency but elevated loss; the actual report concerns the ISP is repaired yet the member remains marked failed due to probe failure at a medical office prioritizing stable response times to a hosted patient system.
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 ‘Observe recovery of a monitored member’. 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 the ISP is repaired yet the member remains marked failed due to probe failure at a medical office prioritizing stable response times to a hosted patient system.
E: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 ‘Observe recovery of a monitored member’. 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 the ISP is repaired yet the member remains marked failed due to probe failure at a medical office prioritizing stable response times to a hosted patient system.
F:Best Quality uses configured quality criteria derived from a health check to prioritize the most suitable available member, which serves the different requirement to feed measured latency, jitter, or loss into a dynamic path-selection rule instead of the behavior delivered by ‘Observe recovery of a monitored member’. If that component were misconfigured, a more characteristic finding would be that a best-quality rule has no meaningful measured quality input for its preferred links; the actual report concerns the ISP is repaired yet the member remains marked failed due to probe failure at a medical office prioritizing stable response times to a hosted patient system.
Question 563
In a change-control meeting for a cloud security tenant inspecting traffic from managed remote laptops, a colleague challenges the proposed control ‘Use inline CASB HTTP header restrictions’ for the requirement to restrict which SaaS tenant a managed user may access by adjusting inspected web request headers. Which explanation accurately describes its behavior?
- A profile group bundles web, application, SSL, and other security controls for policy attachment.
- Web Filter with Inline-CASB can insert or alter supported outbound HTTP headers to enforce SaaS tenant restrictions.
- An enabled antivirus inspection component examines supported file content for malicious signatures or behavior indicators.
- Certificate inspection can evaluate visible TLS metadata but does not expose encrypted HTTP payload contents.
Explanation
Correct Answer
B:‘Use inline CASB HTTP header restrictions’ is used to restrict which SaaS tenant a managed user may access by adjusting inspected web request headers in a cloud security tenant inspecting traffic from managed remote laptops; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that outgoing SaaS requests contain the configured tenant-restriction header under the inline policy; the rollout must also respect this constraint: The SaaS provider must support the header convention and the request must be inspectable.
Incorrect Answers
A:The described behavior is part of ‘Create a security profile group’, used to apply a consistent set of inspection components to selected allowed SASE traffic policies instead of the role of ‘Use inline CASB HTTP header restrictions’. In contrast to ‘Create a security profile group’, ‘Use inline CASB HTTP header restrictions’ follows a different mechanism: Web Filter with Inline-CASB can insert or alter supported outbound HTTP headers to enforce SaaS tenant restrictions. Treating ‘Create a security profile group’ as equivalent would not address staff can sign into unapproved personal SaaS tenants despite being allowed the business SaaS domain in a cloud security tenant inspecting traffic from managed remote laptops.
C:The described behavior is part of ‘Apply an antivirus profile to allowed traffic’, used to detect malware payloads passing through a permitted cloud access policy instead of the role of ‘Use inline CASB HTTP header restrictions’. In contrast to ‘Apply an antivirus profile to allowed traffic’, ‘Use inline CASB HTTP header restrictions’ follows a different mechanism: Web Filter with Inline-CASB can insert or alter supported outbound HTTP headers to enforce SaaS tenant restrictions. Treating ‘Apply an antivirus profile to allowed traffic’ as equivalent would not address staff can sign into unapproved personal SaaS tenants despite being allowed the business SaaS domain in a cloud security tenant inspecting traffic from managed remote laptops.
D:The described behavior is part of ‘Use certificate inspection for metadata-only TLS checks’, used to inspect certificate-related connection metadata without decrypting application bodies instead of the role of ‘Use inline CASB HTTP header restrictions’. In contrast to ‘Use certificate inspection for metadata-only TLS checks’, ‘Use inline CASB HTTP header restrictions’ follows a different mechanism: Web Filter with Inline-CASB can insert or alter supported outbound HTTP headers to enforce SaaS tenant restrictions. Treating ‘Use certificate inspection for metadata-only TLS checks’ as equivalent would not address staff can sign into unapproved personal SaaS tenants despite being allowed the business SaaS domain in a cloud security tenant inspecting traffic from managed remote laptops.
Question 564
During an authorized lab exercise for a video collaboration office using two simultaneously healthy circuits, the acceptance criteria require the team to steer a well-defined TCP service without affecting unrelated traffic to the same server. Which control meets that requirement?
- Restrict the candidate member preference list
- Match service protocol and port
- Use Best Quality with latency
- Match destination address in an SD-WAN rule
Explanation
Correct Answer
B:Service matching narrows selection by transport protocol and destination-port criteria; that scope directly serves the goal to steer a well-defined TCP service without affecting unrelated traffic to the same server in a video collaboration office using two simultaneously healthy circuits. During implementation, port matching cannot reliably distinguish applications that share or change ports rather than treating the configuration label as proof of working service.
Incorrect Answers
A:An explicit member or zone preference limits which eligible paths a matching service may choose, a mechanism intended to prevent a sensitive service from using an otherwise healthy but unapproved ISP rather than the requested ‘Match service protocol and port’ control. The stated task instead is to steer a well-defined TCP service without affecting unrelated traffic to the same server, and adjusting ‘Restrict the candidate member preference list’ would not deliver ‘Match service protocol and port’. For the ‘Restrict the candidate member preference list’ alternative to ‘Match service protocol and port’, service candidate filtering does not replace destination access control and encryption requirements.
C:Best Quality can rank member quality using latency collected by the designated performance health check, a mechanism intended to prefer the lowest-delay usable path for an interactive application rather than the requested ‘Match service protocol and port’ control. The stated task instead is to steer a well-defined TCP service without affecting unrelated traffic to the same server, and adjusting ‘Use Best Quality with latency’ would not deliver ‘Match service protocol and port’. For the ‘Use Best Quality with latency’ alternative to ‘Match service protocol and port’, latency-based ranking does not ensure the lowest commercial ISP bill.
D:Destination-address matching distinguishes route candidates for a specified network target, a mechanism intended to direct traffic to a particular partner subnet over an overlay while other traffic uses internet DIA rather than the requested ‘Match service protocol and port’ control. The stated task instead is to steer a well-defined TCP service without affecting unrelated traffic to the same server, and adjusting ‘Match destination address in an SD-WAN rule’ would not deliver ‘Match service protocol and port’. For the ‘Match destination address in an SD-WAN rule’ alternative to ‘Match service protocol and port’, a matching SD-WAN rule still needs a viable route to the partner prefix.
Question 565
During an authorized lab exercise for a security team classifying devices by their current local protection state, the acceptance criteria require the team to apply a stricter posture and connection configuration to a high-risk user population. Which control meets that requirement?
- Check endpoint vulnerability severity
- Validate fresh endpoint posture telemetry
- Use endpoint-profile assignment for managed groups
- Use a certificate-based posture check
Explanation
Correct Answer
C:Endpoint profile assignment determines which device-side checks and tunnel behavior a managed group receives; that scope directly serves the goal to apply a stricter posture and connection configuration to a high-risk user population in a security team classifying devices by their current local protection state. During implementation, a cloud traffic policy alone does not deploy settings to FortiClient endpoints rather than treating the configuration label as proof of working service.
Incorrect Answers
A:Vulnerability-related posture information can be used to classify a risky endpoint for conditional access, a mechanism intended to apply stricter access to devices with high-severity unresolved vulnerabilities rather than the requested ‘Use endpoint-profile assignment for managed groups’ control. The stated task instead is to apply a stricter posture and connection configuration to a high-risk user population, and adjusting ‘Check endpoint vulnerability severity’ would not deliver ‘Use endpoint-profile assignment for managed groups’. For the ‘Check endpoint vulnerability severity’ alternative to ‘Use endpoint-profile assignment for managed groups’, posture signals require recent endpoint scanning and successful telemetry exchange.
B:Posture-based enforcement depends on updated FortiClient registration and local security-condition evaluation, a mechanism intended to avoid relying on stale compliance information after an endpoint stops reporting to management rather than the requested ‘Use endpoint-profile assignment for managed groups’ control. The stated task instead is to apply a stricter posture and connection configuration to a high-risk user population, and adjusting ‘Validate fresh endpoint posture telemetry’ would not deliver ‘Use endpoint-profile assignment for managed groups’. For the ‘Validate fresh endpoint posture telemetry’ alternative to ‘Use endpoint-profile assignment for managed groups’, identity login success should not be treated as proof of ongoing endpoint compliance.
D:Endpoint tagging can evaluate the presence and properties of a required client certificate, a mechanism intended to identify managed endpoints that carry an enterprise-issued device credential rather than the requested ‘Use endpoint-profile assignment for managed groups’ control. The stated task instead is to apply a stricter posture and connection configuration to a high-risk user population, and adjusting ‘Use a certificate-based posture check’ would not deliver ‘Use endpoint-profile assignment for managed groups’. For the ‘Use a certificate-based posture check’ alternative to ‘Use endpoint-profile assignment for managed groups’, certificate lifecycle and private-key protection matter separately from user authentication.
Question 566
Within a policy owner protecting HTTPS web sessions without blocking business use, the operator applies the control ‘Distinguish SIA from SSA policy intent’ as part of an effort to apply general internet threat protection separately from SaaS-specific data and tenant controls. Which operating behavior should the team expect?
- A profile group bundles web, application, SSL, and other security controls for policy attachment.
- Application Control overrides provide a more specific action than a broad application-category setting.
- SIA focuses on internet-bound security inspection while SSA adds cloud-application controls such as inline CASB or DLP.
- An enabled antivirus inspection component examines supported file content for malicious signatures or behavior indicators.
- API-connected CASB can examine supported SaaS tenant content and events without requiring every action to cross the inline proxy.
Explanation
Correct Answer
C:‘Distinguish SIA from SSA policy intent’ is used to apply general internet threat protection separately from SaaS-specific data and tenant controls in a policy owner protecting HTTPS web sessions without blocking business use; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that the design enforces both baseline web protection and SaaS-specific application policy; the rollout must also respect this constraint: An internet security tunnel does not by itself supply every application-specific SaaS control.
Incorrect Answers
A:The described behavior is part of ‘Create a security profile group’, used to apply a consistent set of inspection components to selected allowed SASE traffic policies instead of the role of ‘Distinguish SIA from SSA policy intent’. In contrast to ‘Create a security profile group’, ‘Distinguish SIA from SSA policy intent’ follows a different mechanism: SIA focuses on internet-bound security inspection while SSA adds cloud-application controls such as inline CASB or DLP. Treating ‘Create a security profile group’ as equivalent would not address a SaaS tenant restriction is expected from generic internet path steering alone in a policy owner protecting HTTPS web sessions without blocking business use.
B:The described behavior is part of ‘Use application category overrides’, used to deny one high-risk application within an otherwise permitted collaboration category instead of the role of ‘Distinguish SIA from SSA policy intent’. In contrast to ‘Use application category overrides’, ‘Distinguish SIA from SSA policy intent’ follows a different mechanism: SIA focuses on internet-bound security inspection while SSA adds cloud-application controls such as inline CASB or DLP. Treating ‘Use application category overrides’ as equivalent would not address a SaaS tenant restriction is expected from generic internet path steering alone in a policy owner protecting HTTPS web sessions without blocking business use.
D:The described behavior is part of ‘Apply an antivirus profile to allowed traffic’, used to detect malware payloads passing through a permitted cloud access policy instead of the role of ‘Distinguish SIA from SSA policy intent’. In contrast to ‘Apply an antivirus profile to allowed traffic’, ‘Distinguish SIA from SSA policy intent’ follows a different mechanism: SIA focuses on internet-bound security inspection while SSA adds cloud-application controls such as inline CASB or DLP. Treating ‘Apply an antivirus profile to allowed traffic’ as equivalent would not address a SaaS tenant restriction is expected from generic internet path steering alone in a policy owner protecting HTTPS web sessions without blocking business use.
E:The described behavior is part of ‘Use cloud API CASB for SaaS data at rest’, used to inspect cloud-service data through supported SaaS APIs rather than only inline user sessions instead of the role of ‘Distinguish SIA from SSA policy intent’. In contrast to ‘Use cloud API CASB for SaaS data at rest’, ‘Distinguish SIA from SSA policy intent’ follows a different mechanism: SIA focuses on internet-bound security inspection while SSA adds cloud-application controls such as inline CASB or DLP. Treating ‘Use cloud API CASB for SaaS data at rest’ as equivalent would not address a SaaS tenant restriction is expected from generic internet path steering alone in a policy owner protecting HTTPS web sessions without blocking business use.
Question 567
At a dual-ISP FortiGate with BGP-learned routes to private sites, the change board is evaluating ‘Use split routing for private and internet destinations’. Which technical consideration must be built into the plan?
- Protect tunnel-control reachability from routing recursion into the same tunnel.
- Routing adjacency and accepted prefix policies must be healthy independently of tunnel state.
- ECMP eligibility does not itself define an application-aware SD-WAN service strategy.
- Firewall policies must authorize both traffic classes with suitable inspection.
Explanation
Correct Answer
D:This condition matters for ‘Use split routing for private and internet destinations’ because destination-specific private routes and a general internet default route allow distinct traffic paths. Omitting the relevant safeguard can produce internet sessions hairpin to the data center despite a planned local-breakout design; a successful test at a dual-ISP FortiGate with BGP-learned routes to private sites would instead demonstrate that private prefixes resolve to overlays while public prefixes use an approved DIA path.
Incorrect Answers
A:The condition is associated with ‘Keep underlay route for tunnel peer’, a mechanism used to preserve transport reachability to an IPsec hub before private overlay traffic is steered instead of ‘Use split routing for private and internet destinations’, because an overlay tunnel requires the public peer endpoint to remain reachable through an underlay path. For ‘Use split routing for private and internet destinations’, unlike ‘Keep underlay route for tunnel peer’, the characteristic failure would be internet sessions hairpin to the data center despite a planned local-breakout design, which this alternative prerequisite would not directly address at a dual-ISP FortiGate with BGP-learned routes to private sites.
B:The condition is associated with ‘Use a BGP learned private prefix’, a mechanism used to obtain branch or data-center destinations without maintaining individual manual static routes instead of ‘Use split routing for private and internet destinations’, because BGP can advertise and learn remote private networks over supported routed overlays. For ‘Use split routing for private and internet destinations’, unlike ‘Use a BGP learned private prefix’, the characteristic failure would be internet sessions hairpin to the data center despite a planned local-breakout design, which this alternative prerequisite would not directly address at a dual-ISP FortiGate with BGP-learned routes to private sites.
C:The condition is associated with ‘Use ECMP-compatible route candidates’, a mechanism used to make multiple eligible equal-cost paths available for subsequent SD-WAN decisions instead of ‘Use split routing for private and internet destinations’, because equal Cost Multi-Path allows compatible routes to coexist as candidates when distance and priority permit. For ‘Use split routing for private and internet destinations’, unlike ‘Use ECMP-compatible route candidates’, the characteristic failure would be internet sessions hairpin to the data center despite a planned local-breakout design, which this alternative prerequisite would not directly address at a dual-ISP FortiGate with BGP-learned routes to private sites.
Question 568
For a dispersed workforce that uses a corporate SAML identity provider, before relying on ‘Configure SAML single sign-on’ to let staff authenticate to FortiSASE through the corporate identity provider, what prerequisite or operational limitation must be checked?
- Proxy SSO often depends on compatible deep inspection and IdP reachability.
- The client browser must reach the IdP and the SP metadata and certificates must agree.
- Configure the correct shared secret and reachable authentication service endpoints.
- The device must be supported and permitted to run FortiClient.
Explanation
Correct Answer
B:This condition matters for ‘Configure SAML single sign-on’ because FortiSASE acts as a SAML service provider while the configured IdP issues assertions for authenticated users. Omitting the relevant safeguard can produce redirect-based identity login cannot complete because the SP and IdP trust are not aligned; a successful test at a dispersed workforce that uses a corporate SAML identity provider would instead demonstrate that a user authenticates at the IdP and returns with an accepted SAML assertion.
Incorrect Answers
A:The condition is associated with ‘Configure agentless proxy SSO’, a mechanism used to associate proxied browser traffic with enterprise user identity during secure web gateway inspection instead of ‘Configure SAML single sign-on’, because sWG SSO authenticates a web proxy session using the configured identity provider. For ‘Configure SAML single sign-on’, unlike ‘Configure agentless proxy SSO’, the characteristic failure would be redirect-based identity login cannot complete because the SP and IdP trust are not aligned, which this alternative prerequisite would not directly address at a dispersed workforce that uses a corporate SAML identity provider.
C:The condition is associated with ‘Configure RADIUS authentication’, a mechanism used to authenticate managed remote agents against a reachable RADIUS infrastructure instead of ‘Configure SAML single sign-on’, because RADIUS integration delegates user authentication to a configured authentication server. For ‘Configure SAML single sign-on’, unlike ‘Configure RADIUS authentication’, the characteristic failure would be redirect-based identity login cannot complete because the SP and IdP trust are not aligned, which this alternative prerequisite would not directly address at a dispersed workforce that uses a corporate SAML identity provider.
D:The condition is associated with ‘Use preconfigured FortiClient installers’, a mechanism used to enroll a small pilot group with minimal manual agent configuration instead of ‘Configure SAML single sign-on’, because the FortiSASE onboarding flow can provide prepared FortiClient installers that users install on their devices. For ‘Configure SAML single sign-on’, unlike ‘Use preconfigured FortiClient installers’, the characteristic failure would be redirect-based identity login cannot complete because the SP and IdP trust are not aligned, which this alternative prerequisite would not directly address at a dispersed workforce that uses a corporate SAML identity provider.
Question 569
During an authorized lab exercise for a hub-and-spoke network with internet breakout and private IPsec overlays, the incident notes state that a destination has a correct static route but a separate steering or policy route sends it elsewhere. Which change is most relevant to this symptom?
- Investigate: Validate policy routing and SD-WAN interaction
- Investigate: Use a route-based IPsec overlay
- Investigate: Keep underlay route for tunnel peer
- Investigate: Review route priority
Explanation
Correct Answer
A:The symptom identifies the missing operational behavior: policy route and SD-WAN service rules can influence forwarding decisions beyond basic destination-table lookup. For a hub-and-spoke network with internet breakout and private IPsec overlays, a direct diagnostic confirmation would be that policy-route diagnostics and the matched service show the actual selection chain; during repair, review configured policy-routing precedence before rewriting otherwise correct static routes.
Incorrect Answers
B:Route-based IPsec exposes a logical tunnel interface that routing and SD-WAN can reference, which serves the different requirement to carry private routed traffic as a selectable interface-based tunnel path instead of the behavior delivered by ‘Validate policy routing and SD-WAN interaction’. If that component were misconfigured, a more characteristic finding would be that a private service rule expects an interface but only policy-based VPN selectors exist; the actual report concerns a destination has a correct static route but a separate steering or policy route sends it elsewhere at a hub-and-spoke network with internet breakout and private IPsec overlays.
C:An overlay tunnel requires the public peer endpoint to remain reachable through an underlay path, which serves the different requirement to preserve transport reachability to an IPsec hub before private overlay traffic is steered instead of the behavior delivered by ‘Validate policy routing and SD-WAN interaction’. If that component were misconfigured, a more characteristic finding would be that the VPN repeatedly drops when the route to its public peer recursively follows the overlay itself; the actual report concerns a destination has a correct static route but a separate steering or policy route sends it elsewhere at a hub-and-spoke network with internet breakout and private IPsec overlays.
D: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 ‘Validate policy routing and SD-WAN interaction’. 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 a destination has a correct static route but a separate steering or policy route sends it elsewhere at a hub-and-spoke network with internet breakout and private IPsec overlays.
Question 570
At a branch outage review comparing session entries and SLA histories, a support engineer needs to verify that ‘Inspect member health-check output’ is active for the goal to explain why a link was removed from service despite remaining physically up. Which observation is decisive?
- The relevant health-check record identifies the failed metric or probe state.
- The timeline connects health deterioration with the observed member transition.
- A traffic log contains the controlled flow's policy match, interface, and disposition.
- The service diagnostic lists the active selected member and alternate eligible candidates.
Explanation
Correct Answer
A:This checks ‘Inspect member health-check output’ at the correct operational boundary: health-check diagnostics expose alive state, loss, latency, jitter, and SLA qualification. It demonstrates the specific capability to explain why a link was removed from service despite remaining physically up in a branch outage review comparing session entries and SLA histories; deployment should additionally respect the constraint: Correlate the event to the health-check target and time of the complaint.
Incorrect Answers
B:That observation belongs to ‘Correlate a failover event with SLA history’, not ‘Inspect member health-check output’; its purpose is to differentiate an ISP performance event from a later manual service-rule edit, the underlying behavior is that time-aligned SLA logs and service events can show when a member failed and traffic was redirected. The reviewer is instead verifying ‘Inspect member health-check output’ for a branch outage review comparing session entries and SLA histories, not the evidence produced by ‘Correlate a failover event with SLA history’.
C:That observation belongs to ‘Review a matched firewall traffic log’, not ‘Inspect member health-check output’; its purpose is to trace a user's source, destination, policy ID, session, and egress interface, the underlying behavior is that traffic logs supply session-level context needed to correlate SD-WAN steering with firewall authorization. The reviewer is instead verifying ‘Inspect member health-check output’ for a branch outage review comparing session entries and SLA histories, not the evidence produced by ‘Review a matched firewall traffic log’.
D:That observation belongs to ‘Inspect selected member in service diagnostics’, not ‘Inspect member health-check output’; its purpose is to establish which egress candidate an SD-WAN service is actively using, the underlying behavior is that SD-WAN service diagnostics show selected members, eligibility, and rule selection behavior. The reviewer is instead verifying ‘Inspect member health-check output’ for a branch outage review comparing session entries and SLA histories, not the evidence produced by ‘Inspect selected member in service diagnostics’.