Fortinet NSE5_SSE_AD-7.6 (Fortinet NSE 5 - FortiSASE and SD-WAN 7.6 Core Administrator) Practice Test 16

Question 150

In a change-control meeting for an off-site workforce where some endpoints fail compliance verification, the proposed control is ‘Validate fresh endpoint posture telemetry’. Which deployment condition is particularly relevant?

  1. Product detection must match the supported platform and endpoint security configuration.
  2. Certificate lifecycle and private-key protection matter separately from user authentication.
  3. Version policy should account for supported platforms and enterprise patch baselines.
  4. Identity login success should not be treated as proof of ongoing endpoint compliance.

Explanation

Correct Answer

D:

This condition matters for ‘Validate fresh endpoint posture telemetry’ because posture-based enforcement depends on updated FortiClient registration and local security-condition evaluation. Omitting the relevant safeguard can produce a disconnected laptop keeps an old compliant tag while its protection status has changed; a successful test at an off-site workforce where some endpoints fail compliance verification would instead demonstrate that registration health and a recent tag update corroborate the current device state.

Incorrect Answers

A:

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 ‘Validate fresh endpoint posture telemetry’, because a posture rule can evaluate security-product presence or protection state and classify the endpoint. For ‘Validate fresh endpoint posture telemetry’, unlike ‘Require endpoint antivirus status’, the characteristic failure would be a disconnected laptop keeps an old compliant tag while its protection status has changed, which this alternative prerequisite would not directly address at an off-site workforce where some endpoints fail compliance verification.

B:

The condition is associated with ‘Use a certificate-based posture check’, a mechanism used to identify managed endpoints that carry an enterprise-issued device credential instead of ‘Validate fresh endpoint posture telemetry’, because endpoint tagging can evaluate the presence and properties of a required client certificate. For ‘Validate fresh endpoint posture telemetry’, unlike ‘Use a certificate-based posture check’, the characteristic failure would be a disconnected laptop keeps an old compliant tag while its protection status has changed, which this alternative prerequisite would not directly address at an off-site workforce where some endpoints fail compliance verification.

C:

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 ‘Validate fresh endpoint posture telemetry’, because OS-version posture criteria allow security rules to distinguish compliant from obsolete endpoint builds. For ‘Validate fresh endpoint posture telemetry’, unlike ‘Use operating-system version posture’, the characteristic failure would be a disconnected laptop keeps an old compliant tag while its protection status has changed, which this alternative prerequisite would not directly address at an off-site workforce where some endpoints fail compliance verification.

Question 151

For a test lab containing an overlay tunnel and two underlay next hops, a maintenance plan requires the firewall team to explain why a failed WAN member stops being considered for new forwarding. Which choice is appropriate?

  1. Check the route's next hop reachability
  2. Confirm return route for remote private access
  3. Inspect route withdrawal after health failure
  4. Use split routing for private and internet destinations

Explanation

Correct Answer

C:

SD-WAN health failure can remove a member's route from the link load-balancing candidate set; that scope directly serves the goal to explain why a failed WAN member stops being considered for new forwarding in a test lab containing an overlay tunnel and two underlay next hops. During implementation, a failed SLA state can change route eligibility without a physical link-down event rather than treating the configuration label as proof of working service.

Incorrect Answers

A:

Forwarding requires that the selected next hop can be resolved and reached via the member, a mechanism intended to differentiate a configured route from an actually usable gateway on a WAN link rather than the requested ‘Inspect route withdrawal after health failure’ control. The stated task instead is to explain why a failed WAN member stops being considered for new forwarding, and adjusting ‘Check the route's next hop reachability’ would not deliver ‘Inspect route withdrawal after health failure’. For the ‘Check the route's next hop reachability’ alternative to ‘Inspect route withdrawal after health failure’, a route's presence alone does not establish next-hop liveness.

B:

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 ‘Inspect route withdrawal after health failure’ control. The stated task instead is to explain why a failed WAN member stops being considered for new forwarding, and adjusting ‘Confirm return route for remote private access’ would not deliver ‘Inspect route withdrawal after health failure’. For the ‘Confirm return route for remote private access’ alternative to ‘Inspect route withdrawal after health failure’, forward-route success is insufficient for stateful end-to-end communication.

