Question 50
In an implementation assurance meeting for fictional Vesper Finance, reviewers observe: A program signs an architecture contract once and ignores the contract after a major solution design change. Which concept explains why the original approach was insufficient?
Explanation
Correct Answer
Architecture Contracts connect approved architectural direction to accountable implementation expectations. Applying this distinction points to the response: Update Architecture Contract commitments and oversight arrangements when approved architectural decisions change. The evidence to seek is: The implementation team and architecture sponsor share current, testable conformance obligations. Applied here, the relevant facts are: A program signs an architecture contract once and ignores the contract after a major solution design change.
Incorrect Answers
The offered principle describes: An Architecture Board's role is governance and architecture leadership, not universal implementation micromanagement. The situation in this question instead depends on: Architecture Contracts connect approved architectural direction to accountable implementation expectations. These are different technical conditions.
This alternative is valid when architecture Compliance is a controlled assessment, not a self-declared claim or automatic veto. The facts here establish a different controlling reason: Architecture Contracts connect approved architectural direction to accountable implementation expectations.
“Governance helps protect architectural integrity while allowing justified change to be reviewed” reflects the mechanism: Governance helps protect architectural integrity while allowing justified change to be reviewed. The actual reported symptoms are better explained by: Architecture Contracts connect approved architectural direction to accountable implementation expectations.