Question 190
In a deployment where a business adds a new private network prefix without changing SD-WAN policies, the team plans to: Reuse route-tag-based dynamic destination matching for the new BGP-learned prefix. Which condition must be established for the chosen implementation to work as described?
- Ensure the prefix is received with the matching community
- Confirm each application is mapped to the correct trust-boundary zone
- Ensure private and public WAN members are separated by security role
- Ensure loopback address stability and routing across active underlays
Explanation
Correct Answer
A:Ensure the prefix is received with the matching community. This is the enabling condition for reuse route-tag-based dynamic destination matching for the new BGP-learned prefix. Without that prerequisite, the expected operational evidence may not appear: check the new route has the expected tag and is eligible for steering. the documented recovery path is to repair missing BGP community signaling rather than adding one-off firewall address entries.
Incorrect Answers
B:Confirm each application is mapped to the correct trust-boundary zone is relevant when the organization must use separate SD-WAN zones and distinct zone-referenced security profiles. Here the prerequisite instead concerns reuse route-tag-based dynamic destination matching for the new BGP-learned prefix, so that different condition would not establish the necessary setup for the stated deployment.
C:Ensure private and public WAN members are separated by security role is relevant when the organization must steer with SD-WAN zones while applying the correct zone-level firewall policy. Here the prerequisite instead concerns reuse route-tag-based dynamic destination matching for the new BGP-learned prefix, so that different condition would not establish the necessary setup for the stated deployment.
D: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 reuse route-tag-based dynamic destination matching for the new BGP-learned prefix, so that different condition would not establish the necessary setup for the stated deployment.
Question 191
A team implemented this choice for a customer: Reuse route-tag-based dynamic destination matching for the new BGP-learned prefix. The requirement was: a business adds a new private network prefix without changing SD-WAN policies. Which observable result most directly demonstrates that the chosen implementation has achieved its intended behavior?
- Test loopback reachability separately from the LAN prefix exchange
- Inspect the zone-based security policy match for the test session
- Check the new route has the expected tag and is eligible for steering
- Compare actual neighbor sessions against the planned loopback topology
Explanation
Correct Answer
C:Check the new route has the expected tag and is eligible for steering. It is the specific operational evidence for the requirement that a business adds a new private network prefix without changing SD-WAN policies. Selecting the design action alone does not prove completion without this observed result.
Incorrect Answers
A: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 check the new route has the expected tag and is eligible for steering, which is the stated acceptance result for this Fortinet deployment.
B:Inspect the zone-based security policy match for the test session would be meaningful evidence when attempting to reference the SD-WAN zone in the firewall policy rather than the member alone. It does not directly demonstrate whether check the new route has the expected tag and is eligible for steering, 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 check the new route has the expected tag and is eligible for steering, which is the stated acceptance result for this Fortinet deployment.
Question 192
A Fortinet team is working on this situation: a business adds a new private network prefix without changing SD-WAN policies. It attempted: Reuse route-tag-based dynamic destination matching for the new BGP-learned prefix. Expected evidence (Check the new route has the expected tag and is eligible for steering) is still absent. Which corrective step most directly addresses the unsuccessful verification before unrelated configuration is changed?
- Restore routing before weakening performance SLA thresholds
- Correct loopback reachability before creating additional per-tunnel neighbors
- Correct the firewall permission while preserving the intended SD-WAN steering decision
- Repair missing BGP community signaling rather than adding one-off firewall address entries
Explanation
Correct Answer
D:Repair missing BGP community signaling rather than adding one-off firewall address entries. The missing evidence (check the new route has the expected tag and is eligible for steering) points to a problem with the implementation of reuse route-tag-based dynamic destination matching for the new BGP-learned prefix. It is the correction specific to that missing operational result rather than a broad relaxation of security policy.
Incorrect Answers
A:Restore routing before weakening performance SLA thresholds addresses a different operational issue: a network has healthy SD-WAN members but no default path out of the branch. This situation calls for repair missing BGP community signaling rather than adding one-off firewall address entries because the missing result relates to check the new route has the expected tag and is eligible for steering.
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 repair missing BGP community signaling rather than adding one-off firewall address entries because the missing result relates to check the new route has the expected tag and is eligible for steering.
C:Correct the firewall permission while preserving the intended SD-WAN steering decision addresses a different operational issue: a branch SD-WAN rule matches a service but the firewall denies its traffic. This situation calls for repair missing BGP community signaling rather than adding one-off firewall address entries because the missing result relates to check the new route has the expected tag and is eligible for steering.
Question 193
An architect is preparing a Fortinet FortiSASE 26 / FortiOS 7.6 design. A team attempts to use BGP tags for static routes that have no community processing. Which design or implementation decision best meets the stated requirement?
- Reference the SD-WAN zone in the firewall policy rather than the member alone
- Steer with SD-WAN zones while applying the correct zone-level firewall policy
- Establish BGP peering to reachable loopback addresses rather than per-underlay interface addresses
- Apply route tags through the appropriate routing process rather than assuming all static routes inherit BGP communities
Explanation
Correct Answer
D:Apply route tags through the appropriate routing process rather than assuming all static routes inherit BGP communities. This addresses the stated requirement: a team attempts to use BGP tags for static routes that have no community processing. The deployment must satisfy the accompanying requirement (Confirm the relevant route is BGP-learned and processed by the route map); the engineer can then validate the result by performing this check: inspect route origin, tag, and matching service rule.
Incorrect Answers
A:Reference the SD-WAN zone in the firewall policy rather than the member alone is a legitimate choice for another type of situation: a firewall policy references an individual physical SD-WAN member and fails to apply. The alternative design first requires the team to verify the physical interface is already associated with the intended zone, but it does not directly implement the specified requirement to apply route tags through the appropriate routing process rather than assuming all static routes inherit BGP communities.
B:Steer with SD-WAN zones while applying the correct zone-level firewall policy is a legitimate choice for another type of situation: an MPLS provider wants separate inspection for private WAN traffic and public broadband sessions. The alternative design first requires the team to ensure private and public WAN members are separated by security role, but it does not directly implement the specified requirement to apply route tags through the appropriate routing process rather than assuming all static routes inherit BGP communities.
C:Establish BGP peering to reachable loopback addresses rather than per-underlay interface addresses is a legitimate choice for another type of situation: two hubs share a stable BGP loopback while physical overlays can change. The alternative design first requires the team to ensure the overlay routes can transport traffic to the loopbacks, but it does not directly implement the specified requirement to apply route tags through the appropriate routing process rather than assuming all static routes inherit BGP communities.
Question 194
In a deployment where a team attempts to use BGP tags for static routes that have no community processing, the team plans to: Apply route tags through the appropriate routing process rather than assuming all static routes inherit BGP communities. Which condition must be established for the chosen implementation to work as described?
- Verify the physical interface is already associated with the intended zone
- Ensure the zone and interfaces exist before route creation
- Confirm the relevant route is BGP-learned and processed by the route map
- Ensure loopback address stability and routing across active underlays
Explanation
Correct Answer
C:Confirm the relevant route is BGP-learned and processed by the route map. This is the enabling condition for apply route tags through the appropriate routing process rather than assuming all static routes inherit BGP communities. Without that prerequisite, the expected operational evidence may not appear: inspect route origin, tag, and matching service rule. the documented recovery path is to correct the route origin or tagging method before troubleshooting unrelated IPsec ciphers.
Incorrect Answers
A:Verify the physical interface is already associated with the intended zone is relevant when the organization must reference the SD-WAN zone in the firewall policy rather than the member alone. Here the prerequisite instead concerns apply route tags through the appropriate routing process rather than assuming all static routes inherit BGP communities, so that different condition would not establish the necessary setup for the stated deployment.
B:Ensure the zone and interfaces exist before route creation is relevant when the organization must install the required static route toward the SD-WAN zone. Here the prerequisite instead concerns apply route tags through the appropriate routing process rather than assuming all static routes inherit BGP communities, so that different condition would not establish the necessary setup for the stated deployment.
D: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 apply route tags through the appropriate routing process rather than assuming all static routes inherit BGP communities, so that different condition would not establish the necessary setup for the stated deployment.
Question 195
A team implemented this choice for a customer: Apply route tags through the appropriate routing process rather than assuming all static routes inherit BGP communities. The requirement was: a team attempts to use BGP tags for static routes that have no community processing. 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
- Check matched firewall policy and zone for each traffic class
- Inspect policy deny logs rather than assuming route selection grants access
Explanation
Correct Answer
B:Inspect route origin, tag, and matching service rule. It is the specific operational evidence for the requirement that a team attempts to use BGP tags for static routes that have no community processing. Selecting the design action alone does not prove completion without this observed result.
Incorrect Answers
A:Inspect the forwarding table for a usable default route through the SD-WAN interface would be meaningful evidence when attempting to install the required static route toward the SD-WAN zone. It does not directly demonstrate whether inspect route origin, tag, and matching service rule, which is the stated acceptance result for this Fortinet deployment.
C:Check matched firewall policy and zone for each traffic class would be meaningful evidence when attempting to steer with SD-WAN zones while applying the correct zone-level firewall policy. It does not directly demonstrate whether inspect route origin, tag, and matching service rule, which is the stated acceptance result for this Fortinet deployment.
D:Inspect policy deny logs rather than assuming route selection grants access would be meaningful evidence when attempting to evaluate the zone-referenced firewall policy independently from the SD-WAN steering rule. It does not directly demonstrate whether inspect route origin, tag, and matching service rule, which is the stated acceptance result for this Fortinet deployment.
Question 196
A Fortinet team is working on this situation: a team attempts to use BGP tags for static routes that have no community processing. It attempted: Apply route tags through the appropriate routing process rather than assuming all static routes inherit BGP communities. Expected evidence (Inspect route origin, tag, and matching service rule) is still absent. Which corrective step most directly addresses the unsuccessful verification before unrelated configuration is changed?
- Correct the route origin or tagging method before troubleshooting unrelated IPsec ciphers
- Correct missing loopback transport reachability rather than repeatedly bouncing the neighbor
- Remove accidental per-overlay sessions after loopback peering is correctly established
- Repair misclassified zone membership rather than replacing the entire overlay template
Explanation
Correct Answer
A:Correct the route origin or tagging method before troubleshooting unrelated IPsec ciphers. The missing evidence (inspect route origin, tag, and matching service rule) points to a problem with the implementation of apply route tags through the appropriate routing process rather than assuming all static routes inherit BGP communities. It is the correction specific to that missing operational result rather than a broad relaxation of security policy.
Incorrect Answers
B:Correct missing loopback transport reachability rather than repeatedly bouncing the neighbor addresses a different operational issue: a branch loses a physical WAN but still sees BGP peering down despite a healthy overlay. This situation calls for correct the route origin or tagging method before troubleshooting unrelated IPsec ciphers because the missing result relates to inspect route origin, tag, and matching service rule.
C: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 route origin or tagging method before troubleshooting unrelated IPsec ciphers because the missing result relates to inspect route origin, tag, and matching service rule.
D:Repair misclassified zone membership rather than replacing the entire overlay template addresses a different operational issue: a site wants different filtering for internet access versus private datacenter overlays. This situation calls for correct the route origin or tagging method before troubleshooting unrelated IPsec ciphers because the missing result relates to inspect route origin, tag, and matching service rule.
Question 197
An architect is preparing a Fortinet FortiSASE 26 / FortiOS 7.6 design. A branch supports both IPv4 and IPv6 BGP destinations with dynamic steering requirements. Which design or implementation decision best meets the stated requirement?
- Use the supported IPv4 or IPv6 route-tag matching for the relevant address family
- Establish BGP peering to reachable loopback addresses rather than per-underlay interface addresses
- Evaluate the zone-referenced firewall policy independently from the SD-WAN steering rule
- Steer with SD-WAN zones while applying the correct zone-level firewall policy
Explanation
Correct Answer
A:Use the supported IPv4 or IPv6 route-tag matching for the relevant address family. This addresses the stated requirement: a branch supports both IPv4 and IPv6 BGP destinations with dynamic steering requirements. The deployment must satisfy the accompanying requirement (Confirm the matching route map and SD-WAN rule address-family scope); the engineer can then validate the result by performing this check: inspect tag presence on the intended IPv4 or IPv6 route.
Incorrect Answers
B:Establish BGP peering to reachable loopback addresses rather than per-underlay interface addresses is a legitimate choice for another type of situation: two hubs share a stable BGP loopback while physical overlays can change. The alternative design first requires the team to ensure the overlay routes can transport traffic to the loopbacks, but it does not directly implement the specified requirement to use the supported IPv4 or IPv6 route-tag matching for the relevant address family.
C:Evaluate the zone-referenced firewall policy independently from the SD-WAN steering rule is a legitimate choice for another type of situation: a branch SD-WAN rule matches a service but the firewall denies its traffic. The alternative design first requires the team to ensure the requested source/destination and security policy allow that session, but it does not directly implement the specified requirement to use the supported IPv4 or IPv6 route-tag matching for the relevant address family.
D:Steer with SD-WAN zones while applying the correct zone-level firewall policy is a legitimate choice for another type of situation: an MPLS provider wants separate inspection for private WAN traffic and public broadband sessions. The alternative design first requires the team to ensure private and public WAN members are separated by security role, but it does not directly implement the specified requirement to use the supported IPv4 or IPv6 route-tag matching for the relevant address family.
Question 198
In a deployment where a branch supports both IPv4 and IPv6 BGP destinations with dynamic steering requirements, the team plans to: Use the supported IPv4 or IPv6 route-tag matching for the relevant address family. Which condition must be established for the chosen implementation to work as described?
- Check that viable underlay and IPsec routes continue to reach the loopback
- Ensure the zone and interfaces exist before route creation
- Verify both hubs have compatible peer and route advertisement configuration
- Confirm the matching route map and SD-WAN rule address-family scope
Explanation
Correct Answer
D:Confirm the matching route map and SD-WAN rule address-family scope. This is the enabling condition for use the supported IPv4 or IPv6 route-tag matching for the relevant address family. Without that prerequisite, the expected operational evidence may not appear: inspect tag presence on the intended IPv4 or IPv6 route. the documented recovery path is to fix a mismatched address-family rule rather than copying an IPv4-only match to IPv6.
Incorrect Answers
A:Check that viable underlay and IPsec routes continue to reach the loopback is relevant when the organization must diagnose transport to the BGP loopback address via surviving overlays. Here the prerequisite instead concerns use the supported IPv4 or IPv6 route-tag matching for the relevant address family, so that different condition would not establish the necessary setup for the stated deployment.
B:Ensure the zone and interfaces exist before route creation is relevant when the organization must install the required static route toward the SD-WAN zone. Here the prerequisite instead concerns use the supported IPv4 or IPv6 route-tag matching for the relevant address family, 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 use the supported IPv4 or IPv6 route-tag matching for the relevant address family, so that different condition would not establish the necessary setup for the stated deployment.
Question 199
A team implemented this choice for a customer: Use the supported IPv4 or IPv6 route-tag matching for the relevant address family. The requirement was: a branch supports both IPv4 and IPv6 BGP destinations with dynamic steering requirements. Which observable result most directly demonstrates that the chosen implementation has achieved its intended behavior?
- Inspect branch route changes when the first hub is unavailable
- Inspect tag presence on the intended IPv4 or IPv6 route
- Inspect route-to-loopback and tunnel state before resetting BGP
- Check matched firewall policy and zone for each traffic class
Explanation
Correct Answer
B:Inspect tag presence on the intended IPv4 or IPv6 route. It is the specific operational evidence for the requirement that a branch supports both IPv4 and IPv6 BGP destinations with dynamic steering requirements. Selecting the design action alone does not prove completion without this observed result.
Incorrect Answers
A: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 tag presence on the intended IPv4 or IPv6 route, which is the stated acceptance result for this Fortinet deployment.
C:Inspect route-to-loopback and tunnel state before resetting BGP would be meaningful evidence when attempting to diagnose transport to the BGP loopback address via surviving overlays. It does not directly demonstrate whether inspect tag presence on the intended IPv4 or IPv6 route, which is the stated acceptance result for this Fortinet deployment.
D:Check matched firewall policy and zone for each traffic class would be meaningful evidence when attempting to steer with SD-WAN zones while applying the correct zone-level firewall policy. It does not directly demonstrate whether inspect tag presence on the intended IPv4 or IPv6 route, which is the stated acceptance result for this Fortinet deployment.
Question 200
A Fortinet team is working on this situation: a branch supports both IPv4 and IPv6 BGP destinations with dynamic steering requirements. It attempted: Use the supported IPv4 or IPv6 route-tag matching for the relevant address family. Expected evidence (Inspect tag presence on the intended IPv4 or IPv6 route) is still absent. Which corrective step most directly addresses the unsuccessful verification before unrelated configuration is changed?
- Correct loopback reachability before creating additional per-tunnel neighbors
- 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
- Restore routing before weakening performance SLA thresholds
Explanation
Correct Answer
C:Fix a mismatched address-family rule rather than copying an IPv4-only match to IPv6. The missing evidence (inspect tag presence on the intended IPv4 or IPv6 route) points to a problem with the implementation of use the supported IPv4 or IPv6 route-tag matching for the relevant address family. It is the correction specific to that missing operational result rather than a broad relaxation of security policy.
Incorrect Answers
A: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 fix a mismatched address-family rule rather than copying an IPv4-only match to IPv6 because the missing result relates to inspect tag presence on the intended IPv4 or IPv6 route.
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 fix a mismatched address-family rule rather than copying an IPv4-only match to IPv6 because the missing result relates to inspect tag presence on the intended IPv4 or IPv6 route.
D:Restore routing before weakening performance SLA thresholds addresses a different operational issue: a network has healthy SD-WAN members but no default path out of the branch. This situation calls for fix a mismatched address-family rule rather than copying an IPv4-only match to IPv6 because the missing result relates to inspect tag presence on the intended IPv4 or IPv6 route.
Fortinet NSE 7 - FortiSASE 26 Architect (NSE7_SSE_AR-26) Practice Tests