D:

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 ‘Inspect route withdrawal after health failure’ control. The stated task instead is to explain why a failed WAN member stops being considered for new forwarding, and adjusting ‘Use split routing for private and internet destinations’ would not deliver ‘Inspect route withdrawal after health failure’. For the ‘Use split routing for private and internet destinations’ alternative to ‘Inspect route withdrawal after health failure’, firewall policies must authorize both traffic classes with suitable inspection.

Question 152

In a change-control meeting for a branch experiencing intermittent packet loss during video meetings, a design review calls for a way to protect application sessions from a link that intermittently drops packets. What should the operator configure?

  1. Select the correct probe server
  2. Create an active probe health check
  3. Set packet-loss SLA threshold
  4. Use SLA measurements for best-quality steering

Explanation

Correct Answer

C:

A loss target evaluates the fraction of missing probes or measured packets before declaring SLA compliance; that scope directly serves the goal to protect application sessions from a link that intermittently drops packets in a branch experiencing intermittent packet loss during video meetings. During implementation, check loss independently of latency and jitter instead of inferring it from link-up state rather than treating the configuration label as proof of working service.

Incorrect Answers

A:

Health checks against a representative reachable target include more of the application path than checks aimed only at the immediate gateway, a mechanism intended to measure user-relevant path health rather than only the nearest ISP hop rather than the requested ‘Set packet-loss SLA threshold’ control. The stated task instead is to protect application sessions from a link that intermittently drops packets, and adjusting ‘Select the correct probe server’ would not deliver ‘Set packet-loss SLA threshold’. For the ‘Select the correct probe server’ alternative to ‘Set packet-loss SLA threshold’, the measurement endpoint must be reliably reachable and appropriate to the application.

B:

Active SD-WAN health checks send periodic probes to a designated target over monitored members, a mechanism intended to measure reachability and delay even when no user sessions traverse a circuit rather than the requested ‘Set packet-loss SLA threshold’ control. The stated task instead is to protect application sessions from a link that intermittently drops packets, and adjusting ‘Create an active probe health check’ would not deliver ‘Set packet-loss SLA threshold’. For the ‘Create an active probe health check’ alternative to ‘Set packet-loss SLA threshold’, the target must answer the selected probe method and be reachable from those paths.

D:

Best Quality uses configured quality criteria derived from a health check to prioritize the most suitable available member, a mechanism intended to feed measured latency, jitter, or loss into a dynamic path-selection rule rather than the requested ‘Set packet-loss SLA threshold’ control. The stated task instead is to protect application sessions from a link that intermittently drops packets, and adjusting ‘Use SLA measurements for best-quality steering’ would not deliver ‘Set packet-loss SLA threshold’. For the ‘Use SLA measurements for best-quality steering’ alternative to ‘Set packet-loss SLA threshold’, choosing best quality differs from deciding which member has the smallest monetary cost.

Question 153

For an onboarding pilot with a small set of managed test laptops, a review of the current state finds that a mass enrollment depends on each employee manually finding and configuring a local installer. Which configuration area most directly addresses this?

  1. Investigate: Deploy FortiClient using enterprise management
  2. Investigate: Maintain FortiClient tenant registration
  3. Investigate: Import users through LDAP
  4. Investigate: Configure RADIUS authentication

Explanation

Correct Answer

A:

The symptom identifies the missing operational behavior: group policy or mobile device management can deploy prepared FortiClient packages to managed endpoints. For an onboarding pilot with a small set of managed test laptops, a direct diagnostic confirmation would be that managed devices receive the intended FortiClient package through centralized deployment; during repair, the enterprise deployment tool must match endpoint operating systems and device ownership.

Incorrect Answers

B:

Registered FortiClient maintains connectivity with FortiSASE endpoint management and supplies identity or posture data, which serves the different requirement to preserve endpoint identification and posture exchange for protected access instead of the behavior delivered by ‘Deploy FortiClient using enterprise management’. If that component were misconfigured, a more characteristic finding would be that a previously trusted endpoint no longer supplies the expected posture information after disconnecting; the actual report concerns a mass enrollment depends on each employee manually finding and configuring a local installer at an onboarding pilot with a small set of managed test laptops.

C:

LDAP integration allows FortiSASE to reference directory accounts and user groups, which serves the different requirement to reuse users and groups defined in an accessible directory server instead of the behavior delivered by ‘Deploy FortiClient using enterprise management’. If that component were misconfigured, a more characteristic finding would be that directory staff are not visible to SASE policy although the directory contains them; the actual report concerns a mass enrollment depends on each employee manually finding and configuring a local installer at an onboarding pilot with a small set of managed test laptops.

D:

