Sign in
Home/The Open Group/TOGAF 9 Part 1 Examination (OG0-091)/Free questions

TOGAF 9 Part 1 Examination (OG0-091) — Free Practice Questions

10 free sample questions from a bank of 275, with the correct answers and explanations. No signup required — start practising right now.

1According to TOGAF, which of the following are the architecture domains that are commonly accepted subsets of an overall enterprise architecture?
  • Application, Business, Data, Technology
  • Capability, Segment, Strategic
  • Context, Definition, Governance, Transformation
  • Definition, Realization, Transition, Vision
Answer: A

The short version

A — Business, Data, Application and Technology are the four TOGAF domains. They partition enterprise concerns into commonly accepted subsets. Other lists mix levels or ADM artifacts.

Key concepts in this question

  • Business Architecture: strategy, governance, org and key processes that create value.
  • Data Architecture: logical and physical data assets, management and governance.
  • Application Architecture: app portfolio, interactions and alignment to business.
  • Technology Architecture: software and hardware infrastructure enabling deployment.
  • BDAT shorthand: memorizing the four prevents confusion with capability or phase terms.

Why A is correct

A is correct because TOGAF defines those four as the architecture domains developed in phases B through D. Business comes first, then Information Systems split into Data and Application, then Technology grounds them in platform. Capability, segment and strategic describe scope slices, while context and vision describe ADM products, not domains. The settled key repeats the standard BDAT set taught across official guides.

Why the others are wrong

  • B. lists capability, segment and strategic, which classify architecture scope, not domains.
  • C. lists context and governance terms, which are ADM concerns, not the four subsets.
  • D. lists vision and transition terms, which are phase outputs, not enduring domains.

OG0-091 exam tip

Domains equal BDAT. Scope words like segment or capability never equal domains.

2Which of the following is the architecture domain that describes the logical software and hardware capabilities?
  • Application Architecture
  • Business Architecture
  • Data Architecture
  • Technology Architecture
Answer: D

The short version

D — Technology Architecture covers logical software and hardware capabilities. It describes infrastructure needed to host business and systems. App, business and data cover other layers.

Key concepts in this question

  • Technology scope: IT infrastructure, middleware, networks, compute and standards.
  • Logical emphasis: required capabilities and services, not yet specific products.
  • Support role: enables deployment of business, data and application services.
  • App contrast: application portfolio and interactions, not underlying platform.
  • Business and data contrast: processes versus information assets, both depend on tech.

Why D is correct

D is correct because official TOGAF text defines Technology Architecture as the logical software and hardware capabilities supporting deployment of higher layers. That includes servers, storage, networks, middleware and communications standards. Application Architecture stops at software portfolios, Business at processes, Data at information. The stem wording mirrors the manual sentence on infrastructure capabilities, so D is the direct match.

Why the others are wrong

  • A. covers application portfolio logic, not infrastructure capabilities.
  • B. covers strategy and processes, far above platform hardware.
  • C. covers data entities and management, not hosting infrastructure.

OG0-091 exam tip

Hardware plus software capabilities equals Technology. Portfolio equals Application, process equals Business.

3According to TOGAF, Which of the following best describes the classification of architectural change in the case where multiple server systems are being consolidated to a single system?
  • A bottom-up change to enhance operational capability
  • An incremental change handled via change management techniques
  • A re-architecting change that puts the whole architecture through an ADM cycle
  • A revision change of the enterprise architecture
  • A simplification change handled via change management techniques
Answer: E

The short version

E — Consolidating servers is a simplification change via change management. Physical consolidation without altering above layers streamlines the baseline. It is not re-architecting or incremental enhancement.

Key concepts in this question

  • Simplification change: reduces complexity at infrastructure level, handled by change control.
  • Baseline update: Technology Architecture description changes while higher layers stay stable.
  • Incremental contrast: small capability lift, not the consolidation pattern.
  • Re-architecting contrast: full ADM cycle for pervasive business or system shifts.
  • Bottom-up contrast: operational enhancement push, not infra reduction.

Why E is correct

