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

Question 280

Within a SASE change-control review using an authorized test identity, the configuration has been applied. Which measurement or record best confirms the goal to permit approved user traffic before applying cloud-delivered inspection profiles?

  1. The intended operator signs in with an authorized administrative identity.
  2. The tenant dashboard reports provisioned cloud enforcement capacity and accessible administration.
  3. Client connectivity shows active SASE steering to a security PoP.
  4. The matching access policy permits the intended group and references its inspection profile group.
  5. Managed endpoints trust the proper CA and inspected sites validate normally.

Explanation

Correct Answer

D:

This checks ‘Configure a SASE allow policy’ at the correct operational boundary: FortiSASE traffic policies determine which user or destination flows are accepted or denied and which security-profile groups apply. It demonstrates the specific capability to permit approved user traffic before applying cloud-delivered inspection profiles in a SASE change-control review using an authorized test identity; deployment should additionally respect the constraint: A security profile does not independently override a deny access policy.

Incorrect Answers

A:

That observation belongs to ‘Assign FortiSASE administrator access’, not ‘Configure a SASE allow policy’; its purpose is to let a delegated operator manage the cloud configuration without sharing the primary account, the underlying behavior is that distinct authorized administrators enable accountable management while the original account retains ownership. The reviewer is instead verifying ‘Configure a SASE allow policy’ for a SASE change-control review using an authorized test identity, not the evidence produced by ‘Assign FortiSASE administrator access’.

B:

That observation belongs to ‘Verify FortiSASE service provisioning’, not ‘Configure a SASE allow policy’; its purpose is to confirm the cloud security service is available before distributing client configurations, the underlying behavior is that FortiSASE must have an active provisioned instance with security points of presence before managed users can use its cloud enforcement. The reviewer is instead verifying ‘Configure a SASE allow policy’ for a SASE change-control review using an authorized test identity, not the evidence produced by ‘Verify FortiSASE service provisioning’.

C:

That observation belongs to ‘Choose an appropriate security PoP path’, not ‘Configure a SASE allow policy’; its purpose is to bring roaming clients to cloud enforcement rather than hairpin every connection through headquarters, the underlying behavior is that FortiSASE steers supported client traffic toward its security points of presence for consistent remote policy enforcement. The reviewer is instead verifying ‘Configure a SASE allow policy’ for a SASE change-control review using an authorized test identity, not the evidence produced by ‘Choose an appropriate security PoP path’.

E:

That observation belongs to ‘Configure SASE certificate trust’, not ‘Configure a SASE allow policy’; its purpose is to avoid TLS warnings and ensure clients trust the cloud security inspection certificate, the underlying behavior is that when deep inspection is used, managed endpoints need the appropriate inspection CA trust anchor. The reviewer is instead verifying ‘Configure a SASE allow policy’ for a SASE change-control review using an authorized test identity, not the evidence produced by ‘Configure SASE certificate trust’.

Question 281

For a security administrator refining profiles for allowed remote-user traffic, a technical review examines the control ‘Enable intrusion prevention’ for the objective to detect and block network exploits recognized by attack signatures or protocol decoders. Which statement best describes what it changes?

  1. Application Control overrides provide a more specific action than a broad application-category setting.
  2. API-connected CASB can examine supported SaaS tenant content and events without requiring every action to cross the inline proxy.
  3. IPS analyzes supported traffic patterns against intrusion-detection signatures and configured actions.
  4. Deep inspection decrypts eligible TLS sessions at the security service for content-aware scanning.

Explanation

Correct Answer

C:

‘Enable intrusion prevention’ is used to detect and block network exploits recognized by attack signatures or protocol decoders in a security administrator refining profiles for allowed remote-user traffic; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that an IPS security event identifies the signature and the resulting block or monitor action; the rollout must also respect this constraint: IPS coverage depends on the traffic inspection path and enabled profile settings.

Incorrect Answers

A:

The described behavior is part of ‘Use application category overrides’, used to deny one high-risk application within an otherwise permitted collaboration category instead of the role of ‘Enable intrusion prevention’. In contrast to ‘Use application category overrides’, ‘Enable intrusion prevention’ follows a different mechanism: IPS analyzes supported traffic patterns against intrusion-detection signatures and configured actions. Treating ‘Use application category overrides’ as equivalent would not address an exploitation pattern crosses SASE despite the desired intrusion-prevention policy in a security administrator refining profiles for allowed remote-user traffic.

B:

The described behavior is part of ‘Use cloud API CASB for SaaS data at rest’, used to inspect cloud-service data through supported SaaS APIs rather than only inline user sessions instead of the role of ‘Enable intrusion prevention’. In contrast to ‘Use cloud API CASB for SaaS data at rest’, ‘Enable intrusion prevention’ follows a different mechanism: IPS analyzes supported traffic patterns against intrusion-detection signatures and configured actions. Treating ‘Use cloud API CASB for SaaS data at rest’ as equivalent would not address an exploitation pattern crosses SASE despite the desired intrusion-prevention policy in a security administrator refining profiles for allowed remote-user traffic.

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 ‘Enable intrusion prevention’. In contrast to ‘Enable SSL deep inspection’, ‘Enable intrusion prevention’ follows a different mechanism: IPS analyzes supported traffic patterns against intrusion-detection signatures and configured actions. Treating ‘Enable SSL deep inspection’ as equivalent would not address an exploitation pattern crosses SASE despite the desired intrusion-prevention policy in a security administrator refining profiles for allowed remote-user traffic.

Question 282

In a change-control meeting for a FortiSASE tenant being prepared for a 60-user remote-work pilot, a colleague challenges the proposed control ‘Use geolocation-aware access restrictions’ for the requirement to restrict access from locations outside an organization-approved geographic footprint. Which explanation accurately describes its behavior?

  1. FortiSASE steers supported client traffic toward its security points of presence for consistent remote policy enforcement.
  2. Geographic policy criteria can help distinguish traffic by geolocation where FortiSASE policy supports that selection.
  3. Policy edits require verification of the selected rule, security profiles, and resulting traffic logs.
  4. FortiSASE traffic policies determine which user or destination flows are accepted or denied and which security-profile groups apply.

Explanation

Correct Answer

B:

‘Use geolocation-aware access restrictions’ is used to restrict access from locations outside an organization-approved geographic footprint in a FortiSASE tenant being prepared for a 60-user remote-work pilot; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that location-aware policy evaluation blocks the disallowed source geography; the rollout must also respect this constraint: IP geolocation is approximate and must not replace strong user identity controls.

Incorrect Answers

A:

The described behavior is part of ‘Choose an appropriate security PoP path’, used to bring roaming clients to cloud enforcement rather than hairpin every connection through headquarters instead of the role of ‘Use geolocation-aware access restrictions’. In contrast to ‘Choose an appropriate security PoP path’, ‘Use geolocation-aware access restrictions’ follows a different mechanism: geographic policy criteria can help distinguish traffic by geolocation where FortiSASE policy supports that selection. Treating ‘Choose an appropriate security PoP path’ as equivalent would not address remote access occurs from a region that violates the deployment's stated geographic rule in a FortiSASE tenant being prepared for a 60-user remote-work pilot.

C:

The described behavior is part of ‘Manage policy change verification’, used to confirm a modified SASE security policy is active before concluding a remediation is complete instead of the role of ‘Use geolocation-aware access restrictions’. In contrast to ‘Manage policy change verification’, ‘Use geolocation-aware access restrictions’ follows a different mechanism: geographic policy criteria can help distinguish traffic by geolocation where FortiSASE policy supports that selection. Treating ‘Manage policy change verification’ as equivalent would not address remote access occurs from a region that violates the deployment's stated geographic rule in a FortiSASE tenant being prepared for a 60-user remote-work pilot.

D:

The described behavior is part of ‘Configure a SASE allow policy’, used to permit approved user traffic before applying cloud-delivered inspection profiles instead of the role of ‘Use geolocation-aware access restrictions’. In contrast to ‘Configure a SASE allow policy’, ‘Use geolocation-aware access restrictions’ follows a different mechanism: geographic policy criteria can help distinguish traffic by geolocation where FortiSASE policy supports that selection. Treating ‘Configure a SASE allow policy’ as equivalent would not address remote access occurs from a region that violates the deployment's stated geographic rule in a FortiSASE tenant being prepared for a 60-user remote-work pilot.

