Implementing Cisco Catalyst SD-WAN Solutions (ENSDWI) Free Sample Questions

A centralized data policy using an 'app-route' action is the correct method for influencing the path of specific traffic flows based on destination prefixes and directing them to a preferred TLOC (in this case, the MPLS circuit). This allows granular control over traffic steering within the SD-WAN fabric. A control policy manipulates routing updates, not data traffic paths directly. Localized policies apply only to a single device and are less scalable for fabric-wide rules. A VPN membership policy controls which sites can communicate within a VPN, but not the path they take.

OMP Graceful Restart is a mechanism that allows a WAN Edge router to continue forwarding traffic using its last known OMP routing information when its control plane connection to the vSmart controller is lost. This prevents traffic black-holing during controller reboots or upgrades. The hold-down timer is for route stability, BFD detects path failures, and route polling is not a standard OMP feature.

Setting the forwarding class maps the matched traffic (e.g., DSCP EF) to a specific hardware queue on the WAN Edge router. This is the first critical step in applying QoS treatment.

After mapping traffic to a forwarding class, you assign that class to a specific queue defined in the QoS map. This queue will have properties like bandwidth percentage and scheduling priority (e.g., Low Latency Queuing).

This statement is false. The vBond orchestrator's primary roles are initial authentication, NAT traversal facilitation, and distributing the list of vSmart controllers to WAN Edge routers. The WAN Edge routers themselves are responsible for establishing and maintaining the IPsec data plane tunnels between each other, using the routing and key information provided by the vSmart controllers.

TLOC Extension is a feature designed for this exact scenario. It allows a WAN Edge router to extend its transport location (TLOC) to another physically connected WAN Edge router over a service-side connection. This enables the second router to use the first router's WAN links, and vice versa, providing active/active forwarding and path redundancy for the service-side segment without needing an FHRP.

In a migration scenario, the hub or datacenter WAN Edge router acts as a gateway. It runs a traditional routing protocol (like BGP or OSPF) on its service side to learn routes from the legacy network. These learned routes are then redistributed into OMP, which advertises them to all other WAN Edge routers in the SD-WAN fabric, enabling connectivity.

The Application-Aware Routing (AAR) section within vManage, specifically its path visualization and AppQoE (Application Quality of Experience) metrics, is designed for this purpose. It calculates a quality score (vQoE) for applications across different paths based on measured loss, latency, and jitter, allowing an administrator to quickly identify the best-performing path and see if traffic is being steered correctly according to policy.

The Hierarchical SD-WAN feature, often referred to as 'Regions', is specifically designed for this purpose. It allows an administrator to divide the overlay network into logical regions, with border routers (or regional hubs) controlling the advertisement of routes between regions. This significantly reduces the OMP routing table size on branch routers and provides a scalable, structured design.

The first step in the ZTP process for a factory-default vEdge router is to resolve ztp.viptela.com. This DNS entry points to Cisco's Plug and Play (PnP) Connect portal, which will then authenticate the device based on its serial number and redirect it to the organization's specific vBond orchestrator address.

Even if an application-aware routing policy determines that a direct internet path is optimal for SaaS traffic, a centralized data policy can override this decision. A common scenario is a data policy that matches specific application traffic and redirects it to a service (like a firewall or secure web gateway) located at a hub or datacenter using a 'service' action. This data policy would take precedence over the AAR policy's path selection.