Question 580
At fictional Bayside Network Services, the following issue emerges in an architecture partitioning review: A large utility separates architectures into business units without documenting interoperability and common rules. Which response most directly resolves the architecture problem?
Explanation
Correct Answer
Partition architecture while defining interfaces and governance for shared cross-partition concerns. The issue requires this response because partitioning is useful only when independently handled areas remain coordinated as one enterprise architecture. Confirmation would be: The partitions remain manageable and shared services or integration boundaries have clear ownership. Applied here, the relevant facts are: A large utility separates architectures into business units without documenting interoperability and common rules.
Incorrect Answers
“Use flexible TOGAF guidance to align digital product evolution with enterprise outcomes and constraints” can be suitable where enterprise architecture can guide rapid digital change when tailored to context and scale. It does not resolve this question’s narrower failure, which follows: Partitioning is useful only when independently handled areas remain coordinated as one enterprise architecture. The relevant action is “Partition architecture while defining interfaces and governance for shared cross-partition concerns”.
The alternative focuses on the technical control described by: The TOGAF standard separates enduring fundamental content from supporting guides for applying it. The present requirement is governed by: Partitioning is useful only when independently handled areas remain coordinated as one enterprise architecture. Apply “Partition architecture while defining interfaces and governance for shared cross-partition concerns” to address that particular cause.
“Run appropriately coordinated ADM phases iteratively where their outputs depend on one another” can be suitable where aDM iteration enables concurrent and revisited phase work rather than prescribing rigid waterfall sequencing. It does not resolve this question’s narrower failure, which follows: Partitioning is useful only when independently handled areas remain coordinated as one enterprise architecture. The relevant action is “Partition architecture while defining interfaces and governance for shared cross-partition concerns”.