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

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’.

Question 161

At a small datacenter with a physical circuit, a cellular backup and tagged VLAN handoffs, an engineer is preparing ‘Use an IPsec interface as a member’ to apply SD-WAN selection to redundant encrypted site-to-site paths. Which TWO statements identify a pertinent deployment safeguard and a direct post-change validation result? Choose TWO.

  1. Bring up the route-based tunnel and verify selectors and reachability independently.
  2. The member status shows the intended lower numerical priority on the preferred circuit.
  3. The VLAN identifier and upstream trunk must agree before health checks can succeed.
  4. The tunnel interface is listed as an SD-WAN overlay member.
  5. The source must be routable toward the monitor target and accepted by its response path.

Explanation

Correct Answers

A:

This safeguard applies to ‘Use an IPsec interface as a member’, which works because route-based IPsec tunnel interfaces can be members whose quality is measured and selected for overlay routing. Without the correct deployment condition, operators may see that the VPN tunnel passes traffic manually but is absent from overlay service member lists in a small datacenter with a physical circuit, a cellular backup and tagged VLAN handoffs.

D:

The observation follows from the operation of ‘Use an IPsec interface as a member’: route-based IPsec tunnel interfaces can be members whose quality is measured and selected for overlay routing. It directly tests the requested ability 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, rather than another policy or network layer.

Incorrect Answers

B:

This result would validate ‘Set member fallback priority’, not ‘Use an IPsec interface as a member’, because a lower member priority value takes precedence when the routing or SD-WAN selection uses priority. That separate implementation serves prefer a designated route candidate when priority is the deciding factor, whereas the audit needs evidence specifically of ‘Use an IPsec interface as a member’ at a small datacenter with a physical circuit, a cellular backup and tagged VLAN handoffs.

C:

The planning point is associated with ‘Use a VLAN interface as a member’, not ‘Use an IPsec interface as a member’; its real role is to steer traffic over a tagged Ethernet handoff from an ISP. The required deployment instead centers on ‘Use an IPsec interface as a member’, rather than ‘Use a VLAN interface as a member’; the distinct symptom to guard against is that the VPN tunnel passes traffic manually but is absent from overlay service member lists.

E:

The planning point is associated with ‘Define the member health-check source’, not ‘Use an IPsec interface as a member’; its real role is to send probes using the correct reachable source address on a multiaddress uplink. The required deployment instead centers on ‘Use an IPsec interface as a member’, rather than ‘Define the member health-check source’; the distinct symptom to guard against is that the VPN tunnel passes traffic manually but is absent from overlay service member lists.

Question 162

For an onboarding pilot with a small set of managed test laptops, a review of the current state finds that a contractor device receives the general employee tunnel settings instead of its restricted profile. Which configuration area most directly addresses this?

  1. Investigate: Deploy FortiClient using enterprise management
  2. Investigate: Match endpoint profiles to the correct user group
  3. Investigate: Use preconfigured FortiClient installers
  4. Investigate: Configure RADIUS authentication

Explanation

Correct Answer

B:

The symptom identifies the missing operational behavior: endpoint profiles can be assigned according to relevant groups or administrative selection. For an onboarding pilot with a small set of managed test laptops, a direct diagnostic confirmation would be that the device's assigned endpoint profile matches the intended identity group; during repair, profile assignment must be checked separately from cloud traffic-policy ordering.

Incorrect Answers

A:

Group policy or mobile device management can deploy prepared FortiClient packages to managed endpoints, which serves the different requirement to roll out FortiClient at scale without requiring hundreds of manual installer sessions instead of the behavior delivered by ‘Match endpoint profiles to the correct user group’. If that component were misconfigured, a more characteristic finding would be that a mass enrollment depends on each employee manually finding and configuring a local installer; the actual report concerns a contractor device receives the general employee tunnel settings instead of its restricted profile at an onboarding pilot with a small set of managed test laptops.

C:

The FortiSASE onboarding flow can provide prepared FortiClient installers that users install on their devices, which serves the different requirement to enroll a small pilot group with minimal manual agent configuration instead of the behavior delivered by ‘Match endpoint profiles to the correct user group’. If that component were misconfigured, a more characteristic finding would be that pilot users install a generic client but lack the intended cloud service configuration; the actual report concerns a contractor device receives the general employee tunnel settings instead of its restricted profile 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 ‘Match endpoint profiles to the correct user group’. 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 contractor device receives the general employee tunnel settings instead of its restricted profile at an onboarding pilot with a small set of managed test laptops.

Question 163

At a logistics site where routing and SD-WAN services have separate responsibilities, a controlled test reveals that fresh sessions choose the new preferred WAN while established sessions appear on the old member. Which setting is the strongest first lead?

  1. Investigate: Use Lowest Cost with an SLA target
  2. Investigate: Match by detected application
  3. Investigate: Treat existing sessions differently from new flows
  4. Investigate: Use Best Quality with latency

Explanation

Correct Answer

C:

The symptom identifies the missing operational behavior: session state and configured failover behavior affect when path changes apply; newly created flows are evaluated against current steering. For a logistics site where routing and SD-WAN services have separate responsibilities, a direct diagnostic confirmation would be that separate old and new session entries reveal their actual selected interfaces; during repair, do not assume a rule edit retroactively redistributes every already established flow.

Incorrect Answers

A:

Lowest Cost chooses the smallest configured member cost among those that satisfy the selected SLA, which serves the different requirement to send a service on the cheapest circuit that still meets quality objectives instead of the behavior delivered by ‘Treat existing sessions differently from new flows’. If that component were misconfigured, a more characteristic finding would be that an inexpensive but degraded path is used despite a threshold-bound application policy; the actual report concerns fresh sessions choose the new preferred WAN while established sessions appear on the old member at a logistics site where routing and SD-WAN services have separate responsibilities.

B:

Application-based SD-WAN rules use application detection information to identify supported traffic signatures, which serves the different requirement to prefer an SD-WAN path based on application identification rather than fixed port alone instead of the behavior delivered by ‘Treat existing sessions differently from new flows’. If that component were misconfigured, a more characteristic finding would be that a named conferencing application is not recognized when steering is configured only by port; the actual report concerns fresh sessions choose the new preferred WAN while established sessions appear on the old member at a logistics site where routing and SD-WAN services have separate responsibilities.

D:

Best Quality can rank member quality using latency collected by the designated performance health check, which serves the different requirement to prefer the lowest-delay usable path for an interactive application instead of the behavior delivered by ‘Treat existing sessions differently from new flows’. If that component were misconfigured, a more characteristic finding would be that highly interactive traffic follows the higher-latency link though both links are reachable; the actual report concerns fresh sessions choose the new preferred WAN while established sessions appear on the old member at a logistics site where routing and SD-WAN services have separate responsibilities.

Question 164

For a campus running FortiOS 7.6 with application-aware policies, a maintenance plan requires the firewall team to send a service on the cheapest circuit that still meets quality objectives. Which choice is appropriate?

  1. Use Best Quality with jitter
  2. Restrict the candidate member preference list
  3. Specify an SD-WAN zone preference
  4. Use Lowest Cost with an SLA target

Explanation

Correct Answer

D:

Lowest Cost chooses the smallest configured member cost among those that satisfy the selected SLA; that scope directly serves the goal to send a service on the cheapest circuit that still meets quality objectives in a campus running FortiOS 7.6 with application-aware policies. During implementation, a cheap member failing its SLA is not preferred solely because of its price rather than treating the configuration label as proof of working service.

Incorrect Answers

A:

Best Quality can evaluate jitter as the link-cost factor to compare delay variation, a mechanism intended to steer delay-sensitive conferencing toward the most stable path rather than the requested ‘Use Lowest Cost with an SLA target’ control. The stated task instead is to send a service on the cheapest circuit that still meets quality objectives, and adjusting ‘Use Best Quality with jitter’ would not deliver ‘Use Lowest Cost with an SLA target’. For the ‘Use Best Quality with jitter’ alternative to ‘Use Lowest Cost with an SLA target’, jitter and mean round-trip latency are separate measurements.

B:

