Cisco 300-410 Practice Test 17
Question 160
During a scheduled validation at the Salem branch site, an engineer sees two MPLS labels on packets leaving an ingress PE and assumes the second label is unnecessary. Engineers must restore a tenant service without disturbing unrelated production services. The attempted fix creates a regression. Which scoped recovery action is most appropriate?
- Remove the new RT imports if other customers' routes become visible.
- Restore the old PE-CE route policy if the new exchange advertises unintended customer networks.
- Revert any change that strips the VPN label before the egress PE can identify the target VRF.
- Remove unintended RT imports and restore prior VRF bindings if customer isolation is breached.
Explanation
Correct Answer
C:Revert any change that strips the VPN label before the egress PE can identify the target VRF. In MPLS L3VPN, the transport label carries packets across the core and the VPN label identifies the service at the egress PE.
Incorrect Answers
A:Remove the new RT imports if other customers' routes become visible. This is a rollback for a different component (MPLS VPN route target import), where Route targets control which VPNv4 routes a VRF imports and exports; an RD provides uniqueness rather than membership. Here the evidence instead concerns mpls l3vpn label stack: In MPLS L3VPN, the transport label carries packets across the core and the VPN label identifies the service at the egress PE.
B:Restore the old PE-CE route policy if the new exchange advertises unintended customer networks. This is a rollback for a different component (PE-to-CE routing separation), where PE-CE routing populates per-customer VRFs before routes can be distributed across an MPLS L3VPN. Here the evidence instead concerns mpls l3vpn label stack: In MPLS L3VPN, the transport label carries packets across the core and the VPN label identifies the service at the egress PE.
D:Remove unintended RT imports and restore prior VRF bindings if customer isolation is breached. This is a rollback for a different component (Customer overlapping addresses), where Overlapping address space is supported by independent VRF forwarding contexts and controlled VPN route membership. Here the evidence instead concerns mpls l3vpn label stack: In MPLS L3VPN, the transport label carries packets across the core and the VPN label identifies the service at the egress PE.
Question 161
During a scheduled validation at the Mobile enterprise edge, pE routers have an Established base BGP session, but no VPNv4 customer routes are exchanged. Engineers must restore management access without disturbing unrelated production services. Which investigation should be prioritized before the engineer modifies configuration?
- Inspect the downstream-advertised implicit-null binding and the penultimate router's label operation.
- Compare NHRP authentication strings and registration failure causes at the hub and spoke.
- Inspect whether the VPNv4 or VPNv6 address family is activated and whether route targets travel as extended communities.
- Inspect route-target extended communities on exported VPN routes and VRF import policy at the receiver.
Explanation
Correct Answer
C:Inspect whether the VPNv4 or VPNv6 address family is activated and whether route targets travel as extended communities. MPLS L3VPN routing requires multiprotocol BGP exchange of VPN NLRI and relevant attributes.
Incorrect Answers
A:Inspect the downstream-advertised implicit-null binding and the penultimate router's label operation. This is an investigation for a different failure condition (MPLS penultimate hop popping), where Penultimate hop popping is expected when an egress LSR advertises implicit null for the relevant FEC. Here the evidence instead concerns mp-bgp vpnv4 address family: MPLS L3VPN routing requires multiprotocol BGP exchange of VPN NLRI and relevant attributes.
B:Compare NHRP authentication strings and registration failure causes at the hub and spoke. This is an investigation for a different failure condition (DMVPN NHRP authentication), where NHRP authentication mismatch can stop a spoke from registering even when tunnel connectivity exists. Here the evidence instead concerns mp-bgp vpnv4 address family: MPLS L3VPN routing requires multiprotocol BGP exchange of VPN NLRI and relevant attributes.
D:Inspect route-target extended communities on exported VPN routes and VRF import policy at the receiver. This is an investigation for a different failure condition (MPLS VPN route target import), where Route targets control which VPNv4 routes a VRF imports and exports; an RD provides uniqueness rather than membership. Here the evidence instead concerns mp-bgp vpnv4 address family: MPLS L3VPN routing requires multiprotocol BGP exchange of VPN NLRI and relevant attributes.
Question 162
During a scheduled validation at the Mobile enterprise edge, pE routers have an Established base BGP session, but no VPNv4 customer routes are exchanged. Engineers must restore management access without disturbing unrelated production services. Which targeted configuration or policy correction best resolves the described fault?
- Align the intended export and import route targets while avoiding broader import of unrelated tenants.
- Repair the NHRP multicast map or dynamic mapping appropriate to hub/spoke roles.
- Retain the intended PHP behavior unless the architecture explicitly requires explicit-null handling.
- Activate the appropriate MP-BGP VPN address family for the PE neighbor and enable required community transport.
Explanation
Correct Answer
D:Activate the appropriate MP-BGP VPN address family for the PE neighbor and enable required community transport. MPLS L3VPN routing requires multiprotocol BGP exchange of VPN NLRI and relevant attributes.
Incorrect Answers
A:Align the intended export and import route targets while avoiding broader import of unrelated tenants. This is a configuration change for a different root cause (MPLS VPN route target import), where Route targets control which VPNv4 routes a VRF imports and exports; an RD provides uniqueness rather than membership. Here the evidence instead concerns mp-bgp vpnv4 address family: MPLS L3VPN routing requires multiprotocol BGP exchange of VPN NLRI and relevant attributes.
B:Repair the NHRP multicast map or dynamic mapping appropriate to hub/spoke roles. This is a configuration change for a different root cause (DMVPN multicast neighbor discovery), where Dynamic routing across GRE/mGRE requires the overlay to carry its multicast or broadcast control traffic. Here the evidence instead concerns mp-bgp vpnv4 address family: MPLS L3VPN routing requires multiprotocol BGP exchange of VPN NLRI and relevant attributes.
C:Retain the intended PHP behavior unless the architecture explicitly requires explicit-null handling. This is a configuration change for a different root cause (MPLS penultimate hop popping), where Penultimate hop popping is expected when an egress LSR advertises implicit null for the relevant FEC. Here the evidence instead concerns mp-bgp vpnv4 address family: MPLS L3VPN routing requires multiprotocol BGP exchange of VPN NLRI and relevant attributes.
Question 163
During a scheduled validation at the Mobile enterprise edge, pE routers have an Established base BGP session, but no VPNv4 customer routes are exchanged. Engineers must restore management access without disturbing unrelated production services. Which post-change check most directly establishes that the repair is correct?
- Verify accepted registrations appear at the hub and authorized spokes can resolve tunnel addresses.
- Verify VPN NLRI and extended communities are received and imported into the correct VRFs.
- Confirm the penultimate router pops the transport label and the egress PE still forwards the packet correctly.
- Verify remote routes and NHRP mappings support the planned direct path without looping.
Explanation
Correct Answer
B:Verify VPN NLRI and extended communities are received and imported into the correct VRFs. MPLS L3VPN routing requires multiprotocol BGP exchange of VPN NLRI and relevant attributes.
Incorrect Answers
A:Verify accepted registrations appear at the hub and authorized spokes can resolve tunnel addresses. This is a validation for another mechanism (DMVPN NHRP authentication), where NHRP authentication mismatch can stop a spoke from registering even when tunnel connectivity exists. Here the evidence instead concerns mp-bgp vpnv4 address family: MPLS L3VPN routing requires multiprotocol BGP exchange of VPN NLRI and relevant attributes.
C:Confirm the penultimate router pops the transport label and the egress PE still forwards the packet correctly. This is a validation for another mechanism (MPLS penultimate hop popping), where Penultimate hop popping is expected when an egress LSR advertises implicit null for the relevant FEC. Here the evidence instead concerns mp-bgp vpnv4 address family: MPLS L3VPN routing requires multiprotocol BGP exchange of VPN NLRI and relevant attributes.
D:Verify remote routes and NHRP mappings support the planned direct path without looping. This is a validation for another mechanism (EIGRP on DMVPN hub), where DMVPN routing adjacency, next-hop propagation, and NHRP shortcut operation must be designed together. Here the evidence instead concerns mp-bgp vpnv4 address family: MPLS L3VPN routing requires multiprotocol BGP exchange of VPN NLRI and relevant attributes.
Question 164
During a scheduled validation at the Mobile enterprise edge, pE routers have an Established base BGP session, but no VPNv4 customer routes are exchanged. Engineers must restore management access without disturbing unrelated production services. Select TWO actions: one investigation and one targeted remediation that belong together for this incident.
- Preserve the transport-plus-VPN label structure or repair the missing correct service label at the ingress PE.
- Activate the appropriate MP-BGP VPN address family for the PE neighbor and enable required community transport.
- Inspect whether the VPNv4 or VPNv6 address family is activated and whether route targets travel as extended communities.
- Check ingress VRF assignment, VRF route table, and imported route targets for tenant overlap.
Explanation
Correct Answers
B:Activate the appropriate MP-BGP VPN address family for the PE neighbor and enable required community transport. MPLS L3VPN routing requires multiprotocol BGP exchange of VPN NLRI and relevant attributes.
C:Inspect whether the VPNv4 or VPNv6 address family is activated and whether route targets travel as extended communities. MPLS L3VPN routing requires multiprotocol BGP exchange of VPN NLRI and relevant attributes.
Incorrect Answers
A:Preserve the transport-plus-VPN label structure or repair the missing correct service label at the ingress PE. This is a configuration change for a different root cause (MPLS L3VPN label stack), where In MPLS L3VPN, the transport label carries packets across the core and the VPN label identifies the service at the egress PE. Here the evidence instead concerns mp-bgp vpnv4 address family: MPLS L3VPN routing requires multiprotocol BGP exchange of VPN NLRI and relevant attributes.
D:Check ingress VRF assignment, VRF route table, and imported route targets for tenant overlap. This is an investigation for a different failure condition (Customer overlapping addresses), where Overlapping address space is supported by independent VRF forwarding contexts and controlled VPN route membership. Here the evidence instead concerns mp-bgp vpnv4 address family: MPLS L3VPN routing requires multiprotocol BGP exchange of VPN NLRI and relevant attributes.
Question 165
Following a production change at the Bismarck remote operations location, a customer-facing interface is configured with the correct IP address, but its routes appear in the global table rather than the tenant table. The incident is affecting management access; the response team has a rollback window. Which observation is the strongest first diagnostic check for this symptom?
- Compare the configured EIGRP autonomous-system numbers and active interface participation.
- Inspect the interface's VRF forwarding assignment and the tenant VRF route table.
- Check each VRF routing table and the approved shared-subnet route-leak policy.
- Compare AS paths as seen by external peers and inspect outbound route policy for each eBGP neighbor.
Explanation
Correct Answer
B:Inspect the interface's VRF forwarding assignment and the tenant VRF route table. VRF-Lite uses separate routing tables, and assigning VRF forwarding to an interface can reset its IP address.
Incorrect Answers
A:Compare the configured EIGRP autonomous-system numbers and active interface participation. This is an investigation for a different failure condition (EIGRP AS mismatch), where EIGRP neighbors for an address family need compatible autonomous-system association and interface settings. Here the evidence instead concerns vrf-lite interface isolation: VRF-Lite uses separate routing tables, and assigning VRF forwarding to an interface can reset its IP address.
C:Check each VRF routing table and the approved shared-subnet route-leak policy. This is an investigation for a different failure condition (VRF-Lite controlled route leaking), where VRF separation is intentional; route exchange between VRFs must be explicit and constrained. Here the evidence instead concerns vrf-lite interface isolation: VRF-Lite uses separate routing tables, and assigning VRF forwarding to an interface can reset its IP address.
D:Compare AS paths as seen by external peers and inspect outbound route policy for each eBGP neighbor. This is an investigation for a different failure condition (BGP inbound traffic engineering), where AS-path prepending can make an advertised path less attractive to remote BGP networks, but cannot guarantee inbound routing. Here the evidence instead concerns vrf-lite interface isolation: VRF-Lite uses separate routing tables, and assigning VRF forwarding to an interface can reset its IP address.
Question 166
Following a production change at the Bismarck remote operations location, a customer-facing interface is configured with the correct IP address, but its routes appear in the global table rather than the tenant table. The incident is affecting management access; the response team has a rollback window. What change best addresses the root mechanism without unnecessarily changing other paths?
- Make stub-area settings consistent across the area, including its ABRs.
- Associate the interface with the intended VRF, then restore its IP configuration as required by the platform.
- Install narrowly scoped inter-VRF routes through an approved leaking method without joining the routing tables wholesale.
- Allow the intended subnet with classless redistribution and a scoped route map instead of exporting everything.
Explanation
Correct Answer
B:Associate the interface with the intended VRF, then restore its IP configuration as required by the platform. VRF-Lite uses separate routing tables, and assigning VRF forwarding to an interface can reset its IP address.
Incorrect Answers
A:Make stub-area settings consistent across the area, including its ABRs. This is a configuration change for a different root cause (OSPF stub option mismatch), where Stub-area option consistency is enforced when OSPF neighbors negotiate adjacency. Here the evidence instead concerns vrf-lite interface isolation: VRF-Lite uses separate routing tables, and assigning VRF forwarding to an interface can reset its IP address.
C:Install narrowly scoped inter-VRF routes through an approved leaking method without joining the routing tables wholesale. This is a configuration change for a different root cause (VRF-Lite controlled route leaking), where VRF separation is intentional; route exchange between VRFs must be explicit and constrained. Here the evidence instead concerns vrf-lite interface isolation: VRF-Lite uses separate routing tables, and assigning VRF forwarding to an interface can reset its IP address.
D:Allow the intended subnet with classless redistribution and a scoped route map instead of exporting everything. This is a configuration change for a different root cause (OSPF classless redistribution), where Redistribution must explicitly cover intended classless networks while avoiding uncontrolled route leakage. Here the evidence instead concerns vrf-lite interface isolation: VRF-Lite uses separate routing tables, and assigning VRF forwarding to an interface can reset its IP address.
Question 167
Following a production change at the Bismarck remote operations location, a customer-facing interface is configured with the correct IP address, but its routes appear in the global table rather than the tenant table. The incident is affecting management access; the response team has a rollback window. Which verification result would provide the most relevant acceptance evidence?
- Confirm only the shared-services prefix is reachable between VRFs and other tenant prefixes remain isolated.
- Simulate forwarding loss and confirm BFD signals the routing neighbor quickly without flapping.
- Verify neighbors form and the area receives the expected default route instead of external Type 5 LSAs.
- Confirm the route appears only in the selected VRF and end-to-end tenant probes work.
Explanation
Correct Answer
D:Confirm the route appears only in the selected VRF and end-to-end tenant probes work. VRF-Lite uses separate routing tables, and assigning VRF forwarding to an interface can reset its IP address.
Incorrect Answers
A:Confirm only the shared-services prefix is reachable between VRFs and other tenant prefixes remain isolated. This is a validation for another mechanism (VRF-Lite controlled route leaking), where VRF separation is intentional; route exchange between VRFs must be explicit and constrained. Here the evidence instead concerns vrf-lite interface isolation: VRF-Lite uses separate routing tables, and assigning VRF forwarding to an interface can reset its IP address.
B:Simulate forwarding loss and confirm BFD signals the routing neighbor quickly without flapping. This is a validation for another mechanism (BFD fast-failure detection), where Bidirectional Forwarding Detection supplies rapid forwarding-path failure detection independent of slow hello timers. Here the evidence instead concerns vrf-lite interface isolation: VRF-Lite uses separate routing tables, and assigning VRF forwarding to an interface can reset its IP address.
C:Verify neighbors form and the area receives the expected default route instead of external Type 5 LSAs. This is a validation for another mechanism (OSPF stub option mismatch), where Stub-area option consistency is enforced when OSPF neighbors negotiate adjacency. Here the evidence instead concerns vrf-lite interface isolation: VRF-Lite uses separate routing tables, and assigning VRF forwarding to an interface can reset its IP address.
Question 168
Following a production change at the Bismarck remote operations location, a customer-facing interface is configured with the correct IP address, but its routes appear in the global table rather than the tenant table. The incident is affecting management access; the response team has a rollback window. Which TWO complementary steps provide both relevant fault isolation and a controlled correction?
- Check each VRF routing table and the approved shared-subnet route-leak policy.
- Configure a consistent loopback update source and sufficient eBGP multihop hop limit.
- Associate the interface with the intended VRF, then restore its IP configuration as required by the platform.
- Inspect the interface's VRF forwarding assignment and the tenant VRF route table.
Explanation
Correct Answers
C:Associate the interface with the intended VRF, then restore its IP configuration as required by the platform. VRF-Lite uses separate routing tables, and assigning VRF forwarding to an interface can reset its IP address.
D:Inspect the interface's VRF forwarding assignment and the tenant VRF route table. VRF-Lite uses separate routing tables, and assigning VRF forwarding to an interface can reset its IP address.
Incorrect Answers
A:Check each VRF routing table and the approved shared-subnet route-leak policy. This is an investigation for a different failure condition (VRF-Lite controlled route leaking), where VRF separation is intentional; route exchange between VRFs must be explicit and constrained. Here the evidence instead concerns vrf-lite interface isolation: VRF-Lite uses separate routing tables, and assigning VRF forwarding to an interface can reset its IP address.
B:Configure a consistent loopback update source and sufficient eBGP multihop hop limit. This is a configuration change for a different root cause (Loopback-sourced eBGP session), where Default eBGP TTL and packet source are designed for directly connected peers; loopback peering needs explicit settings. Here the evidence instead concerns vrf-lite interface isolation: VRF-Lite uses separate routing tables, and assigning VRF forwarding to an interface can reset its IP address.
Question 169
Following a production change at the Roswell regional hub, a DMVPN spoke's tunnel interface remains up/up, but NHRP never registers after its ISP-facing interface was changed. The incident is affecting a tenant service; the response team has a rollback window. Which observation is the strongest first diagnostic check for this symptom?
- Compare IKE/IPsec negotiation output, transform proposals, key lifetimes, and peer reachability.
- Check NHRP multicast mapping and the GRE mode used to carry multicast routing hellos.
- Inspect the IKE peer identity, key selection, and authentication failure logs for the changed NBMA address.
- Check the tunnel source IP/interface, NBMA reachability, and NHRP peer mapping toward the hub.
Explanation
Correct Answer
D:Check the tunnel source IP/interface, NBMA reachability, and NHRP peer mapping toward the hub. DMVPN GRE tunnel reachability depends on a working NBMA underlay and correct tunnel source association.
Incorrect Answers
A:Compare IKE/IPsec negotiation output, transform proposals, key lifetimes, and peer reachability. This is an investigation for a different failure condition (DMVPN IPsec protection mismatch), where DMVPN tunnel protection requires compatible IPsec/IKE parameters for a successful protected GRE overlay. Here the evidence instead concerns dmvpn tunnel source: DMVPN GRE tunnel reachability depends on a working NBMA underlay and correct tunnel source association.
B:Check NHRP multicast mapping and the GRE mode used to carry multicast routing hellos. This is an investigation for a different failure condition (DMVPN multicast neighbor discovery), where Dynamic routing across GRE/mGRE requires the overlay to carry its multicast or broadcast control traffic. Here the evidence instead concerns dmvpn tunnel source: DMVPN GRE tunnel reachability depends on a working NBMA underlay and correct tunnel source association.
C:Inspect the IKE peer identity, key selection, and authentication failure logs for the changed NBMA address. This is an investigation for a different failure condition (IKE peer authentication), where IKE peer authentication is independent of NHRP and must match the correct endpoint identity and credentials. Here the evidence instead concerns dmvpn tunnel source: DMVPN GRE tunnel reachability depends on a working NBMA underlay and correct tunnel source association.
Question 170
Following a production change at the Roswell regional hub, a DMVPN spoke's tunnel interface remains up/up, but NHRP never registers after its ISP-facing interface was changed. The incident is affecting a tenant service; the response team has a rollback window. What change best addresses the root mechanism without unnecessarily changing other paths?
- Align the intended NHRP authentication values without disabling authentication globally.
- Apply a routing policy consistent with the chosen DMVPN phase and intended spoke next-hop behavior.
- Update the authorized peer authentication mapping or identity policy to match the new underlay endpoint.
- Bind the tunnel to the correct reachable underlay source and update dependent NBMA mapping as needed.
Explanation
Correct Answer
D:Bind the tunnel to the correct reachable underlay source and update dependent NBMA mapping as needed. DMVPN GRE tunnel reachability depends on a working NBMA underlay and correct tunnel source association.
Incorrect Answers
A:Align the intended NHRP authentication values without disabling authentication globally. This is a configuration change for a different root cause (DMVPN NHRP authentication), where NHRP authentication mismatch can stop a spoke from registering even when tunnel connectivity exists. Here the evidence instead concerns dmvpn tunnel source: DMVPN GRE tunnel reachability depends on a working NBMA underlay and correct tunnel source association.
B:Apply a routing policy consistent with the chosen DMVPN phase and intended spoke next-hop behavior. This is a configuration change for a different root cause (EIGRP on DMVPN hub), where DMVPN routing adjacency, next-hop propagation, and NHRP shortcut operation must be designed together. Here the evidence instead concerns dmvpn tunnel source: DMVPN GRE tunnel reachability depends on a working NBMA underlay and correct tunnel source association.
C:Update the authorized peer authentication mapping or identity policy to match the new underlay endpoint. This is a configuration change for a different root cause (IKE peer authentication), where IKE peer authentication is independent of NHRP and must match the correct endpoint identity and credentials. Here the evidence instead concerns dmvpn tunnel source: DMVPN GRE tunnel reachability depends on a working NBMA underlay and correct tunnel source association.