Question 290
In a deployment where a network has healthy SD-WAN members but no default path out of the branch, the team plans to: Install the required static route toward the SD-WAN zone. Which condition must be established for the chosen implementation to work as described?
- Confirm the matching route map and SD-WAN rule address-family scope
- Ensure the zone and interfaces exist before route creation
- Ensure the overlay routes can transport traffic to the loopbacks
- Confirm the tunnel and WAN underlay support IP reachability
Explanation
Correct Answer
B:Ensure the zone and interfaces exist before route creation. This is the enabling condition for install the required static route toward the SD-WAN zone. Without that prerequisite, the expected operational evidence may not appear: inspect the forwarding table for a usable default route through the SD-WAN interface. the documented recovery path is to restore routing before weakening performance SLA thresholds.
Incorrect Answers
A:Confirm the matching route map and SD-WAN rule address-family scope is relevant when the organization must use the supported IPv4 or IPv6 route-tag matching for the relevant address family. Here the prerequisite instead concerns install the required static route toward the SD-WAN zone, so that different condition would not establish the necessary setup for the stated deployment.
C:Ensure the overlay routes can transport traffic to the loopbacks is relevant when the organization must establish BGP peering to reachable loopback addresses rather than per-underlay interface addresses. Here the prerequisite instead concerns install the required static route toward the SD-WAN zone, so that different condition would not establish the necessary setup for the stated deployment.
D:Confirm the tunnel and WAN underlay support IP reachability is relevant when the organization must add the required transport route for the loopback through the IPsec overlay. Here the prerequisite instead concerns install the required static route toward the SD-WAN zone, so that different condition would not establish the necessary setup for the stated deployment.
Question 291
A team implemented this choice for a customer: Install the required static route toward the SD-WAN zone. The requirement was: a network has healthy SD-WAN members but no default path out of the branch. Which observable result most directly demonstrates that the chosen implementation has achieved its intended behavior?
- Inspect the forwarding table for a usable default route through the SD-WAN interface
- Inspect route origin, tag, and matching service rule
- Test loopback reachability separately from the LAN prefix exchange
- Compare actual neighbor sessions against the planned loopback topology
Explanation
Correct Answer
A:Inspect the forwarding table for a usable default route through the SD-WAN interface. It is the specific operational evidence for the requirement that a network has healthy SD-WAN members but no default path out of the branch. Selecting the design action alone does not prove completion without this observed result.
Incorrect Answers
B:Inspect route origin, tag, and matching service rule would be meaningful evidence when attempting to apply route tags through the appropriate routing process rather than assuming all static routes inherit BGP communities. It does not directly demonstrate whether inspect the forwarding table for a usable default route through the SD-WAN interface, which is the stated acceptance result for this Fortinet deployment.
C:Test loopback reachability separately from the LAN prefix exchange would be meaningful evidence when attempting to add the required transport route for the loopback through the IPsec overlay. It does not directly demonstrate whether inspect the forwarding table for a usable default route through the SD-WAN interface, which is the stated acceptance result for this Fortinet deployment.
D:Compare actual neighbor sessions against the planned loopback topology would be meaningful evidence when attempting to use the BGP-on-loopback architecture instead of one BGP peering per IPsec overlay. It does not directly demonstrate whether inspect the forwarding table for a usable default route through the SD-WAN interface, which is the stated acceptance result for this Fortinet deployment.
Question 292
A Fortinet team is working on this situation: a network has healthy SD-WAN members but no default path out of the branch. It attempted: Install the required static route toward the SD-WAN zone. Expected evidence (Inspect the forwarding table for a usable default route through the SD-WAN interface) is still absent. Which corrective step most directly addresses the unsuccessful verification before unrelated configuration is changed?
- Restore the second hub's overlay and routing eligibility before pinning sessions to the dead hub
- Correct loopback reachability before creating additional per-tunnel neighbors
- Fix community-list or route-map binding when advertised routes lack the local tag
- Restore routing before weakening performance SLA thresholds
Explanation
Correct Answer
D:Restore routing before weakening performance SLA thresholds. The missing evidence (inspect the forwarding table for a usable default route through the SD-WAN interface) points to a problem with the implementation of install the required static route toward the SD-WAN zone. It is the correction specific to that missing operational result rather than a broad relaxation of security policy.
Incorrect Answers
A:Restore the second hub's overlay and routing eligibility before pinning sessions to the dead hub addresses a different operational issue: a dual-hub fabric must recover from loss of the first datacenter. This situation calls for restore routing before weakening performance SLA thresholds because the missing result relates to inspect the forwarding table for a usable default route through the SD-WAN interface.
B:Correct loopback reachability before creating additional per-tunnel neighbors addresses a different operational issue: two hubs share a stable BGP loopback while physical overlays can change. This situation calls for restore routing before weakening performance SLA thresholds because the missing result relates to inspect the forwarding table for a usable default route through the SD-WAN interface.
C:Fix community-list or route-map binding when advertised routes lack the local tag addresses a different operational issue: an ISP advertises application prefixes using a well-known BGP community. This situation calls for restore routing before weakening performance SLA thresholds because the missing result relates to inspect the forwarding table for a usable default route through the SD-WAN interface.
Question 293
An architect is preparing a Fortinet FortiSASE 26 / FortiOS 7.6 design. A site wants different filtering for internet access versus private datacenter overlays. Which design or implementation decision best meets the stated requirement?
- Apply route tags through the appropriate routing process rather than assuming all static routes inherit BGP communities
- Use separate SD-WAN zones and distinct zone-referenced security profiles
- Diagnose transport to the BGP loopback address via surviving overlays
- Use the BGP-on-loopback architecture instead of one BGP peering per IPsec overlay
Explanation
Correct Answer
B:Use separate SD-WAN zones and distinct zone-referenced security profiles. This addresses the stated requirement: a site wants different filtering for internet access versus private datacenter overlays. The deployment must satisfy the accompanying requirement (Confirm each application is mapped to the correct trust-boundary zone); the engineer can then validate the result by performing this check: verify firewall-policy and security profile selection for both paths.
Incorrect Answers
A:Apply route tags through the appropriate routing process rather than assuming all static routes inherit BGP communities is a legitimate choice for another type of situation: a team attempts to use BGP tags for static routes that have no community processing. The alternative design first requires the team to confirm the relevant route is BGP-learned and processed by the route map, but it does not directly implement the specified requirement to use separate SD-WAN zones and distinct zone-referenced security profiles.
C:Diagnose transport to the BGP loopback address via surviving overlays is a legitimate choice for another type of situation: a branch loses a physical WAN but still sees BGP peering down despite a healthy overlay. The alternative design first requires the team to check that viable underlay and IPsec routes continue to reach the loopback, but it does not directly implement the specified requirement to use separate SD-WAN zones and distinct zone-referenced security profiles.
D:Use the BGP-on-loopback architecture instead of one BGP peering per IPsec overlay is a legitimate choice for another type of situation: an engineering team wants to reduce BGP neighbor count in many parallel overlays. The alternative design first requires the team to ensure loopback address stability and routing across active underlays, but it does not directly implement the specified requirement to use separate SD-WAN zones and distinct zone-referenced security profiles.
Question 294
In a deployment where a site wants different filtering for internet access versus private datacenter overlays, the team plans to: Use separate SD-WAN zones and distinct zone-referenced security profiles. Which condition must be established for the chosen implementation to work as described?
- Confirm the tunnel and WAN underlay support IP reachability
- Configure the community list and inbound route map to set the route tag
- Confirm each application is mapped to the correct trust-boundary zone
- Ensure the inbound route map is applied to the correct BGP neighbor
Explanation
Correct Answer
C:Confirm each application is mapped to the correct trust-boundary zone. This is the enabling condition for use separate SD-WAN zones and distinct zone-referenced security profiles. Without that prerequisite, the expected operational evidence may not appear: verify firewall-policy and security profile selection for both paths. the documented recovery path is to repair misclassified zone membership rather than replacing the entire overlay template.
Incorrect Answers
A:Confirm the tunnel and WAN underlay support IP reachability is relevant when the organization must add the required transport route for the loopback through the IPsec overlay. Here the prerequisite instead concerns use separate SD-WAN zones and distinct zone-referenced security profiles, so that different condition would not establish the necessary setup for the stated deployment.
B:Configure the community list and inbound route map to set the route tag is relevant when the organization must match SD-WAN destination using a BGP-derived route tag rather than a stale static address list. Here the prerequisite instead concerns use separate SD-WAN zones and distinct zone-referenced security profiles, so that different condition would not establish the necessary setup for the stated deployment.
D:Ensure the inbound route map is applied to the correct BGP neighbor is relevant when the organization must translate the matched community into the intended FortiOS route tag. Here the prerequisite instead concerns use separate SD-WAN zones and distinct zone-referenced security profiles, so that different condition would not establish the necessary setup for the stated deployment.
Question 295
A team implemented this choice for a customer: Use separate SD-WAN zones and distinct zone-referenced security profiles. The requirement was: a site wants different filtering for internet access versus private datacenter overlays. Which observable result most directly demonstrates that the chosen implementation has achieved its intended behavior?
- Verify firewall-policy and security profile selection for both paths
- Inspect route origin, tag, and matching service rule
- Inspect branch route changes when the first hub is unavailable
- Inspect tag presence on the intended IPv4 or IPv6 route
Explanation
Correct Answer
A:Verify firewall-policy and security profile selection for both paths. It is the specific operational evidence for the requirement that a site wants different filtering for internet access versus private datacenter overlays. Selecting the design action alone does not prove completion without this observed result.
Incorrect Answers
B:Inspect route origin, tag, and matching service rule would be meaningful evidence when attempting to apply route tags through the appropriate routing process rather than assuming all static routes inherit BGP communities. It does not directly demonstrate whether verify firewall-policy and security profile selection for both paths, which is the stated acceptance result for this Fortinet deployment.
C:Inspect branch route changes when the first hub is unavailable would be meaningful evidence when attempting to plan BGP routing and overlay paths toward both hubs. It does not directly demonstrate whether verify firewall-policy and security profile selection for both paths, which is the stated acceptance result for this Fortinet deployment.
D:Inspect tag presence on the intended IPv4 or IPv6 route would be meaningful evidence when attempting to use the supported IPv4 or IPv6 route-tag matching for the relevant address family. It does not directly demonstrate whether verify firewall-policy and security profile selection for both paths, which is the stated acceptance result for this Fortinet deployment.
Question 296
A Fortinet team is working on this situation: a site wants different filtering for internet access versus private datacenter overlays. It attempted: Use separate SD-WAN zones and distinct zone-referenced security profiles. Expected evidence (Verify firewall-policy and security profile selection for both paths) is still absent. Which corrective step most directly addresses the unsuccessful verification before unrelated configuration is changed?
- Remove accidental per-overlay sessions after loopback peering is correctly established
- Restore the second hub's overlay and routing eligibility before pinning sessions to the dead hub
- Fix a mismatched address-family rule rather than copying an IPv4-only match to IPv6
- Repair misclassified zone membership rather than replacing the entire overlay template
Explanation
Correct Answer
D:Repair misclassified zone membership rather than replacing the entire overlay template. The missing evidence (verify firewall-policy and security profile selection for both paths) points to a problem with the implementation of use separate SD-WAN zones and distinct zone-referenced security profiles. It is the correction specific to that missing operational result rather than a broad relaxation of security policy.
Incorrect Answers
A:Remove accidental per-overlay sessions after loopback peering is correctly established addresses a different operational issue: an engineering team wants to reduce BGP neighbor count in many parallel overlays. This situation calls for repair misclassified zone membership rather than replacing the entire overlay template because the missing result relates to verify firewall-policy and security profile selection for both paths.
B:Restore the second hub's overlay and routing eligibility before pinning sessions to the dead hub addresses a different operational issue: a dual-hub fabric must recover from loss of the first datacenter. This situation calls for repair misclassified zone membership rather than replacing the entire overlay template because the missing result relates to verify firewall-policy and security profile selection for both paths.
C:Fix a mismatched address-family rule rather than copying an IPv4-only match to IPv6 addresses a different operational issue: a branch supports both IPv4 and IPv6 BGP destinations with dynamic steering requirements. This situation calls for repair misclassified zone membership rather than replacing the entire overlay template because the missing result relates to verify firewall-policy and security profile selection for both paths.
Question 297
An architect is preparing a Fortinet FortiSASE 26 / FortiOS 7.6 design. A branch SD-WAN rule matches a service but the firewall denies its traffic. Which design or implementation decision best meets the stated requirement?
- Match SD-WAN destination using a BGP-derived route tag rather than a stale static address list
- Use the supported IPv4 or IPv6 route-tag matching for the relevant address family
- Evaluate the zone-referenced firewall policy independently from the SD-WAN steering rule
- Reuse route-tag-based dynamic destination matching for the new BGP-learned prefix
Explanation
Correct Answer
C:Evaluate the zone-referenced firewall policy independently from the SD-WAN steering rule. This addresses the stated requirement: a branch SD-WAN rule matches a service but the firewall denies its traffic. The deployment must satisfy the accompanying requirement (Ensure the requested source/destination and security policy allow that session); the engineer can then validate the result by performing this check: inspect policy deny logs rather than assuming route selection grants access.
Incorrect Answers
A:Match SD-WAN destination using a BGP-derived route tag rather than a stale static address list is a legitimate choice for another type of situation: a datacenter dynamically advertises many changing subnets through BGP. The alternative design first requires the team to configure the community list and inbound route map to set the route tag, but it does not directly implement the specified requirement to evaluate the zone-referenced firewall policy independently from the SD-WAN steering rule.
B:Use the supported IPv4 or IPv6 route-tag matching for the relevant address family is a legitimate choice for another type of situation: a branch supports both IPv4 and IPv6 BGP destinations with dynamic steering requirements. The alternative design first requires the team to confirm the matching route map and SD-WAN rule address-family scope, but it does not directly implement the specified requirement to evaluate the zone-referenced firewall policy independently from the SD-WAN steering rule.
D:Reuse route-tag-based dynamic destination matching for the new BGP-learned prefix is a legitimate choice for another type of situation: a business adds a new private network prefix without changing SD-WAN policies. The alternative design first requires the team to ensure the prefix is received with the matching community, but it does not directly implement the specified requirement to evaluate the zone-referenced firewall policy independently from the SD-WAN steering rule.
Question 298
In a deployment where a branch SD-WAN rule matches a service but the firewall denies its traffic, the team plans to: Evaluate the zone-referenced firewall policy independently from the SD-WAN steering rule. Which condition must be established for the chosen implementation to work as described?
- Ensure loopback address stability and routing across active underlays
- Ensure the prefix is received with the matching community
- Verify both hubs have compatible peer and route advertisement configuration
- Ensure the requested source/destination and security policy allow that session
Explanation
Correct Answer
D:Ensure the requested source/destination and security policy allow that session. This is the enabling condition for evaluate the zone-referenced firewall policy independently from the SD-WAN steering rule. Without that prerequisite, the expected operational evidence may not appear: inspect policy deny logs rather than assuming route selection grants access. the documented recovery path is to correct the firewall permission while preserving the intended SD-WAN steering decision.
Incorrect Answers
A:Ensure loopback address stability and routing across active underlays is relevant when the organization must use the BGP-on-loopback architecture instead of one BGP peering per IPsec overlay. Here the prerequisite instead concerns evaluate the zone-referenced firewall policy independently from the SD-WAN steering rule, so that different condition would not establish the necessary setup for the stated deployment.
B:Ensure the prefix is received with the matching community is relevant when the organization must reuse route-tag-based dynamic destination matching for the new BGP-learned prefix. Here the prerequisite instead concerns evaluate the zone-referenced firewall policy independently from the SD-WAN steering rule, so that different condition would not establish the necessary setup for the stated deployment.
C:Verify both hubs have compatible peer and route advertisement configuration is relevant when the organization must plan BGP routing and overlay paths toward both hubs. Here the prerequisite instead concerns evaluate the zone-referenced firewall policy independently from the SD-WAN steering rule, so that different condition would not establish the necessary setup for the stated deployment.
Question 299
A team implemented this choice for a customer: Evaluate the zone-referenced firewall policy independently from the SD-WAN steering rule. The requirement was: a branch SD-WAN rule matches a service but the firewall denies its traffic. Which observable result most directly demonstrates that the chosen implementation has achieved its intended behavior?
- Verify routes carry the FortiOS tag used by the SD-WAN rule
- Inspect policy deny logs rather than assuming route selection grants access
- Inspect branch route changes when the first hub is unavailable
- Check the new route has the expected tag and is eligible for steering
Explanation
Correct Answer
B:Inspect policy deny logs rather than assuming route selection grants access. It is the specific operational evidence for the requirement that a branch SD-WAN rule matches a service but the firewall denies its traffic. Selecting the design action alone does not prove completion without this observed result.
Incorrect Answers
A:Verify routes carry the FortiOS tag used by the SD-WAN rule would be meaningful evidence when attempting to translate the matched community into the intended FortiOS route tag. It does not directly demonstrate whether inspect policy deny logs rather than assuming route selection grants access, which is the stated acceptance result for this Fortinet deployment.
C:Inspect branch route changes when the first hub is unavailable would be meaningful evidence when attempting to plan BGP routing and overlay paths toward both hubs. It does not directly demonstrate whether inspect policy deny logs rather than assuming route selection grants access, which is the stated acceptance result for this Fortinet deployment.
D:Check the new route has the expected tag and is eligible for steering would be meaningful evidence when attempting to reuse route-tag-based dynamic destination matching for the new BGP-learned prefix. It does not directly demonstrate whether inspect policy deny logs rather than assuming route selection grants access, which is the stated acceptance result for this Fortinet deployment.
Question 300
A Fortinet team is working on this situation: a branch SD-WAN rule matches a service but the firewall denies its traffic. It attempted: Evaluate the zone-referenced firewall policy independently from the SD-WAN steering rule. Expected evidence (Inspect policy deny logs rather than assuming route selection grants access) is still absent. Which corrective step most directly addresses the unsuccessful verification before unrelated configuration is changed?
- Correct the firewall permission while preserving the intended SD-WAN steering decision
- Remove accidental per-overlay sessions after loopback peering is correctly established
- Restore the second hub's overlay and routing eligibility before pinning sessions to the dead hub
- Correct loopback reachability before creating additional per-tunnel neighbors
Explanation
Correct Answer
A:Correct the firewall permission while preserving the intended SD-WAN steering decision. The missing evidence (inspect policy deny logs rather than assuming route selection grants access) points to a problem with the implementation of evaluate the zone-referenced firewall policy independently from the SD-WAN steering rule. It is the correction specific to that missing operational result rather than a broad relaxation of security policy.
Incorrect Answers
B:Remove accidental per-overlay sessions after loopback peering is correctly established addresses a different operational issue: an engineering team wants to reduce BGP neighbor count in many parallel overlays. This situation calls for correct the firewall permission while preserving the intended SD-WAN steering decision because the missing result relates to inspect policy deny logs rather than assuming route selection grants access.
C:Restore the second hub's overlay and routing eligibility before pinning sessions to the dead hub addresses a different operational issue: a dual-hub fabric must recover from loss of the first datacenter. This situation calls for correct the firewall permission while preserving the intended SD-WAN steering decision because the missing result relates to inspect policy deny logs rather than assuming route selection grants access.
D:Correct loopback reachability before creating additional per-tunnel neighbors addresses a different operational issue: two hubs share a stable BGP loopback while physical overlays can change. This situation calls for correct the firewall permission while preserving the intended SD-WAN steering decision because the missing result relates to inspect policy deny logs rather than assuming route selection grants access.
Fortinet NSE 7 - FortiSASE 26 Architect (NSE7_SSE_AR-26) Practice Tests