Cisco 300-410 Practice Test 12
Question 110
Following a production change at the Tempe branch site, a technician can authenticate through the serial console but fails through the network VTY after AAA changes. The incident is affecting a voice service path; the response team has a rollback window. What change best addresses the root mechanism without unnecessarily changing other paths?
- Correct the supported model-driven telemetry sensor path or receiver settings for the intended interface counters.
- Recreate or align SNMPv3 credentials for the new authoritative engine instead of reusing incompatible localized keys.
- Permit the required TFTP exchange to the authorized host or use an approved more secure backup protocol.
- Correct the VTY AAA binding for remote access while preserving console emergency management.
Explanation
Correct Answer
D:Correct the VTY AAA binding for remote access while preserving console emergency management. Console and VTY lines can use different authentication and authorization methods.
Incorrect Answers
A:Correct the supported model-driven telemetry sensor path or receiver settings for the intended interface counters. This is a configuration change for a different root cause (Model-driven telemetry subscriptions), where Streaming telemetry depends on a supported sensor model and an active subscription to the receiver. Here the evidence instead concerns console versus vty authentication: Console and VTY lines can use different authentication and authorization methods.
B:Recreate or align SNMPv3 credentials for the new authoritative engine instead of reusing incompatible localized keys. This is a configuration change for a different root cause (SNMPv3 engine identity), where SNMPv3 localized authentication keys depend on the engine identity, so device replacement can require credential regeneration. Here the evidence instead concerns console versus vty authentication: Console and VTY lines can use different authentication and authorization methods.
C:Permit the required TFTP exchange to the authorized host or use an approved more secure backup protocol. This is a configuration change for a different root cause (TFTP configuration transfer), where TFTP is a UDP file-transfer service; successful ICMP reachability does not prove file-transfer access. Here the evidence instead concerns console versus vty authentication: Console and VTY lines can use different authentication and authorization methods.
Question 111
Following a production change at the Tempe branch site, a technician can authenticate through the serial console but fails through the network VTY after AAA changes. The incident is affecting a voice service path; the response team has a rollback window. Which verification result would provide the most relevant acceptance evidence?
- Test SSH access from the approved source and denial from unauthorized sources.
- Validate console and VTY logins with their intended distinct credentials and restrictions.
- Verify timestamped interface samples arrive at the collector at the configured cadence.
- Verify hosts receive expected DHCPv6 replies while default-router information still comes from RA.
Explanation
Correct Answer
B:Validate console and VTY logins with their intended distinct credentials and restrictions. Console and VTY lines can use different authentication and authorization methods.
Incorrect Answers
A:Test SSH access from the approved source and denial from unauthorized sources. This is a validation for another mechanism (VTY access-class), where A VTY access-class restricts which source addresses can open remote terminal sessions to the router. Here the evidence instead concerns console versus vty authentication: Console and VTY lines can use different authentication and authorization methods.
C:Verify timestamped interface samples arrive at the collector at the configured cadence. This is a validation for another mechanism (Model-driven telemetry subscriptions), where Streaming telemetry depends on a supported sensor model and an active subscription to the receiver. Here the evidence instead concerns console versus vty authentication: Console and VTY lines can use different authentication and authorization methods.
D:Verify hosts receive expected DHCPv6 replies while default-router information still comes from RA. This is a validation for another mechanism (DHCPv6 relay), where DHCPv6 relaying transports client messages to a remote server; Router Advertisements still convey default-router details. Here the evidence instead concerns console versus vty authentication: Console and VTY lines can use different authentication and authorization methods.
Question 112
Following a production change at the Tempe branch site, a technician can authenticate through the serial console but fails through the network VTY after AAA changes. The incident is affecting a voice service path; the response team has a rollback window. The new configuration worsens service. Which controlled rollback should the team perform?
- Restore the previous probe interval if active measurements add excessive load.
- Disable the newly enabled SCP service if authorization permits unapproved file access.
- Restore the VTY method list if remote access becomes unusable after the change.
- Restore the last valid pool options if another VLAN starts receiving the wrong gateway.
Explanation
Correct Answer
C:Restore the VTY method list if remote access becomes unusable after the change. Console and VTY lines can use different authentication and authorization methods.
Incorrect Answers
A:Restore the previous probe interval if active measurements add excessive load. This is a rollback for a different component (IP SLA UDP jitter monitoring), where Jitter-sensitive applications need measurements of delay variation and loss, not just ICMP reachability. Here the evidence instead concerns console versus vty authentication: Console and VTY lines can use different authentication and authorization methods.
B:Disable the newly enabled SCP service if authorization permits unapproved file access. This is a rollback for a different component (SCP configuration backup), where SCP uses SSH transport but requires appropriate service support and file privileges. Here the evidence instead concerns console versus vty authentication: Console and VTY lines can use different authentication and authorization methods.
D:Restore the last valid pool options if another VLAN starts receiving the wrong gateway. This is a rollback for a different component (DHCP default-router option), where DHCP option 3/default-router tells IPv4 clients which gateway to use; leases can be valid despite a wrong option. Here the evidence instead concerns console versus vty authentication: Console and VTY lines can use different authentication and authorization methods.
Question 113
During a scheduled validation at the Cedar Rapids regional hub, a customer-facing interface is configured with the correct IP address, but its routes appear in the global table rather than the tenant table. Engineers must restore a business-critical application without disturbing unrelated production services. Which investigation should be prioritized before the engineer modifies configuration?
- Compare effective OSPF hello and dead timers and interface network types on both ends.
- Check each VRF routing table and the approved shared-subnet route-leak policy.
- Inspect the interface's VRF forwarding assignment and the tenant VRF route table.
- Trace Type 7 LSAs inside the NSSA and the ABR's Type 7-to-Type 5 translation behavior.
Explanation
Correct Answer
C: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 effective OSPF hello and dead timers and interface network types on both ends. This is an investigation for a different failure condition (OSPF hello and dead timers), where OSPF timer compatibility is necessary for adjacency formation on a common segment. 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: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:Trace Type 7 LSAs inside the NSSA and the ABR's Type 7-to-Type 5 translation behavior. This is an investigation for a different failure condition (OSPF NSSA external route translation), where An NSSA supports Type 7 external advertisements that can be translated into Type 5 at an ABR. 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 114
During a scheduled validation at the Cedar Rapids regional hub, a customer-facing interface is configured with the correct IP address, but its routes appear in the global table rather than the tenant table. Engineers must restore a business-critical application without disturbing unrelated production services. Which targeted configuration or policy correction best resolves the described fault?
- Configure matching OSPF virtual-link endpoints by ABR router ID across an eligible nonstub transit area.
- Install narrowly scoped inter-VRF routes through an approved leaking method without joining the routing tables wholesale.
- Tag routes on first redistribution and deny that tag when importing them back into the source domain.
- Associate the interface with the intended VRF, then restore its IP configuration as required by the platform.
Explanation
Correct Answer
D: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:Configure matching OSPF virtual-link endpoints by ABR router ID across an eligible nonstub transit area. This is a configuration change for a different root cause (OSPF backbone continuity), where An OSPF virtual link extends backbone connectivity through a suitable transit area; it is not built across a stub area. 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: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.
C:Tag routes on first redistribution and deny that tag when importing them back into the source domain. This is a configuration change for a different root cause (Redistribution loop prevention tags), where Consistent route tagging and inbound redistribution filters help prevent feedback loops across routing domains. 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 115
During a scheduled validation at the Cedar Rapids regional hub, a customer-facing interface is configured with the correct IP address, but its routes appear in the global table rather than the tenant table. Engineers must restore a business-critical application without disturbing unrelated production services. Which post-change check most directly establishes that the repair is correct?
- Confirm the route appears only in the selected VRF and end-to-end tenant probes work.
- Confirm core routers stop querying the stub for unrelated destinations while branch routes remain reachable.
- Confirm only the shared-services prefix is reachable between VRFs and other tenant prefixes remain isolated.
- Confirm a stable adjacency and consistent successor selection after the correction.
Explanation
Correct Answer
A: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
B:Confirm core routers stop querying the stub for unrelated destinations while branch routes remain reachable. This is a validation for another mechanism (EIGRP stub branch), where EIGRP stub limits query scope and is appropriate only where the device is not needed as transit. 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: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.
D:Confirm a stable adjacency and consistent successor selection after the correction. This is a validation for another mechanism (EIGRP K-value mismatch), where Traditional EIGRP neighbor adjacency requires compatible metric K-values. 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 116
During a scheduled validation at the Cedar Rapids regional hub, a customer-facing interface is configured with the correct IP address, but its routes appear in the global table rather than the tenant table. Engineers must restore a business-critical application without disturbing unrelated production services. The attempted fix creates a regression. Which scoped recovery action is most appropriate?
- Remove the newly introduced leak routes if other tenant networks become reachable.
- Revert the next-hop rewrite if it diverts traffic from the intended external edge.
- Revert the local-preference policy if it overloads the selected WAN circuit.
- Move the interface back to its prior VRF and restore the original addressing if isolation breaks.
Explanation
Correct Answer
D:Move the interface back to its prior VRF and restore the original addressing if isolation breaks. VRF-Lite uses separate routing tables, and assigning VRF forwarding to an interface can reset its IP address.
Incorrect Answers
A:Remove the newly introduced leak routes if other tenant networks become reachable. This is a rollback for a different component (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:Revert the next-hop rewrite if it diverts traffic from the intended external edge. This is a rollback for a different component (BGP iBGP next-hop reachability), where An iBGP speaker commonly preserves next-hop attributes unless explicitly changed, so next-hop resolution matters. 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:Revert the local-preference policy if it overloads the selected WAN circuit. This is a rollback for a different component (BGP outbound path local preference), where Within an AS, higher BGP local preference normally wins before AS-path length and MED. 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 117
Following a production change at the Omaha distribution campus, a customer CE reaches its connected PE but remote site subnets are absent because the PE does not learn CE prefixes. 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 GRE tunnel keys and tunnel modes between the affected DMVPN endpoints.
- Check the outer transport LSP label and inner VPN service label purpose for the traffic.
- Compare the incoming-label lookup, outgoing label, and outgoing interface in the LFIB.
- Inspect the selected PE-CE routing protocol or static routes within the customer VRF.
Explanation
Correct Answer
D:Inspect the selected PE-CE routing protocol or static routes within the customer VRF. PE-CE routing populates per-customer VRFs before routes can be distributed across an MPLS L3VPN.
Incorrect Answers
A:Compare GRE tunnel keys and tunnel modes between the affected DMVPN endpoints. This is an investigation for a different failure condition (DMVPN tunnel key consistency), where A GRE tunnel key mismatch can prevent compatible overlay traffic from being accepted. Here the evidence instead concerns pe-to-ce routing separation: PE-CE routing populates per-customer VRFs before routes can be distributed across an MPLS L3VPN.
B:Check the outer transport LSP label and inner VPN service label purpose for the traffic. This is an investigation for a different failure condition (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 pe-to-ce routing separation: PE-CE routing populates per-customer VRFs before routes can be distributed across an MPLS L3VPN.
C:Compare the incoming-label lookup, outgoing label, and outgoing interface in the LFIB. This is an investigation for a different failure condition (MPLS incoming versus outgoing labels), where An LSR switches labels using its label forwarding information base, not the customer IP prefix alone. Here the evidence instead concerns pe-to-ce routing separation: PE-CE routing populates per-customer VRFs before routes can be distributed across an MPLS L3VPN.
Question 118
Following a production change at the Omaha distribution campus, a customer CE reaches its connected PE but remote site subnets are absent because the PE does not learn CE prefixes. 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?
- Correct the spoke's NHRP next-hop server and hub tunnel-to-NBMA map for its reachable hub.
- Correct the label/next-hop distribution inconsistency by repairing the underlying LDP/IGP path rather than editing IP routes blindly.
- Enable the intended hub NHRP redirect and spoke NHRP shortcut behavior with a compatible routing design.
- Repair PE-CE adjacency or a scoped static route in the VRF and export only the intended customer prefixes.
Explanation
Correct Answer
D:Repair PE-CE adjacency or a scoped static route in the VRF and export only the intended customer prefixes. PE-CE routing populates per-customer VRFs before routes can be distributed across an MPLS L3VPN.
Incorrect Answers
A:Correct the spoke's NHRP next-hop server and hub tunnel-to-NBMA map for its reachable hub. This is a configuration change for a different root cause (DMVPN NHS mapping), where A spoke typically needs valid NHRP hub mappings and an NHS to bootstrap DMVPN registration. Here the evidence instead concerns pe-to-ce routing separation: PE-CE routing populates per-customer VRFs before routes can be distributed across an MPLS L3VPN.
B:Correct the label/next-hop distribution inconsistency by repairing the underlying LDP/IGP path rather than editing IP routes blindly. This is a configuration change for a different root cause (MPLS incoming versus outgoing labels), where An LSR switches labels using its label forwarding information base, not the customer IP prefix alone. Here the evidence instead concerns pe-to-ce routing separation: PE-CE routing populates per-customer VRFs before routes can be distributed across an MPLS L3VPN.
C:Enable the intended hub NHRP redirect and spoke NHRP shortcut behavior with a compatible routing design. This is a configuration change for a different root cause (DMVPN phase 3 shortcut), where DMVPN phase 3 uses hub redirects and spoke shortcuts to facilitate direct spoke-to-spoke forwarding. Here the evidence instead concerns pe-to-ce routing separation: PE-CE routing populates per-customer VRFs before routes can be distributed across an MPLS L3VPN.
Question 119
Following a production change at the Omaha distribution campus, a customer CE reaches its connected PE but remote site subnets are absent because the PE does not learn CE prefixes. The incident is affecting management access; the response team has a rollback window. Which verification result would provide the most relevant acceptance evidence?
- Verify distinct VPNv4 prefixes appear with their corresponding RDs without cross-tenant forwarding.
- Verify VPN NLRI and extended communities are received and imported into the correct VRFs.
- Check show ip nhrp and tunnel state for successful registration after the correction.
- Verify the PE VRF RIB learns CE routes and the remote VRF receives them via VPN signaling.
Explanation
Correct Answer
D:Verify the PE VRF RIB learns CE routes and the remote VRF receives them via VPN signaling. PE-CE routing populates per-customer VRFs before routes can be distributed across an MPLS L3VPN.
Incorrect Answers
A:Verify distinct VPNv4 prefixes appear with their corresponding RDs without cross-tenant forwarding. This is a validation for another mechanism (MPLS VPN route distinguisher), where A route distinguisher makes overlapping customer prefixes unique in VPNv4, but does not itself authorize route imports. Here the evidence instead concerns pe-to-ce routing separation: PE-CE routing populates per-customer VRFs before routes can be distributed across an MPLS L3VPN.
B:Verify VPN NLRI and extended communities are received and imported into the correct VRFs. This is a validation for another mechanism (MP-BGP VPNv4 address family), where MPLS L3VPN routing requires multiprotocol BGP exchange of VPN NLRI and relevant attributes. Here the evidence instead concerns pe-to-ce routing separation: PE-CE routing populates per-customer VRFs before routes can be distributed across an MPLS L3VPN.
C:Check show ip nhrp and tunnel state for successful registration after the correction. This is a validation for another mechanism (DMVPN NHRP network ID), where NHRP network identifiers help distinguish DMVPN clouds and must match the intended overlay design. Here the evidence instead concerns pe-to-ce routing separation: PE-CE routing populates per-customer VRFs before routes can be distributed across an MPLS L3VPN.
Question 120
Following a production change at the Omaha distribution campus, a customer CE reaches its connected PE but remote site subnets are absent because the PE does not learn CE prefixes. The incident is affecting management access; the response team has a rollback window. The new configuration worsens service. Which controlled rollback should the team perform?
- Disable the shortcut change if dynamic mappings direct traffic to an untrusted or unreachable NBMA address.
- Roll back the IPsec proposal atomically on both sides if secure tunnel establishment fails.
- Remove unintended RT imports and restore prior VRF bindings if customer isolation is breached.
- Restore the old PE-CE route policy if the new exchange advertises unintended customer networks.
Explanation
Correct Answer
D:Restore the old PE-CE route policy if the new exchange advertises unintended customer networks. PE-CE routing populates per-customer VRFs before routes can be distributed across an MPLS L3VPN.
Incorrect Answers
A:Disable the shortcut change if dynamic mappings direct traffic to an untrusted or unreachable NBMA address. This is a rollback for a different component (DMVPN phase 3 shortcut), where DMVPN phase 3 uses hub redirects and spoke shortcuts to facilitate direct spoke-to-spoke forwarding. Here the evidence instead concerns pe-to-ce routing separation: PE-CE routing populates per-customer VRFs before routes can be distributed across an MPLS L3VPN.
B:Roll back the IPsec proposal atomically on both sides if secure tunnel establishment fails. This is a rollback for a different component (DMVPN IPsec protection mismatch), where DMVPN tunnel protection requires compatible IPsec/IKE parameters for a successful protected GRE overlay. Here the evidence instead concerns pe-to-ce routing separation: PE-CE routing populates per-customer VRFs before routes can be distributed across an MPLS L3VPN.
C: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 pe-to-ce routing separation: PE-CE routing populates per-customer VRFs before routes can be distributed across an MPLS L3VPN.