Question 100
A Linux administrator evaluates: A newly deployed VM resolves its own hostname differently from the corporate DNS service. Select TWO complementary answers: the most suitable corrective action AND the evidence proving it worked.
Explanation
Correct Answers
For the specific observation (A newly deployed VM resolves its own hostname differently from the corporate DNS service), the acceptance evidence is: The requested hostname resolves to the intended address through the configured lookup path, and application connections use that result. This verifies the action (Compare resolver settings, /etc/hosts and NSS lookup order; use dig or getent to isolate whether name resolution is local or DNS-based.) rather than merely proving that an unrelated Linux tool works. It also addresses the known risk: Changing firewall rules for a stale local hosts entry or unreachable DNS resolver may leave the original naming fault untouched.
The observed Linux condition is: A newly deployed VM resolves its own hostname differently from the corporate DNS service. The recommended direct administrative response is: Compare resolver settings, /etc/hosts and NSS lookup order; use dig or getent to isolate whether name resolution is local or DNS-based. The relevant failure or security risk is: Changing firewall rules for a stale local hosts entry or unreachable DNS resolver may leave the original naming fault untouched. Validate success with: The requested hostname resolves to the intended address through the configured lookup path, and application connections use that result.
Incorrect Answers
Software RAID health and rebuild with mdadm (1.3) addresses another technical failure: Replacing the wrong disk or trusting a degraded mirror without monitoring rebuild can cause avoidable data loss. The case states: the most suitable corrective action AND the evidence proving it worked. The most direct paired action and test is: The requested hostname resolves to the intended address through the configured lookup path, and application connections use that result.
Persistent filesystem mounting by UUID (1.3) would demonstrate or implement: Using a changing /dev/sdX name or wrong filesystem type can mount the wrong disk or drop the system into emergency mode. This case instead tests DNS resolver diagnosis with dig and hosts precedence; the choice measures or changes another part of the system.
LVM physical volume to logical volume capacity growth (1.3) would demonstrate or implement: pvs, vgs, lvs and the filesystem capacity check show the intended growth with application data intact. The paired-answer requirement concerns DNS resolver diagnosis with dig and hosts precedence; this alternative does not provide the matching intervention and separate acceptance evidence.