Statements 1 and 3 highlight the value and necessity for Architecture Governance to be adopted within organizations. Architecture Governance is the practice and orientation by which Enterprise Architectures and other architectures are managed and controlled at an enterprise-wide level12. It ensures that architectural decisions are aligned with the organization's strategy, objectives, and standards. Architecture Governance also involves establishing and maintaining processes, decision-making, and mechanisms to avoid or minimize potential conflicts of interest, such as between different stakeholders, business units, or projects34. Moreover, Architecture Governance requires transparency and accountability for all actions implemented and their decision support, so that they can be inspected and evaluated by authorized parties, such as auditors, regulators, or customers5 . References:
*The TOGAF Standard, Version 9.2 - Architecture Governance - The Open Group
*Architecture Governance - The Open Group
*Tutorial: Governance in TOGAF's Architecture Development Method (ADM)
*Architecture Governance in TOGAF: Ensuring Effective Management and Compliance
*The TOGAF Standard, Version 9.2 - Definitions - The Open Group
*[Architecture Governance in TOGAF: Ensuring Alignment and Control]

Within the TOGAF Architecture Repository, the Architecture Capability component contains the organizational and governance support needed to operate the repository and the architecture function effectively. This includes the parameters, structures, roles, processes, and control mechanisms that allow the repository and architecture practice to be governed in a disciplined way. Because of that, option D is the correct match.
The other descriptions relate to different repository components. "The architectural representation of assets in use or planned" belongs more closely to the Landscape Repository, which captures current and planned architecture assets. "The standards with which new architectures must comply" corresponds to the Standards Information Base, where relevant standards and rules are maintained. "A record of governance activity across the enterprise" aligns with the Governance Log, which tracks governance-related actions and decisions.
"Authorized change requests from the Architecture Board" would be treated as governance-controlled change information rather than the Architecture Capability itself.
TOGAF distinguishes the Architecture Capability from the content held in the repository because capability is about how architecture is governed and supported, not only what architecture content is stored. Therefore, the correct answer is the parameters, structures, and processes to support governance of the Repository, which is option D.

EA applies architecture principles and practices to analyze, design, plan, and implement enterprise analysis that supports digital transformation, IT growth, and the modernization of IT2. EA also helps organizations improve the efficiency, timeliness, and reliability of business information, as well as the alignment, agility, and adaptability of the architecture to the changing needs and requirements3. Therefore, the best summary of the purpose of EA is to guide effective change.
References: 1: Enterprise architecture - Wikipedia 2: What is enterprise architecture? A framework for transformation 3: 3 The Purpose of Enterprise Architecture - The Open Group

When scoping an architecture in TOGAF, three key axes (dimensions) are used to frame the extent of the architecture work. The first is time period (how far into the future or over what timeframe to plan). The second is depth-how detailed or granular the architecture models will be (e.g., high level, mid level, very detailed). The third is breadth, which refers to which parts (domains, business units, functions) of the enterprise will be included, and which architecture domains (business, data, application, technology) will be in scope. This triple#dimension model helps architects, stakeholders, and governance bodies understand how wide, deep, and forward#looking the architecture effort will be. Thus "breadth, architecture domains" is the correct third dimension.