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

Question 70

For an industrial branch sending payroll traffic to a data-center application, before relying on ‘Use a BGP learned private prefix’ to obtain branch or data-center destinations without maintaining individual manual static routes, what prerequisite or operational limitation must be checked?

  1. Routing adjacency and accepted prefix policies must be healthy independently of tunnel state.
  2. Priority has meaning within the relevant route-selection context, not across unrelated prefixes.
  3. The SD-WAN rule must be reconciled with actual route installation.
  4. ECMP eligibility does not itself define an application-aware SD-WAN service strategy.

Explanation

Correct Answer

A:

This condition matters for ‘Use a BGP learned private prefix’ because BGP can advertise and learn remote private networks over supported routed overlays. Omitting the relevant safeguard can produce the tunnel stays up but dynamically announced private subnets never enter the routing table; a successful test at an industrial branch sending payroll traffic to a data-center application would instead demonstrate that BGP neighbor state and learned route entries show the remote application CIDR.

Incorrect Answers

B:

The condition is associated with ‘Review route priority’, a mechanism used to resolve preference among otherwise comparable FortiGate route candidates instead of ‘Use a BGP learned private prefix’, because route priority can provide an additional selection differentiator when distance and prefix do not distinguish alternatives. For ‘Use a BGP learned private prefix’, unlike ‘Review route priority’, the characteristic failure would be the tunnel stays up but dynamically announced private subnets never enter the routing table, which this alternative prerequisite would not directly address at an industrial branch sending payroll traffic to a data-center application.

C:

The condition is associated with ‘Verify the forwarding information base’, a mechanism used to confirm the FortiGate has installed a usable next hop for a destination instead of ‘Use a BGP learned private prefix’, because the FIB holds selected forwarding entries and is essential to actual packet delivery. For ‘Use a BGP learned private prefix’, unlike ‘Verify the forwarding information base’, the characteristic failure would be the tunnel stays up but dynamically announced private subnets never enter the routing table, which this alternative prerequisite would not directly address at an industrial branch sending payroll traffic to a data-center application.

D:

The condition is associated with ‘Use ECMP-compatible route candidates’, a mechanism used to make multiple eligible equal-cost paths available for subsequent SD-WAN decisions instead of ‘Use a BGP learned private prefix’, because equal Cost Multi-Path allows compatible routes to coexist as candidates when distance and priority permit. For ‘Use a BGP learned private prefix’, unlike ‘Use ECMP-compatible route candidates’, the characteristic failure would be the tunnel stays up but dynamically announced private subnets never enter the routing table, which this alternative prerequisite would not directly address at an industrial branch sending payroll traffic to a data-center application.

Question 71

In a change-control meeting for a coastal retail branch with two internet providers and a FortiGate running FortiOS 7.6, a colleague challenges the proposed control ‘Enable SD-WAN member selection’ for the requirement to place two independently addressed internet interfaces under centralized path selection. Which explanation accurately describes its behavior?

  1. An SD-WAN member on a DHCP WAN can inherit the gateway learned from the DHCP interface.
  2. A statically addressed SD-WAN member must use the reachable ISP next hop for proper packet forwarding.
  3. SD-WAN creates selectable member objects while retaining each interface's underlying addressing and link state.
  4. The stateful firewall policy permits internal-to-zone sessions and can apply source NAT and inspection as required.

Explanation

Correct Answer

C:

‘Enable SD-WAN member selection’ is used to place two independently addressed internet interfaces under centralized path selection in a coastal retail branch with two internet providers and a FortiGate running FortiOS 7.6; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that both carrier-facing ports appear as enabled SD-WAN members; the rollout must also respect this constraint: Check interface references and addressing before adding a physical port to SD-WAN.

Incorrect Answers

A:

The described behavior is part of ‘Use DHCP-provided WAN gateway’, used to keep a dynamically assigned ISP next hop aligned with lease changes instead of the role of ‘Enable SD-WAN member selection’. In contrast to ‘Use DHCP-provided WAN gateway’, ‘Enable SD-WAN member selection’ follows a different mechanism: SD-WAN creates selectable member objects while retaining each interface's underlying addressing and link state. Treating ‘Use DHCP-provided WAN gateway’ as equivalent would not address the WAN ports are up but neither is listed as a selectable SD-WAN member in a coastal retail branch with two internet providers and a FortiGate running FortiOS 7.6.

