Router R1 Cannot Reach R3 Practice Questions

pyATS requires less code than a ping script

Why wrong: pyATS may require more code to set up but provides more functionality.

pyATS can test multiple devices in parallel

Why wrong: While pyATS can do parallel testing, it is not a unique advantage over custom scripts.

pyATS automatically generates test reports

Why wrong: While pyATS can generate reports, the key advantage is the test framework itself.

Resend the authorization request with the code included in the redirect URI.

Why wrong: Repeating the authorization request will generate a new code, not produce an access token.

Decode the authorization code using base64 to extract the access token.

Why wrong: The authorization code is not base64-encoded access token; decoding will not produce a usable token.

Use the authorization code directly in subsequent API requests as a bearer token.

Why wrong: The authorization code is a temporary credential that must be exchanged for an access token; it cannot be used directly.

1. Configure Router ID (router-id [id]). 2. Enable OSPF routing process (router ospf [process-id]). 3. Advertise networks (network [network] [wildcard] area [area]).

Why wrong: This is incorrect because you cannot configure a router ID without first enabling the OSPF process; the router-id command is entered in OSPF router configuration mode, which requires the process to be active.

1. Enable OSPF routing process (router ospf [process-id]). 2. Advertise networks (network [network] [wildcard] area [area]). 3. Configure Router ID (router-id [id]).

Why wrong: This is incorrect because although technically you can set the router ID after network statements, best practice and the standard order in Cisco documentation is to configure the router ID before network statements to ensure a stable router ID during neighbor formation.

1. Advertise networks (network [network] [wildcard] area [area]). 2. Enable OSPF routing process (router ospf [process-id]). 3. Configure Router ID (router-id [id]).

Why wrong: This is incorrect because you cannot advertise networks or configure a router ID before the OSPF process is enabled; network statements are entered in router configuration mode, which only exists after the process is started.

HTTPS is not enabled on the device.

Why wrong: The 'ip http secure-server' command enables HTTPS.

The HTTP server is not enabled.

Why wrong: The configuration includes 'ip http server', so HTTP is enabled.

Authentication is not configured as local.

Why wrong: Authentication is set to local with 'ip http authentication local'.

for iface in interfaces.keys(): print(iface + ': ' + interfaces.get(iface))

Why wrong: Incorrect: Does not skip None, so prints 'None' as a string for entries with None IP.

for iface in interfaces: if interfaces[iface]: print(iface, ':', interfaces[iface])

Why wrong: Incorrect: Uses truthiness check which could skip non-None falsy values, and print with commas produces spaces around the colon (e.g., 'iface : ip'), deviating from expected format.

Change the endpoint to 'GET /dna/intent/api/v1/network-device' which returns all devices without pagination.

Why wrong: Incorrect. This endpoint retrieves network devices, not site health, and may also implement pagination.

Export the site health data using the 'POST /dna/intent/api/v1/site-health/export' endpoint.

Why wrong: Incorrect. This is an export feature that may generate a report, not a direct retrieval of all data in a single API call.

Increase the 'pageSize' parameter to 150 to retrieve all records in a single request.

Why wrong: Incorrect. The API likely has a maximum page size (e.g., 50), so requesting 150 may be rejected or truncated.

Replace BGP with static routes.

Why wrong: Static routes do not scale and would require manual updates.

Remove all BGP learned routes and use only OSPF.

Why wrong: This would lose external connectivity.

Configure a default route to the upstream provider.

Why wrong: A default route only works for internet-bound traffic, not for internal subnets.

event interface

Why wrong: This triggers on interface state changes.

event timer

Why wrong: Timer triggers based on time, not syslog.

event cli match

Why wrong: This triggers on CLI command input, not syslog.

docker start -d -p 8080:80 myapp

Why wrong: docker start does not accept -p; ports are set at run time.

docker run -it -p 8080:80 myapp

Why wrong: -it runs interactively, not detached.

docker run -d -p 80:8080 myapp

Why wrong: Port mapping order is hostPort:containerPort. The mapping is reversed.

1, 3, 5, 7, 9, 11

Why wrong: Only 1, 6, 11 are non-overlapping.

1, 5, 9, 13

Why wrong: Channels 5 and 9 overlap with others.

2, 7, 12

Why wrong: Channel 12 is not allowed in some regions and overlaps.

1, 5, 9, 13

Why wrong: These channels overlap.

1, 3, 5, 7, 9, 11

Why wrong: These overlap due to channel spacing.

2, 7, 12

Why wrong: Channel 12 is not available in all regions and still overlaps.

The `ios_config` module requires a provider statement

Why wrong: Missing provider would cause a different error, not this YAML error.

The `lines:` item should be a list of strings

Why wrong: The snippet shows a list already; that is not the issue.

The `parents:` value must be enclosed in quotes

Why wrong: Quotes are not mandatory for simple strings in YAML.

docker run -it -p 8080:80 -v /host/data:/container/data myapp

Why wrong: -it runs interactively, not detached.

docker start -d -p 8080:80 -v /host/data:/container/data myapp

Why wrong: docker start does not accept -p or -v flags; those are for docker run.

docker compose up -d -p 8080:80 -v /host/data:/container/data myapp

Why wrong: docker compose uses a YAML file for configuration, not command-line flags for port and volume.

The database server is not listening on the expected port

Why wrong: Since other services can reach the database, the listener is working.

The mutual TLS certificates are expired or not trusted

Why wrong: If mTLS were the issue, other services attempting to connect would also likely fail.

The Istio sidecar proxy is misconfigured and rejecting traffic due to a missing ServiceEntry

Why wrong: Without a ServiceEntry, traffic might be blocked by mutual TLS, but the symptom is unreachability, and other services work.

Disable the local firewall on the workstation to allow all outbound traffic.

Why wrong: While a firewall could block traffic, it is not the most likely cause since DNS queries succeed. Disabling the firewall is a security risk and not a targeted solution.

Renew the DHCP lease to obtain a new IP address.

Why wrong: Renewing DHCP may not resolve the issue since the IP configuration appears correct and DNS is reachable.

Restart the network interface card (NIC) to reset the connection.

Why wrong: Restarting the NIC might temporarily reset the connection, but it doesn't address the root cause of routing to the API subnet.