Question 370
During an Architecture Development Method planning meeting at fictional Vesper Finance, the team reports: A retail project draws every database table although its objective is a strategic capability-level decision. What distinction in TOGAF architecture work best accounts for the problem?
Explanation
Correct Answer
Architecture scope is driven by the decision context rather than automatic enterprise-wide detail. Applying this distinction points to the response: Right-size architectural scope by organizational breadth, time, domains, and depth of detail. The evidence to seek is: The architecture engagement stays within authorized boundaries and supports the sponsor's actual decision.
Incorrect Answers
“Opportunities and Solutions turns architectural gaps into candidate implementation building blocks and work packages” reflects the mechanism: Opportunities and Solutions turns architectural gaps into candidate implementation building blocks and work packages. The actual reported symptoms are better explained by: Architecture scope is driven by the decision context rather than automatic enterprise-wide detail.
The offered principle describes: Phase H provides ongoing architecture change management, not first-time Architecture Vision approval. The situation in this question instead depends on: Architecture scope is driven by the decision context rather than automatic enterprise-wide detail. These are different technical conditions.
This alternative is valid when applying this distinction points to the response: Use Phase E to consolidate gaps into work packages and candidate transitions with an initial roadmap. The facts here establish a different controlling reason: Architecture scope is driven by the decision context rather than automatic enterprise-wide detail.