Cisco 300-410 Practice Test 19
Question 180
During a scheduled validation at the Naperville service-provider handoff, a collector reports no new application-flow records after a router refresh although interfaces pass traffic normally. Engineers must restore a customer routing segment without disturbing unrelated production services. The attempted fix creates a regression. Which scoped recovery action is most appropriate?
- Disable the newly enabled SCP service if authorization permits unapproved file access.
- Detach the monitor if it consumes excessive resources on an unsupported interface.
- Remove the new relay if replies reach the wrong IPv6 segment.
- Restore the previous exporter path if exports accidentally reach an external untrusted collector.
Explanation
Correct Answer
B:Detach the monitor if it consumes excessive resources on an unsupported interface. Flexible NetFlow requires a record/monitor and an appropriate interface or platform attachment to observe flows.
Incorrect Answers
A:Disable the newly enabled SCP service if authorization permits unapproved file access. This is a rollback for a different component (SCP configuration backup), where SCP uses SSH transport but requires appropriate service support and file privileges. Here the evidence instead concerns flexible netflow monitor attachment: Flexible NetFlow requires a record/monitor and an appropriate interface or platform attachment to observe flows.
C:Remove the new relay if replies reach the wrong IPv6 segment. This is a rollback for a different component (DHCPv6 relay), where DHCPv6 relaying transports client messages to a remote server; Router Advertisements still convey default-router details. Here the evidence instead concerns flexible netflow monitor attachment: Flexible NetFlow requires a record/monitor and an appropriate interface or platform attachment to observe flows.
D: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 flexible netflow monitor attachment: Flexible NetFlow requires a record/monitor and an appropriate interface or platform attachment to observe flows.
Question 181
Following a production change at the Bismarck remote operations location, a newly inserted extended ACL permit entry never allows the desired HTTPS flow because an earlier broad deny matches it. 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 ACL type, source-only matching, direction, and placement relative to branch and destination.
- Read ACL entries in sequence and review hit counts for the relevant source, destination, protocol, and port.
- Inspect the separate IPv6 ACL and IPv6 traffic-filter binding on the intended interface and direction.
- Inspect ACL time-range references, active time-range status, and router clock/time zone.
Explanation
Correct Answer
B:Read ACL entries in sequence and review hit counts for the relevant source, destination, protocol, and port. Extended ACL processing stops on the first matching entry, followed by an implicit deny if none matches.
Incorrect Answers
A:Check ACL type, source-only matching, direction, and placement relative to branch and destination. This is an investigation for a different failure condition (Standard IPv4 ACL placement), where Standard IPv4 ACLs match source addresses, so placement can cause unintended broad filtering. Here the evidence instead concerns extended acl first-match semantics: Extended ACL processing stops on the first matching entry, followed by an implicit deny if none matches.
C:Inspect the separate IPv6 ACL and IPv6 traffic-filter binding on the intended interface and direction. This is an investigation for a different failure condition (IPv6 traffic-filter placement), where IPv4 ACLs do not filter IPv6 packets; IPv6 traffic filters require their own attachment and careful ICMPv6 treatment. Here the evidence instead concerns extended acl first-match semantics: Extended ACL processing stops on the first matching entry, followed by an implicit deny if none matches.
D:Inspect ACL time-range references, active time-range status, and router clock/time zone. This is an investigation for a different failure condition (Time-based ACL), where Time-based ACL entries depend on correct local time and an actively applied time-range definition. Here the evidence instead concerns extended acl first-match semantics: Extended ACL processing stops on the first matching entry, followed by an implicit deny if none matches.
Question 182
Following a production change at the Bismarck remote operations location, a newly inserted extended ACL permit entry never allows the desired HTTPS flow because an earlier broad deny matches it. 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?
- Move the specific desired permit above the broader deny while preserving least-privilege bounds.
- Use a policy or feasible uRPF mode appropriate for intentional asymmetry, or correct source routing where possible.
- Enable supported ND inspection and guard policies on the affected access segment with proper trust boundaries.
- Apply an appropriately scoped IPv6 access list in the correct direction without relying on IPv4 ACL behavior.
Explanation
Correct Answer
A:Move the specific desired permit above the broader deny while preserving least-privilege bounds. Extended ACL processing stops on the first matching entry, followed by an implicit deny if none matches.
Incorrect Answers
B:Use a policy or feasible uRPF mode appropriate for intentional asymmetry, or correct source routing where possible. This is a configuration change for a different root cause (Strict uRPF asymmetric routing), where Strict uRPF can reject a packet when the best reverse route points to an interface other than its ingress. Here the evidence instead concerns extended acl first-match semantics: Extended ACL processing stops on the first matching entry, followed by an implicit deny if none matches.
C:Enable supported ND inspection and guard policies on the affected access segment with proper trust boundaries. This is a configuration change for a different root cause (IPv6 Neighbor Discovery inspection), where IPv6 ND inspection uses neighbor state and filtering to mitigate neighbor-discovery spoofing. Here the evidence instead concerns extended acl first-match semantics: Extended ACL processing stops on the first matching entry, followed by an implicit deny if none matches.
D:Apply an appropriately scoped IPv6 access list in the correct direction without relying on IPv4 ACL behavior. This is a configuration change for a different root cause (IPv6 traffic-filter placement), where IPv4 ACLs do not filter IPv6 packets; IPv6 traffic filters require their own attachment and careful ICMPv6 treatment. Here the evidence instead concerns extended acl first-match semantics: Extended ACL processing stops on the first matching entry, followed by an implicit deny if none matches.
Question 183
Following a production change at the Bismarck remote operations location, a newly inserted extended ACL permit entry never allows the desired HTTPS flow because an earlier broad deny matches it. The incident is affecting a monitored campus segment; the response team has a rollback window. Which verification result would provide the most relevant acceptance evidence?
- Verify monitoring traffic is permitted and nonapproved sources remain blocked.
- Verify the intended flow matches the new entry and previously denied services remain blocked.
- Test the matching IPv6 flows and required neighbor discovery traffic after deployment.
- Test traffic during and after the authorized window and inspect relevant ACL hit counts.
Explanation
Correct Answer
B:Verify the intended flow matches the new entry and previously denied services remain blocked. Extended ACL processing stops on the first matching entry, followed by an implicit deny if none matches.
Incorrect Answers
A:Verify monitoring traffic is permitted and nonapproved sources remain blocked. This is a validation for another mechanism (ACL implicit deny), where IP access lists implicitly deny traffic that matches no explicit permit statement. Here the evidence instead concerns extended acl first-match semantics: Extended ACL processing stops on the first matching entry, followed by an implicit deny if none matches.
C:Test the matching IPv6 flows and required neighbor discovery traffic after deployment. This is a validation for another mechanism (IPv6 traffic-filter placement), where IPv4 ACLs do not filter IPv6 packets; IPv6 traffic filters require their own attachment and careful ICMPv6 treatment. Here the evidence instead concerns extended acl first-match semantics: Extended ACL processing stops on the first matching entry, followed by an implicit deny if none matches.
D:Test traffic during and after the authorized window and inspect relevant ACL hit counts. This is a validation for another mechanism (Time-based ACL), where Time-based ACL entries depend on correct local time and an actively applied time-range definition. Here the evidence instead concerns extended acl first-match semantics: Extended ACL processing stops on the first matching entry, followed by an implicit deny if none matches.
Question 184
Following a production change at the Bismarck remote operations location, a newly inserted extended ACL permit entry never allows the desired HTTPS flow because an earlier broad deny matches it. The incident is affecting a monitored campus segment; the response team has a rollback window. Which TWO complementary steps provide both relevant fault isolation and a controlled correction?
- Move the specific desired permit above the broader deny while preserving least-privilege bounds.
- Place the standard ACL nearer the intended destination or use a scoped extended ACL when destination precision is required.
- Inspect ACL time-range references, active time-range status, and router clock/time zone.
- Read ACL entries in sequence and review hit counts for the relevant source, destination, protocol, and port.
Explanation
Correct Answers
A:Move the specific desired permit above the broader deny while preserving least-privilege bounds. Extended ACL processing stops on the first matching entry, followed by an implicit deny if none matches.
D:Read ACL entries in sequence and review hit counts for the relevant source, destination, protocol, and port. Extended ACL processing stops on the first matching entry, followed by an implicit deny if none matches.
Incorrect Answers
B:Place the standard ACL nearer the intended destination or use a scoped extended ACL when destination precision is required. This is a configuration change for a different root cause (Standard IPv4 ACL placement), where Standard IPv4 ACLs match source addresses, so placement can cause unintended broad filtering. Here the evidence instead concerns extended acl first-match semantics: Extended ACL processing stops on the first matching entry, followed by an implicit deny if none matches.
C:Inspect ACL time-range references, active time-range status, and router clock/time zone. This is an investigation for a different failure condition (Time-based ACL), where Time-based ACL entries depend on correct local time and an actively applied time-range definition. Here the evidence instead concerns extended acl first-match semantics: Extended ACL processing stops on the first matching entry, followed by an implicit deny if none matches.
Question 185
During a scheduled validation at the Denver hospital campus, routers in an OSPF stub area repeatedly fail adjacency after one side is configured as a normal area. 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.
- Check the area ID on the actual peering interfaces on both sides.
- Inspect the OSPF process router IDs and compare them across the affected area.
- Compare OSPF stub flags and area type on every router participating in the area.
Explanation
Correct Answer
D:Compare OSPF stub flags and area type on every router participating in the area. Stub-area option consistency is enforced when OSPF neighbors negotiate adjacency.
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 stub option mismatch: Stub-area option consistency is enforced when OSPF neighbors negotiate adjacency.
B:Check the area ID on the actual peering interfaces on both sides. This is an investigation for a different failure condition (OSPF area mismatch), where OSPF neighbors must agree on the local link's area ID. Here the evidence instead concerns ospf stub option mismatch: Stub-area option consistency is enforced when OSPF neighbors negotiate adjacency.
C: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 stub option mismatch: Stub-area option consistency is enforced when OSPF neighbors negotiate adjacency.
Question 186
During a scheduled validation at the Denver hospital campus, routers in an OSPF stub area repeatedly fail adjacency after one side is configured as a normal area. Engineers must restore remote-site route stability without disturbing unrelated production services. Which targeted configuration or policy correction best resolves the described fault?
- Make stub-area settings consistent across the area, including its ABRs.
- Configure matching OSPF virtual-link endpoints by ABR router ID across an eligible nonstub transit area.
- Assign a unique stable router ID to the conflicting router and restart the process in a controlled window if necessary.
- Correct the NSSA ABR translation or external-advertisement policy for the approved prefixes.
Explanation
Correct Answer
A:Make stub-area settings consistent across the area, including its ABRs. Stub-area option consistency is enforced when OSPF neighbors negotiate adjacency.
Incorrect Answers
B:Configure matching OSPF virtual-link endpoints by ABR router ID across an eligible nonstub transit area. This is a configuration change for a different root cause (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 stub option mismatch: Stub-area option consistency is enforced when OSPF neighbors negotiate adjacency.
C:Assign a unique stable router ID to the conflicting router and restart the process in a controlled window if necessary. This is a configuration change for a different root cause (OSPF duplicate router ID), where OSPF uses router IDs as unique LSA originator identities within the routing domain. Here the evidence instead concerns ospf stub option mismatch: Stub-area option consistency is enforced when OSPF neighbors negotiate adjacency.
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 stub option mismatch: Stub-area option consistency is enforced when OSPF neighbors negotiate adjacency.
Question 187
During a scheduled validation at the Denver hospital campus, routers in an OSPF stub area repeatedly fail adjacency after one side is configured as a normal area. Engineers must restore remote-site route stability without disturbing unrelated production services. Which post-change check most directly establishes that the repair is correct?
- Confirm the external prefix appears as Type 7 within NSSA and translated Type 5 where required.
- Observe the neighbor reach Full state with stable hellos after correction.
- Verify unique IDs in neighbor views and LSDB originators with stable LSA propagation.
- Verify neighbors form and the area receives the expected default route instead of external Type 5 LSAs.
Explanation
Correct Answer
D:Verify neighbors form and the area receives the expected default route instead of external Type 5 LSAs. Stub-area option consistency is enforced when OSPF neighbors negotiate adjacency.
Incorrect Answers
A: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 stub option mismatch: Stub-area option consistency is enforced when OSPF neighbors negotiate adjacency.
B:Observe the neighbor reach Full state with stable hellos after correction. This is a validation for another mechanism (OSPF hello and dead timers), where OSPF timer compatibility is necessary for adjacency formation on a common segment. Here the evidence instead concerns ospf stub option mismatch: Stub-area option consistency is enforced when OSPF neighbors negotiate adjacency.
C:Verify unique IDs in neighbor views and LSDB originators with stable LSA propagation. This is a validation for another mechanism (OSPF duplicate router ID), where OSPF uses router IDs as unique LSA originator identities within the routing domain. Here the evidence instead concerns ospf stub option mismatch: Stub-area option consistency is enforced when OSPF neighbors negotiate adjacency.
Question 188
During a scheduled validation at the Denver hospital campus, routers in an OSPF stub area repeatedly fail adjacency after one side is configured as a normal area. 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.
- Make stub-area settings consistent across the area, including its ABRs.
- Trace Type 7 LSAs inside the NSSA and the ABR's Type 7-to-Type 5 translation behavior.
- Configure matching OSPF virtual-link endpoints by ABR router ID across an eligible nonstub transit area.
- Compare OSPF stub flags and area type on every router participating in the area.
Explanation
Correct Answers
A:Make stub-area settings consistent across the area, including its ABRs. Stub-area option consistency is enforced when OSPF neighbors negotiate adjacency.
D:Compare OSPF stub flags and area type on every router participating in the area. Stub-area option consistency is enforced when OSPF neighbors negotiate adjacency.
Incorrect Answers
B:Trace Type 7 LSAs inside the NSSA and the ABR's Type 7-to-Type 5 translation behavior. This is an investigation for a different failure condition (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 stub option mismatch: Stub-area option consistency is enforced when OSPF neighbors negotiate adjacency.
C:Configure matching OSPF virtual-link endpoints by ABR router ID across an eligible nonstub transit area. This is a configuration change for a different root cause (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 stub option mismatch: Stub-area option consistency is enforced when OSPF neighbors negotiate adjacency.
Question 189
Following a production change at the Aurora remote operations location, a router learns 10.44.0.0/16 from OSPF and from a floating static route, but the static next hop is used even while OSPF 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 route's selected source, prefix length, and administrative distance in the routing table.
- Compare summary reachability with the actual set of component subnets and the summary discard route.
- Trace route tags and redistribution points to identify reintroduction of the same route.
- Check whether the EIGRP redistribution policy supplies a usable seed metric.
Explanation
Correct Answer
A:Inspect the route's selected source, prefix length, and administrative distance in the routing table. For the same destination prefix, the router prefers the eligible route with the lower administrative distance after longest-prefix selection.
Incorrect Answers
B: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 administrative distance: For the same destination prefix, the router prefers the eligible route with the lower administrative distance after longest-prefix selection.
C:Trace route tags and redistribution points to identify reintroduction of the same route. This is an investigation for a different failure condition (Redistribution loop prevention tags), where Consistent route tagging and inbound redistribution filters help prevent feedback loops across routing domains. Here the evidence instead concerns administrative distance: For the same destination prefix, the router prefers the eligible route with the lower administrative distance after longest-prefix selection.
D:Check whether the EIGRP redistribution policy supplies a usable seed metric. This is an investigation for a different failure condition (EIGRP redistribution seed metric), where EIGRP redistribution generally needs an appropriate seed metric for external routes. Here the evidence instead concerns administrative distance: For the same destination prefix, the router prefers the eligible route with the lower administrative distance after longest-prefix selection.
Question 190
Following a production change at the Aurora remote operations location, a router learns 10.44.0.0/16 from OSPF and from a floating static route, but the static next hop is used even while OSPF 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?
- Tag routes on first redistribution and deny that tag when importing them back into the source domain.
- Allow the intended subnet with classless redistribution and a scoped route map instead of exporting everything.
- Raise the static route's distance above the intended OSPF route or remove the unwanted override.
- Correct the more-specific route or its advertisement if it is unintended; do not only change the aggregate's distance.
Explanation
Correct Answer
C:Raise the static route's distance above the intended OSPF route or remove the unwanted override. For the same destination prefix, the router prefers the eligible route with the lower administrative distance after longest-prefix selection.
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 administrative distance: For the same destination prefix, the router prefers the eligible route with the lower administrative distance after longest-prefix selection.
B:Allow the intended subnet with classless redistribution and a scoped route map instead of exporting everything. This is a configuration change for a different root cause (OSPF classless redistribution), where Redistribution must explicitly cover intended classless networks while avoiding uncontrolled route leakage. Here the evidence instead concerns administrative distance: For the same destination prefix, the router prefers the eligible route with the lower administrative distance after longest-prefix selection.
D:Correct the more-specific route or its advertisement if it is unintended; do not only change the aggregate's distance. This is a configuration change for a different root cause (Longest-prefix selection), where A longer matching prefix is selected before administrative distance is compared among equal-length routes. Here the evidence instead concerns administrative distance: For the same destination prefix, the router prefers the eligible route with the lower administrative distance after longest-prefix selection.