Sign in
Home/The Open Group/TOGAF 9 Combined Part 1 and Part 2 Examination (OG0-093)/Free questions

TOGAF 9 Combined Part 1 and Part 2 Examination (OG0-093) — Free Practice Questions

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

1Which of the following TOGAF components was created to enable architects to design architectures addressing Boundaryless Information Flow?
  • The Architecture Repository
  • The Enterprise Continuum
  • The Integrated Information Infrastructure Model
  • The TOGAF Technical Reference Model
Answer: C

The short version

C — Integrated Information Infrastructure Model enables Boundaryless Information Flow. III-RM gives architects a reference for interoperable information systems that cross organizational limits securely.

Key concepts in this question

  • Boundaryless Information Flow: Open Group vision for trusted, timely information access across enterprise and partner boundaries.
  • III-RM role: Reference model with business and infrastructure applications plus interfaces that guide boundaryless designs.
  • Repository contrast: Architecture Repository stores work products and governance records, but does not itself define the boundaryless pattern.
  • TRM and Continuum contrast: Technical Reference Model taxonomizes platform services, while the Continuum organizes reuse, neither focused on information flow.

Why C is correct

TOGAF created the Integrated Information Infrastructure Model specifically to help design systems supporting Boundaryless Information Flow, per the referenced architecture chapter. It provides components and flows architects assemble for seamless sharing. That stated purpose makes C the settled answer.

Why the others are wrong

  • A. Architecture Repository is wrong because it stores artifacts and governance, not the boundaryless design pattern.
  • B. Enterprise Continuum is wrong because it structures reuse from generic to specific, not information flow architecture.
  • D. Technical Reference Model is wrong because it classifies platform services rather than enabling cross-boundary information use.

OG0-093 exam tip

Link Boundaryless directly to triple-I, picturing information flowing across borders, while Repository equals store and TRM equals taxonomy.

2According to TOGAF, which of the following best describes how the Enterprise Continuum is used in organizing and developing an architecture?
  • It is used to coordinate with the other management frameworks in use
  • It is used to describe how an architecture addresses stakeholder concerns
  • It is used to identify and understand business requirements
  • It is used to provide a system for continuous monitoring
  • It is used to structure re-usable architecture and solution assets
Answer: E

The short version

E — Enterprise Continuum structures reusable assets. It organizes architecture and solution artifacts to maximize investment and guide evolution from generic to organization-specific.

Key concepts in this question

  • Continuum purpose: Classification framework spanning Foundation, Common Systems, Industry and Organization architectures.
  • Reuse economics: Storing proven patterns, blocks and solutions reduces duplication and speeds delivery.
  • Stakeholder and requirement contrasts: Views address concerns and business scenarios elicit needs, but neither organizes asset reuse.
  • Monitoring contrast: Ongoing governance tracks compliance, distinct from structuring reusable content.

Why E is correct

TOGAF defines the Continuum as the means to organize reusable architecture and solution assets, increasing return on architecture investment. It positions each artifact along a generic-to-specific spectrum for selection. That reuse-structuring role is exactly the settled E wording.

Why the others are wrong

  • A. Coordinate frameworks is wrong because framework alignment is handled through governance, not the Continuum.
  • B. Describe stakeholder concerns is wrong because views and viewpoints cover concerns, not asset organization.
  • C. Identify requirements is wrong because business scenarios and Phase A techniques capture needs.
  • D. Continuous monitoring is wrong because compliance oversight belongs to governance, not to reuse classification.

OG0-093 exam tip

Hear Continuum and think library shelves from generic to specific, so structure reusable assets is the instant pick for organizing stems.

3Complete the sentence. TOGAF defines five criteria for a good set of principles: Understandable, Robust, Complete, Consistent and_____.
  • Agile
  • Dynamic
  • Comprehensive
  • Rational
  • Stable
Answer: E

The short version

E — Stable completes the five principle qualities. TOGAF requires principles to be Understandable, Robust, Complete, Consistent and Stable so guidance endures yet adapts.

