Question 270
In a change-control meeting for a remote call center measuring two ISP paths to the same application target, a colleague challenges the proposed control ‘Investigate alive versus SLA-qualified state’ for the requirement to distinguish basic connectivity from acceptable application performance. Which explanation accurately describes its behavior?
- Historical SLA samples and logs help distinguish transient degradation from a persistent member failure.
- The SLA target defines tolerated delay, loss, or jitter against measured health-check values.
- A member may be reachable and report alive while failing a stricter SLA target for performance.
- Health checks against a representative reachable target include more of the application path than checks aimed only at the immediate gateway.
Explanation
Correct Answer
C:‘Investigate alive versus SLA-qualified state’ is used to distinguish basic connectivity from acceptable application performance in a remote call center measuring two ISP paths to the same application target; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that the health data shows alive status yet a failed SLA for the same member; the rollout must also respect this constraint: Do not equate successful probes with meeting every target threshold.
Incorrect Answers
A:The described behavior is part of ‘Review SLA historical changes’, used to establish whether a brief performance decline coincides with a reported outage instead of the role of ‘Investigate alive versus SLA-qualified state’. In contrast to ‘Review SLA historical changes’, ‘Investigate alive versus SLA-qualified state’ follows a different mechanism: a member may be reachable and report alive while failing a stricter SLA target for performance. Treating ‘Review SLA historical changes’ as equivalent would not address an interface is alive in health-check output but excluded from a latency-sensitive rule in a remote call center measuring two ISP paths to the same application target.
B:The described behavior is part of ‘Configure an SLA target for a health check’, used to turn observed quality metrics into a pass-or-fail objective for rule selection instead of the role of ‘Investigate alive versus SLA-qualified state’. In contrast to ‘Configure an SLA target for a health check’, ‘Investigate alive versus SLA-qualified state’ follows a different mechanism: a member may be reachable and report alive while failing a stricter SLA target for performance. Treating ‘Configure an SLA target for a health check’ as equivalent would not address an interface is alive in health-check output but excluded from a latency-sensitive rule in a remote call center measuring two ISP paths to the same application target.
D:The described behavior is part of ‘Select the correct probe server’, used to measure user-relevant path health rather than only the nearest ISP hop instead of the role of ‘Investigate alive versus SLA-qualified state’. In contrast to ‘Select the correct probe server’, ‘Investigate alive versus SLA-qualified state’ follows a different mechanism: a member may be reachable and report alive while failing a stricter SLA target for performance. Treating ‘Select the correct probe server’ as equivalent would not address an interface is alive in health-check output but excluded from a latency-sensitive rule in a remote call center measuring two ISP paths to the same application target.
Question 271
During an authorized lab exercise for a policy owner protecting HTTPS web sessions without blocking business use, the acceptance criteria require the team to apply a consistent set of inspection components to selected allowed SASE traffic policies. Which control meets that requirement?
- Enable intrusion prevention
- Create a security profile group
- Use cloud API CASB for SaaS data at rest
- Apply a web-filter category action
Explanation
Correct Answer
B:A profile group bundles web, application, SSL, and other security controls for policy attachment; that scope directly serves the goal to apply a consistent set of inspection components to selected allowed SASE traffic policies in a policy owner protecting HTTPS web sessions without blocking business use. During implementation, the policy action must accept traffic before attached inspection profiles can process it rather than treating the configuration label as proof of working service.
Incorrect Answers
A:IPS analyzes supported traffic patterns against intrusion-detection signatures and configured actions, a mechanism intended to detect and block network exploits recognized by attack signatures or protocol decoders rather than the requested ‘Create a security profile group’ control. The stated task instead is to apply a consistent set of inspection components to selected allowed SASE traffic policies, and adjusting ‘Enable intrusion prevention’ would not deliver ‘Create a security profile group’. For the ‘Enable intrusion prevention’ alternative to ‘Create a security profile group’, IPS coverage depends on the traffic inspection path and enabled profile settings.
C:API-connected CASB can examine supported SaaS tenant content and events without requiring every action to cross the inline proxy, a mechanism intended to inspect cloud-service data through supported SaaS APIs rather than only inline user sessions rather than the requested ‘Create a security profile group’ control. The stated task instead is to apply a consistent set of inspection components to selected allowed SASE traffic policies, and adjusting ‘Use cloud API CASB for SaaS data at rest’ would not deliver ‘Create a security profile group’. For the ‘Use cloud API CASB for SaaS data at rest’ alternative to ‘Create a security profile group’, aPI authorization and provider support differ from inline real-time access controls.
D:Web filtering classifies requested sites and applies the configured category or URL action, a mechanism intended to block a prohibited web category while allowing legitimate business browsing rather than the requested ‘Create a security profile group’ control. The stated task instead is to apply a consistent set of inspection components to selected allowed SASE traffic policies, and adjusting ‘Apply a web-filter category action’ would not deliver ‘Create a security profile group’. For the ‘Apply a web-filter category action’ alternative to ‘Create a security profile group’, web filtering decisions differ from application-control signatures and DNS resolution policies.
Question 272
In a change-control meeting for a managed laptop fleet governed by FortiClient endpoint profiles, a colleague challenges the proposed control ‘Use operating-system version posture’ for the requirement to restrict access from endpoints that do not meet an approved operating-system baseline. Which explanation accurately describes its behavior?
- Endpoint profile assignment determines which device-side checks and tunnel behavior a managed group receives.
- OS-version posture criteria allow security rules to distinguish compliant from obsolete endpoint builds.
- A posture rule can evaluate security-product presence or protection state and classify the endpoint.
- FortiClient evaluates defined endpoint posture conditions and associates matching endpoints with security tags.
Explanation
Correct Answer
B:‘Use operating-system version posture’ is used to restrict access from endpoints that do not meet an approved operating-system baseline in a managed laptop fleet governed by FortiClient endpoint profiles; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that the endpoint tag reflects the configured OS-version acceptance criterion; the rollout must also respect this constraint: Version policy should account for supported platforms and enterprise patch baselines.
Incorrect Answers
A:The described behavior is part of ‘Use endpoint-profile assignment for managed groups’, used to apply a stricter posture and connection configuration to a high-risk user population instead of the role of ‘Use operating-system version posture’. In contrast to ‘Use endpoint-profile assignment for managed groups’, ‘Use operating-system version posture’ follows a different mechanism: OS-version posture criteria allow security rules to distinguish compliant from obsolete endpoint builds. Treating ‘Use endpoint-profile assignment for managed groups’ as equivalent would not address unpatched legacy operating systems gain the same access as approved updated workstations in a managed laptop fleet governed by FortiClient endpoint profiles.
C:The described behavior is part of ‘Require endpoint antivirus status’, used to treat disabled or missing antimalware protection as a noncompliant device condition instead of the role of ‘Use operating-system version posture’. In contrast to ‘Require endpoint antivirus status’, ‘Use operating-system version posture’ follows a different mechanism: OS-version posture criteria allow security rules to distinguish compliant from obsolete endpoint builds. Treating ‘Require endpoint antivirus status’ as equivalent would not address unpatched legacy operating systems gain the same access as approved updated workstations in a managed laptop fleet governed by FortiClient endpoint profiles.
D:The described behavior is part of ‘Build a security posture tag rule’, used to label endpoints dynamically when a specified local security condition is met instead of the role of ‘Use operating-system version posture’. In contrast to ‘Build a security posture tag rule’, ‘Use operating-system version posture’ follows a different mechanism: OS-version posture criteria allow security rules to distinguish compliant from obsolete endpoint builds. Treating ‘Build a security posture tag rule’ as equivalent would not address unpatched legacy operating systems gain the same access as approved updated workstations in a managed laptop fleet governed by FortiClient endpoint profiles.
Question 273
At a branch connected to a SASE point of presence by an encrypted service path, a support engineer needs to verify that ‘Integrate branch SD-WAN with FortiSASE on-ramp’ is active for the goal to send on-site user internet traffic to FortiSASE cloud inspection using a supported branch edge. Which observation is decisive?
- The designated protected TCP service is reachable through the authorized ZTNA proxy.
- Service connection health and preferred hub state show a usable alternate.
- The branch overlay to the service is established and inspected traffic appears in SASE logs.
- Matching site flows are observed through the branch on-ramp and SASE enforcement logs.
Explanation
Correct Answer
C:This checks ‘Integrate branch SD-WAN with FortiSASE on-ramp’ at the correct operational boundary: a supported FortiGate branch on-ramp can steer site traffic to FortiSASE enforcement PoPs. It demonstrates the specific capability to send on-site user internet traffic to FortiSASE cloud inspection using a supported branch edge in a branch connected to a SASE point of presence by an encrypted service path; deployment should additionally respect the constraint: Branch integration requires transport reachability and matching on-ramp security policy.
Incorrect Answers
A:That observation belongs to ‘Use ZTNA application proxy for a protected TCP app’, not ‘Integrate branch SD-WAN with FortiSASE on-ramp’; its purpose is to publish a narrowly scoped internal TCP application through a FortiGate ZTNA gateway, the underlying behavior is that ZTNA private access targets authorized TCP applications rather than granting generic network reachability. The reviewer is instead verifying ‘Integrate branch SD-WAN with FortiSASE on-ramp’ for a branch connected to a SASE point of presence by an encrypted service path, not the evidence produced by ‘Use ZTNA application proxy for a protected TCP app’.
B:That observation belongs to ‘Use a redundant private-access hub’, not ‘Integrate branch SD-WAN with FortiSASE on-ramp’; its purpose is to maintain access to applications when one data-center gateway or tunnel fails, the underlying behavior is that multiple suitably configured SPA hubs can provide a redundant path to private resources. The reviewer is instead verifying ‘Integrate branch SD-WAN with FortiSASE on-ramp’ for a branch connected to a SASE point of presence by an encrypted service path, not the evidence produced by ‘Use a redundant private-access hub’.
D:That observation belongs to ‘Verify site-based SASE traffic steering’, not ‘Integrate branch SD-WAN with FortiSASE on-ramp’; its purpose is to differentiate local branch DIA from traffic genuinely sent to cloud enforcement, the underlying behavior is that site-based on-ramp configuration determines which branch flows are forwarded into FortiSASE. The reviewer is instead verifying ‘Integrate branch SD-WAN with FortiSASE on-ramp’ for a branch connected to a SASE point of presence by an encrypted service path, not the evidence produced by ‘Verify site-based SASE traffic steering’.
Question 274
At an insurance branch with a real-time application and a bulk-backup workload, an engineer is preparing ‘Match a source subnet in an SD-WAN rule’ to apply a special path selection only to traffic originating in one department network. Which TWO statements identify a pertinent deployment safeguard and a direct post-change validation result? Choose TWO.
- A cheap member failing its SLA is not preferred solely because of its price.
- Manual member preference remains subject to route availability and any needed firewall permission.
- The diagnostic output identifies the matching service and its selected eligible member.
- The matched rule contains the required source address object and other subnets bypass it.
- Source steering does not itself authenticate an individual user.
Explanation
Correct Answers
D:The observation follows from the operation of ‘Match a source subnet in an SD-WAN rule’: source-address criteria restrict SD-WAN rule matching to sessions from specified client address ranges. It directly tests the requested ability to apply a special path selection only to traffic originating in one department network in an insurance branch with a real-time application and a bulk-backup workload, rather than another policy or network layer.
E:This safeguard applies to ‘Match a source subnet in an SD-WAN rule’, which works because source-address criteria restrict SD-WAN rule matching to sessions from specified client address ranges. Without the correct deployment condition, operators may see that all departments are steered to a premium link even though only the trading subnet needs it in an insurance branch with a real-time application and a bulk-backup workload.
Incorrect Answers
A:The planning point is associated with ‘Use Lowest Cost with an SLA target’, not ‘Match a source subnet in an SD-WAN rule’; its real role is to send a service on the cheapest circuit that still meets quality objectives. The required deployment instead centers on ‘Match a source subnet in an SD-WAN rule’, rather than ‘Use Lowest Cost with an SLA target’; the distinct symptom to guard against is that all departments are steered to a premium link even though only the trading subnet needs it.
B:The planning point is associated with ‘Use a manual SD-WAN strategy’, not ‘Match a source subnet in an SD-WAN rule’; its real role is to pin a specific business application to a preferred transport independent of dynamic quality ranking. The required deployment instead centers on ‘Match a source subnet in an SD-WAN rule’, rather than ‘Use a manual SD-WAN strategy’; the distinct symptom to guard against is that all departments are steered to a premium link even though only the trading subnet needs it.
C:This result would validate ‘Test rule matching with service diagnostics’, not ‘Match a source subnet in an SD-WAN rule’, because SD-WAN service diagnostics expose matched rules, interface lists, modes, and selected member status. That separate implementation serves identify which SD-WAN rule and candidate member were chosen for a particular session, whereas the audit needs evidence specifically of ‘Match a source subnet in an SD-WAN rule’ at an insurance branch with a real-time application and a bulk-backup workload.
Question 275
Within a financial services branch where forwarding decisions disagree with interface health, the administrator must repair one-way traffic where forward packets reach the data center but replies do not without redesigning unrelated services. Which option addresses the goal?
- Configure a static partner route through overlay zone
- Install default route through an SD-WAN zone
- Confirm return route for remote private access
- Review administrative distance
- Keep underlay route for tunnel peer
Explanation
Correct Answer
C:Bidirectional reachability requires the remote hub or server-side router to return traffic to the client prefix; that scope directly serves the goal to repair one-way traffic where forward packets reach the data center but replies do not in a financial services branch where forwarding decisions disagree with interface health. During implementation, forward-route success is insufficient for stateful end-to-end communication rather than treating the configuration label as proof of working service.
Incorrect Answers
A:A destination-specific static route referencing the overlay zone makes private routes accessible to SD-WAN selection, a mechanism intended to reach an on-premises network across an IPsec overlay SD-WAN group rather than the requested ‘Confirm return route for remote private access’ control. The stated task instead is to repair one-way traffic where forward packets reach the data center but replies do not, and adjusting ‘Configure a static partner route through overlay zone’ would not deliver ‘Confirm return route for remote private access’. For the ‘Configure a static partner route through overlay zone’ alternative to ‘Confirm return route for remote private access’, the remote peer must also know a return path to the local subnet.
B:A zone-based default static route gives SD-WAN a routing candidate for nonlocal destinations, a mechanism intended to make general internet destinations reachable without listing every WAN member as a separate policy interface rather than the requested ‘Confirm return route for remote private access’ control. The stated task instead is to repair one-way traffic where forward packets reach the data center but replies do not, and adjusting ‘Install default route through an SD-WAN zone’ would not deliver ‘Confirm return route for remote private access’. For the ‘Install default route through an SD-WAN zone’ alternative to ‘Confirm return route for remote private access’, a route must exist before the steering choice can forward a matching session.
D:Administrative distance influences which equal-prefix route source is preferred for installation, a mechanism intended to choose between competing routes learned from different sources for the same prefix rather than the requested ‘Confirm return route for remote private access’ control. The stated task instead is to repair one-way traffic where forward packets reach the data center but replies do not, and adjusting ‘Review administrative distance’ would not deliver ‘Confirm return route for remote private access’. For the ‘Review administrative distance’ alternative to ‘Confirm return route for remote private access’, specificity is considered before comparing administrative distance on different prefix lengths.
E:An overlay tunnel requires the public peer endpoint to remain reachable through an underlay path, a mechanism intended to preserve transport reachability to an IPsec hub before private overlay traffic is steered rather than the requested ‘Confirm return route for remote private access’ control. The stated task instead is to repair one-way traffic where forward packets reach the data center but replies do not, and adjusting ‘Keep underlay route for tunnel peer’ would not deliver ‘Confirm return route for remote private access’. For the ‘Keep underlay route for tunnel peer’ alternative to ‘Confirm return route for remote private access’, protect tunnel-control reachability from routing recursion into the same tunnel.
Question 276
Within a managed laptop fleet governed by FortiClient endpoint profiles, the team wants to avoid an ineffective configuration of ‘Use operating-system version posture’. Which consideration deserves attention?
- A cloud traffic policy alone does not deploy settings to FortiClient endpoints.
- Product detection must match the supported platform and endpoint security configuration.
- Authentication identity and endpoint posture solve different trust checks.
- Version policy should account for supported platforms and enterprise patch baselines.
- The tag logic must accurately represent the actual security requirement.
Explanation
Correct Answer
D:This condition matters for ‘Use operating-system version posture’ because OS-version posture criteria allow security rules to distinguish compliant from obsolete endpoint builds. Omitting the relevant safeguard can produce unpatched legacy operating systems gain the same access as approved updated workstations; a successful test at a managed laptop fleet governed by FortiClient endpoint profiles would instead demonstrate that the endpoint tag reflects the configured OS-version acceptance criterion.
Incorrect Answers
A:The condition is associated with ‘Use endpoint-profile assignment for managed groups’, a mechanism used to apply a stricter posture and connection configuration to a high-risk user population instead of ‘Use operating-system version posture’, because endpoint profile assignment determines which device-side checks and tunnel behavior a managed group receives. For ‘Use operating-system version posture’, unlike ‘Use endpoint-profile assignment for managed groups’, the characteristic failure would be unpatched legacy operating systems gain the same access as approved updated workstations, which this alternative prerequisite would not directly address at a managed laptop fleet governed by FortiClient endpoint profiles.
B: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 ‘Use operating-system version posture’, because a posture rule can evaluate security-product presence or protection state and classify the endpoint. For ‘Use operating-system version posture’, unlike ‘Require endpoint antivirus status’, the characteristic failure would be unpatched legacy operating systems gain the same access as approved updated workstations, which this alternative prerequisite would not directly address at a managed laptop fleet governed by FortiClient endpoint profiles.
C:The condition is associated with ‘Assign compliant endpoint tags to private policies’, a mechanism used to grant sensitive private access only to managed devices meeting specified security conditions instead of ‘Use operating-system version posture’, because private access policies can use security posture tags as dynamic matching criteria. For ‘Use operating-system version posture’, unlike ‘Assign compliant endpoint tags to private policies’, the characteristic failure would be unpatched legacy operating systems gain the same access as approved updated workstations, which this alternative prerequisite would not directly address at a managed laptop fleet governed by FortiClient endpoint profiles.
E: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 ‘Use operating-system version posture’, because FortiClient evaluates defined endpoint posture conditions and associates matching endpoints with security tags. For ‘Use operating-system version posture’, unlike ‘Build a security posture tag rule’, the characteristic failure would be unpatched legacy operating systems gain the same access as approved updated workstations, which this alternative prerequisite would not directly address at a managed laptop fleet governed by FortiClient endpoint profiles.
Question 277
In a change-control meeting for a private-access application that requires device trust as well as user identity, a design review calls for a way to avoid inverting the policy when a tag specifically denotes a noncompliant endpoint. What should the operator configure?
- Check a required running process
- Use operating-system version posture
- Configure pre-connection posture enforcement
- Review the posture tag's allow or deny direction
Explanation
Correct Answer
D:An allow-when-tagged versus deny-when-tagged action determines whether the matched posture condition grants connectivity; that scope directly serves the goal to avoid inverting the policy when a tag specifically denotes a noncompliant endpoint in a private-access application that requires device trust as well as user identity. During implementation, define whether a tag means compliant or noncompliant before using it for admission rather than treating the configuration label as proof of working service.
Incorrect Answers
A:Process-presence conditions can contribute to device posture evaluation where supported, a mechanism intended to permit an internal app only when its approved endpoint security agent is running rather than the requested ‘Review the posture tag's allow or deny direction’ control. The stated task instead is to avoid inverting the policy when a tag specifically denotes a noncompliant endpoint, and adjusting ‘Check a required running process’ would not deliver ‘Review the posture tag's allow or deny direction’. For the ‘Check a required running process’ alternative to ‘Review the posture tag's allow or deny direction’, a process name alone is weaker than cryptographic proof of application integrity.
B:OS-version posture criteria allow security rules to distinguish compliant from obsolete endpoint builds, a mechanism intended to restrict access from endpoints that do not meet an approved operating-system baseline rather than the requested ‘Review the posture tag's allow or deny direction’ control. The stated task instead is to avoid inverting the policy when a tag specifically denotes a noncompliant endpoint, and adjusting ‘Use operating-system version posture’ would not deliver ‘Review the posture tag's allow or deny direction’. For the ‘Use operating-system version posture’ alternative to ‘Review the posture tag's allow or deny direction’, version policy should account for supported platforms and enterprise patch baselines.
C:A configured pre-connection check can allow or deny a tunnel attempt based on an assigned posture tag, a mechanism intended to block an untrusted FortiClient endpoint before it establishes its protected cloud tunnel rather than the requested ‘Review the posture tag's allow or deny direction’ control. The stated task instead is to avoid inverting the policy when a tag specifically denotes a noncompliant endpoint, and adjusting ‘Configure pre-connection posture enforcement’ would not deliver ‘Review the posture tag's allow or deny direction’. For the ‘Configure pre-connection posture enforcement’ alternative to ‘Review the posture tag's allow or deny direction’, this workflow depends on appropriate IPsec remote-agent support and endpoint profile setup.
Question 278
At an enterprise interconnecting SD-WAN overlays and cloud security edges, an engineer is preparing ‘Verify site-based SASE traffic steering’ to differentiate local branch DIA from traffic genuinely sent to cloud enforcement. Which TWO statements identify a pertinent deployment safeguard and a direct post-change validation result? Choose TWO.
- Make the observed steering decision consistent with routing, policy, and tunnel state.
- The protected data-center prefixes need return routes toward FortiSASE clients.
- The routed SPA service connection reaches the approved UDP application behind the hub.
- Matching site flows are observed through the branch on-ramp and SASE enforcement logs.
- Name resolution must be reachable over the chosen private access topology.
Explanation
Correct Answers
A:This safeguard applies to ‘Verify site-based SASE traffic steering’, which works because site-based on-ramp configuration determines which branch flows are forwarded into FortiSASE. Without the correct deployment condition, operators may see that branch internet sessions show a public ISP path and lack expected cloud security logs in an enterprise interconnecting SD-WAN overlays and cloud security edges.
D:The observation follows from the operation of ‘Verify site-based SASE traffic steering’: site-based on-ramp configuration determines which branch flows are forwarded into FortiSASE. It directly tests the requested ability to differentiate local branch DIA from traffic genuinely sent to cloud enforcement in an enterprise interconnecting SD-WAN overlays and cloud security edges, rather than another policy or network layer.
Incorrect Answers
B:The planning point is associated with ‘Use FortiGate as a private-access hub’, not ‘Verify site-based SASE traffic steering’; its real role is to connect remote FortiSASE clients to data-center applications protected behind a FortiGate. The required deployment instead centers on ‘Verify site-based SASE traffic steering’, rather than ‘Use FortiGate as a private-access hub’; the distinct symptom to guard against is that branch internet sessions show a public ISP path and lack expected cloud security logs.
C:This result would validate ‘Use SD-WAN private access for TCP and UDP’, not ‘Verify site-based SASE traffic steering’, because an SD-WAN-based SPA design can provide routed access to private TCP and UDP applications. That separate implementation serves extend private resource connectivity beyond the TCP-focused ZTNA access proxy model, whereas the audit needs evidence specifically of ‘Verify site-based SASE traffic steering’ at an enterprise interconnecting SD-WAN overlays and cloud security edges.
E:The planning point is associated with ‘Configure DNS resolution for private names’, not ‘Verify site-based SASE traffic steering’; its real role is to let remote users resolve internal application FQDNs to protected addresses. The required deployment instead centers on ‘Verify site-based SASE traffic steering’, rather than ‘Configure DNS resolution for private names’; the distinct symptom to guard against is that branch internet sessions show a public ISP path and lack expected cloud security logs.
Question 279
For an operations hub with differentiated perimeter policies for WAN members, a technical review examines the control ‘Define the member health-check source’ for the objective to send probes using the correct reachable source address on a multiaddress uplink. Which statement best describes what it changes?
- Overlay zones provide distinct policy and route targets for tunnel traffic bound for private networks.
- The cost field ranks SLA-qualified members for the Lowest Cost strategy, with smaller values preferred.
- A member's zone association determines which zone-based routes and policies can use that interface.
- A member health-check source setting controls the source IP used by health probes to a monitored server.
Explanation
Correct Answer
D:‘Define the member health-check source’ is used to send probes using the correct reachable source address on a multiaddress uplink in an operations hub with differentiated perimeter policies for WAN members; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that health-check packets use the specified reachable source on the chosen member; the rollout must also respect this constraint: The source must be routable toward the monitor target and accepted by its response path.
Incorrect Answers
A:The described behavior is part of ‘Create a dedicated overlay zone’, used to group IPsec tunnel interfaces separately from physical WAN underlays instead of the role of ‘Define the member health-check source’. In contrast to ‘Create a dedicated overlay zone’, ‘Define the member health-check source’ follows a different mechanism: a member health-check source setting controls the source IP used by health probes to a monitored server. Treating ‘Create a dedicated overlay zone’ as equivalent would not address probes are rejected because they originate from an unexpected secondary interface address in an operations hub with differentiated perimeter policies for WAN members.
B:The described behavior is part of ‘Set member cost’, used to favor a lower-priced uplink only when eligible under lowest-cost SLA rules instead of the role of ‘Define the member health-check source’. In contrast to ‘Set member cost’, ‘Define the member health-check source’ follows a different mechanism: a member health-check source setting controls the source IP used by health probes to a monitored server. Treating ‘Set member cost’ as equivalent would not address probes are rejected because they originate from an unexpected secondary interface address in an operations hub with differentiated perimeter policies for WAN members.
C:The described behavior is part of ‘Assign members to the intended zone’, used to put two ISP circuits in the internet transport zone rather than the private-overlay group instead of the role of ‘Define the member health-check source’. In contrast to ‘Assign members to the intended zone’, ‘Define the member health-check source’ follows a different mechanism: a member health-check source setting controls the source IP used by health probes to a monitored server. Treating ‘Assign members to the intended zone’ as equivalent would not address probes are rejected because they originate from an unexpected secondary interface address in an operations hub with differentiated perimeter policies for WAN members.
Question 280
Within a SASE change-control review using an authorized test identity, the configuration has been applied. Which measurement or record best confirms the goal to permit approved user traffic before applying cloud-delivered inspection profiles?
- The intended operator signs in with an authorized administrative identity.
- The tenant dashboard reports provisioned cloud enforcement capacity and accessible administration.
- Client connectivity shows active SASE steering to a security PoP.
- 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.
Explanation
Correct Answer
D:This checks ‘Configure a SASE allow policy’ at the correct operational boundary: FortiSASE traffic policies determine which user or destination flows are accepted or denied and which security-profile groups apply. It demonstrates the specific capability to permit approved user traffic before applying cloud-delivered inspection profiles in a SASE change-control review using an authorized test identity; deployment should additionally respect the constraint: A security profile does not independently override a deny access policy.
Incorrect Answers
A:That observation belongs to ‘Assign FortiSASE administrator access’, not ‘Configure a SASE allow policy’; its purpose is to let a delegated operator manage the cloud configuration without sharing the primary account, the underlying behavior is that distinct authorized administrators enable accountable management while the original account retains ownership. The reviewer is instead verifying ‘Configure a SASE allow policy’ for a SASE change-control review using an authorized test identity, not the evidence produced by ‘Assign FortiSASE administrator access’.
B:That observation belongs to ‘Verify FortiSASE service provisioning’, not ‘Configure a SASE allow policy’; its purpose is to confirm the cloud security service is available before distributing client configurations, the underlying behavior is that FortiSASE must have an active provisioned instance with security points of presence before managed users can use its cloud enforcement. The reviewer is instead verifying ‘Configure a SASE allow policy’ for a SASE change-control review using an authorized test identity, not the evidence produced by ‘Verify FortiSASE service provisioning’.
C:That observation belongs to ‘Choose an appropriate security PoP path’, not ‘Configure a SASE allow policy’; its purpose is to bring roaming clients to cloud enforcement rather than hairpin every connection through headquarters, the underlying behavior is that FortiSASE steers supported client traffic toward its security points of presence for consistent remote policy enforcement. The reviewer is instead verifying ‘Configure a SASE allow policy’ for a SASE change-control review using an authorized test identity, not the evidence produced by ‘Choose an appropriate security PoP path’.
E:That observation belongs to ‘Configure SASE certificate trust’, not ‘Configure a SASE allow policy’; its purpose is to avoid TLS warnings and ensure clients trust the cloud security inspection certificate, the underlying behavior is that when deep inspection is used, managed endpoints need the appropriate inspection CA trust anchor. The reviewer is instead verifying ‘Configure a SASE allow policy’ for a SASE change-control review using an authorized test identity, not the evidence produced by ‘Configure SASE certificate trust’.