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

Question 690

At a finance team that uses multiple approved SaaS applications, an engineer is preparing ‘Apply remote browser isolation for risky sites’ to isolate web rendering from the endpoint when access is required to a questionable website. Which TWO statements identify a pertinent deployment safeguard and a direct post-change validation result? Choose TWO.

  1. Application behavior and HTTPS fallback must be validated for the deployed browsers.
  2. Use the narrowest necessary exception to avoid weakening protection broadly.
  3. The connected SaaS application's API scans produce inventory and findings about stored content.
  4. The site is rendered within the configured isolation workflow rather than the local browser engine.
  5. RBI mitigates browser-execution exposure; it is not a substitute for identity verification.

Explanation

Correct Answers

D:

The observation follows from the operation of ‘Apply remote browser isolation for risky sites’: remote Browser Isolation executes supported browsing in an isolated remote context and streams a safer representation. It directly tests the requested ability to isolate web rendering from the endpoint when access is required to a questionable website in a finance team that uses multiple approved SaaS applications, rather than another policy or network layer.

E:

This safeguard applies to ‘Apply remote browser isolation for risky sites’, which works because remote Browser Isolation executes supported browsing in an isolated remote context and streams a safer representation. Without the correct deployment condition, operators may see that staff must open a risky research site without directly executing its active page content locally in a finance team that uses multiple approved SaaS applications.

Incorrect Answers

A:

The planning point is associated with ‘Handle QUIC when deep inspection is required’, not ‘Apply remote browser isolation for risky sites’; its real role is to keep SaaS web traffic on an inspectable TLS-over-TCP path for inline content controls. The required deployment instead centers on ‘Apply remote browser isolation for risky sites’, rather than ‘Handle QUIC when deep inspection is required’; the distinct symptom to guard against is that staff must open a risky research site without directly executing its active page content locally.

B:

The planning point is associated with ‘Use a specific URL filter exception’, not ‘Apply remote browser isolation for risky sites’; its real role is to allow a justified business website without disabling an entire restrictive category. The required deployment instead centers on ‘Apply remote browser isolation for risky sites’, rather than ‘Use a specific URL filter exception’; the distinct symptom to guard against is that staff must open a risky research site without directly executing its active page content locally.

C:

This result would validate ‘Use cloud API CASB for SaaS data at rest’, not ‘Apply remote browser isolation for risky sites’, because aPI-connected CASB can examine supported SaaS tenant content and events without requiring every action to cross the inline proxy. That separate implementation serves inspect cloud-service data through supported SaaS APIs rather than only inline user sessions, whereas the audit needs evidence specifically of ‘Apply remote browser isolation for risky sites’ at a finance team that uses multiple approved SaaS applications.

Question 691

At a medical office prioritizing stable response times to a hosted patient system, the change board is evaluating ‘Create an active probe health check’. Which technical consideration must be built into the plan?

  1. The target must answer the selected probe method and be reachable from those paths.
  2. Low average latency alone does not demonstrate satisfactory jitter.
  3. A single probe destination cannot establish health to every application region.
  4. A current snapshot cannot reconstruct past jitter, loss, and threshold violations by itself.

Explanation

Correct Answer

A:

This condition matters for ‘Create an active probe health check’ because active SD-WAN health checks send periodic probes to a designated target over monitored members. Omitting the relevant safeguard can produce the firewall has no latency samples during idle periods despite the need for proactive measurements; a successful test at a medical office prioritizing stable response times to a hosted patient system would instead demonstrate that health-check status shows probe-derived latency and loss for each monitored member.

Incorrect Answers

