Question 250
During an introductory open-source workshop, the task is: A student must compress one large text export as report.gz and mistakenly uses tar without a compression option. What preventive habit belongs in the runbook?
Explanation
Correct Answer
Specify whether a task needs one compressed file or an archive of many files. This practice reduces recurrence of the same problem. Technical reason: gzip compresses an input file; creating a tar container is optional and serves a different packaging purpose. A controlled repeat test should show: report.txt.gz is created and decompression reproduces the original bytes.
Incorrect Answers
“Validate archive integrity instead of assuming a small filename extension proves compression” is a sensible check for: Validate archive integrity instead of assuming a small filename extension proves compression. It is not the prevention measure for the current dependency: Specify whether a task needs one compressed file or an archive of many files. The closer guardrail is “Specify whether a task needs one compressed file or an archive of many files”.
The alternate safeguard protects a separate dependency: Include the correct compression suffix and restore command in backup runbooks. For this failure the continuing exposure is: Specify whether a task needs one compressed file or an archive of many files. Maintain “Specify whether a task needs one compressed file or an archive of many files” instead.
That review tracks a separate failure mechanism: Make archive inspection a mandatory step before restoring untrusted packages. The question requires sustained control over: Specify whether a task needs one compressed file or an archive of many files. The corresponding safeguard is “Specify whether a task needs one compressed file or an archive of many files”.