Cisco 300-410 Practice Test 1
Question 1
During a scheduled validation at the Huntsville data center, wireless clients report high application latency at one campus, but switch interfaces show no sustained errors. Engineers must restore a business-critical application without disturbing unrelated production services. Which investigation should be prioritized before the engineer modifies configuration?
- Inspect the lease's default-router option and compare it with the actual VLAN gateway.
- Inspect configured logging source-interface, VRF-aware transport, and collector allowlists.
- Inspect Cisco Catalyst Center Assurance client health, onboarding timeline, and application reachability signals.
- Run the supported Cisco Catalyst Center Assurance path trace and examine hop-by-hop forwarding evidence.
Explanation
Correct Answer
C:Inspect Cisco Catalyst Center Assurance client health, onboarding timeline, and application reachability signals. Catalyst Center Assurance correlates client experience with network/device telemetry to support diagnosis.
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 catalyst center client assurance: Catalyst Center Assurance correlates client experience with network/device telemetry to support diagnosis.
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 catalyst center client assurance: Catalyst Center Assurance correlates client experience with network/device telemetry to support diagnosis.
D:Run the supported Cisco Catalyst Center Assurance path trace and examine hop-by-hop forwarding evidence. This is an investigation for a different failure condition (Catalyst Center path trace), where Assurance path-trace capabilities can isolate the segment traversed by traffic and support focused troubleshooting. Here the evidence instead concerns catalyst center client assurance: Catalyst Center Assurance correlates client experience with network/device telemetry to support diagnosis.
Question 2
During a scheduled validation at the Huntsville data center, wireless clients report high application latency at one campus, but switch interfaces show no sustained errors. Engineers must restore a business-critical application without disturbing unrelated production services. Which targeted configuration or policy correction best resolves the described fault?
- Set the appropriate remote logging level and destination for the intended operational events.
- Install a trusted certificate matching the intended management DNS name and enforce HTTPS.
- Use targeted Assurance findings to remediate the documented WLAN, authentication, or upstream issue.
- Fix the specifically identified failed link, ACL, or routing segment rather than reconfiguring unrelated sites.
Explanation
Correct Answer
C:Use targeted Assurance findings to remediate the documented WLAN, authentication, or upstream issue. Catalyst Center Assurance correlates client experience with network/device telemetry to support diagnosis.
Incorrect Answers
A:Set the appropriate remote logging level and destination for the intended operational events. This is a configuration change for a different root cause (Syslog severity filtering), where Local logging and remote syslog use separate targets and severity thresholds. Here the evidence instead concerns catalyst center client assurance: Catalyst Center Assurance correlates client experience with network/device telemetry to support diagnosis.
B:Install a trusted certificate matching the intended management DNS name and enforce HTTPS. This is a configuration change for a different root cause (HTTPS device management), where HTTPS management depends on TLS trust and correct certificate identity, not just an enabled port. Here the evidence instead concerns catalyst center client assurance: Catalyst Center Assurance correlates client experience with network/device telemetry to support diagnosis.
D:Fix the specifically identified failed link, ACL, or routing segment rather than reconfiguring unrelated sites. This is a configuration change for a different root cause (Catalyst Center path trace), where Assurance path-trace capabilities can isolate the segment traversed by traffic and support focused troubleshooting. Here the evidence instead concerns catalyst center client assurance: Catalyst Center Assurance correlates client experience with network/device telemetry to support diagnosis.
Question 3
During a scheduled validation at the Huntsville data center, wireless clients report high application latency at one campus, but switch interfaces show no sustained errors. Engineers must restore a business-critical application without disturbing unrelated production services. Which post-change check most directly establishes that the repair is correct?
- Verify authorized SNMP polling works and an unauthorized source remains blocked.
- Confirm client health improves for the affected population rather than relying only on global device uptime.
- Repeat path trace and an application-level test to confirm the failing segment is corrected.
- Verify timestamped interface samples arrive at the collector at the configured cadence.
Explanation
Correct Answer
B:Confirm client health improves for the affected population rather than relying only on global device uptime. Catalyst Center Assurance correlates client experience with network/device telemetry to support diagnosis.
Incorrect Answers
A:Verify authorized SNMP polling works and an unauthorized source remains blocked. This is a validation for another mechanism (SNMPv2c read access), where SNMPv2c community matching and ACL restrictions determine polling access, but v2c itself lacks modern encryption. Here the evidence instead concerns catalyst center client assurance: Catalyst Center Assurance correlates client experience with network/device telemetry to support diagnosis.
C:Repeat path trace and an application-level test to confirm the failing segment is corrected. This is a validation for another mechanism (Catalyst Center path trace), where Assurance path-trace capabilities can isolate the segment traversed by traffic and support focused troubleshooting. Here the evidence instead concerns catalyst center client assurance: Catalyst Center Assurance correlates client experience with network/device telemetry to support diagnosis.
D:Verify timestamped interface samples arrive at the collector at the configured cadence. This is a validation for another mechanism (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 catalyst center client assurance: Catalyst Center Assurance correlates client experience with network/device telemetry to support diagnosis.
Question 4
During a scheduled validation at the Huntsville data center, wireless clients report high application latency at one campus, but switch interfaces show no sustained errors. Engineers must restore a business-critical application 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.
- Run the supported Cisco Catalyst Center Assurance path trace and examine hop-by-hop forwarding evidence.
- Inspect Cisco Catalyst Center Assurance client health, onboarding timeline, and application reachability signals.
- Use targeted Assurance findings to remediate the documented WLAN, authentication, or upstream issue.
Explanation
Correct Answers
C:Inspect Cisco Catalyst Center Assurance client health, onboarding timeline, and application reachability signals. Catalyst Center Assurance correlates client experience with network/device telemetry to support diagnosis.
D:Use targeted Assurance findings to remediate the documented WLAN, authentication, or upstream issue. Catalyst Center Assurance correlates client experience with network/device telemetry to support diagnosis.
Incorrect Answers
A: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 catalyst center client assurance: Catalyst Center Assurance correlates client experience with network/device telemetry to support diagnosis.
B:Run the supported Cisco Catalyst Center Assurance path trace and examine hop-by-hop forwarding evidence. This is an investigation for a different failure condition (Catalyst Center path trace), where Assurance path-trace capabilities can isolate the segment traversed by traffic and support focused troubleshooting. Here the evidence instead concerns catalyst center client assurance: Catalyst Center Assurance correlates client experience with network/device telemetry to support diagnosis.
Question 5
During a scheduled validation at the Columbia hospital campus, legitimate packets are dropped at a dual-homed WAN ingress even though a return path to the source prefix exists through another interface. Engineers must restore remote-site route stability without disturbing unrelated production services. Which investigation should be prioritized before the engineer modifies configuration?
- Inspect uRPF drop counters and the reverse lookup's selected egress interface for the source address.
- Inspect reverse-route availability for packet source prefixes and the configured uRPF mode.
- Inspect the AAA login method-list order and the distinction between RADIUS timeout and explicit Access-Reject.
- Check AAA accounting method lists, TACACS+ reachability, and whether the relevant lines/commands apply accounting.
Explanation
Correct Answer
A:Inspect uRPF drop counters and the reverse lookup's selected egress interface for the source address. Strict uRPF can reject a packet when the best reverse route points to an interface other than its ingress.
Incorrect Answers
B:Inspect reverse-route availability for packet source prefixes and the configured uRPF mode. This is an investigation for a different failure condition (Loose uRPF source validation), where Loose uRPF primarily verifies that some acceptable reverse route exists instead of demanding the same ingress interface. Here the evidence instead concerns strict urpf asymmetric routing: Strict uRPF can reject a packet when the best reverse route points to an interface other than its ingress.
C:Inspect the AAA login method-list order and the distinction between RADIUS timeout and explicit Access-Reject. This is an investigation for a different failure condition (RADIUS AAA fallback), where AAA method lists try subsequent methods for server errors, not necessarily for a definitive authentication rejection. Here the evidence instead concerns strict urpf asymmetric routing: Strict uRPF can reject a packet when the best reverse route points to an interface other than its ingress.
D:Check AAA accounting method lists, TACACS+ reachability, and whether the relevant lines/commands apply accounting. This is an investigation for a different failure condition (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 strict urpf asymmetric routing: Strict uRPF can reject a packet when the best reverse route points to an interface other than its ingress.
Question 6
During a scheduled validation at the Columbia hospital campus, legitimate packets are dropped at a dual-homed WAN ingress even though a return path to the source prefix exists through another interface. Engineers must restore remote-site route stability without disturbing unrelated production services. Which targeted configuration or policy correction best resolves the described fault?
- Adjust the BGP control-plane class and policing rate to preserve trusted peering without unlimited control-plane access.
- Apply an appropriately scoped IPv6 access list in the correct direction without relying on IPv4 ACL behavior.
- Use a policy or feasible uRPF mode appropriate for intentional asymmetry, or correct source routing where possible.
- Enable appropriate source-reachability validation with an explicit exception policy if required by design.
Explanation
Correct Answer
C:Use a policy or feasible uRPF mode appropriate for intentional asymmetry, or correct source routing where possible. Strict uRPF can reject a packet when the best reverse route points to an interface other than its ingress.
Incorrect Answers
A:Adjust the BGP control-plane class and policing rate to preserve trusted peering without unlimited control-plane access. This is a configuration change for a different root cause (CoPP BGP class treatment), where CoPP can protect the route processor but over-restrictive classes can starve essential routing protocol traffic. Here the evidence instead concerns strict urpf asymmetric routing: Strict uRPF can reject a packet when the best reverse route points to an interface other than its ingress.
B: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 strict urpf asymmetric routing: Strict uRPF can reject a packet when the best reverse route points to an interface other than its ingress.
D:Enable appropriate source-reachability validation with an explicit exception policy if required by design. This is a configuration change for a different root cause (Loose uRPF source validation), where Loose uRPF primarily verifies that some acceptable reverse route exists instead of demanding the same ingress interface. Here the evidence instead concerns strict urpf asymmetric routing: Strict uRPF can reject a packet when the best reverse route points to an interface other than its ingress.
Question 7
During a scheduled validation at the Columbia hospital campus, legitimate packets are dropped at a dual-homed WAN ingress even though a return path to the source prefix exists through another interface. Engineers must restore remote-site route stability without disturbing unrelated production services. Which post-change check most directly establishes that the repair is correct?
- Test traffic during and after the authorized window and inspect relevant ACL hit counts.
- Test unroutable spoofed sources and valid externally routed sources with counters.
- Validate known legitimate asymmetric flows pass while spoofed invalid-source packets remain denied.
- Verify monitoring traffic is permitted and nonapproved sources remain blocked.
Explanation
Correct Answer
C:Validate known legitimate asymmetric flows pass while spoofed invalid-source packets remain denied. Strict uRPF can reject a packet when the best reverse route points to an interface other than its ingress.
Incorrect Answers
A: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 strict urpf asymmetric routing: Strict uRPF can reject a packet when the best reverse route points to an interface other than its ingress.
B:Test unroutable spoofed sources and valid externally routed sources with counters. This is a validation for another mechanism (Loose uRPF source validation), where Loose uRPF primarily verifies that some acceptable reverse route exists instead of demanding the same ingress interface. Here the evidence instead concerns strict urpf asymmetric routing: Strict uRPF can reject a packet when the best reverse route points to an interface other than its ingress.
D: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 strict urpf asymmetric routing: Strict uRPF can reject a packet when the best reverse route points to an interface other than its ingress.
Question 8
During a scheduled validation at the Columbia hospital campus, legitimate packets are dropped at a dual-homed WAN ingress even though a return path to the source prefix exists through another interface. 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.
- Inspect uRPF drop counters and the reverse lookup's selected egress interface for the source address.
- Use a policy or feasible uRPF mode appropriate for intentional asymmetry, or correct source routing where possible.
- Require SSH on management lines and disable Telnet while retaining an approved break-glass path.
- Inspect reverse-route availability for packet source prefixes and the configured uRPF mode.
Explanation
Correct Answers
A:Inspect uRPF drop counters and the reverse lookup's selected egress interface for the source address. Strict uRPF can reject a packet when the best reverse route points to an interface other than its ingress.
B:Use a policy or feasible uRPF mode appropriate for intentional asymmetry, or correct source routing where possible. Strict uRPF can reject a packet when the best reverse route points to an interface other than its ingress.
Incorrect Answers
C:Require SSH on management lines and disable Telnet while retaining an approved break-glass path. This is a configuration change for a different root cause (Router SSH hardened management), where SSH provides encrypted remote CLI transport; Telnet sends sessions without encryption. Here the evidence instead concerns strict urpf asymmetric routing: Strict uRPF can reject a packet when the best reverse route points to an interface other than its ingress.
D:Inspect reverse-route availability for packet source prefixes and the configured uRPF mode. This is an investigation for a different failure condition (Loose uRPF source validation), where Loose uRPF primarily verifies that some acceptable reverse route exists instead of demanding the same ingress interface. Here the evidence instead concerns strict urpf asymmetric routing: Strict uRPF can reject a packet when the best reverse route points to an interface other than its ingress.
Question 9
Following a production change at the Boise manufacturing plant, a router's flow cache contains valid conversations but its external collector receives no UDP exports. 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 the DHCP pool range and configured excluded-address entries against reservations.
- Inspect flow record, flow monitor, and whether the monitor is attached in the intended interface direction.
- Inspect line-specific login method lists, transport settings, and source filters separately for console and VTY.
- Inspect exporter destination address, UDP port, source-interface, VRF, and export statistics.
Explanation
Correct Answer
D:Inspect exporter destination address, UDP port, source-interface, VRF, and export statistics. Flow collection and export are distinct: valid local cache entries do not imply successful export transport.
Incorrect Answers
A: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 netflow exporter destination: Flow collection and export are distinct: valid local cache entries do not imply successful export transport.
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 netflow exporter destination: Flow collection and export are distinct: valid local cache entries do not imply successful export transport.
C:Inspect line-specific login method lists, transport settings, and source filters separately for console and VTY. This is an investigation for a different failure condition (Console versus VTY authentication), where Console and VTY lines can use different authentication and authorization methods. Here the evidence instead concerns netflow exporter destination: Flow collection and export are distinct: valid local cache entries do not imply successful export transport.
Question 10
Following a production change at the Boise manufacturing plant, a router's flow cache contains valid conversations but its external collector receives no UDP exports. 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?
- Attach the compatible Flexible NetFlow monitor to the correct traffic-facing interface and direction.
- Align the authorized read-only community and NMS source list without adding public write access.
- Install a trusted certificate matching the intended management DNS name and enforce HTTPS.
- Correct the exporter's receiver, source, and transport settings without changing the flow record unnecessarily.
Explanation
Correct Answer
D:Correct the exporter's receiver, source, and transport settings without changing the flow record unnecessarily. Flow collection and export are distinct: valid local cache entries do not imply successful export transport.
Incorrect Answers
A:Attach the compatible Flexible NetFlow monitor to the correct traffic-facing interface and direction. This is a configuration change for a different root cause (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 netflow exporter destination: Flow collection and export are distinct: valid local cache entries do not imply successful export transport.
B: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 netflow exporter destination: Flow collection and export are distinct: valid local cache entries do not imply successful export transport.
C:Install a trusted certificate matching the intended management DNS name and enforce HTTPS. This is a configuration change for a different root cause (HTTPS device management), where HTTPS management depends on TLS trust and correct certificate identity, not just an enabled port. Here the evidence instead concerns netflow exporter destination: Flow collection and export are distinct: valid local cache entries do not imply successful export transport.