TOGAF Enterprise Architecture Part 1 Examination (OGEA-101) — Free Practice Questions
10 free sample questions from a bank of 108, with the correct answers and explanations. No signup required — start practising right now.
1Which statement about Requirements Management is most correct?
Requirements Management and stakeholder engagement are placed at the center of architecture development.
Stakeholder requirements are captured once in Phase A and managed throughout the ADM cycle.
Requirements Management is a step of all ADM Phases.
The purpose of Requirements Management is to process change requests.
Answer: A
The short version
A — Requirements Management sits at the center of architecture development. It works with continuous stakeholder engagement, not as a one-time capture or single phase step.
Key concepts in this question
Central Requirements Management: ADM places requirements and stakeholder engagement at the hub connecting all phases.
Continuous handling: identification, storage, monitoring, and change handling run throughout the cycle.
Phase A capture myth: requirements are not frozen after Vision but evolve with every domain phase.
Step vs activity: Requirements Management is an ongoing activity, not a discrete step inside each phase.
Why A is correct
TOGAF ADM depicts Requirements Management at the center, linked to every phase, with stakeholder engagement driving elicitation and prioritization. That central continuous positioning is exactly option A. The method stresses dynamic handling of requirements as architectures mature, which rules out once-only or step-based readings. Vendor and community agreement at 89 percent corroborates this central-hub model as the most correct characterization.
Why the others are wrong
B. Captured once in Phase A contradicts the continuous evolution and monitoring role across the ADM.
C. A step of all phases mislabels it, TOGAF calls it a continuous central activity, not a repeated step.
D. Processing change requests is only part of the job, the purpose spans elicitation, traceability, and governance.
OGEA-101 exam tip
Center of the ADM crop-circle diagram equals Requirements Management with stakeholders.
2Which of the following best describes the purpose of the Gap Analysis technique?
To govern the architecture throughout its implementation process
To develop a set of general rules and guidelines for the architecture
To allocate resources for architecture projects
To identify items omitted from the Target Architecture
Answer: D
The short version
D — Gap Analysis finds what the Target omits versus the Baseline. It validates the developing architecture by highlighting shortfalls, so deliberately omitted, accidentally left out, or not yet defined items are made explicit.
Key concepts in this question
Baseline Architecture: the description of the existing implemented state used as the start point for change.
Target Architecture: the description of the desired future state that the ADM cycle is working toward.
Gap Analysis technique: the TOGAF ADM technique in chapter 5 of ADM Techniques that compares Baseline to Target to validate completeness.
Architecture governance vs validation: governance controls implementation, while Gap Analysis checks content completeness during development.
Why D is correct
TOGAF Standard ADM Techniques defines Gap Analysis as the method to highlight the shortfall between Baseline and Target Architecture. It explicitly covers items deliberately omitted, accidentally left out, or not yet defined. That matches option D word for word in intent, and the cited reference pubs.opengroup.org ADM Techniques chapter 5 confirms this purpose. No other ADM technique has this Baseline-to-Target validation role.
Why the others are wrong
A. Governing the architecture through implementation is Architecture Governance and Phase G compliance, not a comparison technique.
B. General rules and guidelines describe Architecture Principles, which direct decisions rather than compare states.
C. Allocating resources for projects is portfolio or implementation planning, not the analytical job of finding gaps.
OGEA-101 exam tip
Remember Gap equals Gone-missing from Target: Baseline minus Target equals to-do list, so link Gap Analysis to Phases B, C, D and E planning.
3Complete the following sentence:
Presenting different ________________ and ______________ to stakeholders helps architects to extract hidden agendas, principles, and requirements that could impact the final Target Architecture.
Architecture Views, Architecture Viewpoints
Alternatives, Trade-offs
Business Scenarios, Business Models
Solutions, Applications
Answer: B
The short version
B — Alternatives and trade-offs surface hidden agendas and requirements. Showing stakeholders different options forces preferences, principles, and constraints into the open before the Target Architecture is fixed.
Key concepts in this question
Architecture alternatives: distinct candidate Target responses to the same drivers, used to explore the solution space.
Trade-offs: explicit comparisons of benefit, cost, risk, and impact across alternatives to support selection.
Stakeholder hidden agendas: unstated concerns or success criteria that emerge only when people react to concrete options.
ADM Technique chapter 10: the TOGAF guidance on alternatives and trade-offs for stakeholder engagement.
Why B is correct
The TOGAF Standard ADM Techniques chapter on alternatives states this sentence verbatim: presenting different alternatives and trade-offs helps extract hidden agendas, principles, and requirements that could impact the final Target Architecture. That is exactly the stem wording, so B is a direct definitional match confirmed by the official reference. The other pairs name real TOGAF artifacts but never appear in this stakeholder elicitation context.
Why the others are wrong
A. Views and viewpoints present the architecture for specific concerns, but the stem is about offering choices to provoke feedback, not about presentation formats.
C. Business Scenarios and Business Models help understand requirements, yet the quoted TOGAF sentence uses alternatives language, not scenario language.
D. Solutions and Applications are implementation outputs, not the decision options used during early elicitation.
OGEA-101 exam tip
Link trade-offs to truth extraction: when the question mentions hidden agendas, choose alternatives and trade-offs every time.
4Consider the following statements related to the TOGAF ADM.
1. All ADM activities are carried out within an iterative cycle of continuous architecture definition and realization
2. The Requirements Management phase is a continuous phase
3. Output from an early phase must not be modified in a later phase
4. The lifecycle of outputs must be managed through a versioning policy
Which statements are correct?
1, 2 & 4
2, 3 & 4
1, 2 & 3
1, 3 & 4
Answer: A
The short version
A — Statements 1, 2 and 4 are true, statement 3 is false. The ADM is iterative, Requirements Management is continuous, outputs are versioned, and early outputs may be modified later.
Key concepts in this question
Iterative ADM cycle: architecture definition and realization proceed through repeated cycles, not a single strict waterfall pass.
Requirements Management as central continuous activity: runs alongside all phases, handling identification, storage, and monitoring of requirements.
Output mutability: early phase outputs may be revisited and changed when later work reveals new insight.
Versioning and lifecycle control: outputs are managed through version control across the ADM.
Why A is correct
TOGAF ADM introduction states all ADM activities occur within an iterative cycle of continuous definition and realization, supporting statement 1. It places Requirements Management at the center as a continuous phase, supporting statement 2. It requires lifecycle management of outputs through versioning, supporting statement 4. It explicitly says output from an early phase may be modified in a later phase, which directly falsifies statement 3. Only combination A keeps the three true statements and excludes the false one.
Why the others are wrong
B. Includes 3, which contradicts the explicit TOGAF rule that early outputs may be modified later.
C. Includes 3 and drops 4, keeping the false mutability ban while losing the true versioning requirement.
D. Includes 3 and drops 2, keeping the false claim while omitting continuous Requirements Management.
OGEA-101 exam tip
Memorize the ADM mantra: iterative, always-on requirements, everything versioned, nothing frozen too early.
5Which of the following are the four purposes that typically frame the planning horizon, depth and breadth of an Architecture Project, and the contents of the EA Repository?
Segment, Capability, Enterprise, and End-to-end Target Architecture
General, Foundational, Subordinate, and Superior Architecture
Strategy, Portfolio, Project, Solution Delivery
Avant-Garde, Big-Bang, Discreet, and Cohesive
Answer: C
The short version
C — The four purposes are Strategy, Portfolio, Project, and Solution Delivery. They frame horizon, depth, breadth, and Repository contents for an Architecture Project.
Key concepts in this question
Strategy purpose: enterprise direction and long-horizon planning guiding architecture intent.
Portfolio and Project purposes: program grouping and single-project delivery scopes with mid horizons.
Solution Delivery purpose: detailed implementation-level architecture for building and deployment.
Planning horizon framing: purposes determine how far ahead, how broad, and how deep to architect.
Why C is correct
TOGAF guidance on architecture purposes defines exactly these four: Strategy, Portfolio, Project, and Solution Delivery. They are used to frame planning horizon, depth and breadth, and what belongs in the EA Repository for a given effort. The settled key C matches this canonical list, confirmed by unanimous community agreement. The other groupings mix landscape levels, generic adjectives, or invented style labels that TOGAF never uses for purposes.
Why the others are wrong
A. Segment, Capability, Enterprise, and End-to-end Target mix landscape granularity with target states, not purposes.
B. General, Foundational, Subordinate, and Superior are not TOGAF purpose names and have no horizon meaning.
D. Avant-Garde, Big-Bang, Discreet, and Cohesive describe delivery styles, not architecture purposes.
OGEA-101 exam tip
Purposes from big to small: Strategy steers, Portfolio groups, Project delivers, Solution builds.
6Complete the sentence. The purpose of Enterprise Architecture is to ________.
govern the stakeholders.
control the bigger changes.
guide effective change.
take major improvement decisions.
Answer: C
The short version
C — Enterprise Architecture exists to guide effective change. It provides a coherent view of current and future states to steer transformation.
Key concepts in this question
Guide effective change: core EA value of directing transformation with clarity and consistency.
Coherent enterprise view: connecting strategy, business, information, and technology across states.
Govern vs control vs decide: oversight and choices are means, guided change is the end.
Current to future transition: Baseline to Target progression enabled by shared understanding.
Why C is correct
TOGAF purpose statements define Enterprise Architecture as guiding effective change by providing coherent and consistent views of current and future states. That wording aligns exactly with option C and the vendor prose. EA does not exist to govern stakeholders as people, merely control large changes, or take isolated major decisions. Its purpose is enabling the enterprise to change purposefully with full context.
Why the others are wrong
A. Govern the stakeholders misplaces governance onto people rather than guiding change through architecture.
B. Control the bigger changes is too narrow and reactive, missing coherent guidance toward the future.
D. Take major improvement decisions is an outcome of guidance, not the defined purpose itself.
OGEA-101 exam tip
EA purpose in three words: guide effective change, always choose that phrasing.
7Which of the following best describes the need for the ADM process to be governed?
To permit the architecture domains to be integrated
To enable development of reference architectures
To enable a fast response to market changes
To verify that the method is being applied correctly
Answer: D
The short version
D — The ADM must be governed to verify the method is applied correctly. Governance keeps domain integration and delivery faithful to the process.
Key concepts in this question
ADM governance need: oversight ensuring the method is followed consistently and correctly.
Correct application: adherence to phases, inputs, outputs, and iteration discipline.
Integration and speed: domain joining and fast response are benefits, not the governance rationale.
Reference architectures: reusable outputs enabled by good practice, not the reason to govern the process.
Why D is correct
TOGAF stresses governing the ADM process itself so architecture work follows the method, meets quality, and stays compliant. Option D captures this directly: verify the method is being applied correctly. Integration of domains happens through the method when governed, but governance exists to ensure that correct application. The settled and community agreement confirms D as the best expression of process governance need.
Why the others are wrong
A. Permitting domain integration is a result of correct ADM use, not the primary governance need.
B. Enabling reference architectures is a Repository outcome, not why the process requires oversight.
C. Fast market response is an agility benefit, not the control reason for governing ADM execution.
OGEA-101 exam tip
Govern the method to keep it honest: ADM governance equals correct application check.
8Which of the following describes the practice by which the enterprise architecture is managed and controlled at an enterprise-wide level?
Corporate governance
IT governance
Technology governance
Architecture governance
Answer: D
The short version
D — Architecture governance manages and controls architectures enterprise-wide. It is the distinct practice for directing enterprise architecture development and compliance at scale.
Key concepts in this question
Architecture Governance: practice and orientation for managing architectures and related activities across the enterprise.
Corporate governance: broader system by which enterprises are directed and controlled, of which architecture governance is one domain.
IT and technology governance: narrower control of IT resources or technology choices, not the whole architecture practice.
Enterprise-wide control: setting compliance, decision rights, and oversight for all architecture work.
Why D is correct
The TOGAF Standard EA Capability and Governance section defines Architecture Governance with this exact phrasing: the practice and orientation by which Enterprise Architectures and other architectures are managed and controlled at an enterprise-wide level. The stem repeats that definition almost verbatim, so D is a direct match. The governance chapter lists its characteristics including compliance, decision-making basis, and reuse targets, confirming this scope.
Why the others are wrong
A. Corporate governance directs the whole enterprise, too broad and not specific to managing architectures.
B. IT governance controls IT use and value, a subset that does not cover business and enterprise architecture management.
C. Technology governance controls technology selection and standards, narrower than enterprise-wide architecture control.
OGEA-101 exam tip
When you see managed and controlled at enterprise-wide level, answer Architecture Governance without hesitation.
9Which of the following best describes purpose of the Business Scenarios?
To guide decision making throughout the enterprise
To catch errors in a project architecture early
To identify risk when implementing an architecture project
To identify and understand requirements
Answer: D
The short version
D — Business Scenarios identify and understand requirements. They elicit business needs by walking through real operational situations.
Key concepts in this question
Business Scenarios technique: structured method to discover business problems and requirements.
Requirements identification: surfacing what the business needs from actors, roles, and processes.
Decision and risk uses: guidance and error catching are secondary benefits, not the core purpose.
Phase A grounding: scenarios feed Vision with stakeholder-driven business understanding.
Why D is correct
TOGAF ADM Techniques defines Business Scenarios as the method to identify and understand requirements, especially business requirements driving architecture. Scenarios explore actors, activities, and outcomes to reveal needs that shape Vision and domain architectures. Options about guiding decisions, catching errors early, or identifying project risk describe useful side effects but not the defined purpose. Only D states the requirements discovery mission.
Why the others are wrong
A. Guiding enterprise decision-making describes Architecture Principles, broader than scenario elicitation.
B. Catching project errors early is a quality benefit, not the scenario purpose of requirements discovery.
C. Identifying implementation risk belongs to Risk Management and readiness work, not scenarios.
OGEA-101 exam tip
Scenarios equal stories to find needs: Business Scenarios always mean requirements discovery.
10What is an objective of the ADM Implementation Governance Phase?
To ensure conformance for the target architecture
To establish the resources for architecture governance
To provide continual monitoring of the governance framework
To finalize the Implementation and Migration Plan
Answer: A
The short version
A — Phase G ensures implementation conformance with the Target Architecture. Implementation Governance exists to keep projects faithful to the defined architecture through governance controls.
Key concepts in this question
Phase G Implementation Governance: ADM phase that oversees solution delivery against the approved architecture.
Conformance and compliance: verifying projects adhere to Target Architecture, standards, and contracts.
Architecture Contracts: agreements that bind implementation to architecture intent and enable monitoring.
Phase E and F vs G: E and F plan migration and packaging, G governs actual build and deployment.
Why A is correct
TOGAF ADM Phase G objectives list ensuring conformance with the Target Architecture by implementation projects as the first objective, plus performing governance over solutions and change requests. That is exactly option A and matches the cited ADM chapter 11 reference. The phase uses Compliance Assessments, Architecture Contracts, and Change Requests to enforce this conformance during delivery.
Why the others are wrong
B. Establishing resources for governance belongs mainly to Preliminary Phase capability setup, not Phase G execution.
C. Continual monitoring of the governance framework is an EA Capability concern, not the Phase G objective of project conformance.
D. Finalizing the Implementation and Migration Plan is Phase F work, completed before Phase G oversight begins.
OGEA-101 exam tip
Link G to Go-live guarding: Phase G governs the build, Phase F finalizes the plan, Phase E maps the work.