Question 160
A Linux administrator evaluates: A virtual network change requires proving a guest is attached to the intended libvirt network without altering its disk. Select TWO complementary answers: the most suitable corrective action AND the evidence proving it worked.
Explanation
Correct Answers
For the specific observation (A virtual network change requires proving a guest is attached to the intended libvirt network without altering its disk), the acceptance evidence is: virsh reports the expected guest state and the guest boots with its assigned vCPU, memory, network and storage. This verifies the action (Use libvirt and virsh to inspect, define, start and manage supported KVM guests, distinguishing guest state from disk-image data.) rather than merely proving that an unrelated Linux tool works. It also addresses the known risk: Deleting or redefining a VM without understanding its storage volumes can lose persistent guest data.
The observed Linux condition is: A virtual network change requires proving a guest is attached to the intended libvirt network without altering its disk. The recommended direct administrative response is: Use libvirt and virsh to inspect, define, start and manage supported KVM guests, distinguishing guest state from disk-image data. The relevant failure or security risk is: Deleting or redefining a VM without understanding its storage volumes can lose persistent guest data. Validate success with: virsh reports the expected guest state and the guest boots with its assigned vCPU, memory, network and storage.
Incorrect Answers
Persistent filesystem mounting by UUID (1.3) would demonstrate or implement: findmnt and mount output show the expected UUID at its intended path after a controlled reboot test. This choice can be useful for that problem, but it does not establish the KVM virtual machine lifecycle with virsh control being assessed here.
Route and socket inspection with IP and ss (1.4) addresses another technical failure: A locally listening service and a reachable default gateway are separate prerequisites; one cannot prove the other. This case instead tests KVM virtual machine lifecycle with virsh; the choice measures or changes another part of the system.
DNS resolver diagnosis with dig and hosts precedence (1.4) would demonstrate or implement: Changing firewall rules for a stale local hosts entry or unreachable DNS resolver may leave the original naming fault untouched. The required paired action and test concerns KVM virtual machine lifecycle with virsh; a passing result for this alternative could leave that requirement unresolved.