RADIUS integration delegates user authentication to a configured authentication server, which serves the different requirement to authenticate managed remote agents against a reachable RADIUS infrastructure instead of the behavior delivered by ‘Deploy FortiClient using enterprise management’. If that component were misconfigured, a more characteristic finding would be that RADIUS-backed users fail access even though their account is accepted directly by the RADIUS server; the actual report concerns a mass enrollment depends on each employee manually finding and configuring a local installer at an onboarding pilot with a small set of managed test laptops.

Question 154

During an authorized lab exercise for an off-site workforce where some endpoints fail compliance verification, a reviewer needs proof the deployment can label endpoints dynamically when a specified local security condition is met. Which observation most directly validates it?

  1. The managed device receives the intended posture tag after a matching check.
  2. Registration health and a recent tag update corroborate the current device state.
  3. The endpoint is tagged only after the required trusted certificate is detected.
  4. Only sessions presenting the approved endpoint posture tag match the private-access permit policy.

Explanation

Correct Answer

A:

This checks ‘Build a security posture tag rule’ at the correct operational boundary: FortiClient evaluates defined endpoint posture conditions and associates matching endpoints with security tags. It demonstrates the specific capability to label endpoints dynamically when a specified local security condition is met in an off-site workforce where some endpoints fail compliance verification; deployment should additionally respect the constraint: The tag logic must accurately represent the actual security requirement.

Incorrect Answers

B:

That observation belongs to ‘Validate fresh endpoint posture telemetry’, not ‘Build a security posture tag rule’; 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 ‘Build a security posture tag rule’ for an off-site workforce where some endpoints fail compliance verification, not the evidence produced by ‘Validate fresh endpoint posture telemetry’.

C:

That observation belongs to ‘Use a certificate-based posture check’, not ‘Build a security posture tag rule’; its purpose is to identify managed endpoints that carry an enterprise-issued device credential, the underlying behavior is that endpoint tagging can evaluate the presence and properties of a required client certificate. The reviewer is instead verifying ‘Build a security posture tag rule’ for an off-site workforce where some endpoints fail compliance verification, not the evidence produced by ‘Use a certificate-based posture check’.

D:

That observation belongs to ‘Assign compliant endpoint tags to private policies’, not ‘Build a security posture tag rule’; 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 ‘Build a security posture tag rule’ for an off-site workforce where some endpoints fail compliance verification, not the evidence produced by ‘Assign compliant endpoint tags to private policies’.

Question 155

At a cloud security tenant inspecting traffic from managed remote laptops, the change request is to detect malware payloads passing through a permitted cloud access policy. Which configuration is the most direct fit?

  1. Handle QUIC when deep inspection is required
  2. Enable SSL deep inspection
  3. Configure application control signatures
  4. Apply an antivirus profile to allowed traffic

Explanation

Correct Answer

D:

An enabled antivirus inspection component examines supported file content for malicious signatures or behavior indicators; that scope directly serves the goal to detect malware payloads passing through a permitted cloud access policy in a cloud security tenant inspecting traffic from managed remote laptops. During implementation, encrypted payload scanning depends on appropriate TLS inspection and certificate trust rather than treating the configuration label as proof of working service.

Incorrect Answers

A:

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 ‘Apply an antivirus profile to allowed traffic’ control. The stated task instead is to detect malware payloads passing through a permitted cloud access policy, and adjusting ‘Handle QUIC when deep inspection is required’ would not deliver ‘Apply an antivirus profile to allowed traffic’. For the ‘Handle QUIC when deep inspection is required’ alternative to ‘Apply an antivirus profile to allowed traffic’, application behavior and HTTPS fallback must be validated for the deployed browsers.

B:

Deep inspection decrypts eligible TLS sessions at the security service for content-aware scanning, a mechanism intended to inspect content carried inside HTTPS when allowed by policy and endpoint trust rather than the requested ‘Apply an antivirus profile to allowed traffic’ control. The stated task instead is to detect malware payloads passing through a permitted cloud access policy, and adjusting ‘Enable SSL deep inspection’ would not deliver ‘Apply an antivirus profile to allowed traffic’. For the ‘Enable SSL deep inspection’ alternative to ‘Apply an antivirus profile to allowed traffic’, certificate deployment and inspection exemptions must be handled to avoid breaking legitimate services.

C:

