Question 610
While investigating a source-of-truth integration for fictional Willowfield Hospitality, the team reports: A network engineer switches branches with uncommitted interface edits, then mistakenly tests a mixture of two feature versions. What should the team add to its network automation operating process?
Explanation
Correct Answer
Require clean-worktree status checks when CI or operators switch network automation release branches. This prevents the recurrence because git checkout can change branch and working-tree files; uncommitted modifications must be managed to avoid accidental mixing. A matching immediate correction is: Safely stash or commit unrelated work and check out the intended branch or detached revision in a clean worktree. Applied here, the relevant facts are: A network engineer switches branches with uncommitted interface edits, then mistakenly tests a mixture of two feature versions. The question asks what should the team add to its network automation operating process.
Incorrect Answers
The proposed action belongs to the mechanism: a cherry-picked commit does not automatically bring every ancestor or dependent change from its original branch. Here the stated fault follows a different mechanism: git checkout can change branch and working-tree files; uncommitted modifications must be managed to avoid accidental mixing. The corrective choice is “Require clean-worktree status checks when CI or operators switch network automation release branches”.
The offered action targets: git revert records an inverse patch in new history rather than moving shared branch pointers backward. The case facts point instead to: git checkout can change branch and working-tree files; uncommitted modifications must be managed to avoid accidental mixing. Implement “Require clean-worktree status checks when CI or operators switch network automation release branches” to address that specific condition.
This alternative is a response to another technical cause: a reproducible simulation needs controlled topology definitions and readiness gates to avoid timing-dependent false failures. The reported case instead depends on: git checkout can change branch and working-tree files; uncommitted modifications must be managed to avoid accidental mixing. The action that directly addresses it is “Require clean-worktree status checks when CI or operators switch network automation release branches”.