Question 120
At fictional Summit Square Mobility, during a cross-agency architecture review, stakeholders identify: An architect describes customer onboarding solely as a software deployment without analyzing responsibilities, rules, or business services. What should the architecture team do first to correct this issue?
Explanation
Correct Answer
Add the missing relevant architecture domains and connect each domain to the shared business outcome. The issue requires this response because the four domains offer complementary perspectives on the enterprise rather than interchangeable labels. Confirmation would be: Stakeholders can see how business responsibilities, data, applications, and technology each contribute to the solution.
Incorrect Answers
The alternative focuses on the technical control described by: Architecture capability includes people, practices, decision rights, and supporting assets working together. The present requirement is governed by: The four domains offer complementary perspectives on the enterprise rather than interchangeable labels. Apply “Add the missing relevant architecture domains and connect each domain to the shared business outcome” to address that particular cause.
“Adopt and tailor the TOGAF framework's reusable method and concepts to the organization's needs rather than replacing them wholesale” can be suitable where the TOGAF standard provides a configurable structure and common method for enterprise architecture work. It does not resolve this question’s narrower failure, which follows: The four domains offer complementary perspectives on the enterprise rather than interchangeable labels. The relevant action is “Add the missing relevant architecture domains and connect each domain to the shared business outcome”.
The offered action, “Organize governed architecture assets within an Architecture Repository with clear categories and accountable ownership”, addresses a different dependency: The architecture repository is a structured store for architecture-related information and work products. The failure reported here instead follows: The four domains offer complementary perspectives on the enterprise rather than interchangeable labels. The targeted response is “Add the missing relevant architecture domains and connect each domain to the shared business outcome”.