Question 60
A Linux administrator evaluates: A critical LV needs additional extents without accidentally extending a different data volume. Select TWO complementary answers: the most suitable corrective action AND the evidence proving it worked.
Explanation
Correct Answers
For the specific observation (A critical LV needs additional extents without accidentally extending a different data volume), the acceptance evidence is: pvs, vgs, lvs and the filesystem capacity check show the intended growth with application data intact. This verifies the action (Inspect physical volumes, volume groups and logical volumes; add supported physical capacity and extend the intended LV and filesystem using compatible tools.) rather than merely proving that an unrelated Linux tool works. It also addresses the known risk: Growing only a virtual disk or logical volume does not automatically make the filesystem report additional usable space.
The observed Linux condition is: A critical LV needs additional extents without accidentally extending a different data volume. The recommended direct administrative response is: Inspect physical volumes, volume groups and logical volumes; add supported physical capacity and extend the intended LV and filesystem using compatible tools. The relevant failure or security risk is: Growing only a virtual disk or logical volume does not automatically make the filesystem report additional usable space. Validate success with: pvs, vgs, lvs and the filesystem capacity check show the intended growth with application data intact.
Incorrect Answers
Filesystem Hierarchy Standard paths (1.1) would demonstrate or implement: Placing persistent configuration or operational logs under temporary paths can cause data loss or a broken service on reboot. The case states: the most suitable corrective action AND the evidence proving it worked. The most direct paired action and test is: pvs, vgs, lvs and the filesystem capacity check show the intended growth with application data intact.
KVM virtual machine lifecycle with virsh (1.7) addresses another technical failure: Deleting or redefining a VM without understanding its storage volumes can lose persistent guest data. This choice can be useful for that problem, but it does not establish the LVM physical volume to logical volume capacity growth control being assessed here.
Persistent network configuration with nmcli (1.4) would demonstrate or implement: nmcli and ip address/ip route show the intended persistent configuration before and after reactivation. This case instead tests LVM physical volume to logical volume capacity growth; the choice measures or changes another part of the system.