B:

The described behavior is part of ‘Set a static WAN member gateway’, used to reach an ISP next hop on a manually numbered uplink instead of the role of ‘Enable SD-WAN member selection’. In contrast to ‘Set a static WAN member gateway’, ‘Enable SD-WAN member selection’ follows a different mechanism: SD-WAN creates selectable member objects while retaining each interface's underlying addressing and link state. Treating ‘Set a static WAN member gateway’ as equivalent would not address the WAN ports are up but neither is listed as a selectable SD-WAN member in a coastal retail branch with two internet providers and a FortiGate running FortiOS 7.6.

D:

The described behavior is part of ‘Allow LAN-to-SD-WAN firewall policy’, used to authorize office clients to reach external destinations over eligible SD-WAN members instead of the role of ‘Enable SD-WAN member selection’. In contrast to ‘Allow LAN-to-SD-WAN firewall policy’, ‘Enable SD-WAN member selection’ follows a different mechanism: SD-WAN creates selectable member objects while retaining each interface's underlying addressing and link state. Treating ‘Allow LAN-to-SD-WAN firewall policy’ as equivalent would not address the WAN ports are up but neither is listed as a selectable SD-WAN member in a coastal retail branch with two internet providers and a FortiGate running FortiOS 7.6.

Question 72

At a coastal retail branch with two internet providers and a FortiGate running FortiOS 7.6, the change request is to place two independently addressed internet interfaces under centralized path selection. Which configuration is the most direct fit?

  1. Set a static WAN member gateway
  2. Allow LAN-to-SD-WAN firewall policy
  3. Use DHCP-provided WAN gateway
  4. Enable SD-WAN member selection
  5. Configure an SD-WAN zone
  6. Install an SD-WAN default route

Explanation

Correct Answer

D:

SD-WAN creates selectable member objects while retaining each interface's underlying addressing and link state; that scope directly serves the goal to place two independently addressed internet interfaces under centralized path selection in a coastal retail branch with two internet providers and a FortiGate running FortiOS 7.6. During implementation, check interface references and addressing before adding a physical port to SD-WAN rather than treating the configuration label as proof of working service.

Incorrect Answers

A:

A statically addressed SD-WAN member must use the reachable ISP next hop for proper packet forwarding, a mechanism intended to reach an ISP next hop on a manually numbered uplink rather than the requested ‘Enable SD-WAN member selection’ control. The stated task instead is to place two independently addressed internet interfaces under centralized path selection, and adjusting ‘Set a static WAN member gateway’ would not deliver ‘Enable SD-WAN member selection’. For the ‘Set a static WAN member gateway’ alternative to ‘Enable SD-WAN member selection’, verify the next hop is reachable on the configured interface subnet.

B:

The stateful firewall policy permits internal-to-zone sessions and can apply source NAT and inspection as required, a mechanism intended to authorize office clients to reach external destinations over eligible SD-WAN members rather than the requested ‘Enable SD-WAN member selection’ control. The stated task instead is to place two independently addressed internet interfaces under centralized path selection, and adjusting ‘Allow LAN-to-SD-WAN firewall policy’ would not deliver ‘Enable SD-WAN member selection’. For the ‘Allow LAN-to-SD-WAN firewall policy’ alternative to ‘Enable SD-WAN member selection’, path steering and firewall permission are separate decisions.

C:

An SD-WAN member on a DHCP WAN can inherit the gateway learned from the DHCP interface, a mechanism intended to keep a dynamically assigned ISP next hop aligned with lease changes rather than the requested ‘Enable SD-WAN member selection’ control. The stated task instead is to place two independently addressed internet interfaces under centralized path selection, and adjusting ‘Use DHCP-provided WAN gateway’ would not deliver ‘Enable SD-WAN member selection’. For the ‘Use DHCP-provided WAN gateway’ alternative to ‘Enable SD-WAN member selection’, a DHCP-derived gateway should not be confused with the SD-WAN zone route itself.

E:

A zone groups SD-WAN members for firewall policies, static routes, and service rules without merging the physical circuits, a mechanism intended to use a common logical outgoing interface for two alternate WAN circuits rather than the requested ‘Enable SD-WAN member selection’ control. The stated task instead is to place two independently addressed internet interfaces under centralized path selection, and adjusting ‘Configure an SD-WAN zone’ would not deliver ‘Enable SD-WAN member selection’. For the ‘Configure an SD-WAN zone’ alternative to ‘Enable SD-WAN member selection’, use the zone as the policy interface instead of individual member ports.