Application Control identifies application behavior and can apply signature-level allow, monitor, or block actions, a mechanism intended to block a specific risky application without disabling every website in its category rather than the requested ‘Apply an antivirus profile to allowed traffic’ control. The stated task instead is to detect malware payloads passing through a permitted cloud access policy, and adjusting ‘Configure application control signatures’ would not deliver ‘Apply an antivirus profile to allowed traffic’. For the ‘Configure application control signatures’ alternative to ‘Apply an antivirus profile to allowed traffic’, port-only access controls are not the same as identifying an application signature.

Question 156

During an authorized lab exercise for a security operations review of remote-user threat detections, a reviewer needs proof the deployment can identify which inspected download was blocked for malware and under which policy. Which observation most directly validates it?

  1. The IPS log records an appropriate attack signature and the related action.
  2. A filtered query event shows the domain and DNS-policy enforcement result.
  3. The web-filter event shows the URL category and associated block action.
  4. A time-matched AV event shows the detection and enforced action for the download.

Explanation

Correct Answer

D:

This checks ‘Inspect antivirus detection events’ at the correct operational boundary: aV logs identify signature or file detections and the security action applied to a session. It demonstrates the specific capability to identify which inspected download was blocked for malware and under which policy in a security operations review of remote-user threat detections; deployment should additionally respect the constraint: A traffic deny log by itself does not establish that antivirus detected malware.

Incorrect Answers

A:

That observation belongs to ‘Inspect IPS threat logs’, not ‘Inspect antivirus detection events’; its purpose is to verify whether an exploit signature triggered inspection rather than a generic connectivity failure, the underlying behavior is that IPS events contain the signature context and configured security response for detected traffic. The reviewer is instead verifying ‘Inspect antivirus detection events’ for a security operations review of remote-user threat detections, not the evidence produced by ‘Inspect IPS threat logs’.

B:

That observation belongs to ‘Inspect DNS-filter threat events’, not ‘Inspect antivirus detection events’; its purpose is to identify blocked malicious name resolution before the browser opens a TCP session, the underlying behavior is that DNS security logs record affected domain requests and configured malicious-domain actions. The reviewer is instead verifying ‘Inspect antivirus detection events’ for a security operations review of remote-user threat detections, not the evidence produced by ‘Inspect DNS-filter threat events’.

C:

That observation belongs to ‘Inspect web-filter category logs’, not ‘Inspect antivirus detection events’; its purpose is to determine whether a website was blocked by category policy rather than by transport failure, the underlying behavior is that web-filter logs associate an HTTP or HTTPS destination with category evaluation and action. The reviewer is instead verifying ‘Inspect antivirus detection events’ for a security operations review of remote-user threat detections, not the evidence produced by ‘Inspect web-filter category logs’.

Question 157

During an authorized lab exercise for an industrial branch sending payroll traffic to a data-center application, the deployment standard specifies the control ‘Use a BGP learned private prefix’ to obtain branch or data-center destinations without maintaining individual manual static routes. Which functional description matches it?

  1. Administrative distance influences which equal-prefix route source is preferred for installation.
  2. BGP can advertise and learn remote private networks over supported routed overlays.
  3. A destination-specific static route referencing the overlay zone makes private routes accessible to SD-WAN selection.
  4. SD-WAN candidate preference works only after routing makes a compatible egress path available.

Explanation

Correct Answer

B:

‘Use a BGP learned private prefix’ is used to obtain branch or data-center destinations without maintaining individual manual static routes in an industrial branch sending payroll traffic to a data-center application; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that BGP neighbor state and learned route entries show the remote application CIDR; the rollout must also respect this constraint: Routing adjacency and accepted prefix policies must be healthy independently of tunnel state.

Incorrect Answers

A:

The described behavior is part of ‘Review administrative distance’, used to choose between competing routes learned from different sources for the same prefix instead of the role of ‘Use a BGP learned private prefix’. In contrast to ‘Review administrative distance’, ‘Use a BGP learned private prefix’ follows a different mechanism: BGP can advertise and learn remote private networks over supported routed overlays. Treating ‘Review administrative distance’ as equivalent would not address the tunnel stays up but dynamically announced private subnets never enter the routing table in an industrial branch sending payroll traffic to a data-center application.

C:

The described behavior is part of ‘Configure a static partner route through overlay zone’, used to reach an on-premises network across an IPsec overlay SD-WAN group instead of the role of ‘Use a BGP learned private prefix’. In contrast to ‘Configure a static partner route through overlay zone’, ‘Use a BGP learned private prefix’ follows a different mechanism: BGP can advertise and learn remote private networks over supported routed overlays. Treating ‘Configure a static partner route through overlay zone’ as equivalent would not address the tunnel stays up but dynamically announced private subnets never enter the routing table in an industrial branch sending payroll traffic to a data-center application.