E is correct because TOGAF change taxonomy treats ten systems to one as a simplification handled via change management techniques. The move changes the Technology baseline but does not reframe business or application architecture, so no full ADM loop is needed. Vendor quote cites infrastructure reduction as the textbook simplification example. That matches server consolidation exactly, making E the settled classification.

Why the others are wrong

  • A. bottom-up enhancement adds capability, opposite of consolidation reduction.
  • B. incremental change is generic small evolution, missing the simplification label.
  • C. re-architecting demands whole ADM cycle for broad impact, overkill for infra merge.
  • D. revision wording does not capture the simplification via change management definition.

OG0-091 exam tip

Many to one servers equals simplification. Full cycle equals re-architecting, small lift equals incremental.

4Which of the following statements best describes the purpose of enterprise architecture?
  • To allow an enterprise to exploit the latest trends in technology
  • To enable the CIO to take effective control of the business units across an enterprise
  • To ensure compliance in an enterprise to corporate auditing standards
  • To optimise an enterprise into an environment that is responsive to business needs
  • To provide a set of standards that all actors must adhere to within an enterprise
Answer: D

The short version

D — Enterprise architecture optimizes the enterprise to be responsive to business needs. It integrates fragmented legacy into a change-ready whole. Tech trends, CIO control or audit alone miss that purpose.

Key concepts in this question

  • Integration goal: unify manual and automated processes fragmented over time.
  • Responsiveness: environment that adapts to strategy shifts and market change.
  • Business alignment: architecture serves delivery of strategy, not tech novelty.
  • Control myth: CIO empowerment is a side effect, not the defined purpose.
  • Standards myth: norms help, but optimization for agility is the higher aim.

Why D is correct

D is correct because the Open Group defines the purpose as optimizing across the enterprise the fragmented legacy into an integrated environment responsive to change and supportive of strategy delivery. That wording centers business agility through coherence. Exploiting trends is opportunistic, CIO control is political, audit compliance is narrow, and mandatory standards are means, not ends. Only D captures optimization plus responsiveness.

Why the others are wrong

  • A. chasing latest trends risks novelty without integration or business support.
  • B. CIO control over units narrows architecture to power, not enterprise responsiveness.
  • C. audit compliance is a constraint to satisfy, not the architecture purpose.
  • E. mandatory standards describe governance output, not the optimization outcome.

OG0-091 exam tip

Purpose equals optimize fragmented legacy into responsive integrated environment. Memorize that sentence.

5Which of the following statements best describes how Architecture Principles are used within the ADM?
  • They are used to define the framework and detailed methodologies
  • They are used to define stakeholders and their concerns
  • They are used to determine the readiness factors impacting the organization
  • They are used to guide decision making within the enterprise
  • They are used to resolve and dispose of requirements
Answer: D

The short version

D — Principles guide decision making across the ADM. They encode enduring business and IT values that shape tradeoffs. Framework, stakeholders or disposal describe other artifacts.

Key concepts in this question

  • Principle nature: durable maxims with rationale and implications for choices.
  • Decision filter: used to judge options, resolve conflicts and keep alignment.
  • Framework contrast: methods and metamodels structure work, principles steer judgment within it.
  • Stakeholder contrast: concerns are captured in views, principles constrain solutions for them.
  • Requirements contrast: disposal is a repository workflow, not principle use.

Why D is correct

D is correct because TOGAF Architecture Principles exist to guide enterprise decision making from vision through implementation. Teams test candidate architectures against principles like reuse or business continuity, ensuring coherence when options clash. They do not define the framework itself, identify stakeholders, assess readiness or dispose requirements. Official chapter on principles frames them as decision guides, matching D exactly.

Why the others are wrong

  • A. framework and methods are defined by ADM structure and metamodel, not by principles.
  • B. stakeholders and concerns are captured via viewpoints, principles then serve those parties.
  • C. readiness factors use separate assessments, principles inform but do not determine them.
  • E. requirement disposal belongs to repository management, not principle application.

OG0-091 exam tip

Principles equal guide decisions. Framework equals method, stakeholder equals concern, disposal equals repository.