Question 283

In a change-control meeting for a finance team that uses multiple approved SaaS applications, a design review calls for a way to block a prohibited web category while allowing legitimate business browsing. What should the operator configure?

  1. Use application category overrides
  2. Apply a web-filter category action
  3. Apply an antivirus profile to allowed traffic
  4. Use certificate inspection for metadata-only TLS checks

Explanation

Correct Answer

B:

Web filtering classifies requested sites and applies the configured category or URL action; that scope directly serves the goal to block a prohibited web category while allowing legitimate business browsing in a finance team that uses multiple approved SaaS applications. During implementation, web filtering decisions differ from application-control signatures and DNS resolution policies rather than treating the configuration label as proof of working service.

Incorrect Answers

A:

Application Control overrides provide a more specific action than a broad application-category setting, a mechanism intended to deny one high-risk application within an otherwise permitted collaboration category rather than the requested ‘Apply a web-filter category action’ control. The stated task instead is to block a prohibited web category while allowing legitimate business browsing, and adjusting ‘Use application category overrides’ would not deliver ‘Apply a web-filter category action’. For the ‘Use application category overrides’ alternative to ‘Apply a web-filter category action’, specific overrides should be tested against recognized application signatures.

C:

An enabled antivirus inspection component examines supported file content for malicious signatures or behavior indicators, a mechanism intended to detect malware payloads passing through a permitted cloud access policy rather than the requested ‘Apply a web-filter category action’ control. The stated task instead is to block a prohibited web category while allowing legitimate business browsing, and adjusting ‘Apply an antivirus profile to allowed traffic’ would not deliver ‘Apply a web-filter category action’. For the ‘Apply an antivirus profile to allowed traffic’ alternative to ‘Apply a web-filter category action’, encrypted payload scanning depends on appropriate TLS inspection and certificate trust.

D:

Certificate inspection can evaluate visible TLS metadata but does not expose encrypted HTTP payload contents, a mechanism intended to inspect certificate-related connection metadata without decrypting application bodies rather than the requested ‘Apply a web-filter category action’ control. The stated task instead is to block a prohibited web category while allowing legitimate business browsing, and adjusting ‘Use certificate inspection for metadata-only TLS checks’ would not deliver ‘Apply a web-filter category action’. For the ‘Use certificate inspection for metadata-only TLS checks’ alternative to ‘Apply a web-filter category action’, choose deep inspection when the requirement actually depends on encrypted content visibility.

Question 284

During an authorized lab exercise for a policy owner protecting HTTPS web sessions without blocking business use, the acceptance criteria require the team to stop requests to known malicious or restricted domains at the DNS layer. Which control meets that requirement?

  1. Configure file filtering
  2. Enable SSL deep inspection
  3. Apply remote browser isolation for risky sites
  4. Use DNS filtering

Explanation

Correct Answer

D:

DNS Filter evaluates domain lookup activity before a client establishes a normal destination session; that scope directly serves the goal to stop requests to known malicious or restricted domains at the DNS layer in a policy owner protecting HTTPS web sessions without blocking business use. During implementation, DNS filtering cannot inspect the contents of an already established HTTPS session rather than treating the configuration label as proof of working service.

Incorrect Answers

A:

File Filter identifies supported file types in inspected sessions and enforces the configured file action, a mechanism intended to block transfer of prohibited file types regardless of benign website category rather than the requested ‘Use DNS filtering’ control. The stated task instead is to stop requests to known malicious or restricted domains at the DNS layer, and adjusting ‘Configure file filtering’ would not deliver ‘Use DNS filtering’. For the ‘Configure file filtering’ alternative to ‘Use DNS filtering’, encrypted transfers need suitable deep inspection for content-aware file filtering.

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 ‘Use DNS filtering’ control. The stated task instead is to stop requests to known malicious or restricted domains at the DNS layer, and adjusting ‘Enable SSL deep inspection’ would not deliver ‘Use DNS filtering’. For the ‘Enable SSL deep inspection’ alternative to ‘Use DNS filtering’, certificate deployment and inspection exemptions must be handled to avoid breaking legitimate services.

