Pass Your Cisco 350-401 Exam Easy!

This test measures a different behavior: Correlate control-connection information with BFD/IPsec tunnel health across the translated transport. It does not establish the target outcome. For the documented fault, the direct acceptance test is: verify the prefix in local VPN routing, OMP advertised routes and remote edge accepted routes in that sequence.

This test measures a different behavior: Capture TLOC/BFD and data-plane tunnel counters between edges while observing no user-data transit at Controller. It does not establish the target outcome. For the documented fault, the direct acceptance test is: verify the prefix in local VPN routing, OMP advertised routes and remote edge accepted routes in that sequence.

This test measures a different behavior: Inspect controller OMP peer status and accepted route advertisements from representative edge devices. It does not establish the target outcome. For the documented fault, the direct acceptance test is: verify the prefix in local VPN routing, OMP advertised routes and remote edge accepted routes in that sequence.

That diagnosis is supported by a different symptom: Tunnels may be up but remote VPN prefixes are not distributed to edge routes. Here the recorded observation is: the branch VPN prefix exists in its local RIB yet is absent from remote OMP routes. The applicable cause is: the prefix was not injected into OMP or was rejected by control policy.

That diagnosis is supported by a different symptom: Application flows stop when an edge has no valid remote TLOC despite an OMP route being present. Here the recorded observation is: the branch VPN prefix exists in its local RIB yet is absent from remote OMP routes. The applicable cause is: the prefix was not injected into OMP or was rejected by control policy.

That diagnosis is supported by a different symptom: OMP peers are healthy while the remote branch has no established data tunnel through translated endpoints. Here the recorded observation is: the branch VPN prefix exists in its local RIB yet is absent from remote OMP routes. The applicable cause is: the prefix was not injected into OMP or was rejected by control policy.

That control reduces a separate risk: NAT mappings and data-plane tunnel reachability fail even though control connections succeeded. For the described design, the recurring risk arises from: the prefix was not injected into OMP or was rejected by control policy. The specific required safeguard is: reconcile OMP advertisements and centralized route policy during new VPN onboarding.

That control reduces a separate risk: A control-plane route existed but no eligible secure edge data-plane transport path was operational. For the described design, the recurring risk arises from: the prefix was not injected into OMP or was rejected by control policy. The specific required safeguard is: reconcile OMP advertisements and centralized route policy during new VPN onboarding.

That control reduces a separate risk: The edge lacks the expected OMP control-plane routes or policy, not a management dashboard login. For the described design, the recurring risk arises from: the prefix was not injected into OMP or was rejected by control policy. The specific required safeguard is: reconcile OMP advertisements and centralized route policy during new VPN onboarding.

Using supported localized policy on the target edge or site template for the required behavior would not implement a supported local TLOC extension between the two edges with required transport and routing settings.

Mapping transport interfaces to intended supported SD-WAN colors and selecting TLOCs in policy would not implement a supported local TLOC extension between the two edges with required transport and routing settings.

Configuring supported application-aware routing policy and BFD-based path measurements on SD-WAN edges would not implement a supported local TLOC extension between the two edges with required transport and routing settings.

This test measures a different behavior: Degrade one transport in a test and observe BFD statistics and selected TLOC change for voice while bulk traffic follows policy. It does not establish the target outcome. For the documented fault, the direct acceptance test is: check that the second edge advertises and can use the peer circuit's extended transport location.

This test measures a different behavior: Confirm local feature-policy match counters change at only the intended branch. It does not establish the target outcome. For the documented fault, the direct acceptance test is: check that the second edge advertises and can use the peer circuit's extended transport location.

This test measures a different behavior: Inspect live local/remote TLOC color attributes and confirm the intended transport is selected. It does not establish the target outcome. For the documented fault, the direct acceptance test is: check that the second edge advertises and can use the peer circuit's extended transport location.

That diagnosis is supported by a different symptom: All branch routers unexpectedly change behavior after a supposed site-only QoS update. Here the recorded observation is: the backup router loses all transport connectivity when its directly attached ISP circuit fails. The applicable cause is: it has no functioning TLOC extension path to the peer transport.