F:

A default static route whose outgoing interface is the SD-WAN zone supplies route reachability before path steering, a mechanism intended to provide a route for internet-bound traffic through the SD-WAN aggregate rather than the requested ‘Enable SD-WAN member selection’ control. The stated task instead is to place two independently addressed internet interfaces under centralized path selection, and adjusting ‘Install an SD-WAN default route’ would not deliver ‘Enable SD-WAN member selection’. For the ‘Install an SD-WAN default route’ alternative to ‘Enable SD-WAN member selection’, an SD-WAN rule does not itself replace the need for a valid route.

Question 73

At a retail hub where two ISP costs differ but application quality still matters, a support engineer needs to verify that ‘Use Best Quality with jitter’ is active for the goal to steer delay-sensitive conferencing toward the most stable path. Which observation is decisive?

  1. The SD-WAN rule matches the designated Internet Service Database object.
  2. The application-control internet-service list contains the learned application destination tuple.
  3. The jitter-ranked rule prefers the link reporting less packet-delay variation.
  4. The narrow rule appears ahead of the broad rule and receives matching hits.

Explanation

Correct Answer

C:

This checks ‘Use Best Quality with jitter’ at the correct operational boundary: Best Quality can evaluate jitter as the link-cost factor to compare delay variation. It demonstrates the specific capability to steer delay-sensitive conferencing toward the most stable path in a retail hub where two ISP costs differ but application quality still matters; deployment should additionally respect the constraint: Jitter and mean round-trip latency are separate measurements.

Incorrect Answers

A:

That observation belongs to ‘Match an Internet Service Database destination’, not ‘Use Best Quality with jitter’; its purpose is to identify cloud-service traffic by maintained service definitions instead of a static destination IP, the underlying behavior is that internet service matching can steer flows associated with a known internet service without manually maintaining every destination subnet. The reviewer is instead verifying ‘Use Best Quality with jitter’ for a retail hub where two ISP costs differ but application quality still matters, not the evidence produced by ‘Match an Internet Service Database destination’.

B:

That observation belongs to ‘Consider first-flow application recognition’, not ‘Use Best Quality with jitter’; 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 jitter’ for a retail hub where two ISP costs differ but application quality still matters, not the evidence produced by ‘Consider first-flow application recognition’.

D:

That observation belongs to ‘Order specific SD-WAN rules above general matches’, not ‘Use Best Quality with jitter’; 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 jitter’ for a retail hub where two ISP costs differ but application quality still matters, not the evidence produced by ‘Order specific SD-WAN rules above general matches’.

Question 74

At a branch FortiGate that terminates an ISP handoff and two IPsec tunnels, an engineer is preparing ‘Move a member between zones’ to change how one interface is referenced by routes and policies without rebuilding the WAN port. Which TWO statements identify a pertinent deployment safeguard and a direct post-change validation result? Choose TWO.

  1. Review policies and static routes referencing the source zone before moving the member.
  2. A one-member zone is still referenced as a zone, not as an individual member in firewall policies.
  3. The member now appears in the target zone and corresponding policies use it.
  4. The member inventory shows wan2 inside the internet transport zone.
  5. Ensure remaining members provide viable routes and sufficient capacity.

Explanation

Correct Answers

A:

This safeguard applies to ‘Move a member between zones’, which works because reassigning the member to a different zone changes its logical policy and rule membership. Without the correct deployment condition, operators may see that the port works but is reachable only through policies for the old zone in a branch FortiGate that terminates an ISP handoff and two IPsec tunnels.

C:

The observation follows from the operation of ‘Move a member between zones’: reassigning the member to a different zone changes its logical policy and rule membership. It directly tests the requested ability to change how one interface is referenced by routes and policies without rebuilding the WAN port in a branch FortiGate that terminates an ISP handoff and two IPsec tunnels, rather than another policy or network layer.

Incorrect Answers

B:

The planning point is associated with ‘Use an isolated single-member zone’, not ‘Move a member between zones’; its real role is to apply a dedicated policy to one exceptional transport while keeping other members grouped. The required deployment instead centers on ‘Move a member between zones’, rather than ‘Use an isolated single-member zone’; the distinct symptom to guard against is that the port works but is reachable only through policies for the old zone.

