Question 420
At fictional Windward Maritime, during a GitLab deployment pipeline rehearsal, the operator observes: An inventory import creates duplicate switch records because device identity is inferred from mutable display names rather than stable identifiers. Which engineering principle explains the described system behavior?
Explanation
Correct Answer
A source of truth provides desired canonical inventory, but consumers must resolve identity correctly and reconcile discrepancies. The corresponding repair is: Use stable authoritative device identifiers and reconcile observed inventory to the source-of-truth records before deployment. Acceptance should show: The device registry maps one approved identity to each physical endpoint and duplicate or stale mappings are flagged.
Incorrect Answers
This principle describes a separate cause: The corresponding repair is: Unstage the unintended file with an index-only reset or equivalent restore-staged operation, leaving the worktree intact. The reported condition is governed by: The corresponding repair is: Use stable authoritative device identifiers and reconcile observed inventory to the source-of-truth records before deployment. The two mechanisms should not be conflated.
The corresponding repair is: Resolve the conflicting lines deliberately against the approved desired network state, run validation, then commit the merged result. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Use stable authoritative device identifiers and reconcile observed inventory to the source-of-truth records before deployment.
The offered statement is true for this other mechanism: The corresponding repair is: Model the relevant links, routing peers and failure cases in CML rather than only a minimal happy-path device. It does not explain the facts described here, which follow from: The corresponding repair is: Use stable authoritative device identifiers and reconcile observed inventory to the source-of-truth records before deployment.