Question 360
At a policy owner protecting HTTPS web sessions without blocking business use, the change board is evaluating ‘Create a security profile group’. Which technical consideration must be built into the plan?
- IPS coverage depends on the traffic inspection path and enabled profile settings.
- Port-only access controls are not the same as identifying an application signature.
- The policy action must accept traffic before attached inspection profiles can process it.
- Encrypted transfers need suitable deep inspection for content-aware file filtering.
Explanation
Correct Answer
C:This condition matters for ‘Create a security profile group’ because a profile group bundles web, application, SSL, and other security controls for policy attachment. Omitting the relevant safeguard can produce individual protections exist but a matched accept policy has no intended profile association; a successful test at a policy owner protecting HTTPS web sessions without blocking business use would instead demonstrate that the access policy references the correct profile group and test detections appear.
Incorrect Answers
A:The condition is associated with ‘Enable intrusion prevention’, a mechanism used to detect and block network exploits recognized by attack signatures or protocol decoders instead of ‘Create a security profile group’, because IPS analyzes supported traffic patterns against intrusion-detection signatures and configured actions. For ‘Create a security profile group’, unlike ‘Enable intrusion prevention’, the characteristic failure would be individual protections exist but a matched accept policy has no intended profile association, which this alternative prerequisite would not directly address at a policy owner protecting HTTPS web sessions without blocking business use.
B:The condition is associated with ‘Configure application control signatures’, a mechanism used to block a specific risky application without disabling every website in its category instead of ‘Create a security profile group’, because Application Control identifies application behavior and can apply signature-level allow, monitor, or block actions. For ‘Create a security profile group’, unlike ‘Configure application control signatures’, the characteristic failure would be individual protections exist but a matched accept policy has no intended profile association, which this alternative prerequisite would not directly address at a policy owner protecting HTTPS web sessions without blocking business use.
D:The condition is associated with ‘Configure file filtering’, a mechanism used to block transfer of prohibited file types regardless of benign website category instead of ‘Create a security profile group’, because file Filter identifies supported file types in inspected sessions and enforces the configured file action. For ‘Create a security profile group’, unlike ‘Configure file filtering’, the characteristic failure would be individual protections exist but a matched accept policy has no intended profile association, which this alternative prerequisite would not directly address at a policy owner protecting HTTPS web sessions without blocking business use.
Question 361
At a contractor access program with different endpoint and connection policies, the rollout includes the control ‘Require endpoint antivirus status’ to treat disabled or missing antimalware protection as a noncompliant device condition. Which observed mechanism is consistent with this configuration?
- A posture rule can evaluate security-product presence or protection state and classify the endpoint.
- Vulnerability-related posture information can be used to classify a risky endpoint for conditional access.
- Endpoint profile assignment determines which device-side checks and tunnel behavior a managed group receives.
- Private access policies can use security posture tags as dynamic matching criteria.
Explanation
Correct Answer
A:‘Require endpoint antivirus status’ is used to treat disabled or missing antimalware protection as a noncompliant device condition in a contractor access program with different endpoint and connection policies; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that the posture telemetry classifies the device according to antivirus status; the rollout must also respect this constraint: Product detection must match the supported platform and endpoint security configuration.
Incorrect Answers
B:The described behavior is part of ‘Check endpoint vulnerability severity’, used to apply stricter access to devices with high-severity unresolved vulnerabilities instead of the role of ‘Require endpoint antivirus status’. In contrast to ‘Check endpoint vulnerability severity’, ‘Require endpoint antivirus status’ follows a different mechanism: a posture rule can evaluate security-product presence or protection state and classify the endpoint. Treating ‘Check endpoint vulnerability severity’ as equivalent would not address a laptop with disabled endpoint protection remains in the trusted access group in a contractor access program with different endpoint and connection policies.
C: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 ‘Require endpoint antivirus status’. In contrast to ‘Use endpoint-profile assignment for managed groups’, ‘Require endpoint antivirus status’ follows a different mechanism: a posture rule can evaluate security-product presence or protection state and classify the endpoint. Treating ‘Use endpoint-profile assignment for managed groups’ as equivalent would not address a laptop with disabled endpoint protection remains in the trusted access group in a contractor access program with different endpoint and connection policies.
D:The described behavior is part of ‘Assign compliant endpoint tags to private policies’, used to grant sensitive private access only to managed devices meeting specified security conditions instead of the role of ‘Require endpoint antivirus status’. In contrast to ‘Assign compliant endpoint tags to private policies’, ‘Require endpoint antivirus status’ follows a different mechanism: a posture rule can evaluate security-product presence or protection state and classify the endpoint. Treating ‘Assign compliant endpoint tags to private policies’ as equivalent would not address a laptop with disabled endpoint protection remains in the trusted access group in a contractor access program with different endpoint and connection policies.
Question 362
At a data analytics site comparing primary and backup overlay health, an engineer is preparing ‘Use passive WAN health measurement’ to derive quality observations from actual matched user sessions rather than dedicated probes. Which TWO statements identify a pertinent deployment safeguard and a direct post-change validation result? Choose TWO.
- Traffic and policy instrumentation must support the passive measurement mechanism.
- Observed session-based metrics appear for the configured passive measurement.
- A measured SLA cannot evaluate a member that is not associated with the check.
- Threshold values should reflect actual application tolerances and the monitored geography.
- The high-variation path fails jitter while the stable path passes.
Explanation
Correct Answers
A:This safeguard applies to ‘Use passive WAN health measurement’, which works because passive measurements can obtain link metrics from observed traffic instead of relying solely on synthetic monitoring packets. Without the correct deployment condition, operators may see that active probes look healthy but user-path measurements are needed for the actual application flow in a data analytics site comparing primary and backup overlay health.
B:The observation follows from the operation of ‘Use passive WAN health measurement’: passive measurements can obtain link metrics from observed traffic instead of relying solely on synthetic monitoring packets. It directly tests the requested ability to derive quality observations from actual matched user sessions rather than dedicated probes in a data analytics site comparing primary and backup overlay health, rather than another policy or network layer.
Incorrect Answers
C:The planning point is associated with ‘Assign the relevant member set to a health check’, not ‘Use passive WAN health measurement’; its real role is to compare only the transport members serving a given application class. The required deployment instead centers on ‘Use passive WAN health measurement’, rather than ‘Assign the relevant member set to a health check’; the distinct symptom to guard against is that active probes look healthy but user-path measurements are needed for the actual application flow.
D:The planning point is associated with ‘Avoid overly strict SLA targets’, not ‘Use passive WAN health measurement’; its real role is to prevent both usable circuits from being excluded by unrealistic quality limits. The required deployment instead centers on ‘Use passive WAN health measurement’, rather than ‘Avoid overly strict SLA targets’; the distinct symptom to guard against is that active probes look healthy but user-path measurements are needed for the actual application flow.
E:This result would validate ‘Set jitter SLA threshold’, not ‘Use passive WAN health measurement’, because a jitter target compares delay variation with an allowed maximum to qualify or reject a member. That separate implementation serves avoid a circuit whose packet-delay variation damages live audio, whereas the audit needs evidence specifically of ‘Use passive WAN health measurement’ at a data analytics site comparing primary and backup overlay health.
Question 363
For a test lab containing an overlay tunnel and two underlay next hops, a maintenance plan requires the firewall team to make general internet destinations reachable without listing every WAN member as a separate policy interface. Which choice is appropriate?
- Inspect route withdrawal after health failure
- Use routing diagnostics before changing SD-WAN cost
- Use split routing for private and internet destinations
- Install default route through an SD-WAN zone
Explanation
Correct Answer
D:A zone-based default static route gives SD-WAN a routing candidate for nonlocal destinations; that scope directly serves the goal to make general internet destinations reachable without listing every WAN member as a separate policy interface in a test lab containing an overlay tunnel and two underlay next hops. During implementation, a route must exist before the steering choice can forward a matching session rather than treating the configuration label as proof of working service.
Incorrect Answers
A:SD-WAN health failure can remove a member's route from the link load-balancing candidate set, a mechanism intended to explain why a failed WAN member stops being considered for new forwarding rather than the requested ‘Install default route through an SD-WAN zone’ control. The stated task instead is to make general internet destinations reachable without listing every WAN member as a separate policy interface, and adjusting ‘Inspect route withdrawal after health failure’ would not deliver ‘Install default route through an SD-WAN zone’. For the ‘Inspect route withdrawal after health failure’ alternative to ‘Install default route through an SD-WAN zone’, a failed SLA state can change route eligibility without a physical link-down event.
B:Route inspection distinguishes absent routes from member cost or performance rankings, a mechanism intended to avoid misdiagnosing unreachable prefixes as an economic-selection problem rather than the requested ‘Install default route through an SD-WAN zone’ control. The stated task instead is to make general internet destinations reachable without listing every WAN member as a separate policy interface, and adjusting ‘Use routing diagnostics before changing SD-WAN cost’ would not deliver ‘Install default route through an SD-WAN zone’. For the ‘Use routing diagnostics before changing SD-WAN cost’ alternative to ‘Install default route through an SD-WAN zone’, cost only influences relevant strategies among candidates that are routable and eligible.
C:Destination-specific private routes and a general internet default route allow distinct traffic paths, a mechanism intended to send corporate destinations over overlay but ordinary internet traffic via local DIA rather than the requested ‘Install default route through an SD-WAN zone’ control. The stated task instead is to make general internet destinations reachable without listing every WAN member as a separate policy interface, and adjusting ‘Use split routing for private and internet destinations’ would not deliver ‘Install default route through an SD-WAN zone’. For the ‘Use split routing for private and internet destinations’ alternative to ‘Install default route through an SD-WAN zone’, firewall policies must authorize both traffic classes with suitable inspection.
Question 364
During an authorized lab exercise for a cloud security tenant inspecting traffic from managed remote laptops, the incident notes state that an approved SaaS service accepts uploads containing explicitly restricted account identifiers. Which change is most relevant to this symptom?
- Investigate: Distinguish SIA from SSA policy intent
- Investigate: Configure data loss prevention patterns
- Investigate: Apply an antivirus profile to allowed traffic
- Investigate: Use DNS filtering
Explanation
Correct Answer
B:The symptom identifies the missing operational behavior: DLP examines supported inspected content for configured sensitive-data patterns and applies an action. For a cloud security tenant inspecting traffic from managed remote laptops, a direct diagnostic confirmation would be that DLP records a matching sensitive-data pattern and the configured action; during repair, detection requires representative patterns and an inspection path that exposes payload content.
Incorrect Answers
A:SIA focuses on internet-bound security inspection while SSA adds cloud-application controls such as inline CASB or DLP, which serves the different requirement to apply general internet threat protection separately from SaaS-specific data and tenant controls instead of the behavior delivered by ‘Configure data loss prevention patterns’. If that component were misconfigured, a more characteristic finding would be that a SaaS tenant restriction is expected from generic internet path steering alone; the actual report concerns an approved SaaS service accepts uploads containing explicitly restricted account identifiers at a cloud security tenant inspecting traffic from managed remote laptops.
C:An enabled antivirus inspection component examines supported file content for malicious signatures or behavior indicators, which serves the different requirement to detect malware payloads passing through a permitted cloud access policy instead of the behavior delivered by ‘Configure data loss prevention patterns’. If that component were misconfigured, a more characteristic finding would be that a download is allowed but malicious file content is not checked by the expected AV inspection; the actual report concerns an approved SaaS service accepts uploads containing explicitly restricted account identifiers at a cloud security tenant inspecting traffic from managed remote laptops.
D: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 ‘Configure data loss prevention patterns’. 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 an approved SaaS service accepts uploads containing explicitly restricted account identifiers at a cloud security tenant inspecting traffic from managed remote laptops.
Question 365
At a FortiSASE tenant being prepared for a 60-user remote-work pilot, the change request is to restrict access from locations outside an organization-approved geographic footprint. Which configuration is the most direct fit?
- Organize SASE users into policy groups
- Assign FortiSASE administrator access
- Separate internet and private access policies
- Use geolocation-aware access restrictions
Explanation
Correct Answer
D:Geographic policy criteria can help distinguish traffic by geolocation where FortiSASE policy supports that selection; that scope directly serves the goal to restrict access from locations outside an organization-approved geographic footprint in a FortiSASE tenant being prepared for a 60-user remote-work pilot. During implementation, iP geolocation is approximate and must not replace strong user identity controls rather than treating the configuration label as proof of working service.
Incorrect Answers
A:User groups provide a membership basis for matching different FortiSASE access policies, a mechanism intended to apply different web access controls to developers and finance staff rather than the requested ‘Use geolocation-aware access restrictions’ control. The stated task instead is to restrict access from locations outside an organization-approved geographic footprint, and adjusting ‘Organize SASE users into policy groups’ would not deliver ‘Use geolocation-aware access restrictions’. For the ‘Organize SASE users into policy groups’ alternative to ‘Use geolocation-aware access restrictions’, authentication source membership must be available for identity-based rule evaluation.
B:Distinct authorized administrators enable accountable management while the original account retains ownership, a mechanism intended to let a delegated operator manage the cloud configuration without sharing the primary account rather than the requested ‘Use geolocation-aware access restrictions’ control. The stated task instead is to restrict access from locations outside an organization-approved geographic footprint, and adjusting ‘Assign FortiSASE administrator access’ would not deliver ‘Use geolocation-aware access restrictions’. For the ‘Assign FortiSASE administrator access’ alternative to ‘Use geolocation-aware access restrictions’, scope and privilege should be limited to the operator's actual duties.
C:SIA and SPA use distinct routing and policy constructs despite sharing the FortiSASE service, a mechanism intended to apply different controls to cloud web traffic and protected data-center applications rather than the requested ‘Use geolocation-aware access restrictions’ control. The stated task instead is to restrict access from locations outside an organization-approved geographic footprint, and adjusting ‘Separate internet and private access policies’ would not deliver ‘Use geolocation-aware access restrictions’. For the ‘Separate internet and private access policies’ alternative to ‘Use geolocation-aware access restrictions’, private resource reachability needs a supported SPA design in addition to SIA controls.
Question 366
Within an off-site workforce where some endpoints fail compliance verification, the administrator must apply stricter access to devices with high-severity unresolved vulnerabilities without redesigning unrelated services. Which option addresses the goal?
- Review the posture tag's allow or deny direction
- Check endpoint vulnerability severity
- Build a security posture tag rule
- Assign compliant endpoint tags to private policies
- Use a certificate-based posture check
Explanation
Correct Answer
B:Vulnerability-related posture information can be used to classify a risky endpoint for conditional access; that scope directly serves the goal to apply stricter access to devices with high-severity unresolved vulnerabilities in an off-site workforce where some endpoints fail compliance verification. During implementation, posture signals require recent endpoint scanning and successful telemetry exchange rather than treating the configuration label as proof of working service.
Incorrect Answers
A:An allow-when-tagged versus deny-when-tagged action determines whether the matched posture condition grants connectivity, a mechanism intended to avoid inverting the policy when a tag specifically denotes a noncompliant endpoint rather than the requested ‘Check endpoint vulnerability severity’ control. The stated task instead is to apply stricter access to devices with high-severity unresolved vulnerabilities, and adjusting ‘Review the posture tag's allow or deny direction’ would not deliver ‘Check endpoint vulnerability severity’. For the ‘Review the posture tag's allow or deny direction’ alternative to ‘Check endpoint vulnerability severity’, define whether a tag means compliant or noncompliant before using it for admission.
C:FortiClient evaluates defined endpoint posture conditions and associates matching endpoints with security tags, a mechanism intended to label endpoints dynamically when a specified local security condition is met rather than the requested ‘Check endpoint vulnerability severity’ control. The stated task instead is to apply stricter access to devices with high-severity unresolved vulnerabilities, and adjusting ‘Build a security posture tag rule’ would not deliver ‘Check endpoint vulnerability severity’. For the ‘Build a security posture tag rule’ alternative to ‘Check endpoint vulnerability severity’, the tag logic must accurately represent the actual security requirement.
D:Private access policies can use security posture tags as dynamic matching criteria, a mechanism intended to grant sensitive private access only to managed devices meeting specified security conditions rather than the requested ‘Check endpoint vulnerability severity’ control. The stated task instead is to apply stricter access to devices with high-severity unresolved vulnerabilities, and adjusting ‘Assign compliant endpoint tags to private policies’ would not deliver ‘Check endpoint vulnerability severity’. For the ‘Assign compliant endpoint tags to private policies’ alternative to ‘Check endpoint vulnerability severity’, authentication identity and endpoint posture solve different trust checks.
E:Endpoint tagging can evaluate the presence and properties of a required client certificate, a mechanism intended to identify managed endpoints that carry an enterprise-issued device credential rather than the requested ‘Check endpoint vulnerability severity’ control. The stated task instead is to apply stricter access to devices with high-severity unresolved vulnerabilities, and adjusting ‘Use a certificate-based posture check’ would not deliver ‘Check endpoint vulnerability severity’. For the ‘Use a certificate-based posture check’ alternative to ‘Check endpoint vulnerability severity’, certificate lifecycle and private-key protection matter separately from user authentication.
Question 367
In a change-control meeting for a dual-ISP FortiGate with BGP-learned routes to private sites, the team is closing the change after testing a design to resolve preference among otherwise comparable FortiGate route candidates. Which result supports closure?
- The routing table lists the default prefix associated with the intended SD-WAN zone.
- Private prefixes resolve to overlays while public prefixes use an approved DIA path.
- The candidate routes have intentional priority ordering reflected in the active table.
- Route and health-check diagnostics show the failed member and available alternate.
Explanation
Correct Answer
C:This checks ‘Review route priority’ at the correct operational boundary: route priority can provide an additional selection differentiator when distance and prefix do not distinguish alternatives. It demonstrates the specific capability to resolve preference among otherwise comparable FortiGate route candidates in a dual-ISP FortiGate with BGP-learned routes to private sites; deployment should additionally respect the constraint: Priority has meaning within the relevant route-selection context, not across unrelated prefixes.
Incorrect Answers
A:That observation belongs to ‘Install default route through an SD-WAN zone’, not ‘Review route priority’; its purpose is to make general internet destinations reachable without listing every WAN member as a separate policy interface, the underlying behavior is that a zone-based default static route gives SD-WAN a routing candidate for nonlocal destinations. The reviewer is instead verifying ‘Review route priority’ for a dual-ISP FortiGate with BGP-learned routes to private sites, not the evidence produced by ‘Install default route through an SD-WAN zone’.
B:That observation belongs to ‘Use split routing for private and internet destinations’, not ‘Review route priority’; its purpose is to send corporate destinations over overlay but ordinary internet traffic via local DIA, the underlying behavior is that destination-specific private routes and a general internet default route allow distinct traffic paths. The reviewer is instead verifying ‘Review route priority’ for a dual-ISP FortiGate with BGP-learned routes to private sites, not the evidence produced by ‘Use split routing for private and internet destinations’.
D:That observation belongs to ‘Inspect route withdrawal after health failure’, not ‘Review route priority’; its purpose is to explain why a failed WAN member stops being considered for new forwarding, the underlying behavior is that SD-WAN health failure can remove a member's route from the link load-balancing candidate set. The reviewer is instead verifying ‘Review route priority’ for a dual-ISP FortiGate with BGP-learned routes to private sites, not the evidence produced by ‘Inspect route withdrawal after health failure’.
Question 368
Within an IT team managing both BYOD browsers and corporate FortiClient installations, the administrator must protect an unmanaged Chromebook's HTTP and HTTPS browsing without installing FortiClient without redesigning unrelated services. Which option addresses the goal?
- Use preconfigured FortiClient installers
- Distribute proxy autoconfiguration settings
- Enroll an agentless web user
- Account for SSO precedence over other methods
- Configure SAML single sign-on
Explanation
Correct Answer
C:Agentless secure web gateway access uses explicit proxy steering rather than a full-device agent tunnel; that scope directly serves the goal to protect an unmanaged Chromebook's HTTP and HTTPS browsing without installing FortiClient in an IT team managing both BYOD browsers and corporate FortiClient installations. During implementation, agentless proxy steering does not automatically tunnel all nonweb IP traffic rather than treating the configuration label as proof of working service.
Incorrect Answers
A: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 ‘Enroll an agentless web user’ control. The stated task instead is to protect an unmanaged Chromebook's HTTP and HTTPS browsing without installing FortiClient, and adjusting ‘Use preconfigured FortiClient installers’ would not deliver ‘Enroll an agentless web user’. For the ‘Use preconfigured FortiClient installers’ alternative to ‘Enroll an agentless web user’, the device must be supported and permitted to run FortiClient.
B:A PAC-based proxy configuration tells supported browsers which web requests should use the cloud proxy, a mechanism intended to direct selected browser destinations to the FortiSASE secure web gateway rather than the requested ‘Enroll an agentless web user’ control. The stated task instead is to protect an unmanaged Chromebook's HTTP and HTTPS browsing without installing FortiClient, and adjusting ‘Distribute proxy autoconfiguration settings’ would not deliver ‘Enroll an agentless web user’. For the ‘Distribute proxy autoconfiguration settings’ alternative to ‘Enroll an agentless web user’, PAC logic and browser support should be tested for exceptions and split behavior.
D:Enabling FortiSASE SSO takes precedence over previously configured user authentication methods, a mechanism intended to avoid expecting local or RADIUS credentials to work after enabling SAML SSO rather than the requested ‘Enroll an agentless web user’ control. The stated task instead is to protect an unmanaged Chromebook's HTTP and HTTPS browsing without installing FortiClient, and adjusting ‘Account for SSO precedence over other methods’ would not deliver ‘Enroll an agentless web user’. For the ‘Account for SSO precedence over other methods’ alternative to ‘Enroll an agentless web user’, plan identity migration and test group mapping before enabling organizational SSO.
E: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 ‘Enroll an agentless web user’ control. The stated task instead is to protect an unmanaged Chromebook's HTTP and HTTPS browsing without installing FortiClient, and adjusting ‘Configure SAML single sign-on’ would not deliver ‘Enroll an agentless web user’. For the ‘Configure SAML single sign-on’ alternative to ‘Enroll an agentless web user’, the client browser must reach the IdP and the SP metadata and certificates must agree.
Question 369
For a cloud security migration with independent web and private-app policies, a technical review examines the control ‘Organize SASE users into policy groups’ for the objective to apply different web access controls to developers and finance staff. Which statement best describes what it changes?
- FortiSASE steers supported client traffic toward its security points of presence for consistent remote policy enforcement.
- FortiSASE must have an active provisioned instance with security points of presence before managed users can use its cloud enforcement.
- User groups provide a membership basis for matching different FortiSASE access policies.
- SIA and SPA use distinct routing and policy constructs despite sharing the FortiSASE service.
Explanation
Correct Answer
C:‘Organize SASE users into policy groups’ is used to apply different web access controls to developers and finance staff in a cloud security migration with independent web and private-app policies; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that group membership and policy matches differ for the two user populations; the rollout must also respect this constraint: Authentication source membership must be available for identity-based rule evaluation.
Incorrect Answers
A:The described behavior is part of ‘Choose an appropriate security PoP path’, used to bring roaming clients to cloud enforcement rather than hairpin every connection through headquarters instead of the role of ‘Organize SASE users into policy groups’. In contrast to ‘Choose an appropriate security PoP path’, ‘Organize SASE users into policy groups’ follows a different mechanism: user groups provide a membership basis for matching different FortiSASE access policies. Treating ‘Choose an appropriate security PoP path’ as equivalent would not address users from two departments unexpectedly receive the same unrestricted access policy in a cloud security migration with independent web and private-app policies.
B:The described behavior is part of ‘Verify FortiSASE service provisioning’, used to confirm the cloud security service is available before distributing client configurations instead of the role of ‘Organize SASE users into policy groups’. In contrast to ‘Verify FortiSASE service provisioning’, ‘Organize SASE users into policy groups’ follows a different mechanism: user groups provide a membership basis for matching different FortiSASE access policies. Treating ‘Verify FortiSASE service provisioning’ as equivalent would not address users from two departments unexpectedly receive the same unrestricted access policy in a cloud security migration with independent web and private-app policies.
D:The described behavior is part of ‘Separate internet and private access policies’, used to apply different controls to cloud web traffic and protected data-center applications instead of the role of ‘Organize SASE users into policy groups’. In contrast to ‘Separate internet and private access policies’, ‘Organize SASE users into policy groups’ follows a different mechanism: user groups provide a membership basis for matching different FortiSASE access policies. Treating ‘Separate internet and private access policies’ as equivalent would not address users from two departments unexpectedly receive the same unrestricted access policy in a cloud security migration with independent web and private-app policies.
Question 370
During an authorized lab exercise for a policy owner protecting HTTPS web sessions without blocking business use, the acceptance criteria require the team to inspect content carried inside HTTPS when allowed by policy and endpoint trust. Which control meets that requirement?
- Use cloud API CASB for SaaS data at rest
- Handle QUIC when deep inspection is required
- Use application category overrides
- Enable SSL deep inspection
Explanation
Correct Answer
D:Deep inspection decrypts eligible TLS sessions at the security service for content-aware scanning; that scope directly serves the goal to inspect content carried inside HTTPS when allowed by policy and endpoint trust in a policy owner protecting HTTPS web sessions without blocking business use. During implementation, certificate deployment and inspection exemptions must be handled to avoid breaking legitimate services rather than treating the configuration label as proof of working service.
Incorrect Answers
A: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 ‘Enable SSL deep inspection’ control. The stated task instead is to inspect content carried inside HTTPS when allowed by policy and endpoint trust, and adjusting ‘Use cloud API CASB for SaaS data at rest’ would not deliver ‘Enable SSL deep inspection’. For the ‘Use cloud API CASB for SaaS data at rest’ alternative to ‘Enable SSL deep inspection’, aPI authorization and provider support differ from inline real-time access controls.
B:Blocking QUIC can force compatible browsers to fall back from HTTP/3 to TLS connections inspectable by the configured SASE controls, a mechanism intended to keep SaaS web traffic on an inspectable TLS-over-TCP path for inline content controls rather than the requested ‘Enable SSL deep inspection’ control. The stated task instead is to inspect content carried inside HTTPS when allowed by policy and endpoint trust, and adjusting ‘Handle QUIC when deep inspection is required’ would not deliver ‘Enable SSL deep inspection’. For the ‘Handle QUIC when deep inspection is required’ alternative to ‘Enable SSL deep inspection’, application behavior and HTTPS fallback must be validated for the deployed browsers.
C:Application Control overrides provide a more specific action than a broad application-category setting, a mechanism intended to deny one high-risk application within an otherwise permitted collaboration category rather than the requested ‘Enable SSL deep inspection’ control. The stated task instead is to inspect content carried inside HTTPS when allowed by policy and endpoint trust, and adjusting ‘Use application category overrides’ would not deliver ‘Enable SSL deep inspection’. For the ‘Use application category overrides’ alternative to ‘Enable SSL deep inspection’, specific overrides should be tested against recognized application signatures.