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

Question 550

Within a retail hub where two ISP costs differ but application quality still matters, after the rollout, operators find that partner subnet flows accidentally match the generic internet steering policy. Where should they focus troubleshooting?

  1. Investigate: Use an SLA target within an SD-WAN service rule
  2. Investigate: Use an implicit SD-WAN rule as fallback
  3. Investigate: Match an Internet Service Database destination
  4. Investigate: Match destination address in an SD-WAN rule
  5. Investigate: Order specific SD-WAN rules above general matches

Explanation

Correct Answer

D:

The symptom identifies the missing operational behavior: destination-address matching distinguishes route candidates for a specified network target. For a retail hub where two ISP costs differ but application quality still matters, a direct diagnostic confirmation would be that the relevant service rule includes the exact partner destination address object; during repair, a matching SD-WAN rule still needs a viable route to the partner prefix.

Incorrect Answers

A:

Associating a service rule with an SLA target filters or prioritizes measured candidates based on the rule's strategy, which serves the different requirement to select a path only after it meets the performance objective for that particular application instead of the behavior delivered by ‘Match destination address in an SD-WAN rule’. If that component were misconfigured, a more characteristic finding would be that the service chooses a reachable circuit that violates the application delay or loss objective; the actual report concerns partner subnet flows accidentally match the generic internet steering policy at a retail hub where two ISP costs differ but application quality still matters.

B:

The implicit SD-WAN rule handles unmatched traffic using available routing and interface-priority logic, which serves the different requirement to provide default path behavior when traffic does not match any explicit steering service instead of the behavior delivered by ‘Match destination address in an SD-WAN rule’. If that component were misconfigured, a more characteristic finding would be that an administrator expects unmatched sessions to be dropped solely because no custom service matched; the actual report concerns partner subnet flows accidentally match the generic internet steering policy at a retail hub where two ISP costs differ but application quality still matters.

C:

Internet service matching can steer flows associated with a known internet service without manually maintaining every destination subnet, which serves the different requirement to identify cloud-service traffic by maintained service definitions instead of a static destination IP instead of the behavior delivered by ‘Match destination address in an SD-WAN rule’. If that component were misconfigured, a more characteristic finding would be that a SaaS provider changes IP addresses and a hardcoded address-match rule misses new endpoints; the actual report concerns partner subnet flows accidentally match the generic internet steering policy at a retail hub where two ISP costs differ but application quality still matters.

E:

SD-WAN service rules are evaluated in configured order, so earlier matching entries can take precedence, which serves the different requirement to ensure a narrow high-priority policy wins instead of a catch-all service rule instead of the behavior delivered by ‘Match destination address in an SD-WAN rule’. If that component were misconfigured, a more characteristic finding would be that a broad any-destination rule captures sessions meant for the later finance-specific rule; the actual report concerns partner subnet flows accidentally match the generic internet steering policy at a retail hub where two ISP costs differ but application quality still matters.

Question 551

For a branch experiencing intermittent packet loss during video meetings, before relying on ‘Set packet-loss SLA threshold’ to protect application sessions from a link that intermittently drops packets, what prerequisite or operational limitation must be checked?

  1. Healthy alternate routing must exist for traffic to continue.
  2. Check loss independently of latency and jitter instead of inferring it from link-up state.
  3. Low average latency alone does not demonstrate satisfactory jitter.
  4. The measurement endpoint must be reliably reachable and appropriate to the application.

Explanation

Correct Answer

B:

This condition matters for ‘Set packet-loss SLA threshold’ because a loss target evaluates the fraction of missing probes or measured packets before declaring SLA compliance. Omitting the relevant safeguard can produce voice quality degrades on a path with normal latency but elevated loss; a successful test at a branch experiencing intermittent packet loss during video meetings would instead demonstrate that health-check results show loss exceeding the configured acceptable percentage.

Incorrect Answers