6Which of the following statements about TOGAF Building Blocks and their use in the ADM cycle is correct?
  • Building Blocks become more implementation-specific in Phase E
  • Building Blocks in phases D, E and F are evolved to a common pattern of steps
  • Building Blocks should be identified in abstract form as part of the Preliminary Phase
  • Building Blocks should be first selected in Phase D
Answer: A

The short version

A — Blocks grow implementation-specific in Phase E. Opportunities and migration planning turns logical blocks into solution blocks tied to work packages. Earlier phases keep them abstract.

Key concepts in this question

  • Building blocks: reusable capability chunks, from abstract architecture blocks to concrete solution blocks.
  • Phase E role: associate gaps with work packages and plan delivery increments.
  • Specificity shift: gaps mapped to vendors, products and deployment details.
  • Preliminary contrast: governance and tailoring, not first abstract identification as sole home.
  • Phase D contrast: technology design selects, but E makes them delivery ready.

Why A is correct

A is correct because TOGAF states building blocks become more implementation-specific in Phase E as solution blocks address gaps. Phases B through D evolve architecture blocks logically, then E links them to work packages, costs and schedules with product choices. That specificity jump is the textbook Phase E marker. Other options misplace identification timing or invent a common steps pattern for D through F that the guide does not teach.

Why the others are wrong

  • B. common steps across D, E and F misstates distinct phase purposes and block handling.
  • C. preliminary abstract identification alone understates iterative block work across ADM.
  • D. first selection only in D ignores earlier business and systems block definition.

OG0-091 exam tip

Phase E equals blocks become specific plus gaps to work packages. Link specificity to migration planning.

7Which one of the following is an objective of Phase A of the TOGAF ADM?
  • To allocate the resources needed to implement the architecture project
  • To define the framework that is going to be used to develop the enterprise architecture
  • To define an IT Strategy that maps out the technology infrastructure
  • To prepare a Solution Architecture for the enterprise
  • To secure formal approval to proceed
Answer: E

The short version

E — Phase A secures formal approval to proceed. Vision and value must earn mandate before detailed work. Resourcing, framework or IT strategy belong elsewhere.

Key concepts in this question

  • Architecture Vision: high-level target plus value case that convinces sponsors.
  • Approval gate: Statement of Work sign-off authorizes B through H effort.
  • Resource contrast: allocation details mature in migration planning, not vision approval.
  • Framework contrast: tailoring happens in Preliminary, not as Phase A objective.
  • Strategy contrast: IT mapping is downstream design, not the approval milestone.

Why E is correct

E is correct because TOGAF lists securing formal approval to proceed as a core Phase A objective alongside vision and stakeholder agreement. Without that mandate, deeper business, systems and technology work lacks authority and funding. Allocating implementation resources, defining the framework, drafting IT strategy or building solution architecture all follow or sit outside A. The exam phrase matches the manual objective verbatim.

Why the others are wrong

  • A. resource allocation for implementation matures in E and F, not vision approval.
  • B. framework definition is Preliminary tailoring, not a Phase A deliverable.
  • C. IT infrastructure strategy is detailed design, downstream of vision sign-off.
  • D. solution architecture for the enterprise is built in later phases, not A.

OG0-091 exam tip

Phase A equals vision plus approval to proceed. Framework equals Preliminary, build equals later.

8Complete the sentence. TOGAF 9 Part III provides a set of resources that can be used to adapt and modify the ____________.
  • Architecture Capability
  • Architecture Development Method
  • Architecture Landscape
  • Architecture Repository
  • Enterprise Continuum
Answer: B

The short version

B — Part III adapts the Architecture Development Method. Guidelines tailor iteration, landscape and styles. Capability, landscape or repository are adapted by other means.

Key concepts in this question

  • Part III scope: ADM Guidelines and Techniques for iteration and specialized use.
  • Adaptation tools: applying iteration, working across landscape levels, handling styles like security.
  • ADM focus: process tailoring, not capability building or repository structure.
  • Capability contrast: establishment of practice lives in Part VII style guidance.
  • Continuum contrast: classification and reuse live in Enterprise Continuum chapters.

