Question 150
A Linux administrator evaluates: An archive exists in cloud storage but the team has no extraction test proving the required files are inside. Select TWO complementary answers: the most suitable corrective action AND the evidence proving it worked.
Explanation
Correct Answers
For the specific observation (An archive exists in cloud storage but the team has no extraction test proving the required files are inside), the acceptance evidence is: The archive inventory matches the intended files and a test extraction reproduces them at the correct locations. This verifies the action (Create and inspect a tar archive with the appropriate compression choice and test extraction into a controlled directory before depending on it.) rather than merely proving that an unrelated Linux tool works. It also addresses the known risk: Mistaking archive packaging for a verified backup or extracting unsafe paths blindly can lose files or overwrite live content.
The observed Linux condition is: An archive exists in cloud storage but the team has no extraction test proving the required files are inside. The recommended direct administrative response is: Create and inspect a tar archive with the appropriate compression choice and test extraction into a controlled directory before depending on it. The relevant failure or security risk is: Mistaking archive packaging for a verified backup or extracting unsafe paths blindly can lose files or overwrite live content. Validate success with: The archive inventory matches the intended files and a test extraction reproduces them at the correct locations.
Incorrect Answers
Ext4 and XFS filesystem repair and growth distinctions (1.3) would demonstrate or implement: Applying an ext4 repair or resize utility to an XFS volume, or repairing a mounted filesystem improperly, can fail or damage data. The case states: the most suitable corrective action AND the evidence proving it worked. The most direct paired action and test is: The archive inventory matches the intended files and a test extraction reproduces them at the correct locations.
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. This choice can be useful for that problem, but it does not establish the Tar archive creation and extraction integrity 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. The paired-answer requirement concerns Tar archive creation and extraction integrity; this alternative does not provide the matching intervention and separate acceptance evidence.