Question 660
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. What sustained architecture control is most appropriate for this risk?
Explanation
Correct Answer
Audit shared dependencies after reorganizing architecture partitions. This safeguard addresses the recurring risk because partitioning is useful only when independently handled areas remain coordinated as one enterprise architecture. Immediate remediation would be: Partition architecture while defining interfaces and governance for shared cross-partition concerns. Applied here, the relevant facts are: A large utility separates architectures into business units without documenting interoperability and common rules.
Incorrect Answers
That review protects the control associated with: The architecture landscape organizes architectures by scope to support coherent decisions at multiple levels. It does not directly prevent the stated recurrence, which concerns: Partitioning is useful only when independently handled areas remain coordinated as one enterprise architecture. The appropriate guardrail is “Audit shared dependencies after reorganizing architecture partitions”.
This safeguard is for the dependency described by: Enterprise architecture can guide rapid digital change when tailored to context and scale. The continuing risk here is determined by: Partitioning is useful only when independently handled areas remain coordinated as one enterprise architecture. The targeted safeguard is “Audit shared dependencies after reorganizing architecture partitions”.
“Keep decision dependencies and feedback loops visible across phases” addresses a different recurring failure: The ADM permits iteration within and between phases so new facts can improve prior decisions. For the condition in this question, maintain “Audit shared dependencies after reorganizing architecture partitions” because partitioning is useful only when independently handled areas remain coordinated as one enterprise architecture.