LFCS · Question #56
LFCS Question #56: Real Exam Question with Answer & Explanation
The correct answer is D: DNS resolution may not be working as route by default tries to resolve names of routers and. A long delay in route command output often signifies a problem with DNS resolution, as the command attempts to resolve IP addresses to hostnames by default.
Question
On a regular users workstation the route command takes a long time before printing out the routing table. Which of the following errors does that indicate?
Options
- AThe local routing information may be corrupted and must be re-validated using a routing protocol.
- BOne of the routers in the routing table is not available which causes the automatic router failure
- CThere may accidentally be more than one default router in which case a default router election
- DDNS resolution may not be working as route by default tries to resolve names of routers and
Explanation
A long delay in route command output often signifies a problem with DNS resolution, as the command attempts to resolve IP addresses to hostnames by default.
Common mistakes.
- A. Corrupted routing information would likely result in routing errors or incorrect paths, not merely a slow display of the routing table.
- B. An unavailable router might cause connectivity issues, but it typically does not directly delay the
routecommand's ability to display the entire table itself, unless that router's name lookup is specifically failing and holding up the process. - C. Multiple default routers could lead to routing ambiguity but would not inherently slow down the
routecommand's execution in displaying the table; it relates more to routing behavior than display speed.
Concept tested. route command behavior and DNS impact
Reference. https://man7.org/linux/man-pages/man8/route.8.html
Topics
Community Discussion
No community discussion yet for this question.