Cisco 300-420 Practice Test 6
Question 50
A distribution router has dozens of connected prefixes and the design calls for a stable outbound EIGRP summary. The observed fault is: An overbroad summary can blackhole traffic for prefixes that are not actually reachable behind that router. What action most directly restores and validates the intended state?
- The controlled recovery is to use route metrics as a substitute for verifying aggregate prefix coverage.
- The controlled recovery is to summarize unrelated prefixes into an overly broad aggregate despite holes.
- The controlled recovery is to assume any pair of branch networks always forms a clean summary.
- The controlled recovery is to narrow the summary and test active and missing covered destinations from adjacent sites.
Explanation
Correct Answer
D:Manual EIGRP summarization reduces advertised detail but can create a discard route to avoid loops for the aggregate. Relevant evidence includes eIGRP advertised prefix list, summary calculation, neighbor table and covered subnet reachability.
Incorrect Answers
A:Use route metrics as a substitute for verifying aggregate prefix coverage. An overbroad summary can blackhole traffic for prefixes that are not actually reachable behind that router. Use the controlled remediation: narrow the summary and test active and missing covered destinations from adjacent sites.
B:Summarize unrelated prefixes into an overly broad aggregate despite holes. An overbroad summary can blackhole traffic for prefixes that are not actually reachable behind that router. Use the controlled remediation: narrow the summary and test active and missing covered destinations from adjacent sites.
C:Assume any pair of branch networks always forms a clean summary. An overbroad summary can blackhole traffic for prefixes that are not actually reachable behind that router. Use the controlled remediation: narrow the summary and test active and missing covered destinations from adjacent sites.
Question 51
A low-bandwidth EIGRP spoke should not be treated as an alternate transit path between regional hubs. What is the most defensible configuration decision?
- Configure the spoke as a transit backbone while claiming it will never carry transit.
- Design EIGRP stub behavior at nontransit spokes while maintaining appropriate hub route reachability.
- Disable all EIGRP advertisements from the branch and assume its networks stay reachable.
- Increase hello timers instead of controlling query propagation into spoke edges.
Explanation
Correct Answer
B:Confirm the result using eIGRP neighbor state, stub flags, received routes and failover query behavior. This is the specific corrective action for EIGRP stub branch neighbor design.
Incorrect Answers
A:Using a stub branch as a presumed transit router can cause blackholes or make expected routes unavailable. The relevant action is design EIGRP stub behavior at nontransit spokes while maintaining appropriate hub route reachability.
C:An EIGRP stub advertises its restricted transit role to reduce query scope and preserve scalable convergence. Instead inspect eIGRP neighbor state, stub flags, received routes and failover query behavior.
D:Using a stub branch as a presumed transit router can cause blackholes or make expected routes unavailable. Increase hello timers instead of controlling query propagation into spoke edges.
Question 52
A low-bandwidth EIGRP spoke should not be treated as an alternate transit path between regional hubs. Which evidence BEST confirms the actual technical behavior?
- EIGRP neighbor state, stub flags, received routes and failover query behavior.
- An old network diagram with no current route, policy, or redundancy state.
- One successful ping to an unrelated test host without a path or failover test.
- A marketing claim without measured routing, capacity or failure-domain evidence.
Explanation
Correct Answer
A:The intended procedure is design EIGRP stub behavior at nontransit spokes while maintaining appropriate hub route reachability. This evidence observes the actual eIGRP stub branch neighbor design mechanism and its result.
Incorrect Answers
B:This observation alone cannot establish eIGRP stub branch neighbor design. The decisive evidence instead includes eIGRP neighbor state, stub flags, received routes and failover query behavior.
C:This observation alone cannot establish eIGRP stub branch neighbor design. An EIGRP stub advertises its restricted transit role to reduce query scope and preserve scalable convergence.
D:This observation alone cannot establish eIGRP stub branch neighbor design. A marketing claim without measured routing, capacity or failure-domain evidence.
Question 53
A low-bandwidth EIGRP spoke should not be treated as an alternate transit path between regional hubs. What networking or enterprise network design concept best explains this scenario?
- An operational up state alone proves every security and design objective is met.
- An EIGRP stub advertises its restricted transit role to reduce query scope and preserve scalable convergence.
- Any single device automatically guarantees high availability for every site.
- A longer IP prefix is always less specific than the default route.
Explanation
Correct Answer
B:This is why the appropriate action is design EIGRP stub behavior at nontransit spokes while maintaining appropriate hub route reachability. Confirm it with eIGRP neighbor state, stub flags, received routes and failover query behavior.
Incorrect Answers
A:An operational up state alone proves every security and design objective is met. This is an incorrect generalization for eIGRP stub branch neighbor design. The relevant rule is an EIGRP stub advertises its restricted transit role to reduce query scope and preserve scalable convergence. Verify using eIGRP neighbor state, stub flags, received routes and failover query behavior.
C:Any single device automatically guarantees high availability for every site. This is an incorrect generalization for eIGRP stub branch neighbor design. The relevant rule is an EIGRP stub advertises its restricted transit role to reduce query scope and preserve scalable convergence. Verify using eIGRP neighbor state, stub flags, received routes and failover query behavior.
D:A longer IP prefix is always less specific than the default route. This is an incorrect generalization for eIGRP stub branch neighbor design. The relevant rule is an EIGRP stub advertises its restricted transit role to reduce query scope and preserve scalable convergence. Verify using eIGRP neighbor state, stub flags, received routes and failover query behavior.
Question 54
A low-bandwidth EIGRP spoke should not be treated as an alternate transit path between regional hubs. Suppose the operator instead makes this incorrect change: Configure the spoke as a transit backbone while claiming it will never carry transit. Which resulting fault should the reviewer identify?
- The failure is entirely cosmetic because all control-plane changes are harmless.
- Collecting telemetry originally caused the missing route or service outage.
- A correct change-control review makes all WAN carriers fail simultaneously.
- Using a stub branch as a presumed transit router can cause blackholes or make expected routes unavailable.
Explanation
Correct Answer
D:The right response is design EIGRP stub behavior at nontransit spokes while maintaining appropriate hub route reachability. This explains why the proposed shortcut does not solve eIGRP stub branch neighbor design.
Incorrect Answers
A:The failure is entirely cosmetic because all control-plane changes are harmless. The actual failure is using a stub branch as a presumed transit router can cause blackholes or make expected routes unavailable. Check eIGRP neighbor state, stub flags, received routes and failover query behavior.
B:Collecting telemetry originally caused the missing route or service outage. The actual failure is using a stub branch as a presumed transit router can cause blackholes or make expected routes unavailable. Check eIGRP neighbor state, stub flags, received routes and failover query behavior.
C:A correct change-control review makes all WAN carriers fail simultaneously. The actual failure is using a stub branch as a presumed transit router can cause blackholes or make expected routes unavailable. Check eIGRP neighbor state, stub flags, received routes and failover query behavior.
Question 55
A low-bandwidth EIGRP spoke should not be treated as an alternate transit path between regional hubs. The observed fault is: Using a stub branch as a presumed transit router can cause blackholes or make expected routes unavailable. How should the issue be corrected and verified?
- Disable all EIGRP advertisements from the branch and assume its networks stay reachable.
- Increase hello timers instead of controlling query propagation into spoke edges.
- Configure the spoke as a transit backbone while claiming it will never carry transit.
- Confirm spoke stub scope and reroute genuine intersite traffic through designated transit devices.
Explanation
Correct Answer
D:An EIGRP stub advertises its restricted transit role to reduce query scope and preserve scalable convergence. Relevant evidence includes eIGRP neighbor state, stub flags, received routes and failover query behavior.
Incorrect Answers
A:Disable all EIGRP advertisements from the branch and assume its networks stay reachable. Using a stub branch as a presumed transit router can cause blackholes or make expected routes unavailable. Use the controlled remediation: confirm spoke stub scope and reroute genuine intersite traffic through designated transit devices.
B:Increase hello timers instead of controlling query propagation into spoke edges. Using a stub branch as a presumed transit router can cause blackholes or make expected routes unavailable. Use the controlled remediation: confirm spoke stub scope and reroute genuine intersite traffic through designated transit devices.
C:Configure the spoke as a transit backbone while claiming it will never carry transit. Using a stub branch as a presumed transit router can cause blackholes or make expected routes unavailable. Use the controlled remediation: confirm spoke stub scope and reroute genuine intersite traffic through designated transit devices.
Question 56
A branch with one uplink must reduce EIGRP query propagation during core instability. What is the BEST supported implementation or corrective action?
- For this enterprise design, the architect should design EIGRP stub behavior at nontransit spokes while maintaining appropriate hub route reachability.
- For this enterprise design, the architect should disable all EIGRP advertisements from the branch and assume its networks stay reachable.
- For this enterprise design, the architect should increase hello timers instead of controlling query propagation into spoke edges.
- For this enterprise design, the architect should configure the spoke as a transit backbone while claiming it will never carry transit.
Explanation
Correct Answer
A:Confirm the result using eIGRP neighbor state, stub flags, received routes and failover query behavior. An EIGRP stub advertises its restricted transit role to reduce query scope and preserve scalable convergence.
Incorrect Answers
B:An EIGRP stub advertises its restricted transit role to reduce query scope and preserve scalable convergence. In this case, a branch with one uplink must reduce EIGRP query propagation during core instability.
C:Using a stub branch as a presumed transit router can cause blackholes or make expected routes unavailable.
D:Using a stub branch as a presumed transit router can cause blackholes or make expected routes unavailable. This change targets the wrong mechanism for EIGRP stub branch neighbor design.
Question 57
A branch with one uplink must reduce EIGRP query propagation during core instability. What should the operator inspect to verify the result?
- Inspect the following evidence: a hostname inventory without effective configuration or operational measurements.
- Inspect the following evidence: eIGRP neighbor state, stub flags, received routes and failover query behavior.
- Inspect the following evidence: an old network diagram with no current route, policy, or redundancy state.
- Inspect the following evidence: one successful ping to an unrelated test host without a path or failover test.
Explanation
Correct Answer
B:The intended procedure is design EIGRP stub behavior at nontransit spokes while maintaining appropriate hub route reachability. An EIGRP stub advertises its restricted transit role to reduce query scope and preserve scalable convergence.
Incorrect Answers
A:This observation alone cannot establish eIGRP stub branch neighbor design. A hostname inventory without effective configuration or operational measurements.
C:This observation alone cannot establish eIGRP stub branch neighbor design. In this case, a branch with one uplink must reduce EIGRP query propagation during core instability.
D:This observation alone cannot establish eIGRP stub branch neighbor design. One successful ping to an unrelated test host without a path or failover test.
Question 58
A branch with one uplink must reduce EIGRP query propagation during core instability. Which technical statement is MOST accurate for this situation?
- The relevant principle is that a longer IP prefix is always less specific than the default route.
- The relevant principle is that an operational up state alone proves every security and design objective is met.
- The relevant principle is that encryption and segmentation are identical mechanisms and can replace each other.
- The relevant principle is that an EIGRP stub advertises its restricted transit role to reduce query scope and preserve scalable convergence.
Explanation
Correct Answer
D:This is why the appropriate action is design EIGRP stub behavior at nontransit spokes while maintaining appropriate hub route reachability.
Incorrect Answers
A:A longer IP prefix is always less specific than the default route. This is an incorrect generalization for eIGRP stub branch neighbor design. The relevant rule is an EIGRP stub advertises its restricted transit role to reduce query scope and preserve scalable convergence. Verify using eIGRP neighbor state, stub flags, received routes and failover query behavior.
B:An operational up state alone proves every security and design objective is met. This is an incorrect generalization for eIGRP stub branch neighbor design. The relevant rule is an EIGRP stub advertises its restricted transit role to reduce query scope and preserve scalable convergence. Verify using eIGRP neighbor state, stub flags, received routes and failover query behavior.
C:Encryption and segmentation are identical mechanisms and can replace each other. This is an incorrect generalization for eIGRP stub branch neighbor design. The relevant rule is an EIGRP stub advertises its restricted transit role to reduce query scope and preserve scalable convergence. Verify using eIGRP neighbor state, stub flags, received routes and failover query behavior.
Question 59
A branch with one uplink must reduce EIGRP query propagation during core instability. Suppose the operator instead makes this incorrect change: Configure the spoke as a transit backbone while claiming it will never carry transit. What weakness does the mistaken approach introduce?
- The resulting technical fault is that using a stub branch as a presumed transit router can cause blackholes or make expected routes unavailable.
- The resulting technical fault is that a correct change-control review makes all WAN carriers fail simultaneously.
- The resulting technical fault is that the only issue is an inaccurate hostname while traffic paths are unaffected.
- The resulting technical fault is that collecting telemetry originally caused the missing route or service outage.
Explanation
Correct Answer
A:The right response is design EIGRP stub behavior at nontransit spokes while maintaining appropriate hub route reachability. An EIGRP stub advertises its restricted transit role to reduce query scope and preserve scalable convergence.
Incorrect Answers
B:A correct change-control review makes all WAN carriers fail simultaneously. The actual failure is using a stub branch as a presumed transit router can cause blackholes or make expected routes unavailable. Check eIGRP neighbor state, stub flags, received routes and failover query behavior.
C:The only issue is an inaccurate hostname while traffic paths are unaffected. The actual failure is using a stub branch as a presumed transit router can cause blackholes or make expected routes unavailable. Check eIGRP neighbor state, stub flags, received routes and failover query behavior.
D:Collecting telemetry originally caused the missing route or service outage. The actual failure is using a stub branch as a presumed transit router can cause blackholes or make expected routes unavailable. Check eIGRP neighbor state, stub flags, received routes and failover query behavior.
Question 60
A branch with one uplink must reduce EIGRP query propagation during core instability. The observed fault is: Using a stub branch as a presumed transit router can cause blackholes or make expected routes unavailable. Which recovery is BEST once this fault is identified?
- The controlled recovery is to increase hello timers instead of controlling query propagation into spoke edges.
- The controlled recovery is to configure the spoke as a transit backbone while claiming it will never carry transit.
- The controlled recovery is to disable all EIGRP advertisements from the branch and assume its networks stay reachable.
- The controlled recovery is to confirm spoke stub scope and reroute genuine intersite traffic through designated transit devices.
Explanation
Correct Answer
D:An EIGRP stub advertises its restricted transit role to reduce query scope and preserve scalable convergence. This corrects the described failure and provides a verifiable outcome.
Incorrect Answers
A:Increase hello timers instead of controlling query propagation into spoke edges. Using a stub branch as a presumed transit router can cause blackholes or make expected routes unavailable. Use the controlled remediation: confirm spoke stub scope and reroute genuine intersite traffic through designated transit devices.
B:Configure the spoke as a transit backbone while claiming it will never carry transit. Using a stub branch as a presumed transit router can cause blackholes or make expected routes unavailable. Use the controlled remediation: confirm spoke stub scope and reroute genuine intersite traffic through designated transit devices.
C:Disable all EIGRP advertisements from the branch and assume its networks stay reachable. Using a stub branch as a presumed transit router can cause blackholes or make expected routes unavailable. Use the controlled remediation: confirm spoke stub scope and reroute genuine intersite traffic through designated transit devices.