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?
Explanation
Correct Answer
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
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.
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.
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