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

Question 570

At a branch outage review comparing session entries and SLA histories, a support engineer needs to verify that ‘Inspect member health-check output’ is active for the goal to explain why a link was removed from service despite remaining physically up. Which observation is decisive?

  1. The relevant health-check record identifies the failed metric or probe state.
  2. The timeline connects health deterioration with the observed member transition.
  3. A traffic log contains the controlled flow's policy match, interface, and disposition.
  4. The service diagnostic lists the active selected member and alternate eligible candidates.

Explanation

Correct Answer

A:

This checks ‘Inspect member health-check output’ at the correct operational boundary: health-check diagnostics expose alive state, loss, latency, jitter, and SLA qualification. It demonstrates the specific capability to explain why a link was removed from service despite remaining physically up in a branch outage review comparing session entries and SLA histories; deployment should additionally respect the constraint: Correlate the event to the health-check target and time of the complaint.

Incorrect Answers

B:

That observation belongs to ‘Correlate a failover event with SLA history’, not ‘Inspect member health-check output’; its purpose is to differentiate an ISP performance event from a later manual service-rule edit, the underlying behavior is that time-aligned SLA logs and service events can show when a member failed and traffic was redirected. The reviewer is instead verifying ‘Inspect member health-check output’ for a branch outage review comparing session entries and SLA histories, not the evidence produced by ‘Correlate a failover event with SLA history’.

C:

That observation belongs to ‘Review a matched firewall traffic log’, not ‘Inspect member health-check output’; its purpose is to trace a user's source, destination, policy ID, session, and egress interface, the underlying behavior is that traffic logs supply session-level context needed to correlate SD-WAN steering with firewall authorization. The reviewer is instead verifying ‘Inspect member health-check output’ for a branch outage review comparing session entries and SLA histories, not the evidence produced by ‘Review a matched firewall traffic log’.

D:

That observation belongs to ‘Inspect selected member in service diagnostics’, not ‘Inspect member health-check output’; its purpose is to establish which egress candidate an SD-WAN service is actively using, the underlying behavior is that SD-WAN service diagnostics show selected members, eligibility, and rule selection behavior. The reviewer is instead verifying ‘Inspect member health-check output’ for a branch outage review comparing session entries and SLA histories, not the evidence produced by ‘Inspect selected member in service diagnostics’.

Question 571

During an authorized lab exercise for a company enrolling remote Windows and macOS employees into FortiSASE, the incident notes state that proxy requests arrive but user-based policies cannot associate them with an authenticated identity. Which change is most relevant to this symptom?

  1. Investigate: Configure RADIUS authentication
  2. Investigate: Use preconfigured FortiClient installers
  3. Investigate: Import users through LDAP
  4. Investigate: Configure agentless proxy SSO

Explanation

Correct Answer

D:

The symptom identifies the missing operational behavior: sWG SSO authenticates a web proxy session using the configured identity provider. For a company enrolling remote Windows and macOS employees into FortiSASE, a direct diagnostic confirmation would be that a controlled browser request establishes an SSO user session for the cloud proxy; during repair, proxy SSO often depends on compatible deep inspection and IdP reachability.

Incorrect Answers

A:

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 ‘Configure agentless proxy SSO’. 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 proxy requests arrive but user-based policies cannot associate them with an authenticated identity at a company enrolling remote Windows and macOS employees into FortiSASE.

B:

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 ‘Configure agentless proxy SSO’. 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 proxy requests arrive but user-based policies cannot associate them with an authenticated identity at a company enrolling remote Windows and macOS employees into FortiSASE.

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 ‘Configure agentless proxy SSO’. 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 proxy requests arrive but user-based policies cannot associate them with an authenticated identity at a company enrolling remote Windows and macOS employees into FortiSASE.

Question 572

In a change-control meeting for a service desk test lab with two addressed carriers and an internal user VLAN, acceptance testing shows that outbound sessions leave an ISP circuit with unroutable private source addresses. Which control should be investigated first?

  1. Investigate: Enable interface-based source NAT
  2. Investigate: Allow LAN-to-SD-WAN firewall policy
  3. Investigate: Set a static WAN member gateway
  4. Investigate: Use DHCP-provided WAN gateway

Explanation

Correct Answer

A:

The symptom identifies the missing operational behavior: source NAT using the outgoing interface address permits private LAN hosts to communicate through each public ISP path. For a service desk test lab with two addressed carriers and an internal user VLAN, a direct diagnostic confirmation would be that a flow trace shows translation to the chosen WAN interface's public address; during repair, the NAT decision belongs in the applicable firewall policy and must match the routing design.

