Deploying NEW-VRF-001 for Full Host Reachability
Refer to the exhibit. An engineer must deploy NEW-VRF-001 in the data center. All hosts require full reachability with all other hosts, no matter on which pod the host deployment occurs. Which set of commands must the engineer include in the deployment? - 
- 
Community Votes
100% of anonymous learners picked answer D. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The exam tests the ability to distinguish between global BGP EVPN configuration and per-VRF route-target policies required for cross-pod L2/L3 connectivity.
This question evaluates the configuration of VXLAN EVPN to ensure full host-to-host reachability across pods in a data center, specifically focusing on VRF and route-target settings. It establishes that 'route-target both auto evpn' is the critical command for enabling automatic import/export of routes within the VRF context.
Candidates often select 'advertise l2vpn evpn', which is a peering-level command used to advertise the EVPN address family to neighbors, rather than the VRF-specific policy needed for route exchange.
Community Discussion (3 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
To achieve full reachability for all hosts regardless of pod location, the VRF must automatically import and export EVPN routes. The commandroute-target both auto evpn under the VRF configuration achieves this by generating a unique Route Distinguisher (RD) and Route Target (RT) based on the VRF name, ensuring consistent labeling across the fabric. This allows the EVPN control plane to correctly propagate MAC/IP reachability information between leaf switches.Why the Other Options Are Wrong
host-reachability protocol bgp is not a standard Cisco NX-OS command for this purpose; reachability is handled via the EVPN signaling mechanism. address-family l2vpn evpn configures the router to participate in the EVPN address family but does not define how routes are imported or exported into the VRF. advertise l2vpn evpn is typically configured under the BGP neighbor/peer configuration to advertise the EVPN AFI/SAFI, not within the VRF definition itself.Community Comment Notes
Community consensus strongly supports Option D. One commenter noted that while 'advertise l2vpn' is valid, it belongs under the peering configuration with spines, whereas the exhibit implies VRF context commands. Another user referenced official Cisco documentation confirming that VRF-based RT automation is key for multi-pod consistency. The majority correctly identified that the VRF needs its own routing policy to accept routes from other pods.Official Reference
Exam Strategy
Always check where the command is applied in the hierarchy. If the requirement is about VRF-specific route exchange (import/export), look for route-target commands inside the VRF configuration block, not global BGP or neighbor blocks.
Frequently Asked Questions
Why is 'advertise l2vpn evpn' incorrect for VRF deployment?
That command is used under BGP neighbor configurations to advertise the EVPN address family, not to define route targets within a specific VRF instance.
What does 'both auto evpn' do in the route-target command?
It automatically generates a Route Distinguisher and Route Target based on the VRF name, applying them for both import and export of EVPN routes.