An explicit member or zone preference limits which eligible paths a matching service may choose, a mechanism intended to prevent a sensitive service from using an otherwise healthy but unapproved ISP rather than the requested ‘Use Lowest Cost with an SLA target’ control. The stated task instead is to send a service on the cheapest circuit that still meets quality objectives, and adjusting ‘Restrict the candidate member preference list’ would not deliver ‘Use Lowest Cost with an SLA target’. For the ‘Restrict the candidate member preference list’ alternative to ‘Use Lowest Cost with an SLA target’, service candidate filtering does not replace destination access control and encryption requirements.

C:

An SD-WAN rule can prefer particular SD-WAN zones instead of enumerating every interface member, a mechanism intended to restrict an application to members grouped within a chosen logical zone rather than the requested ‘Use Lowest Cost with an SLA target’ control. The stated task instead is to send a service on the cheapest circuit that still meets quality objectives, and adjusting ‘Specify an SD-WAN zone preference’ would not deliver ‘Use Lowest Cost with an SLA target’. For the ‘Specify an SD-WAN zone preference’ alternative to ‘Use Lowest Cost with an SLA target’, zone preference and routing reachability must point to compatible paths.

Question 165

For a financial services branch where forwarding decisions disagree with interface health, a technical review examines the control ‘Verify the forwarding information base’ for the objective to confirm the FortiGate has installed a usable next hop for a destination. Which statement best describes what it changes?

  1. Route-based IPsec exposes a logical tunnel interface that routing and SD-WAN can reference.
  2. The FIB holds selected forwarding entries and is essential to actual packet delivery.
  3. Longest-prefix match chooses a more specific valid destination route ahead of a broader default.
  4. An overlay tunnel requires the public peer endpoint to remain reachable through an underlay path.

Explanation

Correct Answer

B:

‘Verify the forwarding information base’ is used to confirm the FortiGate has installed a usable next hop for a destination in a financial services branch where forwarding decisions disagree with interface health; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that a route lookup shows the expected egress interface and reachable next hop; the rollout must also respect this constraint: The SD-WAN rule must be reconciled with actual route installation.

Incorrect Answers

A:

The described behavior is part of ‘Use a route-based IPsec overlay’, used to carry private routed traffic as a selectable interface-based tunnel path instead of the role of ‘Verify the forwarding information base’. In contrast to ‘Use a route-based IPsec overlay’, ‘Verify the forwarding information base’ follows a different mechanism: the FIB holds selected forwarding entries and is essential to actual packet delivery. Treating ‘Use a route-based IPsec overlay’ as equivalent would not address the service-rule configuration looks valid while the forwarding result points elsewhere in a financial services branch where forwarding decisions disagree with interface health.

C:

The described behavior is part of ‘Prefer a more specific prefix’, used to send a partner network into a private tunnel even while default internet routing is present instead of the role of ‘Verify the forwarding information base’. In contrast to ‘Prefer a more specific prefix’, ‘Verify the forwarding information base’ follows a different mechanism: the FIB holds selected forwarding entries and is essential to actual packet delivery. Treating ‘Prefer a more specific prefix’ as equivalent would not address the service-rule configuration looks valid while the forwarding result points elsewhere in a financial services branch where forwarding decisions disagree with interface health.

D:

The described behavior is part of ‘Keep underlay route for tunnel peer’, used to preserve transport reachability to an IPsec hub before private overlay traffic is steered instead of the role of ‘Verify the forwarding information base’. In contrast to ‘Keep underlay route for tunnel peer’, ‘Verify the forwarding information base’ follows a different mechanism: the FIB holds selected forwarding entries and is essential to actual packet delivery. Treating ‘Keep underlay route for tunnel peer’ as equivalent would not address the service-rule configuration looks valid while the forwarding result points elsewhere in a financial services branch where forwarding decisions disagree with interface health.

Question 166

In a change-control meeting for an enterprise interconnecting SD-WAN overlays and cloud security edges, acceptance testing shows that the organization requires an internal UDP service that a TCP-only application proxy cannot carry. Which control should be investigated first?

  1. Investigate: Configure DNS resolution for private names
  2. Investigate: Use SD-WAN private access for TCP and UDP
  3. Investigate: Select hub path using SLA health
  4. Investigate: Verify site-based SASE traffic steering

