Question 670
At an insurance branch with a real-time application and a bulk-backup workload, the change request is to ensure a narrow high-priority policy wins instead of a catch-all service rule. Which configuration is the most direct fit?
- Order specific SD-WAN rules above general matches
- Use DSCP-based SD-WAN steering
- Match an Internet Service Database destination
- Test rule matching with service diagnostics
Explanation
Correct Answer
A:SD-WAN service rules are evaluated in configured order, so earlier matching entries can take precedence; that scope directly serves the goal to ensure a narrow high-priority policy wins instead of a catch-all service rule in an insurance branch with a real-time application and a bulk-backup workload. During implementation, a highly specific match below a catch-all does not automatically outrank it rather than treating the configuration label as proof of working service.
Incorrect Answers
B:DSCP match criteria can steer traffic carrying designated IP-header service markings, a mechanism intended to distinguish preclassified media packets from ordinary web traffic at path-selection time rather than the requested ‘Order specific SD-WAN rules above general matches’ control. The stated task instead is to ensure a narrow high-priority policy wins instead of a catch-all service rule, and adjusting ‘Use DSCP-based SD-WAN steering’ would not deliver ‘Order specific SD-WAN rules above general matches’. For the ‘Use DSCP-based SD-WAN steering’ alternative to ‘Order specific SD-WAN rules above general matches’, trust and policing of DSCP markings require an appropriate network policy design.
C:Internet service matching can steer flows associated with a known internet service without manually maintaining every destination subnet, a mechanism intended to identify cloud-service traffic by maintained service definitions instead of a static destination IP rather than the requested ‘Order specific SD-WAN rules above general matches’ control. The stated task instead is to ensure a narrow high-priority policy wins instead of a catch-all service rule, and adjusting ‘Match an Internet Service Database destination’ would not deliver ‘Order specific SD-WAN rules above general matches’. For the ‘Match an Internet Service Database destination’ alternative to ‘Order specific SD-WAN rules above general matches’, an ISDB object is not the same as a local DNS record or the name of a user group.
D:SD-WAN service diagnostics expose matched rules, interface lists, modes, and selected member status, a mechanism intended to identify which SD-WAN rule and candidate member were chosen for a particular session rather than the requested ‘Order specific SD-WAN rules above general matches’ control. The stated task instead is to ensure a narrow high-priority policy wins instead of a catch-all service rule, and adjusting ‘Test rule matching with service diagnostics’ would not deliver ‘Order specific SD-WAN rules above general matches’. For the ‘Test rule matching with service diagnostics’ alternative to ‘Order specific SD-WAN rules above general matches’, inspect rule match and routing context together before changing quality thresholds.
Question 671
In a change-control meeting for a dispersed workforce that uses a corporate SAML identity provider, a design review calls for a way to preserve endpoint identification and posture exchange for protected access. What should the operator configure?
- Configure RADIUS authentication
- Maintain FortiClient tenant registration
- Configure SAML single sign-on
- Use preconfigured FortiClient installers
Explanation
Correct Answer
B:Registered FortiClient maintains connectivity with FortiSASE endpoint management and supplies identity or posture data; that scope directly serves the goal to preserve endpoint identification and posture exchange for protected access in a dispersed workforce that uses a corporate SAML identity provider. During implementation, ZTNA decisions may depend on fresh registration and endpoint state rather than treating the configuration label as proof of working service.
Incorrect Answers
A:RADIUS integration delegates user authentication to a configured authentication server, a mechanism intended to authenticate managed remote agents against a reachable RADIUS infrastructure rather than the requested ‘Maintain FortiClient tenant registration’ control. The stated task instead is to preserve endpoint identification and posture exchange for protected access, and adjusting ‘Configure RADIUS authentication’ would not deliver ‘Maintain FortiClient tenant registration’. For the ‘Configure RADIUS authentication’ alternative to ‘Maintain FortiClient tenant registration’, configure the correct shared secret and reachable authentication service endpoints.
C:FortiSASE acts as a SAML service provider while the configured IdP issues assertions for authenticated users, a mechanism intended to let staff authenticate to FortiSASE through the corporate identity provider rather than the requested ‘Maintain FortiClient tenant registration’ control. The stated task instead is to preserve endpoint identification and posture exchange for protected access, and adjusting ‘Configure SAML single sign-on’ would not deliver ‘Maintain FortiClient tenant registration’. For the ‘Configure SAML single sign-on’ alternative to ‘Maintain FortiClient tenant registration’, the client browser must reach the IdP and the SP metadata and certificates must agree.
D:The FortiSASE onboarding flow can provide prepared FortiClient installers that users install on their devices, a mechanism intended to enroll a small pilot group with minimal manual agent configuration rather than the requested ‘Maintain FortiClient tenant registration’ control. The stated task instead is to preserve endpoint identification and posture exchange for protected access, and adjusting ‘Use preconfigured FortiClient installers’ would not deliver ‘Maintain FortiClient tenant registration’. For the ‘Use preconfigured FortiClient installers’ alternative to ‘Maintain FortiClient tenant registration’, the device must be supported and permitted to run FortiClient.
Question 672
During an authorized lab exercise for a small campus moving from single-WAN routing to resilient FortiGate SD-WAN, the acceptance criteria require the team to keep ISP transports and IPsec private overlays independently selectable in policy. Which control meets that requirement?
- Set a static WAN member gateway
- Separate underlay and overlay SD-WAN zones
- Install an SD-WAN default route
- Use DHCP-provided WAN gateway
Explanation
Correct Answer
B:Distinct SD-WAN zones make underlay internet circuits and overlay tunnels separate logical choices; that scope directly serves the goal to keep ISP transports and IPsec private overlays independently selectable in policy in a small campus moving from single-WAN routing to resilient FortiGate SD-WAN. During implementation, create the correct member-to-zone mapping before using zones in rules rather than treating the configuration label as proof of working service.
Incorrect Answers
A:A statically addressed SD-WAN member must use the reachable ISP next hop for proper packet forwarding, a mechanism intended to reach an ISP next hop on a manually numbered uplink rather than the requested ‘Separate underlay and overlay SD-WAN zones’ control. The stated task instead is to keep ISP transports and IPsec private overlays independently selectable in policy, and adjusting ‘Set a static WAN member gateway’ would not deliver ‘Separate underlay and overlay SD-WAN zones’. For the ‘Set a static WAN member gateway’ alternative to ‘Separate underlay and overlay SD-WAN zones’, verify the next hop is reachable on the configured interface subnet.
C:A default static route whose outgoing interface is the SD-WAN zone supplies route reachability before path steering, a mechanism intended to provide a route for internet-bound traffic through the SD-WAN aggregate rather than the requested ‘Separate underlay and overlay SD-WAN zones’ control. The stated task instead is to keep ISP transports and IPsec private overlays independently selectable in policy, and adjusting ‘Install an SD-WAN default route’ would not deliver ‘Separate underlay and overlay SD-WAN zones’. For the ‘Install an SD-WAN default route’ alternative to ‘Separate underlay and overlay SD-WAN zones’, an SD-WAN rule does not itself replace the need for a valid route.
D:An SD-WAN member on a DHCP WAN can inherit the gateway learned from the DHCP interface, a mechanism intended to keep a dynamically assigned ISP next hop aligned with lease changes rather than the requested ‘Separate underlay and overlay SD-WAN zones’ control. The stated task instead is to keep ISP transports and IPsec private overlays independently selectable in policy, and adjusting ‘Use DHCP-provided WAN gateway’ would not deliver ‘Separate underlay and overlay SD-WAN zones’. For the ‘Use DHCP-provided WAN gateway’ alternative to ‘Separate underlay and overlay SD-WAN zones’, a DHCP-derived gateway should not be confused with the SD-WAN zone route itself.
Question 673
Within a firewall analyst comparing egress logs with service configuration, the administrator must examine IPv4 SD-WAN rule selection rather than a generic interface status page without redesigning unrelated services. Which option addresses the goal?
- Inspect SD-WAN rule hit counters
- Investigate first-session application identification
- Distinguish dropped from forwarded session outcome
- Correlate a failover event with SLA history
- Use SD-WAN service4 diagnostics
Explanation
Correct Answer
E:The service4 diagnostic command exposes IPv4 rule modes, matched criteria, and selected candidates; that scope directly serves the goal to examine IPv4 SD-WAN rule selection rather than a generic interface status page in a firewall analyst comparing egress logs with service configuration. During implementation, use the IPv6-specific counterpart when investigating IPv6 service steering rather than treating the configuration label as proof of working service.
Incorrect Answers
A:Service rule counters and diagnostics help confirm which policy actually handles observed traffic, a mechanism intended to determine whether sessions are matching the intended service rule before editing path priorities rather than the requested ‘Use SD-WAN service4 diagnostics’ control. The stated task instead is to examine IPv4 SD-WAN rule selection rather than a generic interface status page, and adjusting ‘Inspect SD-WAN rule hit counters’ would not deliver ‘Use SD-WAN service4 diagnostics’. For the ‘Inspect SD-WAN rule hit counters’ alternative to ‘Use SD-WAN service4 diagnostics’, no rule hits often indicates an earlier match or unmatched traffic rather than faulty member quality.
B:Application-detection learning can populate an app-specific destination tuple after the initial inspected connection, a mechanism intended to trace why a newly seen application uses a generic rule before subsequent sessions match its signature rather than the requested ‘Use SD-WAN service4 diagnostics’ control. The stated task instead is to examine IPv4 SD-WAN rule selection rather than a generic interface status page, and adjusting ‘Investigate first-session application identification’ would not deliver ‘Use SD-WAN service4 diagnostics’. For the ‘Investigate first-session application identification’ alternative to ‘Use SD-WAN service4 diagnostics’, Application Control visibility is a prerequisite for this style of app-based rule.
C:A deny disposition in the traffic log is an authorization result, not evidence of performance-based steering failure, a mechanism intended to decide whether a firewall policy denied traffic or SD-WAN simply chose an unexpected path rather than the requested ‘Use SD-WAN service4 diagnostics’ control. The stated task instead is to examine IPv4 SD-WAN rule selection rather than a generic interface status page, and adjusting ‘Distinguish dropped from forwarded session outcome’ would not deliver ‘Use SD-WAN service4 diagnostics’. For the ‘Distinguish dropped from forwarded session outcome’ alternative to ‘Use SD-WAN service4 diagnostics’, investigate authorization before tuning member cost or jitter targets.
D:Time-aligned SLA logs and service events can show when a member failed and traffic was redirected, a mechanism intended to differentiate an ISP performance event from a later manual service-rule edit rather than the requested ‘Use SD-WAN service4 diagnostics’ control. The stated task instead is to examine IPv4 SD-WAN rule selection rather than a generic interface status page, and adjusting ‘Correlate a failover event with SLA history’ would not deliver ‘Use SD-WAN service4 diagnostics’. For the ‘Correlate a failover event with SLA history’ alternative to ‘Use SD-WAN service4 diagnostics’, current settings alone cannot demonstrate the historical trigger for failover.
Question 674
At an operations hub with differentiated perimeter policies for WAN members, a controlled test reveals that the provider's tagged circuit is up at layer two but no logical tagged WAN is selectable. Which setting is the strongest first lead?
- Investigate: Move a member between zones
- Investigate: Use a VLAN interface as a member
- Investigate: Use a physical interface as a member
- Investigate: Use an aggregate interface as a member
Explanation
Correct Answer
B:The symptom identifies the missing operational behavior: an SD-WAN member may reference a VLAN interface rather than only an untagged physical port. For an operations hub with differentiated perimeter policies for WAN members, a direct diagnostic confirmation would be that the correct VLAN subinterface appears as an SD-WAN member; during repair, the VLAN identifier and upstream trunk must agree before health checks can succeed.
Incorrect Answers
A:Reassigning the member to a different zone changes its logical policy and rule membership, which serves the different requirement to change how one interface is referenced by routes and policies without rebuilding the WAN port instead of the behavior delivered by ‘Use a VLAN interface as a member’. If that component were misconfigured, a more characteristic finding would be that the port works but is reachable only through policies for the old zone; the actual report concerns the provider's tagged circuit is up at layer two but no logical tagged WAN is selectable at an operations hub with differentiated perimeter policies for WAN members.
C:Physical WAN ports can act as members with their own connectivity, next hops, costs, and measured health, which serves the different requirement to bring a directly connected broadband circuit under SD-WAN decisions instead of the behavior delivered by ‘Use a VLAN interface as a member’. If that component were misconfigured, a more characteristic finding would be that the carrier port exists but no SD-WAN service can select it; the actual report concerns the provider's tagged circuit is up at layer two but no logical tagged WAN is selectable at an operations hub with differentiated perimeter policies for WAN members.
D:A link aggregation interface can be an SD-WAN member while LAG distributes frames across its constituent ports, which serves the different requirement to treat an LAG upstream handoff as a selectable SD-WAN transport instead of the behavior delivered by ‘Use a VLAN interface as a member’. If that component were misconfigured, a more characteristic finding would be that the administrator adds member ports separately although they belong to one provider LAG; the actual report concerns the provider's tagged circuit is up at layer two but no logical tagged WAN is selectable at an operations hub with differentiated perimeter policies for WAN members.
Question 675
During an authorized lab exercise for a campus running FortiOS 7.6 with application-aware policies, a pilot is about to enable ‘Use DSCP-based SD-WAN steering’. Which precaution is most closely tied to this choice?
- A health check without a service rule association may not control this application's steering.
- Service candidate filtering does not replace destination access control and encryption requirements.
- Trust and policing of DSCP markings require an appropriate network policy design.
- A matching SD-WAN rule still needs a viable route to the partner prefix.
Explanation
Correct Answer
C:This condition matters for ‘Use DSCP-based SD-WAN steering’ because dSCP match criteria can steer traffic carrying designated IP-header service markings. Omitting the relevant safeguard can produce voice packets bearing priority markings share the generic internet selection rule; a successful test at a campus running FortiOS 7.6 with application-aware policies would instead demonstrate that the matched service specifies the corresponding DSCP codepoint and steers marked packets.
Incorrect Answers
A:The condition is associated with ‘Use an SLA target within an SD-WAN service rule’, a mechanism used to select a path only after it meets the performance objective for that particular application instead of ‘Use DSCP-based SD-WAN steering’, because associating a service rule with an SLA target filters or prioritizes measured candidates based on the rule's strategy. For ‘Use DSCP-based SD-WAN steering’, unlike ‘Use an SLA target within an SD-WAN service rule’, the characteristic failure would be voice packets bearing priority markings share the generic internet selection rule, which this alternative prerequisite would not directly address at a campus running FortiOS 7.6 with application-aware policies.
B:The condition is associated with ‘Restrict the candidate member preference list’, a mechanism used to prevent a sensitive service from using an otherwise healthy but unapproved ISP instead of ‘Use DSCP-based SD-WAN steering’, because an explicit member or zone preference limits which eligible paths a matching service may choose. For ‘Use DSCP-based SD-WAN steering’, unlike ‘Restrict the candidate member preference list’, the characteristic failure would be voice packets bearing priority markings share the generic internet selection rule, which this alternative prerequisite would not directly address at a campus running FortiOS 7.6 with application-aware policies.
D:The condition is associated with ‘Match destination address in an SD-WAN rule’, a mechanism used to direct traffic to a particular partner subnet over an overlay while other traffic uses internet DIA instead of ‘Use DSCP-based SD-WAN steering’, because destination-address matching distinguishes route candidates for a specified network target. For ‘Use DSCP-based SD-WAN steering’, unlike ‘Match destination address in an SD-WAN rule’, the characteristic failure would be voice packets bearing priority markings share the generic internet selection rule, which this alternative prerequisite would not directly address at a campus running FortiOS 7.6 with application-aware policies.
Question 676
For a security team classifying devices by their current local protection state, a review of the current state finds that users stop a mandatory protection process yet retain the previous trust classification. Which configuration area most directly addresses this?
- Investigate: Check endpoint vulnerability severity
- Investigate: Use endpoint-profile assignment for managed groups
- Investigate: Check a required running process
- Investigate: Assign compliant endpoint tags to private policies
Explanation
Correct Answer
C:The symptom identifies the missing operational behavior: process-presence conditions can contribute to device posture evaluation where supported. For a security team classifying devices by their current local protection state, a direct diagnostic confirmation would be that the posture rule changes endpoint classification when the process stops or resumes; during repair, a process name alone is weaker than cryptographic proof of application integrity.
Incorrect Answers
A:Vulnerability-related posture information can be used to classify a risky endpoint for conditional access, which serves the different requirement to apply stricter access to devices with high-severity unresolved vulnerabilities instead of the behavior delivered by ‘Check a required running process’. If that component were misconfigured, a more characteristic finding would be that a workstation with a critical unremediated issue continues receiving full sensitive-app access; the actual report concerns users stop a mandatory protection process yet retain the previous trust classification at a security team classifying devices by their current local protection state.
B:Endpoint profile assignment determines which device-side checks and tunnel behavior a managed group receives, which serves the different requirement to apply a stricter posture and connection configuration to a high-risk user population instead of the behavior delivered by ‘Check a required running process’. If that component were misconfigured, a more characteristic finding would be that contractor devices use the default endpoint configuration rather than the intended restricted policy; the actual report concerns users stop a mandatory protection process yet retain the previous trust classification at a security team classifying devices by their current local protection state.
D:Private access policies can use security posture tags as dynamic matching criteria, which serves the different requirement to grant sensitive private access only to managed devices meeting specified security conditions instead of the behavior delivered by ‘Check a required running process’. If that component were misconfigured, a more characteristic finding would be that a valid user's unmanaged laptop reaches a restricted private service despite failing device requirements; the actual report concerns users stop a mandatory protection process yet retain the previous trust classification at a security team classifying devices by their current local protection state.
Question 677
Within a security manager comparing weekly incident and traffic trends, after the rollout, operators find that the help desk cannot determine whether collaboration usage or software updates caused an increase. Where should they focus troubleshooting?
- Investigate: Trend security events by category
- Investigate: Use report time filters for incident scoping
- Investigate: Correlate policy action with destination risk
- Investigate: Compare user traffic volume trends
- Investigate: Review application usage reports
Explanation
Correct Answer
E:The symptom identifies the missing operational behavior: application analytics classify observed traffic into recognizable applications for reporting. For a security manager comparing weekly incident and traffic trends, a direct diagnostic confirmation would be that the report breaks down application categories and their traffic share for the period; during repair, app recognition depends on available inspection and classification signals.
Incorrect Answers
A:Security reporting aggregates action and threat categories so changes can be compared across time, which serves the different requirement to measure whether a newly deployed protection reduced observed prohibited activity instead of the behavior delivered by ‘Review application usage reports’. If that component were misconfigured, a more characteristic finding would be that operators compare total traffic only and miss a rise in blocked high-risk web requests; the actual report concerns the help desk cannot determine whether collaboration usage or software updates caused an increase at a security manager comparing weekly incident and traffic trends.
B:Time-bound analytics separate incident-period activity from unrelated historical traffic, which serves the different requirement to limit an investigation to the period in which an employee reported a cloud access failure instead of the behavior delivered by ‘Review application usage reports’. If that component were misconfigured, a more characteristic finding would be that a current report mixes last month's normal sessions with a 15-minute outage window; the actual report concerns the help desk cannot determine whether collaboration usage or software updates caused an increase at a security manager comparing weekly incident and traffic trends.
C:Security analytics can group blocked traffic by destination or policy to reveal recurring patterns, which serves the different requirement to identify repeated attempts to reach restricted destinations across remote users instead of the behavior delivered by ‘Review application usage reports’. If that component were misconfigured, a more characteristic finding would be that a burst of denials is reported without knowing whether one bad domain or many sites were involved; the actual report concerns the help desk cannot determine whether collaboration usage or software updates caused an increase at a security manager comparing weekly incident and traffic trends.
D:User traffic analytics aggregate bytes and sessions by identity and time for usage investigation, which serves the different requirement to find which authenticated population caused a sustained increase in cloud egress instead of the behavior delivered by ‘Review application usage reports’. If that component were misconfigured, a more characteristic finding would be that an ISP usage spike is blamed on anonymous traffic without identifying the active user groups; the actual report concerns the help desk cannot determine whether collaboration usage or software updates caused an increase at a security manager comparing weekly incident and traffic trends.
Question 678
For a small campus moving from single-WAN routing to resilient FortiGate SD-WAN, a review of the current state finds that an internal application policy unintentionally steers directly to a public ISP underlay. Which configuration area most directly addresses this?
- Investigate: Separate underlay and overlay SD-WAN zones
- Investigate: Set a static WAN member gateway
- Investigate: Use DHCP-provided WAN gateway
- Investigate: Allow LAN-to-SD-WAN firewall policy
Explanation
Correct Answer
A:The symptom identifies the missing operational behavior: distinct SD-WAN zones make underlay internet circuits and overlay tunnels separate logical choices. For a small campus moving from single-WAN routing to resilient FortiGate SD-WAN, a direct diagnostic confirmation would be that firewall and service policies distinguish transport and private-overlay zones; during repair, create the correct member-to-zone mapping before using zones in rules.
Incorrect Answers
B:A statically addressed SD-WAN member must use the reachable ISP next hop for proper packet forwarding, which serves the different requirement to reach an ISP next hop on a manually numbered uplink instead of the behavior delivered by ‘Separate underlay and overlay SD-WAN zones’. If that component were misconfigured, a more characteristic finding would be that the link shows carrier but packets are sent toward an incorrect next-hop address; the actual report concerns an internal application policy unintentionally steers directly to a public ISP underlay at a small campus moving from single-WAN routing to resilient FortiGate SD-WAN.
C:An SD-WAN member on a DHCP WAN can inherit the gateway learned from the DHCP interface, which serves the different requirement to keep a dynamically assigned ISP next hop aligned with lease changes instead of the behavior delivered by ‘Separate underlay and overlay SD-WAN zones’. If that component were misconfigured, a more characteristic finding would be that the dynamic WAN lease renews but a hard-coded obsolete gateway is still being used; the actual report concerns an internal application policy unintentionally steers directly to a public ISP underlay at a small campus moving from single-WAN routing to resilient FortiGate SD-WAN.
D:The stateful firewall policy permits internal-to-zone sessions and can apply source NAT and inspection as required, which serves the different requirement to authorize office clients to reach external destinations over eligible SD-WAN members instead of the behavior delivered by ‘Separate underlay and overlay SD-WAN zones’. If that component were misconfigured, a more characteristic finding would be that an eligible WAN path exists but LAN clients match no accept firewall policy; the actual report concerns an internal application policy unintentionally steers directly to a public ISP underlay at a small campus moving from single-WAN routing to resilient FortiGate SD-WAN.
Question 679
For a regulated company administering SASE policies for several employee groups, before relying on ‘Verify FortiSASE service provisioning’ to confirm the cloud security service is available before distributing client configurations, what prerequisite or operational limitation must be checked?
- Enrollment cannot compensate for an unprovisioned security service or absent entitlement.
- Certificate deployment must be coordinated with inspection and endpoint management.
- A security profile does not independently override a deny access policy.
- Validation should use an authorized test identity and representative destination.
Explanation
Correct Answer
A:This condition matters for ‘Verify FortiSASE service provisioning’ because FortiSASE must have an active provisioned instance with security points of presence before managed users can use its cloud enforcement. Omitting the relevant safeguard can produce installation invitations are sent while the tenant has no functioning security PoP resources; a successful test at a regulated company administering SASE policies for several employee groups would instead demonstrate that the tenant dashboard reports provisioned cloud enforcement capacity and accessible administration.
Incorrect Answers
B:The condition is associated with ‘Configure SASE certificate trust’, a mechanism used to avoid TLS warnings and ensure clients trust the cloud security inspection certificate instead of ‘Verify FortiSASE service provisioning’, because when deep inspection is used, managed endpoints need the appropriate inspection CA trust anchor. For ‘Verify FortiSASE service provisioning’, unlike ‘Configure SASE certificate trust’, the characteristic failure would be installation invitations are sent while the tenant has no functioning security PoP resources, which this alternative prerequisite would not directly address at a regulated company administering SASE policies for several employee groups.
C:The condition is associated with ‘Configure a SASE allow policy’, a mechanism used to permit approved user traffic before applying cloud-delivered inspection profiles instead of ‘Verify FortiSASE service provisioning’, because FortiSASE traffic policies determine which user or destination flows are accepted or denied and which security-profile groups apply. For ‘Verify FortiSASE service provisioning’, unlike ‘Configure a SASE allow policy’, the characteristic failure would be installation invitations are sent while the tenant has no functioning security PoP resources, which this alternative prerequisite would not directly address at a regulated company administering SASE policies for several employee groups.
D:The condition is associated with ‘Manage policy change verification’, a mechanism used to confirm a modified SASE security policy is active before concluding a remediation is complete instead of ‘Verify FortiSASE service provisioning’, because policy edits require verification of the selected rule, security profiles, and resulting traffic logs. For ‘Verify FortiSASE service provisioning’, unlike ‘Manage policy change verification’, the characteristic failure would be installation invitations are sent while the tenant has no functioning security PoP resources, which this alternative prerequisite would not directly address at a regulated company administering SASE policies for several employee groups.
Question 680
In a change-control meeting for an insurance branch with a real-time application and a bulk-backup workload, a colleague challenges the proposed control ‘Order specific SD-WAN rules above general matches’ for the requirement to ensure a narrow high-priority policy wins instead of a catch-all service rule. Which explanation accurately describes its behavior?
- SD-WAN service rules are evaluated in configured order, so earlier matching entries can take precedence.
- An SD-WAN rule can prefer particular SD-WAN zones instead of enumerating every interface member.
- Session state and configured failover behavior affect when path changes apply; newly created flows are evaluated against current steering.
- SD-WAN service diagnostics expose matched rules, interface lists, modes, and selected member status.
Explanation
Correct Answer
A:‘Order specific SD-WAN rules above general matches’ is used to ensure a narrow high-priority policy wins instead of a catch-all service rule in an insurance branch with a real-time application and a bulk-backup workload; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that the narrow rule appears ahead of the broad rule and receives matching hits; the rollout must also respect this constraint: A highly specific match below a catch-all does not automatically outrank it.
Incorrect Answers
B:The described behavior is part of ‘Specify an SD-WAN zone preference’, used to restrict an application to members grouped within a chosen logical zone instead of the role of ‘Order specific SD-WAN rules above general matches’. In contrast to ‘Specify an SD-WAN zone preference’, ‘Order specific SD-WAN rules above general matches’ follows a different mechanism: SD-WAN service rules are evaluated in configured order, so earlier matching entries can take precedence. Treating ‘Specify an SD-WAN zone preference’ as equivalent would not address a broad any-destination rule captures sessions meant for the later finance-specific rule in an insurance branch with a real-time application and a bulk-backup workload.
C:The described behavior is part of ‘Treat existing sessions differently from new flows’, used to troubleshoot a session that remains associated with an earlier selection after an SD-WAN change instead of the role of ‘Order specific SD-WAN rules above general matches’. In contrast to ‘Treat existing sessions differently from new flows’, ‘Order specific SD-WAN rules above general matches’ follows a different mechanism: SD-WAN service rules are evaluated in configured order, so earlier matching entries can take precedence. Treating ‘Treat existing sessions differently from new flows’ as equivalent would not address a broad any-destination rule captures sessions meant for the later finance-specific rule in an insurance branch with a real-time application and a bulk-backup workload.
D:The described behavior is part of ‘Test rule matching with service diagnostics’, used to identify which SD-WAN rule and candidate member were chosen for a particular session instead of the role of ‘Order specific SD-WAN rules above general matches’. In contrast to ‘Test rule matching with service diagnostics’, ‘Order specific SD-WAN rules above general matches’ follows a different mechanism: SD-WAN service rules are evaluated in configured order, so earlier matching entries can take precedence. Treating ‘Test rule matching with service diagnostics’ as equivalent would not address a broad any-destination rule captures sessions meant for the later finance-specific rule in an insurance branch with a real-time application and a bulk-backup workload.