Cisco 300-410 Practice Test 25
Question 240
Following a production change at the Dayton hospital campus, a nightly backup tool can SSH to a router but its SCP upload/download fails despite correct username credentials. The incident is affecting an operations uplink; the response team has a rollback window. The new configuration worsens service. Which controlled rollback should the team perform?
- Disable excessive trap categories if the notifications overwhelm the event collector.
- Restore the old helper if requests are sent to an unauthorized DHCP server.
- 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
D:Disable the newly enabled SCP service if authorization permits unapproved file access. SCP uses SSH transport but requires appropriate service support and file privileges.
Incorrect Answers
A:Disable excessive trap categories if the notifications overwhelm the event collector. This is a rollback for a different component (SNMP traps versus polling), where SNMP traps and informs send asynchronous notifications; polling alone is periodic and can miss brief events. Here the evidence instead concerns scp configuration backup: SCP uses SSH transport but requires appropriate service support and file privileges.
B:Restore the old helper if requests are sent to an unauthorized DHCP server. This is a rollback for a different component (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 scp configuration backup: SCP uses SSH transport but requires appropriate service support and file privileges.
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 scp configuration backup: SCP uses SSH transport but requires appropriate service support and file privileges.
Question 241
Following a production change at the Columbus distribution campus, an NMS configured for SNMPv3 authPriv cannot poll a router whose user is configured for authentication only. The incident is affecting management access; the response team has a rollback window. Which observation is the strongest first diagnostic check for this symptom?
- Check telemetry subscription encoding, sensor path, transport destination, and subscription state.
- Compare SNMPv3 user's group, security level, auth algorithm, privacy algorithm, and credentials.
- Inspect IP SLA UDP-jitter measurements for one-way or round-trip delay variation and loss.
- Inspect line-specific login method lists, transport settings, and source filters separately for console and VTY.
Explanation
Correct Answer
B:Compare SNMPv3 user's group, security level, auth algorithm, privacy algorithm, and credentials. SNMPv3 authPriv requires both authentication and privacy protection to match the client's requirements.
Incorrect Answers
A:Check telemetry subscription encoding, sensor path, transport destination, and subscription state. This is an investigation for a different failure condition (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 snmpv3 security level: SNMPv3 authPriv requires both authentication and privacy protection to match the client's requirements.
C:Inspect IP SLA UDP-jitter measurements for one-way or round-trip delay variation and loss. This is an investigation for a different failure condition (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 snmpv3 security level: SNMPv3 authPriv requires both authentication and privacy protection to match the client's requirements.
D:Inspect line-specific login method lists, transport settings, and source filters separately for console and VTY. This is an investigation for a different failure condition (Console versus VTY authentication), where Console and VTY lines can use different authentication and authorization methods. Here the evidence instead concerns snmpv3 security level: SNMPv3 authPriv requires both authentication and privacy protection to match the client's requirements.
Question 242
Following a production change at the Columbus distribution campus, an NMS configured for SNMPv3 authPriv cannot poll a router whose user is configured for authentication only. 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?
- Tie the static route to a correctly scoped IP SLA track object and install a higher-distance backup route.
- Generate an appropriate RSA key pair and enable the supported SSH server configuration.
- Configure matching SNMPv3 authPriv user/group security parameters for the approved monitoring client.
- Fix the specifically identified failed link, ACL, or routing segment rather than reconfiguring unrelated sites.
Explanation
Correct Answer
C:Configure matching SNMPv3 authPriv user/group security parameters for the approved monitoring client. SNMPv3 authPriv requires both authentication and privacy protection to match the client's requirements.
Incorrect Answers
A:Tie the static route to a correctly scoped IP SLA track object and install a higher-distance backup route. This is a configuration change for a different root cause (IP SLA object tracking failover), where IP SLA probes detect beyond-interface reachability, and object tracking can control static route installation. Here the evidence instead concerns snmpv3 security level: SNMPv3 authPriv requires both authentication and privacy protection to match the client's requirements.
B: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 snmpv3 security level: SNMPv3 authPriv requires both authentication and privacy protection to match the client's requirements.
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 snmpv3 security level: SNMPv3 authPriv requires both authentication and privacy protection to match the client's requirements.
Question 243
Following a production change at the Columbus distribution campus, an NMS configured for SNMPv3 authPriv cannot poll a router whose user is configured for authentication only. The incident is affecting management access; 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.
- Verify the SSH service accepts an encrypted login from the management network.
- Verify authenticated encrypted SNMP operations succeed and insecure requests are denied.
- Repeat path trace and an application-level test to confirm the failing segment is corrected.
Explanation
Correct Answer
C:Verify authenticated encrypted SNMP operations succeed and insecure requests are denied. SNMPv3 authPriv requires both authentication and privacy protection to match the client's requirements.
Incorrect Answers
A:Verify a real configuration copy succeeds and the saved file can be read back. This is a validation for another mechanism (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 snmpv3 security level: SNMPv3 authPriv requires both authentication and privacy protection to match the client's requirements.
B:Verify the SSH service accepts an encrypted login from the management network. This is a validation for another mechanism (SSH prerequisites), where A Cisco IOS SSH server needs valid crypto key material and compatible session settings. Here the evidence instead concerns snmpv3 security level: SNMPv3 authPriv requires both authentication and privacy protection to match the client's requirements.
D:Repeat path trace and an application-level test to confirm the failing segment is corrected. This is a validation for another mechanism (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 snmpv3 security level: SNMPv3 authPriv requires both authentication and privacy protection to match the client's requirements.
Question 244
Following a production change at the Columbus distribution campus, an NMS configured for SNMPv3 authPriv cannot poll a router whose user is configured for authentication only. 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?
- Compare local logging buffer settings with remote trap severity and collector-side filtering.
- Configure matching SNMPv3 authPriv user/group security parameters for the approved monitoring client.
- Correct the supported model-driven telemetry sensor path or receiver settings for the intended interface counters.
- Compare SNMPv3 user's group, security level, auth algorithm, privacy algorithm, and credentials.
Explanation
Correct Answers
B:Configure matching SNMPv3 authPriv user/group security parameters for the approved monitoring client. SNMPv3 authPriv requires both authentication and privacy protection to match the client's requirements.
D:Compare SNMPv3 user's group, security level, auth algorithm, privacy algorithm, and credentials. SNMPv3 authPriv requires both authentication and privacy protection to match the client's requirements.
Incorrect Answers
A:Compare local logging buffer settings with remote trap severity and collector-side filtering. This is an investigation for a different failure condition (Syslog severity filtering), where Local logging and remote syslog use separate targets and severity thresholds. Here the evidence instead concerns snmpv3 security level: SNMPv3 authPriv requires both authentication and privacy protection to match the client's requirements.
C: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 snmpv3 security level: SNMPv3 authPriv requires both authentication and privacy protection to match the client's requirements.
Question 245
During a scheduled validation at the Edison distribution campus, the hub and spokes use the same GRE underlay, but one spoke never appears in NHRP registration cache. Engineers must restore remote-site route stability without disturbing unrelated production services. Which investigation should be prioritized before the engineer modifies configuration?
- Compare NHRP network-ID configuration and DMVPN cloud membership on the tunnel interfaces.
- Inspect the static NHRP map and NHS configuration on the spoke and the hub's tunnel identity.
- Inspect the routing protocol's next-hop handling, EIGRP split-horizon, and DMVPN phase architecture.
- Check the tunnel source IP/interface, NBMA reachability, and NHRP peer mapping toward the hub.
Explanation
Correct Answer
A:Compare NHRP network-ID configuration and DMVPN cloud membership on the tunnel interfaces. NHRP network identifiers help distinguish DMVPN clouds and must match the intended overlay design.
Incorrect Answers
B:Inspect the static NHRP map and NHS configuration on the spoke and the hub's tunnel identity. This is an investigation for a different failure condition (DMVPN NHS mapping), where A spoke typically needs valid NHRP hub mappings and an NHS to bootstrap DMVPN registration. Here the evidence instead concerns dmvpn nhrp network id: NHRP network identifiers help distinguish DMVPN clouds and must match the intended overlay design.
C:Inspect the routing protocol's next-hop handling, EIGRP split-horizon, and DMVPN phase architecture. This is an investigation for a different failure condition (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 nhrp network id: NHRP network identifiers help distinguish DMVPN clouds and must match the intended overlay design.
D: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 dmvpn nhrp network id: NHRP network identifiers help distinguish DMVPN clouds and must match the intended overlay design.
Question 246
During a scheduled validation at the Edison distribution campus, the hub and spokes use the same GRE underlay, but one spoke never appears in NHRP registration cache. Engineers must restore remote-site route stability without disturbing unrelated production services. Which targeted configuration or policy correction best resolves the described fault?
- Correct the spoke's NHRP next-hop server and hub tunnel-to-NBMA map for its reachable hub.
- Apply a routing policy consistent with the chosen DMVPN phase and intended spoke next-hop behavior.
- Use a consistent NHRP network ID and tunnel addressing plan for the intended DMVPN cloud.
- Repair the NHRP multicast map or dynamic mapping appropriate to hub/spoke roles.
Explanation
Correct Answer
C:Use a consistent NHRP network ID and tunnel addressing plan for the intended DMVPN cloud. NHRP network identifiers help distinguish DMVPN clouds and must match the intended overlay design.
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 dmvpn nhrp network id: NHRP network identifiers help distinguish DMVPN clouds and must match the intended overlay design.
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 nhrp network id: NHRP network identifiers help distinguish DMVPN clouds and must match the intended overlay design.
D: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 dmvpn nhrp network id: NHRP network identifiers help distinguish DMVPN clouds and must match the intended overlay design.
Question 247
During a scheduled validation at the Edison distribution campus, the hub and spokes use the same GRE underlay, but one spoke never appears in NHRP registration cache. 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 IPsec SAs form and protected DMVPN traffic increments encapsulation/decapsulation counters.
- Check show ip nhrp and tunnel state for successful registration after the correction.
- Verify the spoke reaches the hub's NBMA endpoint and NHRP registration succeeds.
- Check tunnel counters and NHRP registration after restoring matched encapsulation settings.
Explanation
Correct Answer
B:Check show ip nhrp and tunnel state for successful registration after the correction. NHRP network identifiers help distinguish DMVPN clouds and must match the intended overlay design.
Incorrect Answers
A:Verify IPsec SAs form and protected DMVPN traffic increments encapsulation/decapsulation counters. This is a validation for another mechanism (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 nhrp network id: NHRP network identifiers help distinguish DMVPN clouds and must match the intended overlay design.
C: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 dmvpn nhrp network id: NHRP network identifiers help distinguish DMVPN clouds and must match the intended overlay design.
D:Check tunnel counters and NHRP registration after restoring matched encapsulation settings. This is a validation for another mechanism (DMVPN tunnel key consistency), where A GRE tunnel key mismatch can prevent compatible overlay traffic from being accepted. Here the evidence instead concerns dmvpn nhrp network id: NHRP network identifiers help distinguish DMVPN clouds and must match the intended overlay design.
Question 248
During a scheduled validation at the Edison distribution campus, the hub and spokes use the same GRE underlay, but one spoke never appears in NHRP registration cache. Engineers must restore remote-site route stability without disturbing unrelated production services. Select TWO actions: one investigation and one targeted remediation that belong together for this incident.
- Use a consistent NHRP network ID and tunnel addressing plan for the intended DMVPN cloud.
- Compare NHRP network-ID configuration and DMVPN cloud membership on the tunnel interfaces.
- Enable the intended hub NHRP redirect and spoke NHRP shortcut behavior with a compatible routing design.
- Check the tunnel source IP/interface, NBMA reachability, and NHRP peer mapping toward the hub.
Explanation
Correct Answers
A:Use a consistent NHRP network ID and tunnel addressing plan for the intended DMVPN cloud. NHRP network identifiers help distinguish DMVPN clouds and must match the intended overlay design.
B:Compare NHRP network-ID configuration and DMVPN cloud membership on the tunnel interfaces. NHRP network identifiers help distinguish DMVPN clouds and must match the intended overlay design.
Incorrect Answers
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 dmvpn nhrp network id: NHRP network identifiers help distinguish DMVPN clouds and must match the intended overlay design.
D: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 dmvpn nhrp network id: NHRP network identifiers help distinguish DMVPN clouds and must match the intended overlay design.
Question 249
During a scheduled validation at the Tempe data center, a small leaf branch receives EIGRP queries for destinations it could never provide, increasing convergence time. Engineers must restore a business-critical application without disturbing unrelated production services. Which investigation should be prioritized before the engineer modifies configuration?
- Check key IDs, configured authentication mode, key validity, and key strings at both ends.
- Confirm the branch is a leaf and inspect whether its neighbors treat it as an EIGRP stub.
- Compare the configured EIGRP autonomous-system numbers and active interface participation.
- Inspect outstanding EIGRP queries, stub boundaries, and slow or unreachable neighbors.
Explanation
Correct Answer
B:Confirm the branch is a leaf and inspect whether its neighbors treat it as an EIGRP stub. EIGRP stub limits query scope and is appropriate only where the device is not needed as transit.
Incorrect Answers
A:Check key IDs, configured authentication mode, key validity, and key strings at both ends. This is an investigation for a different failure condition (EIGRP neighbor authentication), where Routing authentication mismatches prevent EIGRP neighbors from exchanging trusted updates. Here the evidence instead concerns eigrp stub branch: EIGRP stub limits query scope and is appropriate only where the device is not needed as transit.
C: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 eigrp stub branch: EIGRP stub limits query scope and is appropriate only where the device is not needed as transit.
D:Inspect outstanding EIGRP queries, stub boundaries, and slow or unreachable neighbors. This is an investigation for a different failure condition (EIGRP stuck-in-active), where EIGRP stuck-in-active often arises when a router does not receive timely replies to diffusion queries. Here the evidence instead concerns eigrp stub branch: EIGRP stub limits query scope and is appropriate only where the device is not needed as transit.
Question 250
During a scheduled validation at the Tempe data center, a small leaf branch receives EIGRP queries for destinations it could never provide, increasing convergence time. Engineers must restore a business-critical application without disturbing unrelated production services. Which targeted configuration or policy correction best resolves the described fault?
- Use a topology that supplies a loop-free reported-distance candidate rather than forcing an ineligible alternate.
- Configure the intended EIGRP stub behavior and advertise only approved connected or summary routes.
- Choose a variance that admits only loop-free feasible routes and does not exceed capacity constraints.
- Reduce needless query scope with appropriate stubs or route summarization and repair the nonresponding link.
Explanation
Correct Answer
B:Configure the intended EIGRP stub behavior and advertise only approved connected or summary routes. EIGRP stub limits query scope and is appropriate only where the device is not needed as transit.
Incorrect Answers
A:Use a topology that supplies a loop-free reported-distance candidate rather than forcing an ineligible alternate. This is a configuration change for a different root cause (EIGRP feasible successor), where The EIGRP feasibility condition requires a neighbor's reported distance below the local feasible distance. Here the evidence instead concerns eigrp stub branch: EIGRP stub limits query scope and is appropriate only where the device is not needed as transit.
C:Choose a variance that admits only loop-free feasible routes and does not exceed capacity constraints. This is a configuration change for a different root cause (EIGRP unequal-cost load balancing), where EIGRP variance enables unequal-cost traffic sharing only for qualifying loop-free candidates. Here the evidence instead concerns eigrp stub branch: EIGRP stub limits query scope and is appropriate only where the device is not needed as transit.
D:Reduce needless query scope with appropriate stubs or route summarization and repair the nonresponding link. This is a configuration change for a different root cause (EIGRP stuck-in-active), where EIGRP stuck-in-active often arises when a router does not receive timely replies to diffusion queries. Here the evidence instead concerns eigrp stub branch: EIGRP stub limits query scope and is appropriate only where the device is not needed as transit.