Question 400
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 technical evidence should be required before closing this change?
Explanation
Correct Answer
The working tree reports the intended revision and no uncommitted cross-branch edits before test execution. This directly verifies the related correction: Safely stash or commit unrelated work and check out the intended branch or detached revision in a clean worktree. It checks the technical distinction: Git checkout can change branch and working-tree files; uncommitted modifications must be managed to avoid accidental mixing.
Incorrect Answers
This observation would test a different technical dependency: This directly verifies the related correction: Produce a reproducible versioned build artifact in the build stage and use that immutable artifact for subsequent validation and deployment. The current issue is governed by: This directly verifies the related correction: Safely stash or commit unrelated work and check out the intended branch or detached revision in a clean worktree. Its decisive check is “The working tree reports the intended revision and no uncommitted cross-branch edits before test execution”.
The alternative verifies a different condition: This directly verifies the related correction: Model the relevant links, routing peers and failure cases in CML rather than only a minimal happy-path device. The current case instead depends on: This directly verifies the related correction: Safely stash or commit unrelated work and check out the intended branch or detached revision in a clean worktree. Confirm that “The working tree reports the intended revision and no uncommitted cross-branch edits before test execution”.
This observation would test a different technical dependency: This directly verifies the related correction: Build a representative topology in Cisco Modeling Labs and execute the automation against simulated devices before live release. The current issue is governed by: This directly verifies the related correction: Safely stash or commit unrelated work and check out the intended branch or detached revision in a clean worktree. Its decisive check is “The working tree reports the intended revision and no uncommitted cross-branch edits before test execution”.