Question 740
Within a small datacenter with a physical circuit, a cellular backup and tagged VLAN handoffs, the operator applies the control ‘Disable a maintenance member’ as part of an effort to exclude a WAN circuit from SD-WAN decisions during scheduled carrier work. Which operating behavior should the team expect?
- A zone can contain one member, allowing special security or routing treatment for that interface.
- A link aggregation interface can be an SD-WAN member while LAG distributes frames across its constituent ports.
- Disabling an SD-WAN member removes it from eligible SD-WAN selection without requiring deletion of its configuration.
- Overlay zones provide distinct policy and route targets for tunnel traffic bound for private networks.
- A FortiExtender-provided network interface can participate as an SD-WAN member alongside wired transports.
Explanation
Correct Answer
C:‘Disable a maintenance member’ is used to exclude a WAN circuit from SD-WAN decisions during scheduled carrier work in a small datacenter with a physical circuit, a cellular backup and tagged VLAN handoffs; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that member status shows the maintenance circuit disabled and other members eligible; the rollout must also respect this constraint: Ensure remaining members provide viable routes and sufficient capacity.
Incorrect Answers
A:The described behavior is part of ‘Use an isolated single-member zone’, used to apply a dedicated policy to one exceptional transport while keeping other members grouped instead of the role of ‘Disable a maintenance member’. In contrast to ‘Use an isolated single-member zone’, ‘Disable a maintenance member’ follows a different mechanism: disabling an SD-WAN member removes it from eligible SD-WAN selection without requiring deletion of its configuration. Treating ‘Use an isolated single-member zone’ as equivalent would not address the drained circuit is still chosen for new flows during maintenance in a small datacenter with a physical circuit, a cellular backup and tagged VLAN handoffs.
B:The described behavior is part of ‘Use an aggregate interface as a member’, used to treat an LAG upstream handoff as a selectable SD-WAN transport instead of the role of ‘Disable a maintenance member’. In contrast to ‘Use an aggregate interface as a member’, ‘Disable a maintenance member’ follows a different mechanism: disabling an SD-WAN member removes it from eligible SD-WAN selection without requiring deletion of its configuration. Treating ‘Use an aggregate interface as a member’ as equivalent would not address the drained circuit is still chosen for new flows during maintenance in a small datacenter with a physical circuit, a cellular backup and tagged VLAN handoffs.
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 ‘Disable a maintenance member’. In contrast to ‘Create a dedicated overlay zone’, ‘Disable a maintenance member’ follows a different mechanism: disabling an SD-WAN member removes it from eligible SD-WAN selection without requiring deletion of its configuration. Treating ‘Create a dedicated overlay zone’ as equivalent would not address the drained circuit is still chosen for new flows during maintenance in a small datacenter with a physical circuit, a cellular backup and tagged VLAN handoffs.
E:The described behavior is part of ‘Use a FortiExtender interface member’, used to include a cellular backup path in SD-WAN selection instead of the role of ‘Disable a maintenance member’. In contrast to ‘Use a FortiExtender interface member’, ‘Disable a maintenance member’ follows a different mechanism: disabling an SD-WAN member removes it from eligible SD-WAN selection without requiring deletion of its configuration. Treating ‘Use a FortiExtender interface member’ as equivalent would not address the drained circuit is still chosen for new flows during maintenance in a small datacenter with a physical circuit, a cellular backup and tagged VLAN handoffs.
Question 741
During an authorized lab exercise for a contractor access program with different endpoint and connection policies, a pilot is about to enable ‘Require endpoint antivirus status’. Which precaution is most closely tied to this choice?
- Product detection must match the supported platform and endpoint security configuration.
- A process name alone is weaker than cryptographic proof of application integrity.
- This workflow depends on appropriate IPsec remote-agent support and endpoint profile setup.
- Authentication identity and endpoint posture solve different trust checks.
Explanation
Correct Answer
A:This condition matters for ‘Require endpoint antivirus status’ because a posture rule can evaluate security-product presence or protection state and classify the endpoint. Omitting the relevant safeguard can produce a laptop with disabled endpoint protection remains in the trusted access group; a successful test at a contractor access program with different endpoint and connection policies would instead demonstrate that the posture telemetry classifies the device according to antivirus status.
Incorrect Answers
B:The condition is associated with ‘Check a required running process’, a mechanism used to permit an internal app only when its approved endpoint security agent is running instead of ‘Require endpoint antivirus status’, because process-presence conditions can contribute to device posture evaluation where supported. For ‘Require endpoint antivirus status’, unlike ‘Check a required running process’, the characteristic failure would be a laptop with disabled endpoint protection remains in the trusted access group, which this alternative prerequisite would not directly address at a contractor access program with different endpoint and connection policies.
C:The condition is associated with ‘Configure pre-connection posture enforcement’, a mechanism used to block an untrusted FortiClient endpoint before it establishes its protected cloud tunnel instead of ‘Require endpoint antivirus status’, because a configured pre-connection check can allow or deny a tunnel attempt based on an assigned posture tag. For ‘Require endpoint antivirus status’, unlike ‘Configure pre-connection posture enforcement’, the characteristic failure would be a laptop with disabled endpoint protection remains in the trusted access group, 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 ‘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 ‘Require endpoint antivirus status’, because private access policies can use security posture tags as dynamic matching criteria. For ‘Require endpoint antivirus status’, unlike ‘Assign compliant endpoint tags to private policies’, the characteristic failure would be a laptop with disabled endpoint protection remains in the trusted access group, which this alternative prerequisite would not directly address at a contractor access program with different endpoint and connection policies.
Question 742
For a test lab containing an overlay tunnel and two underlay next hops, a maintenance plan requires the firewall team to avoid misdiagnosing unreachable prefixes as an economic-selection problem. Which choice is appropriate?
- Confirm return route for remote private access
- Use routing diagnostics before changing SD-WAN cost
- Inspect route withdrawal after health failure
- Review administrative distance
Explanation
Correct Answer
B:Route inspection distinguishes absent routes from member cost or performance rankings; that scope directly serves the goal to avoid misdiagnosing unreachable prefixes as an economic-selection problem in a test lab containing an overlay tunnel and two underlay next hops. During implementation, cost only influences relevant strategies among candidates that are routable and eligible rather than treating the configuration label as proof of working service.
Incorrect Answers
A:Bidirectional reachability requires the remote hub or server-side router to return traffic to the client prefix, a mechanism intended to repair one-way traffic where forward packets reach the data center but replies do not rather than the requested ‘Use routing diagnostics before changing SD-WAN cost’ control. The stated task instead is to avoid misdiagnosing unreachable prefixes as an economic-selection problem, and adjusting ‘Confirm return route for remote private access’ would not deliver ‘Use routing diagnostics before changing SD-WAN cost’. For the ‘Confirm return route for remote private access’ alternative to ‘Use routing diagnostics before changing SD-WAN cost’, forward-route success is insufficient for stateful end-to-end communication.
C: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 ‘Use routing diagnostics before changing SD-WAN cost’ control. The stated task instead is to avoid misdiagnosing unreachable prefixes as an economic-selection problem, and adjusting ‘Inspect route withdrawal after health failure’ would not deliver ‘Use routing diagnostics before changing SD-WAN cost’. For the ‘Inspect route withdrawal after health failure’ alternative to ‘Use routing diagnostics before changing SD-WAN cost’, a failed SLA state can change route eligibility without a physical link-down event.
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 ‘Use routing diagnostics before changing SD-WAN cost’ control. The stated task instead is to avoid misdiagnosing unreachable prefixes as an economic-selection problem, and adjusting ‘Review administrative distance’ would not deliver ‘Use routing diagnostics before changing SD-WAN cost’. For the ‘Review administrative distance’ alternative to ‘Use routing diagnostics before changing SD-WAN cost’, specificity is considered before comparing administrative distance on different prefix lengths.
Question 743
At a finance team that uses multiple approved SaaS applications, a support engineer needs to verify that ‘Apply remote browser isolation for risky sites’ is active for the goal to isolate web rendering from the endpoint when access is required to a questionable website. Which observation is decisive?
- The connected SaaS application's API scans produce inventory and findings about stored content.
- The site is rendered within the configured isolation workflow rather than the local browser engine.
- An IPS security event identifies the signature and the resulting block or monitor action.
- Outgoing SaaS requests contain the configured tenant-restriction header under the inline policy.
Explanation
Correct Answer
B:This checks ‘Apply remote browser isolation for risky sites’ at the correct operational boundary: remote Browser Isolation executes supported browsing in an isolated remote context and streams a safer representation. It demonstrates the specific capability to isolate web rendering from the endpoint when access is required to a questionable website in a finance team that uses multiple approved SaaS applications; deployment should additionally respect the constraint: RBI mitigates browser-execution exposure; it is not a substitute for identity verification.
Incorrect Answers
A:That observation belongs to ‘Use cloud API CASB for SaaS data at rest’, not ‘Apply remote browser isolation for risky sites’; its purpose is to inspect cloud-service data through supported SaaS APIs rather than only inline user sessions, the underlying behavior is that aPI-connected CASB can examine supported SaaS tenant content and events without requiring every action to cross the inline proxy. The reviewer is instead verifying ‘Apply remote browser isolation for risky sites’ for a finance team that uses multiple approved SaaS applications, not the evidence produced by ‘Use cloud API CASB for SaaS data at rest’.
C:That observation belongs to ‘Enable intrusion prevention’, not ‘Apply remote browser isolation for risky sites’; its purpose is to detect and block network exploits recognized by attack signatures or protocol decoders, the underlying behavior is that IPS analyzes supported traffic patterns against intrusion-detection signatures and configured actions. The reviewer is instead verifying ‘Apply remote browser isolation for risky sites’ for a finance team that uses multiple approved SaaS applications, not the evidence produced by ‘Enable intrusion prevention’.
D:That observation belongs to ‘Use inline CASB HTTP header restrictions’, not ‘Apply remote browser isolation for risky sites’; 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 ‘Apply remote browser isolation for risky sites’ for a finance team that uses multiple approved SaaS applications, not the evidence produced by ‘Use inline CASB HTTP header restrictions’.
Question 744
In a change-control meeting for a hub-and-spoke network with internet breakout and private IPsec overlays, a colleague challenges the proposed control ‘Compare routing table and SD-WAN rule decision’ for the requirement to find which stage prevents a preferred member from being used. Which explanation accurately describes its behavior?
- Equal Cost Multi-Path allows compatible routes to coexist as candidates when distance and priority permit.
- Policy route and SD-WAN service rules can influence forwarding decisions beyond basic destination-table lookup.
- SD-WAN candidate preference works only after routing makes a compatible egress path available.
- SD-WAN health failure can remove a member's route from the link load-balancing candidate set.
Explanation
Correct Answer
C:‘Compare routing table and SD-WAN rule decision’ is used to find which stage prevents a preferred member from being used in a hub-and-spoke network with internet breakout and private IPsec overlays; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that routing diagnostics and service diagnostics together reveal the incompatible candidate; the rollout must also respect this constraint: Changing a preference list alone cannot repair a missing route.
Incorrect Answers
A:The described behavior is part of ‘Use ECMP-compatible route candidates’, used to make multiple eligible equal-cost paths available for subsequent SD-WAN decisions instead of the role of ‘Compare routing table and SD-WAN rule decision’. In contrast to ‘Use ECMP-compatible route candidates’, ‘Compare routing table and SD-WAN rule decision’ follows a different mechanism: SD-WAN candidate preference works only after routing makes a compatible egress path available. Treating ‘Use ECMP-compatible route candidates’ as equivalent would not address an SD-WAN service names wan2 first but forwarding still excludes wan2 in a hub-and-spoke network with internet breakout and private IPsec overlays.
B:The described behavior is part of ‘Validate policy routing and SD-WAN interaction’, used to identify why a matching policy-route decision changes normal egress selection instead of the role of ‘Compare routing table and SD-WAN rule decision’. In contrast to ‘Validate policy routing and SD-WAN interaction’, ‘Compare routing table and SD-WAN rule decision’ follows a different mechanism: SD-WAN candidate preference works only after routing makes a compatible egress path available. Treating ‘Validate policy routing and SD-WAN interaction’ as equivalent would not address an SD-WAN service names wan2 first but forwarding still excludes wan2 in a hub-and-spoke network with internet breakout and private IPsec overlays.
D:The described behavior is part of ‘Inspect route withdrawal after health failure’, used to explain why a failed WAN member stops being considered for new forwarding instead of the role of ‘Compare routing table and SD-WAN rule decision’. In contrast to ‘Inspect route withdrawal after health failure’, ‘Compare routing table and SD-WAN rule decision’ follows a different mechanism: SD-WAN candidate preference works only after routing makes a compatible egress path available. Treating ‘Inspect route withdrawal after health failure’ as equivalent would not address an SD-WAN service names wan2 first but forwarding still excludes wan2 in a hub-and-spoke network with internet breakout and private IPsec overlays.
Question 745
Within a FortiSASE deployment that protects a central application behind a FortiGate, the team wants to avoid an ineffective configuration of ‘Use ZTNA application proxy for a protected TCP app’. Which consideration deserves attention?
- Routing reachability and firewall permission must both be satisfied.
- Branch integration requires transport reachability and matching on-ramp security policy.
- The FortiGate ZTNA server, access policy, and required client posture must be configured.
- Choose the private-access architecture according to protocol and trust requirements.
- Name resolution must be reachable over the chosen private access topology.
Explanation
Correct Answer
C:This condition matters for ‘Use ZTNA application proxy for a protected TCP app’ because ZTNA private access targets authorized TCP applications rather than granting generic network reachability. Omitting the relevant safeguard can produce an administrator offers broad subnet access when only one protected TCP service is approved; a successful test at a FortiSASE deployment that protects a central application behind a FortiGate would instead demonstrate that the designated protected TCP service is reachable through the authorized ZTNA proxy.
Incorrect Answers
A:The condition is associated with ‘Allow security PoP access to private applications’, a mechanism used to permit cloud-originated SPA traffic through the data-center firewall policy instead of ‘Use ZTNA application proxy for a protected TCP app’, because hub-side FortiGate policies authorize FortiSASE service traffic toward the protected servers. For ‘Use ZTNA application proxy for a protected TCP app’, unlike ‘Allow security PoP access to private applications’, the characteristic failure would be an administrator offers broad subnet access when only one protected TCP service is approved, which this alternative prerequisite would not directly address at a FortiSASE deployment that protects a central application behind a FortiGate.
B:The condition is associated with ‘Integrate branch SD-WAN with FortiSASE on-ramp’, a mechanism used to send on-site user internet traffic to FortiSASE cloud inspection using a supported branch edge instead of ‘Use ZTNA application proxy for a protected TCP app’, because a supported FortiGate branch on-ramp can steer site traffic to FortiSASE enforcement PoPs. For ‘Use ZTNA application proxy for a protected TCP app’, unlike ‘Integrate branch SD-WAN with FortiSASE on-ramp’, the characteristic failure would be an administrator offers broad subnet access when only one protected TCP service is approved, which this alternative prerequisite would not directly address at a FortiSASE deployment that protects a central application behind a FortiGate.
D:The condition is associated with ‘Use SD-WAN private access for TCP and UDP’, a mechanism used to extend private resource connectivity beyond the TCP-focused ZTNA access proxy model instead of ‘Use ZTNA application proxy for a protected TCP app’, because an SD-WAN-based SPA design can provide routed access to private TCP and UDP applications. For ‘Use ZTNA application proxy for a protected TCP app’, unlike ‘Use SD-WAN private access for TCP and UDP’, the characteristic failure would be an administrator offers broad subnet access when only one protected TCP service is approved, which this alternative prerequisite would not directly address at a FortiSASE deployment that protects a central application behind a FortiGate.
E:The condition is associated with ‘Configure DNS resolution for private names’, a mechanism used to let remote users resolve internal application FQDNs to protected addresses instead of ‘Use ZTNA application proxy for a protected TCP app’, because private or split-DNS settings direct internal-name lookups to appropriate enterprise DNS servers. For ‘Use ZTNA application proxy for a protected TCP app’, unlike ‘Configure DNS resolution for private names’, the characteristic failure would be an administrator offers broad subnet access when only one protected TCP service is approved, which this alternative prerequisite would not directly address at a FortiSASE deployment that protects a central application behind a FortiGate.
Question 746
In a change-control meeting for a security team classifying devices by their current local protection state, the team is closing the change after testing a design to permit an internal app only when its approved endpoint security agent is running. Which result supports closure?
- Registration health and a recent tag update corroborate the current device state.
- The posture rule changes endpoint classification when the process stops or resumes.
- Only sessions presenting the approved endpoint posture tag match the private-access permit policy.
- The device's posture classification reflects the configured vulnerability severity.
Explanation
Correct Answer
B:This checks ‘Check a required running process’ at the correct operational boundary: process-presence conditions can contribute to device posture evaluation where supported. It demonstrates the specific capability to permit an internal app only when its approved endpoint security agent is running in a security team classifying devices by their current local protection state; deployment should additionally respect the constraint: A process name alone is weaker than cryptographic proof of application integrity.
Incorrect Answers
A:That observation belongs to ‘Validate fresh endpoint posture telemetry’, not ‘Check a required running process’; its purpose is to avoid relying on stale compliance information after an endpoint stops reporting to management, the underlying behavior is that posture-based enforcement depends on updated FortiClient registration and local security-condition evaluation. The reviewer is instead verifying ‘Check a required running process’ for a security team classifying devices by their current local protection state, not the evidence produced by ‘Validate fresh endpoint posture telemetry’.
C:That observation belongs to ‘Assign compliant endpoint tags to private policies’, not ‘Check a required running process’; its purpose is to grant sensitive private access only to managed devices meeting specified security conditions, the underlying behavior is that private access policies can use security posture tags as dynamic matching criteria. The reviewer is instead verifying ‘Check a required running process’ for a security team classifying devices by their current local protection state, not the evidence produced by ‘Assign compliant endpoint tags to private policies’.
D:That observation belongs to ‘Check endpoint vulnerability severity’, not ‘Check a required running process’; its purpose is to apply stricter access to devices with high-severity unresolved vulnerabilities, the underlying behavior is that vulnerability-related posture information can be used to classify a risky endpoint for conditional access. The reviewer is instead verifying ‘Check a required running process’ for a security team classifying devices by their current local protection state, not the evidence produced by ‘Check endpoint vulnerability severity’.
Question 747
In a change-control meeting for a small datacenter with a physical circuit, a cellular backup and tagged VLAN handoffs, the team is closing the change after testing a design to apply SD-WAN selection to redundant encrypted site-to-site paths. Which result supports closure?
- The tunnel interface is listed as an SD-WAN overlay member.
- Member status shows the maintenance circuit disabled and other members eligible.
- The member inventory shows wan2 inside the internet transport zone.
- The correct VLAN subinterface appears as an SD-WAN member.
Explanation
Correct Answer
A:This checks ‘Use an IPsec interface as a member’ at the correct operational boundary: route-based IPsec tunnel interfaces can be members whose quality is measured and selected for overlay routing. It demonstrates the specific capability to apply SD-WAN selection to redundant encrypted site-to-site paths in a small datacenter with a physical circuit, a cellular backup and tagged VLAN handoffs; deployment should additionally respect the constraint: Bring up the route-based tunnel and verify selectors and reachability independently.
Incorrect Answers
B:That observation belongs to ‘Disable a maintenance member’, not ‘Use an IPsec interface as a member’; its purpose is to exclude a WAN circuit from SD-WAN decisions during scheduled carrier work, the underlying behavior is that disabling an SD-WAN member removes it from eligible SD-WAN selection without requiring deletion of its configuration. The reviewer is instead verifying ‘Use an IPsec interface as a member’ for a small datacenter with a physical circuit, a cellular backup and tagged VLAN handoffs, not the evidence produced by ‘Disable a maintenance member’.
C:That observation belongs to ‘Assign members to the intended zone’, not ‘Use an IPsec interface as a member’; its purpose is to put two ISP circuits in the internet transport zone rather than the private-overlay group, the underlying behavior is that a member's zone association determines which zone-based routes and policies can use that interface. The reviewer is instead verifying ‘Use an IPsec interface as a member’ for a small datacenter with a physical circuit, a cellular backup and tagged VLAN handoffs, not the evidence produced by ‘Assign members to the intended zone’.
D:That observation belongs to ‘Use a VLAN interface as a member’, not ‘Use an IPsec interface as a member’; its purpose is to steer traffic over a tagged Ethernet handoff from an ISP, the underlying behavior is that an SD-WAN member may reference a VLAN interface rather than only an untagged physical port. The reviewer is instead verifying ‘Use an IPsec interface as a member’ for a small datacenter with a physical circuit, a cellular backup and tagged VLAN handoffs, not the evidence produced by ‘Use a VLAN interface as a member’.
Question 748
For a data analytics site comparing primary and backup overlay health, a technical review examines the control ‘Assign the relevant member set to a health check’ for the objective to compare only the transport members serving a given application class. Which statement best describes what it changes?
- Health checks against a representative reachable target include more of the application path than checks aimed only at the immediate gateway.
- Failed health checks can withdraw the broken member's routes from the SD-WAN eligible path group.
- Separate health checks can reveal that a circuit reaches one remote service well but another poorly.
- An SD-WAN health check monitors the configured member interfaces instead of automatically representing every interface.
Explanation
Correct Answer
D:‘Assign the relevant member set to a health check’ is used to compare only the transport members serving a given application class in a data analytics site comparing primary and backup overlay health; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that the monitor lists the active overlay and backup overlay members; the rollout must also respect this constraint: A measured SLA cannot evaluate a member that is not associated with the check.
Incorrect Answers
A: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 ‘Assign the relevant member set to a health check’. In contrast to ‘Select the correct probe server’, ‘Assign the relevant member set to a health check’ follows a different mechanism: an SD-WAN health check monitors the configured member interfaces instead of automatically representing every interface. Treating ‘Select the correct probe server’ as equivalent would not address a backup VPN is never included in the app's observed SLA metrics in a data analytics site comparing primary and backup overlay health.
B:The described behavior is part of ‘Use probe loss to trigger failover’, used to remove a genuinely unreachable transport from eligible load-balancing routes instead of the role of ‘Assign the relevant member set to a health check’. In contrast to ‘Use probe loss to trigger failover’, ‘Assign the relevant member set to a health check’ follows a different mechanism: an SD-WAN health check monitors the configured member interfaces instead of automatically representing every interface. Treating ‘Use probe loss to trigger failover’ as equivalent would not address a backup VPN is never included in the app's observed SLA metrics in a data analytics site comparing primary and backup overlay health.
C:The described behavior is part of ‘Compare health across multiple SLAs’, used to measure distinct service destinations separately rather than treating the internet as one uniform path instead of the role of ‘Assign the relevant member set to a health check’. In contrast to ‘Compare health across multiple SLAs’, ‘Assign the relevant member set to a health check’ follows a different mechanism: an SD-WAN health check monitors the configured member interfaces instead of automatically representing every interface. Treating ‘Compare health across multiple SLAs’ as equivalent would not address a backup VPN is never included in the app's observed SLA metrics in a data analytics site comparing primary and backup overlay health.
Question 749
For a security operations review of remote-user threat detections, a technical review examines the control ‘Inspect antivirus detection events’ for the objective to identify which inspected download was blocked for malware and under which policy. Which statement best describes what it changes?
- AV logs identify signature or file detections and the security action applied to a session.
- DNS security logs record affected domain requests and configured malicious-domain actions.
- Authentication events reveal the login or SSO step at which a FortiSASE user failed to establish identity.
- IPS events contain the signature context and configured security response for detected traffic.
Explanation
Correct Answer
A:‘Inspect antivirus detection events’ is used to identify which inspected download was blocked for malware and under which policy in a security operations review of remote-user threat detections; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that a time-matched AV event shows the detection and enforced action for the download; the rollout must also respect this constraint: A traffic deny log by itself does not establish that antivirus detected malware.
Incorrect Answers
B:The described behavior is part of ‘Inspect DNS-filter threat events’, used to identify blocked malicious name resolution before the browser opens a TCP session instead of the role of ‘Inspect antivirus detection events’. In contrast to ‘Inspect DNS-filter threat events’, ‘Inspect antivirus detection events’ follows a different mechanism: aV logs identify signature or file detections and the security action applied to a session. Treating ‘Inspect DNS-filter threat events’ as equivalent would not address a user reports a blocked download but only aggregate bandwidth charts were examined in a security operations review of remote-user threat detections.
C:The described behavior is part of ‘Correlate cloud authentication events’, used to distinguish failed identity sign-in from a denied security profile decision instead of the role of ‘Inspect antivirus detection events’. In contrast to ‘Correlate cloud authentication events’, ‘Inspect antivirus detection events’ follows a different mechanism: aV logs identify signature or file detections and the security action applied to a session. Treating ‘Correlate cloud authentication events’ as equivalent would not address a user reports a blocked download but only aggregate bandwidth charts were examined in a security operations review of remote-user threat detections.
D:The described behavior is part of ‘Inspect IPS threat logs’, used to verify whether an exploit signature triggered inspection rather than a generic connectivity failure instead of the role of ‘Inspect antivirus detection events’. In contrast to ‘Inspect IPS threat logs’, ‘Inspect antivirus detection events’ follows a different mechanism: aV logs identify signature or file detections and the security action applied to a session. Treating ‘Inspect IPS threat logs’ as equivalent would not address a user reports a blocked download but only aggregate bandwidth charts were examined in a security operations review of remote-user threat detections.
Question 750
During an authorized lab exercise for a global remote-user rollout with separate employee and contractor policies, a pilot is about to enable ‘Import users through LDAP’. Which precaution is most closely tied to this choice?
- The client browser must reach the IdP and the SP metadata and certificates must agree.
- FortiSASE must reach the directory service through its permitted network path.
- PAC logic and browser support should be tested for exceptions and split behavior.
- Profile assignment must be checked separately from cloud traffic-policy ordering.
Explanation
Correct Answer
B:This condition matters for ‘Import users through LDAP’ because LDAP integration allows FortiSASE to reference directory accounts and user groups. Omitting the relevant safeguard can produce directory staff are not visible to SASE policy although the directory contains them; a successful test at a global remote-user rollout with separate employee and contractor policies would instead demonstrate that the configured LDAP source resolves expected groups and authenticated users.
Incorrect Answers
A:The condition is associated with ‘Configure SAML single sign-on’, a mechanism used to let staff authenticate to FortiSASE through the corporate identity provider instead of ‘Import users through LDAP’, because FortiSASE acts as a SAML service provider while the configured IdP issues assertions for authenticated users. For ‘Import users through LDAP’, unlike ‘Configure SAML single sign-on’, the characteristic failure would be directory staff are not visible to SASE policy although the directory contains them, which this alternative prerequisite would not directly address at a global remote-user rollout with separate employee and contractor policies.
C:The condition is associated with ‘Distribute proxy autoconfiguration settings’, a mechanism used to direct selected browser destinations to the FortiSASE secure web gateway instead of ‘Import users through LDAP’, because a PAC-based proxy configuration tells supported browsers which web requests should use the cloud proxy. For ‘Import users through LDAP’, unlike ‘Distribute proxy autoconfiguration settings’, the characteristic failure would be directory staff are not visible to SASE policy although the directory contains them, which this alternative prerequisite would not directly address at a global remote-user rollout with separate employee and contractor policies.
D:The condition is associated with ‘Match endpoint profiles to the correct user group’, a mechanism used to deliver one set of endpoint controls to contractors and a stricter set to employees instead of ‘Import users through LDAP’, because endpoint profiles can be assigned according to relevant groups or administrative selection. For ‘Import users through LDAP’, unlike ‘Match endpoint profiles to the correct user group’, the characteristic failure would be directory staff are not visible to SASE policy although the directory contains them, which this alternative prerequisite would not directly address at a global remote-user rollout with separate employee and contractor policies.