A:

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 ‘Set packet-loss SLA threshold’, because failed health checks can withdraw the broken member's routes from the SD-WAN eligible path group. For ‘Set packet-loss SLA threshold’, unlike ‘Use probe loss to trigger failover’, the characteristic failure would be voice quality degrades on a path with normal latency but elevated loss, which this alternative prerequisite would not directly address at a branch experiencing intermittent packet loss during video meetings.

C:

The condition is associated with ‘Set jitter SLA threshold’, a mechanism used to avoid a circuit whose packet-delay variation damages live audio instead of ‘Set packet-loss SLA threshold’, because a jitter target compares delay variation with an allowed maximum to qualify or reject a member. For ‘Set packet-loss SLA threshold’, unlike ‘Set jitter SLA threshold’, the characteristic failure would be voice quality degrades on a path with normal latency but elevated loss, which this alternative prerequisite would not directly address at a branch experiencing intermittent packet loss during video meetings.

D:

The condition is associated with ‘Select the correct probe server’, a mechanism used to measure user-relevant path health rather than only the nearest ISP hop instead of ‘Set packet-loss SLA threshold’, because health checks against a representative reachable target include more of the application path than checks aimed only at the immediate gateway. For ‘Set packet-loss SLA threshold’, unlike ‘Select the correct probe server’, the characteristic failure would be voice quality degrades on a path with normal latency but elevated loss, which this alternative prerequisite would not directly address at a branch experiencing intermittent packet loss during video meetings.

Question 552

During an authorized lab exercise for a global remote-user rollout with separate employee and contractor policies, a pilot is about to enable ‘Distribute proxy autoconfiguration settings’. Which precaution is most closely tied to this choice?

  1. The enterprise deployment tool must match endpoint operating systems and device ownership.
  2. Agentless proxy steering does not automatically tunnel all nonweb IP traffic.
  3. Profile assignment must be checked separately from cloud traffic-policy ordering.
  4. PAC logic and browser support should be tested for exceptions and split behavior.

Explanation

Correct Answer

D:

This condition matters for ‘Distribute proxy autoconfiguration settings’ because a PAC-based proxy configuration tells supported browsers which web requests should use the cloud proxy. Omitting the relevant safeguard can produce a remote browser connects directly to internet sites instead of the required SWG; a successful test at a global remote-user rollout with separate employee and contractor policies would instead demonstrate that browser proxy resolution selects the FortiSASE proxy for the intended URLs.

Incorrect Answers

A:

The condition is associated with ‘Deploy FortiClient using enterprise management’, a mechanism used to roll out FortiClient at scale without requiring hundreds of manual installer sessions instead of ‘Distribute proxy autoconfiguration settings’, because group policy or mobile device management can deploy prepared FortiClient packages to managed endpoints. For ‘Distribute proxy autoconfiguration settings’, unlike ‘Deploy FortiClient using enterprise management’, the characteristic failure would be a remote browser connects directly to internet sites instead of the required SWG, which this alternative prerequisite would not directly address at a global remote-user rollout with separate employee and contractor policies.

B:

The condition is associated with ‘Enroll an agentless web user’, a mechanism used to protect an unmanaged Chromebook's HTTP and HTTPS browsing without installing FortiClient instead of ‘Distribute proxy autoconfiguration settings’, because agentless secure web gateway access uses explicit proxy steering rather than a full-device agent tunnel. For ‘Distribute proxy autoconfiguration settings’, unlike ‘Enroll an agentless web user’, the characteristic failure would be a remote browser connects directly to internet sites instead of the required SWG, which this alternative prerequisite would not directly address at a global remote-user rollout with separate employee and contractor policies.

C:

The condition is associated with ‘Match endpoint profiles to the correct user group’, a mechanism used to deliver one set of endpoint controls to contractors and a stricter set to employees instead of ‘Distribute proxy autoconfiguration settings’, because endpoint profiles can be assigned according to relevant groups or administrative selection. For ‘Distribute proxy autoconfiguration settings’, unlike ‘Match endpoint profiles to the correct user group’, the characteristic failure would be a remote browser connects directly to internet sites instead of the required SWG, which this alternative prerequisite would not directly address at a global remote-user rollout with separate employee and contractor policies.

Question 553