That diagnosis is supported by a different symptom: Voice stays pinned to a high-loss circuit even though an eligible second circuit is healthy. Here the recorded observation is: the backup router loses all transport connectivity when its directly attached ISP circuit fails. The applicable cause is: it has no functioning TLOC extension path to the peer transport.

That diagnosis is supported by a different symptom: An Internet-only traffic policy chooses an MPLS TLOC after a template update. Here the recorded observation is: the backup router loses all transport connectivity when its directly attached ISP circuit fails. The applicable cause is: it has no functioning TLOC extension path to the peer transport.

That control reduces a separate risk: NAT mappings and data-plane tunnel reachability fail even though control connections succeeded. For the described design, the recurring risk arises from: it has no functioning TLOC extension path to the peer transport. The specific required safeguard is: monitor TLOC-extension interface status and transport next-hop routing during site maintenance.

That control reduces a separate risk: Transport color classification or policy match does not reflect the physical circuit role. For the described design, the recurring risk arises from: it has no functioning TLOC extension path to the peer transport. The specific required safeguard is: monitor TLOC-extension interface status and transport next-hop routing during site maintenance.

That control reduces a separate risk: The configured application SLA and transport selection policy are not steering flows from measured degraded path. For the described design, the recurring risk arises from: it has no functioning TLOC extension path to the peer transport. The specific required safeguard is: monitor TLOC-extension interface status and transport next-hop routing during site maintenance.

Checking SD-WAN NAT traversal behavior and reachable TLOC public/private address mappings would not map transport interfaces to intended supported SD-WAN colors and select TLOCs in policy.

Implementing a supported local TLOC extension between the two edges with required transport and routing settings would not map transport interfaces to intended supported SD-WAN colors and select TLOCs in policy.

Using supported localized policy on the target edge or site template for the required behavior would not map transport interfaces to intended supported SD-WAN colors and select TLOCs in policy.

This test measures a different behavior: Check that the second edge advertises and can use the peer circuit's extended transport location. It does not establish the target outcome. For the documented fault, the direct acceptance test is: inspect live local/remote TLOC color attributes and confirm the intended transport is selected.

This test measures a different behavior: Correlate control-connection information with BFD/IPsec tunnel health across the translated transport. It does not establish the target outcome. For the documented fault, the direct acceptance test is: inspect live local/remote TLOC color attributes and confirm the intended transport is selected.

This test measures a different behavior: Confirm local feature-policy match counters change at only the intended branch. It does not establish the target outcome. For the documented fault, the direct acceptance test is: inspect live local/remote TLOC color attributes and confirm the intended transport is selected.

That diagnosis is supported by a different symptom: OMP peers are healthy while the remote branch has no established data tunnel through translated endpoints. Here the recorded observation is: an Internet-only traffic policy chooses an MPLS TLOC after a template update. The applicable cause is: transport color classification or policy match does not reflect the physical circuit role.

That diagnosis is supported by a different symptom: All branch routers unexpectedly change behavior after a supposed site-only QoS update. Here the recorded observation is: an Internet-only traffic policy chooses an MPLS TLOC after a template update. The applicable cause is: transport color classification or policy match does not reflect the physical circuit role.

That diagnosis is supported by a different symptom: The backup router loses all transport connectivity when its directly attached ISP circuit fails. Here the recorded observation is: an Internet-only traffic policy chooses an MPLS TLOC after a template update. The applicable cause is: transport color classification or policy match does not reflect the physical circuit role.

That control reduces a separate risk: It has no functioning TLOC extension path to the peer transport. For the described design, the recurring risk arises from: transport color classification or policy match does not reflect the physical circuit role. The specific required safeguard is: review transport color, encapsulation and allowed colors at every edge refresh.

That control reduces a separate risk: NAT mappings and data-plane tunnel reachability fail even though control connections succeeded. For the described design, the recurring risk arises from: transport color classification or policy match does not reflect the physical circuit role. The specific required safeguard is: review transport color, encapsulation and allowed colors at every edge refresh.

That control reduces a separate risk: The policy was distributed centrally instead of scoped to the single local branch. For the described design, the recurring risk arises from: transport color classification or policy match does not reflect the physical circuit role. The specific required safeguard is: review transport color, encapsulation and allowed colors at every edge refresh.