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.
Question 651
For a policy owner protecting HTTPS web sessions without blocking business use, a review of the current state finds that a SaaS tenant restriction is expected from generic internet path steering alone. Which configuration area most directly addresses this?
- Investigate: Use application category overrides
- Investigate: Distinguish SIA from SSA policy intent
- Investigate: Use DNS filtering
- Investigate: Configure data loss prevention patterns
Explanation
Correct Answer
B:The symptom identifies the missing operational behavior: SIA focuses on internet-bound security inspection while SSA adds cloud-application controls such as inline CASB or DLP. For a policy owner protecting HTTPS web sessions without blocking business use, a direct diagnostic confirmation would be that the design enforces both baseline web protection and SaaS-specific application policy; during repair, an internet security tunnel does not by itself supply every application-specific SaaS control.
Incorrect Answers
A:Application Control overrides provide a more specific action than a broad application-category setting, which serves the different requirement to deny one high-risk application within an otherwise permitted collaboration category instead of the behavior delivered by ‘Distinguish SIA from SSA policy intent’. If that component were misconfigured, a more characteristic finding would be that a collaboration category is allowed and one explicitly banned application still runs; the actual report concerns a SaaS tenant restriction is expected from generic internet path steering alone at a policy owner protecting HTTPS web sessions without blocking business use.
C:DNS Filter evaluates domain lookup activity before a client establishes a normal destination session, which serves the different requirement to stop requests to known malicious or restricted domains at the DNS layer instead of the behavior delivered by ‘Distinguish SIA from SSA policy intent’. If that component were misconfigured, a more characteristic finding would be that clients resolve domains known to be malicious even before the associated web connection starts; the actual report concerns a SaaS tenant restriction is expected from generic internet path steering alone at a policy owner protecting HTTPS web sessions without blocking business use.
D:DLP examines supported inspected content for configured sensitive-data patterns and applies an action, which serves the different requirement to stop sensitive strings from leaving through permitted web or SaaS uploads instead of the behavior delivered by ‘Distinguish SIA from SSA policy intent’. If that component were misconfigured, a more characteristic finding would be that an approved SaaS service accepts uploads containing explicitly restricted account identifiers; the actual report concerns a SaaS tenant restriction is expected from generic internet path steering alone at a policy owner protecting HTTPS web sessions without blocking business use.
Question 652
During an authorized lab exercise for an industrial branch sending payroll traffic to a data-center application, the deployment standard specifies the control ‘Review administrative distance’ to choose between competing routes learned from different sources for the same prefix. Which functional description matches it?
- Policy route and SD-WAN service rules can influence forwarding decisions beyond basic destination-table lookup.
- Bidirectional reachability requires the remote hub or server-side router to return traffic to the client prefix.
- Route-based IPsec exposes a logical tunnel interface that routing and SD-WAN can reference.
- Administrative distance influences which equal-prefix route source is preferred for installation.
Explanation
Correct Answer
D:‘Review administrative distance’ is used 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; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that the expected route has the winning administrative distance for its destination; the rollout must also respect this constraint: Specificity is considered before comparing administrative distance on different prefix lengths.
Incorrect Answers
A:The described behavior is part of ‘Validate policy routing and SD-WAN interaction’, used to identify why a matching policy-route decision changes normal egress selection instead of the role of ‘Review administrative distance’. In contrast to ‘Validate policy routing and SD-WAN interaction’, ‘Review administrative distance’ follows a different mechanism: administrative distance influences which equal-prefix route source is preferred for installation. Treating ‘Validate policy routing and SD-WAN interaction’ as equivalent would not address a backup static route remains installed ahead of an intended learned route due to distance in an industrial branch sending payroll traffic to a data-center application.
B:The described behavior is part of ‘Confirm return route for remote private access’, used to repair one-way traffic where forward packets reach the data center but replies do not instead of the role of ‘Review administrative distance’. In contrast to ‘Confirm return route for remote private access’, ‘Review administrative distance’ follows a different mechanism: administrative distance influences which equal-prefix route source is preferred for installation. Treating ‘Confirm return route for remote private access’ as equivalent would not address a backup static route remains installed ahead of an intended learned route due to distance in an industrial branch sending payroll traffic to a data-center application.
C:The described behavior is part of ‘Use a route-based IPsec overlay’, used to carry private routed traffic as a selectable interface-based tunnel path instead of the role of ‘Review administrative distance’. In contrast to ‘Use a route-based IPsec overlay’, ‘Review administrative distance’ follows a different mechanism: administrative distance influences which equal-prefix route source is preferred for installation. Treating ‘Use a route-based IPsec overlay’ as equivalent would not address a backup static route remains installed ahead of an intended learned route due to distance in an industrial branch sending payroll traffic to a data-center application.
Question 653
For a campus running FortiOS 7.6 with application-aware policies, a maintenance plan requires the firewall team to explain why the first newly observed app session may not match application-based steering immediately. Which choice is appropriate?
- Use an SLA target within an SD-WAN service rule
- Use an implicit SD-WAN rule as fallback
- Consider first-flow application recognition
- Match a source subnet in an SD-WAN rule
Explanation
Correct Answer
C:FortiOS learns application signatures and destination tuples from inspected sessions for subsequent application-based matches; that scope directly serves the goal to explain why the first newly observed app session may not match application-based steering immediately in a campus running FortiOS 7.6 with application-aware policies. During implementation, do not assume every first encrypted connection is identified before its initial path is chosen rather than treating the configuration label as proof of working service.
Incorrect Answers
A:Associating a service rule with an SLA target filters or prioritizes measured candidates based on the rule's strategy, a mechanism intended to select a path only after it meets the performance objective for that particular application rather than the requested ‘Consider first-flow application recognition’ control. The stated task instead is to explain why the first newly observed app session may not match application-based steering immediately, and adjusting ‘Use an SLA target within an SD-WAN service rule’ would not deliver ‘Consider first-flow application recognition’. For the ‘Use an SLA target within an SD-WAN service rule’ alternative to ‘Consider first-flow application recognition’, a health check without a service rule association may not control this application's steering.
B:The implicit SD-WAN rule handles unmatched traffic using available routing and interface-priority logic, a mechanism intended to provide default path behavior when traffic does not match any explicit steering service rather than the requested ‘Consider first-flow application recognition’ control. The stated task instead is to explain why the first newly observed app session may not match application-based steering immediately, and adjusting ‘Use an implicit SD-WAN rule as fallback’ would not deliver ‘Consider first-flow application recognition’. For the ‘Use an implicit SD-WAN rule as fallback’ alternative to ‘Consider first-flow application recognition’, firewall rules can still deny these flows regardless of the implicit path decision.
D:Source-address criteria restrict SD-WAN rule matching to sessions from specified client address ranges, a mechanism intended to apply a special path selection only to traffic originating in one department network rather than the requested ‘Consider first-flow application recognition’ control. The stated task instead is to explain why the first newly observed app session may not match application-based steering immediately, and adjusting ‘Match a source subnet in an SD-WAN rule’ would not deliver ‘Consider first-flow application recognition’. For the ‘Match a source subnet in an SD-WAN rule’ alternative to ‘Consider first-flow application recognition’, source steering does not itself authenticate an individual user.
Question 654
For a policy owner protecting HTTPS web sessions without blocking business use, a review of the current state finds that clients resolve domains known to be malicious even before the associated web connection starts. Which configuration area most directly addresses this?
- Investigate: Use DNS filtering
- Investigate: Create a security profile group
- Investigate: Apply remote browser isolation for risky sites
- Investigate: Use application category overrides
Explanation
Correct Answer
A:The symptom identifies the missing operational behavior: DNS Filter evaluates domain lookup activity before a client establishes a normal destination session. For a policy owner protecting HTTPS web sessions without blocking business use, a direct diagnostic confirmation would be that DNS query logs show the configured domain-category or threat action; during repair, DNS filtering cannot inspect the contents of an already established HTTPS session.
Incorrect Answers
B:A profile group bundles web, application, SSL, and other security controls for policy attachment, which serves the different requirement to apply a consistent set of inspection components to selected allowed SASE traffic policies instead of the behavior delivered by ‘Use DNS filtering’. If that component were misconfigured, a more characteristic finding would be that individual protections exist but a matched accept policy has no intended profile association; the actual report concerns clients resolve domains known to be malicious even before the associated web connection starts at a policy owner protecting HTTPS web sessions without blocking business use.
C:Remote Browser Isolation executes supported browsing in an isolated remote context and streams a safer representation, which serves the different requirement to isolate web rendering from the endpoint when access is required to a questionable website instead of the behavior delivered by ‘Use DNS filtering’. If that component were misconfigured, a more characteristic finding would be that staff must open a risky research site without directly executing its active page content locally; the actual report concerns clients resolve domains known to be malicious even before the associated web connection starts at a policy owner protecting HTTPS web sessions without blocking business use.
D:Application Control overrides provide a more specific action than a broad application-category setting, which serves the different requirement to deny one high-risk application within an otherwise permitted collaboration category instead of the behavior delivered by ‘Use DNS filtering’. If that component were misconfigured, a more characteristic finding would be that a collaboration category is allowed and one explicitly banned application still runs; the actual report concerns clients resolve domains known to be malicious even before the associated web connection starts at a policy owner protecting HTTPS web sessions without blocking business use.
Question 655
For a private-access application that requires device trust as well as user identity, before relying on ‘Review the posture tag's allow or deny direction’ to avoid inverting the policy when a tag specifically denotes a noncompliant endpoint, what prerequisite or operational limitation must be checked?
- Product detection must match the supported platform and endpoint security configuration.
- Posture signals require recent endpoint scanning and successful telemetry exchange.
- Define whether a tag means compliant or noncompliant before using it for admission.
- The tag logic must accurately represent the actual security requirement.
Explanation
Correct Answer
C:This condition matters for ‘Review the posture tag's allow or deny direction’ because an allow-when-tagged versus deny-when-tagged action determines whether the matched posture condition grants connectivity. Omitting the relevant safeguard can produce devices labeled as risky are inadvertently allowed by an inverted preconnection action; a successful test at a private-access application that requires device trust as well as user identity would instead demonstrate that the configured action denies devices carrying the noncompliant tag.
Incorrect Answers
A:The condition is associated with ‘Require endpoint antivirus status’, a mechanism used to treat disabled or missing antimalware protection as a noncompliant device condition instead of ‘Review the posture tag's allow or deny direction’, because a posture rule can evaluate security-product presence or protection state and classify the endpoint. For ‘Review the posture tag's allow or deny direction’, unlike ‘Require endpoint antivirus status’, the characteristic failure would be devices labeled as risky are inadvertently allowed by an inverted preconnection action, which this alternative prerequisite would not directly address at a private-access application that requires device trust as well as user identity.
B:The condition is associated with ‘Check endpoint vulnerability severity’, a mechanism used to apply stricter access to devices with high-severity unresolved vulnerabilities instead of ‘Review the posture tag's allow or deny direction’, because vulnerability-related posture information can be used to classify a risky endpoint for conditional access. For ‘Review the posture tag's allow or deny direction’, unlike ‘Check endpoint vulnerability severity’, the characteristic failure would be devices labeled as risky are inadvertently allowed by an inverted preconnection action, which this alternative prerequisite would not directly address at a private-access application that requires device trust as well as user identity.
D:The condition is associated with ‘Build a security posture tag rule’, a mechanism used to label endpoints dynamically when a specified local security condition is met instead of ‘Review the posture tag's allow or deny direction’, because FortiClient evaluates defined endpoint posture conditions and associates matching endpoints with security tags. For ‘Review the posture tag's allow or deny direction’, unlike ‘Build a security posture tag rule’, the characteristic failure would be devices labeled as risky are inadvertently allowed by an inverted preconnection action, which this alternative prerequisite would not directly address at a private-access application that requires device trust as well as user identity.
Question 656
At a regional hub where live transport measurements do not agree with the user complaint, the rollout includes the control ‘Configure an SLA target for a health check’ to turn observed quality metrics into a pass-or-fail objective for rule selection. Which observed mechanism is consistent with this configuration?
- The SLA target defines tolerated delay, loss, or jitter against measured health-check values.
- Passive measurements can obtain link metrics from observed traffic instead of relying solely on synthetic monitoring packets.
- Targets tighter than achievable WAN conditions can cause otherwise connected members to fail policy qualification.
- An SD-WAN health check monitors the configured member interfaces instead of automatically representing every interface.
Explanation
Correct Answer
A:‘Configure an SLA target for a health check’ is used to turn observed quality metrics into a pass-or-fail objective for rule selection 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 health-check's target reports individual member pass or failure against stated limits; the rollout must also respect this constraint: Measurement alone and selecting a traffic-steering target are different steps.
Incorrect Answers
B:The described behavior is part of ‘Use passive WAN health measurement’, used to derive quality observations from actual matched user sessions rather than dedicated probes instead of the role of ‘Configure an SLA target for a health check’. In contrast to ‘Use passive WAN health measurement’, ‘Configure an SLA target for a health check’ follows a different mechanism: the SLA target defines tolerated delay, loss, or jitter against measured health-check values. Treating ‘Use passive WAN health measurement’ as equivalent would not address probe numbers are visible but the rule cannot distinguish qualifying and nonqualifying links in a regional hub where live transport measurements do not agree with the user complaint.
C:The described behavior is part of ‘Avoid overly strict SLA targets’, used to prevent both usable circuits from being excluded by unrealistic quality limits instead of the role of ‘Configure an SLA target for a health check’. In contrast to ‘Avoid overly strict SLA targets’, ‘Configure an SLA target for a health check’ follows a different mechanism: the SLA target defines tolerated delay, loss, or jitter against measured health-check values. Treating ‘Avoid overly strict SLA targets’ as equivalent would not address probe numbers are visible but the rule cannot distinguish qualifying and nonqualifying links in a regional hub where live transport measurements do not agree with the user complaint.
D: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 ‘Configure an SLA target for a health check’. In contrast to ‘Assign the relevant member set to a health check’, ‘Configure an SLA target for a health check’ follows a different mechanism: the SLA target defines tolerated delay, loss, or jitter against measured health-check values. Treating ‘Assign the relevant member set to a health check’ as equivalent would not address probe numbers are visible but the rule cannot distinguish qualifying and nonqualifying links in a regional hub where live transport measurements do not agree with the user complaint.
Question 657
At a regulated company administering SASE policies for several employee groups, a support engineer needs to verify that ‘Configure SASE certificate trust’ is active for the goal to avoid TLS warnings and ensure clients trust the cloud security inspection certificate. Which observation is decisive?
- Location-aware policy evaluation blocks the disallowed source geography.
- The matching access policy permits the intended group and references its inspection profile group.
- Managed endpoints trust the proper CA and inspected sites validate normally.
- Test flows and logs show the new intended policy match and enforcement action.
Explanation
Correct Answer
C:This checks ‘Configure SASE certificate trust’ at the correct operational boundary: when deep inspection is used, managed endpoints need the appropriate inspection CA trust anchor. It demonstrates the specific capability to avoid TLS warnings and ensure clients trust the cloud security inspection certificate in a regulated company administering SASE policies for several employee groups; deployment should additionally respect the constraint: Certificate deployment must be coordinated with inspection and endpoint management.
Incorrect Answers
A:That observation belongs to ‘Use geolocation-aware access restrictions’, not ‘Configure SASE certificate trust’; 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 ‘Configure SASE certificate trust’ for a regulated company administering SASE policies for several employee groups, not the evidence produced by ‘Use geolocation-aware access restrictions’.
B:That observation belongs to ‘Configure a SASE allow policy’, not ‘Configure SASE certificate trust’; its purpose is to permit approved user traffic before applying cloud-delivered inspection profiles, the underlying behavior is that FortiSASE traffic policies determine which user or destination flows are accepted or denied and which security-profile groups apply. The reviewer is instead verifying ‘Configure SASE certificate trust’ for a regulated company administering SASE policies for several employee groups, not the evidence produced by ‘Configure a SASE allow policy’.
D:That observation belongs to ‘Manage policy change verification’, not ‘Configure SASE certificate trust’; its purpose is to confirm a modified SASE security policy is active before concluding a remediation is complete, the underlying behavior is that policy edits require verification of the selected rule, security profiles, and resulting traffic logs. The reviewer is instead verifying ‘Configure SASE certificate trust’ for a regulated company administering SASE policies for several employee groups, not the evidence produced by ‘Manage policy change verification’.
Question 658
In a change-control meeting for a company enrolling remote Windows and macOS employees into FortiSASE, a colleague challenges the proposed control ‘Configure agentless proxy SSO’ for the requirement to associate proxied browser traffic with enterprise user identity during secure web gateway inspection. Which explanation accurately describes its behavior?
- SWG SSO authenticates a web proxy session using the configured identity provider.
- Agentless secure web gateway access uses explicit proxy steering rather than a full-device agent tunnel.
- A PAC-based proxy configuration tells supported browsers which web requests should use the cloud proxy.
- The Onboard Users workflow provides information that remote users use for FortiSASE client registration.
Explanation
Correct Answer
A:‘Configure agentless proxy SSO’ is used to associate proxied browser traffic with enterprise user identity during secure web gateway inspection in a company enrolling remote Windows and macOS employees into FortiSASE; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that a controlled browser request establishes an SSO user session for the cloud proxy; the rollout must also respect this constraint: Proxy SSO often depends on compatible deep inspection and IdP reachability.
Incorrect Answers
B:The described behavior is part of ‘Enroll an agentless web user’, used to protect an unmanaged Chromebook's HTTP and HTTPS browsing without installing FortiClient instead of the role of ‘Configure agentless proxy SSO’. In contrast to ‘Enroll an agentless web user’, ‘Configure agentless proxy SSO’ follows a different mechanism: sWG SSO authenticates a web proxy session using the configured identity provider. Treating ‘Enroll an agentless web user’ as equivalent would not address proxy requests arrive but user-based policies cannot associate them with an authenticated identity in a company enrolling remote Windows and macOS employees into FortiSASE.
C:The described behavior is part of ‘Distribute proxy autoconfiguration settings’, used to direct selected browser destinations to the FortiSASE secure web gateway instead of the role of ‘Configure agentless proxy SSO’. In contrast to ‘Distribute proxy autoconfiguration settings’, ‘Configure agentless proxy SSO’ follows a different mechanism: sWG SSO authenticates a web proxy session using the configured identity provider. Treating ‘Distribute proxy autoconfiguration settings’ as equivalent would not address proxy requests arrive but user-based policies cannot associate them with an authenticated identity in a company enrolling remote Windows and macOS employees into FortiSASE.
D:The described behavior is part of ‘Distribute a FortiSASE invitation code’, used to bind an invited remote user's FortiClient enrollment to the correct organization instead of the role of ‘Configure agentless proxy SSO’. In contrast to ‘Distribute a FortiSASE invitation code’, ‘Configure agentless proxy SSO’ follows a different mechanism: sWG SSO authenticates a web proxy session using the configured identity provider. Treating ‘Distribute a FortiSASE invitation code’ as equivalent would not address proxy requests arrive but user-based policies cannot associate them with an authenticated identity in a company enrolling remote Windows and macOS employees into FortiSASE.
Question 659
Within a hub-and-spoke network with internet breakout and private IPsec overlays, the team wants to avoid an ineffective configuration of ‘Prefer a more specific prefix’. Which consideration deserves attention?
- Priority has meaning within the relevant route-selection context, not across unrelated prefixes.
- A route's presence alone does not establish next-hop liveness.
- SD-WAN application preference cannot create missing reachability to an internal network.
- A route must exist before the steering choice can forward a matching session.
- Tunnel security negotiation and return routing still need separate validation.
Explanation
Correct Answer
C:This condition matters for ‘Prefer a more specific prefix’ because longest-prefix match chooses a more specific valid destination route ahead of a broader default. Omitting the relevant safeguard can produce partner traffic exits public internet despite a required private-subnet route being missing; a successful test at a hub-and-spoke network with internet breakout and private IPsec overlays would instead demonstrate that the routing table has a valid longer-prefix route to the partner CIDR.
Incorrect Answers
A:The condition is associated with ‘Review route priority’, a mechanism used to resolve preference among otherwise comparable FortiGate route candidates instead of ‘Prefer a more specific prefix’, because route priority can provide an additional selection differentiator when distance and prefix do not distinguish alternatives. For ‘Prefer a more specific prefix’, unlike ‘Review route priority’, the characteristic failure would be partner traffic exits public internet despite a required private-subnet route being missing, which this alternative prerequisite would not directly address at a hub-and-spoke network with internet breakout and private IPsec overlays.
B:The condition is associated with ‘Check the route's next hop reachability’, a mechanism used to differentiate a configured route from an actually usable gateway on a WAN link instead of ‘Prefer a more specific prefix’, because forwarding requires that the selected next hop can be resolved and reached via the member. For ‘Prefer a more specific prefix’, unlike ‘Check the route's next hop reachability’, the characteristic failure would be partner traffic exits public internet despite a required private-subnet route being missing, which this alternative prerequisite would not directly address at a hub-and-spoke network with internet breakout and private IPsec overlays.
D:The condition is associated with ‘Install default route through an SD-WAN zone’, a mechanism used to make general internet destinations reachable without listing every WAN member as a separate policy interface instead of ‘Prefer a more specific prefix’, because a zone-based default static route gives SD-WAN a routing candidate for nonlocal destinations. For ‘Prefer a more specific prefix’, unlike ‘Install default route through an SD-WAN zone’, the characteristic failure would be partner traffic exits public internet despite a required private-subnet route being missing, which this alternative prerequisite would not directly address at a hub-and-spoke network with internet breakout and private IPsec overlays.
E:The condition is associated with ‘Use a route-based IPsec overlay’, a mechanism used to carry private routed traffic as a selectable interface-based tunnel path instead of ‘Prefer a more specific prefix’, because route-based IPsec exposes a logical tunnel interface that routing and SD-WAN can reference. For ‘Prefer a more specific prefix’, unlike ‘Use a route-based IPsec overlay’, the characteristic failure would be partner traffic exits public internet despite a required private-subnet route being missing, which this alternative prerequisite would not directly address at a hub-and-spoke network with internet breakout and private IPsec overlays.
Question 660
At a logistics site where routing and SD-WAN services have separate responsibilities, a controlled test reveals that a named conferencing application is not recognized when steering is configured only by port. Which setting is the strongest first lead?
- Investigate: Test rule matching with service diagnostics
- Investigate: Match an Internet Service Database destination
- Investigate: Match by detected application
- Investigate: Specify an SD-WAN zone preference
Explanation
Correct Answer
C:The symptom identifies the missing operational behavior: application-based SD-WAN rules use application detection information to identify supported traffic signatures. For a logistics site where routing and SD-WAN services have separate responsibilities, a direct diagnostic confirmation would be that the application-based service criterion matches a previously recognized application flow; during repair, Application Control must be enabled in the matching firewall policy for identification-based steering.
Incorrect Answers
A:SD-WAN service diagnostics expose matched rules, interface lists, modes, and selected member status, which serves the different requirement to identify which SD-WAN rule and candidate member were chosen for a particular session instead of the behavior delivered by ‘Match by detected application’. If that component were misconfigured, a more characteristic finding would be that a flow takes an unexpected path but the rule and member ordering are unknown; the actual report concerns a named conferencing application is not recognized when steering is configured only by port at a logistics site where routing and SD-WAN services have separate responsibilities.
B:Internet service matching can steer flows associated with a known internet service without manually maintaining every destination subnet, which serves the different requirement to identify cloud-service traffic by maintained service definitions instead of a static destination IP instead of the behavior delivered by ‘Match by detected application’. If that component were misconfigured, a more characteristic finding would be that a SaaS provider changes IP addresses and a hardcoded address-match rule misses new endpoints; the actual report concerns a named conferencing application is not recognized when steering is configured only by port at a logistics site where routing and SD-WAN services have separate responsibilities.
D:An SD-WAN rule can prefer particular SD-WAN zones instead of enumerating every interface member, which serves the different requirement to restrict an application to members grouped within a chosen logical zone instead of the behavior delivered by ‘Match by detected application’. If that component were misconfigured, a more characteristic finding would be that a private-app rule keeps considering internet underlay members that are in the wrong zone; the actual report concerns a named conferencing application is not recognized when steering is configured only by port at a logistics site where routing and SD-WAN services have separate responsibilities.