Why B is correct

B is correct because TOGAF 9 Part III collects resources to adapt and modify the ADM process itself. It shows how to iterate phases, engage at capability versus segment levels, and blend specialist architectures. Architecture Capability, Landscape, Repository and Continuum are distinct constructs with their own chapters. The sentence stem mirrors the manual intro on adapting the ADM, so B completes it.

Why the others are wrong

  • A. capability building is governed elsewhere, Part III tailors process execution.
  • C. landscape describes engagement tiers, it is a lens for ADM, not the adapted object.
  • D. repository structure is content storage, not the method being modified.
  • E. continuum organizes reuse, separate from method adaptation guidance.

OG0-091 exam tip

Part III equals adapt the ADM. Capability, repository and continuum are different parts.

9Which of the following best describes how TOGAF defines an enterprise?
  • Any collection of organizations that has a common set of goals
  • Any corporation with more than 10,000 employees
  • Any organization involved in commerce
  • Any organization whose stock is traded
  • Any set of organizations based at the same geographic location
Answer: A

The short version

A — Enterprise is any collection with common goals. Size, commerce or listing do not define it. Shared purpose allows government, supply chain or federated scope.

Key concepts in this question

  • Broad definition: TOGAF avoids limiting enterprise to one company or sector.
  • Goal bond: joint objectives justify joint architecture across orgs.
  • Size myth: headcount thresholds never appear in the definition.
  • Commerce myth: non-profits and agencies can be enterprises under TOGAF.
  • Place myth: co-location is irrelevant to architectural scope.

Why A is correct

A is correct because the manual defines an enterprise as any collection of organizations with common goals, from business unit to cross-agency ecosystem. That breadth lets TOGAF serve mergers, supply chains and public federations. Corporation size, commercial activity, stock listing or geography would exclude valid cases the framework must support. Only A preserves purpose-driven scoping.

Why the others are wrong

  • B. headcount limit excludes small firms and federations that still need architecture.
  • C. commerce limit excludes government and non-profit enterprises.
  • D. traded stock limit confuses legal form with architectural scope.
  • E. same location limit ignores distributed and virtual enterprises.

OG0-091 exam tip

Enterprise equals common goals, any collection. Size, commerce, listing or place are traps.

10Which of the following is an objective of Phase B, Business Architecture?
  • To confirm the ability of the enterprise to undergo change
  • To demonstrate how stakeholder concerns are addressed in the Business Architecture
  • To develop a Target Technology Architecture to support the business
  • To finalize the Architecture Vision and Architecture Definition documents
  • To maximize the business value from the architecture
Answer: B

The short version

B — Phase B shows stakeholder concerns met in Business Architecture. Target business design must trace to drivers and viewpoints. Change ability, tech design or value max belong to other aims.

Key concepts in this question

  • Business focus: org, functions, processes and information flows at target.
  • Concern trace: each key stakeholder issue gets modeled response and rationale.
  • Readiness contrast: ability to change is assessed in requirements and implementation phases.
  • Tech contrast: target technology to support business is Phase D, not B.
  • Document contrast: finalizing vision docs spans A and later, not the B objective.

Why B is correct

B is correct because TOGAF Phase B objectives include demonstrating how stakeholder concerns are addressed in the Business Architecture. Modelers capture drivers, goals and viewpoints, then show coverage in baseline-to-target gaps and views. Confirming change appetite, building tech target, finalizing vision docs or maximizing value are valid worries but not the stated B proof point. B alone names the concern-to-model accountability.

Why the others are wrong

  • A. change ability confirmation belongs to readiness and migration assessment.
  • C. target technology support is the Phase D deliverable, not business proof.
  • D. finalizing vision and definition docs is a cross-phase control, not B specific.
  • E. maximizing value is an overarching benefit, not the testable B objective.

OG0-091 exam tip

Phase B equals business plus stakeholder coverage. Tech target equals D, change equals readiness.

Want the full bank of 275 questions for TOGAF 9 Part 1 Examination (OG0-091)? See all practice exams.