B:

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 ‘Create an active probe health check’, because a jitter target compares delay variation with an allowed maximum to qualify or reject a member. For ‘Create an active probe health check’, unlike ‘Set jitter SLA threshold’, the characteristic failure would be the firewall has no latency samples during idle periods despite the need for proactive measurements, 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 ‘Compare health across multiple SLAs’, a mechanism used to measure distinct service destinations separately rather than treating the internet as one uniform path instead of ‘Create an active probe health check’, because separate health checks can reveal that a circuit reaches one remote service well but another poorly. For ‘Create an active probe health check’, unlike ‘Compare health across multiple SLAs’, the characteristic failure would be the firewall has no latency samples during idle periods despite the need for proactive measurements, 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 ‘Review SLA historical changes’, a mechanism used to establish whether a brief performance decline coincides with a reported outage instead of ‘Create an active probe health check’, because historical SLA samples and logs help distinguish transient degradation from a persistent member failure. For ‘Create an active probe health check’, unlike ‘Review SLA historical changes’, the characteristic failure would be the firewall has no latency samples during idle periods despite the need for proactive measurements, which this alternative prerequisite would not directly address at a medical office prioritizing stable response times to a hosted patient system.

Question 692

For a retail hub where two ISP costs differ but application quality still matters, before relying on ‘Match destination address in an SD-WAN rule’ to direct traffic to a particular partner subnet over an overlay while other traffic uses internet DIA, what prerequisite or operational limitation must be checked?

  1. A matching SD-WAN rule still needs a viable route to the partner prefix.
  2. A cheap member failing its SLA is not preferred solely because of its price.
  3. Application Control must be enabled in the matching firewall policy for identification-based steering.
  4. Port matching cannot reliably distinguish applications that share or change ports.

Explanation

Correct Answer

A:

This condition matters for ‘Match destination address in an SD-WAN rule’ because destination-address matching distinguishes route candidates for a specified network target. Omitting the relevant safeguard can produce partner subnet flows accidentally match the generic internet steering policy; a successful test at a retail hub where two ISP costs differ but application quality still matters would instead demonstrate that the relevant service rule includes the exact partner destination address object.

Incorrect Answers

B:

The condition is associated with ‘Use Lowest Cost with an SLA target’, a mechanism used to send a service on the cheapest circuit that still meets quality objectives instead of ‘Match destination address in an SD-WAN rule’, because Lowest Cost chooses the smallest configured member cost among those that satisfy the selected SLA. For ‘Match destination address in an SD-WAN rule’, unlike ‘Use Lowest Cost with an SLA target’, the characteristic failure would be partner subnet flows accidentally match the generic internet steering policy, which this alternative prerequisite would not directly address at a retail hub where two ISP costs differ but application quality still matters.

C:

The condition is associated with ‘Match by detected application’, a mechanism used to prefer an SD-WAN path based on application identification rather than fixed port alone instead of ‘Match destination address in an SD-WAN rule’, because application-based SD-WAN rules use application detection information to identify supported traffic signatures. For ‘Match destination address in an SD-WAN rule’, unlike ‘Match by detected application’, the characteristic failure would be partner subnet flows accidentally match the generic internet steering policy, which this alternative prerequisite would not directly address at a retail hub where two ISP costs differ but application quality still matters.

D:

The condition is associated with ‘Match service protocol and port’, a mechanism used to steer a well-defined TCP service without affecting unrelated traffic to the same server instead of ‘Match destination address in an SD-WAN rule’, because service matching narrows selection by transport protocol and destination-port criteria. For ‘Match destination address in an SD-WAN rule’, unlike ‘Match service protocol and port’, the characteristic failure would be partner subnet flows accidentally match the generic internet steering policy, which this alternative prerequisite would not directly address at a retail hub where two ISP costs differ but application quality still matters.

Question 693

At a SASE change-control review using an authorized test identity, the rollout includes the control ‘Configure a SASE allow policy’ to permit approved user traffic before applying cloud-delivered inspection profiles. Which observed mechanism is consistent with this configuration?

  1. SIA and SPA use distinct routing and policy constructs despite sharing the FortiSASE service.
  2. Geographic policy criteria can help distinguish traffic by geolocation where FortiSASE policy supports that selection.
  3. Distinct authorized administrators enable accountable management while the original account retains ownership.
  4. FortiSASE traffic policies determine which user or destination flows are accepted or denied and which security-profile groups apply.

Explanation

Correct Answer

D:

‘Configure a SASE allow policy’ is used to permit approved user traffic before applying cloud-delivered inspection profiles in a SASE change-control review using an authorized test identity; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that the matching access policy permits the intended group and references its inspection profile group; the rollout must also respect this constraint: A security profile does not independently override a deny access policy.

