Question 640
During an authorized lab exercise for a help desk investigating a short cloud access degradation, the acceptance criteria require the team to measure whether a newly deployed protection reduced observed prohibited activity. Which control meets that requirement?
- Review application usage reports
- Compare user traffic volume trends
- Trend security events by category
- Use report time filters for incident scoping
Explanation
Correct Answer
C:Security reporting aggregates action and threat categories so changes can be compared across time; that scope directly serves the goal to measure whether a newly deployed protection reduced observed prohibited activity in a help desk investigating a short cloud access degradation. During implementation, changes in log policy or user population must be considered before claiming a causal improvement rather than treating the configuration label as proof of working service.
Incorrect Answers
A: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 ‘Trend security events by category’ control. The stated task instead is to measure whether a newly deployed protection reduced observed prohibited activity, and adjusting ‘Review application usage reports’ would not deliver ‘Trend security events by category’. For the ‘Review application usage reports’ alternative to ‘Trend security events by category’, app recognition depends on available inspection and classification signals.
B:User traffic analytics aggregate bytes and sessions by identity and time for usage investigation, a mechanism intended to find which authenticated population caused a sustained increase in cloud egress rather than the requested ‘Trend security events by category’ control. The stated task instead is to measure whether a newly deployed protection reduced observed prohibited activity, and adjusting ‘Compare user traffic volume trends’ would not deliver ‘Trend security events by category’. For the ‘Compare user traffic volume trends’ alternative to ‘Trend security events by category’, traffic volume alone is not evidence that a session is malicious.
D: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 ‘Trend security events by category’ control. The stated task instead is to measure whether a newly deployed protection reduced observed prohibited activity, and adjusting ‘Use report time filters for incident scoping’ would not deliver ‘Trend security events by category’. For the ‘Use report time filters for incident scoping’ alternative to ‘Trend security events by category’, correlate device and timezone timestamps before drawing incident chronology conclusions.
Question 641
At a logistics site where routing and SD-WAN services have separate responsibilities, the team will implement ‘Use a manual SD-WAN strategy’ to pin a specific business application to a preferred transport independent of dynamic quality ranking. Select THREE statements that accurately describe this control's mechanism, deployment consideration, and validating evidence. Choose THREE.
- Manual member preference remains subject to route availability and any needed firewall permission.
- Zone preference and routing reachability must point to compatible paths.
- The Manual strategy respects an administrator-specified interface preference list of eligible SD-WAN members.
- Application-based SD-WAN rules use application detection information to identify supported traffic signatures.
- The traffic session matches both the path-selection rule and an enabled permit policy.
- The matching service displays Manual mode and the chosen ordered member list.
Explanation
Correct Answers
A:This safeguard applies to ‘Use a manual SD-WAN strategy’, which works because the Manual strategy respects an administrator-specified interface preference list of eligible SD-WAN members. Without the correct deployment condition, operators may see that office backup traffic follows an undesired member despite a fixed circuit preference requirement in a logistics site where routing and SD-WAN services have separate responsibilities.
C:This is the mechanism behind ‘Use a manual SD-WAN strategy’ in a logistics site where routing and SD-WAN services have separate responsibilities; its objective is to pin a specific business application to a preferred transport independent of dynamic quality ranking. The deployment can be confirmed when the matching service displays Manual mode and the chosen ordered member list, subject to the boundary that manual member preference remains subject to route availability and any needed firewall permission.
F:The observation follows from the operation of ‘Use a manual SD-WAN strategy’: the Manual strategy respects an administrator-specified interface preference list of eligible SD-WAN members. It directly tests the requested ability to pin a specific business application to a preferred transport independent of dynamic quality ranking in a logistics site where routing and SD-WAN services have separate responsibilities, rather than another policy or network layer.
Incorrect Answers
B:The planning point is associated with ‘Specify an SD-WAN zone preference’, not ‘Use a manual SD-WAN strategy’; its real role is to restrict an application to members grouped within a chosen logical zone. The required deployment instead centers on ‘Use a manual SD-WAN strategy’, rather than ‘Specify an SD-WAN zone preference’; the distinct symptom to guard against is that office backup traffic follows an undesired member despite a fixed circuit preference requirement.
D:This describes ‘Match by detected application’, not the requested ‘Use a manual SD-WAN strategy’, and is meant to prefer an SD-WAN path based on application identification rather than fixed port alone. Its evidence would be that the application-based service criterion matches a previously recognized application flow, not a demonstration of ‘Use a manual SD-WAN strategy’ and its distinct outcome.
E:This result would validate ‘Separate steering from security authorization’, not ‘Use a manual SD-WAN strategy’, because SD-WAN rules determine egress path candidates; firewall policies separately allow or deny traffic. That separate implementation serves choose a fast WAN without accidentally treating SD-WAN selection as firewall access permission, whereas the audit needs evidence specifically of ‘Use a manual SD-WAN strategy’ at a logistics site where routing and SD-WAN services have separate responsibilities.
Question 642
Within a medical office prioritizing stable response times to a hosted patient system, the operator applies the control ‘Avoid overly strict SLA targets’ as part of an effort to prevent both usable circuits from being excluded by unrealistic quality limits. Which operating behavior should the team expect?
- Targets tighter than achievable WAN conditions can cause otherwise connected members to fail policy qualification.
- Separate health checks can reveal that a circuit reaches one remote service well but another poorly.
- An SD-WAN health check monitors the configured member interfaces instead of automatically representing every interface.
- Active SD-WAN health checks send periodic probes to a designated target over monitored members.
- A member may be reachable and report alive while failing a stricter SLA target for performance.
Explanation
Correct Answer
A:‘Avoid overly strict SLA targets’ is used to prevent both usable circuits from being excluded by unrealistic quality limits in a medical office prioritizing stable response times to a hosted patient system; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that measured path conditions are compared with realistic business-grade target values; the rollout must also respect this constraint: Threshold values should reflect actual application tolerances and the monitored geography.
Incorrect Answers
B: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 ‘Avoid overly strict SLA targets’. In contrast to ‘Compare health across multiple SLAs’, ‘Avoid overly strict SLA targets’ follows a different mechanism: targets tighter than achievable WAN conditions can cause otherwise connected members to fail policy qualification. Treating ‘Compare health across multiple SLAs’ as equivalent would not address all monitored links remain alive but neither meets a configured near-zero latency threshold in a medical office prioritizing stable response times to a hosted patient system.
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 ‘Avoid overly strict SLA targets’. In contrast to ‘Assign the relevant member set to a health check’, ‘Avoid overly strict SLA targets’ follows a different mechanism: targets tighter than achievable WAN conditions can cause otherwise connected members to fail policy qualification. Treating ‘Assign the relevant member set to a health check’ as equivalent would not address all monitored links remain alive but neither meets a configured near-zero latency threshold in a medical office prioritizing stable response times to a hosted patient system.
D:The described behavior is part of ‘Create an active probe health check’, used to measure reachability and delay even when no user sessions traverse a circuit instead of the role of ‘Avoid overly strict SLA targets’. In contrast to ‘Create an active probe health check’, ‘Avoid overly strict SLA targets’ follows a different mechanism: targets tighter than achievable WAN conditions can cause otherwise connected members to fail policy qualification. Treating ‘Create an active probe health check’ as equivalent would not address all monitored links remain alive but neither meets a configured near-zero latency threshold in a medical office prioritizing stable response times to a hosted patient system.
E:The described behavior is part of ‘Investigate alive versus SLA-qualified state’, used to distinguish basic connectivity from acceptable application performance instead of the role of ‘Avoid overly strict SLA targets’. In contrast to ‘Investigate alive versus SLA-qualified state’, ‘Avoid overly strict SLA targets’ follows a different mechanism: targets tighter than achievable WAN conditions can cause otherwise connected members to fail policy qualification. Treating ‘Investigate alive versus SLA-qualified state’ as equivalent would not address all monitored links remain alive but neither meets a configured near-zero latency threshold in a medical office prioritizing stable response times to a hosted patient system.
Question 643
During an authorized lab exercise for a retail hub where two ISP costs differ but application quality still matters, the deployment standard specifies the control ‘Use an implicit SD-WAN rule as fallback’ to provide default path behavior when traffic does not match any explicit steering service. Which functional description matches it?
- Best Quality supports loss-oriented link comparison using measured health data.
- Best Quality can evaluate jitter as the link-cost factor to compare delay variation.
- SD-WAN rules determine egress path candidates; firewall policies separately allow or deny traffic.
- The implicit SD-WAN rule handles unmatched traffic using available routing and interface-priority logic.
Explanation
Correct Answer
D:‘Use an implicit SD-WAN rule as fallback’ is used to provide default path behavior when traffic does not match any explicit steering service in a retail hub where two ISP costs differ but application quality still matters; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that unmatched flows follow the implicit selection rather than a nonexistent custom service; the rollout must also respect this constraint: Firewall rules can still deny these flows regardless of the implicit path decision.
Incorrect Answers
A:The described behavior is part of ‘Use Best Quality with packet loss’, used to prefer the circuit losing fewer packets for interactive services instead of the role of ‘Use an implicit SD-WAN rule as fallback’. In contrast to ‘Use Best Quality with packet loss’, ‘Use an implicit SD-WAN rule as fallback’ follows a different mechanism: the implicit SD-WAN rule handles unmatched traffic using available routing and interface-priority logic. Treating ‘Use Best Quality with packet loss’ as equivalent would not address an administrator expects unmatched sessions to be dropped solely because no custom service matched in a retail hub where two ISP costs differ but application quality still matters.
B:The described behavior is part of ‘Use Best Quality with jitter’, used to steer delay-sensitive conferencing toward the most stable path instead of the role of ‘Use an implicit SD-WAN rule as fallback’. In contrast to ‘Use Best Quality with jitter’, ‘Use an implicit SD-WAN rule as fallback’ follows a different mechanism: the implicit SD-WAN rule handles unmatched traffic using available routing and interface-priority logic. Treating ‘Use Best Quality with jitter’ as equivalent would not address an administrator expects unmatched sessions to be dropped solely because no custom service matched in a retail hub where two ISP costs differ but application quality still matters.
C:The described behavior is part of ‘Separate steering from security authorization’, used to choose a fast WAN without accidentally treating SD-WAN selection as firewall access permission instead of the role of ‘Use an implicit SD-WAN rule as fallback’. In contrast to ‘Separate steering from security authorization’, ‘Use an implicit SD-WAN rule as fallback’ follows a different mechanism: the implicit SD-WAN rule handles unmatched traffic using available routing and interface-priority logic. Treating ‘Separate steering from security authorization’ as equivalent would not address an administrator expects unmatched sessions to be dropped solely because no custom service matched in a retail hub where two ISP costs differ but application quality still matters.
Question 644
Within a test lab containing an overlay tunnel and two underlay next hops, the configuration has been applied. Which measurement or record best confirms the goal to make multiple eligible equal-cost paths available for subsequent SD-WAN decisions?
- Route and health-check diagnostics show the failed member and available alternate.
- The route view includes the intended equal-cost candidates for that prefix.
- The expected route has the winning administrative distance for its destination.
- The remote forwarding table contains a route back to the branch network.
- ARP or neighbor resolution and route lookup identify the reachable gateway.
- The target private CIDR resolves through the overlay SD-WAN zone.
Explanation
Correct Answer
B:This checks ‘Use ECMP-compatible route candidates’ at the correct operational boundary: equal Cost Multi-Path allows compatible routes to coexist as candidates when distance and priority permit. It demonstrates the specific capability to make multiple eligible equal-cost paths available for subsequent SD-WAN decisions in a test lab containing an overlay tunnel and two underlay next hops; deployment should additionally respect the constraint: ECMP eligibility does not itself define an application-aware SD-WAN service strategy.
Incorrect Answers
A:That observation belongs to ‘Inspect route withdrawal after health failure’, not ‘Use ECMP-compatible route candidates’; its purpose is to explain why a failed WAN member stops being considered for new forwarding, the underlying behavior is that SD-WAN health failure can remove a member's route from the link load-balancing candidate set. The reviewer is instead verifying ‘Use ECMP-compatible route candidates’ for a test lab containing an overlay tunnel and two underlay next hops, not the evidence produced by ‘Inspect route withdrawal after health failure’.
C:That observation belongs to ‘Review administrative distance’, not ‘Use ECMP-compatible route candidates’; its purpose is to choose between competing routes learned from different sources for the same prefix, the underlying behavior is that administrative distance influences which equal-prefix route source is preferred for installation. The reviewer is instead verifying ‘Use ECMP-compatible route candidates’ for a test lab containing an overlay tunnel and two underlay next hops, not the evidence produced by ‘Review administrative distance’.
D:That observation belongs to ‘Confirm return route for remote private access’, not ‘Use ECMP-compatible route candidates’; its purpose is to repair one-way traffic where forward packets reach the data center but replies do not, the underlying behavior is that bidirectional reachability requires the remote hub or server-side router to return traffic to the client prefix. The reviewer is instead verifying ‘Use ECMP-compatible route candidates’ for a test lab containing an overlay tunnel and two underlay next hops, not the evidence produced by ‘Confirm return route for remote private access’.
E:That observation belongs to ‘Check the route's next hop reachability’, not ‘Use ECMP-compatible route candidates’; its purpose is to differentiate a configured route from an actually usable gateway on a WAN link, the underlying behavior is that forwarding requires that the selected next hop can be resolved and reached via the member. The reviewer is instead verifying ‘Use ECMP-compatible route candidates’ for a test lab containing an overlay tunnel and two underlay next hops, not the evidence produced by ‘Check the route's next hop reachability’.
F:That observation belongs to ‘Configure a static partner route through overlay zone’, not ‘Use ECMP-compatible route candidates’; its purpose is to reach an on-premises network across an IPsec overlay SD-WAN group, the underlying behavior is that a destination-specific static route referencing the overlay zone makes private routes accessible to SD-WAN selection. The reviewer is instead verifying ‘Use ECMP-compatible route candidates’ for a test lab containing an overlay tunnel and two underlay next hops, not the evidence produced by ‘Configure a static partner route through overlay zone’.
Question 645
In a change-control meeting for an industrial branch sending payroll traffic to a data-center application, a design review calls for a way to choose between competing routes learned from different sources for the same prefix. What should the operator configure?
- Use routing diagnostics before changing SD-WAN cost
- Use ECMP-compatible route candidates
- Inspect route withdrawal after health failure
- Review administrative distance
Explanation
Correct Answer
D:Administrative distance influences which equal-prefix route source is preferred for installation; that scope directly serves the goal to choose between competing routes learned from different sources for the same prefix in an industrial branch sending payroll traffic to a data-center application. During implementation, specificity is considered before comparing administrative distance on different prefix lengths rather than treating the configuration label as proof of working service.
Incorrect Answers
A:Route inspection distinguishes absent routes from member cost or performance rankings, a mechanism intended to avoid misdiagnosing unreachable prefixes as an economic-selection problem rather than the requested ‘Review administrative distance’ control. The stated task instead is to choose between competing routes learned from different sources for the same prefix, and adjusting ‘Use routing diagnostics before changing SD-WAN cost’ would not deliver ‘Review administrative distance’. For the ‘Use routing diagnostics before changing SD-WAN cost’ alternative to ‘Review administrative distance’, cost only influences relevant strategies among candidates that are routable and eligible.
B:Equal Cost Multi-Path allows compatible routes to coexist as candidates when distance and priority permit, a mechanism intended to make multiple eligible equal-cost paths available for subsequent SD-WAN decisions rather than the requested ‘Review administrative distance’ control. The stated task instead is to choose between competing routes learned from different sources for the same prefix, and adjusting ‘Use ECMP-compatible route candidates’ would not deliver ‘Review administrative distance’. For the ‘Use ECMP-compatible route candidates’ alternative to ‘Review administrative distance’, ECMP eligibility does not itself define an application-aware SD-WAN service strategy.
C:SD-WAN health failure can remove a member's route from the link load-balancing candidate set, a mechanism intended to explain why a failed WAN member stops being considered for new forwarding rather than the requested ‘Review administrative distance’ control. The stated task instead is to choose between competing routes learned from different sources for the same prefix, and adjusting ‘Inspect route withdrawal after health failure’ would not deliver ‘Review administrative distance’. For the ‘Inspect route withdrawal after health failure’ alternative to ‘Review administrative distance’, a failed SLA state can change route eligibility without a physical link-down event.
Question 646
At a branch outage review comparing session entries and SLA histories, the team will implement ‘Inspect member health-check output’ to explain why a link was removed from service despite remaining physically up. Select THREE statements that accurately describe this control's mechanism, deployment consideration, and validating evidence. Choose THREE.
- Rule hit evidence increments for a controlled session that meets the match criteria.
- Correlate the event to the health-check target and time of the complaint.
- Logging must be enabled on the applicable policy to retain session evidence.
- Time-aligned SLA logs and service events can show when a member failed and traffic was redirected.
- The relevant health-check record identifies the failed metric or probe state.
- Health-check diagnostics expose alive state, loss, latency, jitter, and SLA qualification.
Explanation
Correct Answers
B:This safeguard applies to ‘Inspect member health-check output’, which works because health-check diagnostics expose alive state, loss, latency, jitter, and SLA qualification. Without the correct deployment condition, operators may see that the standby uplink appears up at layer one but is excluded as unhealthy in a branch outage review comparing session entries and SLA histories.
E:The observation follows from the operation of ‘Inspect member health-check output’: health-check diagnostics expose alive state, loss, latency, jitter, and SLA qualification. It directly tests the requested ability to explain why a link was removed from service despite remaining physically up in a branch outage review comparing session entries and SLA histories, rather than another policy or network layer.
F:This is the mechanism behind ‘Inspect member health-check output’ in a branch outage review comparing session entries and SLA histories; its objective is to explain why a link was removed from service despite remaining physically up. The deployment can be confirmed when the relevant health-check record identifies the failed metric or probe state, subject to the boundary that correlate the event to the health-check target and time of the complaint.
Incorrect Answers
A:This result would validate ‘Inspect SD-WAN rule hit counters’, not ‘Inspect member health-check output’, because service rule counters and diagnostics help confirm which policy actually handles observed traffic. That separate implementation serves determine whether sessions are matching the intended service rule before editing path priorities, whereas the audit needs evidence specifically of ‘Inspect member health-check output’ at a branch outage review comparing session entries and SLA histories.
C:The planning point is associated with ‘Review a matched firewall traffic log’, not ‘Inspect member health-check output’; its real role is to trace a user's source, destination, policy ID, session, and egress interface. The required deployment instead centers on ‘Inspect member health-check output’, rather than ‘Review a matched firewall traffic log’; the distinct symptom to guard against is that the standby uplink appears up at layer one but is excluded as unhealthy.
D:This describes ‘Correlate a failover event with SLA history’, not the requested ‘Inspect member health-check output’, and is meant to differentiate an ISP performance event from a later manual service-rule edit. Its evidence would be that the timeline connects health deterioration with the observed member transition, not a demonstration of ‘Inspect member health-check output’ and its distinct outcome.
Question 647
During an authorized lab exercise for a medical office prioritizing stable response times to a hosted patient system, the acceptance criteria require the team to measure reachability and delay even when no user sessions traverse a circuit. Which control meets that requirement?
- Select the correct probe server
- Use passive WAN health measurement
- Create an active probe health check
- Assign the relevant member set to a health check
Explanation
Correct Answer
C:Active SD-WAN health checks send periodic probes to a designated target over monitored members; that scope directly serves the goal to measure reachability and delay even when no user sessions traverse a circuit in a medical office prioritizing stable response times to a hosted patient system. During implementation, the target must answer the selected probe method and be reachable from those paths rather than treating the configuration label as proof of working service.
Incorrect Answers
A:Health checks against a representative reachable target include more of the application path than checks aimed only at the immediate gateway, a mechanism intended to measure user-relevant path health rather than only the nearest ISP hop rather than the requested ‘Create an active probe health check’ control. The stated task instead is to measure reachability and delay even when no user sessions traverse a circuit, and adjusting ‘Select the correct probe server’ would not deliver ‘Create an active probe health check’. For the ‘Select the correct probe server’ alternative to ‘Create an active probe health check’, the measurement endpoint must be reliably reachable and appropriate to the application.
B:Passive measurements can obtain link metrics from observed traffic instead of relying solely on synthetic monitoring packets, a mechanism intended to derive quality observations from actual matched user sessions rather than dedicated probes rather than the requested ‘Create an active probe health check’ control. The stated task instead is to measure reachability and delay even when no user sessions traverse a circuit, and adjusting ‘Use passive WAN health measurement’ would not deliver ‘Create an active probe health check’. For the ‘Use passive WAN health measurement’ alternative to ‘Create an active probe health check’, traffic and policy instrumentation must support the passive measurement mechanism.
D:An SD-WAN health check monitors the configured member interfaces instead of automatically representing every interface, a mechanism intended to compare only the transport members serving a given application class rather than the requested ‘Create an active probe health check’ control. The stated task instead is to measure reachability and delay even when no user sessions traverse a circuit, and adjusting ‘Assign the relevant member set to a health check’ would not deliver ‘Create an active probe health check’. For the ‘Assign the relevant member set to a health check’ alternative to ‘Create an active probe health check’, a measured SLA cannot evaluate a member that is not associated with the check.
Question 648
In a change-control meeting for a FortiSASE security investigation following a blocked user action, a colleague challenges the proposed control ‘Inspect DNS-filter threat events’ for the requirement to identify blocked malicious name resolution before the browser opens a TCP session. Which explanation accurately describes its behavior?
- DLP logs record content-rule matches and the action taken for an inspected transfer.
- IPS events contain the signature context and configured security response for detected traffic.
- DNS security logs record affected domain requests and configured malicious-domain actions.
- AV logs identify signature or file detections and the security action applied to a session.
Explanation
Correct Answer
C:‘Inspect DNS-filter threat events’ is used to identify blocked malicious name resolution before the browser opens a TCP session in a FortiSASE security investigation following a blocked user action; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that a filtered query event shows the domain and DNS-policy enforcement result; the rollout must also respect this constraint: DNS filtering operates at name resolution, not by scanning file payloads.
Incorrect Answers
A:The described behavior is part of ‘Inspect DLP matches’, used to explain which sensitive-content pattern caused a SaaS upload to be denied instead of the role of ‘Inspect DNS-filter threat events’. In contrast to ‘Inspect DLP matches’, ‘Inspect DNS-filter threat events’ follows a different mechanism: DNS security logs record affected domain requests and configured malicious-domain actions. Treating ‘Inspect DLP matches’ as equivalent would not address clients cannot resolve a dangerous domain while normal internet connectivity still works in a FortiSASE security investigation following a blocked user action.
B:The described behavior is part of ‘Inspect IPS threat logs’, used to verify whether an exploit signature triggered inspection rather than a generic connectivity failure instead of the role of ‘Inspect DNS-filter threat events’. In contrast to ‘Inspect IPS threat logs’, ‘Inspect DNS-filter threat events’ follows a different mechanism: DNS security logs record affected domain requests and configured malicious-domain actions. Treating ‘Inspect IPS threat logs’ as equivalent would not address clients cannot resolve a dangerous domain while normal internet connectivity still works in a FortiSASE security investigation following a blocked user action.
D:The described behavior is part of ‘Inspect antivirus detection events’, used to identify which inspected download was blocked for malware and under which policy instead of the role of ‘Inspect DNS-filter threat events’. In contrast to ‘Inspect antivirus detection events’, ‘Inspect DNS-filter threat events’ follows a different mechanism: DNS security logs record affected domain requests and configured malicious-domain actions. Treating ‘Inspect antivirus detection events’ as equivalent would not address clients cannot resolve a dangerous domain while normal internet connectivity still works in a FortiSASE security investigation following a blocked user action.
Question 649
For a branch connected to a SASE point of presence by an encrypted service path, before relying on ‘Integrate branch SD-WAN with FortiSASE on-ramp’ to send on-site user internet traffic to FortiSASE cloud inspection using a supported branch edge, what prerequisite or operational limitation must be checked?
- Routing reachability and firewall permission must both be satisfied.
- Branch integration requires transport reachability and matching on-ramp security policy.
- Choose the private-access architecture according to protocol and trust requirements.
- The alternate hub must advertise the needed application prefix to take over.
Explanation
Correct Answer
B:This condition matters for ‘Integrate branch SD-WAN with FortiSASE on-ramp’ because a supported FortiGate branch on-ramp can steer site traffic to FortiSASE enforcement PoPs. Omitting the relevant safeguard can produce the branch's WAN works locally but site users bypass the expected SASE inspection path; a successful test at a branch connected to a SASE point of presence by an encrypted service path would instead demonstrate that the branch overlay to the service is established and inspected traffic appears in SASE logs.
Incorrect Answers
A:The condition is associated with ‘Allow security PoP access to private applications’, a mechanism used to permit cloud-originated SPA traffic through the data-center firewall policy instead of ‘Integrate branch SD-WAN with FortiSASE on-ramp’, because hub-side FortiGate policies authorize FortiSASE service traffic toward the protected servers. For ‘Integrate branch SD-WAN with FortiSASE on-ramp’, unlike ‘Allow security PoP access to private applications’, the characteristic failure would be the branch's WAN works locally but site users bypass the expected SASE inspection path, which this alternative prerequisite would not directly address at a branch connected to a SASE point of presence by an encrypted service path.
C:The condition is associated with ‘Use SD-WAN private access for TCP and UDP’, a mechanism used to extend private resource connectivity beyond the TCP-focused ZTNA access proxy model instead of ‘Integrate branch SD-WAN with FortiSASE on-ramp’, because an SD-WAN-based SPA design can provide routed access to private TCP and UDP applications. For ‘Integrate branch SD-WAN with FortiSASE on-ramp’, unlike ‘Use SD-WAN private access for TCP and UDP’, the characteristic failure would be the branch's WAN works locally but site users bypass the expected SASE inspection path, which this alternative prerequisite would not directly address at a branch connected to a SASE point of presence by an encrypted service path.
D:The condition is associated with ‘Select hub path using SLA health’, a mechanism used to prefer a viable SPA route when one private-access connection becomes degraded instead of ‘Integrate branch SD-WAN with FortiSASE on-ramp’, because health and service-connection priorities can influence which reachable private hub path is preferred. For ‘Integrate branch SD-WAN with FortiSASE on-ramp’, unlike ‘Select hub path using SLA health’, the characteristic failure would be the branch's WAN works locally but site users bypass the expected SASE inspection path, which this alternative prerequisite would not directly address at a branch connected to a SASE point of presence by an encrypted service path.
Question 650
In a change-control meeting for a branch connected to a SASE point of presence by an encrypted service path, a design review calls for a way to prefer a viable SPA route when one private-access connection becomes degraded. What should the operator configure?
- Use ZTNA application proxy for a protected TCP app
- Use IPsec transport for the SASE branch connection
- Verify site-based SASE traffic steering
- Select hub path using SLA health
Explanation
Correct Answer
D:Health and service-connection priorities can influence which reachable private hub path is preferred; that scope directly serves the goal to prefer a viable SPA route when one private-access connection becomes degraded in a branch connected to a SASE point of presence by an encrypted service path. During implementation, the alternate hub must advertise the needed application prefix to take over rather than treating the configuration label as proof of working service.
Incorrect Answers
A:ZTNA private access targets authorized TCP applications rather than granting generic network reachability, a mechanism intended to publish a narrowly scoped internal TCP application through a FortiGate ZTNA gateway rather than the requested ‘Select hub path using SLA health’ control. The stated task instead is to prefer a viable SPA route when one private-access connection becomes degraded, and adjusting ‘Use ZTNA application proxy for a protected TCP app’ would not deliver ‘Select hub path using SLA health’. For the ‘Use ZTNA application proxy for a protected TCP app’ alternative to ‘Select hub path using SLA health’, the FortiGate ZTNA server, access policy, and required client posture must be configured.
B:An IPsec-based on-ramp encapsulates site traffic for cloud delivery over the public underlay, a mechanism intended to carry branch traffic securely across an untrusted ISP toward a SASE service edge rather than the requested ‘Select hub path using SLA health’ control. The stated task instead is to prefer a viable SPA route when one private-access connection becomes degraded, and adjusting ‘Use IPsec transport for the SASE branch connection’ would not deliver ‘Select hub path using SLA health’. For the ‘Use IPsec transport for the SASE branch connection’ alternative to ‘Select hub path using SLA health’, iKE negotiations and underlay routing must work before traffic steering over the tunnel.
C:Site-based on-ramp configuration determines which branch flows are forwarded into FortiSASE, a mechanism intended to differentiate local branch DIA from traffic genuinely sent to cloud enforcement rather than the requested ‘Select hub path using SLA health’ control. The stated task instead is to prefer a viable SPA route when one private-access connection becomes degraded, and adjusting ‘Verify site-based SASE traffic steering’ would not deliver ‘Select hub path using SLA health’. For the ‘Verify site-based SASE traffic steering’ alternative to ‘Select hub path using SLA health’, make the observed steering decision consistent with routing, policy, and tunnel state.