Cisco 300-420 Practice Test 5
Question 40
An enterprise wants selective interarea route availability while preventing unexpected transit through an access area. The observed fault is: Uncontrolled leaking or inconsistent metrics can create unexpected paths or excessive access-area routes. Which controlled remediation should be used?
- The controlled recovery is to assume changing a device hostname changes IS-IS shortest paths.
- The controlled recovery is to leak every Level-2 prefix into every Level-1 area without control.
- The controlled recovery is to correct metric and leaking policies then compare selected paths and table size.
- The controlled recovery is to assign arbitrary metrics without comparing link capacity and failure outcomes.
Explanation
Correct Answer
C:Relevant evidence includes iS-IS LSP metrics, area boundary routes, route-leak policy matches and active best paths. This corrects the described failure and provides a verifiable outcome.
Incorrect Answers
A:Assume changing a device hostname changes IS-IS shortest paths. Uncontrolled leaking or inconsistent metrics can create unexpected paths or excessive access-area routes. Use the controlled remediation: correct metric and leaking policies then compare selected paths and table size.
B:Leak every Level-2 prefix into every Level-1 area without control. Uncontrolled leaking or inconsistent metrics can create unexpected paths or excessive access-area routes. Use the controlled remediation: correct metric and leaking policies then compare selected paths and table size.
D:Assign arbitrary metrics without comparing link capacity and failure outcomes. Uncontrolled leaking or inconsistent metrics can create unexpected paths or excessive access-area routes. Use the controlled remediation: correct metric and leaking policies then compare selected paths and table size.
Question 41
An EIGRP enterprise needs smaller branch tables while preserving specific downstream subnets under a contiguous region block. What is the BEST supported implementation or corrective action?
- Summarize unrelated prefixes into an overly broad aggregate despite holes.
- Configure justified EIGRP interface-level summarization for contiguous prefixes at the intended boundary.
- Assume any pair of branch networks always forms a clean summary.
- Use route metrics as a substitute for verifying aggregate prefix coverage.
Explanation
Correct Answer
B:Manual EIGRP summarization reduces advertised detail but can create a discard route to avoid loops for the aggregate. This is the specific corrective action for EIGRP route summarization at distribution boundaries.
Incorrect Answers
A:An overbroad summary can blackhole traffic for prefixes that are not actually reachable behind that router. This change targets the wrong mechanism for EIGRP route summarization at distribution boundaries.
C:Assume any pair of branch networks always forms a clean summary. Manual EIGRP summarization reduces advertised detail but can create a discard route to avoid loops for the aggregate. Instead inspect eIGRP advertised prefix list, summary calculation, neighbor table and covered subnet reachability.
D:An overbroad summary can blackhole traffic for prefixes that are not actually reachable behind that router.
Question 42
An EIGRP enterprise needs smaller branch tables while preserving specific downstream subnets under a contiguous region block. What should the operator inspect to verify the result?
- A feature-license screenshot without the required design or acceptance tests.
- A marketing claim without measured routing, capacity or failure-domain evidence.
- EIGRP advertised prefix list, summary calculation, neighbor table and covered subnet reachability.
- A hostname inventory without effective configuration or operational measurements.
Explanation
Correct Answer
C:Manual EIGRP summarization reduces advertised detail but can create a discard route to avoid loops for the aggregate. This evidence observes the actual eIGRP route summarization at distribution boundaries mechanism and its result.
Incorrect Answers
A:This observation alone cannot establish eIGRP route summarization at distribution boundaries. Manual EIGRP summarization reduces advertised detail but can create a discard route to avoid loops for the aggregate.
B:This observation alone cannot establish eIGRP route summarization at distribution boundaries. The decisive evidence instead includes eIGRP advertised prefix list, summary calculation, neighbor table and covered subnet reachability.
D:This observation alone cannot establish eIGRP route summarization at distribution boundaries. A hostname inventory without effective configuration or operational measurements.
Question 43
An EIGRP enterprise needs smaller branch tables while preserving specific downstream subnets under a contiguous region block. Which technical statement is MOST accurate for this situation?
- Any single device automatically guarantees high availability for every site.
- Encryption and segmentation are identical mechanisms and can replace each other.
- Manual EIGRP summarization reduces advertised detail but can create a discard route to avoid loops for the aggregate.
- Cloud connectivity automatically removes any requirement for routing or policy.
Explanation
Correct Answer
C:This is why the appropriate action is configure justified EIGRP interface-level summarization for contiguous prefixes at the intended boundary. Confirm it with eIGRP advertised prefix list, summary calculation, neighbor table and covered subnet reachability.
Incorrect Answers
A:Any single device automatically guarantees high availability for every site. This is an incorrect generalization for eIGRP route summarization at distribution boundaries. The relevant rule is manual EIGRP summarization reduces advertised detail but can create a discard route to avoid loops for the aggregate. Verify using eIGRP advertised prefix list, summary calculation, neighbor table and covered subnet reachability.
B:Encryption and segmentation are identical mechanisms and can replace each other. This is an incorrect generalization for eIGRP route summarization at distribution boundaries. The relevant rule is manual EIGRP summarization reduces advertised detail but can create a discard route to avoid loops for the aggregate. Verify using eIGRP advertised prefix list, summary calculation, neighbor table and covered subnet reachability.
D:Cloud connectivity automatically removes any requirement for routing or policy. This is an incorrect generalization for eIGRP route summarization at distribution boundaries. The relevant rule is manual EIGRP summarization reduces advertised detail but can create a discard route to avoid loops for the aggregate. Verify using eIGRP advertised prefix list, summary calculation, neighbor table and covered subnet reachability.
Question 44
An EIGRP enterprise needs smaller branch tables while preserving specific downstream subnets under a contiguous region block. Suppose the operator instead makes this incorrect change: Summarize unrelated prefixes into an overly broad aggregate despite holes. What weakness does the mistaken approach introduce?
- The only issue is an inaccurate hostname while traffic paths are unaffected.
- A healthy unrelated system proves the intended failure domain is protected.
- An overbroad summary can blackhole traffic for prefixes that are not actually reachable behind that router.
- The failure is entirely cosmetic because all control-plane changes are harmless.
Explanation
Correct Answer
C:This explains why the proposed shortcut does not solve eIGRP route summarization at distribution boundaries. Manual EIGRP summarization reduces advertised detail but can create a discard route to avoid loops for the aggregate.
Incorrect Answers
A:The only issue is an inaccurate hostname while traffic paths are unaffected. The actual failure is an overbroad summary can blackhole traffic for prefixes that are not actually reachable behind that router. Check eIGRP advertised prefix list, summary calculation, neighbor table and covered subnet reachability.
B:A healthy unrelated system proves the intended failure domain is protected. The actual failure is an overbroad summary can blackhole traffic for prefixes that are not actually reachable behind that router. Check eIGRP advertised prefix list, summary calculation, neighbor table and covered subnet reachability.
D:The failure is entirely cosmetic because all control-plane changes are harmless. The actual failure is an overbroad summary can blackhole traffic for prefixes that are not actually reachable behind that router. Check eIGRP advertised prefix list, summary calculation, neighbor table and covered subnet reachability.
Question 45
An EIGRP enterprise needs smaller branch tables while preserving specific downstream subnets under a contiguous region block. The observed fault is: An overbroad summary can blackhole traffic for prefixes that are not actually reachable behind that router. Which recovery is BEST once this fault is identified?
- Assume any pair of branch networks always forms a clean summary.
- Use route metrics as a substitute for verifying aggregate prefix coverage.
- Summarize unrelated prefixes into an overly broad aggregate despite holes.
- 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. This corrects the described failure and provides a verifiable outcome.
Incorrect Answers
A: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.
B: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.
C: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.
Question 46
A distribution router has dozens of connected prefixes and the design calls for a stable outbound EIGRP summary. Which operator action most directly resolves this condition?
- For this enterprise design, the architect should assume any pair of branch networks always forms a clean summary.
- For this enterprise design, the architect should use route metrics as a substitute for verifying aggregate prefix coverage.
- For this enterprise design, the architect should summarize unrelated prefixes into an overly broad aggregate despite holes.
- For this enterprise design, the architect should configure justified EIGRP interface-level summarization for contiguous prefixes at the intended boundary.
Explanation
Correct Answer
D:Manual EIGRP summarization reduces advertised detail but can create a discard route to avoid loops for the aggregate. Confirm the result using eIGRP advertised prefix list, summary calculation, neighbor table and covered subnet reachability.
Incorrect Answers
A:Assume any pair of branch networks always forms a clean summary. Manual EIGRP summarization reduces advertised detail but can create a discard route to avoid loops for the aggregate. Instead inspect eIGRP advertised prefix list, summary calculation, neighbor table and covered subnet reachability.
B:An overbroad summary can blackhole traffic for prefixes that are not actually reachable behind that router. Use route metrics as a substitute for verifying aggregate prefix coverage.
C:An overbroad summary can blackhole traffic for prefixes that are not actually reachable behind that router. The relevant action is configure justified EIGRP interface-level summarization for contiguous prefixes at the intended boundary.
Question 47
A distribution router has dozens of connected prefixes and the design calls for a stable outbound EIGRP summary. Which collection of observations most directly tests the suspected cause?
- Inspect the following evidence: an old network diagram with no current route, policy, or redundancy state.
- Inspect the following evidence: eIGRP advertised prefix list, summary calculation, neighbor table and covered subnet reachability.
- Inspect the following evidence: a feature-license screenshot without the required design or acceptance tests.
- Inspect the following evidence: a marketing claim without measured routing, capacity or failure-domain evidence.
Explanation
Correct Answer
B:Manual EIGRP summarization reduces advertised detail but can create a discard route to avoid loops for the aggregate. The intended procedure is configure justified EIGRP interface-level summarization for contiguous prefixes at the intended boundary.
Incorrect Answers
A:This observation alone cannot establish eIGRP route summarization at distribution boundaries. An old network diagram with no current route, policy, or redundancy state.
C:This observation alone cannot establish eIGRP route summarization at distribution boundaries. A feature-license screenshot without the required design or acceptance tests.
D:This observation alone cannot establish eIGRP route summarization at distribution boundaries. A marketing claim without measured routing, capacity or failure-domain evidence.
Question 48
A distribution router has dozens of connected prefixes and the design calls for a stable outbound EIGRP summary. Which system behavior underlies the appropriate response?
- The relevant principle is that cloud connectivity automatically removes any requirement for routing or policy.
- The relevant principle is that any single device automatically guarantees high availability for every site.
- The relevant principle is that a longer IP prefix is always less specific than the default route.
- The relevant principle is that manual EIGRP summarization reduces advertised detail but can create a discard route to avoid loops for the aggregate.
Explanation
Correct Answer
D:This is why the appropriate action is configure justified EIGRP interface-level summarization for contiguous prefixes at the intended boundary. Manual EIGRP summarization reduces advertised detail but can create a discard route to avoid loops for the aggregate.
Incorrect Answers
A:Cloud connectivity automatically removes any requirement for routing or policy. This is an incorrect generalization for eIGRP route summarization at distribution boundaries. The relevant rule is manual EIGRP summarization reduces advertised detail but can create a discard route to avoid loops for the aggregate. Verify using eIGRP advertised prefix list, summary calculation, neighbor table and covered subnet reachability.
B:Any single device automatically guarantees high availability for every site. This is an incorrect generalization for eIGRP route summarization at distribution boundaries. The relevant rule is manual EIGRP summarization reduces advertised detail but can create a discard route to avoid loops for the aggregate. Verify using eIGRP advertised prefix list, summary calculation, neighbor table and covered subnet reachability.
C:A longer IP prefix is always less specific than the default route. This is an incorrect generalization for eIGRP route summarization at distribution boundaries. The relevant rule is manual EIGRP summarization reduces advertised detail but can create a discard route to avoid loops for the aggregate. Verify using eIGRP advertised prefix list, summary calculation, neighbor table and covered subnet reachability.
Question 49
A distribution router has dozens of connected prefixes and the design calls for a stable outbound EIGRP summary. Suppose the operator instead makes this incorrect change: Summarize unrelated prefixes into an overly broad aggregate despite holes. Which failure or risk follows from this shortcut?
- The resulting technical fault is that the failure is entirely cosmetic because all control-plane changes are harmless.
- The resulting technical fault is that collecting telemetry originally caused the missing route or service outage.
- The resulting technical fault is that a healthy unrelated system proves the intended failure domain is protected.
- The resulting technical fault is that an overbroad summary can blackhole traffic for prefixes that are not actually reachable behind that router.
Explanation
Correct Answer
D:This explains why the proposed shortcut does not solve eIGRP route summarization at distribution boundaries. The right response is configure justified EIGRP interface-level summarization for contiguous prefixes at the intended boundary.
Incorrect Answers
A:The failure is entirely cosmetic because all control-plane changes are harmless. The actual failure is an overbroad summary can blackhole traffic for prefixes that are not actually reachable behind that router. Check eIGRP advertised prefix list, summary calculation, neighbor table and covered subnet reachability.
B:Collecting telemetry originally caused the missing route or service outage. The actual failure is an overbroad summary can blackhole traffic for prefixes that are not actually reachable behind that router. Check eIGRP advertised prefix list, summary calculation, neighbor table and covered subnet reachability.
C:A healthy unrelated system proves the intended failure domain is protected. The actual failure is an overbroad summary can blackhole traffic for prefixes that are not actually reachable behind that router. Check eIGRP advertised prefix list, summary calculation, neighbor table and covered subnet reachability.
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.