Key concepts in this question

  • Architecture principles: Durable rules and guidelines shaping decisions across business, data, application and technology domains.
  • First four qualities: Clarity for comprehension, robustness for decision quality, completeness for coverage, and consistency for coherence.
  • Stable meaning: Enduring over time while allowing controlled accommodation of change, avoiding churn from every project.
  • Distractor traits: Agile, dynamic, comprehensive and rational sound appealing but are not the TOGAF list term.

Why E is correct

The standard chapter on principle qualities lists Stable as the fifth criterion, defined as enduring yet able to accommodate change. This balances longevity with flexibility. Because memorization of the five-word set is directly tested, E is the settled completion.

Why the others are wrong

  • A. Agile is wrong because adaptability is covered by Stable with governance, not by standalone agility wording.
  • B. Dynamic is wrong because TOGAF stresses endurance over frequent change for principles.
  • C. Comprehensive is wrong because coverage is already expressed by Complete in the set.
  • D. Rational is wrong because reasoning quality is part of Robust, not a separate fifth term.

OG0-093 exam tip

Recite URCCS as Understandable Robust Complete Consistent Stable, locking the S-word as Stable whenever the five-criteria stem appears.

4Complete the sentence. According to TOGAF, a ______________is a representation of a system from the perspective of a related set of_____________.
  • view, concerns
  • viewpoint, views
  • view, requirements
  • view, stakeholders
Answer: A

The short version

A — A view represents the system from related concerns. TOGAF defines an architecture view as one or more models seen through the lens of a stakeholder concern set.

Key concepts in this question

  • View definition: Representation addressing a related set of concerns, often visualized with diagrams and catalogs.
  • Concern examples: Performance, security, manageability and usability that motivate what a view must show.
  • Viewpoint contrast: The template or perspective specification used to construct views, not the representation itself.
  • Stakeholder and requirement traps: Stakeholders hold concerns and requirements demand capabilities, but the definition pairs view with concerns.

Why A is correct

The Basic Concepts chapter states an architecture view is a representation from the perspective of a related set of concerns, composed of models. That exact pairing matches A word for word. Because the stem quotes the definition, A is the settled answer.

Why the others are wrong

  • B. Viewpoint and views is wrong because it reverses the relationship, viewpoints define conventions for creating views.
  • C. View and requirements is wrong because requirements are addressed by architecture, not the definitional counterpart of view.
  • D. View and stakeholders is wrong because stakeholders own concerns, while concerns are the lens named in the definition.

OG0-093 exam tip

Memorize view-concerns and viewpoint-conventions as a pair, so representation plus related set immediately resolves to view plus concerns.

5Which of the following best describes the Standards Information Base?
  • A repository area holding a description of the organization specific architecture framework and method
  • A repository area holding a record of the governance activity across the enterprise
  • A repository area holding guidelines and templates used to create new architectures
  • A repository area holding processes to support governance of the Architecture Repository
  • A repository area holding specifications to which architectures must conform
Answer: E

The short version

E — Standards Information Base holds conformance specifications. It is the Repository area for standards architectures must meet, ensuring interoperability and compliance.

Key concepts in this question

  • SIB content: Selected norms, product standards and service specifications governing implementation choices.
  • Repository partitioning: Separates method, governance records, templates and standards for clear stewardship.
  • Framework and template contrasts: Method areas describe the process and templates aid creation, neither mandating conformance.
  • Governance records contrast: Logs activity and decisions, while SIB prescribes what solutions must follow.

Why E is correct

TOGAF states the Standards Information Base provides a repository area to hold specifications to which architectures must conform. Projects consult it to select compliant building blocks. That conformance-repository role makes E the settled description.

Why the others are wrong

  • A. Framework and method area is wrong because it describes the architecture approach itself, not mandatory specifications.
  • B. Governance activity record is wrong because it tracks decisions and compliance events rather than holding standards.
  • C. Guidelines and templates area is wrong because it helps create architectures but does not impose conformance.
  • D. Governance support processes are wrong because they describe repository management, not the standards content.

OG0-093 exam tip

Link SIB S to Specifications, so repository holding specifications to which architectures must conform is your cue for that option.