Incorrect Answers

B:

The stateful firewall policy permits internal-to-zone sessions and can apply source NAT and inspection as required, which serves the different requirement to authorize office clients to reach external destinations over eligible SD-WAN members instead of the behavior delivered by ‘Enable interface-based source NAT’. If that component were misconfigured, a more characteristic finding would be that an eligible WAN path exists but LAN clients match no accept firewall policy; the actual report concerns outbound sessions leave an ISP circuit with unroutable private source addresses at a service desk test lab with two addressed carriers and an internal user VLAN.

C:

A statically addressed SD-WAN member must use the reachable ISP next hop for proper packet forwarding, which serves the different requirement to reach an ISP next hop on a manually numbered uplink instead of the behavior delivered by ‘Enable interface-based source NAT’. If that component were misconfigured, a more characteristic finding would be that the link shows carrier but packets are sent toward an incorrect next-hop address; the actual report concerns outbound sessions leave an ISP circuit with unroutable private source addresses at a service desk test lab with two addressed carriers and an internal user VLAN.

D:

An SD-WAN member on a DHCP WAN can inherit the gateway learned from the DHCP interface, which serves the different requirement to keep a dynamically assigned ISP next hop aligned with lease changes instead of the behavior delivered by ‘Enable interface-based source NAT’. If that component were misconfigured, a more characteristic finding would be that the dynamic WAN lease renews but a hard-coded obsolete gateway is still being used; the actual report concerns outbound sessions leave an ISP circuit with unroutable private source addresses at a service desk test lab with two addressed carriers and an internal user VLAN.

Question 573

At a company enrolling remote Windows and macOS employees into FortiSASE, the change request is to associate proxied browser traffic with enterprise user identity during secure web gateway inspection. Which configuration is the most direct fit?

  1. Distribute a FortiSASE invitation code
  2. Account for SSO precedence over other methods
  3. Match endpoint profiles to the correct user group
  4. Configure agentless proxy SSO

Explanation

Correct Answer

D:

SWG SSO authenticates a web proxy session using the configured identity provider; that scope directly serves the goal to associate proxied browser traffic with enterprise user identity during secure web gateway inspection in a company enrolling remote Windows and macOS employees into FortiSASE. During implementation, proxy SSO often depends on compatible deep inspection and IdP reachability rather than treating the configuration label as proof of working service.

Incorrect Answers

A:

The Onboard Users workflow provides information that remote users use for FortiSASE client registration, a mechanism intended to bind an invited remote user's FortiClient enrollment to the correct organization rather than the requested ‘Configure agentless proxy SSO’ control. The stated task instead is to associate proxied browser traffic with enterprise user identity during secure web gateway inspection, and adjusting ‘Distribute a FortiSASE invitation code’ would not deliver ‘Configure agentless proxy SSO’. For the ‘Distribute a FortiSASE invitation code’ alternative to ‘Configure agentless proxy SSO’, onboarding credentials should be shared only with the intended users.

B:

Enabling FortiSASE SSO takes precedence over previously configured user authentication methods, a mechanism intended to avoid expecting local or RADIUS credentials to work after enabling SAML SSO rather than the requested ‘Configure agentless proxy SSO’ control. The stated task instead is to associate proxied browser traffic with enterprise user identity during secure web gateway inspection, and adjusting ‘Account for SSO precedence over other methods’ would not deliver ‘Configure agentless proxy SSO’. For the ‘Account for SSO precedence over other methods’ alternative to ‘Configure agentless proxy SSO’, plan identity migration and test group mapping before enabling organizational SSO.

C:

Endpoint profiles can be assigned according to relevant groups or administrative selection, a mechanism intended to deliver one set of endpoint controls to contractors and a stricter set to employees rather than the requested ‘Configure agentless proxy SSO’ control. The stated task instead is to associate proxied browser traffic with enterprise user identity during secure web gateway inspection, and adjusting ‘Match endpoint profiles to the correct user group’ would not deliver ‘Configure agentless proxy SSO’. For the ‘Match endpoint profiles to the correct user group’ alternative to ‘Configure agentless proxy SSO’, profile assignment must be checked separately from cloud traffic-policy ordering.

Question 574