D:

This result would validate ‘Assign members to the intended zone’, not ‘Move a member between zones’, because a member's zone association determines which zone-based routes and policies can use that interface. That separate implementation serves put two ISP circuits in the internet transport zone rather than the private-overlay group, whereas the audit needs evidence specifically of ‘Move a member between zones’ at a branch FortiGate that terminates an ISP handoff and two IPsec tunnels.

E:

The planning point is associated with ‘Disable a maintenance member’, not ‘Move a member between zones’; its real role is to exclude a WAN circuit from SD-WAN decisions during scheduled carrier work. The required deployment instead centers on ‘Move a member between zones’, rather than ‘Disable a maintenance member’; the distinct symptom to guard against is that the port works but is reachable only through policies for the old zone.

Question 75

At a financial services branch where forwarding decisions disagree with interface health, a controlled test reveals that a private service rule expects an interface but only policy-based VPN selectors exist. Which setting is the strongest first lead?

  1. Investigate: Confirm return route for remote private access
  2. Investigate: Configure a static partner route through overlay zone
  3. Investigate: Use ECMP-compatible route candidates
  4. Investigate: Use a route-based IPsec overlay

Explanation

Correct Answer

D:

The symptom identifies the missing operational behavior: route-based IPsec exposes a logical tunnel interface that routing and SD-WAN can reference. For a financial services branch where forwarding decisions disagree with interface health, a direct diagnostic confirmation would be that the IPsec interface is active and represented in overlay routing and member tables; during repair, tunnel security negotiation and return routing still need separate validation.

Incorrect Answers

A:

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 ‘Use a route-based IPsec overlay’. 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 a private service rule expects an interface but only policy-based VPN selectors exist at a financial services branch where forwarding decisions disagree with interface health.

B:

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 ‘Use a route-based IPsec overlay’. 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 a private service rule expects an interface but only policy-based VPN selectors exist at a financial services branch where forwarding decisions disagree with interface health.

C:

Equal Cost Multi-Path allows compatible routes to coexist as candidates when distance and priority permit, which serves the different requirement to make multiple eligible equal-cost paths available for subsequent SD-WAN decisions instead of the behavior delivered by ‘Use a route-based IPsec overlay’. If that component were misconfigured, a more characteristic finding would be that only one ISP next hop is installed while the desired design expects equal-path eligibility; the actual report concerns a private service rule expects an interface but only policy-based VPN selectors exist at a financial services branch where forwarding decisions disagree with interface health.

Question 76

Within a managed laptop fleet governed by FortiClient endpoint profiles, the team wants to avoid an ineffective configuration of ‘Configure pre-connection posture enforcement’. Which consideration deserves attention?

  1. This workflow depends on appropriate IPsec remote-agent support and endpoint profile setup.
  2. Product detection must match the supported platform and endpoint security configuration.
  3. A process name alone is weaker than cryptographic proof of application integrity.
  4. The tag logic must accurately represent the actual security requirement.
  5. Define whether a tag means compliant or noncompliant before using it for admission.

Explanation

Correct Answer

A:

This condition matters for ‘Configure pre-connection posture enforcement’ because a configured pre-connection check can allow or deny a tunnel attempt based on an assigned posture tag. Omitting the relevant safeguard can produce a failed device is permitted to connect and only rejected later at application policy; a successful test at a managed laptop fleet governed by FortiClient endpoint profiles would instead demonstrate that FortiClient rejects the tunnel according to the configured posture-tag action.

Incorrect Answers

B:

The condition is associated with ‘Require endpoint antivirus status’, a mechanism used to treat disabled or missing antimalware protection as a noncompliant device condition instead of ‘Configure pre-connection posture enforcement’, because a posture rule can evaluate security-product presence or protection state and classify the endpoint. For ‘Configure pre-connection posture enforcement’, unlike ‘Require endpoint antivirus status’, the characteristic failure would be a failed device is permitted to connect and only rejected later at application policy, which this alternative prerequisite would not directly address at a managed laptop fleet governed by FortiClient endpoint profiles.

C:

The condition is associated with ‘Check a required running process’, a mechanism used to permit an internal app only when its approved endpoint security agent is running instead of ‘Configure pre-connection posture enforcement’, because process-presence conditions can contribute to device posture evaluation where supported. For ‘Configure pre-connection posture enforcement’, unlike ‘Check a required running process’, the characteristic failure would be a failed device is permitted to connect and only rejected later at application policy, which this alternative prerequisite would not directly address at a managed laptop fleet governed by FortiClient endpoint profiles.

D:

The condition is associated with ‘Build a security posture tag rule’, a mechanism used to label endpoints dynamically when a specified local security condition is met instead of ‘Configure pre-connection posture enforcement’, because FortiClient evaluates defined endpoint posture conditions and associates matching endpoints with security tags. For ‘Configure pre-connection posture enforcement’, unlike ‘Build a security posture tag rule’, the characteristic failure would be a failed device is permitted to connect and only rejected later at application policy, which this alternative prerequisite would not directly address at a managed laptop fleet governed by FortiClient endpoint profiles.

E:

The condition is associated with ‘Review the posture tag's allow or deny direction’, a mechanism used to avoid inverting the policy when a tag specifically denotes a noncompliant endpoint instead of ‘Configure pre-connection posture enforcement’, because an allow-when-tagged versus deny-when-tagged action determines whether the matched posture condition grants connectivity. For ‘Configure pre-connection posture enforcement’, unlike ‘Review the posture tag's allow or deny direction’, the characteristic failure would be a failed device is permitted to connect and only rejected later at application policy, which this alternative prerequisite would not directly address at a managed laptop fleet governed by FortiClient endpoint profiles.

Question 77

In a change-control meeting for a financial services branch where forwarding decisions disagree with interface health, the proposed control is ‘Use a route-based IPsec overlay’. Which deployment condition is particularly relevant?

  1. Forward-route success is insufficient for stateful end-to-end communication.
  2. A route's presence alone does not establish next-hop liveness.
  3. Tunnel security negotiation and return routing still need separate validation.
  4. The remote peer must also know a return path to the local subnet.

Explanation

Correct Answer

C:

This condition matters for ‘Use a route-based IPsec overlay’ because route-based IPsec exposes a logical tunnel interface that routing and SD-WAN can reference. Omitting the relevant safeguard can produce a private service rule expects an interface but only policy-based VPN selectors exist; a successful test at a financial services branch where forwarding decisions disagree with interface health would instead demonstrate that the IPsec interface is active and represented in overlay routing and member tables.

Incorrect Answers

A:

The condition is associated with ‘Confirm return route for remote private access’, a mechanism used to repair one-way traffic where forward packets reach the data center but replies do not instead of ‘Use a route-based IPsec overlay’, because bidirectional reachability requires the remote hub or server-side router to return traffic to the client prefix. For ‘Use a route-based IPsec overlay’, unlike ‘Confirm return route for remote private access’, the characteristic failure would be a private service rule expects an interface but only policy-based VPN selectors exist, which this alternative prerequisite would not directly address at a financial services branch where forwarding decisions disagree with interface health.

B:

The condition is associated with ‘Check the route's next hop reachability’, a mechanism used to differentiate a configured route from an actually usable gateway on a WAN link instead of ‘Use a route-based IPsec overlay’, because forwarding requires that the selected next hop can be resolved and reached via the member. For ‘Use a route-based IPsec overlay’, unlike ‘Check the route's next hop reachability’, the characteristic failure would be a private service rule expects an interface but only policy-based VPN selectors exist, which this alternative prerequisite would not directly address at a financial services branch where forwarding decisions disagree with interface health.

D:

The condition is associated with ‘Configure a static partner route through overlay zone’, a mechanism used to reach an on-premises network across an IPsec overlay SD-WAN group instead of ‘Use a route-based IPsec overlay’, because a destination-specific static route referencing the overlay zone makes private routes accessible to SD-WAN selection. For ‘Use a route-based IPsec overlay’, unlike ‘Configure a static partner route through overlay zone’, the characteristic failure would be a private service rule expects an interface but only policy-based VPN selectors exist, which this alternative prerequisite would not directly address at a financial services branch where forwarding decisions disagree with interface health.

Question 78