6Which of the following best describes the purpose of the Gap Analysis technique?
  • To determine service levels for the architecture
  • To establish quality metrics for the architecture
  • To identify commercial building blocks to be purchased
  • To identify missing functions
  • To validate nonfunctional requirements
Answer: D

The short version

D — Gap Analysis finds missing functions. It compares Baseline and Target architectures to expose overlooked capabilities, then plans work to close them.

Key concepts in this question

  • Gap technique: Matrix mapping of current versus desired building blocks to highlight eliminations, retentions and new needs.
  • Validation role: Ensures essential information processing needs and stakeholder concerns are not forgotten.
  • Service and metric contrasts: Service levels and quality metrics refine success criteria but do not reveal absent functions.
  • Procurement and NFR contrasts: Buying blocks and validating nonfunctionals follow after gaps are known.

Why D is correct

TOGAF introduces Gap Analysis as the step that asks what was forgotten, focusing on missing stakeholder coverage and processing needs. Identified gaps become work packages in the Roadmap. That forgotten-function hunt is exactly the settled D purpose.

Why the others are wrong

  • A. Determine service levels is wrong because levels are defined in requirements and contracts, not by gap mapping.
  • B. Establish quality metrics is wrong because metrics measure success rather than uncover absent capabilities.
  • C. Identify purchasable blocks is wrong because sourcing follows gap identification, it does not define the technique.
  • E. Validate nonfunctionals is wrong because that assurance activity is broader than gap-specific function discovery.

OG0-093 exam tip

Picture Baseline versus Target with holes in between, so any forgotten or missing function stem means Gap Analysis.

7Which of the following describes how the Enterprise Continuum is used when developing an Enterprise Architecture?
  • To describe how an architecture addresses stakeholder concerns
  • To identify and understand business requirements
  • To classify architecture and solution assets
  • To coordinate with the other management frameworks in use
Answer: C

The short version

C — Continuum classifies architecture and solution assets. It provides methods to categorize artifacts as they evolve from generic foundations to organization-specific designs.

Key concepts in this question

  • Classification spectrum: Foundation through Common Systems and Industry to Organization-Specific architectures and solutions.
  • Artifact governance: Placing items on the spectrum clarifies reuse potential and ownership.
  • Concern and requirement contrasts: Views show how concerns are addressed and scenarios surface needs, separate from classification.
  • Framework coordination: Cross-framework alignment is governance work, not the Continuum method.

Why C is correct

The Enterprise Continuum chapter defines methods for classifying internal and external artifacts along the evolution path. That taxonomy guides architects to reuse before building anew. Because the stem asks how the Continuum is used in development, classify assets is the settled answer.

Why the others are wrong

  • A. Describe stakeholder concerns is wrong because that is the role of views constructed from viewpoints.
  • B. Identify business requirements is wrong because business scenarios and Phase A elicit requirements.
  • D. Coordinate frameworks is wrong because management-framework alignment sits outside Continuum classification.

OG0-093 exam tip

Use Continuum equals classify and reuse, reserving address-concerns for views and understand-requirements for business scenarios.

8Complete the sentence by selecting the applicable pair of words. A/an _____is used in Phase A to help identify and understand business _____that the architecture has to address.
  • activity model, perspective
  • business scenario, requirements
  • use case, interconnections
  • architecture view, concerns
  • business transformation readiness assessment, constraints
Answer: B

The short version

B — Business scenario plus requirements fits Phase A discovery. Phase A uses scenarios to surface business needs and shape an Architecture Vision that responds to them.

Key concepts in this question

  • Phase A aim: Secure commitment through a Vision that links strategy, stakeholders and value.
  • Business scenarios: Narrative technique describing actors, roles and outcomes to expose requirements.
  • Activity and use-case contrasts: Models detail processes or interactions, but TOGAF names scenarios for Vision-level discovery.
  • View and readiness contrasts: Views communicate concerns and readiness assesses change capacity, neither the paired Phase A discovery tool.

Why B is correct