During an authorized lab exercise for a branch FortiGate that terminates an ISP handoff and two IPsec tunnels, the incident notes state that the port works but is reachable only through policies for the old zone. Which change is most relevant to this symptom?

  1. Investigate: Use an IPsec interface as a member
  2. Investigate: Use an aggregate interface as a member
  3. Investigate: Move a member between zones
  4. Investigate: Disable a maintenance member

Explanation

Correct Answer

C:

The symptom identifies the missing operational behavior: reassigning the member to a different zone changes its logical policy and rule membership. For a branch FortiGate that terminates an ISP handoff and two IPsec tunnels, a direct diagnostic confirmation would be that the member now appears in the target zone and corresponding policies use it; during repair, review policies and static routes referencing the source zone before moving the member.

Incorrect Answers

A:

Route-based IPsec tunnel interfaces can be members whose quality is measured and selected for overlay routing, which serves the different requirement to apply SD-WAN selection to redundant encrypted site-to-site paths instead of the behavior delivered by ‘Move a member between zones’. If that component were misconfigured, a more characteristic finding would be that the VPN tunnel passes traffic manually but is absent from overlay service member lists; the actual report concerns the port works but is reachable only through policies for the old zone at a branch FortiGate that terminates an ISP handoff and two IPsec tunnels.

B:

A link aggregation interface can be an SD-WAN member while LAG distributes frames across its constituent ports, which serves the different requirement to treat an LAG upstream handoff as a selectable SD-WAN transport instead of the behavior delivered by ‘Move a member between zones’. If that component were misconfigured, a more characteristic finding would be that the administrator adds member ports separately although they belong to one provider LAG; the actual report concerns the port works but is reachable only through policies for the old zone at a branch FortiGate that terminates an ISP handoff and two IPsec tunnels.

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 ‘Move a member between zones’. 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 the port works but is reachable only through policies for the old zone at a branch FortiGate that terminates an ISP handoff and two IPsec tunnels.

Question 575

At a medical office prioritizing stable response times to a hosted patient system, the change board is evaluating ‘Select the correct probe server’. Which technical consideration must be built into the plan?

  1. The measurement endpoint must be reliably reachable and appropriate to the application.
  2. Thresholds must be realistic for the probe destination and business application.
  3. Choosing best quality differs from deciding which member has the smallest monetary cost.
  4. Do not equate successful probes with meeting every target threshold.

Explanation

Correct Answer

A:

This condition matters for ‘Select the correct probe server’ because health checks against a representative reachable target include more of the application path than checks aimed only at the immediate gateway. Omitting the relevant safeguard can produce all circuits reach their gateways but the real remote service path is impaired; a successful test at a medical office prioritizing stable response times to a hosted patient system would instead demonstrate that probe results to the intended external target reflect the actual remote-path problem.

Incorrect Answers

B:

The condition is associated with ‘Set latency SLA threshold’, a mechanism used to exclude paths whose round-trip delay exceeds a real-time application's bound instead of ‘Select the correct probe server’, because a latency target makes a member fail that SLA when measured delay exceeds the configured limit. For ‘Select the correct probe server’, unlike ‘Set latency SLA threshold’, the characteristic failure would be all circuits reach their gateways but the real remote service path is impaired, which this alternative prerequisite would not directly address at a medical office prioritizing stable response times to a hosted patient system.

C:

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 ‘Select the correct probe server’, because Best Quality uses configured quality criteria derived from a health check to prioritize the most suitable available member. For ‘Select the correct probe server’, unlike ‘Use SLA measurements for best-quality steering’, the characteristic failure would be all circuits reach their gateways but the real remote service path is impaired, which this alternative prerequisite would not directly address at a medical office prioritizing stable response times to a hosted patient system.

D:

The condition is associated with ‘Investigate alive versus SLA-qualified state’, a mechanism used to distinguish basic connectivity from acceptable application performance instead of ‘Select the correct probe server’, because a member may be reachable and report alive while failing a stricter SLA target for performance. For ‘Select the correct probe server’, unlike ‘Investigate alive versus SLA-qualified state’, the characteristic failure would be all circuits reach their gateways but the real remote service path is impaired, which this alternative prerequisite would not directly address at a medical office prioritizing stable response times to a hosted patient system.

Question 576