C:

Remote Browser Isolation executes supported browsing in an isolated remote context and streams a safer representation, a mechanism intended to isolate web rendering from the endpoint when access is required to a questionable website rather than the requested ‘Use DNS filtering’ control. The stated task instead is to stop requests to known malicious or restricted domains at the DNS layer, and adjusting ‘Apply remote browser isolation for risky sites’ would not deliver ‘Use DNS filtering’. For the ‘Apply remote browser isolation for risky sites’ alternative to ‘Use DNS filtering’, RBI mitigates browser-execution exposure; it is not a substitute for identity verification.

Question 285

Within a remote call center measuring two ISP paths to the same application target, the team wants to avoid an ineffective configuration of ‘Investigate alive versus SLA-qualified state’. Which consideration deserves attention?

  1. Do not equate successful probes with meeting every target threshold.
  2. Choosing best quality differs from deciding which member has the smallest monetary cost.
  3. Healthy alternate routing must exist for traffic to continue.
  4. A failed probe does not by itself prove the physical carrier link is down.
  5. A current snapshot cannot reconstruct past jitter, loss, and threshold violations by itself.

Explanation

Correct Answer

A:

This condition matters for ‘Investigate alive versus SLA-qualified state’ because a member may be reachable and report alive while failing a stricter SLA target for performance. Omitting the relevant safeguard can produce an interface is alive in health-check output but excluded from a latency-sensitive rule; a successful test at a remote call center measuring two ISP paths to the same application target would instead demonstrate that the health data shows alive status yet a failed SLA for the same member.

Incorrect Answers

B:

The condition is associated with ‘Use SLA measurements for best-quality steering’, a mechanism used to feed measured latency, jitter, or loss into a dynamic path-selection rule instead of ‘Investigate alive versus SLA-qualified state’, because Best Quality uses configured quality criteria derived from a health check to prioritize the most suitable available member. For ‘Investigate alive versus SLA-qualified state’, unlike ‘Use SLA measurements for best-quality steering’, the characteristic failure would be an interface is alive in health-check output but excluded from a latency-sensitive rule, which this alternative prerequisite would not directly address at a remote call center measuring two ISP paths to the same application target.

C:

The condition is associated with ‘Use probe loss to trigger failover’, a mechanism used to remove a genuinely unreachable transport from eligible load-balancing routes instead of ‘Investigate alive versus SLA-qualified state’, because failed health checks can withdraw the broken member's routes from the SD-WAN eligible path group. For ‘Investigate alive versus SLA-qualified state’, unlike ‘Use probe loss to trigger failover’, the characteristic failure would be an interface is alive in health-check output but excluded from a latency-sensitive rule, which this alternative prerequisite would not directly address at a remote call center measuring two ISP paths to the same application target.

D:

The condition is associated with ‘Check probe-path asymmetry’, a mechanism used to confirm health responses return correctly when transport routes are asymmetric instead of ‘Investigate alive versus SLA-qualified state’, because health tests depend on packets reaching the target and return traffic finding a valid response path. For ‘Investigate alive versus SLA-qualified state’, unlike ‘Check probe-path asymmetry’, the characteristic failure would be an interface is alive in health-check output but excluded from a latency-sensitive rule, which this alternative prerequisite would not directly address at a remote call center measuring two ISP paths to the same application target.

E:

The condition is associated with ‘Review SLA historical changes’, a mechanism used to establish whether a brief performance decline coincides with a reported outage instead of ‘Investigate alive versus SLA-qualified state’, because historical SLA samples and logs help distinguish transient degradation from a persistent member failure. For ‘Investigate alive versus SLA-qualified state’, unlike ‘Review SLA historical changes’, the characteristic failure would be an interface is alive in health-check output but excluded from a latency-sensitive rule, which this alternative prerequisite would not directly address at a remote call center measuring two ISP paths to the same application target.

Question 286