Explanation

Correct Answer

B:

The symptom identifies the missing operational behavior: an SD-WAN-based SPA design can provide routed access to private TCP and UDP applications. For an enterprise interconnecting SD-WAN overlays and cloud security edges, a direct diagnostic confirmation would be that the routed SPA service connection reaches the approved UDP application behind the hub; during repair, choose the private-access architecture according to protocol and trust requirements.

Incorrect Answers

A:

Private or split-DNS settings direct internal-name lookups to appropriate enterprise DNS servers, which serves the different requirement to let remote users resolve internal application FQDNs to protected addresses instead of the behavior delivered by ‘Use SD-WAN private access for TCP and UDP’. If that component were misconfigured, a more characteristic finding would be that an internal application works by IP address but its private hostname fails resolution; the actual report concerns the organization requires an internal UDP service that a TCP-only application proxy cannot carry at an enterprise interconnecting SD-WAN overlays and cloud security edges.

C:

Health and service-connection priorities can influence which reachable private hub path is preferred, which serves the different requirement to prefer a viable SPA route when one private-access connection becomes degraded instead of the behavior delivered by ‘Use SD-WAN private access for TCP and UDP’. If that component were misconfigured, a more characteristic finding would be that users continue taking a poor-quality service connection while a healthy hub exists; the actual report concerns the organization requires an internal UDP service that a TCP-only application proxy cannot carry at an enterprise interconnecting SD-WAN overlays and cloud security edges.

D:

Site-based on-ramp configuration determines which branch flows are forwarded into FortiSASE, which serves the different requirement to differentiate local branch DIA from traffic genuinely sent to cloud enforcement instead of the behavior delivered by ‘Use SD-WAN private access for TCP and UDP’. If that component were misconfigured, a more characteristic finding would be that branch internet sessions show a public ISP path and lack expected cloud security logs; the actual report concerns the organization requires an internal UDP service that a TCP-only application proxy cannot carry at an enterprise interconnecting SD-WAN overlays and cloud security edges.

Question 167

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

  1. Posture signals require recent endpoint scanning and successful telemetry exchange.
  2. The tag logic must accurately represent the actual security requirement.
  3. Authentication identity and endpoint posture solve different trust checks.
  4. Version policy should account for supported platforms and enterprise patch baselines.

Explanation

Correct Answer

A:

This condition matters for ‘Check endpoint vulnerability severity’ because vulnerability-related posture information can be used to classify a risky endpoint for conditional access. Omitting the relevant safeguard can produce a workstation with a critical unremediated issue continues receiving full sensitive-app access; a successful test at an off-site workforce where some endpoints fail compliance verification would instead demonstrate that the device's posture classification reflects the configured vulnerability severity.

Incorrect Answers

B:

The condition is associated with ‘Build a security posture tag rule’, a mechanism used to label endpoints dynamically when a specified local security condition is met instead of ‘Check endpoint vulnerability severity’, because FortiClient evaluates defined endpoint posture conditions and associates matching endpoints with security tags. For ‘Check endpoint vulnerability severity’, unlike ‘Build a security posture tag rule’, the characteristic failure would be a workstation with a critical unremediated issue continues receiving full sensitive-app access, 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 ‘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 ‘Check endpoint vulnerability severity’, because private access policies can use security posture tags as dynamic matching criteria. For ‘Check endpoint vulnerability severity’, unlike ‘Assign compliant endpoint tags to private policies’, the characteristic failure would be a workstation with a critical unremediated issue continues receiving full sensitive-app access, which this alternative prerequisite would not directly address at an off-site workforce where some endpoints fail compliance verification.

D:

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 ‘Check endpoint vulnerability severity’, because OS-version posture criteria allow security rules to distinguish compliant from obsolete endpoint builds. For ‘Check endpoint vulnerability severity’, unlike ‘Use operating-system version posture’, the characteristic failure would be a workstation with a critical unremediated issue continues receiving full sensitive-app access, which this alternative prerequisite would not directly address at an off-site workforce where some endpoints fail compliance verification.

