Question 300
A Linux administrator evaluates: An audit finds temporary API tokens committed to a Containerfile used by an automated image builder. Select TWO complementary answers: the most suitable corrective action AND the evidence proving it worked.
Explanation
Correct Answers
The observed Linux condition is: An audit finds temporary API tokens committed to a Containerfile used by an automated image builder. The recommended direct administrative response is: Use Dockerfile or Containerfile instructions to build repeatable images, while supplying environment-specific settings and secrets at runtime through supported secure mechanisms. The relevant failure or security risk is: Embedding production credentials or mutable state in image layers can leak secrets across registries and image history. Validate success with: A fresh image build reproduces application binaries while deployed instances receive approved runtime configuration without secrets in image layers.
For the specific observation (An audit finds temporary API tokens committed to a Containerfile used by an automated image builder), the acceptance evidence is: A fresh image build reproduces application binaries while deployed instances receive approved runtime configuration without secrets in image layers. This verifies the action (Use Dockerfile or Containerfile instructions to build repeatable images, while supplying environment-specific settings and secrets at runtime through supported secure mechanisms.) rather than merely proving that an unrelated Linux tool works. It also addresses the known risk: Embedding production credentials or mutable state in image layers can leak secrets across registries and image history.
Incorrect Answers
Local account creation with useradd and defaults (2.2) would demonstrate or implement: getent passwd, id and the home directory show the approved identity, primary group, login shell and initial files. The case states: An audit finds temporary API tokens committed to a Containerfile used by an automated image builder. The most direct paired action and test is: Use Dockerfile or Containerfile instructions to build repeatable images, while supplying environment-specific settings and secrets at runtime through supported secure mechanisms.
Linux symbolic versus hard links (2.1) would demonstrate or implement: A hard link cannot span filesystem boundaries; a symlink can become dangling after the named target is removed. This choice can be useful for that problem, but it does not establish the Container image build versus runtime configuration control being assessed here.
Systemd service start versus boot enablement (2.5) addresses another technical failure: A service started manually may still be disabled at boot, and an enabled service need not be running yet. This case instead tests Container image build versus runtime configuration; the choice measures or changes another part of the system.