Explanation
Architecture governance is the practice of ensuring compliance with the enterprise architecture and its principles, standards, and goals. Architecture governance provides the means to establish, monitor, and control the architecture development and implementation processes, and to resolve any issues or conflicts that may arise. Architecture governance also ensures that all stakeholders are represented and involved in the decision-making process, and that their interests and concerns are balanced and aligned. Statements 1 and 2 highlight the value and necessity for architecture governance to be adopted within organizations, as they emphasize the importance of responsibility, accountability, fairness, and transparency in the architectural activities. Statements 3 and 4 are more related to the benefits and outcomes of having a good enterprise architecture, rather than the governance aspect.References: : The TOGAF Standard, Version 9.2, Part VI:
Architecture Capability Framework, Chapter 50: Architecture Governance : The TOGAF Standard, Version
9.2, Part III: ADM Guidelines and Techniques, Chapter 29: Architecture Governance

* Phase A: Architecture Vision
o Develop a high-level aspirational vision of the capabilities and business value to be delivered as a result of the proposed Enterprise Architecture o Define the scope and boundaries of the architecture engagement o Identify the key stakeholders and their concerns and expectations o Define the Architecture Vision statement and the Architecture Definition Document o Obtain approval and commitment from the sponsors and stakeholders
* Phase B: Business Architecture
o Develop the Target Business Architecture that describes how the enterprise needs to operate to achieve the business goals o Define the Baseline Business Architecture, if not available o Perform a gap analysis between the Baseline and Target Business Architectures o Define candidate roadmap components for the Business Architecture o Resolve impacts across the Architecture Landscape
* Phase C: Information Systems Architecture
o Develop the Target Data Architecture that enables the Business Architecture and the Architecture Vision o Develop the Target Application Architecture that supports the Business Architecture and the Architecture Vision o Define the Baseline Data and Application Architectures, if not available o Perform a gap analysis between the Baseline and Target Data and Application Architectures o Define candidate roadmap components for the Information Systems Architecture o Resolve impacts across the Architecture Landscape
* Phase D: Technology Architecture
o Develop the Target Technology Architecture that enables the Information Systems Architecture and the Architecture Vision o Define the Baseline Technology Architecture, if not available o Perform a gap analysis between the Baseline and Target Technology Architectures o Identify candidate Architecture Roadmap components based upon gaps between the Baseline and Target Technology Architectures o Resolve impacts across the Architecture Landscape Therefore, the correct matching of the objectives and the phases is:
* 1C: Develop the Target Data Architecture that enables the Business Architecture and the Architecture Vision
* 2B: Develop the Target Business Architecture that describes how the enterprise needs to operate to achieve the business goals
* 3A: Develop a high-level aspirational vision of the capabilities and business value to be delivered as a result of the proposed Enterprise Architecture
* 4D: Identify candidate Architecture Roadmap components based upon gaps between the Baseline and Target Technology Architectures

The four dimensions used to scope an architecture are Breadth, Depth, Time Period, and Architecture Domains. Breadth refers to the extent of the enterprise covered by the architecture. Depth refers to the level of detail and completeness of the architecture. Time Period refers to the planning horizon and the number of Transition Architectures required to achieve the Target Architecture. Architecture Domains refer to the four domains of Business, Data, Application, and Technology that constitute an enterprise's architecture. Reference: The TOGAF Standard | The Open Group Website, Section 3.2.1 Phase A: Architecture Vision.

The Architecture Requirements Repository stores all the requirements that are output of the architecture development cycle, as well as the requirements that are input to the architecture development cycle1. The Architecture Requirements Repository includes the following types of requirements1:
*Stakeholder Requirements: These are the high-level requirements and expectations of the stakeholders, derived from the business drivers, goals, and objectives. They are captured and refined in the Architecture Vision phase and the Requirements Management phase.
*Architecture Requirements: These are the detailed requirements that specify what the architecture must do or deliver to meet the stakeholder requirements. They are derived and refined in the Business, Information Systems, and Technology Architecture phases.
*Implementation and Migration Requirements: These are the detailed requirements that specify what the implementation and migration projects must do or deliver to realize the architecture. They are derived and refined in the Opportunities and Solutions and Migration Planning phases.
The Architecture Requirements Repository is used to manage the architecture requirements throughout the architecture lifecycle, ensuring their traceability, consistency, and compliance1. The Architecture Board is the authority that reviews and approves the architecture requirements, as well as the architecture deliverables and artifacts, as part of the architecture governance process2.
References: 1: Architecture Requirements Repository 2: Architecture Board

Explanation
The objective of the ADM Implementation Governance Phase is to provide an architectural oversight of the implementation and to ensure conformance for the target architecture. This phase involves establishing procedures and processes to monitor and control the implementation projects and to verify that they comply with the defined architecture. Reference: The TOGAF Standard | The Open Group Website, Section 3.2.7 Phase G: Implementation Governance.