OGEA-101 Exam Dumps - TOGAF Enterprise Architecture Part 1 Exam (English)

According to the TOGAF standard, the two statements provided refer to different scopes within which architecture can be developed:

Groups of countries, governments, or governmental organizations working together typically align with broader, often international, scopes of architecture that transcend individual enterprise boundaries.

Partnerships and alliances of businesses working together, such as a consortium or supply chain, refer to collaborative efforts that can define architecture at a scope involving multiple enterprises.

In both cases, the term " Architectures Scopes " is appropriate because it reflects the varying levels and contexts in which architectures can be defined, ranging from single business units to collaborative inter-organizational efforts.

In TOGAF, Architecture Governance is concerned with establishing and operating the structures, processes, and controls that ensure architecture is properly managed and complied with across the enterprise. A central part of this practice is the implementation of controls over the creation and evolution of architectural components. This means governance is not only about defining architecture, but also about ensuring that architecture work products, building blocks, standards, and implementation activities are developed in a controlled and consistent way.

Option B is therefore the best answer because it reflects the core governance function of directing and controlling architecture-related work. Governance in TOGAF includes oversight, compliance assessment, decision rights, dispensations, and monitoring conformance to approved architectures and standards.

Option A may occur in leadership engagement, but it is not the clearest definition of architecture governance practice itself. Option C is incorrect because the Statement of Architecture Work is produced and maintained as part of ADM execution, especially early-phase planning, not as a defining governance practice throughout the full cycle. Option D relates more to stakeholder management and requirements management, which are important architecture activities, but they are not the best direct description of architecture governance.

Therefore, the correct answer is B.

The graphic represents the Architecture Alternatives and Trade-off technique described in the TOGAF ADM guidelines. This technique evaluates different architecture options against defined criteria derived from the Architecture Vision, Architecture Principles, and Requirements. The purpose of the method is to identify and compare multiple potential architecture approaches before selecting the most appropriate one.

In practice, architects generate several candidate architectures that could meet the enterprise’s needs. Each alternative is evaluated against criteria such as business value, risk, cost, compliance with principles, and alignment with requirements. Through structured comparison, stakeholders can understand the strengths and weaknesses of each alternative and select the most suitable architecture direction.

Because the evaluation process focuses on different architectural approaches for achieving the target state, the method is used to identify Alternative Target Architectures. These alternatives represent different ways the enterprise could structure its future architecture before committing to a single preferred solution.

The other options do not match the purpose of the diagram. Business Scenarios are used to understand requirements, Solution Building Blocks are implementation components, and Architecture Solutions represent final implementation outcomes rather than competing architecture options. Therefore, the method illustrated helps identify Alternative Target Architectures, making Option B the correct answer.

 In the ADM documents which are under development and have not undergone any formal review and approval process are called “draft”. This indicates that they are subject to change and refinement as the architecture development progresses. Reference: The TOGAF® Standard | The Open Group Website, Section 4.2.5 Architecture Deliverables.

In TOGAF, draft deliverables are those that are not yet finished or approved. They are work-in-progress versions that may have version numbers like 0.1, 0.5, or 0.9.

Once reviewed and approved, they become final deliverables.