Within a security administrator refining profiles for allowed remote-user traffic, the administrator must detect and block network exploits recognized by attack signatures or protocol decoders without redesigning unrelated services. Which option addresses the goal?

  1. Enable SSL deep inspection
  2. Use cloud API CASB for SaaS data at rest
  3. Use certificate inspection for metadata-only TLS checks
  4. Configure file filtering
  5. Enable intrusion prevention

Explanation

Correct Answer

E:

IPS analyzes supported traffic patterns against intrusion-detection signatures and configured actions; that scope directly serves the goal to detect and block network exploits recognized by attack signatures or protocol decoders in a security administrator refining profiles for allowed remote-user traffic. During implementation, IPS coverage depends on the traffic inspection path and enabled profile settings rather than treating the configuration label as proof of working service.

Incorrect Answers

A:

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 ‘Enable intrusion prevention’ control. The stated task instead is to detect and block network exploits recognized by attack signatures or protocol decoders, and adjusting ‘Enable SSL deep inspection’ would not deliver ‘Enable intrusion prevention’. For the ‘Enable SSL deep inspection’ alternative to ‘Enable intrusion prevention’, certificate deployment and inspection exemptions must be handled to avoid breaking legitimate services.

B:

API-connected CASB can examine supported SaaS tenant content and events without requiring every action to cross the inline proxy, a mechanism intended to inspect cloud-service data through supported SaaS APIs rather than only inline user sessions rather than the requested ‘Enable intrusion prevention’ control. The stated task instead is to detect and block network exploits recognized by attack signatures or protocol decoders, and adjusting ‘Use cloud API CASB for SaaS data at rest’ would not deliver ‘Enable intrusion prevention’. For the ‘Use cloud API CASB for SaaS data at rest’ alternative to ‘Enable intrusion prevention’, aPI authorization and provider support differ from inline real-time access controls.

C:

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 ‘Enable intrusion prevention’ control. The stated task instead is to detect and block network exploits recognized by attack signatures or protocol decoders, and adjusting ‘Use certificate inspection for metadata-only TLS checks’ would not deliver ‘Enable intrusion prevention’. For the ‘Use certificate inspection for metadata-only TLS checks’ alternative to ‘Enable intrusion prevention’, choose deep inspection when the requirement actually depends on encrypted content visibility.

D:

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 ‘Enable intrusion prevention’ control. The stated task instead is to detect and block network exploits recognized by attack signatures or protocol decoders, and adjusting ‘Configure file filtering’ would not deliver ‘Enable intrusion prevention’. For the ‘Configure file filtering’ alternative to ‘Enable intrusion prevention’, encrypted transfers need suitable deep inspection for content-aware file filtering.

Question 554

For a regional hub where live transport measurements do not agree with the user complaint, a maintenance plan requires the firewall team to exclude paths whose round-trip delay exceeds a real-time application's bound. Which choice is appropriate?

  1. Select the correct probe server
  2. Set latency SLA threshold
  3. Review SLA historical changes
  4. Set jitter SLA threshold

Explanation

Correct Answer

B:

A latency target makes a member fail that SLA when measured delay exceeds the configured limit; that scope directly serves the goal to exclude paths whose round-trip delay exceeds a real-time application's bound in a regional hub where live transport measurements do not agree with the user complaint. During implementation, thresholds must be realistic for the probe destination and business application rather than treating the configuration label as proof of working service.

Incorrect Answers

A:

Health checks against a representative reachable target include more of the application path than checks aimed only at the immediate gateway, a mechanism intended to measure user-relevant path health rather than only the nearest ISP hop rather than the requested ‘Set latency SLA threshold’ control. The stated task instead is to exclude paths whose round-trip delay exceeds a real-time application's bound, and adjusting ‘Select the correct probe server’ would not deliver ‘Set latency SLA threshold’. For the ‘Select the correct probe server’ alternative to ‘Set latency SLA threshold’, the measurement endpoint must be reliably reachable and appropriate to the application.

C:

Historical SLA samples and logs help distinguish transient degradation from a persistent member failure, a mechanism intended to establish whether a brief performance decline coincides with a reported outage rather than the requested ‘Set latency SLA threshold’ control. The stated task instead is to exclude paths whose round-trip delay exceeds a real-time application's bound, and adjusting ‘Review SLA historical changes’ would not deliver ‘Set latency SLA threshold’. For the ‘Review SLA historical changes’ alternative to ‘Set latency SLA threshold’, a current snapshot cannot reconstruct past jitter, loss, and threshold violations by itself.

D:

A jitter target compares delay variation with an allowed maximum to qualify or reject a member, a mechanism intended to avoid a circuit whose packet-delay variation damages live audio rather than the requested ‘Set latency SLA threshold’ control. The stated task instead is to exclude paths whose round-trip delay exceeds a real-time application's bound, and adjusting ‘Set jitter SLA threshold’ would not deliver ‘Set latency SLA threshold’. For the ‘Set jitter SLA threshold’ alternative to ‘Set latency SLA threshold’, low average latency alone does not demonstrate satisfactory jitter.

Question 555

Within an operations hub with differentiated perimeter policies for WAN members, the administrator must send probes using the correct reachable source address on a multiaddress uplink without redesigning unrelated services. Which option addresses the goal?

  1. Use an IPsec interface as a member
  2. Move a member between zones
  3. Define the member health-check source
  4. Assign members to the intended zone
  5. Set member cost

Explanation

Correct Answer

C:

A member health-check source setting controls the source IP used by health probes to a monitored server; that scope directly serves the goal to send probes using the correct reachable source address on a multiaddress uplink in an operations hub with differentiated perimeter policies for WAN members. During implementation, the source must be routable toward the monitor target and accepted by its response path rather than treating the configuration label as proof of working service.

Incorrect Answers

A:

Route-based IPsec tunnel interfaces can be members whose quality is measured and selected for overlay routing, a mechanism intended to apply SD-WAN selection to redundant encrypted site-to-site paths rather than the requested ‘Define the member health-check source’ control. The stated task instead is to send probes using the correct reachable source address on a multiaddress uplink, and adjusting ‘Use an IPsec interface as a member’ would not deliver ‘Define the member health-check source’. For the ‘Use an IPsec interface as a member’ alternative to ‘Define the member health-check source’, bring up the route-based tunnel and verify selectors and reachability independently.

B:

Reassigning the member to a different zone changes its logical policy and rule membership, a mechanism intended to change how one interface is referenced by routes and policies without rebuilding the WAN port rather than the requested ‘Define the member health-check source’ control. The stated task instead is to send probes using the correct reachable source address on a multiaddress uplink, and adjusting ‘Move a member between zones’ would not deliver ‘Define the member health-check source’. For the ‘Move a member between zones’ alternative to ‘Define the member health-check source’, review policies and static routes referencing the source zone before moving the member.

D:

A member's zone association determines which zone-based routes and policies can use that interface, a mechanism intended to put two ISP circuits in the internet transport zone rather than the private-overlay group rather than the requested ‘Define the member health-check source’ control. The stated task instead is to send probes using the correct reachable source address on a multiaddress uplink, and adjusting ‘Assign members to the intended zone’ would not deliver ‘Define the member health-check source’. For the ‘Assign members to the intended zone’ alternative to ‘Define the member health-check source’, zone placement does not automatically create a firewall rule or a route.

E:

The cost field ranks SLA-qualified members for the Lowest Cost strategy, with smaller values preferred, a mechanism intended to favor a lower-priced uplink only when eligible under lowest-cost SLA rules rather than the requested ‘Define the member health-check source’ control. The stated task instead is to send probes using the correct reachable source address on a multiaddress uplink, and adjusting ‘Set member cost’ would not deliver ‘Define the member health-check source’. For the ‘Set member cost’ alternative to ‘Define the member health-check source’, cost does not replace health measurements or firewall policy matching.

Question 556

