Question 250
During readiness review, which case-specific risk must the team still rule out before declaring this change successful? Security wants to determine whether an unauthorized SaaS upload was prevented by inline-CASB rather than a blanket web-filter deny.
- A rule configuration screenshot alone is weaker than observed matched-session behavior
- A domain deny would block the service as a whole and not demonstrate operation-level control
- The backup link being alive does not by itself prove the application still works
- A single average bandwidth value without time and member context cannot establish the spike's path
Explanation
Correct Answer
B:A domain deny would block the service as a whole and not demonstrate operation-level control. The planned change can still miss the requirement if this condition is left unresolved. Inline SaaS inspection can produce activity-level events distinct from domain-category blocks.
Incorrect Answers
A:A rule configuration screenshot alone is weaker than observed matched-session behavior. It could be appropriate when an auditor asks for evidence that a newly configured SD-WAN rule affects only the intended application group. However, that does not resolve the stated condition: security wants to determine whether an unauthorized SaaS upload was prevented by inline-CASB rather than a blanket web-filter deny. A more direct answer is a domain deny would block the service as a whole and not demonstrate operation-level control.
C:The backup link being alive does not by itself prove the application still works. 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 security wants to determine whether an unauthorized SaaS upload was prevented by inline-CASB rather than a blanket web-filter deny, so a domain deny would block the service as a whole and not demonstrate operation-level control is the better fit.
D:A single average bandwidth value without time and member context cannot establish the spike's path. That is a useful action for a different circumstance: a network lead wants to correlate a sudden traffic spike with which of two WAN members carried the load. The present case is constrained by security wants to determine whether an unauthorized SaaS upload was prevented by inline-CASB rather than a blanket web-filter deny; the targeted response is a domain deny would block the service as a whole and not demonstrate operation-level control.
Question 251
For a change review, the team proposes to verify the FortiManager-to-FortiSASE central-management link and the supported synchronized object types because: FortiSASE configuration is being centrally managed, but changes made in FortiManager do not appear in the remote tenant. Which explanation connects the change to the underlying behavior?
- 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
- Cloud PoPs apply policy on the user path, independent of the user's physical branch location
- Central management requires proper integration; not every setting necessarily synchronizes in both directions
Explanation
Correct Answer
D:Central management requires proper integration; not every setting necessarily synchronizes in both directions. It directly explains the need to verify the FortiManager-to-FortiSASE central-management link and the supported synchronized object types. The narrow validation is: A supported changed object appears in the FortiSASE tenant after successful synchronization.
Incorrect Answers
A:A profile group provides centrally defined inspection behavior that can be selected by relevant policies. That is a useful action for a different circumstance: a remote-work tenant plans to reuse common web-filter and IPS profiles across hundreds of users, with only selected groups receiving additional controls. The present case is constrained by fortiSASE configuration is being centrally managed, but changes made in FortiManager do not appear in the remote tenant; the targeted response is central management requires proper integration; not every setting necessarily synchronizes in both directions.
B:FortiManager can centrally synchronize selected object types with FortiSASE where integration is configured. It could be appropriate when a central network management program wants address groups and security profile groups shared between on-premise FortiGate and the FortiSASE tenant. However, that does not resolve the stated condition: fortiSASE configuration is being centrally managed, but changes made in FortiManager do not appear in the remote tenant. A more direct answer is central management requires proper integration; not every setting necessarily synchronizes in both directions.
C:Cloud PoPs apply policy on the user path, independent of the user's physical branch location. 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 fortiSASE configuration is being centrally managed, but changes made in FortiManager do not appear in the remote tenant. The relevant choice is central management requires proper integration; not every setting necessarily synchronizes in both directions.
Question 252
For a change review, the team proposes to provide an Internet default route that resolves through the SD-WAN design before testing policy steering because: An engineer added an SD-WAN steering rule but expected it to override a missing default route for general Internet traffic. Which explanation connects the change to the underlying behavior?
- A usable member requires a valid layer-3 next hop, not just a physically active interface
- A steering rule selects among already reachable egress paths; it is not a substitute for the forwarding route
- Policy routes can affect forwarding independently of ordinary destination route and member preference
- A change of egress public IP can affect remote-session continuity even when a new path is reachable
Explanation
Correct Answer
B:A steering rule selects among already reachable egress paths; it is not a substitute for the forwarding route. It directly explains the need to provide an Internet default route that resolves through the SD-WAN design before testing policy steering. The narrow validation is: New outbound sessions have a valid route and then match the intended steering strategy.
Incorrect Answers
A:A usable member requires a valid layer-3 next hop, not just a physically active interface. It could be appropriate when a WAN circuit changes its upstream gateway through DHCP; an old static next hop still refers to the former router. However, that does not resolve the stated condition: an engineer added an SD-WAN steering rule but expected it to override a missing default route for general Internet traffic. A more direct answer is a steering rule selects among already reachable egress paths; it is not a substitute for the forwarding route.
C:Policy routes can affect forwarding independently of ordinary destination route and member preference. 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 engineer added an SD-WAN steering rule but expected it to override a missing default route for general Internet traffic; the targeted response is a steering rule selects among already reachable egress paths; it is not a substitute for the forwarding route.
D:A change of egress public IP can affect remote-session continuity even when a new path is reachable. The outcome for that step belongs to a NATed application stops after switching from ISP1 to ISP2 because the upstream sees a different public source address. Here the decisive requirement concerns an engineer added an SD-WAN steering rule but expected it to override a missing default route for general Internet traffic, so a steering rule selects among already reachable egress paths; it is not a substitute for the forwarding route is the better fit.
Question 253
The team is troubleshooting the following Fortinet 7.6 deployment: The network team configures a load-balancing algorithm by source IP, then complains each employee's sessions generally stay on one circuit. Which specific corrective action should be prioritized?
- Inspect the configurable implicit SD-WAN rule rather than assuming no traffic selection occurs
- Use an appropriate load-balancing strategy and verify how the selected algorithm distributes sessions
- Correct the SD-WAN rule's source criteria to the actual migrated subnet
- Verify the source-IP hash selection and choose a different supported balancing method if per-session spreading is required
Explanation
Correct Answer
D:Verify the source-IP hash selection and choose a different supported balancing method if per-session spreading is required. Source-IP hashing intentionally associates the same source with a deterministic member selection. The acceptance check should show: Under a session-based distribution rule, new connections can spread independently rather than strictly by source IP.
Incorrect Answers
A:Inspect the configurable implicit SD-WAN rule rather than assuming no traffic selection occurs. That is a useful action for a different circumstance: no custom SD-WAN rule matches an otherwise permitted Internet session, but the session still leaves through an SD-WAN member. The present case is constrained by the network team configures a load-balancing algorithm by source IP, then complains each employee's sessions generally stay on one circuit; the targeted response is verify the source-IP hash selection and choose a different supported balancing method if per-session spreading is required.
B:Use an appropriate load-balancing strategy and verify how the selected algorithm distributes sessions. It addresses a branch wants bulk backup transfers to distribute across two eligible WAN circuits instead of consistently choosing one preferred link. In the reported environment, the missing behavior instead relates to the network team configures a load-balancing algorithm by source IP, then complains each employee's sessions generally stay on one circuit. The relevant choice is verify the source-IP hash selection and choose a different supported balancing method if per-session spreading is required.
C:Correct the SD-WAN rule's source criteria to the actual migrated subnet. It could be appropriate when fortiGate's traffic policy permits VoIP, but its SD-WAN rule is scoped to the wrong source network after a subnet migration. However, that does not resolve the stated condition: the network team configures a load-balancing algorithm by source IP, then complains each employee's sessions generally stay on one circuit. A more direct answer is verify the source-IP hash selection and choose a different supported balancing method if per-session spreading is required.
Question 254
For the stated scenario, what is the most important remaining blind spot after the proposed correction? A policy owner needs the same source subnet to reach two applications over different WANs without changing the firewall allow decision.
- Steering alone cannot resolve a mistaken destination prefix or absent BGP route
- Changing the firewall policy action alone does not select the distinct outbound members
- Checking only tunnel status can miss route or firewall-policy defects
- A link SLA tweak cannot explain a route that already wins or loses on routing preference
Explanation
Correct Answer
B:Changing the firewall policy action alone does not select the distinct outbound members. The planned change can still miss the requirement if this condition is left unresolved. SD-WAN steering is independent of the permit policy and can choose links using service-specific matches.
Incorrect Answers
A: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 a policy owner needs the same source subnet to reach two applications over different WANs without changing the firewall allow decision, so changing the firewall policy action alone does not select the distinct outbound members is the better fit.
C:Checking only tunnel status can miss route or firewall-policy defects. That is a useful action for a different circumstance: following a tunnel migration, the interface is healthy but users cannot reach private subnets behind the SD-WAN hub. The present case is constrained by a policy owner needs the same source subnet to reach two applications over different WANs without changing the firewall allow decision; the targeted response is changing the firewall policy action alone does not select the distinct outbound members.
D:A link SLA tweak cannot explain a route that already wins or loses on routing preference. It could be appropriate when a FortiGate has overlapping routes to the same subnet and analysts see intermittent egress selection they attribute to SD-WAN health checks. However, that does not resolve the stated condition: a policy owner needs the same source subnet to reach two applications over different WANs without changing the firewall allow decision. A more direct answer is changing the firewall policy action alone does not select the distinct outbound members.
Question 255
After the authorized change to generate a filtered security or usage report with the relevant block category, user grouping and comparable time windows, which result actually demonstrates that this site's requirement is met? Initial issue: 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 output attributes the month's usage to the correct user group without mixing other periods
- The report shows blocked-event trends per cohort alongside enough traffic context to interpret the change
- The resulting report covers the incident window and contains the expected user/security information
- The retrieved dataset matches the intended bounded period and record counts
Explanation
Correct Answer
B:The report shows blocked-event trends per cohort alongside enough traffic context to interpret the change. This is stronger than a saved configuration because it tests the intended operational result. Grouping by both user and enforcement action helps separate policy behavior from raw request volume.
Incorrect Answers
A:The output attributes the month's usage to the correct user group without mixing other periods. It could be appropriate when a department asks which user cohort consumed the most bandwidth across FortiSASE Internet access this month. 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 the report shows blocked-event trends per cohort alongside enough traffic context to interpret the change.
C:The resulting report covers the incident window and contains the expected user/security information. That is a useful action for a different circumstance: during an incident bridge, analysts need a fresh one-off FortiSASE report for the last two hours, not the normal weekly summary. 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 the report shows blocked-event trends per cohort alongside enough traffic context to interpret the change.
D:The retrieved dataset matches the intended bounded period and record counts. The outcome for that step belongs to an analyst exports the currently filtered FortiSASE security-log view but expects every historical event in the tenant to appear in that export. Here the decisive requirement concerns 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, so the report shows blocked-event trends per cohort alongside enough traffic context to interpret the change is the better fit.
Question 256
Given this incident — A customer configures a new SAML identity provider, but the first user test fails due to an outdated signing certificate. — the administrator plans to update the trusted SAML signing-certificate configuration to the active identity-provider certificate. Which technical principle justifies it?
- FortiClient is the endpoint agent that steers the chosen remote traffic and receives managed connection settings
- Endpoint assignment depends on available synchronized directory membership and profile matching
- A stale signature verification key prevents valid assertions from being accepted even when users know their passwords
- Group-based authorization requires that the relevant identity-group attributes are available to the SASE policy
Explanation
Correct Answer
C:A stale signature verification key prevents valid assertions from being accepted even when users know their passwords. This is why the proposed repair addresses the reported behavior; confirm by checking: The test assertion validates and the user signs in with the expected claims.
Incorrect Answers
A:FortiClient is the endpoint agent that steers the chosen remote traffic and receives managed connection settings. The outcome for that step belongs to a workforce requires full agent-based secure Internet access with centrally controlled settings on company-managed laptops. Here the decisive requirement concerns a customer configures a new SAML identity provider, but the first user test fails due to an outdated signing certificate, so a stale signature verification key prevents valid assertions from being accepted even when users know their passwords is the better fit.
B:Endpoint assignment depends on available synchronized directory membership and profile matching. It could be appropriate when a company configures an Active Directory group for endpoint profiles, but a recently added user still receives the Default profile. However, that does not resolve the stated condition: a customer configures a new SAML identity provider, but the first user test fails due to an outdated signing certificate. A more direct answer is a stale signature verification key prevents valid assertions from being accepted even when users know their passwords.
D:Group-based authorization requires that the relevant identity-group attributes are available to the SASE policy. It addresses a company chooses LDAP as an identity source, but FortiSASE cannot apply a group-based access policy despite successful basic user lookup. In the reported environment, the missing behavior instead relates to a customer configures a new SAML identity provider, but the first user test fails due to an outdated signing certificate. The relevant choice is a stale signature verification key prevents valid assertions from being accepted even when users know their passwords.
Question 257
Given this incident — An organization plans a SASE service deployment to users in multiple countries but its security policy requires a documented processing-location decision. — the administrator plans to perform a data-residency and jurisdiction review before finalizing supported FortiSASE regions. Which technical principle justifies it?
- Service routing and jurisdictional obligations are separate from basic tunnel connectivity
- Change auditing associates security configuration actions with users and times
- Cloud PoPs apply policy on the user path, independent of the user's physical branch location
- Regional selection affects where remote users connect and where service processing may occur
Explanation
Correct Answer
A:Service routing and jurisdictional obligations are separate from basic tunnel connectivity. This is why the proposed repair addresses the reported behavior; confirm by checking: The regional configuration and its documented business/legal approval agree with required locations.
Incorrect Answers
B:Change auditing associates security configuration actions with users and times. It addresses an internal audit asks whether a just-deployed SASE policy was changed by an authorized operator during a specific window. In the reported environment, the missing behavior instead relates to an organization plans a SASE service deployment to users in multiple countries but its security policy requires a documented processing-location decision. The relevant choice is service routing and jurisdictional obligations are separate from basic tunnel connectivity.
C:Cloud PoPs apply policy on the user path, independent of the user's physical branch location. The outcome for that step belongs to 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. Here the decisive requirement concerns an organization plans a SASE service deployment to users in multiple countries but its security policy requires a documented processing-location decision, so service routing and jurisdictional obligations are separate from basic tunnel connectivity is the better fit.
D:Regional selection affects where remote users connect and where service processing may occur. That is a useful action for a different circumstance: a multinational company is activating FortiSASE and must decide which geographical security PoP regions should serve its remote employees. The present case is constrained by an organization plans a SASE service deployment to users in multiple countries but its security policy requires a documented processing-location decision; the targeted response is service routing and jurisdictional obligations are separate from basic tunnel connectivity.
Question 258
The operator wants evidence before implementing a fix. Which specific check best distinguishes the reported failure? A security policy allows a video conference service, but the steering rule built using only destination subnets matches unrelated applications at the same cloud provider.
- Inspect the traffic's identified service/application and the rule's match criteria
- Inspect the service classification in logs and the selected Internet-service rule criterion
- Inspect the matched rule ID and its priority-members list for payroll sessions
- Inspect per-member jitter and the rule's quality metric/selection status
Explanation
Correct Answer
A:Inspect the traffic's identified service/application and the rule's match criteria. The observed evidence guides the targeted repair: Use the supported application or Internet-service matching criteria for the intended conference traffic.
Incorrect Answers
B:Inspect the service classification in logs and the selected Internet-service rule criterion. It addresses an administrator expects an Internet-service destination selector to match a vendor's dynamically maintained service IPs, not an outdated manual CIDR list. In the reported environment, the missing behavior instead relates to a security policy allows a video conference service, but the steering rule built using only destination subnets matches unrelated applications at the same cloud provider. The relevant choice is inspect the traffic's identified service/application and the rule's match criteria.
C:Inspect the matched rule ID and its priority-members list for payroll sessions. The outcome for that step belongs to a helpdesk needs payroll application traffic pinned to an approved ISP while the second WAN remains available for other services. Here the decisive requirement concerns a security policy allows a video conference service, but the steering rule built using only destination subnets matches unrelated applications at the same cloud provider, so inspect the traffic's identified service/application and the rule's match criteria is the better fit.
D:Inspect per-member jitter and the rule's quality metric/selection status. 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 security policy allows a video conference service, but the steering rule built using only destination subnets matches unrelated applications at the same cloud provider; the targeted response is inspect the traffic's identified service/application and the rule's match criteria.
Question 259
At a FortiSASE/SD-WAN site, this issue is reported: 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. What is the most direct technical change to address the stated requirement?
- Use FortiSASE SPA PoP-to-FortiGate hub IPsec connectivity with specific private routing and access policies
- Configure FortiSASE secure private access through the existing SD-WAN hub using the supported connector integration
- Manage and verify the supported SD-WAN hub configuration objects through FortiManager with controlled deployment
- Validate BGP adjacency and learned private routes across the tunnel
Explanation
Correct Answer
A:Use FortiSASE SPA PoP-to-FortiGate hub IPsec connectivity with specific private routing and access policies. The overlay creates protected paths between remote SASE PoPs and hosted private networks. The configuration alone must be followed by a functioning test: The private service is accessible to authorized remote users solely via the intended secure connector path.
Incorrect Answers
B:Configure FortiSASE secure private access through the existing SD-WAN hub using the supported connector integration. It addresses a customer wants remote FortiClient users to reach a database behind an existing FortiGate SD-WAN hub rather than exposing the database publicly. 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 use FortiSASE SPA PoP-to-FortiGate hub IPsec connectivity with specific private routing and access policies.
C:Manage and verify the supported SD-WAN hub configuration objects through FortiManager with controlled deployment. That is a useful action for a different circumstance: a company uses FortiManager for its FortiGate hub configurations and wants to prevent the SASE overlay settings from drifting across multiple sites. 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 use FortiSASE SPA PoP-to-FortiGate hub IPsec connectivity with specific private routing and access policies.
D:Validate BGP adjacency and learned private routes across the tunnel. The outcome for that step belongs 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. 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 use FortiSASE SPA PoP-to-FortiGate hub IPsec connectivity with specific private routing and access policies is the better fit.
Question 260
For a change review, the team proposes to reference the intended SD-WAN zone for traffic-policy control rather than individual members when using the SD-WAN design because: 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. Which explanation connects the change to the underlying behavior?
- FortiGate logically groups SD-WAN members into zones and uses zones as policy interfaces
- The routing table must supply reachability before SD-WAN steering can select a usable member; policy alone is not a route
- Steering can choose only among configured members; simply having two interfaces with addresses does not make them SD-WAN candidates
- The firewall policy is a separate permission decision from member selection; a valid SD-WAN path does not itself allow sessions
Explanation
Correct Answer
A:FortiGate logically groups SD-WAN members into zones and uses zones as policy interfaces. This is why the proposed repair addresses the reported behavior; confirm by checking: The policy matches sessions sent through either eligible member of its designated zone.
Incorrect Answers
B:The routing table must supply reachability before SD-WAN steering can select a usable member; policy alone is not a route. 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 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 fortiGate logically groups SD-WAN members into zones and uses zones as policy interfaces.
C:Steering can choose only among configured members; simply having two interfaces with addresses does not make them SD-WAN candidates. That is a useful action for a different circumstance: a new branch has two internet circuits configured as ordinary FortiGate interfaces, but no SD-WAN members exist; the owner wants policy-based path steering. 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 fortiGate logically groups SD-WAN members into zones and uses zones as policy interfaces.
D:The firewall policy is a separate permission decision from member selection; a valid SD-WAN path does not itself allow sessions. The outcome for that step belongs to a newly installed branch has healthy ISP links and an SD-WAN zone, yet LAN clients cannot browse because the existing allow policy targets only a former WAN interface. Here the decisive requirement concerns 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, so fortiGate logically groups SD-WAN members into zones and uses zones as policy interfaces is the better fit.
Fortinet NSE 5 - FortiSASE and SD-WAN 7.6 Core Administrator (NSE5_SSE_AD-7.6) Practice Tests