300-420 Exam Dumps : Designing Cisco Enterprise Networks

Ethernet Local Management Interface is used between the customer edge and provider edge to communicate service status information for Ethernet services. Under MEF Ethernet service operations, E-LMI provides the CE with information about Ethernet Virtual Connection status, including whether a configured EVC is available or unavailable. This allows the customer device to react to a provider-side service condition without relying only on physical link state. The CE-to-PE link can remain physically up even while the provider EVC is down; E-LMI closes that operational visibility gap by reporting the EVC state to the customer edge. It is not a routing protocol and does not broadcast multicast routes from the CE to the PE. It also does not broadcast to all subnets when an EVC is added. The key function defined by the MEF process is notifying the CE of EVC availability state and related service information. Reference topics: Metro Ethernet, E-LMI, Ethernet Virtual Connection, CE-to-PE signaling, MEF service operations.

The correct choice is to use a distribute list outbound under the RIP process to stop EIGRP-learned prefixes from being advertised back into the RIP domain. In multipoint two-way redistribution, the major risk is route feedback: a route learned from one protocol is redistributed into another protocol and then reintroduced back into the original domain through another redistribution point. RIPv1 is especially limited because it is classful and has no native route tagging, so filtering must be carefully placed when route tags are unavailable. By filtering outbound advertisements under the RIP process, the design prevents routes that originated in the EIGRP domain from being sent into RIP where they could be relearned elsewhere and create loops or suboptimal paths. Inbound filtering on only one process does not reliably stop feedback at all redistribution points. A stronger modern design would use route tags with protocols that support them, but given the answer choices, outbound filtering toward RIP is the appropriate loop-prevention method. Reference topics: route redistribution, distribute lists, route feedback, RIPv1 limitations, EIGRP integration.

Cisco SD-WAN components map to distinct control, management, orchestration, and forwarding roles. vManage is the centralized management plane used for configuration templates, monitoring, software management, and operational visibility. vSmart is the centralized control-plane component that distributes OMP routes, TLOC information, security parameters, and centralized policy to WAN Edge devices. vBond is the orchestration component used during onboarding; it authenticates devices, helps them discover controllers, and assists with NAT traversal. The WAN Edge router, whether physical or virtual, forms the data plane at the branch, campus, or data center and forwards user traffic through secure overlay tunnels. Correctly identifying these roles is essential because SD-WAN scale and resiliency depend on separating management, control, orchestration, and forwarding responsibilities. A design that confuses vManage with vSmart or vBond will misplace policy, onboarding, and forwarding functions. Reference topics: Cisco SD-WAN architecture, vManage, vSmart, vBond, WAN Edge, OMP, overlay control plane.