Incorrect Answers

A:

The described behavior is part of ‘Separate internet and private access policies’, used to apply different controls to cloud web traffic and protected data-center applications instead of the role of ‘Configure a SASE allow policy’. In contrast to ‘Separate internet and private access policies’, ‘Configure a SASE allow policy’ follows a different mechanism: FortiSASE traffic policies determine which user or destination flows are accepted or denied and which security-profile groups apply. Treating ‘Separate internet and private access policies’ as equivalent would not address the required application remains blocked even though the desired inspection profiles exist in a SASE change-control review using an authorized test identity.

B:

The described behavior is part of ‘Use geolocation-aware access restrictions’, used to restrict access from locations outside an organization-approved geographic footprint instead of the role of ‘Configure a SASE allow policy’. In contrast to ‘Use geolocation-aware access restrictions’, ‘Configure a SASE allow policy’ follows a different mechanism: FortiSASE traffic policies determine which user or destination flows are accepted or denied and which security-profile groups apply. Treating ‘Use geolocation-aware access restrictions’ as equivalent would not address the required application remains blocked even though the desired inspection profiles exist in a SASE change-control review using an authorized test identity.

C:

The described behavior is part of ‘Assign FortiSASE administrator access’, used to let a delegated operator manage the cloud configuration without sharing the primary account instead of the role of ‘Configure a SASE allow policy’. In contrast to ‘Assign FortiSASE administrator access’, ‘Configure a SASE allow policy’ follows a different mechanism: FortiSASE traffic policies determine which user or destination flows are accepted or denied and which security-profile groups apply. Treating ‘Assign FortiSASE administrator access’ as equivalent would not address the required application remains blocked even though the desired inspection profiles exist in a SASE change-control review using an authorized test identity.

Question 694

In a change-control meeting for a policy owner determining which protective control stopped a session, acceptance testing shows that a marketing site fails and the team incorrectly assumes the SASE tunnel is down. Which control should be investigated first?

  1. Investigate: Correlate cloud authentication events
  2. Investigate: Inspect web-filter category logs
  3. Investigate: Inspect IPS threat logs
  4. Investigate: Inspect antivirus detection events

Explanation

Correct Answer

B:

The symptom identifies the missing operational behavior: web-filter logs associate an HTTP or HTTPS destination with category evaluation and action. For a policy owner determining which protective control stopped a session, a direct diagnostic confirmation would be that the web-filter event shows the URL category and associated block action; during repair, category decisions must be distinguished from DNS filter results and generic firewall denies.

Incorrect Answers

A:

Authentication events reveal the login or SSO step at which a FortiSASE user failed to establish identity, which serves the different requirement to distinguish failed identity sign-in from a denied security profile decision instead of the behavior delivered by ‘Inspect web-filter category logs’. If that component were misconfigured, a more characteristic finding would be that a remote user never reaches the SASE security session because SAML login failed; the actual report concerns a marketing site fails and the team incorrectly assumes the SASE tunnel is down at a policy owner determining which protective control stopped a session.

C:

IPS events contain the signature context and configured security response for detected traffic, which serves the different requirement to verify whether an exploit signature triggered inspection rather than a generic connectivity failure instead of the behavior delivered by ‘Inspect web-filter category logs’. If that component were misconfigured, a more characteristic finding would be that a connection is reset during a suspected exploit test but there is no rule-level explanation; the actual report concerns a marketing site fails and the team incorrectly assumes the SASE tunnel is down at a policy owner determining which protective control stopped a session.

D:

AV logs identify signature or file detections and the security action applied to a session, which serves the different requirement to identify which inspected download was blocked for malware and under which policy instead of the behavior delivered by ‘Inspect web-filter category logs’. If that component were misconfigured, a more characteristic finding would be that a user reports a blocked download but only aggregate bandwidth charts were examined; the actual report concerns a marketing site fails and the team incorrectly assumes the SASE tunnel is down at a policy owner determining which protective control stopped a session.