Within a dual-carrier site separating internet transport from data-center overlays, after the rollout, operators find that two otherwise equivalent members do not follow the expected fallback order. Where should they focus troubleshooting?

  1. Investigate: Use a FortiExtender interface member
  2. Investigate: Set member fallback priority
  3. Investigate: Use a VLAN interface as a member
  4. Investigate: Disable a maintenance member
  5. Investigate: Assign members to the intended zone

Explanation

Correct Answer

B:

The symptom identifies the missing operational behavior: a lower member priority value takes precedence when the routing or SD-WAN selection uses priority. For a dual-carrier site separating internet transport from data-center overlays, a direct diagnostic confirmation would be that the member status shows the intended lower numerical priority on the preferred circuit; during repair, priority is not a substitute for configuring measured quality criteria.

Incorrect Answers

A:

A FortiExtender-provided network interface can participate as an SD-WAN member alongside wired transports, which serves the different requirement to include a cellular backup path in SD-WAN selection instead of the behavior delivered by ‘Set member fallback priority’. If that component were misconfigured, a more characteristic finding would be that the LTE backup shows connectivity in its device view but is never considered for SD-WAN; the actual report concerns two otherwise equivalent members do not follow the expected fallback order at a dual-carrier site separating internet transport from data-center overlays.

C:

An SD-WAN member may reference a VLAN interface rather than only an untagged physical port, which serves the different requirement to steer traffic over a tagged Ethernet handoff from an ISP instead of the behavior delivered by ‘Set member fallback priority’. If that component were misconfigured, a more characteristic finding would be that the provider's tagged circuit is up at layer two but no logical tagged WAN is selectable; the actual report concerns two otherwise equivalent members do not follow the expected fallback order at a dual-carrier site separating internet transport from data-center overlays.

D:

Disabling an SD-WAN member removes it from eligible SD-WAN selection without requiring deletion of its configuration, which serves the different requirement to exclude a WAN circuit from SD-WAN decisions during scheduled carrier work instead of the behavior delivered by ‘Set member fallback priority’. If that component were misconfigured, a more characteristic finding would be that the drained circuit is still chosen for new flows during maintenance; the actual report concerns two otherwise equivalent members do not follow the expected fallback order at a dual-carrier site separating internet transport from data-center overlays.

E:

A member's zone association determines which zone-based routes and policies can use that interface, which serves the different requirement to put two ISP circuits in the internet transport zone rather than the private-overlay group instead of the behavior delivered by ‘Set member fallback priority’. If that component were misconfigured, a more characteristic finding would be that wan2 is operational but traffic for the transport zone cannot select it; the actual report concerns two otherwise equivalent members do not follow the expected fallback order at a dual-carrier site separating internet transport from data-center overlays.

Question 287

In a change-control meeting for a branch experiencing intermittent packet loss during video meetings, a design review calls for a way to establish whether a brief performance decline coincides with a reported outage. What should the operator configure?

  1. Use probe loss to trigger failover
  2. Set packet-loss SLA threshold
  3. Review SLA historical changes
  4. Select the correct probe server

Explanation

Correct Answer

C:

Historical SLA samples and logs help distinguish transient degradation from a persistent member failure; that scope directly serves the goal to establish whether a brief performance decline coincides with a reported outage in a branch experiencing intermittent packet loss during video meetings. During implementation, a current snapshot cannot reconstruct past jitter, loss, and threshold violations by itself rather than treating the configuration label as proof of working service.

Incorrect Answers

A:

Failed health checks can withdraw the broken member's routes from the SD-WAN eligible path group, a mechanism intended to remove a genuinely unreachable transport from eligible load-balancing routes rather than the requested ‘Review SLA historical changes’ control. The stated task instead is to establish whether a brief performance decline coincides with a reported outage, and adjusting ‘Use probe loss to trigger failover’ would not deliver ‘Review SLA historical changes’. For the ‘Use probe loss to trigger failover’ alternative to ‘Review SLA historical changes’, healthy alternate routing must exist for traffic to continue.

B:

A loss target evaluates the fraction of missing probes or measured packets before declaring SLA compliance, a mechanism intended to protect application sessions from a link that intermittently drops packets rather than the requested ‘Review SLA historical changes’ control. The stated task instead is to establish whether a brief performance decline coincides with a reported outage, and adjusting ‘Set packet-loss SLA threshold’ would not deliver ‘Review SLA historical changes’. For the ‘Set packet-loss SLA threshold’ alternative to ‘Review SLA historical changes’, check loss independently of latency and jitter instead of inferring it from link-up state.

D:

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 ‘Review SLA historical changes’ control. The stated task instead is to establish whether a brief performance decline coincides with a reported outage, and adjusting ‘Select the correct probe server’ would not deliver ‘Review SLA historical changes’. For the ‘Select the correct probe server’ alternative to ‘Review SLA historical changes’, the measurement endpoint must be reliably reachable and appropriate to the application.

Question 288

At a cloud security tenant inspecting traffic from managed remote laptops, an engineer is preparing ‘Use inline CASB HTTP header restrictions’ to restrict which SaaS tenant a managed user may access by adjusting inspected web request headers. Which TWO statements identify a pertinent deployment safeguard and a direct post-change validation result? Choose TWO.

  1. Use the narrowest necessary exception to avoid weakening protection broadly.
  2. The SaaS provider must support the header convention and the request must be inspectable.
  3. Encrypted transfers need suitable deep inspection for content-aware file filtering.
  4. Outgoing SaaS requests contain the configured tenant-restriction header under the inline policy.
  5. The site is rendered within the configured isolation workflow rather than the local browser engine.

Explanation

Correct Answers

B:

This safeguard applies to ‘Use inline CASB HTTP header restrictions’, which works because Web Filter with Inline-CASB can insert or alter supported outbound HTTP headers to enforce SaaS tenant restrictions. Without the correct deployment condition, operators may see that staff can sign into unapproved personal SaaS tenants despite being allowed the business SaaS domain in a cloud security tenant inspecting traffic from managed remote laptops.

D:

The observation follows from the operation of ‘Use inline CASB HTTP header restrictions’: Web Filter with Inline-CASB can insert or alter supported outbound HTTP headers to enforce SaaS tenant restrictions. It directly tests the requested ability to restrict which SaaS tenant a managed user may access by adjusting inspected web request headers in a cloud security tenant inspecting traffic from managed remote laptops, rather than another policy or network layer.

Incorrect Answers

A:

The planning point is associated with ‘Use a specific URL filter exception’, not ‘Use inline CASB HTTP header restrictions’; its real role is to allow a justified business website without disabling an entire restrictive category. The required deployment instead centers on ‘Use inline CASB HTTP header restrictions’, rather than ‘Use a specific URL filter exception’; the distinct symptom to guard against is that staff can sign into unapproved personal SaaS tenants despite being allowed the business SaaS domain.

C:

The planning point is associated with ‘Configure file filtering’, not ‘Use inline CASB HTTP header restrictions’; its real role is to block transfer of prohibited file types regardless of benign website category. The required deployment instead centers on ‘Use inline CASB HTTP header restrictions’, rather than ‘Configure file filtering’; the distinct symptom to guard against is that staff can sign into unapproved personal SaaS tenants despite being allowed the business SaaS domain.

E:

This result would validate ‘Apply remote browser isolation for risky sites’, not ‘Use inline CASB HTTP header restrictions’, because remote Browser Isolation executes supported browsing in an isolated remote context and streams a safer representation. That separate implementation serves isolate web rendering from the endpoint when access is required to a questionable website, whereas the audit needs evidence specifically of ‘Use inline CASB HTTP header restrictions’ at a cloud security tenant inspecting traffic from managed remote laptops.

Question 289

Within a dispersed workforce that uses a corporate SAML identity provider, after the rollout, operators find that a previously trusted endpoint no longer supplies the expected posture information after disconnecting. Where should they focus troubleshooting?

  1. Investigate: Configure agentless proxy SSO
  2. Investigate: Account for SSO precedence over other methods
  3. Investigate: Import users through LDAP
  4. Investigate: Configure RADIUS authentication
  5. Investigate: Maintain FortiClient tenant registration

Explanation

Correct Answer

E:

The symptom identifies the missing operational behavior: registered FortiClient maintains connectivity with FortiSASE endpoint management and supplies identity or posture data. For a dispersed workforce that uses a corporate SAML identity provider, a direct diagnostic confirmation would be that the managed client reports active registration and current posture telemetry; during repair, ZTNA decisions may depend on fresh registration and endpoint state.

Incorrect Answers

A:

SWG SSO authenticates a web proxy session using the configured identity provider, which serves the different requirement to associate proxied browser traffic with enterprise user identity during secure web gateway inspection instead of the behavior delivered by ‘Maintain FortiClient tenant registration’. If that component were misconfigured, a more characteristic finding would be that proxy requests arrive but user-based policies cannot associate them with an authenticated identity; the actual report concerns a previously trusted endpoint no longer supplies the expected posture information after disconnecting at a dispersed workforce that uses a corporate SAML identity provider.

B:

Enabling FortiSASE SSO takes precedence over previously configured user authentication methods, which serves the different requirement to avoid expecting local or RADIUS credentials to work after enabling SAML SSO instead of the behavior delivered by ‘Maintain FortiClient tenant registration’. If that component were misconfigured, a more characteristic finding would be that an old LDAP-based login stops working immediately after the SAML SSO cutover; the actual report concerns a previously trusted endpoint no longer supplies the expected posture information after disconnecting at a dispersed workforce that uses a corporate SAML identity provider.

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 ‘Maintain FortiClient tenant registration’. 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 previously trusted endpoint no longer supplies the expected posture information after disconnecting at a dispersed workforce that uses a corporate SAML identity provider.

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 ‘Maintain FortiClient tenant registration’. 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 previously trusted endpoint no longer supplies the expected posture information after disconnecting at a dispersed workforce that uses a corporate SAML identity provider.

Question 290

During an authorized lab exercise for a hub-and-spoke network with internet breakout and private IPsec overlays, the incident notes state that partner traffic exits public internet despite a required private-subnet route being missing. Which change is most relevant to this symptom?

  1. Investigate: Configure a static partner route through overlay zone
  2. Investigate: Install default route through an SD-WAN zone
  3. Investigate: Prefer a more specific prefix
  4. Investigate: Confirm return route for remote private access

Explanation

Correct Answer

C:

The symptom identifies the missing operational behavior: longest-prefix match chooses a more specific valid destination route ahead of a broader default. For a hub-and-spoke network with internet breakout and private IPsec overlays, a direct diagnostic confirmation would be that the routing table has a valid longer-prefix route to the partner CIDR; during repair, SD-WAN application preference cannot create missing reachability to an internal network.

Incorrect Answers

A:

A destination-specific static route referencing the overlay zone makes private routes accessible to SD-WAN selection, which serves the different requirement to reach an on-premises network across an IPsec overlay SD-WAN group instead of the behavior delivered by ‘Prefer a more specific prefix’. If that component were misconfigured, a more characteristic finding would be that the overlay tunnels are healthy but the remote private prefix lacks a usable route; the actual report concerns partner traffic exits public internet despite a required private-subnet route being missing at a hub-and-spoke network with internet breakout and private IPsec overlays.

B:

A zone-based default static route gives SD-WAN a routing candidate for nonlocal destinations, which serves the different requirement to make general internet destinations reachable without listing every WAN member as a separate policy interface instead of the behavior delivered by ‘Prefer a more specific prefix’. If that component were misconfigured, a more characteristic finding would be that the WAN health monitors pass but the route lookup has no path for 0.0.0.0/0; the actual report concerns partner traffic exits public internet despite a required private-subnet route being missing at a hub-and-spoke network with internet breakout and private IPsec overlays.

D:

Bidirectional reachability requires the remote hub or server-side router to return traffic to the client prefix, which serves the different requirement to repair one-way traffic where forward packets reach the data center but replies do not instead of the behavior delivered by ‘Prefer a more specific prefix’. If that component were misconfigured, a more characteristic finding would be that SYN packets arrive at the protected application but no responses reach the branch client; the actual report concerns partner traffic exits public internet despite a required private-subnet route being missing at a hub-and-spoke network with internet breakout and private IPsec overlays.

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