Cisco 300-410 Practice Test 76
Question 750
Following a production change at the Chandler remote operations location, a router cannot back up its running configuration to a TFTP server across a firewall, while ICMP ping works. The incident is affecting remote-site route stability; the response team has a rollback window. What change best addresses the root mechanism without unnecessarily changing other paths?
- Correct the IOS DHCP pool default-router option and renew affected leases.
- Enable the appropriate SCP service and narrowly scoped permissions for the backup account.
- Configure the correct ip helper-address on the client-facing routed interface.
- Permit the required TFTP exchange to the authorized host or use an approved more secure backup protocol.
Explanation
Correct Answer
D:Permit the required TFTP exchange to the authorized host or use an approved more secure backup protocol. TFTP is a UDP file-transfer service; successful ICMP reachability does not prove file-transfer access.
Incorrect Answers
A:Correct the IOS DHCP pool default-router option and renew affected leases. This is a configuration change for a different root cause (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 tftp configuration transfer: TFTP is a UDP file-transfer service; successful ICMP reachability does not prove file-transfer access.
B:Enable the appropriate SCP service and narrowly scoped permissions for the backup account. This is a configuration change for a different root cause (SCP configuration backup), where SCP uses SSH transport but requires appropriate service support and file privileges. Here the evidence instead concerns tftp configuration transfer: TFTP is a UDP file-transfer service; successful ICMP reachability does not prove file-transfer access.
C:Configure the correct ip helper-address on the client-facing routed interface. This is a configuration change for a different root cause (IPv4 DHCP relay), where IPv4 DHCP Discover broadcasts require a relay when the DHCP server resides beyond a Layer 3 boundary. Here the evidence instead concerns tftp configuration transfer: TFTP is a UDP file-transfer service; successful ICMP reachability does not prove file-transfer access.
Question 751
Following a production change at the Chandler remote operations location, a router cannot back up its running configuration to a TFTP server across a firewall, while ICMP ping works. The incident is affecting remote-site route stability; the response team has a rollback window. Which verification result would provide the most relevant acceptance evidence?
- Verify a real configuration copy succeeds and the saved file can be read back.
- Confirm successful SNMPv3 authentication to the new engine ID after credential repair.
- Verify authenticated encrypted SNMP operations succeed and insecure requests are denied.
- Verify timestamped interface samples arrive at the collector at the configured cadence.
Explanation
Correct Answer
A:Verify a real configuration copy succeeds and the saved file can be read back. TFTP is a UDP file-transfer service; successful ICMP reachability does not prove file-transfer access.
Incorrect Answers
B:Confirm successful SNMPv3 authentication to the new engine ID after credential repair. This is a validation for another mechanism (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 tftp configuration transfer: TFTP is a UDP file-transfer service; successful ICMP reachability does not prove file-transfer access.
C:Verify authenticated encrypted SNMP operations succeed and insecure requests are denied. This is a validation for another mechanism (SNMPv3 security level), where SNMPv3 authPriv requires both authentication and privacy protection to match the client's requirements. Here the evidence instead concerns tftp configuration transfer: TFTP is a UDP file-transfer service; successful ICMP reachability does not prove file-transfer access.
D: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 tftp configuration transfer: TFTP is a UDP file-transfer service; successful ICMP reachability does not prove file-transfer access.
Question 752
Following a production change at the Chandler remote operations location, a router cannot back up its running configuration to a TFTP server across a firewall, while ICMP ping works. The incident is affecting remote-site route stability; the response team has a rollback window. The new configuration worsens service. Which controlled rollback should the team perform?
- Roll back the targeted change if broader client cohorts deteriorate after remediation.
- Undo a broad TFTP firewall permit if it exposes the device to untrusted endpoints.
- Restore the previous exporter path if exports accidentally reach an external untrusted collector.
- Disable the newly enabled SCP service if authorization permits unapproved file access.
Explanation
Correct Answer
B:Undo a broad TFTP firewall permit if it exposes the device to untrusted endpoints. TFTP is a UDP file-transfer service; successful ICMP reachability does not prove file-transfer access.
Incorrect Answers
A:Roll back the targeted change if broader client cohorts deteriorate after remediation. This is a rollback for a different component (Catalyst Center client assurance), where Catalyst Center Assurance correlates client experience with network/device telemetry to support diagnosis. Here the evidence instead concerns tftp configuration transfer: TFTP is a UDP file-transfer service; successful ICMP reachability does not prove file-transfer access.
C:Restore the previous exporter path if exports accidentally reach an external untrusted collector. This is a rollback for a different component (NetFlow exporter destination), where Flow collection and export are distinct: valid local cache entries do not imply successful export transport. Here the evidence instead concerns tftp configuration transfer: TFTP is a UDP file-transfer service; successful ICMP reachability does not prove file-transfer access.
D: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 tftp configuration transfer: TFTP is a UDP file-transfer service; successful ICMP reachability does not prove file-transfer access.
Question 753
During a scheduled validation at the Aurora warehouse network, two VPN customers use the same 10.1.0.0/16 space and their routes collide in a shared provider VPN control-plane design. Engineers must restore remote-site route stability without disturbing unrelated production services. Which investigation should be prioritized before the engineer modifies configuration?
- Check how the PE constructs VPNv4 routes and whether each VRF uses a distinct route distinguisher.
- Inspect route-target extended communities on exported VPN routes and VRF import policy at the receiver.
- Check the tunnel source IP/interface, NBMA reachability, and NHRP peer mapping toward the hub.
- Compare NHRP network-ID configuration and DMVPN cloud membership on the tunnel interfaces.
Explanation
Correct Answer
A:Check how the PE constructs VPNv4 routes and whether each VRF uses a distinct route distinguisher. A route distinguisher makes overlapping customer prefixes unique in VPNv4, but does not itself authorize route imports.
Incorrect Answers
B: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 mpls vpn route distinguisher: A route distinguisher makes overlapping customer prefixes unique in VPNv4, but does not itself authorize route imports.
C:Check the tunnel source IP/interface, NBMA reachability, and NHRP peer mapping toward the hub. This is an investigation for a different failure condition (DMVPN tunnel source), where DMVPN GRE tunnel reachability depends on a working NBMA underlay and correct tunnel source association. Here the evidence instead concerns mpls vpn route distinguisher: A route distinguisher makes overlapping customer prefixes unique in VPNv4, but does not itself authorize route imports.
D:Compare NHRP network-ID configuration and DMVPN cloud membership on the tunnel interfaces. This is an investigation for a different failure condition (DMVPN NHRP network ID), where NHRP network identifiers help distinguish DMVPN clouds and must match the intended overlay design. Here the evidence instead concerns mpls vpn route distinguisher: A route distinguisher makes overlapping customer prefixes unique in VPNv4, but does not itself authorize route imports.
Question 754
During a scheduled validation at the Aurora warehouse network, two VPN customers use the same 10.1.0.0/16 space and their routes collide in a shared provider VPN control-plane design. Engineers must restore remote-site route stability without disturbing unrelated production services. Which targeted configuration or policy correction best resolves the described fault?
- Align the intended NHRP authentication values without disabling authentication globally.
- Assign appropriate distinct RDs so overlapping customer prefixes become unique VPN address-family entries.
- Align the intended export and import route targets while avoiding broader import of unrelated tenants.
- Preserve the transport-plus-VPN label structure or repair the missing correct service label at the ingress PE.
Explanation
Correct Answer
B:Assign appropriate distinct RDs so overlapping customer prefixes become unique VPN address-family entries. A route distinguisher makes overlapping customer prefixes unique in VPNv4, but does not itself authorize route imports.
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 mpls vpn route distinguisher: A route distinguisher makes overlapping customer prefixes unique in VPNv4, but does not itself authorize route imports.
C: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 mpls vpn route distinguisher: A route distinguisher makes overlapping customer prefixes unique in VPNv4, but does not itself authorize route imports.
D: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 mpls vpn route distinguisher: A route distinguisher makes overlapping customer prefixes unique in VPNv4, but does not itself authorize route imports.
Question 755
During a scheduled validation at the Aurora warehouse network, two VPN customers use the same 10.1.0.0/16 space and their routes collide in a shared provider VPN control-plane design. Engineers must restore remote-site route stability without disturbing unrelated production services. Which post-change check most directly establishes that the repair is correct?
- Verify distinct VPNv4 prefixes appear with their corresponding RDs without cross-tenant forwarding.
- Confirm only approved VPN routes appear in the destination VRF with expected next-hop reachability.
- Verify the spoke registers with the intended NHS and can resolve hub tunnel reachability.
- Verify accepted registrations appear at the hub and authorized spokes can resolve tunnel addresses.
Explanation
Correct Answer
A:Verify distinct VPNv4 prefixes appear with their corresponding RDs without cross-tenant forwarding. A route distinguisher makes overlapping customer prefixes unique in VPNv4, but does not itself authorize route imports.
Incorrect Answers
B:Confirm only approved VPN routes appear in the destination VRF with expected next-hop reachability. This is a validation for another mechanism (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 vpn route distinguisher: A route distinguisher makes overlapping customer prefixes unique in VPNv4, but does not itself authorize route imports.
C:Verify the spoke registers with the intended NHS and can resolve hub tunnel reachability. This is a validation for another mechanism (DMVPN NHS mapping), where A spoke typically needs valid NHRP hub mappings and an NHS to bootstrap DMVPN registration. Here the evidence instead concerns mpls vpn route distinguisher: A route distinguisher makes overlapping customer prefixes unique in VPNv4, but does not itself authorize route imports.
D: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 mpls vpn route distinguisher: A route distinguisher makes overlapping customer prefixes unique in VPNv4, but does not itself authorize route imports.
Question 756
During a scheduled validation at the Aurora warehouse network, two VPN customers use the same 10.1.0.0/16 space and their routes collide in a shared provider VPN control-plane design. Engineers must restore remote-site route stability without disturbing unrelated production services. The attempted fix creates a regression. Which scoped recovery action is most appropriate?
- Restore the earlier RD design if route updates unexpectedly withdraw active customer prefixes.
- Remove unintended RT imports and restore prior VRF bindings if customer isolation is breached.
- Remove the new RT imports if other customers' routes become visible.
- Roll back the core path change if the label-switched path diverges from the intended FEC.
Explanation
Correct Answer
A:Restore the earlier RD design if route updates unexpectedly withdraw active customer prefixes. A route distinguisher makes overlapping customer prefixes unique in VPNv4, but does not itself authorize route imports.
Incorrect Answers
B: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 vpn route distinguisher: A route distinguisher makes overlapping customer prefixes unique in VPNv4, but does not itself authorize route imports.
C: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 vpn route distinguisher: A route distinguisher makes overlapping customer prefixes unique in VPNv4, but does not itself authorize route imports.
D:Roll back the core path change if the label-switched path diverges from the intended FEC. This is a rollback for a different component (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 mpls vpn route distinguisher: A route distinguisher makes overlapping customer prefixes unique in VPNv4, but does not itself authorize route imports.
Question 757
Following a production change at the Fargo manufacturing plant, a packet capture at the egress PE shows the transport label missing one hop before the destination PE, and an engineer suspects corruption. 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 NHRP network-ID configuration and DMVPN cloud membership on the tunnel interfaces.
- 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.
- Inspect the downstream-advertised implicit-null binding and the penultimate router's label operation.
Explanation
Correct Answer
D:Inspect the downstream-advertised implicit-null binding and the penultimate router's label operation. Penultimate hop popping is expected when an egress LSR advertises implicit null for the relevant FEC.
Incorrect Answers
A:Compare NHRP network-ID configuration and DMVPN cloud membership on the tunnel interfaces. This is an investigation for a different failure condition (DMVPN NHRP network ID), where NHRP network identifiers help distinguish DMVPN clouds and must match the intended overlay design. Here the evidence instead concerns mpls penultimate hop popping: Penultimate hop popping is expected when an egress LSR advertises implicit null for the relevant FEC.
B: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 mpls penultimate hop popping: Penultimate hop popping is expected when an egress LSR advertises implicit null for the relevant FEC.
C:Check the tunnel source IP/interface, NBMA reachability, and NHRP peer mapping toward the hub. This is an investigation for a different failure condition (DMVPN tunnel source), where DMVPN GRE tunnel reachability depends on a working NBMA underlay and correct tunnel source association. Here the evidence instead concerns mpls penultimate hop popping: Penultimate hop popping is expected when an egress LSR advertises implicit null for the relevant FEC.
Question 758
Following a production change at the Fargo manufacturing plant, a packet capture at the egress PE shows the transport label missing one hop before the destination PE, and an engineer suspects corruption. 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?
- Retain the intended PHP behavior unless the architecture explicitly requires explicit-null handling.
- Align supported IPsec proposals and tunnel protection profiles on both endpoints without downgrading policy.
- 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.
Explanation
Correct Answer
A:Retain the intended PHP behavior unless the architecture explicitly requires explicit-null handling. Penultimate hop popping is expected when an egress LSR advertises implicit null for the relevant FEC.
Incorrect Answers
B:Align supported IPsec proposals and tunnel protection profiles on both endpoints without downgrading policy. This is a configuration change for a different root cause (DMVPN IPsec protection mismatch), where DMVPN tunnel protection requires compatible IPsec/IKE parameters for a successful protected GRE overlay. Here the evidence instead concerns mpls penultimate hop popping: Penultimate hop popping is expected when an egress LSR advertises implicit null for the relevant FEC.
C: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 mpls penultimate hop popping: Penultimate hop popping is expected when an egress LSR advertises implicit null for the relevant FEC.
D: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 mpls penultimate hop popping: Penultimate hop popping is expected when an egress LSR advertises implicit null for the relevant FEC.
Question 759
Following a production change at the Fargo manufacturing plant, a packet capture at the egress PE shows the transport label missing one hop before the destination PE, and an engineer suspects corruption. The incident is affecting a tenant service; the response team has a rollback window. Which verification result would provide the most relevant acceptance evidence?
- 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.
- Confirm only approved VPN routes appear in the destination VRF with expected next-hop reachability.
- Verify the spoke reaches the hub's NBMA endpoint and NHRP registration succeeds.
Explanation
Correct Answer
B:Confirm the penultimate router pops the transport label and the egress PE still forwards the packet correctly. Penultimate hop popping is expected when an egress LSR advertises implicit null for the relevant FEC.
Incorrect Answers
A: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 mpls penultimate hop popping: Penultimate hop popping is expected when an egress LSR advertises implicit null for the relevant FEC.
C:Confirm only approved VPN routes appear in the destination VRF with expected next-hop reachability. This is a validation for another mechanism (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 penultimate hop popping: Penultimate hop popping is expected when an egress LSR advertises implicit null for the relevant FEC.
D:Verify the spoke reaches the hub's NBMA endpoint and NHRP registration succeeds. This is a validation for another mechanism (DMVPN tunnel source), where DMVPN GRE tunnel reachability depends on a working NBMA underlay and correct tunnel source association. Here the evidence instead concerns mpls penultimate hop popping: Penultimate hop popping is expected when an egress LSR advertises implicit null for the relevant FEC.
Question 760
Following a production change at the Fargo manufacturing plant, a packet capture at the egress PE shows the transport label missing one hop before the destination PE, and an engineer suspects corruption. The incident is affecting a tenant service; the response team has a rollback window. The new configuration worsens service. Which controlled rollback should the team perform?
- Restore the previous valid secret pair if the rotation prevents registration.
- Revert the address-family change if unrelated VPN route exchanges begin unexpectedly.
- Restore the previous label advertisement policy if a deliberate explicit-null change breaks services.
- Disable the shortcut change if dynamic mappings direct traffic to an untrusted or unreachable NBMA address.
Explanation
Correct Answer
C:Restore the previous label advertisement policy if a deliberate explicit-null change breaks services. Penultimate hop popping is expected when an egress LSR advertises implicit null for the relevant FEC.
Incorrect Answers
A:Restore the previous valid secret pair if the rotation prevents registration. This is a rollback for a different component (DMVPN NHRP authentication), where NHRP authentication mismatch can stop a spoke from registering even when tunnel connectivity exists. Here the evidence instead concerns mpls penultimate hop popping: Penultimate hop popping is expected when an egress LSR advertises implicit null for the relevant FEC.
B:Revert the address-family change if unrelated VPN route exchanges begin unexpectedly. This is a rollback for a different component (MP-BGP VPNv4 address family), where MPLS L3VPN routing requires multiprotocol BGP exchange of VPN NLRI and relevant attributes. Here the evidence instead concerns mpls penultimate hop popping: Penultimate hop popping is expected when an egress LSR advertises implicit null for the relevant FEC.
D: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 mpls penultimate hop popping: Penultimate hop popping is expected when an egress LSR advertises implicit null for the relevant FEC.