Question 168

In a change-control meeting for a contractor access program with different endpoint and connection policies, acceptance testing shows that a valid user's unmanaged laptop reaches a restricted private service despite failing device requirements. Which control should be investigated first?

  1. Investigate: Use endpoint-profile assignment for managed groups
  2. Investigate: Use operating-system version posture
  3. Investigate: Assign compliant endpoint tags to private policies
  4. Investigate: Review the posture tag's allow or deny direction

Explanation

Correct Answer

C:

The symptom identifies the missing operational behavior: private access policies can use security posture tags as dynamic matching criteria. For a contractor access program with different endpoint and connection policies, a direct diagnostic confirmation would be that only sessions presenting the approved endpoint posture tag match the private-access permit policy; during repair, authentication identity and endpoint posture solve different trust checks.

Incorrect Answers

A:

Endpoint profile assignment determines which device-side checks and tunnel behavior a managed group receives, which serves the different requirement to apply a stricter posture and connection configuration to a high-risk user population instead of the behavior delivered by ‘Assign compliant endpoint tags to private policies’. If that component were misconfigured, a more characteristic finding would be that contractor devices use the default endpoint configuration rather than the intended restricted policy; the actual report concerns a valid user's unmanaged laptop reaches a restricted private service despite failing device requirements at a contractor access program with different endpoint and connection policies.

B:

OS-version posture criteria allow security rules to distinguish compliant from obsolete endpoint builds, which serves the different requirement to restrict access from endpoints that do not meet an approved operating-system baseline instead of the behavior delivered by ‘Assign compliant endpoint tags to private policies’. If that component were misconfigured, a more characteristic finding would be that unpatched legacy operating systems gain the same access as approved updated workstations; the actual report concerns a valid user's unmanaged laptop reaches a restricted private service despite failing device requirements at a contractor access program with different endpoint and connection policies.

D:

An allow-when-tagged versus deny-when-tagged action determines whether the matched posture condition grants connectivity, which serves the different requirement to avoid inverting the policy when a tag specifically denotes a noncompliant endpoint instead of the behavior delivered by ‘Assign compliant endpoint tags to private policies’. If that component were misconfigured, a more characteristic finding would be that devices labeled as risky are inadvertently allowed by an inverted preconnection action; the actual report concerns a valid user's unmanaged laptop reaches a restricted private service despite failing device requirements at a contractor access program with different endpoint and connection policies.

Question 169

During an authorized lab exercise for a finance team that uses multiple approved SaaS applications, the deployment standard specifies the control ‘Apply a web-filter category action’ to block a prohibited web category while allowing legitimate business browsing. Which functional description matches it?

  1. Web filtering classifies requested sites and applies the configured category or URL action.
  2. File Filter identifies supported file types in inspected sessions and enforces the configured file action.
  3. URL-level exceptions can refine category-based web filtering when an approved exception is required.
  4. Deep inspection decrypts eligible TLS sessions at the security service for content-aware scanning.

Explanation

Correct Answer

A:

‘Apply a web-filter category action’ is used to block a prohibited web category while allowing legitimate business browsing in a finance team that uses multiple approved SaaS applications; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that a test destination in the prohibited category is blocked with a web-filter log; the rollout must also respect this constraint: Web filtering decisions differ from application-control signatures and DNS resolution policies.

Incorrect Answers

B:

The described behavior is part of ‘Configure file filtering’, used to block transfer of prohibited file types regardless of benign website category instead of the role of ‘Apply a web-filter category action’. In contrast to ‘Configure file filtering’, ‘Apply a web-filter category action’ follows a different mechanism: web filtering classifies requested sites and applies the configured category or URL action. Treating ‘Configure file filtering’ as equivalent would not address users can visit an explicitly prohibited class of websites despite cloud web steering in a finance team that uses multiple approved SaaS applications.

C:

