Question 750
A systems administrator investigates this finding: A host receives a DNS response but uses an unexpected search suffix for a short hostname. Which mechanism BEST fits this evidence?
Explanation
Correct Answer
Short names are ambiguous when search domains differ. This explains the symptom rather than a coincidental service condition. Verification: The intended full hostname resolves consistently.
Incorrect Answers
DNS lookup and IP reachability are distinct operations. That can explain why an application connects by IP but fails by a private hostname, whereas the current evidence supports resolver search domains can transform unqualified names into different FQDN queries.
The alternative describes an incorrect prefix length changes which IPs the kernel treats as on-link, which is relevant when a corporate subnet is /26 but the host was configured with /24. It does not explain this case because short names are ambiguous when search domains differ.
An updated authoritative record does not retroactively invalidate every local cache. That can explain why a DNS cache continues returning old records after a failover, whereas the current evidence supports resolver search domains can transform unqualified names into different FQDN queries.





CompTIA Linux+ (XK0-006) Practice Tests