Within a private-access rollout spanning two data-center hubs, the operator applies the control ‘Use IPsec transport for the SASE branch connection’ as part of an effort to carry branch traffic securely across an untrusted ISP toward a SASE service edge. Which operating behavior should the team expect?

  1. An SD-WAN-based SPA design can provide routed access to private TCP and UDP applications.
  2. An IPsec-based on-ramp encapsulates site traffic for cloud delivery over the public underlay.
  3. FortiGate can provide the secure private access hub that forwards authorized cloud-to-private traffic.
  4. A supported FortiGate branch on-ramp can steer site traffic to FortiSASE enforcement PoPs.
  5. ZTNA private access targets authorized TCP applications rather than granting generic network reachability.

Explanation

Correct Answer

B:

‘Use IPsec transport for the SASE branch connection’ is used to carry branch traffic securely across an untrusted ISP toward a SASE service edge in a private-access rollout spanning two data-center hubs; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that the secure IPsec association is established to the intended cloud edge; the rollout must also respect this constraint: IKE negotiations and underlay routing must work before traffic steering over the tunnel.

Incorrect Answers

A:

The described behavior is part of ‘Use SD-WAN private access for TCP and UDP’, used to extend private resource connectivity beyond the TCP-focused ZTNA access proxy model instead of the role of ‘Use IPsec transport for the SASE branch connection’. In contrast to ‘Use SD-WAN private access for TCP and UDP’, ‘Use IPsec transport for the SASE branch connection’ follows a different mechanism: an IPsec-based on-ramp encapsulates site traffic for cloud delivery over the public underlay. Treating ‘Use SD-WAN private access for TCP and UDP’ as equivalent would not address branch packets are routed directly to internet without the configured secure service tunnel in a private-access rollout spanning two data-center hubs.

C:

The described behavior is part of ‘Use FortiGate as a private-access hub’, used to connect remote FortiSASE clients to data-center applications protected behind a FortiGate instead of the role of ‘Use IPsec transport for the SASE branch connection’. In contrast to ‘Use FortiGate as a private-access hub’, ‘Use IPsec transport for the SASE branch connection’ follows a different mechanism: an IPsec-based on-ramp encapsulates site traffic for cloud delivery over the public underlay. Treating ‘Use FortiGate as a private-access hub’ as equivalent would not address branch packets are routed directly to internet without the configured secure service tunnel in a private-access rollout spanning two data-center hubs.

D:

The described behavior is part of ‘Integrate branch SD-WAN with FortiSASE on-ramp’, used to send on-site user internet traffic to FortiSASE cloud inspection using a supported branch edge instead of the role of ‘Use IPsec transport for the SASE branch connection’. In contrast to ‘Integrate branch SD-WAN with FortiSASE on-ramp’, ‘Use IPsec transport for the SASE branch connection’ follows a different mechanism: an IPsec-based on-ramp encapsulates site traffic for cloud delivery over the public underlay. Treating ‘Integrate branch SD-WAN with FortiSASE on-ramp’ as equivalent would not address branch packets are routed directly to internet without the configured secure service tunnel in a private-access rollout spanning two data-center hubs.

E:

The described behavior is part of ‘Use ZTNA application proxy for a protected TCP app’, used to publish a narrowly scoped internal TCP application through a FortiGate ZTNA gateway instead of the role of ‘Use IPsec transport for the SASE branch connection’. In contrast to ‘Use ZTNA application proxy for a protected TCP app’, ‘Use IPsec transport for the SASE branch connection’ follows a different mechanism: an IPsec-based on-ramp encapsulates site traffic for cloud delivery over the public underlay. Treating ‘Use ZTNA application proxy for a protected TCP app’ as equivalent would not address branch packets are routed directly to internet without the configured secure service tunnel in a private-access rollout spanning two data-center hubs.

Question 577

During an authorized lab exercise for a branch experiencing intermittent packet loss during video meetings, the deployment standard specifies the control ‘Review SLA historical changes’ to establish whether a brief performance decline coincides with a reported outage. Which functional description matches it?

  1. Historical SLA samples and logs help distinguish transient degradation from a persistent member failure.
  2. A latency target makes a member fail that SLA when measured delay exceeds the configured limit.
  3. An SD-WAN health check monitors the configured member interfaces instead of automatically representing every interface.
  4. Health checks against a representative reachable target include more of the application path than checks aimed only at the immediate gateway.

Explanation

Correct Answer

A:

‘Review SLA historical changes’ is used to establish whether a brief performance decline coincides with a reported outage in a branch experiencing intermittent packet loss during video meetings; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that recorded SLA-quality history shows the earlier failed interval and subsequent recovery; the rollout must also respect this constraint: A current snapshot cannot reconstruct past jitter, loss, and threshold violations by itself.