TOGAF steps for Develop Architecture Vision cite business scenarios as the appropriate technique to discover and document business requirements. The scenario outputs directly inform Vision scope. That named pairing makes business scenario plus requirements the settled completion.

Why the others are wrong

  • A. Activity model and perspective is wrong because models elaborate processes later rather than framing Vision requirements.
  • C. Use case and interconnections is wrong because use cases detail interactions, not the Vision discovery pairing.
  • D. Architecture view and concerns is wrong because views communicate a design, they do not elicit initial business needs.
  • E. Readiness assessment and constraints is wrong because that tool gauges transformation risk, not requirement discovery.

OG0-093 exam tip

Anchor Phase A to business scenarios for requirements, saving views for communication and readiness for transformation risk.

9According to TOGAF, which of the following best describes the purpose of an Architecture Roadmap?
  • To act as a deliverable container for artifacts created during a project
  • To ensure that architecture information is communicated to the right stakeholders at the right time
  • To govern the architecture throughout its implementation process
  • To provide a high-level view of the end architecture product
  • To show progression of change from the Baseline Architecture to the Target Architecture
Answer: E

The short version

E — Roadmap shows progression from Baseline to Target. It lays work packages on a timeline with business value and Transition Architectures as intermediate steps.

Key concepts in this question

  • Roadmap content: Sequenced packages, dependencies, value at each stage and transition states toward the Target.
  • Phasing: Incrementally built in Phases E and F, informed by earlier gaps and migration planning.
  • Container and communication contrasts: Catalogs hold artifacts and communication plans target stakeholders, neither timeline progression.
  • Governance and end-state contrasts: Implementation governance oversees delivery and architecture definition depicts the end, not the journey.

Why E is correct

The deliverable description defines the Roadmap purpose as showing progression from Baseline to Target over time, highlighting value per stage. Transition Architectures mark viable plateaus. That timeline-of-change definition matches E exactly as settled.

Why the others are wrong

  • A. Deliverable container is wrong because containers group artifacts rather than sequence change over time.
  • B. Communication timing is wrong because stakeholder messaging is a communication plan function.
  • C. Govern implementation is wrong because governance enforces compliance during delivery.
  • D. High-level end view is wrong because that depicts Target state, not staged progression.

OG0-093 exam tip

See Roadmap and picture a dated path with Baseline left and Target right, choosing progression wording every time.

10Which of the following does the TOGAF standard describe as an Architecture Pattern?
  • An implementation specific solution building block
  • A work product describing an aspect of an architecture
  • A detailed description of the interfaces between building blocks
  • A package of functionality defined to meet the business needs of the organization.
  • A way to identify combinations of building blocks that have been proven to deliver solutions
Answer: E

The short version

E — An Architecture Pattern identifies proven block combinations. TOGAF describes patterns as reusable mixes of building blocks known to deliver effective solutions.

Key concepts in this question

  • Pattern value: Captures experience so architects start from proven arrangements rather than novel composition.
  • ABB and SBB mix: Combines abstract capabilities with concrete products that previously succeeded together.
  • Building block contrast: Single functionality packages meet business needs but lack the combinatorial guidance of patterns.
  • Artifact and interface contrasts: Work products describe aspects and interface specs detail connections, not proven combos.

Why E is correct

The introduction to patterns promises help identifying Architecture and Solution Building Block combinations proven effective in the past for future use. That promise is the settled definition behind E. Patterns thus accelerate confident design.

Why the others are wrong

  • A. Implementation-specific block is wrong because that describes a Solution Building Block, not a pattern across blocks.
  • B. Work product aspect is wrong because that is an artifact, which records rather than recommends combinations.
  • C. Interface detail is wrong because interfaces specify connections without asserting proven effectiveness.
  • D. Functionality package is wrong because it defines one capability, not a proven multi-block solution shape.

OG0-093 exam tip

Link pattern to proven combo, so whenever the stem mentions combinations proven to deliver, select that wording without hesitation.

Want the full bank of 554 questions for TOGAF 9 Combined Part 1 and Part 2 Examination (OG0-093)? See all practice exams.