Cisco 300-410 Practice Test 49
Question 480
Following a production change at the Roanoke service-provider handoff, a spoke's NHRP adjacency worked until the IPsec proposal changed, after which GRE-over-IPsec traffic stops. The incident is affecting a business-critical application; the response team has a rollback window. The new configuration worsens service. Which controlled rollback should the team perform?
- Disable the shortcut change if dynamic mappings direct traffic to an untrusted or unreachable NBMA address.
- Restore the prior multicast map if the change floods routing hellos to unintended endpoints.
- Restore the former NHS mapping if the hub migration was incomplete.
- Roll back the IPsec proposal atomically on both sides if secure tunnel establishment fails.
Explanation
Correct Answer
D:Roll back the IPsec proposal atomically on both sides if secure tunnel establishment fails. DMVPN tunnel protection requires compatible IPsec/IKE parameters for a successful protected GRE overlay.
Incorrect Answers
A:Disable the shortcut change if dynamic mappings direct traffic to an untrusted or unreachable NBMA address. This is a rollback for a different component (DMVPN phase 3 shortcut), where DMVPN phase 3 uses hub redirects and spoke shortcuts to facilitate direct spoke-to-spoke forwarding. Here the evidence instead concerns dmvpn ipsec protection mismatch: DMVPN tunnel protection requires compatible IPsec/IKE parameters for a successful protected GRE overlay.
B:Restore the prior multicast map if the change floods routing hellos to unintended endpoints. This is a rollback for a different component (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 ipsec protection mismatch: DMVPN tunnel protection requires compatible IPsec/IKE parameters for a successful protected GRE overlay.
C:Restore the former NHS mapping if the hub migration was incomplete. This is a rollback for a different component (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 ipsec protection mismatch: DMVPN tunnel protection requires compatible IPsec/IKE parameters for a successful protected GRE overlay.
Question 481
Following a production change at the Savannah branch site, an operations collector receives no interface telemetry from a router even though the device has network reachability. The incident is affecting a customer routing segment; the response team has a rollback window. Which observation is the strongest first diagnostic check for this symptom?
- Inspect which debug condition or filter can isolate the affected neighbor or interface.
- Check UDP/69 transfer initiation, server write permissions, and return data-channel filtering.
- Inspect the VTY access-class, source subnet permit entries, and applied inbound direction.
- Check telemetry subscription encoding, sensor path, transport destination, and subscription state.
Explanation
Correct Answer
D:Check telemetry subscription encoding, sensor path, transport destination, and subscription state. Streaming telemetry depends on a supported sensor model and an active subscription to the receiver.
Incorrect Answers
A:Inspect which debug condition or filter can isolate the affected neighbor or interface. This is an investigation for a different failure condition (Conditional debugging), where Conditional debugs reduce diagnostic impact by restricting runtime detail to a relevant context. Here the evidence instead concerns model-driven telemetry subscriptions: Streaming telemetry depends on a supported sensor model and an active subscription to the receiver.
B:Check UDP/69 transfer initiation, server write permissions, and return data-channel filtering. This is an investigation for a different failure condition (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 model-driven telemetry subscriptions: Streaming telemetry depends on a supported sensor model and an active subscription to the receiver.
C:Inspect the VTY access-class, source subnet permit entries, and applied inbound direction. This is an investigation for a different failure condition (VTY access-class), where A VTY access-class restricts which source addresses can open remote terminal sessions to the router. Here the evidence instead concerns model-driven telemetry subscriptions: Streaming telemetry depends on a supported sensor model and an active subscription to the receiver.
Question 482
Following a production change at the Savannah branch site, an operations collector receives no interface telemetry from a router even though the device has network reachability. The incident is affecting a customer routing segment; the response team has a rollback window. What change best addresses the root mechanism without unnecessarily changing other paths?
- Recreate or align SNMPv3 credentials for the new authoritative engine instead of reusing incompatible localized keys.
- Tie the static route to a correctly scoped IP SLA track object and install a higher-distance backup route.
- Fix the specifically identified failed link, ACL, or routing segment rather than reconfiguring unrelated sites.
- Correct the supported model-driven telemetry sensor path or receiver settings for the intended interface counters.
Explanation
Correct Answer
D:Correct the supported model-driven telemetry sensor path or receiver settings for the intended interface counters. Streaming telemetry depends on a supported sensor model and an active subscription to the receiver.
Incorrect Answers
A:Recreate or align SNMPv3 credentials for the new authoritative engine instead of reusing incompatible localized keys. This is a configuration change for a different root cause (SNMPv3 engine identity), where SNMPv3 localized authentication keys depend on the engine identity, so device replacement can require credential regeneration. Here the evidence instead concerns model-driven telemetry subscriptions: Streaming telemetry depends on a supported sensor model and an active subscription to the receiver.
B: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 model-driven telemetry subscriptions: Streaming telemetry depends on a supported sensor model and an active subscription to the receiver.
C: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 model-driven telemetry subscriptions: Streaming telemetry depends on a supported sensor model and an active subscription to the receiver.
Question 483
Following a production change at the Savannah branch site, an operations collector receives no interface telemetry from a router even though the device has network reachability. The incident is affecting a customer routing segment; the response team has a rollback window. Which verification result would provide the most relevant acceptance evidence?
- Compare event timestamps across devices after a known simultaneous test event.
- Capture a relay-generated request and verify the server replies with a lease for the client's subnet.
- Confirm successful SNMPv3 authentication to the new engine ID after credential repair.
- Verify timestamped interface samples arrive at the collector at the configured cadence.
Explanation
Correct Answer
D:Verify timestamped interface samples arrive at the collector at the configured cadence. Streaming telemetry depends on a supported sensor model and an active subscription to the receiver.
Incorrect Answers
A:Compare event timestamps across devices after a known simultaneous test event. This is a validation for another mechanism (Time synchronization for logs), where Reliable timestamps depend on synchronized device clocks and appropriately configured log timestamps. Here the evidence instead concerns model-driven telemetry subscriptions: Streaming telemetry depends on a supported sensor model and an active subscription to the receiver.
B:Capture a relay-generated request and verify the server replies with a lease for the client's subnet. This is a validation for another mechanism (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 model-driven telemetry subscriptions: Streaming telemetry depends on a supported sensor model and an active subscription to the receiver.
C: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 model-driven telemetry subscriptions: Streaming telemetry depends on a supported sensor model and an active subscription to the receiver.
Question 484
Following a production change at the Savannah branch site, an operations collector receives no interface telemetry from a router even though the device has network reachability. The incident is affecting a customer routing segment; the response team has a rollback window. Which TWO complementary steps provide both relevant fault isolation and a controlled correction?
- Inspect exporter destination address, UDP port, source-interface, VRF, and export statistics.
- Repair synchronization to approved NTP sources and use consistent timestamp settings.
- Correct the supported model-driven telemetry sensor path or receiver settings for the intended interface counters.
- Check telemetry subscription encoding, sensor path, transport destination, and subscription state.
Explanation
Correct Answers
C:Correct the supported model-driven telemetry sensor path or receiver settings for the intended interface counters. Streaming telemetry depends on a supported sensor model and an active subscription to the receiver.
D:Check telemetry subscription encoding, sensor path, transport destination, and subscription state. Streaming telemetry depends on a supported sensor model and an active subscription to the receiver.
Incorrect Answers
A: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 model-driven telemetry subscriptions: Streaming telemetry depends on a supported sensor model and an active subscription to the receiver.
B:Repair synchronization to approved NTP sources and use consistent timestamp settings. This is a configuration change for a different root cause (Time synchronization for logs), where Reliable timestamps depend on synchronized device clocks and appropriately configured log timestamps. Here the evidence instead concerns model-driven telemetry subscriptions: Streaming telemetry depends on a supported sensor model and an active subscription to the receiver.
Question 485
During a scheduled validation at the Springfield distribution campus, multiple branch routes across an ABR produce excessive interarea LSAs and the intended summary is not advertised. Engineers must restore remote-site route stability without disturbing unrelated production services. Which investigation should be prioritized before the engineer modifies configuration?
- Check ABR topology and ensure the proposed transit area can support an OSPF virtual link.
- Compare OSPF stub flags and area type on every router participating in the area.
- Compare interface MTUs and DBD packet handling rather than changing OSPF cost.
- Inspect the ABR's area range and confirm the source subnets actually belong to the summarized area.
Explanation
Correct Answer
D: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:Check ABR topology and ensure the proposed transit area can support an OSPF virtual link. This is an investigation for a different failure condition (OSPF backbone continuity), where An OSPF virtual link extends backbone connectivity through a suitable transit area; it is not built across a stub area. Here the evidence instead concerns ospf interarea summarization: OSPF interarea summarization is performed at ABRs with an area range for appropriate source routes.
B: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.
Question 486
During a scheduled validation at the Springfield distribution campus, multiple branch routes across an ABR produce excessive interarea LSAs and the intended summary is not advertised. Engineers must restore remote-site route stability without disturbing unrelated production services. Which targeted configuration or policy correction best resolves the described fault?
- Apply the correct OSPF area-range summary at the ABR instead of an ASBR-only summary command.
- Make stub-area settings consistent across the area, including its ABRs.
- Select the appropriate external metric type and cost policy to reflect the enterprise exit preference.
- Correct the NSSA ABR translation or external-advertisement policy for the approved prefixes.
Explanation
Correct Answer
A: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
B: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:Select the appropriate external metric type and cost policy to reflect the enterprise exit preference. This is a configuration change for a different root cause (OSPF external route type), where OSPF E1 considers internal path cost with external cost, while E2 primarily compares the external metric. Here the evidence instead concerns ospf interarea summarization: OSPF interarea summarization is performed at ABRs with an area range for appropriate source routes.
D: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.
Question 487
During a scheduled validation at the Springfield distribution campus, multiple branch routes across an ABR produce excessive interarea LSAs and the intended summary is not advertised. 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 the summarized interarea LSA and the absence of redundant component advertisements downstream.
- Confirm the external prefix appears as Type 7 within NSSA and translated Type 5 where required.
- Verify adjacency reaches Full and LSAs are exchanged in the expected area.
- Verify virtual adjacency and restored backbone LSA connectivity without unintended topology loops.
Explanation
Correct Answer
A:Verify the summarized interarea LSA and the absence of redundant component advertisements downstream. OSPF interarea summarization is performed at ABRs with an area range for appropriate source routes.
Incorrect Answers
B:Confirm the external prefix appears as Type 7 within NSSA and translated Type 5 where required. This is a validation for another mechanism (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.
C:Verify adjacency reaches Full and LSAs are exchanged in the expected area. This is a validation for another mechanism (OSPF area mismatch), where OSPF neighbors must agree on the local link's area ID. Here the evidence instead concerns ospf interarea summarization: OSPF interarea summarization is performed at ABRs with an area range for appropriate source routes.
D:Verify virtual adjacency and restored backbone LSA connectivity without unintended topology loops. This is a validation for another mechanism (OSPF backbone continuity), where An OSPF virtual link extends backbone connectivity through a suitable transit area; it is not built across a stub area. Here the evidence instead concerns ospf interarea summarization: OSPF interarea summarization is performed at ABRs with an area range for appropriate source routes.
Question 488
During a scheduled validation at the Springfield distribution campus, multiple branch routes across an ABR produce excessive interarea LSAs and the intended summary is not advertised. 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.
- Compare OSPF stub flags and area type on every router participating in the area.
- Apply the correct OSPF area-range summary at the ABR instead of an ASBR-only summary command.
- Inspect the ABR's area range and confirm the source subnets actually belong to the summarized area.
- Correct the NSSA ABR translation or external-advertisement policy for the approved prefixes.
Explanation
Correct Answers
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.
C: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.
D: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.
Question 489
Following a production change at the Raleigh warehouse network, a directly connected subnet redistributed into EIGRP is missing from neighbor topology even though the redistribution command is present. 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?
- Check whether the EIGRP redistribution policy supplies a usable seed metric.
- Compare the destination's matching prefixes and their lengths, not merely route-source preference.
- Inspect the redistribution source, subnets handling, and whether a match or prefix filter excludes /27.
- Compare summary reachability with the actual set of component subnets and the summary discard route.
Explanation
Correct Answer
A:Check whether the EIGRP redistribution policy supplies a usable seed metric. EIGRP redistribution generally needs an appropriate seed metric for external routes.
Incorrect Answers
B:Compare the destination's matching prefixes and their lengths, not merely route-source preference. This is an investigation for a different failure condition (Longest-prefix selection), where A longer matching prefix is selected before administrative distance is compared among equal-length routes. Here the evidence instead concerns eigrp redistribution seed metric: EIGRP redistribution generally needs an appropriate seed metric for external routes.
C:Inspect the redistribution source, subnets handling, and whether a match or prefix filter excludes /27. This is an investigation for a different failure condition (OSPF classless redistribution), where Redistribution must explicitly cover intended classless networks while avoiding uncontrolled route leakage. Here the evidence instead concerns eigrp redistribution seed metric: EIGRP redistribution generally needs an appropriate seed metric for external routes.
D:Compare summary reachability with the actual set of component subnets and the summary discard route. This is an investigation for a different failure condition (Summary route black hole), where An aggregate can intentionally create a discard route and must not promise reachability for withdrawn component networks. Here the evidence instead concerns eigrp redistribution seed metric: EIGRP redistribution generally needs an appropriate seed metric for external routes.
Question 490
Following a production change at the Raleigh warehouse network, a directly connected subnet redistributed into EIGRP is missing from neighbor topology even though the redistribution command is present. 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?
- Tag routes on first redistribution and deny that tag when importing them back into the source domain.
- Refine the aggregate or restore specific reachable routes so the advertisement does not imply missing coverage.
- Raise the static route's distance above the intended OSPF route or remove the unwanted override.
- Provide the required EIGRP seed metric through redistribution or a route map for the intended source.
Explanation
Correct Answer
D:Provide the required EIGRP seed metric through redistribution or a route map for the intended source. EIGRP redistribution generally needs an appropriate seed metric for external routes.
Incorrect Answers
A:Tag routes on first redistribution and deny that tag when importing them back into the source domain. This is a configuration change for a different root cause (Redistribution loop prevention tags), where Consistent route tagging and inbound redistribution filters help prevent feedback loops across routing domains. Here the evidence instead concerns eigrp redistribution seed metric: EIGRP redistribution generally needs an appropriate seed metric for external routes.
B:Refine the aggregate or restore specific reachable routes so the advertisement does not imply missing coverage. This is a configuration change for a different root cause (Summary route black hole), where An aggregate can intentionally create a discard route and must not promise reachability for withdrawn component networks. Here the evidence instead concerns eigrp redistribution seed metric: EIGRP redistribution generally needs an appropriate seed metric for external routes.
C:Raise the static route's distance above the intended OSPF route or remove the unwanted override. This is a configuration change for a different root cause (Administrative distance), where For the same destination prefix, the router prefers the eligible route with the lower administrative distance after longest-prefix selection. Here the evidence instead concerns eigrp redistribution seed metric: EIGRP redistribution generally needs an appropriate seed metric for external routes.