For a distribution office that must retain user connectivity during ISP maintenance, a technical review examines the control ‘Enable SD-WAN traffic logging on the egress policy’ for the objective to retain session evidence when validating a new dual-WAN deployment. Which statement best describes what it changes?

  1. SD-WAN creates selectable member objects while retaining each interface's underlying addressing and link state.
  2. A zone groups SD-WAN members for firewall policies, static routes, and service rules without merging the physical circuits.
  3. Logging allowed traffic records matched firewall-policy activity and supports investigation of chosen egress paths.
  4. Distinct SD-WAN zones make underlay internet circuits and overlay tunnels separate logical choices.

Explanation

Correct Answer

C:

‘Enable SD-WAN traffic logging on the egress policy’ is used to retain session evidence when validating a new dual-WAN deployment in a distribution office that must retain user connectivity during ISP maintenance; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that traffic logs include session entries associated with the enabled outbound policy; the rollout must also respect this constraint: Logging visibility should be configured on the matched firewall policy, not assumed from SD-WAN alone.

Incorrect Answers

A:

The described behavior is part of ‘Enable SD-WAN member selection’, used to place two independently addressed internet interfaces under centralized path selection instead of the role of ‘Enable SD-WAN traffic logging on the egress policy’. In contrast to ‘Enable SD-WAN member selection’, ‘Enable SD-WAN traffic logging on the egress policy’ follows a different mechanism: logging allowed traffic records matched firewall-policy activity and supports investigation of chosen egress paths. Treating ‘Enable SD-WAN member selection’ as equivalent would not address user reports cannot be correlated to traffic sessions because accepted sessions are not logged in a distribution office that must retain user connectivity during ISP maintenance.

B:

The described behavior is part of ‘Configure an SD-WAN zone’, used to use a common logical outgoing interface for two alternate WAN circuits instead of the role of ‘Enable SD-WAN traffic logging on the egress policy’. In contrast to ‘Configure an SD-WAN zone’, ‘Enable SD-WAN traffic logging on the egress policy’ follows a different mechanism: logging allowed traffic records matched firewall-policy activity and supports investigation of chosen egress paths. Treating ‘Configure an SD-WAN zone’ as equivalent would not address user reports cannot be correlated to traffic sessions because accepted sessions are not logged in a distribution office that must retain user connectivity during ISP maintenance.

D:

The described behavior is part of ‘Separate underlay and overlay SD-WAN zones’, used to keep ISP transports and IPsec private overlays independently selectable in policy instead of the role of ‘Enable SD-WAN traffic logging on the egress policy’. In contrast to ‘Separate underlay and overlay SD-WAN zones’, ‘Enable SD-WAN traffic logging on the egress policy’ follows a different mechanism: logging allowed traffic records matched firewall-policy activity and supports investigation of chosen egress paths. Treating ‘Separate underlay and overlay SD-WAN zones’ as equivalent would not address user reports cannot be correlated to traffic sessions because accepted sessions are not logged in a distribution office that must retain user connectivity during ISP maintenance.

Question 557

In a change-control meeting for a company enrolling remote Windows and macOS employees into FortiSASE, a colleague challenges the proposed control ‘Use preconfigured FortiClient installers’ for the requirement to enroll a small pilot group with minimal manual agent configuration. Which explanation accurately describes its behavior?

  1. Agentless secure web gateway access uses explicit proxy steering rather than a full-device agent tunnel.
  2. Registered FortiClient maintains connectivity with FortiSASE endpoint management and supplies identity or posture data.
  3. FortiSASE acts as a SAML service provider while the configured IdP issues assertions for authenticated users.
  4. The FortiSASE onboarding flow can provide prepared FortiClient installers that users install on their devices.

Explanation

Correct Answer

D:

‘Use preconfigured FortiClient installers’ is used to enroll a small pilot group with minimal manual agent configuration in a company enrolling remote Windows and macOS employees into FortiSASE; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that the installed agent registers to the correct FortiSASE tenant using its onboarding configuration; the rollout must also respect this constraint: The device must be supported and permitted to run FortiClient.

Incorrect Answers

A:

The described behavior is part of ‘Enroll an agentless web user’, used to protect an unmanaged Chromebook's HTTP and HTTPS browsing without installing FortiClient instead of the role of ‘Use preconfigured FortiClient installers’. In contrast to ‘Enroll an agentless web user’, ‘Use preconfigured FortiClient installers’ follows a different mechanism: the FortiSASE onboarding flow can provide prepared FortiClient installers that users install on their devices. Treating ‘Enroll an agentless web user’ as equivalent would not address pilot users install a generic client but lack the intended cloud service configuration in a company enrolling remote Windows and macOS employees into FortiSASE.

B:

The described behavior is part of ‘Maintain FortiClient tenant registration’, used to preserve endpoint identification and posture exchange for protected access instead of the role of ‘Use preconfigured FortiClient installers’. In contrast to ‘Maintain FortiClient tenant registration’, ‘Use preconfigured FortiClient installers’ follows a different mechanism: the FortiSASE onboarding flow can provide prepared FortiClient installers that users install on their devices. Treating ‘Maintain FortiClient tenant registration’ as equivalent would not address pilot users install a generic client but lack the intended cloud service configuration in a company enrolling remote Windows and macOS employees into FortiSASE.

C:

The described behavior is part of ‘Configure SAML single sign-on’, used to let staff authenticate to FortiSASE through the corporate identity provider instead of the role of ‘Use preconfigured FortiClient installers’. In contrast to ‘Configure SAML single sign-on’, ‘Use preconfigured FortiClient installers’ follows a different mechanism: the FortiSASE onboarding flow can provide prepared FortiClient installers that users install on their devices. Treating ‘Configure SAML single sign-on’ as equivalent would not address pilot users install a generic client but lack the intended cloud service configuration in a company enrolling remote Windows and macOS employees into FortiSASE.

Question 558

In a change-control meeting for a private-access rollout spanning two data-center hubs, the team is closing the change after testing a design to permit cloud-originated SPA traffic through the data-center firewall policy. Which result supports closure?

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

Explanation

Correct Answer

C:

This checks ‘Allow security PoP access to private applications’ at the correct operational boundary: hub-side FortiGate policies authorize FortiSASE service traffic toward the protected servers. It demonstrates the specific capability to permit cloud-originated SPA traffic through the data-center firewall policy in a private-access rollout spanning two data-center hubs; deployment should additionally respect the constraint: Routing reachability and firewall permission must both be satisfied.

Incorrect Answers

A:

That observation belongs to ‘Verify site-based SASE traffic steering’, not ‘Allow security PoP access to private applications’; its purpose is to differentiate local branch DIA from traffic genuinely sent to cloud enforcement, the underlying behavior is that site-based on-ramp configuration determines which branch flows are forwarded into FortiSASE. The reviewer is instead verifying ‘Allow security PoP access to private applications’ for a private-access rollout spanning two data-center hubs, not the evidence produced by ‘Verify site-based SASE traffic steering’.

B:

That observation belongs to ‘Configure DNS resolution for private names’, not ‘Allow security PoP access to private applications’; 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 ‘Allow security PoP access to private applications’ for a private-access rollout spanning two data-center hubs, not the evidence produced by ‘Configure DNS resolution for private names’.

D:

That observation belongs to ‘Advertise internal prefixes to SPA routing’, not ‘Allow security PoP access to private applications’; 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 ‘Allow security PoP access to private applications’ for a private-access rollout spanning two data-center hubs, not the evidence produced by ‘Advertise internal prefixes to SPA routing’.

Question 559

Within a dispersed workforce that uses a corporate SAML identity provider, after the rollout, operators find that employees have the agent installed but cannot associate it with the enterprise tenant. Where should they focus troubleshooting?

  1. Investigate: Configure SAML single sign-on
  2. Investigate: Distribute a FortiSASE invitation code
  3. Investigate: Maintain FortiClient tenant registration
  4. Investigate: Configure RADIUS authentication
  5. Investigate: Configure agentless proxy SSO

Explanation

Correct Answer

B:

The symptom identifies the missing operational behavior: the Onboard Users workflow provides information that remote users use for FortiSASE client registration. For a dispersed workforce that uses a corporate SAML identity provider, a direct diagnostic confirmation would be that the endpoint registers to the intended FortiSASE environment after using the invitation; during repair, onboarding credentials should be shared only with the intended users.

Incorrect Answers

A:

FortiSASE acts as a SAML service provider while the configured IdP issues assertions for authenticated users, which serves the different requirement to let staff authenticate to FortiSASE through the corporate identity provider instead of the behavior delivered by ‘Distribute a FortiSASE invitation code’. If that component were misconfigured, a more characteristic finding would be that redirect-based identity login cannot complete because the SP and IdP trust are not aligned; the actual report concerns employees have the agent installed but cannot associate it with the enterprise tenant at a dispersed workforce that uses a corporate SAML identity provider.

C:

Registered FortiClient maintains connectivity with FortiSASE endpoint management and supplies identity or posture data, which serves the different requirement to preserve endpoint identification and posture exchange for protected access instead of the behavior delivered by ‘Distribute a FortiSASE invitation code’. If that component were misconfigured, a more characteristic finding would be that a previously trusted endpoint no longer supplies the expected posture information after disconnecting; the actual report concerns employees have the agent installed but cannot associate it with the enterprise tenant 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 ‘Distribute a FortiSASE invitation code’. 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 employees have the agent installed but cannot associate it with the enterprise tenant at a dispersed workforce that uses a corporate SAML identity provider.

E:

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 ‘Distribute a FortiSASE invitation code’. 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 employees have the agent installed but cannot associate it with the enterprise tenant at a dispersed workforce that uses a corporate SAML identity provider.

Question 560

In a change-control meeting for a video collaboration office using two simultaneously healthy circuits, the team is closing the change after testing a design to prefer the circuit losing fewer packets for interactive services. Which result supports closure?

  1. Separate old and new session entries reveal their actual selected interfaces.
  2. The narrow rule appears ahead of the broad rule and receives matching hits.
  3. The rule's loss criterion ranks the measured low-loss member first.
  4. The application-control internet-service list contains the learned application destination tuple.

Explanation

Correct Answer

C:

This checks ‘Use Best Quality with packet loss’ at the correct operational boundary: Best Quality supports loss-oriented link comparison using measured health data. It demonstrates the specific capability to prefer the circuit losing fewer packets for interactive services in a video collaboration office using two simultaneously healthy circuits; deployment should additionally respect the constraint: A low loss figure does not necessarily imply better latency or lower cost.

Incorrect Answers

A:

That observation belongs to ‘Treat existing sessions differently from new flows’, not ‘Use Best Quality with packet loss’; its purpose is to troubleshoot a session that remains associated with an earlier selection after an SD-WAN change, the underlying behavior is that session state and configured failover behavior affect when path changes apply; newly created flows are evaluated against current steering. The reviewer is instead verifying ‘Use Best Quality with packet loss’ for a video collaboration office using two simultaneously healthy circuits, not the evidence produced by ‘Treat existing sessions differently from new flows’.

B:

That observation belongs to ‘Order specific SD-WAN rules above general matches’, not ‘Use Best Quality with packet loss’; its purpose is to ensure a narrow high-priority policy wins instead of a catch-all service rule, the underlying behavior is that SD-WAN service rules are evaluated in configured order, so earlier matching entries can take precedence. The reviewer is instead verifying ‘Use Best Quality with packet loss’ for a video collaboration office using two simultaneously healthy circuits, not the evidence produced by ‘Order specific SD-WAN rules above general matches’.

D:

That observation belongs to ‘Consider first-flow application recognition’, not ‘Use Best Quality with packet loss’; its purpose is to explain why the first newly observed app session may not match application-based steering immediately, the underlying behavior is that FortiOS learns application signatures and destination tuples from inspected sessions for subsequent application-based matches. The reviewer is instead verifying ‘Use Best Quality with packet loss’ for a video collaboration office using two simultaneously healthy circuits, not the evidence produced by ‘Consider first-flow application recognition’.

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