Incorrect Answers

B:

The described behavior is part of ‘Set latency SLA threshold’, used to exclude paths whose round-trip delay exceeds a real-time application's bound instead of the role of ‘Review SLA historical changes’. In contrast to ‘Set latency SLA threshold’, ‘Review SLA historical changes’ follows a different mechanism: historical SLA samples and logs help distinguish transient degradation from a persistent member failure. Treating ‘Set latency SLA threshold’ as equivalent would not address a link is healthy now but the outage timeline is unexplained in a branch experiencing intermittent packet loss during video meetings.

C:

The described behavior is part of ‘Assign the relevant member set to a health check’, used to compare only the transport members serving a given application class instead of the role of ‘Review SLA historical changes’. In contrast to ‘Assign the relevant member set to a health check’, ‘Review SLA historical changes’ follows a different mechanism: historical SLA samples and logs help distinguish transient degradation from a persistent member failure. Treating ‘Assign the relevant member set to a health check’ as equivalent would not address a link is healthy now but the outage timeline is unexplained in a branch experiencing intermittent packet loss during video meetings.

D:

The described behavior is part of ‘Select the correct probe server’, used to measure user-relevant path health rather than only the nearest ISP hop instead of the role of ‘Review SLA historical changes’. In contrast to ‘Select the correct probe server’, ‘Review SLA historical changes’ follows a different mechanism: historical SLA samples and logs help distinguish transient degradation from a persistent member failure. Treating ‘Select the correct probe server’ as equivalent would not address a link is healthy now but the outage timeline is unexplained in a branch experiencing intermittent packet loss during video meetings.

Question 578

In a change-control meeting for a hub-and-spoke network with internet breakout and private IPsec overlays, a colleague challenges the proposed control ‘Prefer a more specific prefix’ for the requirement to send a partner network into a private tunnel even while default internet routing is present. Which explanation accurately describes its behavior?

  1. A zone-based default static route gives SD-WAN a routing candidate for nonlocal destinations.
  2. Longest-prefix match chooses a more specific valid destination route ahead of a broader default.
  3. SD-WAN candidate preference works only after routing makes a compatible egress path available.
  4. Route inspection distinguishes absent routes from member cost or performance rankings.

Explanation

Correct Answer

B:

‘Prefer a more specific prefix’ is used to send a partner network into a private tunnel even while default internet routing is present in a hub-and-spoke network with internet breakout and private IPsec overlays; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that the routing table has a valid longer-prefix route to the partner CIDR; the rollout must also respect this constraint: SD-WAN application preference cannot create missing reachability to an internal network.

Incorrect Answers

A:

The described behavior is part of ‘Install default route through an SD-WAN zone’, used to make general internet destinations reachable without listing every WAN member as a separate policy interface instead of the role of ‘Prefer a more specific prefix’. In contrast to ‘Install default route through an SD-WAN zone’, ‘Prefer a more specific prefix’ follows a different mechanism: longest-prefix match chooses a more specific valid destination route ahead of a broader default. Treating ‘Install default route through an SD-WAN zone’ as equivalent would not address partner traffic exits public internet despite a required private-subnet route being missing in a hub-and-spoke network with internet breakout and private IPsec overlays.

C:

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 ‘Prefer a more specific prefix’. In contrast to ‘Compare routing table and SD-WAN rule decision’, ‘Prefer a more specific prefix’ follows a different mechanism: longest-prefix match chooses a more specific valid destination route ahead of a broader default. Treating ‘Compare routing table and SD-WAN rule decision’ as equivalent would not address partner traffic exits public internet despite a required private-subnet route being missing in a hub-and-spoke network with internet breakout and private IPsec overlays.

D:

The described behavior is part of ‘Use routing diagnostics before changing SD-WAN cost’, used to avoid misdiagnosing unreachable prefixes as an economic-selection problem instead of the role of ‘Prefer a more specific prefix’. In contrast to ‘Use routing diagnostics before changing SD-WAN cost’, ‘Prefer a more specific prefix’ follows a different mechanism: longest-prefix match chooses a more specific valid destination route ahead of a broader default. Treating ‘Use routing diagnostics before changing SD-WAN cost’ as equivalent would not address partner traffic exits public internet despite a required private-subnet route being missing in a hub-and-spoke network with internet breakout and private IPsec overlays.

Question 579

