Cisco 300-410 Practice Test 35
Question 340
During a scheduled validation at the Newark remote operations location, critical route changes appear locally, but the remote syslog collector receives only a subset of severity levels. Engineers must restore an operations uplink without disturbing unrelated production services. The attempted fix creates a regression. Which scoped recovery action is most appropriate?
- Restore the prior trusted key configuration if rotating device keys breaks automated management.
- Revert the source-interface change if network policy rejects the replacement source address.
- Restore earlier remote logging limits if the new level floods the collector.
- Restore the old helper if requests are sent to an unauthorized DHCP server.
Explanation
Correct Answer
C:Restore earlier remote logging limits if the new level floods the collector. Local logging and remote syslog use separate targets and severity thresholds.
Incorrect Answers
A:Restore the prior trusted key configuration if rotating device keys breaks automated management. This is a rollback for a different component (SSH prerequisites), where A Cisco IOS SSH server needs valid crypto key material and compatible session settings. Here the evidence instead concerns syslog severity filtering: Local logging and remote syslog use separate targets and severity thresholds.
B:Revert the source-interface change if network policy rejects the replacement source address. This is a rollback for a different component (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 syslog severity filtering: Local logging and remote syslog use separate targets and severity thresholds.
D: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 syslog severity filtering: Local logging and remote syslog use separate targets and severity thresholds.
Question 341
During a scheduled validation at the Columbia hospital campus, two routers on the same IPv4 segment exchange EIGRP hellos yet never form a neighbor relationship after a migration. Engineers must restore an operations uplink without disturbing unrelated production services. Which investigation should be prioritized before the engineer modifies configuration?
- 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.
- Compare the alternate neighbor's reported distance with the current successor's feasible distance.
Explanation
Correct Answer
B:Compare the configured EIGRP autonomous-system numbers and active interface participation. EIGRP neighbors for an address family need compatible autonomous-system association and interface settings.
Incorrect Answers
A:Confirm the branch is a leaf and inspect whether its neighbors treat it as an EIGRP stub. This is an investigation for a different failure condition (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 eigrp as mismatch: EIGRP neighbors for an address family need compatible autonomous-system association and interface settings.
C: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 as mismatch: EIGRP neighbors for an address family need compatible autonomous-system association and interface settings.
D:Compare the alternate neighbor's reported distance with the current successor's feasible distance. This is an investigation for a different failure condition (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 as mismatch: EIGRP neighbors for an address family need compatible autonomous-system association and interface settings.
Question 342
During a scheduled validation at the Columbia hospital campus, two routers on the same IPv4 segment exchange EIGRP hellos yet never form a neighbor relationship after a migration. Engineers must restore an operations uplink 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.
- Align the EIGRP process or named address-family AS number across the peers.
- Choose a variance that admits only loop-free feasible routes and does not exceed capacity constraints.
Explanation
Correct Answer
C:Align the EIGRP process or named address-family AS number across the peers. EIGRP neighbors for an address family need compatible autonomous-system association and interface settings.
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 as mismatch: EIGRP neighbors for an address family need compatible autonomous-system association and interface settings.
B:Configure the intended EIGRP stub behavior and advertise only approved connected or summary routes. This is a configuration change for a different root cause (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 eigrp as mismatch: EIGRP neighbors for an address family need compatible autonomous-system association and interface settings.
D: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 as mismatch: EIGRP neighbors for an address family need compatible autonomous-system association and interface settings.
Question 343
During a scheduled validation at the Columbia hospital campus, two routers on the same IPv4 segment exchange EIGRP hellos yet never form a neighbor relationship after a migration. Engineers must restore an operations uplink without disturbing unrelated production services. Which post-change check most directly establishes that the repair is correct?
- Confirm secure neighbors form and authentication-related logs stop appearing.
- Confirm core routers stop querying the stub for unrelated destinations while branch routes remain reachable.
- Check whether the reported distance is strictly less than the feasible distance before declaring it feasible.
- Check both peers appear in the EIGRP neighbor table and routes converge.
Explanation
Correct Answer
D:Check both peers appear in the EIGRP neighbor table and routes converge. EIGRP neighbors for an address family need compatible autonomous-system association and interface settings.
Incorrect Answers
A:Confirm secure neighbors form and authentication-related logs stop appearing. This is a validation for another mechanism (EIGRP neighbor authentication), where Routing authentication mismatches prevent EIGRP neighbors from exchanging trusted updates. Here the evidence instead concerns eigrp as mismatch: EIGRP neighbors for an address family need compatible autonomous-system association and interface settings.
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 eigrp as mismatch: EIGRP neighbors for an address family need compatible autonomous-system association and interface settings.
C:Check whether the reported distance is strictly less than the feasible distance before declaring it feasible. This is a validation for another mechanism (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 as mismatch: EIGRP neighbors for an address family need compatible autonomous-system association and interface settings.
Question 344
During a scheduled validation at the Columbia hospital campus, two routers on the same IPv4 segment exchange EIGRP hellos yet never form a neighbor relationship after a migration. Engineers must restore an operations uplink without disturbing unrelated production services. Select TWO actions: one investigation and one targeted remediation that belong together for this incident.
- Align the EIGRP process or named address-family AS number across the peers.
- Reduce needless query scope with appropriate stubs or route summarization and repair the nonresponding link.
- 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.
Explanation
Correct Answers
A:Align the EIGRP process or named address-family AS number across the peers. EIGRP neighbors for an address family need compatible autonomous-system association and interface settings.
D:Compare the configured EIGRP autonomous-system numbers and active interface participation. EIGRP neighbors for an address family need compatible autonomous-system association and interface settings.
Incorrect Answers
B: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 as mismatch: EIGRP neighbors for an address family need compatible autonomous-system association and interface settings.
C:Confirm the branch is a leaf and inspect whether its neighbors treat it as an EIGRP stub. This is an investigation for a different failure condition (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 eigrp as mismatch: EIGRP neighbors for an address family need compatible autonomous-system association and interface settings.
Question 345
Following a production change at the Austin hospital campus, hub NHRP logs show registration rejections after a security key rotation, although GRE underlay reachability is healthy. The incident is affecting remote-site route stability; the response team has a rollback window. Which observation is the strongest first diagnostic check for this symptom?
- Inspect the routing protocol's next-hop handling, EIGRP split-horizon, and DMVPN phase architecture.
- Compare NHRP network-ID configuration and DMVPN cloud membership on the tunnel interfaces.
- Compare GRE tunnel keys and tunnel modes between the affected DMVPN endpoints.
- Compare NHRP authentication strings and registration failure causes at the hub and spoke.
Explanation
Correct Answer
D:Compare NHRP authentication strings and registration failure causes at the hub and spoke. NHRP authentication mismatch can stop a spoke from registering even when tunnel connectivity exists.
Incorrect Answers
A: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 authentication: NHRP authentication mismatch can stop a spoke from registering even when tunnel connectivity exists.
B: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 dmvpn nhrp authentication: NHRP authentication mismatch can stop a spoke from registering even when tunnel connectivity exists.
C: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 dmvpn nhrp authentication: NHRP authentication mismatch can stop a spoke from registering even when tunnel connectivity exists.
Question 346
Following a production change at the Austin hospital campus, hub NHRP logs show registration rejections after a security key rotation, although GRE underlay reachability is healthy. 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?
- Repair the NHRP multicast map or dynamic mapping appropriate to hub/spoke roles.
- Align the intended NHRP authentication values without disabling authentication globally.
- 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.
Explanation
Correct Answer
B:Align the intended NHRP authentication values without disabling authentication globally. NHRP authentication mismatch can stop a spoke from registering even when tunnel connectivity exists.
Incorrect Answers
A: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 authentication: NHRP authentication mismatch can stop a spoke from registering even when tunnel connectivity exists.
C: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 authentication: NHRP authentication mismatch can stop a spoke from registering even when tunnel connectivity exists.
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 dmvpn nhrp authentication: NHRP authentication mismatch can stop a spoke from registering even when tunnel connectivity exists.
Question 347
Following a production change at the Austin hospital campus, hub NHRP logs show registration rejections after a security key rotation, although GRE underlay reachability is healthy. 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 secure IKE and IPsec associations form with the expected peer identity.
- Verify accepted registrations appear at the hub and authorized spokes can resolve tunnel addresses.
- Verify remote routes and NHRP mappings support the planned direct path without looping.
- Check show ip nhrp and tunnel state for successful registration after the correction.
Explanation
Correct Answer
B:Verify accepted registrations appear at the hub and authorized spokes can resolve tunnel addresses. NHRP authentication mismatch can stop a spoke from registering even when tunnel connectivity exists.
Incorrect Answers
A:Verify secure IKE and IPsec associations form with the expected peer identity. This is a validation for another mechanism (IKE peer authentication), where IKE peer authentication is independent of NHRP and must match the correct endpoint identity and credentials. Here the evidence instead concerns dmvpn nhrp authentication: NHRP authentication mismatch can stop a spoke from registering even when tunnel connectivity exists.
C:Verify remote routes and NHRP mappings support the planned direct path without looping. This is a validation for another mechanism (EIGRP on DMVPN hub), where DMVPN routing adjacency, next-hop propagation, and NHRP shortcut operation must be designed together. Here the evidence instead concerns dmvpn nhrp authentication: NHRP authentication mismatch can stop a spoke from registering even when tunnel connectivity exists.
D: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 dmvpn nhrp authentication: NHRP authentication mismatch can stop a spoke from registering even when tunnel connectivity exists.
Question 348
Following a production change at the Austin hospital campus, hub NHRP logs show registration rejections after a security key rotation, although GRE underlay reachability is healthy. The incident is affecting remote-site route stability; the response team has a rollback window. Which TWO complementary steps provide both relevant fault isolation and a controlled correction?
- Compare NHRP authentication strings and registration failure causes at the hub and spoke.
- Inspect the IKE peer identity, key selection, and authentication failure logs for the changed NBMA address.
- Align the intended NHRP authentication values without disabling authentication globally.
- Repair the NHRP multicast map or dynamic mapping appropriate to hub/spoke roles.
Explanation
Correct Answers
A:Compare NHRP authentication strings and registration failure causes at the hub and spoke. NHRP authentication mismatch can stop a spoke from registering even when tunnel connectivity exists.
C:Align the intended NHRP authentication values without disabling authentication globally. NHRP authentication mismatch can stop a spoke from registering even when tunnel connectivity exists.
Incorrect Answers
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 dmvpn nhrp authentication: NHRP authentication mismatch can stop a spoke from registering even when tunnel connectivity exists.
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 authentication: NHRP authentication mismatch can stop a spoke from registering even when tunnel connectivity exists.
Question 349
Following a production change at the Naperville manufacturing plant, multiple branch routes across an ABR produce excessive interarea LSAs and the intended summary is not advertised. The incident is affecting a voice service path; the response team has a rollback window. Which observation is the strongest first diagnostic check for this symptom?
- Compare OSPF stub flags and area type on every router participating in the area.
- Inspect the ABR's area range and confirm the source subnets actually belong to the summarized area.
- Compare interface MTUs and DBD packet handling rather than changing OSPF cost.
- Inspect the OSPF process router IDs and compare them across the affected area.
Explanation
Correct Answer
B:Inspect the ABR's area range and confirm the source subnets actually belong to the summarized area. OSPF interarea summarization is performed at ABRs with an area range for appropriate source routes.
Incorrect Answers
A:Compare OSPF stub flags and area type on every router participating in the area. This is an investigation for a different failure condition (OSPF stub option mismatch), where Stub-area option consistency is enforced when OSPF neighbors negotiate adjacency. Here the evidence instead concerns ospf interarea summarization: OSPF interarea summarization is performed at ABRs with an area range for appropriate source routes.
C:Compare interface MTUs and DBD packet handling rather than changing OSPF cost. This is an investigation for a different failure condition (OSPF database exchange MTU), where An MTU mismatch can prevent OSPF database description exchange from completing. Here the evidence instead concerns ospf interarea summarization: OSPF interarea summarization is performed at ABRs with an area range for appropriate source routes.
D:Inspect the OSPF process router IDs and compare them across the affected area. This is an investigation for a different failure condition (OSPF duplicate router ID), where OSPF uses router IDs as unique LSA originator identities within the routing domain. Here the evidence instead concerns ospf interarea summarization: OSPF interarea summarization is performed at ABRs with an area range for appropriate source routes.
Question 350
Following a production change at the Naperville manufacturing plant, multiple branch routes across an ABR produce excessive interarea LSAs and the intended summary is not advertised. 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?
- Make stub-area settings consistent across the area, including its ABRs.
- Apply the correct OSPF area-range summary at the ABR instead of an ASBR-only summary command.
- Correct the NSSA ABR translation or external-advertisement policy for the approved prefixes.
- Align the OSPF timer pair and compatible network type for the shared segment.
Explanation
Correct Answer
B:Apply the correct OSPF area-range summary at the ABR instead of an ASBR-only summary command. OSPF interarea summarization is performed at ABRs with an area range for appropriate source routes.
Incorrect Answers
A:Make stub-area settings consistent across the area, including its ABRs. This is a configuration change for a different root cause (OSPF stub option mismatch), where Stub-area option consistency is enforced when OSPF neighbors negotiate adjacency. Here the evidence instead concerns ospf interarea summarization: OSPF interarea summarization is performed at ABRs with an area range for appropriate source routes.
C:Correct the NSSA ABR translation or external-advertisement policy for the approved prefixes. This is a configuration change for a different root cause (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 ospf interarea summarization: OSPF interarea summarization is performed at ABRs with an area range for appropriate source routes.
D:Align the OSPF timer pair and compatible network type for the shared segment. This is a configuration change for a different root cause (OSPF hello and dead timers), where OSPF timer compatibility is necessary for adjacency formation on a common segment. Here the evidence instead concerns ospf interarea summarization: OSPF interarea summarization is performed at ABRs with an area range for appropriate source routes.