For a security administrator refining profiles for allowed remote-user traffic, a technical review examines the control ‘Use certificate inspection for metadata-only TLS checks’ for the objective to inspect certificate-related connection metadata without decrypting application bodies. Which statement best describes what it changes?

  1. Certificate inspection can evaluate visible TLS metadata but does not expose encrypted HTTP payload contents.
  2. DNS Filter evaluates domain lookup activity before a client establishes a normal destination session.
  3. IPS analyzes supported traffic patterns against intrusion-detection signatures and configured actions.
  4. An enabled antivirus inspection component examines supported file content for malicious signatures or behavior indicators.

Explanation

Correct Answer

A:

‘Use certificate inspection for metadata-only TLS checks’ is used to inspect certificate-related connection metadata without decrypting application bodies 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 the selected profile explicitly performs metadata checks without claiming payload inspection; the rollout must also respect this constraint: Choose deep inspection when the requirement actually depends on encrypted content visibility.

Incorrect Answers

B:

The described behavior is part of ‘Use DNS filtering’, used to stop requests to known malicious or restricted domains at the DNS layer instead of the role of ‘Use certificate inspection for metadata-only TLS checks’. In contrast to ‘Use DNS filtering’, ‘Use certificate inspection for metadata-only TLS checks’ follows a different mechanism: certificate inspection can evaluate visible TLS metadata but does not expose encrypted HTTP payload contents. Treating ‘Use DNS filtering’ as equivalent would not address an administrator expects a certificate-only mode to detect sensitive text in HTTPS uploads in a security administrator refining profiles for allowed remote-user traffic.

C:

The described behavior is part of ‘Enable intrusion prevention’, used to detect and block network exploits recognized by attack signatures or protocol decoders instead of the role of ‘Use certificate inspection for metadata-only TLS checks’. In contrast to ‘Enable intrusion prevention’, ‘Use certificate inspection for metadata-only TLS checks’ follows a different mechanism: certificate inspection can evaluate visible TLS metadata but does not expose encrypted HTTP payload contents. Treating ‘Enable intrusion prevention’ as equivalent would not address an administrator expects a certificate-only mode to detect sensitive text in HTTPS uploads in a security administrator refining profiles for allowed remote-user traffic.

D:

The described behavior is part of ‘Apply an antivirus profile to allowed traffic’, used to detect malware payloads passing through a permitted cloud access policy instead of the role of ‘Use certificate inspection for metadata-only TLS checks’. In contrast to ‘Apply an antivirus profile to allowed traffic’, ‘Use certificate inspection for metadata-only TLS checks’ follows a different mechanism: certificate inspection can evaluate visible TLS metadata but does not expose encrypted HTTP payload contents. Treating ‘Apply an antivirus profile to allowed traffic’ as equivalent would not address an administrator expects a certificate-only mode to detect sensitive text in HTTPS uploads in a security administrator refining profiles for allowed remote-user traffic.

Question 79

At a policy owner protecting HTTPS web sessions without blocking business use, an engineer is preparing ‘Distinguish SIA from SSA policy intent’ to apply general internet threat protection separately from SaaS-specific data and tenant controls. Which TWO statements identify a pertinent deployment safeguard and a direct post-change validation result? Choose TWO.

  1. The selected profile explicitly performs metadata checks without claiming payload inspection.
  2. The design enforces both baseline web protection and SaaS-specific application policy.
  3. An internet security tunnel does not by itself supply every application-specific SaaS control.
  4. API authorization and provider support differ from inline real-time access controls.
  5. The policy action must accept traffic before attached inspection profiles can process it.

Explanation

Correct Answers

B:

The observation follows from the operation of ‘Distinguish SIA from SSA policy intent’: SIA focuses on internet-bound security inspection while SSA adds cloud-application controls such as inline CASB or DLP. It directly tests the requested ability to apply general internet threat protection separately from SaaS-specific data and tenant controls in a policy owner protecting HTTPS web sessions without blocking business use, rather than another policy or network layer.

C:

This safeguard applies to ‘Distinguish SIA from SSA policy intent’, which works because SIA focuses on internet-bound security inspection while SSA adds cloud-application controls such as inline CASB or DLP. Without the correct deployment condition, operators may see that a SaaS tenant restriction is expected from generic internet path steering alone in a policy owner protecting HTTPS web sessions without blocking business use.

Incorrect Answers

A:

This result would validate ‘Use certificate inspection for metadata-only TLS checks’, not ‘Distinguish SIA from SSA policy intent’, because certificate inspection can evaluate visible TLS metadata but does not expose encrypted HTTP payload contents. That separate implementation serves inspect certificate-related connection metadata without decrypting application bodies, whereas the audit needs evidence specifically of ‘Distinguish SIA from SSA policy intent’ at a policy owner protecting HTTPS web sessions without blocking business use.

D:

The planning point is associated with ‘Use cloud API CASB for SaaS data at rest’, not ‘Distinguish SIA from SSA policy intent’; its real role is to inspect cloud-service data through supported SaaS APIs rather than only inline user sessions. The required deployment instead centers on ‘Distinguish SIA from SSA policy intent’, rather than ‘Use cloud API CASB for SaaS data at rest’; the distinct symptom to guard against is that a SaaS tenant restriction is expected from generic internet path steering alone.

E:

The planning point is associated with ‘Create a security profile group’, not ‘Distinguish SIA from SSA policy intent’; its real role is to apply a consistent set of inspection components to selected allowed SASE traffic policies. The required deployment instead centers on ‘Distinguish SIA from SSA policy intent’, rather than ‘Create a security profile group’; the distinct symptom to guard against is that a SaaS tenant restriction is expected from generic internet path steering alone.

Question 80

Within an IT team managing both BYOD browsers and corporate FortiClient installations, the administrator must authenticate a limited lab user when no central identity source has yet been connected without redesigning unrelated services. Which option addresses the goal?

  1. Maintain FortiClient tenant registration
  2. Configure agentless proxy SSO
  3. Configure SAML single sign-on
  4. Distribute proxy autoconfiguration settings
  5. Create a local FortiSASE test user

Explanation

Correct Answer

E:

Local user records and groups can be configured for a small controlled FortiSASE rollout; that scope directly serves the goal to authenticate a limited lab user when no central identity source has yet been connected in an IT team managing both BYOD browsers and corporate FortiClient installations. During implementation, local credentials are less desirable than an enterprise identity source at scale rather than treating the configuration label as proof of working service.

Incorrect Answers

A:

Registered FortiClient maintains connectivity with FortiSASE endpoint management and supplies identity or posture data, a mechanism intended to preserve endpoint identification and posture exchange for protected access rather than the requested ‘Create a local FortiSASE test user’ control. The stated task instead is to authenticate a limited lab user when no central identity source has yet been connected, and adjusting ‘Maintain FortiClient tenant registration’ would not deliver ‘Create a local FortiSASE test user’. For the ‘Maintain FortiClient tenant registration’ alternative to ‘Create a local FortiSASE test user’, ZTNA decisions may depend on fresh registration and endpoint state.

B:

SWG SSO authenticates a web proxy session using the configured identity provider, a mechanism intended to associate proxied browser traffic with enterprise user identity during secure web gateway inspection rather than the requested ‘Create a local FortiSASE test user’ control. The stated task instead is to authenticate a limited lab user when no central identity source has yet been connected, and adjusting ‘Configure agentless proxy SSO’ would not deliver ‘Create a local FortiSASE test user’. For the ‘Configure agentless proxy SSO’ alternative to ‘Create a local FortiSASE test user’, proxy SSO often depends on compatible deep inspection and IdP reachability.

C:

FortiSASE acts as a SAML service provider while the configured IdP issues assertions for authenticated users, a mechanism intended to let staff authenticate to FortiSASE through the corporate identity provider rather than the requested ‘Create a local FortiSASE test user’ control. The stated task instead is to authenticate a limited lab user when no central identity source has yet been connected, and adjusting ‘Configure SAML single sign-on’ would not deliver ‘Create a local FortiSASE test user’. For the ‘Configure SAML single sign-on’ alternative to ‘Create a local FortiSASE test user’, the client browser must reach the IdP and the SP metadata and certificates must agree.

D:

A PAC-based proxy configuration tells supported browsers which web requests should use the cloud proxy, a mechanism intended to direct selected browser destinations to the FortiSASE secure web gateway rather than the requested ‘Create a local FortiSASE test user’ control. The stated task instead is to authenticate a limited lab user when no central identity source has yet been connected, and adjusting ‘Distribute proxy autoconfiguration settings’ would not deliver ‘Create a local FortiSASE test user’. For the ‘Distribute proxy autoconfiguration settings’ alternative to ‘Create a local FortiSASE test user’, PAC logic and browser support should be tested for exceptions and split behavior.

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