Question 695

Within a retail campus where underlay and overlay paths require distinct treatment, the configuration has been applied. Which measurement or record best confirms the goal to put two ISP circuits in the internet transport zone rather than the private-overlay group?

  1. The correct VLAN subinterface appears as an SD-WAN member.
  2. Member status shows the maintenance circuit disabled and other members eligible.
  3. The member inventory shows wan2 inside the internet transport zone.
  4. Health-check packets use the specified reachable source on the chosen member.
  5. The physical WAN device is an enabled member with a valid gateway.

Explanation

Correct Answer

C:

This checks ‘Assign members to the intended zone’ at the correct operational boundary: a member's zone association determines which zone-based routes and policies can use that interface. It demonstrates the specific capability to put two ISP circuits in the internet transport zone rather than the private-overlay group in a retail campus where underlay and overlay paths require distinct treatment; deployment should additionally respect the constraint: Zone placement does not automatically create a firewall rule or a route.

Incorrect Answers

A:

That observation belongs to ‘Use a VLAN interface as a member’, not ‘Assign members to the intended zone’; its purpose is to steer traffic over a tagged Ethernet handoff from an ISP, the underlying behavior is that an SD-WAN member may reference a VLAN interface rather than only an untagged physical port. The reviewer is instead verifying ‘Assign members to the intended zone’ for a retail campus where underlay and overlay paths require distinct treatment, not the evidence produced by ‘Use a VLAN interface as a member’.

B:

That observation belongs to ‘Disable a maintenance member’, not ‘Assign members to the intended zone’; its purpose is to exclude a WAN circuit from SD-WAN decisions during scheduled carrier work, the underlying behavior is that disabling an SD-WAN member removes it from eligible SD-WAN selection without requiring deletion of its configuration. The reviewer is instead verifying ‘Assign members to the intended zone’ for a retail campus where underlay and overlay paths require distinct treatment, not the evidence produced by ‘Disable a maintenance member’.

D:

That observation belongs to ‘Define the member health-check source’, not ‘Assign members to the intended zone’; its purpose is to send probes using the correct reachable source address on a multiaddress uplink, the underlying behavior is that a member health-check source setting controls the source IP used by health probes to a monitored server. The reviewer is instead verifying ‘Assign members to the intended zone’ for a retail campus where underlay and overlay paths require distinct treatment, not the evidence produced by ‘Define the member health-check source’.

E:

That observation belongs to ‘Use a physical interface as a member’, not ‘Assign members to the intended zone’; its purpose is to bring a directly connected broadband circuit under SD-WAN decisions, the underlying behavior is that physical WAN ports can act as members with their own connectivity, next hops, costs, and measured health. The reviewer is instead verifying ‘Assign members to the intended zone’ for a retail campus where underlay and overlay paths require distinct treatment, not the evidence produced by ‘Use a physical interface as a member’.

Question 696

During an authorized lab exercise for a cloud protection help desk correlating identity and traffic evidence, the deployment standard specifies the control ‘Inspect IPS threat logs’ to verify whether an exploit signature triggered inspection rather than a generic connectivity failure. Which functional description matches it?

  1. Web-filter logs associate an HTTP or HTTPS destination with category evaluation and action.
  2. IPS events contain the signature context and configured security response for detected traffic.
  3. DNS security logs record affected domain requests and configured malicious-domain actions.
  4. Authentication events reveal the login or SSO step at which a FortiSASE user failed to establish identity.

Explanation

Correct Answer

B:

‘Inspect IPS threat logs’ is used to verify whether an exploit signature triggered inspection rather than a generic connectivity failure in a cloud protection help desk correlating identity and traffic evidence; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that the IPS log records an appropriate attack signature and the related action; the rollout must also respect this constraint: A reset alone is not sufficient evidence to attribute the decision to IPS.

Incorrect Answers

A:

