Cisco 300-410 Practice Test 75
Question 740
During a scheduled validation at the Spokane branch site, telnet management is still reachable on a production router after a security baseline requiring encrypted administration. Engineers must restore a business-critical application without disturbing unrelated production services. The attempted fix creates a regression. Which scoped recovery action is most appropriate?
- Revert transport restriction only under controlled emergency access if SSH setup breaks all management.
- Remove the maintenance permit if clocks or schedules cannot be trusted.
- Restore the former ACL order if the specific permit unintentionally opens additional sources.
- Back out an overly restrictive ND policy if it disrupts legitimate neighbor discovery.
Explanation
Correct Answer
A:Revert transport restriction only under controlled emergency access if SSH setup breaks all management. SSH provides encrypted remote CLI transport; Telnet sends sessions without encryption.
Incorrect Answers
B:Remove the maintenance permit if clocks or schedules cannot be trusted. This is a rollback for a different component (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 router ssh hardened management: SSH provides encrypted remote CLI transport; Telnet sends sessions without encryption.
C:Restore the former ACL order if the specific permit unintentionally opens additional sources. This is a rollback for a different component (Extended ACL first-match semantics), where Extended ACL processing stops on the first matching entry, followed by an implicit deny if none matches. Here the evidence instead concerns router ssh hardened management: SSH provides encrypted remote CLI transport; Telnet sends sessions without encryption.
D:Back out an overly restrictive ND policy if it disrupts legitimate neighbor discovery. This is a rollback for a different component (IPv6 Neighbor Discovery inspection), where IPv6 ND inspection uses neighbor state and filtering to mitigate neighbor-discovery spoofing. Here the evidence instead concerns router ssh hardened management: SSH provides encrypted remote CLI transport; Telnet sends sessions without encryption.
Question 741
During a scheduled validation at the Tulsa warehouse network, an eBGP neighbor configured to use loopbacks cannot establish even though both loopback IPs are reachable. Engineers must restore an operations uplink without disturbing unrelated production services. Which investigation should be prioritized before the engineer modifies configuration?
- Inspect TCP reachability and confirm the neighbor's configured remote-as matches its new AS.
- Check update-source, neighbor IP, and ebgp-multihop TTL against the actual topology.
- Inspect the received BGP next-hop address and its reachability in the IGP or VRF.
- Inspect local preference distributed in iBGP along with route selection results.
Explanation
Correct Answer
B:Check update-source, neighbor IP, and ebgp-multihop TTL against the actual topology. Default eBGP TTL and packet source are designed for directly connected peers; loopback peering needs explicit settings.
Incorrect Answers
A: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 loopback-sourced ebgp session: Default eBGP TTL and packet source are designed for directly connected peers; loopback peering needs explicit settings.
C:Inspect the received BGP next-hop address and its reachability in the IGP or VRF. This is an investigation for a different failure condition (BGP iBGP next-hop reachability), where An iBGP speaker commonly preserves next-hop attributes unless explicitly changed, so next-hop resolution matters. Here the evidence instead concerns loopback-sourced ebgp session: Default eBGP TTL and packet source are designed for directly connected peers; loopback peering needs explicit settings.
D: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 loopback-sourced ebgp session: Default eBGP TTL and packet source are designed for directly connected peers; loopback peering needs explicit settings.
Question 742
During a scheduled validation at the Tulsa warehouse network, an eBGP neighbor configured to use loopbacks cannot establish even though both loopback IPs are reachable. Engineers must restore an operations uplink without disturbing unrelated production services. Which targeted configuration or policy correction best resolves the described fault?
- Configure a consistent loopback update source and sufficient eBGP multihop hop limit.
- Refine the aggregate or restore specific reachable routes so the advertisement does not imply missing coverage.
- Mark the intended iBGP neighbors as route-reflector clients under the correct address family.
- Reduce needless query scope with appropriate stubs or route summarization and repair the nonresponding link.
Explanation
Correct Answer
A:Configure a consistent loopback update source and sufficient eBGP multihop hop limit. Default eBGP TTL and packet source are designed for directly connected peers; loopback peering needs explicit settings.
Incorrect Answers
B:Refine the aggregate or restore specific reachable routes so the advertisement does not imply missing coverage. This is a configuration change for a different root cause (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 loopback-sourced ebgp session: Default eBGP TTL and packet source are designed for directly connected peers; loopback peering needs explicit settings.
C:Mark the intended iBGP neighbors as route-reflector clients under the correct address family. This is a configuration change for a different root cause (BGP route reflector clients), where Route reflectors relax iBGP split-horizon for configured clients while using loop-prevention attributes. Here the evidence instead concerns loopback-sourced ebgp session: Default eBGP TTL and packet source are designed for directly connected peers; loopback peering needs explicit settings.
D:Reduce needless query scope with appropriate stubs or route summarization and repair the nonresponding link. This is a configuration change for a different root cause (EIGRP stuck-in-active), where EIGRP stuck-in-active often arises when a router does not receive timely replies to diffusion queries. Here the evidence instead concerns loopback-sourced ebgp session: Default eBGP TTL and packet source are designed for directly connected peers; loopback peering needs explicit settings.
Question 743
During a scheduled validation at the Tulsa warehouse network, an eBGP neighbor configured to use loopbacks cannot establish even though both loopback IPs are reachable. Engineers must restore an operations uplink without disturbing unrelated production services. Which post-change check most directly establishes that the repair is correct?
- Check whether the reported distance is strictly less than the feasible distance before declaring it feasible.
- Confirm internal BGP speakers consistently choose the preferred exit while backup remains available.
- Probe each component prefix and examine forwarding to ensure the summary does not attract unreachable traffic.
- Verify TCP 179 establishment using the loopback source and an Established BGP session.
Explanation
Correct Answer
D:Verify TCP 179 establishment using the loopback source and an Established BGP session. Default eBGP TTL and packet source are designed for directly connected peers; loopback peering needs explicit settings.
Incorrect Answers
A:Check whether the reported distance is strictly less than the feasible distance before declaring it feasible. This is a validation for another mechanism (EIGRP feasible successor), where The EIGRP feasibility condition requires a neighbor's reported distance below the local feasible distance. Here the evidence instead concerns loopback-sourced ebgp session: Default eBGP TTL and packet source are designed for directly connected peers; loopback peering needs explicit settings.
B:Confirm internal BGP speakers consistently choose the preferred exit while backup remains available. This is a validation for another mechanism (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 loopback-sourced ebgp session: Default eBGP TTL and packet source are designed for directly connected peers; loopback peering needs explicit settings.
C:Probe each component prefix and examine forwarding to ensure the summary does not attract unreachable traffic. This is a validation for another mechanism (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 loopback-sourced ebgp session: Default eBGP TTL and packet source are designed for directly connected peers; loopback peering needs explicit settings.
Question 744
During a scheduled validation at the Tulsa warehouse network, an eBGP neighbor configured to use loopbacks cannot establish even though both loopback IPs are reachable. 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.
- Check update-source, neighbor IP, and ebgp-multihop TTL against the actual topology.
- Compare AS paths as seen by external peers and inspect outbound route policy for each eBGP neighbor.
- Configure a consistent loopback update source and sufficient eBGP multihop hop limit.
- Mark the intended iBGP neighbors as route-reflector clients under the correct address family.
Explanation
Correct Answers
A:Check update-source, neighbor IP, and ebgp-multihop TTL against the actual topology. Default eBGP TTL and packet source are designed for directly connected peers; loopback peering needs explicit settings.
C:Configure a consistent loopback update source and sufficient eBGP multihop hop limit. Default eBGP TTL and packet source are designed for directly connected peers; loopback peering needs explicit settings.
Incorrect Answers
B:Compare AS paths as seen by external peers and inspect outbound route policy for each eBGP neighbor. This is an investigation for a different failure condition (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 loopback-sourced ebgp session: Default eBGP TTL and packet source are designed for directly connected peers; loopback peering needs explicit settings.
D:Mark the intended iBGP neighbors as route-reflector clients under the correct address family. This is a configuration change for a different root cause (BGP route reflector clients), where Route reflectors relax iBGP split-horizon for configured clients while using loop-prevention attributes. Here the evidence instead concerns loopback-sourced ebgp session: Default eBGP TTL and packet source are designed for directly connected peers; loopback peering needs explicit settings.
Question 745
During a scheduled validation at the Madison enterprise edge, an aggregate static route through the WAN is present, yet traffic for one subnet follows a separate path learned through a dynamic protocol. Engineers must restore management access without disturbing unrelated production services. Which investigation should be prioritized before the engineer modifies configuration?
- Inspect route-map sequence order, each match condition, and hit counts against the missing prefixes.
- Check whether the EIGRP redistribution policy supplies a usable seed metric.
- Inspect the redistribution source, subnets handling, and whether a match or prefix filter excludes /27.
- 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:Check whether the EIGRP redistribution policy supplies a usable seed metric. This is an investigation for a different failure condition (EIGRP redistribution seed metric), where EIGRP redistribution generally needs an appropriate seed metric for external routes. Here the evidence instead concerns longest-prefix selection: A longer matching prefix is selected before administrative distance is compared among equal-length routes.
C:Inspect the redistribution source, subnets handling, and whether a match or prefix filter excludes /27. This is an investigation for a different failure condition (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.
Question 746
During a scheduled validation at the Madison enterprise edge, an aggregate static route through the WAN is present, yet traffic for one subnet follows a separate path learned through a dynamic protocol. Engineers must restore management access without disturbing unrelated production services. Which targeted configuration or policy correction best resolves the described fault?
- Provide the required EIGRP seed metric through redistribution or a route map for the intended source.
- 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.
- Allow the intended subnet with classless redistribution and a scoped route map instead of exporting everything.
Explanation
Correct Answer
C: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:Provide the required EIGRP seed metric through redistribution or a route map for the intended source. This is a configuration change for a different root cause (EIGRP redistribution seed metric), where EIGRP redistribution generally needs an appropriate seed metric for external routes. Here the evidence instead concerns longest-prefix selection: A longer matching prefix is selected before administrative distance is compared among equal-length routes.
B: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.
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.
Question 747
During a scheduled validation at the Madison enterprise edge, an aggregate static route through the WAN is present, yet traffic for one subnet follows a separate path learned through a dynamic protocol. Engineers must restore management access without disturbing unrelated production services. Which post-change check most directly establishes that the repair is correct?
- Check resulting redistributed prefixes and route-map matches after refreshing policy application.
- Use a destination-specific forwarding lookup to confirm which most-specific route is selected.
- Verify the OSPF route wins when healthy and the static route takes over only when the primary disappears.
- Verify the external EIGRP route and plausible composite metric appear in neighbor tables.
Explanation
Correct Answer
B:Use a destination-specific forwarding lookup to confirm which most-specific route is selected. A longer matching prefix is selected before administrative distance is compared among equal-length routes.
Incorrect Answers
A:Check resulting redistributed prefixes and route-map matches after refreshing policy application. This is a validation for another mechanism (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.
C:Verify the OSPF route wins when healthy and the static route takes over only when the primary disappears. This is a validation for another mechanism (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.
D:Verify the external EIGRP route and plausible composite metric appear in neighbor tables. This is a validation for another mechanism (EIGRP redistribution seed metric), where EIGRP redistribution generally needs an appropriate seed metric for external routes. Here the evidence instead concerns longest-prefix selection: A longer matching prefix is selected before administrative distance is compared among equal-length routes.
Question 748
During a scheduled validation at the Madison enterprise edge, an aggregate static route through the WAN is present, yet traffic for one subnet follows a separate path learned through a dynamic protocol. Engineers must restore management access without disturbing unrelated production services. Select TWO actions: one investigation and one targeted remediation that belong together for this incident.
- Correct the more-specific route or its advertisement if it is unintended; do not only change the aggregate's distance.
- Tag routes on first redistribution and deny that tag when importing them back into the source domain.
- Check whether the EIGRP redistribution policy supplies a usable seed metric.
- Compare the destination's matching prefixes and their lengths, not merely route-source preference.
Explanation
Correct Answers
A: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.
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
B:Tag routes on first redistribution and deny that tag when importing them back into the source domain. This is a configuration change for a different root cause (Redistribution loop prevention tags), where Consistent route tagging and inbound redistribution filters help prevent feedback loops across routing domains. Here the evidence instead concerns longest-prefix selection: A longer matching prefix is selected before administrative distance is compared among equal-length routes.
C:Check whether the EIGRP redistribution policy supplies a usable seed metric. This is an investigation for a different failure condition (EIGRP redistribution seed metric), where EIGRP redistribution generally needs an appropriate seed metric for external routes. Here the evidence instead concerns longest-prefix selection: A longer matching prefix is selected before administrative distance is compared among equal-length routes.
Question 749
Following a production change at the Chandler remote operations location, a router cannot back up its running configuration to a TFTP server across a firewall, while ICMP ping works. 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?
- Check RA managed-config flag, DHCPv6 relay destination, and routed reachability to the service.
- Inspect the authoritative engine ID and how user keys are localized to it.
- Check UDP/69 transfer initiation, server write permissions, and return data-channel filtering.
- Check SCP server enablement, privilege, AAA authorization, and management path reachability.
Explanation
Correct Answer
C:Check UDP/69 transfer initiation, server write permissions, and return data-channel filtering. TFTP is a UDP file-transfer service; successful ICMP reachability does not prove file-transfer access.
Incorrect Answers
A:Check RA managed-config flag, DHCPv6 relay destination, and routed reachability to the service. This is an investigation for a different failure condition (DHCPv6 relay), where DHCPv6 relaying transports client messages to a remote server; Router Advertisements still convey default-router details. Here the evidence instead concerns tftp configuration transfer: TFTP is a UDP file-transfer service; successful ICMP reachability does not prove file-transfer access.
B:Inspect the authoritative engine ID and how user keys are localized to it. This is an investigation for a different failure condition (SNMPv3 engine identity), where SNMPv3 localized authentication keys depend on the engine identity, so device replacement can require credential regeneration. Here the evidence instead concerns tftp configuration transfer: TFTP is a UDP file-transfer service; successful ICMP reachability does not prove file-transfer access.
D:Check SCP server enablement, privilege, AAA authorization, and management path reachability. This is an investigation for a different failure condition (SCP configuration backup), where SCP uses SSH transport but requires appropriate service support and file privileges. Here the evidence instead concerns tftp configuration transfer: TFTP is a UDP file-transfer service; successful ICMP reachability does not prove file-transfer access.
Question 750
Following a production change at the Chandler remote operations location, a router cannot back up its running configuration to a TFTP server across a firewall, while ICMP ping works. 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?
- Correct the IOS DHCP pool default-router option and renew affected leases.
- Enable the appropriate SCP service and narrowly scoped permissions for the backup account.
- Configure the correct ip helper-address on the client-facing routed interface.
- Permit the required TFTP exchange to the authorized host or use an approved more secure backup protocol.
Explanation
Correct Answer
D:Permit the required TFTP exchange to the authorized host or use an approved more secure backup protocol. TFTP is a UDP file-transfer service; successful ICMP reachability does not prove file-transfer access.
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 tftp configuration transfer: TFTP is a UDP file-transfer service; successful ICMP reachability does not prove file-transfer access.
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 tftp configuration transfer: TFTP is a UDP file-transfer service; successful ICMP reachability does not prove file-transfer access.
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 tftp configuration transfer: TFTP is a UDP file-transfer service; successful ICMP reachability does not prove file-transfer access.