Question 520
A Linux administrator evaluates: A team must examine the difference between a tested infrastructure branch and the release branch. Select TWO complementary answers: the most suitable corrective action AND the evidence proving it worked.
Explanation
Correct Answers
The observed Linux condition is: A team must examine the difference between a tested infrastructure branch and the release branch. The recommended direct administrative response is: Create a feature branch, commit coherent changes, review a diff and merge the approved branch into the intended base with a clear history. The relevant failure or security risk is: Editing the main branch directly or merging without a review can deploy untested configuration to production. Validate success with: Git status, log and diff show the reviewed commit on the intended branch with no unrelated changes included.
For the specific observation (A team must examine the difference between a tested infrastructure branch and the release branch), the acceptance evidence is: Git status, log and diff show the reviewed commit on the intended branch with no unrelated changes included. This verifies the action (Create a feature branch, commit coherent changes, review a diff and merge the approved branch into the intended base with a clear history.) rather than merely proving that an unrelated Linux tool works. It also addresses the known risk: Editing the main branch directly or merging without a review can deploy untested configuration to production.
Incorrect Answers
First-boot provisioning with cloud-init and Kickstart (4.1) addresses another technical failure: Running initial setup as an untracked manual step can leave machines without required accounts, updates or trusted configuration. The case states: A team must examine the difference between a tested infrastructure branch and the release branch. The most direct paired action and test is: Create a feature branch, commit coherent changes, review a diff and merge the approved branch into the intended base with a clear history.
Shell exit status and fail-fast pipelines (4.2) would demonstrate or implement: An intentionally failed command triggers a nonzero job result and stops the dependent publication or deletion step. This case instead tests Git branch workflow and reviewed merging; the choice measures or changes another part of the system.
AI data governance and sensitive prompt handling (4.5) would demonstrate or implement: Pasting plaintext secrets or sensitive logs into unapproved AI services can expose data beyond the organization’s authorized boundary. The required paired action and test concerns Git branch workflow and reviewed merging; a passing result for this alternative could leave that requirement unresolved.