The described behavior is part of ‘Use a specific URL filter exception’, used to allow a justified business website without disabling an entire restrictive category instead of the role of ‘Apply a web-filter category action’. In contrast to ‘Use a specific URL filter exception’, ‘Apply a web-filter category action’ follows a different mechanism: web filtering classifies requested sites and applies the configured category or URL action. Treating ‘Use a specific URL filter exception’ as equivalent would not address users can visit an explicitly prohibited class of websites despite cloud web steering in a finance team that uses multiple approved SaaS applications.

D:

The described behavior is part of ‘Enable SSL deep inspection’, used to inspect content carried inside HTTPS when allowed by policy and endpoint trust instead of the role of ‘Apply a web-filter category action’. In contrast to ‘Enable SSL deep inspection’, ‘Apply a web-filter category action’ follows a different mechanism: web filtering classifies requested sites and applies the configured category or URL action. Treating ‘Enable SSL deep inspection’ as equivalent would not address users can visit an explicitly prohibited class of websites despite cloud web steering in a finance team that uses multiple approved SaaS applications.

Question 170

Within an enterprise interconnecting SD-WAN overlays and cloud security edges, the configuration has been applied. Which measurement or record best confirms the goal to differentiate local branch DIA from traffic genuinely sent to cloud enforcement?

  1. The branch overlay to the service is established and inspected traffic appears in SASE logs.
  2. Matching site flows are observed through the branch on-ramp and SASE enforcement logs.
  3. The intended private prefix is visible through the correct service connection.
  4. An enrolled client resolves the private FQDN through the intended enterprise DNS path.
  5. An explicit hub policy accepts the intended PoP-to-server application flow.

Explanation

Correct Answer

B:

This checks ‘Verify site-based SASE traffic steering’ at the correct operational boundary: site-based on-ramp configuration determines which branch flows are forwarded into FortiSASE. It demonstrates the specific capability to differentiate local branch DIA from traffic genuinely sent to cloud enforcement in an enterprise interconnecting SD-WAN overlays and cloud security edges; deployment should additionally respect the constraint: Make the observed steering decision consistent with routing, policy, and tunnel state.

Incorrect Answers

A:

That observation belongs to ‘Integrate branch SD-WAN with FortiSASE on-ramp’, not ‘Verify site-based SASE traffic steering’; its purpose is to send on-site user internet traffic to FortiSASE cloud inspection using a supported branch edge, the underlying behavior is that a supported FortiGate branch on-ramp can steer site traffic to FortiSASE enforcement PoPs. The reviewer is instead verifying ‘Verify site-based SASE traffic steering’ for an enterprise interconnecting SD-WAN overlays and cloud security edges, not the evidence produced by ‘Integrate branch SD-WAN with FortiSASE on-ramp’.

C:

That observation belongs to ‘Advertise internal prefixes to SPA routing’, not ‘Verify site-based SASE traffic steering’; its purpose is to make specific private data-center networks reachable from security PoPs, the underlying behavior is that routing advertisement or static private routes informs FortiSASE how to reach protected application subnets. The reviewer is instead verifying ‘Verify site-based SASE traffic steering’ for an enterprise interconnecting SD-WAN overlays and cloud security edges, not the evidence produced by ‘Advertise internal prefixes to SPA routing’.

D:

That observation belongs to ‘Configure DNS resolution for private names’, not ‘Verify site-based SASE traffic steering’; its purpose is to let remote users resolve internal application FQDNs to protected addresses, the underlying behavior is that private or split-DNS settings direct internal-name lookups to appropriate enterprise DNS servers. The reviewer is instead verifying ‘Verify site-based SASE traffic steering’ for an enterprise interconnecting SD-WAN overlays and cloud security edges, not the evidence produced by ‘Configure DNS resolution for private names’.

E:

That observation belongs to ‘Allow security PoP access to private applications’, not ‘Verify site-based SASE traffic steering’; its purpose is to permit cloud-originated SPA traffic through the data-center firewall policy, the underlying behavior is that hub-side FortiGate policies authorize FortiSASE service traffic toward the protected servers. The reviewer is instead verifying ‘Verify site-based SASE traffic steering’ for an enterprise interconnecting SD-WAN overlays and cloud security edges, not the evidence produced by ‘Allow security PoP access to private applications’.

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