For a financial services branch where forwarding decisions disagree with interface health, a technical review examines the control ‘Confirm return route for remote private access’ for the objective to repair one-way traffic where forward packets reach the data center but replies do not. Which statement best describes what it changes?

  1. SD-WAN candidate preference works only after routing makes a compatible egress path available.
  2. Longest-prefix match chooses a more specific valid destination route ahead of a broader default.
  3. Equal Cost Multi-Path allows compatible routes to coexist as candidates when distance and priority permit.
  4. Bidirectional reachability requires the remote hub or server-side router to return traffic to the client prefix.

Explanation

Correct Answer

D:

‘Confirm return route for remote private access’ is used to repair one-way traffic where forward packets reach the data center but replies do not 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 the remote forwarding table contains a route back to the branch network; the rollout must also respect this constraint: Forward-route success is insufficient for stateful end-to-end communication.

Incorrect Answers

A:

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 ‘Confirm return route for remote private access’. In contrast to ‘Compare routing table and SD-WAN rule decision’, ‘Confirm return route for remote private access’ follows a different mechanism: bidirectional reachability requires the remote hub or server-side router to return traffic to the client prefix. Treating ‘Compare routing table and SD-WAN rule decision’ as equivalent would not address SYN packets arrive at the protected application but no responses reach the branch client in a financial services branch where forwarding decisions disagree with interface health.

B:

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 ‘Confirm return route for remote private access’. In contrast to ‘Prefer a more specific prefix’, ‘Confirm return route for remote private access’ follows a different mechanism: bidirectional reachability requires the remote hub or server-side router to return traffic to the client prefix. Treating ‘Prefer a more specific prefix’ as equivalent would not address SYN packets arrive at the protected application but no responses reach the branch client in a financial services branch where forwarding decisions disagree with interface health.

C:

The described behavior is part of ‘Use ECMP-compatible route candidates’, used to make multiple eligible equal-cost paths available for subsequent SD-WAN decisions instead of the role of ‘Confirm return route for remote private access’. In contrast to ‘Use ECMP-compatible route candidates’, ‘Confirm return route for remote private access’ follows a different mechanism: bidirectional reachability requires the remote hub or server-side router to return traffic to the client prefix. Treating ‘Use ECMP-compatible route candidates’ as equivalent would not address SYN packets arrive at the protected application but no responses reach the branch client in a financial services branch where forwarding decisions disagree with interface health.

Question 580

For a FortiSASE security investigation following a blocked user action, an audit asks for evidence that the team can identify blocked malicious name resolution before the browser opens a TCP session. Which finding would answer that question?

  1. The IPS log records an appropriate attack signature and the related action.
  2. A time-matched AV event shows the detection and enforced action for the download.
  3. A filtered query event shows the domain and DNS-policy enforcement result.
  4. The authentication event shows IdP or user-session failure independent of traffic-filter logs.

Explanation

Correct Answer

C:

This checks ‘Inspect DNS-filter threat events’ at the correct operational boundary: DNS security logs record affected domain requests and configured malicious-domain actions. It demonstrates the specific capability to identify blocked malicious name resolution before the browser opens a TCP session in a FortiSASE security investigation following a blocked user action; deployment should additionally respect the constraint: DNS filtering operates at name resolution, not by scanning file payloads.

Incorrect Answers

A:

That observation belongs to ‘Inspect IPS threat logs’, not ‘Inspect DNS-filter threat 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 DNS-filter threat events’ for a FortiSASE security investigation following a blocked user action, not the evidence produced by ‘Inspect IPS threat logs’.

B:

That observation belongs to ‘Inspect antivirus detection events’, not ‘Inspect DNS-filter threat events’; its purpose is to identify which inspected download was blocked for malware and under which policy, the underlying behavior is that aV logs identify signature or file detections and the security action applied to a session. The reviewer is instead verifying ‘Inspect DNS-filter threat events’ for a FortiSASE security investigation following a blocked user action, not the evidence produced by ‘Inspect antivirus detection events’.

D:

That observation belongs to ‘Correlate cloud authentication events’, not ‘Inspect DNS-filter threat events’; its purpose is to distinguish failed identity sign-in from a denied security profile decision, the underlying behavior is that authentication events reveal the login or SSO step at which a FortiSASE user failed to establish identity. The reviewer is instead verifying ‘Inspect DNS-filter threat events’ for a FortiSASE security investigation following a blocked user action, not the evidence produced by ‘Correlate cloud authentication events’.

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