Cisco 300-410 Practice Test 78
Question 770
Following a production change at the Albany manufacturing plant, a secure management portal presents a certificate name mismatch after a router IP/name change. 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?
- Install a trusted certificate matching the intended management DNS name and enforce HTTPS.
- Align the authorized read-only community and NMS source list without adding public write access.
- Generate an appropriate RSA key pair and enable the supported SSH server configuration.
- Fix the specifically identified failed link, ACL, or routing segment rather than reconfiguring unrelated sites.
Explanation
Correct Answer
A:Install a trusted certificate matching the intended management DNS name and enforce HTTPS. HTTPS management depends on TLS trust and correct certificate identity, not just an enabled port.
Incorrect Answers
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 https device management: HTTPS management depends on TLS trust and correct certificate identity, not just an enabled port.
C: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 https device management: HTTPS management depends on TLS trust and correct certificate identity, not just an enabled port.
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 https device management: HTTPS management depends on TLS trust and correct certificate identity, not just an enabled port.
Question 771
Following a production change at the Albany manufacturing plant, a secure management portal presents a certificate name mismatch after a router IP/name change. The incident is affecting a tenant service; the response team has a rollback window. Which verification result would provide the most relevant acceptance evidence?
- Verify the collector receives decoded flows and the router's export success counter increments.
- Trigger a known test event and verify the message arrives with expected severity and facility.
- Confirm browser TLS validation succeeds without bypassing certificate errors.
- Repeat path trace and an application-level test to confirm the failing segment is corrected.
Explanation
Correct Answer
C:Confirm browser TLS validation succeeds without bypassing certificate errors. HTTPS management depends on TLS trust and correct certificate identity, not just an enabled port.
Incorrect Answers
A:Verify the collector receives decoded flows and the router's export success counter increments. This is a validation for another mechanism (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 https device management: HTTPS management depends on TLS trust and correct certificate identity, not just an enabled port.
B:Trigger a known test event and verify the message arrives with expected severity and facility. This is a validation for another mechanism (Syslog severity filtering), where Local logging and remote syslog use separate targets and severity thresholds. Here the evidence instead concerns https device management: HTTPS management depends on TLS trust and correct certificate identity, not just an enabled port.
D: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 https device management: HTTPS management depends on TLS trust and correct certificate identity, not just an enabled port.
Question 772
Following a production change at the Albany manufacturing plant, a secure management portal presents a certificate name mismatch after a router IP/name change. The incident is affecting a tenant service; the response team has a rollback window. The new configuration worsens service. Which controlled rollback should the team perform?
- Restore the previous policy or route on the affected hop if the trace exposes a regression.
- Detach the new track object if transient probe loss causes excessive failover.
- Restore the previous scoped community policy if polling from legitimate collectors breaks.
- Reinstate the previous valid certificate if the new enrollment breaks management access.
Explanation
Correct Answer
D:Reinstate the previous valid certificate if the new enrollment breaks management access. HTTPS management depends on TLS trust and correct certificate identity, not just an enabled port.
Incorrect Answers
A:Restore the previous policy or route on the affected hop if the trace exposes a regression. This is a rollback for a different component (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 https device management: HTTPS management depends on TLS trust and correct certificate identity, not just an enabled port.
B:Detach the new track object if transient probe loss causes excessive failover. This is a rollback for a different component (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 https device management: HTTPS management depends on TLS trust and correct certificate identity, not just an enabled port.
C:Restore the previous scoped community policy if polling from legitimate collectors breaks. This is a rollback for a different component (SNMPv2c read access), where SNMPv2c community matching and ACL restrictions determine polling access, but v2c itself lacks modern encryption. Here the evidence instead concerns https device management: HTTPS management depends on TLS trust and correct certificate identity, not just an enabled port.
Question 773
During a scheduled validation at the Plano remote operations location, voice quality is poor on a WAN path even though ordinary ping latency remains within target. Engineers must restore remote-site route stability without disturbing unrelated production services. Which investigation should be prioritized before the engineer modifies configuration?
- Inspect IP SLA probe status, tracked object, and whether the static route references that object.
- Inspect IP SLA UDP-jitter measurements for one-way or round-trip delay variation and loss.
- Inspect line-specific login method lists, transport settings, and source filters separately for console and VTY.
- Inspect which debug condition or filter can isolate the affected neighbor or interface.
Explanation
Correct Answer
B:Inspect IP SLA UDP-jitter measurements for one-way or round-trip delay variation and loss. Jitter-sensitive applications need measurements of delay variation and loss, not just ICMP reachability.
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 ip sla udp jitter monitoring: Jitter-sensitive applications need measurements of delay variation and loss, not just ICMP reachability.
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 ip sla udp jitter monitoring: Jitter-sensitive applications need measurements of delay variation and loss, not just ICMP reachability.
D:Inspect which debug condition or filter can isolate the affected neighbor or interface. This is an investigation for a different failure condition (Conditional debugging), where Conditional debugs reduce diagnostic impact by restricting runtime detail to a relevant context. Here the evidence instead concerns ip sla udp jitter monitoring: Jitter-sensitive applications need measurements of delay variation and loss, not just ICMP reachability.
Question 774
During a scheduled validation at the Plano remote operations location, voice quality is poor on a WAN path even though ordinary ping latency remains within target. Engineers must restore remote-site route stability without disturbing unrelated production services. Which targeted configuration or policy correction best resolves the described fault?
- Enable the intended interface-event SNMP notifications to the approved NMS recipient.
- Enable the appropriate SCP service and narrowly scoped permissions for the backup account.
- Deploy an appropriately timed UDP-jitter operation to a supported responder for the voice path.
- Tie the static route to a correctly scoped IP SLA track object and install a higher-distance backup route.
Explanation
Correct Answer
C:Deploy an appropriately timed UDP-jitter operation to a supported responder for the voice path. Jitter-sensitive applications need measurements of delay variation and loss, not just ICMP reachability.
Incorrect Answers
A:Enable the intended interface-event SNMP notifications to the approved NMS recipient. This is a configuration change for a different root cause (SNMP traps versus polling), where SNMP traps and informs send asynchronous notifications; polling alone is periodic and can miss brief events. Here the evidence instead concerns ip sla udp jitter monitoring: Jitter-sensitive applications need measurements of delay variation and loss, not just ICMP reachability.
B:Enable the appropriate SCP service and narrowly scoped permissions for the backup account. This is a configuration change for a different root cause (SCP configuration backup), where SCP uses SSH transport but requires appropriate service support and file privileges. Here the evidence instead concerns ip sla udp jitter monitoring: Jitter-sensitive applications need measurements of delay variation and loss, not just ICMP reachability.
D:Tie the static route to a correctly scoped IP SLA track object and install a higher-distance backup route. This is a configuration change for a different root cause (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 ip sla udp jitter monitoring: Jitter-sensitive applications need measurements of delay variation and loss, not just ICMP reachability.
Question 775
During a scheduled validation at the Plano remote operations location, voice quality is poor on a WAN path even though ordinary ping latency remains within target. Engineers must restore remote-site route stability without disturbing unrelated production services. Which post-change check most directly establishes that the repair is correct?
- Verify a real configuration copy succeeds and the saved file can be read back.
- Verify the collector receives decoded flows and the router's export success counter increments.
- Simulate upstream failure and confirm the tracked route withdraws while backup routing activates.
- Confirm jitter, packet loss, and delay statistics reflect a controlled impairment test.
Explanation
Correct Answer
D:Confirm jitter, packet loss, and delay statistics reflect a controlled impairment test. Jitter-sensitive applications need measurements of delay variation and loss, not just ICMP reachability.
Incorrect Answers
A:Verify a real configuration copy succeeds and the saved file can be read back. This is a validation for another mechanism (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 ip sla udp jitter monitoring: Jitter-sensitive applications need measurements of delay variation and loss, not just ICMP reachability.
B:Verify the collector receives decoded flows and the router's export success counter increments. This is a validation for another mechanism (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 ip sla udp jitter monitoring: Jitter-sensitive applications need measurements of delay variation and loss, not just ICMP reachability.
C: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 ip sla udp jitter monitoring: Jitter-sensitive applications need measurements of delay variation and loss, not just ICMP reachability.
Question 776
During a scheduled validation at the Plano remote operations location, voice quality is poor on a WAN path even though ordinary ping latency remains within target. Engineers must restore remote-site route stability without disturbing unrelated production services. The attempted fix creates a regression. Which scoped recovery action is most appropriate?
- Detach the new track object if transient probe loss causes excessive failover.
- Restore earlier remote logging limits if the new level floods the collector.
- Restore the previous probe interval if active measurements add excessive load.
- Reinstate the previous valid certificate if the new enrollment breaks management access.
Explanation
Correct Answer
C:Restore the previous probe interval if active measurements add excessive load. Jitter-sensitive applications need measurements of delay variation and loss, not just ICMP reachability.
Incorrect Answers
A:Detach the new track object if transient probe loss causes excessive failover. This is a rollback for a different component (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 ip sla udp jitter monitoring: Jitter-sensitive applications need measurements of delay variation and loss, not just ICMP reachability.
B:Restore earlier remote logging limits if the new level floods the collector. This is a rollback for a different component (Syslog severity filtering), where Local logging and remote syslog use separate targets and severity thresholds. Here the evidence instead concerns ip sla udp jitter monitoring: Jitter-sensitive applications need measurements of delay variation and loss, not just ICMP reachability.
D:Reinstate the previous valid certificate if the new enrollment breaks management access. This is a rollback for a different component (HTTPS device management), where HTTPS management depends on TLS trust and correct certificate identity, not just an enabled port. Here the evidence instead concerns ip sla udp jitter monitoring: Jitter-sensitive applications need measurements of delay variation and loss, not just ICMP reachability.
Question 777
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. Which observation is the strongest first diagnostic check for this symptom?
- Inspect AAA command-authorization method lists, server response attributes, and privilege level for the operator.
- Inspect local username/secret presence and effective AAA method list applied to the VTY lines.
- Check AAA accounting method lists, TACACS+ reachability, and whether the relevant lines/commands apply accounting.
- Identify the ingress port carrying unauthorized Router Advertisements and inspect RA Guard trust role.
Explanation
Correct Answer
A:Inspect AAA command-authorization method lists, server response attributes, and privilege level for the operator. TACACS+ can authorize individual CLI commands separately from successful login authentication.
Incorrect Answers
B:Inspect local username/secret presence and effective AAA method list applied to the VTY lines. This is an investigation for a different failure condition (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: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 tacacs+ command authorization: TACACS+ can authorize individual CLI commands separately from successful login authentication.
D:Identify the ingress port carrying unauthorized Router Advertisements and inspect RA Guard trust role. This is an investigation for a different failure condition (IPv6 Router Advertisement Guard), where RA Guard controls where IPv6 Router Advertisements are accepted on Layer 2 access segments. Here the evidence instead concerns tacacs+ command authorization: TACACS+ can authorize individual CLI commands separately from successful login authentication.
Question 778
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. What change best addresses the root mechanism without unnecessarily changing other paths?
- Apply an appropriately scoped IPv6 access list in the correct direction without relying on IPv4 ACL behavior.
- Enable the appropriate AAA exec and command accounting to the authorized accounting server.
- Tie the SSH permit to a correctly defined time range and synchronize device time.
- Correct the scoped TACACS+ command set or method-list binding without granting unrestricted administrative privilege.
Explanation
Correct Answer
D:Correct the scoped TACACS+ command set or method-list binding without granting unrestricted administrative privilege. TACACS+ can authorize individual CLI commands separately from successful login authentication.
Incorrect Answers
A: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 tacacs+ command authorization: TACACS+ can authorize individual CLI commands separately from successful login authentication.
B:Enable the appropriate AAA exec and command accounting to the authorized accounting server. This is a configuration change for a different root cause (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.
C:Tie the SSH permit to a correctly defined time range and synchronize device time. This is a configuration change for a different root cause (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 tacacs+ command authorization: TACACS+ can authorize individual CLI commands separately from successful login authentication.
Question 779
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. Which verification result would provide the most relevant acceptance evidence?
- Confirm permitted commands execute while prohibited configuration commands are still rejected and logged.
- Simulate RADIUS unreachability and confirm designated local break-glass login succeeds without bypassing normal rejects.
- Test authorized SSH sessions and a bounded excess-load probe while observing CoPP counters.
- Confirm a controlled test login uses local authentication only under the designed fallback condition.
Explanation
Correct Answer
A:Confirm permitted commands execute while prohibited configuration commands are still rejected and logged. TACACS+ can authorize individual CLI commands separately from successful login authentication.
Incorrect Answers
B:Simulate RADIUS unreachability and confirm designated local break-glass login succeeds without bypassing normal rejects. This is a validation for another mechanism (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 tacacs+ command authorization: TACACS+ can authorize individual CLI commands separately from successful login authentication.
C:Test authorized SSH sessions and a bounded excess-load probe while observing CoPP counters. This is a validation for another mechanism (CoPP management access), where Management packets destined to the router's CPU are subject to control-plane policing. Here the evidence instead concerns tacacs+ command authorization: TACACS+ can authorize individual CLI commands separately from successful login authentication.
D:Confirm a controlled test login uses local authentication only under the designed fallback condition. This is a validation for another mechanism (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.
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.