The described behavior is part of ‘Inspect web-filter category logs’, used to determine whether a website was blocked by category policy rather than by transport failure instead of the role of ‘Inspect IPS threat logs’. In contrast to ‘Inspect web-filter category logs’, ‘Inspect IPS threat logs’ follows a different mechanism: IPS events contain the signature context and configured security response for detected traffic. Treating ‘Inspect web-filter category logs’ as equivalent would not address a connection is reset during a suspected exploit test but there is no rule-level explanation in a cloud protection help desk correlating identity and traffic evidence.

C:

The described behavior is part of ‘Inspect DNS-filter threat events’, used to identify blocked malicious name resolution before the browser opens a TCP session instead of the role of ‘Inspect IPS threat logs’. In contrast to ‘Inspect DNS-filter threat events’, ‘Inspect IPS threat logs’ follows a different mechanism: IPS events contain the signature context and configured security response for detected traffic. Treating ‘Inspect DNS-filter threat events’ as equivalent would not address a connection is reset during a suspected exploit test but there is no rule-level explanation in a cloud protection help desk correlating identity and traffic evidence.

D:

The described behavior is part of ‘Correlate cloud authentication events’, used to distinguish failed identity sign-in from a denied security profile decision instead of the role of ‘Inspect IPS threat logs’. In contrast to ‘Correlate cloud authentication events’, ‘Inspect IPS threat logs’ follows a different mechanism: IPS events contain the signature context and configured security response for detected traffic. Treating ‘Correlate cloud authentication events’ as equivalent would not address a connection is reset during a suspected exploit test but there is no rule-level explanation in a cloud protection help desk correlating identity and traffic evidence.

Question 697

At a campus running FortiOS 7.6 with application-aware policies, the rollout includes the control ‘Consider first-flow application recognition’ to explain why the first newly observed app session may not match application-based steering immediately. Which observed mechanism is consistent with this configuration?

  1. Source-address criteria restrict SD-WAN rule matching to sessions from specified client address ranges.
  2. SD-WAN rules determine egress path candidates; firewall policies separately allow or deny traffic.
  3. FortiOS learns application signatures and destination tuples from inspected sessions for subsequent application-based matches.
  4. Application-based SD-WAN rules use application detection information to identify supported traffic signatures.

Explanation

Correct Answer

C:

‘Consider first-flow application recognition’ is used to explain why the first newly observed app session may not match application-based steering immediately in a campus running FortiOS 7.6 with application-aware policies; this is its actual operating effect, rather than an unrelated feature from the other choices. A useful confirmation would find that the application-control internet-service list contains the learned application destination tuple; the rollout must also respect this constraint: Do not assume every first encrypted connection is identified before its initial path is chosen.

Incorrect Answers

A:

The described behavior is part of ‘Match a source subnet in an SD-WAN rule’, used to apply a special path selection only to traffic originating in one department network instead of the role of ‘Consider first-flow application recognition’. In contrast to ‘Match a source subnet in an SD-WAN rule’, ‘Consider first-flow application recognition’ follows a different mechanism: FortiOS learns application signatures and destination tuples from inspected sessions for subsequent application-based matches. Treating ‘Match a source subnet in an SD-WAN rule’ as equivalent would not address the first session uses a general path but later sessions to the recognized service use the preferred route in a campus running FortiOS 7.6 with application-aware policies.

B:

The described behavior is part of ‘Separate steering from security authorization’, used to choose a fast WAN without accidentally treating SD-WAN selection as firewall access permission instead of the role of ‘Consider first-flow application recognition’. In contrast to ‘Separate steering from security authorization’, ‘Consider first-flow application recognition’ follows a different mechanism: FortiOS learns application signatures and destination tuples from inspected sessions for subsequent application-based matches. Treating ‘Separate steering from security authorization’ as equivalent would not address the first session uses a general path but later sessions to the recognized service use the preferred route in a campus running FortiOS 7.6 with application-aware policies.

D:

The described behavior is part of ‘Match by detected application’, used to prefer an SD-WAN path based on application identification rather than fixed port alone instead of the role of ‘Consider first-flow application recognition’. In contrast to ‘Match by detected application’, ‘Consider first-flow application recognition’ follows a different mechanism: FortiOS learns application signatures and destination tuples from inspected sessions for subsequent application-based matches. Treating ‘Match by detected application’ as equivalent would not address the first session uses a general path but later sessions to the recognized service use the preferred route in a campus running FortiOS 7.6 with application-aware policies.

