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.
Question 261
At a FortiSASE/SD-WAN site, this issue is reported: Two WAN interfaces show up, but the network manager needs continuous health information even when no users are active. What is the most direct technical change to address the stated requirement?
- Configure an active performance SLA with a reachable probe server on both members
- Use Lowest Cost (SLA) steering with relevant performance targets and appropriate member costs
- Configure a latency target in the performance SLA and bind it to the call-center rule
- Distinguish link availability from SLA compliance and review the rule's qualifying-member selection
Explanation
Correct Answer
A:Configure an active performance SLA with a reachable probe server on both members. Active probes create measurement traffic independently of client session demand. The configuration alone must be followed by a functioning test: The monitored members report latency, loss and jitter while the branch is idle.
Incorrect Answers
B:Use Lowest Cost (SLA) steering with relevant performance targets and appropriate member costs. The outcome for that step belongs to a finance department wants lower monthly WAN costs but only from links that satisfy latency and jitter requirements. Here the decisive requirement concerns two WAN interfaces show up, but the network manager needs continuous health information even when no users are active, so configure an active performance SLA with a reachable probe server on both members is the better fit.
C:Configure a latency target in the performance SLA and bind it to the call-center rule. That is a useful action for a different circumstance: a call-center SLA must avoid any WAN link whose one-way delay is above an agreed threshold. The present case is constrained by two WAN interfaces show up, but the network manager needs continuous health information even when no users are active; the targeted response is configure an active performance SLA with a reachable probe server on both members.
D:Distinguish link availability from SLA compliance and review the rule's qualifying-member selection. It addresses an SD-WAN operator sees a link marked alive but the performance SLA map shows it misses the configured voice target. In the reported environment, the missing behavior instead relates to two WAN interfaces show up, but the network manager needs continuous health information even when no users are active. The relevant choice is configure an active performance SLA with a reachable probe server on both members.
Question 262
For the stated scenario, what is the most important remaining blind spot after the proposed correction? A security team needs to determine whether a remote user's web traffic actually traverses a FortiSASE enforcement point rather than exiting locally.
- Correct BGP prefixes cannot traverse a tunnel that never establishes
- An Internet-only SWG proxy is not equivalent to routed private UDP application access
- Expanding a broad any-to-any rule would unnecessarily widen application access
- Successful login to the admin portal does not prove an endpoint's application traffic is steered to a PoP
Explanation
Correct Answer
D:Successful login to the admin portal does not prove an endpoint's application traffic is steered to a PoP. The planned change can still miss the requirement if this condition is left unresolved. The PoP is where the cloud-delivered access policy evaluates the relevant traffic flow.
Incorrect Answers
A:Correct BGP prefixes cannot traverse a tunnel that never establishes. That is a useful action for a different circumstance: fortiSASE private-access connector is configured but no IPsec security association is established between the SASE PoP and the FortiGate hub. The present case is constrained by a security team needs to determine whether a remote user's web traffic actually traverses a FortiSASE enforcement point rather than exiting locally; the targeted response is successful login to the admin portal does not prove an endpoint's application traffic is steered to a PoP.
B:An Internet-only SWG proxy is not equivalent to routed private UDP application access. It addresses an organization needs private TCP and UDP access to multiple office services without publishing public listener ports. In the reported environment, the missing behavior instead relates to a security team needs to determine whether a remote user's web traffic actually traverses a FortiSASE enforcement point rather than exiting locally. The relevant choice is successful login to the admin portal does not prove an endpoint's application traffic is steered to a PoP.
C:Expanding a broad any-to-any rule would unnecessarily widen application access. It could be appropriate when a private application behind the hub is routed correctly, but the security gateway denies the remote SASE user's source subnet. However, that does not resolve the stated condition: a security team needs to determine whether a remote user's web traffic actually traverses a FortiSASE enforcement point rather than exiting locally. A more direct answer is successful login to the admin portal does not prove an endpoint's application traffic is steered to a PoP.
Question 263
A proposed repair is to verify and apply the required FortiSASE license entitlement for the selected deployment before enabling the features. Why should that repair work in this particular situation? Context: A SASE tenant is ready for configuration but the administrator cannot activate the intended service functions under the current subscription.
- Available subscription entitlements constrain which managed SASE services can be deployed
- Least-privilege administrative roles separate day-to-day visibility from high-impact tenant changes
- Service routing and jurisdictional obligations are separate from basic tunnel connectivity
- FortiManager can centrally synchronize selected object types with FortiSASE where integration is configured
Explanation
Correct Answer
A:Available subscription entitlements constrain which managed SASE services can be deployed. This is why the proposed repair addresses the reported behavior; confirm by checking: The appropriate capability is visible and usable after entitlement verification and provisioning.
Incorrect Answers
B:Least-privilege administrative roles separate day-to-day visibility from high-impact tenant changes. That is a useful action for a different circumstance: a company needs administrators to troubleshoot access policies without allowing every operator to change identity sources or global settings. The present case is constrained by a SASE tenant is ready for configuration but the administrator cannot activate the intended service functions under the current subscription; the targeted response is available subscription entitlements constrain which managed SASE services can be deployed.
C: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 a SASE tenant is ready for configuration but the administrator cannot activate the intended service functions under the current subscription. The relevant choice is available subscription entitlements constrain which managed SASE services can be deployed.
D:FortiManager can centrally synchronize selected object types with FortiSASE where integration is configured. The outcome for that step belongs to a central network management program wants address groups and security profile groups shared between on-premise FortiGate and the FortiSASE tenant. Here the decisive requirement concerns a SASE tenant is ready for configuration but the administrator cannot activate the intended service functions under the current subscription, so available subscription entitlements constrain which managed SASE services can be deployed is the better fit.
Question 264
During readiness review, which case-specific risk must the team still rule out before declaring this change successful? A WAN circuit changes its upstream gateway through DHCP; an old static next hop still refers to the former router.
- A static rule definition alone cannot show the dynamic decision made for an affected session
- Lowest Cost (SLA) mode could prefer a cheaper merely compliant path rather than the best jitter
- Best-quality steering may prefer a single superior path rather than share load
- Changing a security profile cannot resolve an unreachable WAN gateway
Explanation
Correct Answer
D:Changing a security profile cannot resolve an unreachable WAN gateway. The planned change can still miss the requirement if this condition is left unresolved. A usable member requires a valid layer-3 next hop, not just a physically active interface.
Incorrect Answers
A:A static rule definition alone cannot show the dynamic decision made for an affected session. That is a useful action for a different circumstance: an IT team monitors a policy's configuration text but still cannot explain why a selected member changed during a short quality incident. The present case is constrained by a WAN circuit changes its upstream gateway through DHCP; an old static next hop still refers to the former router; the targeted response is changing a security profile cannot resolve an unreachable WAN gateway.
B: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: a WAN circuit changes its upstream gateway through DHCP; an old static next hop still refers to the former router. A more direct answer is changing a security profile cannot resolve an unreachable WAN gateway.
C:Best-quality steering may prefer a single superior path rather than share load. 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 a WAN circuit changes its upstream gateway through DHCP; an old static next hop still refers to the former router. The relevant choice is changing a security profile cannot resolve an unreachable WAN gateway.
Question 265
During readiness review, which case-specific risk must the team still rule out before declaring this change successful? A bank requires private site-to-site application access through its FortiGate SD-WAN hub, while local Internet traffic should exit each branch directly.
- Keeping both members in one shared zone prevents policy separation solely by member identity
- A live tunnel without matching routes or permitted firewall policy does not establish private application reachability
- Passive measurement may be uninformative for an idle site and should not be assumed equivalent to active probing
- A static route pointing to a zone does not automatically populate that zone with members
Explanation
Correct Answer
B:A live tunnel without matching routes or permitted firewall policy does not establish private application reachability. The planned change can still miss the requirement if this condition is left unresolved. SD-WAN can distinguish overlay and underlay transport and steer traffic based on intended destination and policy.
Incorrect Answers
A:Keeping both members in one shared zone prevents policy separation solely by member identity. That is a useful action for a different circumstance: a branch combines broadband and private MPLS, but private traffic requires a different firewall inspection policy from public Internet traffic. The present case is constrained by 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 targeted response is a live tunnel without matching routes or permitted firewall policy does not establish private application reachability.
C:Passive measurement may be uninformative for an idle site and should not be assumed equivalent to active probing. 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 bank requires private site-to-site application access through its FortiGate SD-WAN hub, while local Internet traffic should exit each branch directly, so a live tunnel without matching routes or permitted firewall policy does not establish private application reachability is the better fit.
D:A static route pointing to a zone does not automatically populate that zone with members. It could be appropriate when a FortiGate administrator can see a new virtual-wan-link zone but cannot find the new ISP as an eligible steering member. However, that does not resolve the stated condition: a bank requires private site-to-site application access through its FortiGate SD-WAN hub, while local Internet traffic should exit each branch directly. A more direct answer is a live tunnel without matching routes or permitted firewall policy does not establish private application reachability.
Question 266
An acceptance test is needed after the change. Which measured outcome best confirms the described Fortinet issue has been resolved? A branch switches to a new ISP and forgets to update the static route's gateway, causing repeated probe failures on that member.
- Private application traffic enters the tunnel and unrelated Internet traffic uses the WAN
- The repaired member is both routed and SLA-qualified when its measured performance meets the target
- The corrected interface reaches its first hop and the remote SLA server
- Fresh connections successfully establish through the chosen ISP's correct translated source
Explanation
Correct Answer
C:The corrected interface reaches its first hop and the remote SLA server. It demonstrates that the intended path or control is actually working, not merely configured.
Incorrect Answers
A:Private application traffic enters the tunnel and unrelated Internet traffic uses the WAN. It could be appropriate when a branch traffic policy should use one ISP for public destinations but a private tunnel for an RFC1918 destination. 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 the corrected interface reaches its first hop and the remote SLA server.
B:The repaired member is both routed and SLA-qualified when its measured performance meets the target. The outcome for that step belongs to an administrator configured two redundant WAN routes but an SD-WAN service reports one member unavailable because its required SLA is failing. 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 the corrected interface reaches its first hop and the remote SLA server is the better fit.
D:Fresh connections successfully establish through the chosen ISP's correct translated source. It addresses a NATed application stops after switching from ISP1 to ISP2 because the upstream sees a different public source address. In the reported environment, the missing behavior instead relates to a branch switches to a new ISP and forgets to update the static route's gateway, causing repeated probe failures on that member. The relevant choice is the corrected interface reaches its first hop and the remote SLA server.
Question 267
The team plans to provision the contractor using an agentless Internet proxy policy and omit unrelated private-access grants for the situation below. Which remaining implementation pitfall is directly relevant to this same requirement? A temporary contractor should use the secure web gateway but must not be able to reach private network IP ranges via a full tunnel.
- Successful SWG authentication is not proof that private-access privileges are safely absent unless policy scope is reviewed
- Editing the default profile group globally may unintentionally affect users outside the chosen cohort
- Changing an unrelated security inspection profile does not solve geographical path selection
- An Internet-only SWG proxy is not equivalent to routed private UDP application access
Explanation
Correct Answer
A:Successful SWG authentication is not proof that private-access privileges are safely absent unless policy scope is reviewed. This is an implementation boundary for the proposed fix, so the deployment needs a specific follow-up check.
Incorrect Answers
B:Editing the default profile group globally may unintentionally affect users outside the chosen cohort. 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 a temporary contractor should use the secure web gateway but must not be able to reach private network IP ranges via a full tunnel, so successful SWG authentication is not proof that private-access privileges are safely absent unless policy scope is reviewed is the better fit.
C:Changing an unrelated security inspection profile does not solve geographical path selection. That is a useful action for a different circumstance: the SASE team receives reports that remote users in one region have unusually long service round trips despite healthy home broadband. The present case is constrained by a temporary contractor should use the secure web gateway but must not be able to reach private network IP ranges via a full tunnel; the targeted response is successful SWG authentication is not proof that private-access privileges are safely absent unless policy scope is reviewed.
D:An Internet-only SWG proxy is not equivalent to routed private UDP application access. It addresses an organization needs private TCP and UDP access to multiple office services without publishing public listener ports. In the reported environment, the missing behavior instead relates 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. The relevant choice is successful SWG authentication is not proof that private-access privileges are safely absent unless policy scope is reviewed.
Question 268
During implementation, the administrator observes: A retailer wants its LTE backup circuit to be used sparingly while broadband remains usable; LTE billing is metered. Which intervention targets the described fault rather than an adjacent workflow?
- Separate Internet destinations and private prefixes using explicit routing and steering decisions
- Use FortiGate SD-WAN health and member monitoring widgets after member and SLA configuration
- Use a steering policy with preferred primary member and health-based failover to LTE, rather than unrestricted equal sharing
- Apply the required security profiles to the matching allow firewall policy independently of SD-WAN member setup
Explanation
Correct Answer
C:Use a steering policy with preferred primary member and health-based failover to LTE, rather than unrestricted equal sharing. Member preference combined with failure detection limits routine use of a metered backup path. The configuration alone must be followed by a functioning test: Normal traffic uses broadband, but simulated broadband failure makes new eligible flows use LTE.
Incorrect Answers
A:Separate Internet destinations and private prefixes using explicit routing and steering decisions. It could be appropriate when a branch uses public DIA for cloud apps but should keep existing on-prem application routing through its corporate overlay. However, that does not resolve the stated condition: a retailer wants its LTE backup circuit to be used sparingly while broadband remains usable; LTE billing is metered. A more direct answer is use a steering policy with preferred primary member and health-based failover to LTE, rather than unrestricted equal sharing.
B:Use FortiGate SD-WAN health and member monitoring widgets after member and SLA configuration. The outcome for that step belongs to a new deployment has two ISP connections but operators cannot compare their real-time health from the ordinary interface inventory. Here the decisive requirement concerns a retailer wants its LTE backup circuit to be used sparingly while broadband remains usable; LTE billing is metered, so use a steering policy with preferred primary member and health-based failover to LTE, rather than unrestricted equal sharing is the better fit.
D:Apply the required security profiles to the matching allow firewall policy independently of SD-WAN member setup. It addresses a branch was built with two SD-WAN members, but a team assumes this alone automatically adds application inspection to client sessions. In the reported environment, the missing behavior instead relates to a retailer wants its LTE backup circuit to be used sparingly while broadband remains usable; LTE billing is metered. The relevant choice is use a steering policy with preferred primary member and health-based failover to LTE, rather than unrestricted equal sharing.
Question 269
For this Fortinet incident, which observation should the engineer collect first to validate the suspected condition? An analyst exports the currently filtered FortiSASE security-log view but expects every historical event in the tenant to appear in that export.
- Inspect report template, recurrence and recipient configuration
- Inspect log-forwarding destination, connection status and event receipt in the external system
- Inspect report category, action filters, group attribution and period lengths
- Inspect active filters, date limits and the export's documented entry scope
Explanation
Correct Answer
D:Inspect active filters, date limits and the export's documented entry scope. This check isolates the relevant control before the change. The current visible-log export reflects selected entries rather than an unlimited historical dataset.
Incorrect Answers
A:Inspect report template, recurrence and recipient configuration. That is a useful action for a different circumstance: the compliance manager needs the same user-traffic report delivered every Monday without an operator manually rerunning it. The present case is constrained by an analyst exports the currently filtered FortiSASE security-log view but expects every historical event in the tenant to appear in that export; the targeted response is inspect active filters, date limits and the export's documented entry scope.
B:Inspect log-forwarding destination, connection status and event receipt in the external system. 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 an analyst exports the currently filtered FortiSASE security-log view but expects every historical event in the tenant to appear in that export. The relevant choice is inspect active filters, date limits and the export's documented entry scope.
C:Inspect report category, action filters, group attribution and period lengths. It could be appropriate when 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. However, that does not resolve the stated condition: an analyst exports the currently filtered FortiSASE security-log view but expects every historical event in the tenant to appear in that export. A more direct answer is inspect active filters, date limits and the export's documented entry scope.
Question 270
Before changing the configuration, the team needs to isolate the problem. Which diagnostic check is most targeted here? Incident: A remote employee reaches the hub over IPsec, but an internal firewall policy forwards a server reply through a different, untracked WAN path.
- Inspect routing for both source and return destinations and the denied or asymmetric session entries
- Inspect BGP neighbor state and the expected route in the routing table
- Inspect BGP peering and the hub/PoP routing tables for the specific destination prefix
- Inspect IKE negotiation, peer reachability and IPsec tunnel status
Explanation
Correct Answer
A:Inspect routing for both source and return destinations and the denied or asymmetric session entries. The observed evidence guides the targeted repair: Correct return-path routing and stateful policy consistency for private applications over SPA.
Incorrect Answers
B:Inspect BGP neighbor state and the expected route in the routing table. 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 remote employee reaches the hub over IPsec, but an internal firewall policy forwards a server reply through a different, untracked WAN path, so inspect routing for both source and return destinations and the denied or asymmetric session entries is the better fit.
C:Inspect BGP peering and the hub/PoP routing tables for the specific destination prefix. It addresses the FortiSASE SPA IPsec tunnel is up, but remote users cannot reach private prefixes behind the FortiGate hub. In the reported environment, the missing behavior instead relates to a remote employee reaches the hub over IPsec, but an internal firewall policy forwards a server reply through a different, untracked WAN path. The relevant choice is inspect routing for both source and return destinations and the denied or asymmetric session entries.
D:Inspect IKE negotiation, peer reachability and IPsec tunnel status. That is a useful action for a different circumstance: fortiSASE private-access connector is configured but no IPsec security association is established between the SASE PoP and the FortiGate hub. 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 inspect routing for both source and return destinations and the denied or asymmetric session entries.
Fortinet NSE 5 - FortiSASE and SD-WAN 7.6 Core Administrator (NSE5_SSE_AD-7.6) Practice Tests