Question 120
The team has applied the proposed fix. Which user-visible or logged result is the strongest validation for this case? A finance department wants lower monthly WAN costs but only from links that satisfy latency and jitter requirements.
- Changing measured quality produces a corresponding member-selection change for the voice rule
- The lower-cost compliant link is selected; a lower-cost failing link does not automatically win
- Fresh monitoring intervals show quality consistent with the restored circuit and the SLA target
- The monitor updates quality statistics as application sessions traverse the selected WAN
Explanation
Correct Answer
B:The lower-cost compliant link is selected; a lower-cost failing link does not automatically win. This is stronger than a saved configuration because it tests the intended operational result. This strategy elects the lowest-cost member among links meeting the SLA before considering preference ties.
Incorrect Answers
A:Changing measured quality produces a corresponding member-selection change for the voice rule. It could be appropriate when an administrator configured a voice SLA but notices the corresponding SD-WAN rule still selects a poor-quality circuit. However, that does not resolve the stated condition: a finance department wants lower monthly WAN costs but only from links that satisfy latency and jitter requirements. A more direct answer is the lower-cost compliant link is selected; a lower-cost failing link does not automatically win.
C:Fresh monitoring intervals show quality consistent with the restored circuit and the SLA target. That is a useful action for a different circumstance: a branch upgraded an ISP, yet the SLA interface health view still shows old packet-loss and jitter statistics from before the maintenance. The present case is constrained by a finance department wants lower monthly WAN costs but only from links that satisfy latency and jitter requirements; the targeted response is the lower-cost compliant link is selected; a lower-cost failing link does not automatically win.
D:The monitor updates quality statistics as application sessions traverse the selected WAN. The outcome for that step belongs to a metered branch wants link-quality measurements without creating additional periodic probe traffic during normal use. Here the decisive requirement concerns a finance department wants lower monthly WAN costs but only from links that satisfy latency and jitter requirements, so the lower-cost compliant link is selected; a lower-cost failing link does not automatically win is the better fit.
Question 121
Before changing the configuration, the team needs to isolate the problem. Which diagnostic check is most targeted here? Incident: After moving one ISP into SD-WAN, an operator expects the ISP address to remain a valid direct firewall-policy interface target for all WAN rules.
- Examine an identified conference flow and verify which SD-WAN rule it matches
- Examine the underlay carrier and last-mile path of each member, not just the FortiGate interface names
- Query the active SD-WAN rule status for the destination or application represented by the sample flow
- Inspect the policy's destination interface and the assigned zone of that WAN member
Explanation
Correct Answer
D:Inspect the policy's destination interface and the assigned zone of that WAN member. This check isolates the relevant control before the change. FortiGate logically groups SD-WAN members into zones and uses zones as policy interfaces.
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: after moving one ISP into SD-WAN, an operator expects the ISP address to remain a valid direct firewall-policy interface target for all WAN rules. A more direct answer is inspect the policy's destination interface and the assigned zone of that WAN member.
B:Examine the underlay carrier and last-mile path of each member, not just the FortiGate interface names. It addresses a company wants to prevent simultaneous failure of two Internet circuits from the same carrier. In the reported environment, the missing behavior instead relates to after moving one ISP into SD-WAN, an operator expects the ISP address to remain a valid direct firewall-policy interface target for all WAN rules. The relevant choice is inspect the policy's destination interface and the assigned zone of that WAN member.
C:Query the active SD-WAN rule status for the destination or application represented by the sample flow. That is a useful action for a different circumstance: a branch has two active ISP ports but no deliberate way to confirm which one should carry a sample cloud-app session. The present case is constrained by after moving one ISP into SD-WAN, an operator expects the ISP address to remain a valid direct firewall-policy interface target for all WAN rules; the targeted response is inspect the policy's destination interface and the assigned zone of that WAN member.
Question 122
During implementation, the administrator observes: A company configures an Active Directory group for endpoint profiles, but a recently added user still receives the Default profile. Which intervention targets the described fault rather than an adjacent workflow?
- Trigger the supported endpoint-profile update and verify the client receives the current managed configuration
- Sync the AD connection and verify the effective user/group-based endpoint-profile assignment
- Create and assign different endpoint profiles with the corresponding allowed disconnect behavior
- Configure and test the supported SAML identity provider integration and user-group claims
Explanation
Correct Answer
B:Sync the AD connection and verify the effective user/group-based endpoint-profile assignment. Endpoint assignment depends on available synchronized directory membership and profile matching. The acceptance check should show: The new user receives the assigned custom profile once membership is correctly recognized.
Incorrect Answers
A:Trigger the supported endpoint-profile update and verify the client receives the current managed configuration. That is a useful action for a different circumstance: a remote endpoint has FortiClient installed, but the connection profile is stale after the administrator changes the tenant settings. The present case is constrained by a company configures an Active Directory group for endpoint profiles, but a recently added user still receives the Default profile; the targeted response is sync the AD connection and verify the effective user/group-based endpoint-profile assignment.
C:Create and assign different endpoint profiles with the corresponding allowed disconnect behavior. It could be appropriate when one group of remote staff must use always-on FortiClient connectivity, while IT administrators are allowed to disconnect temporarily. However, that does not resolve the stated condition: a company configures an Active Directory group for endpoint profiles, but a recently added user still receives the Default profile. A more direct answer is sync the AD connection and verify the effective user/group-based endpoint-profile assignment.
D:Configure and test the supported SAML identity provider integration and user-group claims. The outcome for that step belongs to a corporation already authenticates its employees with an enterprise SAML identity provider and wants single sign-on for FortiSASE user access. Here the decisive requirement concerns a company configures an Active Directory group for endpoint profiles, but a recently added user still receives the Default profile, so sync the AD connection and verify the effective user/group-based endpoint-profile assignment is the better fit.
Question 123
The team is troubleshooting the following Fortinet 7.6 deployment: A branch switches to a new ISP and forgets to update the static route's gateway, causing repeated probe failures on that member. Which specific corrective action should be prioritized?
- Inspect the live session's interface, policy and SD-WAN rule context alongside routing diagnostics
- Correct the upstream gateway next hop and verify reachability from that member
- Keep the more-specific private route toward the tunnel while using default Internet reachability for public traffic
- Check SNAT and session behavior when rerouting across WAN members, not only link quality
Explanation
Correct Answer
B:Correct the upstream gateway next hop and verify reachability from that member. Health probes cannot succeed through an unreachable gateway even if their target is valid. The acceptance check should show: The corrected interface reaches its first hop and the remote SLA server.
Incorrect Answers
A:Inspect the live session's interface, policy and SD-WAN rule context alongside routing diagnostics. That is a useful action for a different circumstance: an SD-WAN operator wants to prove that a payment session left through the correct tunnel after an incident, rather than infer from routes alone. The present case is constrained by a branch switches to a new ISP and forgets to update the static route's gateway, causing repeated probe failures on that member; the targeted response is correct the upstream gateway next hop and verify reachability from that member.
C:Keep the more-specific private route toward the tunnel while using default Internet reachability for public traffic. The outcome for that step belongs to a branch traffic policy should use one ISP for public destinations but a private tunnel for an RFC1918 destination. Here the decisive requirement concerns a branch switches to a new ISP and forgets to update the static route's gateway, causing repeated probe failures on that member, so correct the upstream gateway next hop and verify reachability from that member is the better fit.
D:Check SNAT and session behavior when rerouting across WAN members, not only link quality. It could be appropriate when a NATed application stops after switching from ISP1 to ISP2 because the upstream sees a different public source address. However, that does not resolve the stated condition: a branch switches to a new ISP and forgets to update the static route's gateway, causing repeated probe failures on that member. A more direct answer is correct the upstream gateway next hop and verify reachability from that member.
Question 124
After the authorized change to fix the measured quality or revise a justified SLA threshold instead of treating route presence as proof of eligibility, which result actually demonstrates that this site's requirement is met? Initial issue: An administrator configured two redundant WAN routes but an SD-WAN service reports one member unavailable because its required SLA is failing.
- The repaired member is both routed and SLA-qualified when its measured performance meets the target
- The hub routing table contains the expected reachable prefixes across the overlay
- The destination gains a usable route and a new session follows the intended eligible WAN2 member
- The observed egress follows the final documented routing and SD-WAN policy design
Explanation
Correct Answer
A:The repaired member is both routed and SLA-qualified when its measured performance meets the target. It demonstrates that the intended path or control is actually working, not merely configured.
Incorrect Answers
B:The hub routing table contains the expected reachable prefixes across the overlay. It addresses remote users can reach an SASE security PoP, but the FortiGate SD-WAN hub never learns the private prefix it should send toward that PoP. In the reported environment, the missing behavior instead relates to an administrator configured two redundant WAN routes but an SD-WAN service reports one member unavailable because its required SLA is failing. The relevant choice is the repaired member is both routed and SLA-qualified when its measured performance meets the target.
C:The destination gains a usable route and a new session follows the intended eligible WAN2 member. The outcome for that step belongs to a FortiGate has a manual SD-WAN rule preferring WAN2, but a route lookup for the destination has no usable next hop. Here the decisive requirement concerns an administrator configured two redundant WAN routes but an SD-WAN service reports one member unavailable because its required SLA is failing, so the repaired member is both routed and SLA-qualified when its measured performance meets the target is the better fit.
D:The observed egress follows the final documented routing and SD-WAN policy design. That is a useful action for a different circumstance: an internal subnet uses an explicit policy route to a particular WAN interface, but the operator assumes all traffic is governed by the later SD-WAN rule. The present case is constrained by an administrator configured two redundant WAN routes but an SD-WAN service reports one member unavailable because its required SLA is failing; the targeted response is the repaired member is both routed and SLA-qualified when its measured performance meets the target.
Question 125
An acceptance test is needed after the change. Which measured outcome best confirms the described Fortinet issue has been resolved? A NATed application stops after switching from ISP1 to ISP2 because the upstream sees a different public source address.
- Fresh connections successfully establish through the chosen ISP's correct translated source
- New outbound sessions have a valid route and then match the intended steering strategy
- The hub routing table contains the expected reachable prefixes across the overlay
- The observed egress follows the final documented routing and SD-WAN policy design
Explanation
Correct Answer
A:Fresh connections successfully establish through the chosen ISP's correct translated source. It demonstrates that the intended path or control is actually working, not merely configured.
Incorrect Answers
B:New outbound sessions have a valid route and then match the intended steering strategy. It addresses an engineer added an SD-WAN steering rule but expected it to override a missing default route for general Internet traffic. In the reported environment, the missing behavior instead relates to a NATed application stops after switching from ISP1 to ISP2 because the upstream sees a different public source address. The relevant choice is fresh connections successfully establish through the chosen ISP's correct translated source.
C:The hub routing table contains the expected reachable prefixes across the overlay. The outcome for that step belongs to remote users can reach an SASE security PoP, but the FortiGate SD-WAN hub never learns the private prefix it should send toward that PoP. Here the decisive requirement concerns a NATed application stops after switching from ISP1 to ISP2 because the upstream sees a different public source address, so fresh connections successfully establish through the chosen ISP's correct translated source is the better fit.
D:The observed egress follows the final documented routing and SD-WAN policy design. That is a useful action for a different circumstance: an internal subnet uses an explicit policy route to a particular WAN interface, but the operator assumes all traffic is governed by the later SD-WAN rule. The present case is constrained by a NATed application stops after switching from ISP1 to ISP2 because the upstream sees a different public source address; the targeted response is fresh connections successfully establish through the chosen ISP's correct translated source.
Question 126
For a change review, the team proposes to correct return-path routing and stateful policy consistency for private applications over SPA because: A remote employee reaches the hub over IPsec, but an internal firewall policy forwards a server reply through a different, untracked WAN path. Which explanation connects the change to the underlying behavior?
- Peer addressing must match the current hub for an IPsec overlay to negotiate correctly
- Stateful application connectivity depends on viable forward and reverse paths matching security expectations
- Centralized orchestration can standardize supported configuration across FortiGate hubs while preserving site-specific data
- SPA via hub overlays carries private application traffic through encrypted controlled connectivity
Explanation
Correct Answer
B:Stateful application connectivity depends on viable forward and reverse paths matching security expectations. It directly explains the need to correct return-path routing and stateful policy consistency for private applications over SPA. The narrow validation is: A remote session completes request and response through the intended protected private path.
Incorrect Answers
A:Peer addressing must match the current hub for an IPsec overlay to negotiate correctly. 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 remote employee reaches the hub over IPsec, but an internal firewall policy forwards a server reply through a different, untracked WAN path, so stateful application connectivity depends on viable forward and reverse paths matching security expectations is the better fit.
C:Centralized orchestration can standardize supported configuration across FortiGate hubs while preserving site-specific data. 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 remote employee reaches the hub over IPsec, but an internal firewall policy forwards a server reply through a different, untracked WAN path. A more direct answer is stateful application connectivity depends on viable forward and reverse paths matching security expectations.
D:SPA via hub overlays carries private application traffic through encrypted controlled connectivity. That is a useful action for a different circumstance: an organization needs private TCP and UDP access to multiple office services without publishing public listener ports. The present case is constrained by a remote employee reaches the hub over IPsec, but an internal firewall policy forwards a server reply through a different, untracked WAN path; the targeted response is stateful application connectivity depends on viable forward and reverse paths matching security expectations.
Question 127
Given this incident — 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. — the administrator plans to generate a filtered security or usage report with the relevant block category, user grouping and comparable time windows. Which technical principle justifies it?
- External forwarding supports a separate retention/compliance workflow beyond dashboards' immediate views
- The current visible-log export reflects selected entries rather than an unlimited historical dataset
- 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
D:Grouping by both user and enforcement action helps separate policy behavior from raw request volume. It directly explains the need to generate a filtered security or usage report with the relevant block category, user grouping and comparable time windows. The narrow validation is: The report shows blocked-event trends per cohort alongside enough traffic context to interpret the change.
Incorrect Answers
A:External forwarding supports a separate retention/compliance workflow beyond dashboards' immediate views. That is a useful action for a different circumstance: a regulated organization must retain FortiSASE security logs in an approved on-premises analytics system beyond the service's ordinary retention window. The present case is constrained by 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; the targeted response is grouping by both user and enforcement action helps separate policy behavior from raw request volume.
B:The current visible-log export reflects selected entries rather than an unlimited historical dataset. It addresses an analyst exports the currently filtered FortiSASE security-log view but expects every historical event in the tenant to appear in that export. In the reported environment, the missing behavior instead relates 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. The relevant choice is grouping by both user and enforcement action helps separate policy behavior from raw request volume.
C:Time-window comparison can distinguish a real category-policy trend from a single cumulative count. It could be appropriate when a security officer needs proof that web-category policy violations increased after a recent configuration change. However, that does not resolve the stated condition: 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. A more direct answer is grouping by both user and enforcement action helps separate policy behavior from raw request volume.
Question 128
During readiness review, which case-specific risk must the team still rule out before declaring this change successful? 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.
- An allow-any Internet policy is not a substitute for private-prefix routing and least-privilege access
- An agentless web proxy is not equivalent to full-device private-network tunnel access
- A traffic log showing an allowed website request is not proof of who edited the policy
- An on-premises branch-only firewall rule cannot cover remote sessions that never traverse that branch
Explanation
Correct Answer
A:An allow-any Internet policy is not a substitute for private-prefix routing and least-privilege access. This is an implementation boundary for the proposed fix, so the deployment needs a specific follow-up check.
Incorrect Answers
B:An agentless web proxy is not equivalent to full-device private-network tunnel access. That is a useful action for a different circumstance: external contractors cannot install FortiClient, but they must use secure browser access through a managed gateway. The present case is constrained by 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 targeted response is an allow-any Internet policy is not a substitute for private-prefix routing and least-privilege access.
C:A traffic log showing an allowed website request is not proof of who edited the policy. The outcome for that step belongs to an internal audit asks whether a just-deployed SASE policy was changed by an authorized operator during a specific window. Here the decisive requirement concerns 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, so an allow-any Internet policy is not a substitute for private-prefix routing and least-privilege access is the better fit.
D:An on-premises branch-only firewall rule cannot cover remote sessions that never traverse that branch. It addresses a large retailer wants to prove that security policy enforcement for mobile employees is cloud-based rather than tied to their nearest on-premises office firewall. In the reported environment, the missing behavior instead relates to 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 relevant choice is an allow-any Internet policy is not a substitute for private-prefix routing and least-privilege access.
Question 129
The team plans to troubleshoot BGP neighbor establishment and route advertisement over the SPA overlay for the situation below. Which remaining implementation pitfall is directly relevant to this same requirement? Remote users can reach an SASE security PoP, but the FortiGate SD-WAN hub never learns the private prefix it should send toward that PoP.
- Lowest Cost (SLA) mode could prefer a cheaper merely compliant path rather than the best jitter
- An allow policy with broad destination 'all' is not an SD-WAN member-selection rule
- Deleting all custom rules does not disable the implicit fallback behavior
- An established IPsec security association alone does not prove the necessary BGP routes exist
Explanation
Correct Answer
D:An established IPsec security association alone does not prove the necessary BGP routes exist. The planned change can still miss the requirement if this condition is left unresolved. The FortiSASE-to-hub integration uses IPsec transport and routing information to reach private networks.
Incorrect Answers
A:Lowest Cost (SLA) mode could prefer a cheaper merely compliant path rather than the best jitter. It could be appropriate when video calls degrade on one WAN, and the administrator wants path selection based on measured jitter rather than link price. However, that does not resolve the stated condition: remote users can reach an SASE security PoP, but the FortiGate SD-WAN hub never learns the private prefix it should send toward that PoP. A more direct answer is an established IPsec security association alone does not prove the necessary BGP routes exist.
B:An allow policy with broad destination 'all' is not an SD-WAN member-selection rule. That is a useful action for a different circumstance: a custom policy is supposed to steer emergency traffic over a dedicated LTE link, but the operator only enabled the general default Internet policy. The present case is constrained by remote users can reach an SASE security PoP, but the FortiGate SD-WAN hub never learns the private prefix it should send toward that PoP; the targeted response is an established IPsec security association alone does not prove the necessary BGP routes exist.
C:Deleting all custom rules does not disable the implicit fallback behavior. It addresses no custom SD-WAN rule matches an otherwise permitted Internet session, but the session still leaves through an SD-WAN member. In the reported environment, the missing behavior instead relates to remote users can reach an SASE security PoP, but the FortiGate SD-WAN hub never learns the private prefix it should send toward that PoP. The relevant choice is an established IPsec security association alone does not prove the necessary BGP routes exist.
Question 130
During readiness review, which case-specific risk must the team still rule out before declaring this change successful? An organization moves its endpoint compliance policy to a stricter baseline and wants to avoid unexpected denial for every remote user at once.
- Immediate tenant-wide enforcement without testing can interrupt otherwise legitimate access
- Instructing users to ignore all certificate warnings would hide genuine TLS risks
- Application allowlisting alone may not detect prohibited information within an otherwise allowed upload
- Editing the shared default profile can affect other user groups unintentionally
Explanation
Correct Answer
A:Immediate tenant-wide enforcement without testing can interrupt otherwise legitimate access. This is an implementation boundary for the proposed fix, so the deployment needs a specific follow-up check.
Incorrect Answers
B:Instructing users to ignore all certificate warnings would hide genuine TLS risks. That is a useful action for a different circumstance: a browser user receives certificate warnings after FortiSASE deep inspection is activated for HTTPS sessions. The present case is constrained by an organization moves its endpoint compliance policy to a stricter baseline and wants to avoid unexpected denial for every remote user at once; the targeted response is immediate tenant-wide enforcement without testing can interrupt otherwise legitimate access.
C:Application allowlisting alone may not detect prohibited information within an otherwise allowed upload. The outcome for that step belongs to a company must prevent employees from uploading a known sensitive document pattern into unapproved SaaS applications. Here the decisive requirement concerns an organization moves its endpoint compliance policy to a stricter baseline and wants to avoid unexpected denial for every remote user at once, so immediate tenant-wide enforcement without testing can interrupt otherwise legitimate access is the better fit.
D:Editing the shared default profile can affect other user groups unintentionally. It addresses a remote employee group must receive stricter web inspection than another group while both use FortiSASE Internet access. In the reported environment, the missing behavior instead relates to an organization moves its endpoint compliance policy to a stricter baseline and wants to avoid unexpected denial for every remote user at once. The relevant choice is immediate tenant-wide enforcement without testing can interrupt otherwise legitimate access.
Fortinet NSE 5 - FortiSASE and SD-WAN 7.6 Core Administrator (NSE5_SSE_AD-7.6) Practice Tests