Cisco 300-410 Practice Test 79
Question 780
Following a production change at the Salem regional hub, a network operator can log in to a router but receives authorization failures for permitted show commands after a TACACS+ policy update. The incident is affecting a voice service path; the response team has a rollback window. The new configuration worsens service. Which controlled rollback should the team perform?
- Restore the prior accounting configuration if new statements overwhelm the server or expose secrets.
- Remove temporary fallback users and reinstate previous line bindings if the recovery test fails.
- Restore prior ACL placement if unrelated production flows become blocked.
- Restore the previous server command set if the change unintentionally expands administrator access.
Explanation
Correct Answer
D:Restore the previous server command set if the change unintentionally expands administrator access. TACACS+ can authorize individual CLI commands separately from successful login authentication.
Incorrect Answers
A:Restore the prior accounting configuration if new statements overwhelm the server or expose secrets. This is a rollback for a different component (AAA accounting records), where AAA accounting is distinct from authentication and authorization and must be explicitly configured for required events. Here the evidence instead concerns tacacs+ command authorization: TACACS+ can authorize individual CLI commands separately from successful login authentication.
B:Remove temporary fallback users and reinstate previous line bindings if the recovery test fails. This is a rollback for a different component (AAA local user authentication), where A local fallback requires valid local users and an AAA login method list that actually references the local database. Here the evidence instead concerns tacacs+ command authorization: TACACS+ can authorize individual CLI commands separately from successful login authentication.
C:Restore prior ACL placement if unrelated production flows become blocked. This is a rollback for a different component (Standard IPv4 ACL placement), where Standard IPv4 ACLs match source addresses, so placement can cause unintended broad filtering. Here the evidence instead concerns tacacs+ command authorization: TACACS+ can authorize individual CLI commands separately from successful login authentication.
Question 781
Following a production change at the Eugene service-provider handoff, clients on a newly added routed VLAN send DHCP Discover broadcasts but receive no offers from a central server on another subnet. The incident is affecting a business-critical application; the response team has a rollback window. Which observation is the strongest first diagnostic check for this symptom?
- Check community string, configured NMS source ACL, UDP 161 reachability, and SNMP service counters.
- Inspect flow record, flow monitor, and whether the monitor is attached in the intended interface direction.
- Inspect Cisco Catalyst Center Assurance client health, onboarding timeline, and application reachability signals.
- Inspect the client VLAN gateway's helper address, routed path to server, and DHCP relay forwarding.
Explanation
Correct Answer
D:Inspect the client VLAN gateway's helper address, routed path to server, and DHCP relay forwarding. IPv4 DHCP Discover broadcasts require a relay when the DHCP server resides beyond a Layer 3 boundary.
Incorrect Answers
A:Check community string, configured NMS source ACL, UDP 161 reachability, and SNMP service counters. This is an investigation for a different failure condition (SNMPv2c read access), where SNMPv2c community matching and ACL restrictions determine polling access, but v2c itself lacks modern encryption. Here the evidence instead concerns ipv4 dhcp relay: IPv4 DHCP Discover broadcasts require a relay when the DHCP server resides beyond a Layer 3 boundary.
B:Inspect flow record, flow monitor, and whether the monitor is attached in the intended interface direction. This is an investigation for a different failure condition (Flexible NetFlow monitor attachment), where Flexible NetFlow requires a record/monitor and an appropriate interface or platform attachment to observe flows. Here the evidence instead concerns ipv4 dhcp relay: IPv4 DHCP Discover broadcasts require a relay when the DHCP server resides beyond a Layer 3 boundary.
C:Inspect Cisco Catalyst Center Assurance client health, onboarding timeline, and application reachability signals. This is an investigation for a different failure condition (Catalyst Center client assurance), where Catalyst Center Assurance correlates client experience with network/device telemetry to support diagnosis. Here the evidence instead concerns ipv4 dhcp relay: IPv4 DHCP Discover broadcasts require a relay when the DHCP server resides beyond a Layer 3 boundary.
Question 782
Following a production change at the Eugene service-provider handoff, clients on a newly added routed VLAN send DHCP Discover broadcasts but receive no offers from a central server on another subnet. The incident is affecting a business-critical application; the response team has a rollback window. What change best addresses the root mechanism without unnecessarily changing other paths?
- Configure the correct ip helper-address on the client-facing routed interface.
- Generate an appropriate RSA key pair and enable the supported SSH server configuration.
- Correct the IOS DHCP pool default-router option and renew affected leases.
- Exclude the reserved range from automatic assignment and correct affected leases.
Explanation
Correct Answer
A:Configure the correct ip helper-address on the client-facing routed interface. IPv4 DHCP Discover broadcasts require a relay when the DHCP server resides beyond a Layer 3 boundary.
Incorrect Answers
B:Generate an appropriate RSA key pair and enable the supported SSH server configuration. This is a configuration change for a different root cause (SSH prerequisites), where A Cisco IOS SSH server needs valid crypto key material and compatible session settings. Here the evidence instead concerns ipv4 dhcp relay: IPv4 DHCP Discover broadcasts require a relay when the DHCP server resides beyond a Layer 3 boundary.
C:Correct the IOS DHCP pool default-router option and renew affected leases. This is a configuration change for a different root cause (DHCP default-router option), where DHCP option 3/default-router tells IPv4 clients which gateway to use; leases can be valid despite a wrong option. Here the evidence instead concerns ipv4 dhcp relay: IPv4 DHCP Discover broadcasts require a relay when the DHCP server resides beyond a Layer 3 boundary.
D:Exclude the reserved range from automatic assignment and correct affected leases. This is a configuration change for a different root cause (DHCP address exclusions), where IOS DHCP address exclusions keep reserved addresses out of automatic lease allocation. Here the evidence instead concerns ipv4 dhcp relay: IPv4 DHCP Discover broadcasts require a relay when the DHCP server resides beyond a Layer 3 boundary.
Question 783
Following a production change at the Eugene service-provider handoff, clients on a newly added routed VLAN send DHCP Discover broadcasts but receive no offers from a central server on another subnet. The incident is affecting a business-critical application; the response team has a rollback window. Which verification result would provide the most relevant acceptance evidence?
- Capture a relay-generated request and verify the server replies with a lease for the client's subnet.
- Simulate upstream failure and confirm the tracked route withdraws while backup routing activates.
- Request new test leases and confirm no protected printer address is offered.
- Verify a test client receives the correct gateway and can reach a remote subnet.
Explanation
Correct Answer
A:Capture a relay-generated request and verify the server replies with a lease for the client's subnet. IPv4 DHCP Discover broadcasts require a relay when the DHCP server resides beyond a Layer 3 boundary.
Incorrect Answers
B:Simulate upstream failure and confirm the tracked route withdraws while backup routing activates. This is a validation for another mechanism (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 ipv4 dhcp relay: IPv4 DHCP Discover broadcasts require a relay when the DHCP server resides beyond a Layer 3 boundary.
C:Request new test leases and confirm no protected printer address is offered. This is a validation for another mechanism (DHCP address exclusions), where IOS DHCP address exclusions keep reserved addresses out of automatic lease allocation. Here the evidence instead concerns ipv4 dhcp relay: IPv4 DHCP Discover broadcasts require a relay when the DHCP server resides beyond a Layer 3 boundary.
D:Verify a test client receives the correct gateway and can reach a remote subnet. This is a validation for another mechanism (DHCP default-router option), where DHCP option 3/default-router tells IPv4 clients which gateway to use; leases can be valid despite a wrong option. Here the evidence instead concerns ipv4 dhcp relay: IPv4 DHCP Discover broadcasts require a relay when the DHCP server resides beyond a Layer 3 boundary.
Question 784
Following a production change at the Eugene service-provider handoff, clients on a newly added routed VLAN send DHCP Discover broadcasts but receive no offers from a central server on another subnet. The incident is affecting a business-critical application; the response team has a rollback window. Which TWO complementary steps provide both relevant fault isolation and a controlled correction?
- Inspect the lease's default-router option and compare it with the actual VLAN gateway.
- Exclude the reserved range from automatic assignment and correct affected leases.
- Inspect the client VLAN gateway's helper address, routed path to server, and DHCP relay forwarding.
- Configure the correct ip helper-address on the client-facing routed interface.
Explanation
Correct Answers
C:Inspect the client VLAN gateway's helper address, routed path to server, and DHCP relay forwarding. IPv4 DHCP Discover broadcasts require a relay when the DHCP server resides beyond a Layer 3 boundary.
D:Configure the correct ip helper-address on the client-facing routed interface. IPv4 DHCP Discover broadcasts require a relay when the DHCP server resides beyond a Layer 3 boundary.
Incorrect Answers
A:Inspect the lease's default-router option and compare it with the actual VLAN gateway. This is an investigation for a different failure condition (DHCP default-router option), where DHCP option 3/default-router tells IPv4 clients which gateway to use; leases can be valid despite a wrong option. Here the evidence instead concerns ipv4 dhcp relay: IPv4 DHCP Discover broadcasts require a relay when the DHCP server resides beyond a Layer 3 boundary.
B:Exclude the reserved range from automatic assignment and correct affected leases. This is a configuration change for a different root cause (DHCP address exclusions), where IOS DHCP address exclusions keep reserved addresses out of automatic lease allocation. Here the evidence instead concerns ipv4 dhcp relay: IPv4 DHCP Discover broadcasts require a relay when the DHCP server resides beyond a Layer 3 boundary.
Question 785
Following a production change at the Edison hospital campus, a route map is defined for steering finance traffic to a backup next hop, but packets still follow the normal routing table. 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?
- Trace Type 7 LSAs inside the NSSA and the ABR's Type 7-to-Type 5 translation behavior.
- Check the incoming interface's policy attachment and ACL matches for the affected source traffic.
- Compare the alternate neighbor's reported distance with the current successor's feasible distance.
- Compare the configured EIGRP autonomous-system numbers and active interface participation.
Explanation
Correct Answer
B:Check the incoming interface's policy attachment and ACL matches for the affected source traffic. Interface policy-based routing must be attached to the ingress path and match the intended traffic.
Incorrect Answers
A: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 policy-based routing ingress interface: Interface policy-based routing must be attached to the ingress path and match the intended traffic.
C: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 policy-based routing ingress interface: Interface policy-based routing must be attached to the ingress path and match the intended traffic.
D:Compare the configured EIGRP autonomous-system numbers and active interface participation. This is an investigation for a different failure condition (EIGRP AS mismatch), where EIGRP neighbors for an address family need compatible autonomous-system association and interface settings. Here the evidence instead concerns policy-based routing ingress interface: Interface policy-based routing must be attached to the ingress path and match the intended traffic.
Question 786
Following a production change at the Edison hospital campus, a route map is defined for steering finance traffic to a backup next hop, but packets still follow the normal routing table. 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?
- Apply the correct policy route map inbound on the ingress interface after verifying its match scope.
- Configure matching OSPF virtual-link endpoints by ABR router ID across an eligible nonstub transit area.
- Correct the more-specific route or its advertisement if it is unintended; do not only change the aggregate's distance.
- Configure the intended EIGRP stub behavior and advertise only approved connected or summary routes.
Explanation
Correct Answer
A:Apply the correct policy route map inbound on the ingress interface after verifying its match scope. Interface policy-based routing must be attached to the ingress path and match the intended traffic.
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 policy-based routing ingress interface: Interface policy-based routing must be attached to the ingress path and match the intended traffic.
C: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 policy-based routing ingress interface: Interface policy-based routing must be attached to the ingress path and match the intended traffic.
D: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 policy-based routing ingress interface: Interface policy-based routing must be attached to the ingress path and match the intended traffic.
Question 787
Following a production change at the Edison hospital campus, a route map is defined for steering finance traffic to a backup next hop, but packets still follow the normal routing table. 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?
- Use a destination-specific forwarding lookup to confirm which most-specific route is selected.
- Confirm the route appears only in the selected VRF and end-to-end tenant probes work.
- Use interface policy statistics and controlled test flows to prove matching packets take the alternate next hop.
- Verify externally observed paths show the intended extra AS hops without losing prefix reachability.
Explanation
Correct Answer
C:Use interface policy statistics and controlled test flows to prove matching packets take the alternate next hop. Interface policy-based routing must be attached to the ingress path and match the intended traffic.
Incorrect Answers
A:Use a destination-specific forwarding lookup to confirm which most-specific route is selected. This is a validation for another mechanism (Longest-prefix selection), where A longer matching prefix is selected before administrative distance is compared among equal-length routes. Here the evidence instead concerns policy-based routing ingress interface: Interface policy-based routing must be attached to the ingress path and match the intended traffic.
B:Confirm the route appears only in the selected VRF and end-to-end tenant probes work. This is a validation for another mechanism (VRF-Lite interface isolation), where VRF-Lite uses separate routing tables, and assigning VRF forwarding to an interface can reset its IP address. Here the evidence instead concerns policy-based routing ingress interface: Interface policy-based routing must be attached to the ingress path and match the intended traffic.
D:Verify externally observed paths show the intended extra AS hops without losing prefix reachability. This is a validation for another mechanism (BGP inbound traffic engineering), where AS-path prepending can make an advertised path less attractive to remote BGP networks, but cannot guarantee inbound routing. Here the evidence instead concerns policy-based routing ingress interface: Interface policy-based routing must be attached to the ingress path and match the intended traffic.
Question 788
Following a production change at the Edison hospital campus, a route map is defined for steering finance traffic to a backup next hop, but packets still follow the normal routing table. 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?
- Apply the correct policy route map inbound on the ingress interface after verifying its match scope.
- Inspect local preference distributed in iBGP along with route selection results.
- Apply a scoped local policy route map for router-generated packets if that behavior is required.
- Check the incoming interface's policy attachment and ACL matches for the affected source traffic.
Explanation
Correct Answers
A:Apply the correct policy route map inbound on the ingress interface after verifying its match scope. Interface policy-based routing must be attached to the ingress path and match the intended traffic.
D:Check the incoming interface's policy attachment and ACL matches for the affected source traffic. Interface policy-based routing must be attached to the ingress path and match the intended traffic.
Incorrect Answers
B:Inspect local preference distributed in iBGP along with route selection results. This is an investigation for a different failure condition (BGP outbound path local preference), where Within an AS, higher BGP local preference normally wins before AS-path length and MED. Here the evidence instead concerns policy-based routing ingress interface: Interface policy-based routing must be attached to the ingress path and match the intended traffic.
C:Apply a scoped local policy route map for router-generated packets if that behavior is required. This is a configuration change for a different root cause (Locally generated PBR), where Transit PBR on an interface does not automatically change forwarding of locally originated packets. Here the evidence instead concerns policy-based routing ingress interface: Interface policy-based routing must be attached to the ingress path and match the intended traffic.
Question 789
Following a production change at the Roanoke service-provider handoff, an aggregate static route through the WAN is present, yet traffic for one subnet follows a separate path learned through a dynamic protocol. 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 route-map sequence order, each match condition, and hit counts against the missing prefixes.
- Compare summary reachability with the actual set of component subnets and the summary discard route.
- Inspect TCP reachability and confirm the neighbor's configured remote-as matches its new AS.
- Compare the destination's matching prefixes and their lengths, not merely route-source preference.
Explanation
Correct Answer
D:Compare the destination's matching prefixes and their lengths, not merely route-source preference. A longer matching prefix is selected before administrative distance is compared among equal-length routes.
Incorrect Answers
A:Inspect route-map sequence order, each match condition, and hit counts against the missing prefixes. This is an investigation for a different failure condition (Route-map permit sequence), where Route maps are processed by ordered sequence; the first matching clause determines the permit or deny action. Here the evidence instead concerns longest-prefix selection: A longer matching prefix is selected before administrative distance is compared among equal-length routes.
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 longest-prefix selection: A longer matching prefix is selected before administrative distance is compared among equal-length routes.
C:Inspect TCP reachability and confirm the neighbor's configured remote-as matches its new AS. This is an investigation for a different failure condition (BGP peer remote AS), where BGP neighbors must agree on configured peer AS identity and establish a TCP session. Here the evidence instead concerns longest-prefix selection: A longer matching prefix is selected before administrative distance is compared among equal-length routes.
Question 790
Following a production change at the Roanoke service-provider handoff, an aggregate static route through the WAN is present, yet traffic for one subnet follows a separate path learned through a dynamic protocol. 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?
- 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.
- Put the intended permit conditions before the catch-all deny or narrow the deny match.
- Allow the intended subnet with classless redistribution and a scoped route map instead of exporting everything.
Explanation
Correct Answer
B:Correct the more-specific route or its advertisement if it is unintended; do not only change the aggregate's distance. A longer matching prefix is selected before administrative distance is compared among equal-length routes.
Incorrect Answers
A: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 longest-prefix selection: A longer matching prefix is selected before administrative distance is compared among equal-length routes.
C:Put the intended permit conditions before the catch-all deny or narrow the deny match. This is a configuration change for a different root cause (Route-map permit sequence), where Route maps are processed by ordered sequence; the first matching clause determines the permit or deny action. Here the evidence instead concerns longest-prefix selection: A longer matching prefix is selected before administrative distance is compared among equal-length routes.
D: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 longest-prefix selection: A longer matching prefix is selected before administrative distance is compared among equal-length routes.