Question 230
For this Fortinet incident, which observation should the engineer collect first to validate the suspected condition? An administrator plans to give video conferencing first priority over bulk patch downloads on a two-link branch.
- Inspect probe results and confirm whether the rule actually references their SLA target
- Examine an identified conference flow and verify which SD-WAN rule it matches
- Inspect whether the VPN tunnel is established and whether routes to private prefixes use the overlay zone
- Check the backup member's acquired address, gateway reachability and route state
Explanation
Correct Answer
B:Examine an identified conference flow and verify which SD-WAN rule it matches. This check isolates the relevant control before the change. SD-WAN uses ordered match criteria and steering strategy to differentiate application traffic classes.
Incorrect Answers
A:Inspect probe results and confirm whether the rule actually references their SLA target. It could be appropriate when a support engineer sees packet loss on one uplink but all interface LEDs are green and traffic continues to pick the poor circuit. However, that does not resolve the stated condition: an administrator plans to give video conferencing first priority over bulk patch downloads on a two-link branch. A more direct answer is examine an identified conference flow and verify which SD-WAN rule it matches.
C:Inspect whether the VPN tunnel is established and whether routes to private prefixes use the overlay zone. That is a useful action for a different circumstance: a bank requires private site-to-site application access through its FortiGate SD-WAN hub, while local Internet traffic should exit each branch directly. The present case is constrained by an administrator plans to give video conferencing first priority over bulk patch downloads on a two-link branch; the targeted response is examine an identified conference flow and verify which SD-WAN rule it matches.
D:Check the backup member's acquired address, gateway reachability and route state. The outcome for that step belongs to during branch turn-up, the backup ISP port shows link-up but has no assigned IP or gateway from its provider. Here the decisive requirement concerns an administrator plans to give video conferencing first priority over bulk patch downloads on a two-link branch, so examine an identified conference flow and verify which SD-WAN rule it matches is the better fit.
Question 231
Before changing the configuration, the team needs to isolate the problem. Which diagnostic check is most targeted here? Incident: A company tests new FortiSASE SPA integration, but remote users can reach only the hub firewall, not the server subnet behind it.
- Inspect the route and traffic classification for one public SaaS destination and one private server
- Inspect the private server subnet in BGP tables and test the hub's own reachability to that subnet
- Inspect the connector's configured peer and IKE negotiation destination during connection attempts
- Inspect which private destination prefixes and application protocols are permitted through the connector
Explanation
Correct Answer
B:Inspect the private server subnet in BGP tables and test the hub's own reachability to that subnet. This check isolates the relevant control before the change. PoP-to-hub transport can work while destinations behind the hub are still unadvertised or unpermitted.
Incorrect Answers
A:Inspect the route and traffic classification for one public SaaS destination and one private server. That is a useful action for a different circumstance: fortiSASE remote clients reach SASE points of presence, yet office users need direct access to the Internet without unnecessarily hairpinning via a corporate hub. The present case is constrained by a company tests new FortiSASE SPA integration, but remote users can reach only the hub firewall, not the server subnet behind it; the targeted response is inspect the private server subnet in BGP tables and test the hub's own reachability to that subnet.
C:Inspect the connector's configured peer and IKE negotiation destination during connection attempts. The outcome for that step belongs to after a hub IP address changes, the FortiSASE connector still tries to establish an IPsec tunnel toward the old peer. Here the decisive requirement concerns a company tests new FortiSASE SPA integration, but remote users can reach only the hub firewall, not the server subnet behind it, so inspect the private server subnet in BGP tables and test the hub's own reachability to that subnet is the better fit.
D:Inspect which private destination prefixes and application protocols are permitted through the connector. It could be appropriate when an organization needs private TCP and UDP access to multiple office services without publishing public listener ports. However, that does not resolve the stated condition: a company tests new FortiSASE SPA integration, but remote users can reach only the hub firewall, not the server subnet behind it. A more direct answer is inspect the private server subnet in BGP tables and test the hub's own reachability to that subnet.
Question 232
At a FortiSASE/SD-WAN site, this issue is reported: A service provider reuses a FortiGate SD-WAN hub for FortiSASE SPA and wants to confirm BGP is functioning, not only an IPsec phase-one tunnel. What is the most direct technical change to address the stated requirement?
- Correct return-path routing and stateful policy consistency for private applications over SPA
- Use FortiSASE SPA PoP-to-FortiGate hub IPsec connectivity with specific private routing and access policies
- Validate BGP adjacency and learned private routes across the tunnel
- Manage and verify the supported SD-WAN hub configuration objects through FortiManager with controlled deployment
Explanation
Correct Answer
C:Validate BGP adjacency and learned private routes across the tunnel. BGP exchanges reachable private prefixes required by the PoP-to-hub design. The configuration alone must be followed by a functioning test: The remote private destination is learned from the intended hub and forwarded over the VPN.
Incorrect Answers
A:Correct return-path routing and stateful policy consistency for private applications over SPA. The outcome for that step belongs to a remote employee reaches the hub over IPsec, but an internal firewall policy forwards a server reply through a different, untracked WAN path. Here the decisive requirement concerns a service provider reuses a FortiGate SD-WAN hub for FortiSASE SPA and wants to confirm BGP is functioning, not only an IPsec phase-one tunnel, so validate BGP adjacency and learned private routes across the tunnel is the better fit.
B:Use FortiSASE SPA PoP-to-FortiGate hub IPsec connectivity with specific private routing and access policies. It addresses 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. In the reported environment, the missing behavior instead relates to a service provider reuses a FortiGate SD-WAN hub for FortiSASE SPA and wants to confirm BGP is functioning, not only an IPsec phase-one tunnel. The relevant choice is validate BGP adjacency and learned private routes across the tunnel.
D:Manage and verify the supported SD-WAN hub configuration objects through FortiManager with controlled deployment. It could be appropriate when a company uses FortiManager for its FortiGate hub configurations and wants to prevent the SASE overlay settings from drifting across multiple sites. However, that does not resolve the stated condition: a service provider reuses a FortiGate SD-WAN hub for FortiSASE SPA and wants to confirm BGP is functioning, not only an IPsec phase-one tunnel. A more direct answer is validate BGP adjacency and learned private routes across the tunnel.
Question 233
The team is troubleshooting the following Fortinet 7.6 deployment: One group of remote staff must use always-on FortiClient connectivity, while IT administrators are allowed to disconnect temporarily. Which specific corrective action should be prioritized?
- Configure the supported SWG SSO policy with required deep SSL inspection and trusted CA handling
- Check the FortiSASE RADIUS server settings and shared secret against the server-side client definition
- Create and assign different endpoint profiles with the corresponding allowed disconnect behavior
- Provision the contractor using an agentless Internet proxy policy and omit unrelated private-access grants
Explanation
Correct Answer
C:Create and assign different endpoint profiles with the corresponding allowed disconnect behavior. Endpoint profiles can differentiate connection behavior by selected AD or non-AD user groups. The configuration alone must be followed by a functioning test: Standard staff cannot disconnect, while the approved IT group has the intended exception.
Incorrect Answers
A:Configure the supported SWG SSO policy with required deep SSL inspection and trusted CA handling. It could be appropriate when the SASE team expects users to authenticate through SWG SSO but the configured policy uses certificate inspection only. However, that does not resolve the stated condition: one group of remote staff must use always-on FortiClient connectivity, while IT administrators are allowed to disconnect temporarily. A more direct answer is create and assign different endpoint profiles with the corresponding allowed disconnect behavior.
B: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 one group of remote staff must use always-on FortiClient connectivity, while IT administrators are allowed to disconnect temporarily. The relevant choice is create and assign different endpoint profiles with the corresponding allowed disconnect behavior.
D:Provision the contractor using an agentless Internet proxy policy and omit unrelated private-access grants. The outcome for that step belongs to a temporary contractor should use the secure web gateway but must not be able to reach private network IP ranges via a full tunnel. Here the decisive requirement concerns one group of remote staff must use always-on FortiClient connectivity, while IT administrators are allowed to disconnect temporarily, so create and assign different endpoint profiles with the corresponding allowed disconnect behavior is the better fit.
Question 234
The operator wants evidence before implementing a fix. Which specific check best distinguishes the reported failure? An auditor asks for evidence that a newly configured SD-WAN rule affects only the intended application group.
- Inspect traffic classification, rule ID and source/destination fields for both cohorts
- Filter logs by source, destination, time and relevant rule or session identifiers
- Review exact timestamps and event types around the member transition
- Inspect transaction timestamps and log status on both sides of the impairment
Explanation
Correct Answer
A:Inspect traffic classification, rule ID and source/destination fields for both cohorts. The observed evidence guides the targeted repair: Filter traffic logs by the dedicated rule and compare matching and nonmatching application sessions.
Incorrect Answers
B:Filter logs by source, destination, time and relevant rule or session identifiers. It addresses a helpdesk needs to determine which SD-WAN rule sent a transaction to the backup ISP after a policy change. In the reported environment, the missing behavior instead relates to an auditor asks for evidence that a newly configured SD-WAN rule affects only the intended application group. The relevant choice is inspect traffic classification, rule ID and source/destination fields for both cohorts.
C:Review exact timestamps and event types around the member transition. That is a useful action for a different circumstance: an operator says a VPN application keeps failing over but cannot show whether the trigger was packet loss or a routing change. The present case is constrained by an auditor asks for evidence that a newly configured SD-WAN rule affects only the intended application group; the targeted response is inspect traffic classification, rule ID and source/destination fields for both cohorts.
D:Inspect transaction timestamps and log status on both sides of the impairment. The outcome for that step belongs to a branch rollout claims reliable failover because the WAN link state changed, but the business owner wants proof that application transactions continued. Here the decisive requirement concerns an auditor asks for evidence that a newly configured SD-WAN rule affects only the intended application group, so inspect traffic classification, rule ID and source/destination fields for both cohorts is the better fit.
Question 235
The operator wants evidence before implementing a fix. Which specific check best distinguishes the reported failure? A dual-ISP FortiGate has SD-WAN members and an Internet access policy, but forwarding lookup reports no route to public destinations.
- Examine an identified conference flow and verify which SD-WAN rule it matches
- Inspect whether the VPN tunnel is established and whether routes to private prefixes use the overlay zone
- Review the route lookup for a representative public destination and the next-hop resolution
- Inspect the configured health checks and each member's monitored state in the SD-WAN dashboard
Explanation
Correct Answer
C:Review the route lookup for a representative public destination and the next-hop resolution. The observed evidence guides the targeted repair: Install a valid default route that resolves through the intended SD-WAN zone or member design.
Incorrect Answers
A:Examine an identified conference flow and verify which SD-WAN rule it matches. It could be appropriate when an administrator plans to give video conferencing first priority over bulk patch downloads on a two-link branch. However, that does not resolve the stated condition: a dual-ISP FortiGate has SD-WAN members and an Internet access policy, but forwarding lookup reports no route to public destinations. A more direct answer is review the route lookup for a representative public destination and the next-hop resolution.
B:Inspect whether the VPN tunnel is established and whether routes to private prefixes use the overlay zone. The outcome for that step belongs to a bank requires private site-to-site application access through its FortiGate SD-WAN hub, while local Internet traffic should exit each branch directly. Here the decisive requirement concerns a dual-ISP FortiGate has SD-WAN members and an Internet access policy, but forwarding lookup reports no route to public destinations, so review the route lookup for a representative public destination and the next-hop resolution is the better fit.
D:Inspect the configured health checks and each member's monitored state in the SD-WAN dashboard. It addresses a new deployment has two ISP connections but operators cannot compare their real-time health from the ordinary interface inventory. In the reported environment, the missing behavior instead relates to a dual-ISP FortiGate has SD-WAN members and an Internet access policy, but forwarding lookup reports no route to public destinations. The relevant choice is review the route lookup for a representative public destination and the next-hop resolution.
Question 236
After the authorized change to apply the required security profiles to the matching allow firewall policy independently of SD-WAN member setup, which result actually demonstrates that this site's requirement is met? Initial issue: A branch was built with two SD-WAN members, but a team assumes this alone automatically adds application inspection to client sessions.
- Traffic transitions to a qualifying link when the poor circuit crosses its configured SLA bounds
- Branch users reach the hub-hosted application through IPsec while ordinary Internet access uses the local ISP
- A new external session finds a default route and egresses on an eligible SD-WAN member
- An allowed session uses an SD-WAN member while the relevant content/security event is logged by its profile
Explanation
Correct Answer
D:An allowed session uses an SD-WAN member while the relevant content/security event is logged by its profile. This is stronger than a saved configuration because it tests the intended operational result. Path selection and security inspection are separate controls in FortiOS.
Incorrect Answers
A:Traffic transitions to a qualifying link when the poor circuit crosses its configured SLA bounds. It could be appropriate when a support engineer sees packet loss on one uplink but all interface LEDs are green and traffic continues to pick the poor circuit. However, that does not resolve the stated condition: a branch was built with two SD-WAN members, but a team assumes this alone automatically adds application inspection to client sessions. A more direct answer is an allowed session uses an SD-WAN member while the relevant content/security event is logged by its profile.
B:Branch users reach the hub-hosted application through IPsec while ordinary Internet access uses the local ISP. That is a useful action for a different circumstance: a bank requires private site-to-site application access through its FortiGate SD-WAN hub, while local Internet traffic should exit each branch directly. The present case is constrained by a branch was built with two SD-WAN members, but a team assumes this alone automatically adds application inspection to client sessions; the targeted response is an allowed session uses an SD-WAN member while the relevant content/security event is logged by its profile.
C:A new external session finds a default route and egresses on an eligible SD-WAN member. It addresses a dual-ISP FortiGate has SD-WAN members and an Internet access policy, but forwarding lookup reports no route to public destinations. In the reported environment, the missing behavior instead relates to a branch was built with two SD-WAN members, but a team assumes this alone automatically adds application inspection to client sessions. The relevant choice is an allowed session uses an SD-WAN member while the relevant content/security event is logged by its profile.
Question 237
For this Fortinet incident, which observation should the engineer collect first to validate the suspected condition? An administrator configured a voice SLA but notices the corresponding SD-WAN rule still selects a poor-quality circuit.
- Compare measured jitter for each member with the voice SLA target rather than only checking packet loss
- Inspect the rule's configured SLA target and current selected-member diagnostics
- Check the configured probe target and active health-check status for each member
- Inspect whether the monitored service has sufficient real sessions to supply passive samples
Explanation
Correct Answer
B:Inspect the rule's configured SLA target and current selected-member diagnostics. This check isolates the relevant control before the change. Measured SLA state affects a rule only when that rule's selection logic actually uses it.
Incorrect Answers
A:Compare measured jitter for each member with the voice SLA target rather than only checking packet loss. It could be appropriate when a voice application performs poorly with high jitter even though packet loss is low on both WANs. However, that does not resolve the stated condition: an administrator configured a voice SLA but notices the corresponding SD-WAN rule still selects a poor-quality circuit. A more direct answer is inspect the rule's configured SLA target and current selected-member diagnostics.
C:Check the configured probe target and active health-check status for each member. The outcome for that step belongs to two WAN interfaces show up, but the network manager needs continuous health information even when no users are active. Here the decisive requirement concerns an administrator configured a voice SLA but notices the corresponding SD-WAN rule still selects a poor-quality circuit, so inspect the rule's configured SLA target and current selected-member diagnostics is the better fit.
D:Inspect whether the monitored service has sufficient real sessions to supply passive samples. That is a useful action for a different circumstance: a metered branch wants link-quality measurements without creating additional periodic probe traffic during normal use. The present case is constrained by an administrator configured a voice SLA but notices the corresponding SD-WAN rule still selects a poor-quality circuit; the targeted response is inspect the rule's configured SLA target and current selected-member diagnostics.
Question 238
The team plans to install or correct the private route to resolve through the proper overlay zone and enforce its firewall policy for the situation below. Which remaining implementation pitfall is directly relevant to this same requirement? Following a tunnel migration, the interface is healthy but users cannot reach private subnets behind the SD-WAN hub.
- Checking only tunnel status can miss route or firewall-policy defects
- Source-based hashing should not be represented as a guarantee of per-connection even balance for one user
- Merely changing the member SLA cannot fix an earlier catchall consuming the wrong traffic
- Adding more SLA targets to the later rule cannot help while it is never evaluated for matching traffic
Explanation
Correct Answer
A:Checking only tunnel status can miss route or firewall-policy defects. This is an implementation boundary for the proposed fix, so the deployment needs a specific follow-up check.
Incorrect Answers
B:Source-based hashing should not be represented as a guarantee of per-connection even balance for one user. The outcome for that step belongs to the network team configures a load-balancing algorithm by source IP, then complains each employee's sessions generally stay on one circuit. Here the decisive requirement concerns following a tunnel migration, the interface is healthy but users cannot reach private subnets behind the SD-WAN hub, so checking only tunnel status can miss route or firewall-policy defects is the better fit.
C:Merely changing the member SLA cannot fix an earlier catchall consuming the wrong traffic. It addresses a configuration has one generic catchall rule and one narrowly matched billing rule; billing traffic uses the wrong member. In the reported environment, the missing behavior instead relates to following a tunnel migration, the interface is healthy but users cannot reach private subnets behind the SD-WAN hub. The relevant choice is checking only tunnel status can miss route or firewall-policy defects.
D:Adding more SLA targets to the later rule cannot help while it is never evaluated for matching traffic. That is a useful action for a different circumstance: a single high-priority SD-WAN rule is matching every WAN flow, preventing a later SaaS-specific rule from being used. The present case is constrained by following a tunnel migration, the interface is healthy but users cannot reach private subnets behind the SD-WAN hub; the targeted response is checking only tunnel status can miss route or firewall-policy defects.
Question 239
After the authorized change to reduce the required qualifying-member minimum only if the availability design permits it, or restore a third qualifying member, which result actually demonstrates that this site's requirement is met? Initial issue: 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.
- Under a session-based distribution rule, new connections can spread independently rather than strictly by source IP
- Emergency flows use the intended LTE member without rerouting unrelated Web traffic
- The rule becomes active only once the configured qualifying-member count is satisfied
- The SaaS service hits its own rule while generic traffic remains under the broad steering rule
Explanation
Correct Answer
C:The rule becomes active only once the configured qualifying-member count is satisfied. It demonstrates that the intended path or control is actually working, not merely configured.
Incorrect Answers
A:Under a session-based distribution rule, new connections can spread independently rather than strictly by source IP. The outcome for that step belongs to the network team configures a load-balancing algorithm by source IP, then complains each employee's sessions generally stay on one circuit. Here the decisive requirement concerns 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, so the rule becomes active only once the configured qualifying-member count is satisfied is the better fit.
B:Emergency flows use the intended LTE member without rerouting unrelated Web 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: 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. A more direct answer is the rule becomes active only once the configured qualifying-member count is satisfied.
D:The SaaS service hits its own rule while generic traffic remains under the broad steering rule. It addresses a single high-priority SD-WAN rule is matching every WAN flow, preventing a later SaaS-specific rule from being used. In the reported environment, the missing behavior instead relates to 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. The relevant choice is the rule becomes active only once the configured qualifying-member count is satisfied.
Question 240
For the stated scenario, what is the most important remaining blind spot after the proposed correction? A company must prevent employees from uploading a known sensitive document pattern into unapproved SaaS applications.
- A passing antivirus signal cannot override a separately required management-telemetry check
- Application allowlisting alone may not detect prohibited information within an otherwise allowed upload
- An inventory dashboard that reports posture without enforcing it does not satisfy conditional-access goals
- A successful SSO login does not erase high-severity vulnerability findings
Explanation
Correct Answer
B:Application allowlisting alone may not detect prohibited information within an otherwise allowed upload. The planned change can still miss the requirement if this condition is left unresolved. Data loss prevention evaluates sensitive-data patterns or content conditions rather than just the site name.
Incorrect Answers
A:A passing antivirus signal cannot override a separately required management-telemetry check. It could be appropriate when a managed endpoint runs antivirus, yet it has stopped sending required endpoint telemetry to the FortiSASE management service. However, that does not resolve the stated condition: a company must prevent employees from uploading a known sensitive document pattern into unapproved SaaS applications. A more direct answer is application allowlisting alone may not detect prohibited information within an otherwise allowed upload.
C:An inventory dashboard that reports posture without enforcing it does not satisfy conditional-access goals. That is a useful action for a different circumstance: security wants a noncompliant laptop to be unable to access protected company applications until it passes device checks. The present case is constrained by a company must prevent employees from uploading a known sensitive document pattern into unapproved SaaS applications; the targeted response is application allowlisting alone may not detect prohibited information within an otherwise allowed upload.
D:A successful SSO login does not erase high-severity vulnerability findings. The outcome for that step belongs to a remote fleet must reject endpoints with known high or critical vulnerabilities before they reach private applications. Here the decisive requirement concerns a company must prevent employees from uploading a known sensitive document pattern into unapproved SaaS applications, so application allowlisting alone may not detect prohibited information within an otherwise allowed upload is the better fit.
Fortinet NSE 5 - FortiSASE and SD-WAN 7.6 Core Administrator (NSE5_SSE_AD-7.6) Practice Tests