Cisco 300-410 Practice Test 77
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.
Question 761
During a scheduled validation at the Reno data center, two MPLS core neighbors can ping interface IPs but cannot maintain an LDP session after router-ID changes. Engineers must restore a voice service path without disturbing unrelated production services. Which investigation should be prioritized before the engineer modifies configuration?
- Examine the selected LDP transport address and TCP reachability between LDP identifiers.
- Check how the PE constructs VPNv4 routes and whether each VRF uses a distinct route distinguisher.
- Check ingress VRF assignment, VRF route table, and imported route targets for tenant overlap.
- Inspect the downstream-advertised implicit-null binding and the penultimate router's label operation.
Explanation
Correct Answer
A:Examine the selected LDP transport address and TCP reachability between LDP identifiers. LDP discovery can succeed while its TCP transport session fails if the chosen transport addresses are unreachable.
Incorrect Answers
B:Check how the PE constructs VPNv4 routes and whether each VRF uses a distinct route distinguisher. This is an investigation for a different failure condition (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 ldp router-id transport reachability: LDP discovery can succeed while its TCP transport session fails if the chosen transport addresses are unreachable.
C: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 ldp router-id transport reachability: LDP discovery can succeed while its TCP transport session fails if the chosen transport addresses are unreachable.
D: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 ldp router-id transport reachability: LDP discovery can succeed while its TCP transport session fails if the chosen transport addresses are unreachable.
Question 762
During a scheduled validation at the Reno data center, two MPLS core neighbors can ping interface IPs but cannot maintain an LDP session after router-ID changes. Engineers must restore a voice service path without disturbing unrelated production services. Which targeted configuration or policy correction best resolves the described fault?
- Assign appropriate distinct RDs so overlapping customer prefixes become unique VPN address-family entries.
- Enable the intended hub NHRP redirect and spoke NHRP shortcut behavior with a compatible routing design.
- Apply a routing policy consistent with the chosen DMVPN phase and intended spoke next-hop behavior.
- Make the intended LDP router-ID transport reachable through the core IGP and correct source selection.
Explanation
Correct Answer
D:Make the intended LDP router-ID transport reachable through the core IGP and correct source selection. LDP discovery can succeed while its TCP transport session fails if the chosen transport addresses are unreachable.
Incorrect Answers
A:Assign appropriate distinct RDs so overlapping customer prefixes become unique VPN address-family entries. This is a configuration change for a different root cause (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 ldp router-id transport reachability: LDP discovery can succeed while its TCP transport session fails if the chosen transport addresses are unreachable.
B: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 ldp router-id transport reachability: LDP discovery can succeed while its TCP transport session fails if the chosen transport addresses are unreachable.
C: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 ldp router-id transport reachability: LDP discovery can succeed while its TCP transport session fails if the chosen transport addresses are unreachable.
Question 763
During a scheduled validation at the Reno data center, two MPLS core neighbors can ping interface IPs but cannot maintain an LDP session after router-ID changes. Engineers must restore a voice service path without disturbing unrelated production services. Which post-change check most directly establishes that the repair is correct?
- Verify VPN NLRI and extended communities are received and imported into the correct VRFs.
- Verify a spoke obtains a shortcut mapping and subsequent traffic uses a direct spoke-to-spoke tunnel.
- Confirm the penultimate router pops the transport label and the egress PE still forwards the packet correctly.
- Verify LDP neighbors remain Operational and bindings appear across the repaired segment.
Explanation
Correct Answer
D:Verify LDP neighbors remain Operational and bindings appear across the repaired segment. LDP discovery can succeed while its TCP transport session fails if the chosen transport addresses are unreachable.
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 ldp router-id transport reachability: LDP discovery can succeed while its TCP transport session fails if the chosen transport addresses are unreachable.
B:Verify a spoke obtains a shortcut mapping and subsequent traffic uses a direct spoke-to-spoke tunnel. This is a validation for another mechanism (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 ldp router-id transport reachability: LDP discovery can succeed while its TCP transport session fails if the chosen transport addresses are unreachable.
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 ldp router-id transport reachability: LDP discovery can succeed while its TCP transport session fails if the chosen transport addresses are unreachable.
Question 764
During a scheduled validation at the Reno data center, two MPLS core neighbors can ping interface IPs but cannot maintain an LDP session after router-ID changes. Engineers must restore a voice service path without disturbing unrelated production services. Select TWO actions: one investigation and one targeted remediation that belong together for this incident.
- Inspect NHRP redirect generation on the hub and shortcut handling on spokes.
- Make the intended LDP router-ID transport reachable through the core IGP and correct source selection.
- Examine the selected LDP transport address and TCP reachability between LDP identifiers.
- Correct the label/next-hop distribution inconsistency by repairing the underlying LDP/IGP path rather than editing IP routes blindly.
Explanation
Correct Answers
B:Make the intended LDP router-ID transport reachable through the core IGP and correct source selection. LDP discovery can succeed while its TCP transport session fails if the chosen transport addresses are unreachable.
C:Examine the selected LDP transport address and TCP reachability between LDP identifiers. LDP discovery can succeed while its TCP transport session fails if the chosen transport addresses are unreachable.
Incorrect Answers
A:Inspect NHRP redirect generation on the hub and shortcut handling on spokes. This is an investigation for a different failure condition (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 ldp router-id transport reachability: LDP discovery can succeed while its TCP transport session fails if the chosen transport addresses are unreachable.
D: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 ldp router-id transport reachability: LDP discovery can succeed while its TCP transport session fails if the chosen transport addresses are unreachable.
Question 765
Following a production change at the Lansing warehouse network, an engineer sees two MPLS labels on packets leaving an ingress PE and assumes the second label is unnecessary. The incident is affecting a monitored campus segment; 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.
- Inspect the selected PE-CE routing protocol or static routes within the customer VRF.
- Inspect the IKE peer identity, key selection, and authentication failure logs for the changed NBMA address.
- Check the outer transport LSP label and inner VPN service label purpose for the traffic.
Explanation
Correct Answer
D:Check the outer transport LSP label and inner VPN service label purpose for the traffic. 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: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 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:Inspect the selected PE-CE routing protocol or static routes within the customer VRF. This is an investigation for a different failure condition (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.
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 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 766
Following a production change at the Lansing warehouse network, an engineer sees two MPLS labels on packets leaving an ingress PE and assumes the second label is unnecessary. The incident is affecting a monitored campus segment; the response team has a rollback window. What change best addresses the root mechanism without unnecessarily changing other paths?
- Align the intended export and import route targets while avoiding broader import of unrelated tenants.
- Use a consistent NHRP network ID and tunnel addressing plan for the intended DMVPN cloud.
- Preserve the transport-plus-VPN label structure or repair the missing correct service label at the ingress PE.
- Apply a routing policy consistent with the chosen DMVPN phase and intended spoke next-hop behavior.
Explanation
Correct Answer
C:Preserve the transport-plus-VPN label structure or repair the missing correct service label at the ingress PE. 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: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 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:Use a consistent NHRP network ID and tunnel addressing plan for the intended DMVPN cloud. This is a configuration change for a different root cause (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 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: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 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 767
Following a production change at the Lansing warehouse network, an engineer sees two MPLS labels on packets leaving an ingress PE and assumes the second label is unnecessary. The incident is affecting a monitored campus segment; the response team has a rollback window. Which verification result would provide the most relevant acceptance evidence?
- Capture ingress and egress label operations and confirm the egress PE selects the intended customer VRF.
- Confirm the penultimate router pops the transport label and the egress PE still forwards the packet correctly.
- Verify VPN NLRI and extended communities are received and imported into the correct VRFs.
- Confirm only approved VPN routes appear in the destination VRF with expected next-hop reachability.
Explanation
Correct Answer
A:Capture ingress and egress label operations and confirm the egress PE selects the intended customer 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
B: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 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.
C: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 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: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 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 768
Following a production change at the Lansing warehouse network, an engineer sees two MPLS labels on packets leaving an ingress PE and assumes the second label is unnecessary. The incident is affecting a monitored campus segment; the response team has a rollback window. Which TWO complementary steps provide both relevant fault isolation and a controlled correction?
- Correct the interface-to-VRF mapping and route-target isolation rather than renumbering both tenants.
- Preserve the transport-plus-VPN label structure or repair the missing correct service label at the ingress PE.
- Inspect the selected PE-CE routing protocol or static routes within the customer VRF.
- Check the outer transport LSP label and inner VPN service label purpose for the traffic.
Explanation
Correct Answers
B:Preserve the transport-plus-VPN label structure or repair the missing correct service label at the ingress PE. In MPLS L3VPN, the transport label carries packets across the core and the VPN label identifies the service at the egress PE.
D:Check the outer transport LSP label and inner VPN service label purpose for the traffic. 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:Correct the interface-to-VRF mapping and route-target isolation rather than renumbering both tenants. This is a configuration change for a different root cause (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.
C:Inspect the selected PE-CE routing protocol or static routes within the customer VRF. This is an investigation for a different failure condition (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.
Question 769
Following a production change at the Albany manufacturing plant, a secure management portal presents a certificate name mismatch after a router IP/name change. 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 SNMPv3 user's group, security level, auth algorithm, privacy algorithm, and credentials.
- Inspect configured logging source-interface, VRF-aware transport, and collector allowlists.
- Inspect HTTPS service status and certificate subject or SAN against the accessed DNS name.
- Inspect exporter destination address, UDP port, source-interface, VRF, and export statistics.
Explanation
Correct Answer
C:Inspect HTTPS service status and certificate subject or SAN against the accessed DNS name. HTTPS management depends on TLS trust and correct certificate identity, not just an enabled port.
Incorrect Answers
A:Compare SNMPv3 user's group, security level, auth algorithm, privacy algorithm, and credentials. This is an investigation for a different failure condition (SNMPv3 security level), where SNMPv3 authPriv requires both authentication and privacy protection to match the client's requirements. Here the evidence instead concerns https device management: HTTPS management depends on TLS trust and correct certificate identity, not just an enabled port.
B:Inspect configured logging source-interface, VRF-aware transport, and collector allowlists. This is an investigation for a different failure condition (Syslog source interface), where Syslog transport can fail when its source or VRF does not match collector reachability and access rules. Here the evidence instead concerns https device management: HTTPS management depends on TLS trust and correct certificate identity, not just an enabled port.
D:Inspect exporter destination address, UDP port, source-interface, VRF, and export statistics. This is an investigation for a different failure condition (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 https device management: HTTPS management depends on TLS trust and correct certificate identity, not just an enabled port.
Question 770
Following a production change at the Albany manufacturing plant, a secure management portal presents a certificate name mismatch after a router IP/name change. 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?
- Install a trusted certificate matching the intended management DNS name and enforce HTTPS.
- Align the authorized read-only community and NMS source list without adding public write access.
- Generate an appropriate RSA key pair and enable the supported SSH server configuration.
- Fix the specifically identified failed link, ACL, or routing segment rather than reconfiguring unrelated sites.
Explanation
Correct Answer
A:Install a trusted certificate matching the intended management DNS name and enforce HTTPS. HTTPS management depends on TLS trust and correct certificate identity, not just an enabled port.
Incorrect Answers
B:Align the authorized read-only community and NMS source list without adding public write access. This is a configuration change for a different root cause (SNMPv2c read access), where SNMPv2c community matching and ACL restrictions determine polling access, but v2c itself lacks modern encryption. Here the evidence instead concerns https device management: HTTPS management depends on TLS trust and correct certificate identity, not just an enabled port.
C:Generate an appropriate RSA key pair and enable the supported SSH server configuration. This is a configuration change for a different root cause (SSH prerequisites), where A Cisco IOS SSH server needs valid crypto key material and compatible session settings. Here the evidence instead concerns https device management: HTTPS management depends on TLS trust and correct certificate identity, not just an enabled port.
D:Fix the specifically identified failed link, ACL, or routing segment rather than reconfiguring unrelated sites. This is a configuration change for a different root cause (Catalyst Center path trace), where Assurance path-trace capabilities can isolate the segment traversed by traffic and support focused troubleshooting. Here the evidence instead concerns https device management: HTTPS management depends on TLS trust and correct certificate identity, not just an enabled port.