Question 698

During an authorized lab exercise for a FortiSASE deployment that protects a central application behind a FortiGate, the incident notes state that an administrator offers broad subnet access when only one protected TCP service is approved. Which change is most relevant to this symptom?

  1. Investigate: Establish BGP with the SPA hub
  2. Investigate: Select hub path using SLA health
  3. Investigate: Integrate branch SD-WAN with FortiSASE on-ramp
  4. Investigate: Use ZTNA application proxy for a protected TCP app

Explanation

Correct Answer

D:

The symptom identifies the missing operational behavior: ZTNA private access targets authorized TCP applications rather than granting generic network reachability. For a FortiSASE deployment that protects a central application behind a FortiGate, a direct diagnostic confirmation would be that the designated protected TCP service is reachable through the authorized ZTNA proxy; during repair, the FortiGate ZTNA server, access policy, and required client posture must be configured.

Incorrect Answers

A:

A supported SPA BGP design learns and advertises routes over the selected overlay connection, which serves the different requirement to exchange private network reachability dynamically between FortiSASE and a FortiGate hub instead of the behavior delivered by ‘Use ZTNA application proxy for a protected TCP app’. If that component were misconfigured, a more characteristic finding would be that the hub responds on its tunnel addresses but remote application routes never appear; the actual report concerns an administrator offers broad subnet access when only one protected TCP service is approved at a FortiSASE deployment that protects a central application behind a FortiGate.

B:

Health and service-connection priorities can influence which reachable private hub path is preferred, which serves the different requirement to prefer a viable SPA route when one private-access connection becomes degraded instead of the behavior delivered by ‘Use ZTNA application proxy for a protected TCP app’. If that component were misconfigured, a more characteristic finding would be that users continue taking a poor-quality service connection while a healthy hub exists; the actual report concerns an administrator offers broad subnet access when only one protected TCP service is approved at a FortiSASE deployment that protects a central application behind a FortiGate.

C:

A supported FortiGate branch on-ramp can steer site traffic to FortiSASE enforcement PoPs, which serves the different requirement to send on-site user internet traffic to FortiSASE cloud inspection using a supported branch edge instead of the behavior delivered by ‘Use ZTNA application proxy for a protected TCP app’. If that component were misconfigured, a more characteristic finding would be that the branch's WAN works locally but site users bypass the expected SASE inspection path; the actual report concerns an administrator offers broad subnet access when only one protected TCP service is approved at a FortiSASE deployment that protects a central application behind a FortiGate.

Question 699

In a change-control meeting for a finance team that uses multiple approved SaaS applications, a design review calls for a way to keep SaaS web traffic on an inspectable TLS-over-TCP path for inline content controls. What should the operator configure?

  1. Use cloud API CASB for SaaS data at rest
  2. Apply remote browser isolation for risky sites
  3. Apply an antivirus profile to allowed traffic
  4. Handle QUIC when deep inspection is required

Explanation

Correct Answer

D:

Blocking QUIC can force compatible browsers to fall back from HTTP/3 to TLS connections inspectable by the configured SASE controls; that scope directly serves the goal to keep SaaS web traffic on an inspectable TLS-over-TCP path for inline content controls in a finance team that uses multiple approved SaaS applications. During implementation, application behavior and HTTPS fallback must be validated for the deployed browsers rather than treating the configuration label as proof of working service.

Incorrect Answers

A:

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 ‘Handle QUIC when deep inspection is required’ control. The stated task instead is to keep SaaS web traffic on an inspectable TLS-over-TCP path for inline content controls, and adjusting ‘Use cloud API CASB for SaaS data at rest’ would not deliver ‘Handle QUIC when deep inspection is required’. For the ‘Use cloud API CASB for SaaS data at rest’ alternative to ‘Handle QUIC when deep inspection is required’, aPI authorization and provider support differ from inline real-time access controls.

B:

Remote Browser Isolation executes supported browsing in an isolated remote context and streams a safer representation, a mechanism intended to isolate web rendering from the endpoint when access is required to a questionable website rather than the requested ‘Handle QUIC when deep inspection is required’ control. The stated task instead is to keep SaaS web traffic on an inspectable TLS-over-TCP path for inline content controls, and adjusting ‘Apply remote browser isolation for risky sites’ would not deliver ‘Handle QUIC when deep inspection is required’. For the ‘Apply remote browser isolation for risky sites’ alternative to ‘Handle QUIC when deep inspection is required’, RBI mitigates browser-execution exposure; it is not a substitute for identity verification.

C:

An enabled antivirus inspection component examines supported file content for malicious signatures or behavior indicators, a mechanism intended to detect malware payloads passing through a permitted cloud access policy rather than the requested ‘Handle QUIC when deep inspection is required’ control. The stated task instead is to keep SaaS web traffic on an inspectable TLS-over-TCP path for inline content controls, and adjusting ‘Apply an antivirus profile to allowed traffic’ would not deliver ‘Handle QUIC when deep inspection is required’. For the ‘Apply an antivirus profile to allowed traffic’ alternative to ‘Handle QUIC when deep inspection is required’, encrypted payload scanning depends on appropriate TLS inspection and certificate trust.

Question 700

In a change-control meeting for a distribution office that must retain user connectivity during ISP maintenance, the proposed control is ‘Enable SD-WAN traffic logging on the egress policy’. Which deployment condition is particularly relevant?

  1. Create the correct member-to-zone mapping before using zones in rules.
  2. The NAT decision belongs in the applicable firewall policy and must match the routing design.
  3. Use the zone as the policy interface instead of individual member ports.
  4. Logging visibility should be configured on the matched firewall policy, not assumed from SD-WAN alone.

Explanation

Correct Answer

D:

This condition matters for ‘Enable SD-WAN traffic logging on the egress policy’ because logging allowed traffic records matched firewall-policy activity and supports investigation of chosen egress paths. Omitting the relevant safeguard can produce user reports cannot be correlated to traffic sessions because accepted sessions are not logged; a successful test at a distribution office that must retain user connectivity during ISP maintenance would instead demonstrate that traffic logs include session entries associated with the enabled outbound policy.

Incorrect Answers

A:

The condition is associated with ‘Separate underlay and overlay SD-WAN zones’, a mechanism used to keep ISP transports and IPsec private overlays independently selectable in policy instead of ‘Enable SD-WAN traffic logging on the egress policy’, because distinct SD-WAN zones make underlay internet circuits and overlay tunnels separate logical choices. For ‘Enable SD-WAN traffic logging on the egress policy’, unlike ‘Separate underlay and overlay SD-WAN zones’, the characteristic failure would be user reports cannot be correlated to traffic sessions because accepted sessions are not logged, which this alternative prerequisite would not directly address at a distribution office that must retain user connectivity during ISP maintenance.

B:

The condition is associated with ‘Enable interface-based source NAT’, a mechanism used to translate RFC1918 office source addresses for public internet egress instead of ‘Enable SD-WAN traffic logging on the egress policy’, because source NAT using the outgoing interface address permits private LAN hosts to communicate through each public ISP path. For ‘Enable SD-WAN traffic logging on the egress policy’, unlike ‘Enable interface-based source NAT’, the characteristic failure would be user reports cannot be correlated to traffic sessions because accepted sessions are not logged, which this alternative prerequisite would not directly address at a distribution office that must retain user connectivity during ISP maintenance.

C:

The condition is associated with ‘Configure an SD-WAN zone’, a mechanism used to use a common logical outgoing interface for two alternate WAN circuits instead of ‘Enable SD-WAN traffic logging on the egress policy’, because a zone groups SD-WAN members for firewall policies, static routes, and service rules without merging the physical circuits. For ‘Enable SD-WAN traffic logging on the egress policy’, unlike ‘Configure an SD-WAN zone’, the characteristic failure would be user reports cannot be correlated to traffic sessions because accepted sessions are not logged, which this alternative prerequisite would not directly address at a distribution office that must retain user connectivity during ISP maintenance.

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