D:

The described behavior is part of ‘Compare routing table and SD-WAN rule decision’, used to find which stage prevents a preferred member from being used instead of the role of ‘Use a BGP learned private prefix’. In contrast to ‘Compare routing table and SD-WAN rule decision’, ‘Use a BGP learned private prefix’ follows a different mechanism: BGP can advertise and learn remote private networks over supported routed overlays. Treating ‘Compare routing table and SD-WAN rule decision’ as equivalent would not address the tunnel stays up but dynamically announced private subnets never enter the routing table in an industrial branch sending payroll traffic to a data-center application.

Question 158

During an authorized lab exercise for a logistics site where routing and SD-WAN services have separate responsibilities, a reviewer needs proof the deployment can troubleshoot a session that remains associated with an earlier selection after an SD-WAN change. Which observation most directly validates it?

  1. The diagnostic output identifies the matching service and its selected eligible member.
  2. The rule's loss criterion ranks the measured low-loss member first.
  3. Separate old and new session entries reveal their actual selected interfaces.
  4. The jitter-ranked rule prefers the link reporting less packet-delay variation.

Explanation

Correct Answer

C:

This checks ‘Treat existing sessions differently from new flows’ at the correct operational boundary: session state and configured failover behavior affect when path changes apply; newly created flows are evaluated against current steering. It demonstrates the specific capability to troubleshoot a session that remains associated with an earlier selection after an SD-WAN change in a logistics site where routing and SD-WAN services have separate responsibilities; deployment should additionally respect the constraint: Do not assume a rule edit retroactively redistributes every already established flow.

Incorrect Answers

A:

That observation belongs to ‘Test rule matching with service diagnostics’, not ‘Treat existing sessions differently from new flows’; its purpose is to identify which SD-WAN rule and candidate member were chosen for a particular session, the underlying behavior is that SD-WAN service diagnostics expose matched rules, interface lists, modes, and selected member status. The reviewer is instead verifying ‘Treat existing sessions differently from new flows’ for a logistics site where routing and SD-WAN services have separate responsibilities, not the evidence produced by ‘Test rule matching with service diagnostics’.

B:

That observation belongs to ‘Use Best Quality with packet loss’, not ‘Treat existing sessions differently from new flows’; its purpose is to prefer the circuit losing fewer packets for interactive services, the underlying behavior is that Best Quality supports loss-oriented link comparison using measured health data. The reviewer is instead verifying ‘Treat existing sessions differently from new flows’ for a logistics site where routing and SD-WAN services have separate responsibilities, not the evidence produced by ‘Use Best Quality with packet loss’.

D:

That observation belongs to ‘Use Best Quality with jitter’, not ‘Treat existing sessions differently from new flows’; its purpose is to steer delay-sensitive conferencing toward the most stable path, the underlying behavior is that Best Quality can evaluate jitter as the link-cost factor to compare delay variation. The reviewer is instead verifying ‘Treat existing sessions differently from new flows’ for a logistics site where routing and SD-WAN services have separate responsibilities, not the evidence produced by ‘Use Best Quality with jitter’.

Question 159

In a change-control meeting for a dispersed workforce that uses a corporate SAML identity provider, a design review calls for a way to bind an invited remote user's FortiClient enrollment to the correct organization. What should the operator configure?

  1. Configure agentless proxy SSO
  2. Enroll an agentless web user
  3. Deploy FortiClient using enterprise management
  4. Distribute a FortiSASE invitation code

Explanation

Correct Answer

D:

The Onboard Users workflow provides information that remote users use for FortiSASE client registration; that scope directly serves the goal to bind an invited remote user's FortiClient enrollment to the correct organization in a dispersed workforce that uses a corporate SAML identity provider. During implementation, onboarding credentials should be shared only with the intended users rather than treating the configuration label as proof of working service.

Incorrect Answers

A:

SWG SSO authenticates a web proxy session using the configured identity provider, a mechanism intended to associate proxied browser traffic with enterprise user identity during secure web gateway inspection rather than the requested ‘Distribute a FortiSASE invitation code’ control. The stated task instead is to bind an invited remote user's FortiClient enrollment to the correct organization, and adjusting ‘Configure agentless proxy SSO’ would not deliver ‘Distribute a FortiSASE invitation code’. For the ‘Configure agentless proxy SSO’ alternative to ‘Distribute a FortiSASE invitation code’, proxy SSO often depends on compatible deep inspection and IdP reachability.

