Which one of the following is an essential aspect of architecture governance?

Architecture Governance is the practice of managing and controlling enterprise architectures at a corporate level. A primary and essential aspect of this function is to ensure that implementation projects conform to the defined enterprise architecture. This involves establishing a system of controls over the implementation of the architecture, conducting compliance reviews, and managing dispensations. The goal is to ensure that the realized solution adheres to the principles, standards, and requirements set forth in the architecture, thereby delivering the intended business value and managing risk.

A. Authoring the Architecture Definition Document: This is a development activity performed during the ADM phases (B, C, D), not a primary governance function, which is about oversight.
C. Controlling the implementation and deployment organizations: Governance provides oversight and ensures compliance; it does not directly control or manage project teams, which is a project management function.
D. Authoring the Communications Plan for a given architecture project: This is a planning activity within Phase A of the ADM, not a core governance responsibility.
E. Conducting Business Scenarios: This is a technique used in Phase A to elicit requirements and understand the business context, not an aspect of governance.

1. The Open Group Standard, TOGAF® Version 9.2, Part VI, Chapter 44, "Architecture Governance". Section 44.1 introduces governance as the mechanism to ensure "compliance of all projects with the enterprise architecture".

2. The Open Group Standard, TOGAF® Version 9.2, Part VI, Chapter 44.2.1, "Architecture Governance Framework". This section details the processes, including "Compliance", which is described as a key area.

3. The Open Group Standard, TOGAF® Version 9.2, Part VI, Chapter 45, "Architecture Compliance". The entire chapter is dedicated to this essential governance activity.