Question 700
After the authorized change to create an overlay-only SD-WAN zone and place the two VPN tunnel interfaces within it, which result actually demonstrates that this site's requirement is met? Initial issue: Two VPN overlays need to share a private-access policy without also sharing the policy used for direct Internet breakout.
- A single zone policy covers sessions egressing via any eligible member assigned to that zone
- Private application traffic matches the intended overlay policy after the zone correction
- Private traffic may steer between overlays while the Internet firewall policy still targets underlays
- Sessions over either provider hit the single intended allow policy and retain appropriate inspection
Explanation
Correct Answer
C:Private traffic may steer between overlays while the Internet firewall policy still targets underlays. It demonstrates that the intended path or control is actually working, not merely configured.
Incorrect Answers
A:A single zone policy covers sessions egressing via any eligible member assigned to that zone. The outcome for that step belongs to a FortiGate using zone-based policies shows the original interface port but the administrator cannot select it as a distinct policy destination. Here the decisive requirement concerns two VPN overlays need to share a private-access policy without also sharing the policy used for direct Internet breakout, so private traffic may steer between overlays while the Internet firewall policy still targets underlays is the better fit.
B:Private application traffic matches the intended overlay policy after the zone correction. It could be appropriate when during site migration, the team assigns an overlay tunnel to the ordinary Internet zone, then discovers it is subject to public-web policy handling. However, that does not resolve the stated condition: two VPN overlays need to share a private-access policy without also sharing the policy used for direct Internet breakout. A more direct answer is private traffic may steer between overlays while the Internet firewall policy still targets underlays.
D:Sessions over either provider hit the single intended allow policy and retain appropriate inspection. It addresses a smaller site has two equivalent broadband providers requiring the same security policy and no per-carrier inspection differences. In the reported environment, the missing behavior instead relates to two VPN overlays need to share a private-access policy without also sharing the policy used for direct Internet breakout. The relevant choice is private traffic may steer between overlays while the Internet firewall policy still targets underlays.
Question 701
For a change review, the team proposes to inspect administrative event and change records for the FortiSASE tenant because: An internal audit asks whether a just-deployed SASE policy was changed by an authorized operator during a specific window. Which explanation connects the change to the underlying behavior?
- Change auditing associates security configuration actions with users and times
- A profile group provides centrally defined inspection behavior that can be selected by relevant policies
- FortiManager can centrally synchronize selected object types with FortiSASE where integration is configured
- Service routing and jurisdictional obligations are separate from basic tunnel connectivity
Explanation
Correct Answer
A:Change auditing associates security configuration actions with users and times. This is why the proposed repair addresses the reported behavior; confirm by checking: The audit record identifies the account and event corresponding to the deployed change.
Incorrect Answers
B:A profile group provides centrally defined inspection behavior that can be selected by relevant policies. The outcome for that step belongs to a remote-work tenant plans to reuse common web-filter and IPS profiles across hundreds of users, with only selected groups receiving additional controls. Here the decisive requirement concerns an internal audit asks whether a just-deployed SASE policy was changed by an authorized operator during a specific window, so change auditing associates security configuration actions with users and times is the better fit.
C:FortiManager can centrally synchronize selected object types with FortiSASE where integration is configured. That is a useful action for a different circumstance: a central network management program wants address groups and security profile groups shared between on-premise FortiGate and the FortiSASE tenant. The present case is constrained by an internal audit asks whether a just-deployed SASE policy was changed by an authorized operator during a specific window; the targeted response is change auditing associates security configuration actions with users and times.
D:Service routing and jurisdictional obligations are separate from basic tunnel connectivity. It addresses an organization plans a SASE service deployment to users in multiple countries but its security policy requires a documented processing-location decision. In the reported environment, the missing behavior instead relates to an internal audit asks whether a just-deployed SASE policy was changed by an authorized operator during a specific window. The relevant choice is change auditing associates security configuration actions with users and times.
Question 702
At a FortiSASE/SD-WAN site, this issue is reported: The SASE team expects users to authenticate through SWG SSO but the configured policy uses certificate inspection only. What is the most direct technical change to address the stated requirement?
- Check the FortiSASE RADIUS server settings and shared secret against the server-side client definition
- Use the supported agentless secure web gateway or proxy onboarding method for that browser-access requirement
- Configure the supported SWG SSO policy with required deep SSL inspection and trusted CA handling
- Sync the AD connection and verify the effective user/group-based endpoint-profile assignment
Explanation
Correct Answer
C:Configure the supported SWG SSO policy with required deep SSL inspection and trusted CA handling. FortiSASE SWG SSO requires its supported deep-inspection path; certificate-only inspection is not equivalent. The configuration alone must be followed by a functioning test: A test SWG SSO user authenticates successfully and follows the intended proxy policy.
Incorrect Answers
A:Check the FortiSASE RADIUS server settings and shared secret against the server-side client definition. It addresses rADIUS-backed authentication works for a test account on the directory server but fails for FortiSASE users after onboarding. In the reported environment, the missing behavior instead relates to the SASE team expects users to authenticate through SWG SSO but the configured policy uses certificate inspection only. The relevant choice is configure the supported SWG SSO policy with required deep SSL inspection and trusted CA handling.
B:Use the supported agentless secure web gateway or proxy onboarding method for that browser-access requirement. It could be appropriate when external contractors cannot install FortiClient, but they must use secure browser access through a managed gateway. However, that does not resolve the stated condition: the SASE team expects users to authenticate through SWG SSO but the configured policy uses certificate inspection only. A more direct answer is configure the supported SWG SSO policy with required deep SSL inspection and trusted CA handling.
D:Sync the AD connection and verify the effective user/group-based endpoint-profile assignment. The outcome for that step belongs to a company configures an Active Directory group for endpoint profiles, but a recently added user still receives the Default profile. Here the decisive requirement concerns the SASE team expects users to authenticate through SWG SSO but the configured policy uses certificate inspection only, so configure the supported SWG SSO policy with required deep SSL inspection and trusted CA handling is the better fit.
Question 703
The operator wants evidence before implementing a fix. Which specific check best distinguishes the reported failure? A new starter can sign in to FortiSASE but receives the default policy instead of the department-specific policy.
- Inspect the failing SAML response signature and configured trust certificate validity
- Inspect browser proxy configuration and the contractor's authentication state
- Inspect authentication failure records and RADIUS client/server configuration for the integration
- Inspect the authenticated principal's effective group and the policy selector that was matched
Explanation
Correct Answer
D:Inspect the authenticated principal's effective group and the policy selector that was matched. This check isolates the relevant control before the change. Identity-based policy assignment depends on group membership, not just successful authentication.
Incorrect Answers
A:Inspect the failing SAML response signature and configured trust certificate validity. It addresses a customer configures a new SAML identity provider, but the first user test fails due to an outdated signing certificate. In the reported environment, the missing behavior instead relates to a new starter can sign in to FortiSASE but receives the default policy instead of the department-specific policy. The relevant choice is inspect the authenticated principal's effective group and the policy selector that was matched.
B:Inspect browser proxy configuration and the contractor's authentication state. It could be appropriate when external contractors cannot install FortiClient, but they must use secure browser access through a managed gateway. However, that does not resolve the stated condition: a new starter can sign in to FortiSASE but receives the default policy instead of the department-specific policy. A more direct answer is inspect the authenticated principal's effective group and the policy selector that was matched.
C:Inspect authentication failure records and RADIUS client/server configuration for the integration. That is a useful action for a different circumstance: rADIUS-backed authentication works for a test account on the directory server but fails for FortiSASE users after onboarding. The present case is constrained by a new starter can sign in to FortiSASE but receives the default policy instead of the department-specific policy; the targeted response is inspect the authenticated principal's effective group and the policy selector that was matched.
Question 704
Given this incident — A VPN call is suffering because the rule's manual preference points first to a WAN whose SLA is repeatedly poor. — the administrator plans to switch to a quality-aware strategy with a matching SLA requirement for the application. Which technical principle justifies it?
- The best-quality strategy compares eligible links by the selected measured quality factor
- The minimum SLA-meeting members constraint gates rule activation independently of individual link health
- An ordinary allow policy decides permission; the steering rule determines eligible egress selection for matched traffic
- A link preference by itself does not dynamically guarantee application-level latency or loss quality
Explanation
Correct Answer
D:A link preference by itself does not dynamically guarantee application-level latency or loss quality. It directly explains the need to switch to a quality-aware strategy with a matching SLA requirement for the application. The narrow validation is: Matching calls select a qualifying WAN during controlled primary-path degradation.
Incorrect Answers
A:The best-quality strategy compares eligible links by the selected measured quality factor. That is a useful action for a different circumstance: video calls degrade on one WAN, and the administrator wants path selection based on measured jitter rather than link price. The present case is constrained by a VPN call is suffering because the rule's manual preference points first to a WAN whose SLA is repeatedly poor; the targeted response is a link preference by itself does not dynamically guarantee application-level latency or loss quality.
B:The minimum SLA-meeting members constraint gates rule activation independently of individual link health. It addresses after a data-center maintenance event, a configured rule remains disabled because its minimum number of SLA-passing members is three but only two are healthy. In the reported environment, the missing behavior instead relates to a VPN call is suffering because the rule's manual preference points first to a WAN whose SLA is repeatedly poor. The relevant choice is a link preference by itself does not dynamically guarantee application-level latency or loss quality.
C:An ordinary allow policy decides permission; the steering rule determines eligible egress selection for matched traffic. It could be appropriate when a custom policy is supposed to steer emergency traffic over a dedicated LTE link, but the operator only enabled the general default Internet policy. However, that does not resolve the stated condition: a VPN call is suffering because the rule's manual preference points first to a WAN whose SLA is repeatedly poor. A more direct answer is a link preference by itself does not dynamically guarantee application-level latency or loss quality.
Question 705
The team plans to use a matching SD-WAN rule with a manual member preference for the payroll traffic for the situation below. Which remaining implementation pitfall is directly relevant to this same requirement? A helpdesk needs payroll application traffic pinned to an approved ISP while the second WAN remains available for other services.
- Increasing probe timeout does not fix a gateway that no longer exists
- Keeping the retired address object can deny traffic even when VPN negotiation succeeds
- A generic implicit rule cannot enforce the specific payroll preference when a suitable custom rule is required
- A member preference cannot create a missing route to a remote prefix
Explanation
Correct Answer
C:A generic implicit rule cannot enforce the specific payroll preference when a suitable custom rule is required. This is an implementation boundary for the proposed fix, so the deployment needs a specific follow-up check.
Incorrect Answers
A:Increasing probe timeout does not fix a gateway that no longer exists. It addresses a branch switches to a new ISP and forgets to update the static route's gateway, causing repeated probe failures on that member. In the reported environment, the missing behavior instead relates to a helpdesk needs payroll application traffic pinned to an approved ISP while the second WAN remains available for other services. The relevant choice is a generic implicit rule cannot enforce the specific payroll preference when a suitable custom rule is required.
B:Keeping the retired address object can deny traffic even when VPN negotiation succeeds. The outcome for that step belongs to an existing site-to-site IPsec tunnel remains up but a private application is unreachable after an address change. Here the decisive requirement concerns a helpdesk needs payroll application traffic pinned to an approved ISP while the second WAN remains available for other services, so a generic implicit rule cannot enforce the specific payroll preference when a suitable custom rule is required is the better fit.
D:A member preference cannot create a missing route to a remote prefix. It could be appropriate when a FortiGate has a manual SD-WAN rule preferring WAN2, but a route lookup for the destination has no usable next hop. However, that does not resolve the stated condition: a helpdesk needs payroll application traffic pinned to an approved ISP while the second WAN remains available for other services. A more direct answer is a generic implicit rule cannot enforce the specific payroll preference when a suitable custom rule is required.
Question 706
During implementation, the administrator observes: A compliance team needs DNS domain filtering in addition to URL categorization because some unwanted domains are contacted without normal browser requests. Which intervention targets the described fault rather than an adjacent workflow?
- Attach an appropriate web-filter category policy to the matching FortiSASE security profile group
- Create or assign a narrowly targeted security profile group to the intended user-group policy
- Apply DNS-filter settings where supported to the relevant FortiSASE policy profile
- Deploy the appropriate FortiSASE inspection root certificate using a trusted endpoint-management method
Explanation
Correct Answer
C:Apply DNS-filter settings where supported to the relevant FortiSASE policy profile. DNS filtering can enforce policy based on name resolution queries, complementing web URL checks. The configuration alone must be followed by a functioning test: Blocked-domain resolution attempts follow the configured DNS policy and produce expected events.
Incorrect Answers
A:Attach an appropriate web-filter category policy to the matching FortiSASE security profile group. The outcome for that step belongs to employees visit known phishing categories, and the security lead wants to block those categories without relying on destination IP addresses alone. Here the decisive requirement concerns a compliance team needs DNS domain filtering in addition to URL categorization because some unwanted domains are contacted without normal browser requests, so apply DNS-filter settings where supported to the relevant FortiSASE policy profile is the better fit.
B:Create or assign a narrowly targeted security profile group to the intended user-group policy. It addresses a new web-filter policy blocks a category for everyone because the administrator attached the restrictive profile to a broad general rule. In the reported environment, the missing behavior instead relates to a compliance team needs DNS domain filtering in addition to URL categorization because some unwanted domains are contacted without normal browser requests. The relevant choice is apply DNS-filter settings where supported to the relevant FortiSASE policy profile.
D:Deploy the appropriate FortiSASE inspection root certificate using a trusted endpoint-management method. It could be appropriate when a browser user receives certificate warnings after FortiSASE deep inspection is activated for HTTPS sessions. However, that does not resolve the stated condition: a compliance team needs DNS domain filtering in addition to URL categorization because some unwanted domains are contacted without normal browser requests. A more direct answer is apply DNS-filter settings where supported to the relevant FortiSASE policy profile.
Question 707
Given this incident — A security officer needs proof that web-category policy violations increased after a recent configuration change. — the administrator plans to compare relevant web-filter security events across defined before-and-after reporting periods. Which technical principle justifies it?
- External forwarding supports a separate retention/compliance workflow beyond dashboards' immediate views
- On-demand generation allows a targeted investigation without waiting for the next scheduled run
- Time-window comparison can distinguish a real category-policy trend from a single cumulative count
- Grouping by both user and enforcement action helps separate policy behavior from raw request volume
Explanation
Correct Answer
C:Time-window comparison can distinguish a real category-policy trend from a single cumulative count. This is why the proposed repair addresses the reported behavior; confirm by checking: The resulting report shows comparable event trends with the change timestamp documented.
Incorrect Answers
A:External forwarding supports a separate retention/compliance workflow beyond dashboards' immediate views. It addresses a regulated organization must retain FortiSASE security logs in an approved on-premises analytics system beyond the service's ordinary retention window. In the reported environment, the missing behavior instead relates to a security officer needs proof that web-category policy violations increased after a recent configuration change. The relevant choice is time-window comparison can distinguish a real category-policy trend from a single cumulative count.
B:On-demand generation allows a targeted investigation without waiting for the next scheduled run. It could be appropriate when during an incident bridge, analysts need a fresh one-off FortiSASE report for the last two hours, not the normal weekly summary. However, that does not resolve the stated condition: a security officer needs proof that web-category policy violations increased after a recent configuration change. A more direct answer is time-window comparison can distinguish a real category-policy trend from a single cumulative count.
D:Grouping by both user and enforcement action helps separate policy behavior from raw request volume. The outcome for that step belongs to management wants to compare blocked website trends by user group and demonstrate that the change was not only a temporary increase in total web traffic. Here the decisive requirement concerns a security officer needs proof that web-category policy violations increased after a recent configuration change, so time-window comparison can distinguish a real category-policy trend from a single cumulative count is the better fit.
Question 708
For the stated scenario, what is the most important remaining blind spot after the proposed correction? Two WANs both meet the application SLA, but the accounting team requires the cheapest acceptable link for everyday SaaS access.
- A manual-only priority rule would not use the defined cost comparison in the same way
- A perfect application match still fails without valid forwarding reachability
- Creating duplicate static routes does not make a degraded link satisfy a performance objective
- Steering alone cannot resolve a mistaken destination prefix or absent BGP route
Explanation
Correct Answer
A:A manual-only priority rule would not use the defined cost comparison in the same way. This is an implementation boundary for the proposed fix, so the deployment needs a specific follow-up check.
Incorrect Answers
B:A perfect application match still fails without valid forwarding reachability. That is a useful action for a different circumstance: an engineer added an SD-WAN steering rule but expected it to override a missing default route for general Internet traffic. The present case is constrained by two WANs both meet the application SLA, but the accounting team requires the cheapest acceptable link for everyday SaaS access; the targeted response is a manual-only priority rule would not use the defined cost comparison in the same way.
C:Creating duplicate static routes does not make a degraded link satisfy a performance objective. It addresses an administrator configured two redundant WAN routes but an SD-WAN service reports one member unavailable because its required SLA is failing. In the reported environment, the missing behavior instead relates to two WANs both meet the application SLA, but the accounting team requires the cheapest acceptable link for everyday SaaS access. The relevant choice is a manual-only priority rule would not use the defined cost comparison in the same way.
D:Steering alone cannot resolve a mistaken destination prefix or absent BGP route. The outcome for that step belongs to an SD-WAN hub learns a private route over BGP but the branch still uses a competing less-specific static path for one destination. Here the decisive requirement concerns two WANs both meet the application SLA, but the accounting team requires the cheapest acceptable link for everyday SaaS access, so a manual-only priority rule would not use the defined cost comparison in the same way is the better fit.
Question 709
The operator wants evidence before implementing a fix. Which specific check best distinguishes the reported failure? The SASE team receives reports that remote users in one region have unusually long service round trips despite healthy home broadband.
- Check actual PoP assignment and network path latency from representative users in the affected area
- Inspect the tenant's active subscriptions and whether the required capability is included
- Review policy mandates against the tenant's actual allowed service regions and logging arrangements
- Inspect policy-to-profile-group binding for two user cohorts with different requirements
Explanation
Correct Answer
A:Check actual PoP assignment and network path latency from representative users in the affected area. The observed evidence guides the targeted repair: Compare FortiSASE selected PoP location and regional routing against expected tenant provisioning and client connectivity.
Incorrect Answers
B:Inspect the tenant's active subscriptions and whether the required capability is included. That is a useful action for a different circumstance: a SASE tenant is ready for configuration but the administrator cannot activate the intended service functions under the current subscription. The present case is constrained by the SASE team receives reports that remote users in one region have unusually long service round trips despite healthy home broadband; the targeted response is check actual PoP assignment and network path latency from representative users in the affected area.
C:Review policy mandates against the tenant's actual allowed service regions and logging arrangements. The outcome for that step belongs to an organization plans a SASE service deployment to users in multiple countries but its security policy requires a documented processing-location decision. Here the decisive requirement concerns the SASE team receives reports that remote users in one region have unusually long service round trips despite healthy home broadband, so check actual PoP assignment and network path latency from representative users in the affected area is the better fit.
D:Inspect policy-to-profile-group binding for two user cohorts with different requirements. It addresses a remote-work tenant plans to reuse common web-filter and IPS profiles across hundreds of users, with only selected groups receiving additional controls. In the reported environment, the missing behavior instead relates to the SASE team receives reports that remote users in one region have unusually long service round trips despite healthy home broadband. The relevant choice is check actual PoP assignment and network path latency from representative users in the affected area.
Question 710
During implementation, the administrator observes: An organization needs private TCP and UDP access to multiple office services without publishing public listener ports. Which intervention targets the described fault rather than an adjacent workflow?
- Use FortiSASE SPA with a supported FortiGate hub connection for the approved private network prefixes
- Use FortiSASE SPA PoP-to-FortiGate hub IPsec connectivity with specific private routing and access policies
- Update connector peer information and ensure the new hub endpoint is reachable
- Validate hub-specific route advertisement, preference and available SPA connectivity for both hubs
Explanation
Correct Answer
A:Use FortiSASE SPA with a supported FortiGate hub connection for the approved private network prefixes. SPA via hub overlays carries private application traffic through encrypted controlled connectivity. The configuration alone must be followed by a functioning test: Approved TCP and UDP application tests succeed through the overlay without public exposure.
Incorrect Answers
B:Use FortiSASE SPA PoP-to-FortiGate hub IPsec connectivity with specific private routing and access policies. That is a useful action for a different circumstance: a secure private access rollout uses a hub-and-spoke VPN topology and engineers expect private traffic to be accessible without exposing on-prem applications to the public Internet. The present case is constrained by an organization needs private TCP and UDP access to multiple office services without publishing public listener ports; the targeted response is use FortiSASE SPA with a supported FortiGate hub connection for the approved private network prefixes.
C:Update connector peer information and ensure the new hub endpoint is reachable. It addresses after a hub IP address changes, the FortiSASE connector still tries to establish an IPsec tunnel toward the old peer. In the reported environment, the missing behavior instead relates to an organization needs private TCP and UDP access to multiple office services without publishing public listener ports. The relevant choice is use FortiSASE SPA with a supported FortiGate hub connection for the approved private network prefixes.
D:Validate hub-specific route advertisement, preference and available SPA connectivity for both hubs. The outcome for that step belongs to an organization adds a second FortiGate hub for resilience but has not defined which private prefixes each hub advertises. Here the decisive requirement concerns an organization needs private TCP and UDP access to multiple office services without publishing public listener ports, so use FortiSASE SPA with a supported FortiGate hub connection for the approved private network prefixes is the better fit.
Fortinet NSE 5 - FortiSASE and SD-WAN 7.6 Core Administrator (NSE5_SSE_AD-7.6) Practice Tests