B:

Agentless secure web gateway access uses explicit proxy steering rather than a full-device agent tunnel, a mechanism intended to protect an unmanaged Chromebook's HTTP and HTTPS browsing without installing FortiClient rather than the requested ‘Distribute a FortiSASE invitation code’ control. The stated task instead is to bind an invited remote user's FortiClient enrollment to the correct organization, and adjusting ‘Enroll an agentless web user’ would not deliver ‘Distribute a FortiSASE invitation code’. For the ‘Enroll an agentless web user’ alternative to ‘Distribute a FortiSASE invitation code’, agentless proxy steering does not automatically tunnel all nonweb IP traffic.

C:

Group policy or mobile device management can deploy prepared FortiClient packages to managed endpoints, a mechanism intended to roll out FortiClient at scale without requiring hundreds of manual installer sessions rather than the requested ‘Distribute a FortiSASE invitation code’ control. The stated task instead is to bind an invited remote user's FortiClient enrollment to the correct organization, and adjusting ‘Deploy FortiClient using enterprise management’ would not deliver ‘Distribute a FortiSASE invitation code’. For the ‘Deploy FortiClient using enterprise management’ alternative to ‘Distribute a FortiSASE invitation code’, the enterprise deployment tool must match endpoint operating systems and device ownership.

Question 160

Within a global remote-user rollout with separate employee and contractor policies, the configuration has been applied. Which measurement or record best confirms the goal to reuse users and groups defined in an accessible directory server?

  1. A controlled browser request establishes an SSO user session for the cloud proxy.
  2. Managed devices receive the intended FortiClient package through centralized deployment.
  3. The new local identity appears in the authorized access group and can authenticate.
  4. FortiSASE test authentication obtains a valid response from the designated RADIUS source.
  5. The configured LDAP source resolves expected groups and authenticated users.

Explanation

Correct Answer

E:

This checks ‘Import users through LDAP’ at the correct operational boundary: LDAP integration allows FortiSASE to reference directory accounts and user groups. It demonstrates the specific capability to reuse users and groups defined in an accessible directory server in a global remote-user rollout with separate employee and contractor policies; deployment should additionally respect the constraint: FortiSASE must reach the directory service through its permitted network path.

Incorrect Answers

A:

That observation belongs to ‘Configure agentless proxy SSO’, not ‘Import users through LDAP’; its purpose is to associate proxied browser traffic with enterprise user identity during secure web gateway inspection, the underlying behavior is that sWG SSO authenticates a web proxy session using the configured identity provider. The reviewer is instead verifying ‘Import users through LDAP’ for a global remote-user rollout with separate employee and contractor policies, not the evidence produced by ‘Configure agentless proxy SSO’.

B:

That observation belongs to ‘Deploy FortiClient using enterprise management’, not ‘Import users through LDAP’; its purpose is to roll out FortiClient at scale without requiring hundreds of manual installer sessions, the underlying behavior is that group policy or mobile device management can deploy prepared FortiClient packages to managed endpoints. The reviewer is instead verifying ‘Import users through LDAP’ for a global remote-user rollout with separate employee and contractor policies, not the evidence produced by ‘Deploy FortiClient using enterprise management’.

C:

That observation belongs to ‘Create a local FortiSASE test user’, not ‘Import users through LDAP’; its purpose is to authenticate a limited lab user when no central identity source has yet been connected, the underlying behavior is that local user records and groups can be configured for a small controlled FortiSASE rollout. The reviewer is instead verifying ‘Import users through LDAP’ for a global remote-user rollout with separate employee and contractor policies, not the evidence produced by ‘Create a local FortiSASE test user’.

D:

That observation belongs to ‘Configure RADIUS authentication’, not ‘Import users through LDAP’; its purpose is to authenticate managed remote agents against a reachable RADIUS infrastructure, the underlying behavior is that RADIUS integration delegates user authentication to a configured authentication server. The reviewer is instead verifying ‘Import users through LDAP’ for a global remote-user rollout with separate employee and contractor policies, not the evidence produced by ‘Configure RADIUS authentication’.

Fortinet NSE 5 - FortiSASE and SD-WAN 7.6 Core Administrator (NSE5_SSE_AD-7.6) Practice Tests