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.
Question 371
For a dual-ISP FortiGate with BGP-learned routes to private sites, a review of the current state finds that internet sessions hairpin to the data center despite a planned local-breakout design. Which configuration area most directly addresses this?
- Investigate: Inspect route withdrawal after health failure
- Investigate: Review administrative distance
- Investigate: Configure a static partner route through overlay zone
- Investigate: Use split routing for private and internet destinations
Explanation
Correct Answer
D:The symptom identifies the missing operational behavior: destination-specific private routes and a general internet default route allow distinct traffic paths. For a dual-ISP FortiGate with BGP-learned routes to private sites, a direct diagnostic confirmation would be that private prefixes resolve to overlays while public prefixes use an approved DIA path; during repair, firewall policies must authorize both traffic classes with suitable inspection.
Incorrect Answers
A:SD-WAN health failure can remove a member's route from the link load-balancing candidate set, which serves the different requirement to explain why a failed WAN member stops being considered for new forwarding instead of the behavior delivered by ‘Use split routing for private and internet destinations’. If that component were misconfigured, a more characteristic finding would be that a path disappears from installed eligible routes when probes fail though interface carrier remains up; the actual report concerns internet sessions hairpin to the data center despite a planned local-breakout design at a dual-ISP FortiGate with BGP-learned routes to private sites.
B:Administrative distance influences which equal-prefix route source is preferred for installation, which serves the different requirement to choose between competing routes learned from different sources for the same prefix instead of the behavior delivered by ‘Use split routing for private and internet destinations’. If that component were misconfigured, a more characteristic finding would be that a backup static route remains installed ahead of an intended learned route due to distance; the actual report concerns internet sessions hairpin to the data center despite a planned local-breakout design at a dual-ISP FortiGate with BGP-learned routes to private sites.
C:A destination-specific static route referencing the overlay zone makes private routes accessible to SD-WAN selection, which serves the different requirement to reach an on-premises network across an IPsec overlay SD-WAN group instead of the behavior delivered by ‘Use split routing for private and internet destinations’. If that component were misconfigured, a more characteristic finding would be that the overlay tunnels are healthy but the remote private prefix lacks a usable route; the actual report concerns internet sessions hairpin to the data center despite a planned local-breakout design at a dual-ISP FortiGate with BGP-learned routes to private sites.
Question 372
During an authorized lab exercise for a security manager comparing weekly incident and traffic trends, the deployment standard specifies the control ‘Review application usage reports’ to identify which SaaS or application class dominates inspected remote traffic. Which functional description matches it?
- User traffic analytics aggregate bytes and sessions by identity and time for usage investigation.
- Security reporting aggregates action and threat categories so changes can be compared across time.
- Application analytics classify observed traffic into recognizable applications for reporting.
- Time-bound analytics separate incident-period activity from unrelated historical traffic.
Explanation
Correct Answer
C:‘Review application usage reports’ is used to identify which SaaS or application class dominates inspected remote traffic in a security manager comparing weekly incident and traffic trends; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that the report breaks down application categories and their traffic share for the period; the rollout must also respect this constraint: App recognition depends on available inspection and classification signals.
Incorrect Answers
A:The described behavior is part of ‘Compare user traffic volume trends’, used to find which authenticated population caused a sustained increase in cloud egress instead of the role of ‘Review application usage reports’. In contrast to ‘Compare user traffic volume trends’, ‘Review application usage reports’ follows a different mechanism: application analytics classify observed traffic into recognizable applications for reporting. Treating ‘Compare user traffic volume trends’ as equivalent would not address the help desk cannot determine whether collaboration usage or software updates caused an increase in a security manager comparing weekly incident and traffic trends.
B:The described behavior is part of ‘Trend security events by category’, used to measure whether a newly deployed protection reduced observed prohibited activity instead of the role of ‘Review application usage reports’. In contrast to ‘Trend security events by category’, ‘Review application usage reports’ follows a different mechanism: application analytics classify observed traffic into recognizable applications for reporting. Treating ‘Trend security events by category’ as equivalent would not address the help desk cannot determine whether collaboration usage or software updates caused an increase in a security manager comparing weekly incident and traffic trends.
D:The described behavior is part of ‘Use report time filters for incident scoping’, used to limit an investigation to the period in which an employee reported a cloud access failure instead of the role of ‘Review application usage reports’. In contrast to ‘Use report time filters for incident scoping’, ‘Review application usage reports’ follows a different mechanism: application analytics classify observed traffic into recognizable applications for reporting. Treating ‘Use report time filters for incident scoping’ as equivalent would not address the help desk cannot determine whether collaboration usage or software updates caused an increase in a security manager comparing weekly incident and traffic trends.
Question 373
During an authorized lab exercise for a contractor access program with different endpoint and connection policies, a pilot is about to enable ‘Assign compliant endpoint tags to private policies’. Which precaution is most closely tied to this choice?
- Identity login success should not be treated as proof of ongoing endpoint compliance.
- Version policy should account for supported platforms and enterprise patch baselines.
- Authentication identity and endpoint posture solve different trust checks.
- Product detection must match the supported platform and endpoint security configuration.
Explanation
Correct Answer
C:This condition matters for ‘Assign compliant endpoint tags to private policies’ because private access policies can use security posture tags as dynamic matching criteria. Omitting the relevant safeguard can produce a valid user's unmanaged laptop reaches a restricted private service despite failing device requirements; a successful test at a contractor access program with different endpoint and connection policies would instead demonstrate that only sessions presenting the approved endpoint posture tag match the private-access permit policy.
Incorrect Answers
A:The condition is associated with ‘Validate fresh endpoint posture telemetry’, a mechanism used to avoid relying on stale compliance information after an endpoint stops reporting to management instead of ‘Assign compliant endpoint tags to private policies’, because posture-based enforcement depends on updated FortiClient registration and local security-condition evaluation. For ‘Assign compliant endpoint tags to private policies’, unlike ‘Validate fresh endpoint posture telemetry’, the characteristic failure would be a valid user's unmanaged laptop reaches a restricted private service despite failing device requirements, which this alternative prerequisite would not directly address at a contractor access program with different endpoint and connection policies.
B:The condition is associated with ‘Use operating-system version posture’, a mechanism used to restrict access from endpoints that do not meet an approved operating-system baseline instead of ‘Assign compliant endpoint tags to private policies’, because OS-version posture criteria allow security rules to distinguish compliant from obsolete endpoint builds. For ‘Assign compliant endpoint tags to private policies’, unlike ‘Use operating-system version posture’, the characteristic failure would be a valid user's unmanaged laptop reaches a restricted private service despite failing device requirements, which this alternative prerequisite would not directly address at a contractor access program with different endpoint and connection policies.
D: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 ‘Assign compliant endpoint tags to private policies’, because a posture rule can evaluate security-product presence or protection state and classify the endpoint. For ‘Assign compliant endpoint tags to private policies’, unlike ‘Require endpoint antivirus status’, the characteristic failure would be a valid user's unmanaged laptop reaches a restricted private service despite failing device requirements, which this alternative prerequisite would not directly address at a contractor access program with different endpoint and connection policies.
Question 374
Within a video collaboration office using two simultaneously healthy circuits, the operator applies the control ‘Specify an SD-WAN zone preference’ as part of an effort to restrict an application to members grouped within a chosen logical zone. Which operating behavior should the team expect?
- Destination-address matching distinguishes route candidates for a specified network target.
- SD-WAN service rules are evaluated in configured order, so earlier matching entries can take precedence.
- Best Quality can evaluate jitter as the link-cost factor to compare delay variation.
- SD-WAN service diagnostics expose matched rules, interface lists, modes, and selected member status.
- An SD-WAN rule can prefer particular SD-WAN zones instead of enumerating every interface member.
Explanation
Correct Answer
E:‘Specify an SD-WAN zone preference’ is used to restrict an application to members grouped within a chosen logical zone in a video collaboration office using two simultaneously healthy circuits; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that the service rule references the intended overlay zone for candidate selection; the rollout must also respect this constraint: Zone preference and routing reachability must point to compatible paths.
Incorrect Answers
A:The described behavior is part of ‘Match destination address in an SD-WAN rule’, used to direct traffic to a particular partner subnet over an overlay while other traffic uses internet DIA instead of the role of ‘Specify an SD-WAN zone preference’. In contrast to ‘Match destination address in an SD-WAN rule’, ‘Specify an SD-WAN zone preference’ follows a different mechanism: an SD-WAN rule can prefer particular SD-WAN zones instead of enumerating every interface member. Treating ‘Match destination address in an SD-WAN rule’ as equivalent would not address a private-app rule keeps considering internet underlay members that are in the wrong zone in a video collaboration office using two simultaneously healthy circuits.
B:The described behavior is part of ‘Order specific SD-WAN rules above general matches’, used to ensure a narrow high-priority policy wins instead of a catch-all service rule instead of the role of ‘Specify an SD-WAN zone preference’. In contrast to ‘Order specific SD-WAN rules above general matches’, ‘Specify an SD-WAN zone preference’ follows a different mechanism: an SD-WAN rule can prefer particular SD-WAN zones instead of enumerating every interface member. Treating ‘Order specific SD-WAN rules above general matches’ as equivalent would not address a private-app rule keeps considering internet underlay members that are in the wrong zone in a video collaboration office using two simultaneously healthy circuits.
C:The described behavior is part of ‘Use Best Quality with jitter’, used to steer delay-sensitive conferencing toward the most stable path instead of the role of ‘Specify an SD-WAN zone preference’. In contrast to ‘Use Best Quality with jitter’, ‘Specify an SD-WAN zone preference’ follows a different mechanism: an SD-WAN rule can prefer particular SD-WAN zones instead of enumerating every interface member. Treating ‘Use Best Quality with jitter’ as equivalent would not address a private-app rule keeps considering internet underlay members that are in the wrong zone in a video collaboration office using two simultaneously healthy circuits.
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 ‘Specify an SD-WAN zone preference’. In contrast to ‘Test rule matching with service diagnostics’, ‘Specify an SD-WAN zone preference’ follows a different mechanism: an SD-WAN rule can prefer particular SD-WAN zones instead of enumerating every interface member. Treating ‘Test rule matching with service diagnostics’ as equivalent would not address a private-app rule keeps considering internet underlay members that are in the wrong zone in a video collaboration office using two simultaneously healthy circuits.
Question 375
During an authorized lab exercise for a regional hub where live transport measurements do not agree with the user complaint, a pilot is about to enable ‘Configure an SLA target for a health check’. Which precaution is most closely tied to this choice?
- Measurement alone and selecting a traffic-steering target are different steps.
- The measurement endpoint must be reliably reachable and appropriate to the application.
- Threshold values should reflect actual application tolerances and the monitored geography.
- Healthy alternate routing must exist for traffic to continue.
Explanation
Correct Answer
A:This condition matters for ‘Configure an SLA target for a health check’ because the SLA target defines tolerated delay, loss, or jitter against measured health-check values. Omitting the relevant safeguard can produce probe numbers are visible but the rule cannot distinguish qualifying and nonqualifying links; a successful test at a regional hub where live transport measurements do not agree with the user complaint would instead demonstrate that the health-check's target reports individual member pass or failure against stated limits.
Incorrect Answers
B:The condition is associated with ‘Select the correct probe server’, a mechanism used to measure user-relevant path health rather than only the nearest ISP hop instead of ‘Configure an SLA target for a health check’, because health checks against a representative reachable target include more of the application path than checks aimed only at the immediate gateway. For ‘Configure an SLA target for a health check’, unlike ‘Select the correct probe server’, the characteristic failure would be probe numbers are visible but the rule cannot distinguish qualifying and nonqualifying links, which this alternative prerequisite would not directly address at a regional hub where live transport measurements do not agree with the user complaint.
C:The condition is associated with ‘Avoid overly strict SLA targets’, a mechanism used to prevent both usable circuits from being excluded by unrealistic quality limits instead of ‘Configure an SLA target for a health check’, because targets tighter than achievable WAN conditions can cause otherwise connected members to fail policy qualification. For ‘Configure an SLA target for a health check’, unlike ‘Avoid overly strict SLA targets’, the characteristic failure would be probe numbers are visible but the rule cannot distinguish qualifying and nonqualifying links, which this alternative prerequisite would not directly address at a regional hub where live transport measurements do not agree with the user complaint.
D:The condition is associated with ‘Use probe loss to trigger failover’, a mechanism used to remove a genuinely unreachable transport from eligible load-balancing routes instead of ‘Configure an SLA target for a health check’, because failed health checks can withdraw the broken member's routes from the SD-WAN eligible path group. For ‘Configure an SLA target for a health check’, unlike ‘Use probe loss to trigger failover’, the characteristic failure would be probe numbers are visible but the rule cannot distinguish qualifying and nonqualifying links, which this alternative prerequisite would not directly address at a regional hub where live transport measurements do not agree with the user complaint.
Question 376
At a financial services branch where forwarding decisions disagree with interface health, a controlled test reveals that SYN packets arrive at the protected application but no responses reach the branch client. Which setting is the strongest first lead?
- Investigate: Prefer a more specific prefix
- Investigate: Configure a static partner route through overlay zone
- Investigate: Confirm return route for remote private access
- Investigate: Keep underlay route for tunnel peer
Explanation
Correct Answer
C:The symptom identifies the missing operational behavior: bidirectional reachability requires the remote hub or server-side router to return traffic to the client prefix. For a financial services branch where forwarding decisions disagree with interface health, a direct diagnostic confirmation would be that the remote forwarding table contains a route back to the branch network; during repair, forward-route success is insufficient for stateful end-to-end communication.
Incorrect Answers
A:Longest-prefix match chooses a more specific valid destination route ahead of a broader default, which serves the different requirement to send a partner network into a private tunnel even while default internet routing is present instead of the behavior delivered by ‘Confirm return route for remote private access’. If that component were misconfigured, a more characteristic finding would be that partner traffic exits public internet despite a required private-subnet route being missing; the actual report concerns SYN packets arrive at the protected application but no responses reach the branch client at a financial services branch where forwarding decisions disagree with interface health.
B:A destination-specific static route referencing the overlay zone makes private routes accessible to SD-WAN selection, which serves the different requirement to reach an on-premises network across an IPsec overlay SD-WAN group instead of the behavior delivered by ‘Confirm return route for remote private access’. If that component were misconfigured, a more characteristic finding would be that the overlay tunnels are healthy but the remote private prefix lacks a usable route; the actual report concerns SYN packets arrive at the protected application but no responses reach the branch client at a financial services branch where forwarding decisions disagree with interface health.
D:An overlay tunnel requires the public peer endpoint to remain reachable through an underlay path, which serves the different requirement to preserve transport reachability to an IPsec hub before private overlay traffic is steered instead of the behavior delivered by ‘Confirm return route for remote private access’. If that component were misconfigured, a more characteristic finding would be that the VPN repeatedly drops when the route to its public peer recursively follows the overlay itself; the actual report concerns SYN packets arrive at the protected application but no responses reach the branch client at a financial services branch where forwarding decisions disagree with interface health.
Question 377
For an operations hub with differentiated perimeter policies for WAN members, a technical review examines the control ‘Use a VLAN interface as a member’ for the objective to steer traffic over a tagged Ethernet handoff from an ISP. Which statement best describes what it changes?
- An SD-WAN member may reference a VLAN interface rather than only an untagged physical port.
- The cost field ranks SLA-qualified members for the Lowest Cost strategy, with smaller values preferred.
- Route-based IPsec tunnel interfaces can be members whose quality is measured and selected for overlay routing.
- Overlay zones provide distinct policy and route targets for tunnel traffic bound for private networks.
Explanation
Correct Answer
A:‘Use a VLAN interface as a member’ is used to steer traffic over a tagged Ethernet handoff from an ISP 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 the correct VLAN subinterface appears as an SD-WAN member; the rollout must also respect this constraint: The VLAN identifier and upstream trunk must agree before health checks can succeed.
Incorrect Answers
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 ‘Use a VLAN interface as a member’. In contrast to ‘Set member cost’, ‘Use a VLAN interface as a member’ follows a different mechanism: an SD-WAN member may reference a VLAN interface rather than only an untagged physical port. Treating ‘Set member cost’ as equivalent would not address the provider's tagged circuit is up at layer two but no logical tagged WAN is selectable in an operations hub with differentiated perimeter policies for WAN members.
C:The described behavior is part of ‘Use an IPsec interface as a member’, used to apply SD-WAN selection to redundant encrypted site-to-site paths instead of the role of ‘Use a VLAN interface as a member’. In contrast to ‘Use an IPsec interface as a member’, ‘Use a VLAN interface as a member’ follows a different mechanism: an SD-WAN member may reference a VLAN interface rather than only an untagged physical port. Treating ‘Use an IPsec interface as a member’ as equivalent would not address the provider's tagged circuit is up at layer two but no logical tagged WAN is selectable in an operations hub with differentiated perimeter policies for WAN members.
D: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 ‘Use a VLAN interface as a member’. In contrast to ‘Create a dedicated overlay zone’, ‘Use a VLAN interface as a member’ follows a different mechanism: an SD-WAN member may reference a VLAN interface rather than only an untagged physical port. Treating ‘Create a dedicated overlay zone’ as equivalent would not address the provider's tagged circuit is up at layer two but no logical tagged WAN is selectable in an operations hub with differentiated perimeter policies for WAN members.
Question 378
In a change-control meeting for a SASE change-control review using an authorized test identity, acceptance testing shows that an internal application is evaluated only as a generic public web destination. Which control should be investigated first?
- Investigate: Choose an appropriate security PoP path
- Investigate: Configure SASE certificate trust
- Investigate: Separate internet and private access policies
- Investigate: Verify FortiSASE service provisioning
Explanation
Correct Answer
C:The symptom identifies the missing operational behavior: SIA and SPA use distinct routing and policy constructs despite sharing the FortiSASE service. For a SASE change-control review using an authorized test identity, a direct diagnostic confirmation would be that the design documents and logs show separate SIA and SPA traffic paths; during repair, private resource reachability needs a supported SPA design in addition to SIA controls.
Incorrect Answers
A:FortiSASE steers supported client traffic toward its security points of presence for consistent remote policy enforcement, which serves the different requirement to bring roaming clients to cloud enforcement rather than hairpin every connection through headquarters instead of the behavior delivered by ‘Separate internet and private access policies’. If that component were misconfigured, a more characteristic finding would be that off-site users bypass cloud inspection while on-premises users remain protected; the actual report concerns an internal application is evaluated only as a generic public web destination at a SASE change-control review using an authorized test identity.
B:When deep inspection is used, managed endpoints need the appropriate inspection CA trust anchor, which serves the different requirement to avoid TLS warnings and ensure clients trust the cloud security inspection certificate instead of the behavior delivered by ‘Separate internet and private access policies’. If that component were misconfigured, a more characteristic finding would be that browsers show certificate warnings when protected HTTPS traffic is inspected; the actual report concerns an internal application is evaluated only as a generic public web destination at a SASE change-control review using an authorized test identity.
D:FortiSASE must have an active provisioned instance with security points of presence before managed users can use its cloud enforcement, which serves the different requirement to confirm the cloud security service is available before distributing client configurations instead of the behavior delivered by ‘Separate internet and private access policies’. If that component were misconfigured, a more characteristic finding would be that installation invitations are sent while the tenant has no functioning security PoP resources; the actual report concerns an internal application is evaluated only as a generic public web destination at a SASE change-control review using an authorized test identity.
Question 379
During an authorized lab exercise for a data analytics site comparing primary and backup overlay health, a reviewer needs proof the deployment can compare only the transport members serving a given application class. Which observation most directly validates it?
- Health-check status shows probe-derived latency and loss for each monitored member.
- The monitor lists the active overlay and backup overlay members.
- The failed member becomes ineligible while a healthy route is preferred.
- The high-variation path fails jitter while the stable path passes.
Explanation
Correct Answer
B:This checks ‘Assign the relevant member set to a health check’ at the correct operational boundary: an SD-WAN health check monitors the configured member interfaces instead of automatically representing every interface. It demonstrates the specific capability to compare only the transport members serving a given application class in a data analytics site comparing primary and backup overlay health; deployment should additionally respect the constraint: A measured SLA cannot evaluate a member that is not associated with the check.
Incorrect Answers
A:That observation belongs to ‘Create an active probe health check’, not ‘Assign the relevant member set to a health check’; its purpose is to measure reachability and delay even when no user sessions traverse a circuit, the underlying behavior is that active SD-WAN health checks send periodic probes to a designated target over monitored members. The reviewer is instead verifying ‘Assign the relevant member set to a health check’ for a data analytics site comparing primary and backup overlay health, not the evidence produced by ‘Create an active probe health check’.
C:That observation belongs to ‘Use probe loss to trigger failover’, not ‘Assign the relevant member set to a health check’; its purpose is to remove a genuinely unreachable transport from eligible load-balancing routes, the underlying behavior is that failed health checks can withdraw the broken member's routes from the SD-WAN eligible path group. The reviewer is instead verifying ‘Assign the relevant member set to a health check’ for a data analytics site comparing primary and backup overlay health, not the evidence produced by ‘Use probe loss to trigger failover’.
D:That observation belongs to ‘Set jitter SLA threshold’, not ‘Assign the relevant member set to a health check’; its purpose is to avoid a circuit whose packet-delay variation damages live audio, the underlying behavior is that a jitter target compares delay variation with an allowed maximum to qualify or reject a member. The reviewer is instead verifying ‘Assign the relevant member set to a health check’ for a data analytics site comparing primary and backup overlay health, not the evidence produced by ‘Set jitter SLA threshold’.
Question 380
Within a remote workforce with strict data-handling rules and encrypted web traffic, the configuration has been applied. Which measurement or record best confirms the goal to deny one high-risk application within an otherwise permitted collaboration category?
- Inspected HTTPS sessions show content controls operating with a trusted inspection CA.
- DNS query logs show the configured domain-category or threat action.
- Test sessions use the supported inspectable transport and trigger inline control actions.
- The named application override applies the intended block despite the wider category allowance.
- Outgoing SaaS requests contain the configured tenant-restriction header under the inline policy.
Explanation
Correct Answer
D:This checks ‘Use application category overrides’ at the correct operational boundary: Application Control overrides provide a more specific action than a broad application-category setting. It demonstrates the specific capability to deny one high-risk application within an otherwise permitted collaboration category in a remote workforce with strict data-handling rules and encrypted web traffic; deployment should additionally respect the constraint: Specific overrides should be tested against recognized application signatures.
Incorrect Answers
A:That observation belongs to ‘Enable SSL deep inspection’, not ‘Use application category overrides’; its purpose is to inspect content carried inside HTTPS when allowed by policy and endpoint trust, the underlying behavior is that deep inspection decrypts eligible TLS sessions at the security service for content-aware scanning. The reviewer is instead verifying ‘Use application category overrides’ for a remote workforce with strict data-handling rules and encrypted web traffic, not the evidence produced by ‘Enable SSL deep inspection’.
B:That observation belongs to ‘Use DNS filtering’, not ‘Use application category overrides’; its purpose is to stop requests to known malicious or restricted domains at the DNS layer, the underlying behavior is that DNS Filter evaluates domain lookup activity before a client establishes a normal destination session. The reviewer is instead verifying ‘Use application category overrides’ for a remote workforce with strict data-handling rules and encrypted web traffic, not the evidence produced by ‘Use DNS filtering’.
C:That observation belongs to ‘Handle QUIC when deep inspection is required’, not ‘Use application category overrides’; its purpose is to keep SaaS web traffic on an inspectable TLS-over-TCP path for inline content controls, the underlying behavior is that blocking QUIC can force compatible browsers to fall back from HTTP/3 to TLS connections inspectable by the configured SASE controls. The reviewer is instead verifying ‘Use application category overrides’ for a remote workforce with strict data-handling rules and encrypted web traffic, not the evidence produced by ‘Handle QUIC when deep inspection is required’.
E:That observation belongs to ‘Use inline CASB HTTP header restrictions’, not ‘Use application category overrides’; its purpose is to restrict which SaaS tenant a managed user may access by adjusting inspected web request headers, the underlying behavior is that Web Filter with Inline-CASB can insert or alter supported outbound HTTP headers to enforce SaaS tenant restrictions. The reviewer is instead verifying ‘Use application category overrides’ for a remote workforce with strict data-handling rules and encrypted web traffic, not the evidence produced by ‘Use inline CASB HTTP header restrictions’.