Cisco 300-410 Practice Test 3
Question 20
During a scheduled validation at the Mobile enterprise edge, clients on a newly added routed VLAN send DHCP Discover broadcasts but receive no offers from a central server on another subnet. Engineers must restore a monitored campus segment without disturbing unrelated production services. The attempted fix creates a regression. Which scoped recovery action is most appropriate?
- Restore the last valid pool options if another VLAN starts receiving the wrong gateway.
- Undo a broad TFTP firewall permit if it exposes the device to untrusted endpoints.
- Restore prior pool bounds if authorized clients are left without usable addresses.
- Restore the old helper if requests are sent to an unauthorized DHCP server.
Explanation
Correct Answer
D:Restore the old helper if requests are sent to an unauthorized DHCP server. IPv4 DHCP Discover broadcasts require a relay when the DHCP server resides beyond a Layer 3 boundary.
Incorrect Answers
A:Restore the last valid pool options if another VLAN starts receiving the wrong gateway. This is a rollback for a different component (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:Undo a broad TFTP firewall permit if it exposes the device to untrusted endpoints. This is a rollback for a different component (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 ipv4 dhcp relay: IPv4 DHCP Discover broadcasts require a relay when the DHCP server resides beyond a Layer 3 boundary.
C:Restore prior pool bounds if authorized clients are left without usable addresses. This is a rollback for a different component (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 21
During a scheduled validation at the Raleigh hospital campus, newly leased IPv4 clients reach peers on their local VLAN but cannot route off-subnet. Engineers must restore an operations uplink without disturbing unrelated production services. Which investigation should be prioritized before the engineer modifies configuration?
- Inspect exporter destination address, UDP port, source-interface, VRF, and export statistics.
- Inspect the client VLAN gateway's helper address, routed path to server, and DHCP relay forwarding.
- Inspect the lease's default-router option and compare it with the actual VLAN gateway.
- Inspect the DHCP pool range and configured excluded-address entries against reservations.
Explanation
Correct Answer
C:Inspect the lease's default-router option and compare it with the actual VLAN gateway. DHCP option 3/default-router tells IPv4 clients which gateway to use; leases can be valid despite a wrong option.
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 dhcp default-router option: DHCP option 3/default-router tells IPv4 clients which gateway to use; leases can be valid despite a wrong option.
B:Inspect the client VLAN gateway's helper address, routed path to server, and DHCP relay forwarding. This is an investigation for a different failure condition (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 dhcp default-router option: DHCP option 3/default-router tells IPv4 clients which gateway to use; leases can be valid despite a wrong option.
D:Inspect the DHCP pool range and configured excluded-address entries against reservations. This is an investigation for a different failure condition (DHCP address exclusions), where IOS DHCP address exclusions keep reserved addresses out of automatic lease allocation. Here the evidence instead concerns dhcp default-router option: DHCP option 3/default-router tells IPv4 clients which gateway to use; leases can be valid despite a wrong option.
Question 22
During a scheduled validation at the Raleigh hospital campus, newly leased IPv4 clients reach peers on their local VLAN but cannot route off-subnet. Engineers must restore an operations uplink without disturbing unrelated production services. Which targeted configuration or policy correction best resolves the described fault?
- Add a least-privilege VTY access-class exception for the authorized administration subnet.
- Correct the IOS DHCP pool default-router option and renew affected leases.
- Configure the correct ip helper-address on the client-facing routed interface.
- Exclude the reserved range from automatic assignment and correct affected leases.
Explanation
Correct Answer
B:Correct the IOS DHCP pool default-router option and renew affected leases. DHCP option 3/default-router tells IPv4 clients which gateway to use; leases can be valid despite a wrong option.
Incorrect Answers
A:Add a least-privilege VTY access-class exception for the authorized administration subnet. This is a configuration change for a different root cause (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 dhcp default-router option: DHCP option 3/default-router tells IPv4 clients which gateway to use; leases can be valid despite a wrong option.
C:Configure the correct ip helper-address on the client-facing routed interface. This is a configuration change for a different root cause (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 dhcp default-router option: DHCP option 3/default-router tells IPv4 clients which gateway to use; leases can be valid despite a wrong option.
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 dhcp default-router option: DHCP option 3/default-router tells IPv4 clients which gateway to use; leases can be valid despite a wrong option.
Question 23
During a scheduled validation at the Raleigh hospital campus, newly leased IPv4 clients reach peers on their local VLAN but cannot route off-subnet. Engineers must restore an operations uplink without disturbing unrelated production services. Which post-change check most directly establishes that the repair is correct?
- Capture a relay-generated request and verify the server replies with a lease for the client's subnet.
- Verify a test client receives the correct gateway and can reach a remote subnet.
- Run a controlled SCP copy and compare file checksum or contents after transfer.
- Request new test leases and confirm no protected printer address is offered.
Explanation
Correct Answer
B:Verify a test client receives the correct gateway and can reach a remote subnet. DHCP option 3/default-router tells IPv4 clients which gateway to use; leases can be valid despite a wrong option.
Incorrect Answers
A: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 dhcp default-router option: DHCP option 3/default-router tells IPv4 clients which gateway to use; leases can be valid despite a wrong option.
C:Run a controlled SCP copy and compare file checksum or contents after transfer. This is a validation for another mechanism (SCP configuration backup), where SCP uses SSH transport but requires appropriate service support and file privileges. Here the evidence instead concerns dhcp default-router option: DHCP option 3/default-router tells IPv4 clients which gateway to use; leases can be valid despite a wrong option.
D: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 dhcp default-router option: DHCP option 3/default-router tells IPv4 clients which gateway to use; leases can be valid despite a wrong option.
Question 24
During a scheduled validation at the Raleigh hospital campus, newly leased IPv4 clients reach peers on their local VLAN but cannot route off-subnet. Engineers must restore an operations uplink without disturbing unrelated production services. Select TWO actions: one investigation and one targeted remediation that belong together for this incident.
- Correct the IOS DHCP pool default-router option and renew affected leases.
- Inspect the lease's default-router option and compare it with the actual VLAN gateway.
- Inspect the client VLAN gateway's helper address, routed path to server, and DHCP relay forwarding.
- Exclude the reserved range from automatic assignment and correct affected leases.
Explanation
Correct Answers
A:Correct the IOS DHCP pool default-router option and renew affected leases. DHCP option 3/default-router tells IPv4 clients which gateway to use; leases can be valid despite a wrong option.
B:Inspect the lease's default-router option and compare it with the actual VLAN gateway. DHCP option 3/default-router tells IPv4 clients which gateway to use; leases can be valid despite a wrong option.
Incorrect Answers
C:Inspect the client VLAN gateway's helper address, routed path to server, and DHCP relay forwarding. This is an investigation for a different failure condition (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 dhcp default-router option: DHCP option 3/default-router tells IPv4 clients which gateway to use; leases can be valid despite a wrong option.
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 dhcp default-router option: DHCP option 3/default-router tells IPv4 clients which gateway to use; leases can be valid despite a wrong option.
Question 25
During a scheduled validation at the Newark remote operations location, a provider router sees an IP route for a customer prefix but no corresponding label forwarding entry on an expected MPLS path. Engineers must restore a monitored campus segment without disturbing unrelated production services. Which investigation should be prioritized before the engineer modifies configuration?
- Compare the incoming-label lookup, outgoing label, and outgoing interface in the LFIB.
- Examine the selected LDP transport address and TCP reachability between LDP identifiers.
- Inspect LDP neighbor state, label bindings, and the forwarding table for the forwarding equivalence class.
- Inspect the downstream-advertised implicit-null binding and the penultimate router's label operation.
Explanation
Correct Answer
C:Inspect LDP neighbor state, label bindings, and the forwarding table for the forwarding equivalence class. MPLS forwarding requires valid label bindings and next-hop label operations along the label-switched path.
Incorrect Answers
A:Compare the incoming-label lookup, outgoing label, and outgoing interface in the LFIB. This is an investigation for a different failure condition (MPLS incoming versus outgoing labels), where An LSR switches labels using its label forwarding information base, not the customer IP prefix alone. Here the evidence instead concerns mpls label assignment: MPLS forwarding requires valid label bindings and next-hop label operations along the label-switched path.
B:Examine the selected LDP transport address and TCP reachability between LDP identifiers. This is an investigation for a different failure condition (LDP router-ID transport reachability), where LDP discovery can succeed while its TCP transport session fails if the chosen transport addresses are unreachable. Here the evidence instead concerns mpls label assignment: MPLS forwarding requires valid label bindings and next-hop label operations along the label-switched path.
D:Inspect the downstream-advertised implicit-null binding and the penultimate router's label operation. This is an investigation for a different failure condition (MPLS penultimate hop popping), where Penultimate hop popping is expected when an egress LSR advertises implicit null for the relevant FEC. Here the evidence instead concerns mpls label assignment: MPLS forwarding requires valid label bindings and next-hop label operations along the label-switched path.
Question 26
During a scheduled validation at the Newark remote operations location, a provider router sees an IP route for a customer prefix but no corresponding label forwarding entry on an expected MPLS path. Engineers must restore a monitored campus segment without disturbing unrelated production services. Which targeted configuration or policy correction best resolves the described fault?
- Repair LDP adjacency or label distribution for the intended core path while keeping IGP reachability intact.
- Make the intended LDP router-ID transport reachable through the core IGP and correct source selection.
- Retain the intended PHP behavior unless the architecture explicitly requires explicit-null handling.
- Correct the label/next-hop distribution inconsistency by repairing the underlying LDP/IGP path rather than editing IP routes blindly.
Explanation
Correct Answer
A:Repair LDP adjacency or label distribution for the intended core path while keeping IGP reachability intact. MPLS forwarding requires valid label bindings and next-hop label operations along the label-switched path.
Incorrect Answers
B:Make the intended LDP router-ID transport reachable through the core IGP and correct source selection. This is a configuration change for a different root cause (LDP router-ID transport reachability), where LDP discovery can succeed while its TCP transport session fails if the chosen transport addresses are unreachable. Here the evidence instead concerns mpls label assignment: MPLS forwarding requires valid label bindings and next-hop label operations along the label-switched path.
C:Retain the intended PHP behavior unless the architecture explicitly requires explicit-null handling. This is a configuration change for a different root cause (MPLS penultimate hop popping), where Penultimate hop popping is expected when an egress LSR advertises implicit null for the relevant FEC. Here the evidence instead concerns mpls label assignment: MPLS forwarding requires valid label bindings and next-hop label operations along the label-switched path.
D:Correct the label/next-hop distribution inconsistency by repairing the underlying LDP/IGP path rather than editing IP routes blindly. This is a configuration change for a different root cause (MPLS incoming versus outgoing labels), where An LSR switches labels using its label forwarding information base, not the customer IP prefix alone. Here the evidence instead concerns mpls label assignment: MPLS forwarding requires valid label bindings and next-hop label operations along the label-switched path.
Question 27
During a scheduled validation at the Newark remote operations location, a provider router sees an IP route for a customer prefix but no corresponding label forwarding entry on an expected MPLS path. Engineers must restore a monitored campus segment without disturbing unrelated production services. Which post-change check most directly establishes that the repair is correct?
- Verify the label stack operation at each hop and the expected egress reachability.
- Verify LDP neighbors remain Operational and bindings appear across the repaired segment.
- Confirm the penultimate router pops the transport label and the egress PE still forwards the packet correctly.
- Compare control-plane bindings with the LFIB and verify labeled packets reach the next-hop router.
Explanation
Correct Answer
D:Compare control-plane bindings with the LFIB and verify labeled packets reach the next-hop router. MPLS forwarding requires valid label bindings and next-hop label operations along the label-switched path.
Incorrect Answers
A:Verify the label stack operation at each hop and the expected egress reachability. This is a validation for another mechanism (MPLS incoming versus outgoing labels), where An LSR switches labels using its label forwarding information base, not the customer IP prefix alone. Here the evidence instead concerns mpls label assignment: MPLS forwarding requires valid label bindings and next-hop label operations along the label-switched path.
B:Verify LDP neighbors remain Operational and bindings appear across the repaired segment. This is a validation for another mechanism (LDP router-ID transport reachability), where LDP discovery can succeed while its TCP transport session fails if the chosen transport addresses are unreachable. Here the evidence instead concerns mpls label assignment: MPLS forwarding requires valid label bindings and next-hop label operations along the label-switched path.
C:Confirm the penultimate router pops the transport label and the egress PE still forwards the packet correctly. This is a validation for another mechanism (MPLS penultimate hop popping), where Penultimate hop popping is expected when an egress LSR advertises implicit null for the relevant FEC. Here the evidence instead concerns mpls label assignment: MPLS forwarding requires valid label bindings and next-hop label operations along the label-switched path.
Question 28
During a scheduled validation at the Newark remote operations location, a provider router sees an IP route for a customer prefix but no corresponding label forwarding entry on an expected MPLS path. Engineers must restore a monitored campus segment without disturbing unrelated production services. Select TWO actions: one investigation and one targeted remediation that belong together for this incident.
- Repair LDP adjacency or label distribution for the intended core path while keeping IGP reachability intact.
- Make the intended LDP router-ID transport reachable through the core IGP and correct source selection.
- Inspect the downstream-advertised implicit-null binding and the penultimate router's label operation.
- Inspect LDP neighbor state, label bindings, and the forwarding table for the forwarding equivalence class.
Explanation
Correct Answers
A:Repair LDP adjacency or label distribution for the intended core path while keeping IGP reachability intact. MPLS forwarding requires valid label bindings and next-hop label operations along the label-switched path.
D:Inspect LDP neighbor state, label bindings, and the forwarding table for the forwarding equivalence class. MPLS forwarding requires valid label bindings and next-hop label operations along the label-switched path.
Incorrect Answers
B:Make the intended LDP router-ID transport reachable through the core IGP and correct source selection. This is a configuration change for a different root cause (LDP router-ID transport reachability), where LDP discovery can succeed while its TCP transport session fails if the chosen transport addresses are unreachable. Here the evidence instead concerns mpls label assignment: MPLS forwarding requires valid label bindings and next-hop label operations along the label-switched path.
C:Inspect the downstream-advertised implicit-null binding and the penultimate router's label operation. This is an investigation for a different failure condition (MPLS penultimate hop popping), where Penultimate hop popping is expected when an egress LSR advertises implicit null for the relevant FEC. Here the evidence instead concerns mpls label assignment: MPLS forwarding requires valid label bindings and next-hop label operations along the label-switched path.
Question 29
Following a production change at the Spokane regional hub, critical route changes appear locally, but the remote syslog collector receives only a subset of severity levels. The incident is affecting a tenant service; the response team has a rollback window. Which observation is the strongest first diagnostic check for this symptom?
- Inspect IP SLA probe status, tracked object, and whether the static route references that object.
- Inspect configured logging source-interface, VRF-aware transport, and collector allowlists.
- Check telemetry subscription encoding, sensor path, transport destination, and subscription state.
- Compare local logging buffer settings with remote trap severity and collector-side filtering.
Explanation
Correct Answer
D:Compare local logging buffer settings with remote trap severity and collector-side filtering. Local logging and remote syslog use separate targets and severity thresholds.
Incorrect Answers
A:Inspect IP SLA probe status, tracked object, and whether the static route references that object. This is an investigation for a different failure condition (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 syslog severity filtering: Local logging and remote syslog use separate targets and severity thresholds.
B:Inspect configured logging source-interface, VRF-aware transport, and collector allowlists. This is an investigation for a different failure condition (Syslog source interface), where Syslog transport can fail when its source or VRF does not match collector reachability and access rules. Here the evidence instead concerns syslog severity filtering: Local logging and remote syslog use separate targets and severity thresholds.
C:Check telemetry subscription encoding, sensor path, transport destination, and subscription state. This is an investigation for a different failure condition (Model-driven telemetry subscriptions), where Streaming telemetry depends on a supported sensor model and an active subscription to the receiver. Here the evidence instead concerns syslog severity filtering: Local logging and remote syslog use separate targets and severity thresholds.
Question 30
Following a production change at the Spokane regional hub, critical route changes appear locally, but the remote syslog collector receives only a subset of severity levels. The incident is affecting a tenant service; the response team has a rollback window. What change best addresses the root mechanism without unnecessarily changing other paths?
- Set the appropriate remote logging level and destination for the intended operational events.
- Add a least-privilege VTY access-class exception for the authorized administration subnet.
- Set the intended reachable source-interface and VRF context for remote syslog traffic.
- Align the authorized read-only community and NMS source list without adding public write access.
Explanation
Correct Answer
A:Set the appropriate remote logging level and destination for the intended operational events. Local logging and remote syslog use separate targets and severity thresholds.
Incorrect Answers
B:Add a least-privilege VTY access-class exception for the authorized administration subnet. This is a configuration change for a different root cause (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 syslog severity filtering: Local logging and remote syslog use separate targets and severity thresholds.
C:Set the intended reachable source-interface and VRF context for remote syslog traffic. This is a configuration change for a different root cause (Syslog source interface), where Syslog transport can fail when its source or VRF does not match collector reachability and access rules. Here the evidence instead concerns syslog severity filtering: Local logging and remote syslog use separate targets and severity thresholds.
D:Align the authorized read-only community and NMS source list without adding public write access. This is a configuration change for a different root cause (SNMPv2c read access), where SNMPv2c community matching and ACL restrictions determine polling access, but v2c itself lacks modern encryption. Here the evidence instead concerns syslog severity filtering: Local logging and remote syslog use separate targets and severity thresholds.