Overview
This unit builds the mental model every other part of the TOGAF Standard assumes. You learn that an enterprise is defined by scope, not by legal entity, why Enterprise Architecture (EA) exists, and the benefits it brings. You also learn why the TOGAF Standard works as a framework, the four architecture domains (Business, Data, Application, Technology), and architecture abstraction from contextual down to physical.
The second half introduces the structures that hold architecture work: the Enterprise Continuum for classifying assets from generic to organization-specific, the Architecture Repository for storing them, the Content Framework and Enterprise Metamodel for describing them consistently, and the Architecture Capability that produces them. Two techniques recur across the method: risk management (initial versus residual risk) and gap analysis (baseline versus target). Unit 3 then puts all of these terms to work inside the ADM phases.
How it's tested
OGEA-101 is a closed-book paper of 40 simple multiple-choice questions, and Concepts questions are mostly recall and recognition: a definition paired with four real TOGAF terms, a 'which of the following is a benefit' list, or 'which is NOT one of the four domains'. The options are written to be plausible, so near-synonyms are the main hazard.
-
Definition match
The stem paraphrases a definition (for example, a view of the repository that classifies assets from generic to specific) and you choose the term. Look for the one distinguishing word, such as 'classify' versus 'store'.
-
Which is NOT
A list question asks which item is not one of the four domains, not a repository area, or not an EA benefit. Distractors are often terms from another TOGAF structure, such as 'Information Systems' or 'Security' offered as a fifth domain.
-
Concept to location
You are told an asset (a reference model, an approved standard, a compliance record) and asked where it belongs: a point on the Enterprise Continuum or an area of the Architecture Repository.
A stem says an organization wants to store the standards that new architectures must comply with, separate from reference models it has bought. Which part of the Architecture Repository holds them? Reference Library is tempting because standards feel like reference material. But reference material that guides is the Reference Library, while mandatory standards sit in the Standards Library. The word 'must comply' is the clue that decides it.
Learning outcomes 12
Official learning outcomes from the The Open Group outline, in outline order.
1.1 Describe what an enterprise isAn enterprise is a scope of interest, not a company boundary.
- What it means
- In the TOGAF Standard an enterprise is the highest level of description of an organization, covering all its missions and functions, and it can span several organizations. A single division, a whole corporation, or a supply-chain partnership can each be the 'enterprise' for a given architecture.
- What to understand
- The definition is scope-based: the enterprise is whatever the architecture effort chooses to treat as a whole. That is why scoping in the Preliminary Phase and Phase A matters, and why an 'extended enterprise' can include partners, suppliers and customers.
- How it shows up
- A stem describes a government department working with outside agencies on a shared service and asks whether this can be treated as one enterprise. It can.
- Common confusion
- Equating 'enterprise' with a single legal entity or with large companies only.
1.2 Explain the purpose of Enterprise ArchitectureEA structures and aligns the enterprise so change can be delivered effectively.
- What it means
- EA describes how the enterprise's business, data, applications and technology fit together, both now and in a desired future state, so that change can be planned and governed. Its purpose is to optimize a fragmented set of processes and systems into an integrated environment that responds to change and supports the business strategy.
- What to understand
- EA is a planning and decision-support discipline, not a documentation exercise or an IT-only design. It works at enterprise scale, gives a single view across silos, and connects strategy to the projects that execute it.
- How it shows up
- Options contrast 'documenting current IT systems' with 'enabling the enterprise to realize its strategy through coordinated change'; the second describes the purpose.
- Common confusion
- Treating EA as solution architecture for one project, or as an IT inventory.
1.3 List the key benefits of having an Enterprise ArchitectureBenefits fall into operations, IT, investment and procurement groups.
- What it means
- The TOGAF Standard groups EA benefits as: more effective and efficient business operations; more effective and efficient digital transformation and IT operations; better return on existing investment with reduced risk for future investment; and faster, simpler, cheaper procurement.
- What to understand
- Each group has concrete examples: lower change-management cost, more agile organization, shared business capabilities, reduced complexity in IT, portability of applications, and procurement decisions made against a coherent plan. Know these as outcomes of having an EA, not of using any specific tool.
- How it shows up
- A 'which is a benefit of EA' question lists one real benefit, such as reduced risk for future investment, among items that are side issues or the opposite.
- Common confusion
- Picking a benefit of a single project (faster delivery of one system) rather than an enterprise-wide benefit.
1.4 Explain why the TOGAF Standard is suitable as a framework for EAA proven, generic, adaptable method plus supporting content.
- What it means
- The TOGAF Standard is an open, vendor-neutral framework built on industry consensus. It provides a tested method (the ADM), a common vocabulary, a content framework and metamodel, and guidance that an organization can tailor rather than invent from scratch.
- What to understand
- Its suitability comes from being generic and adaptable: the 10th Edition separates the stable Fundamental Content from the TOGAF Series Guides, so organizations adopt the core and pick guidance that fits. It is meant to be tailored, not followed literally.
- How it shows up
- A question asks why an organization would adopt TOGAF; the answer centers on a reusable, tailorable method and common language, not on product certification or a mandatory toolset.
- Common confusion
- Believing the TOGAF Standard must be applied in full and without change to be compliant.
1.5 Name the four architecture domainsBusiness, Data, Application and Technology.
- What it means
- The TOGAF Standard supports four architecture domains that together form the overall EA: Business Architecture, Data Architecture, Application Architecture and Technology Architecture. Data and Application are developed together in Phase C as the Information Systems Architectures.
- What to understand
- Business defines strategy, governance, organization and key processes; Data defines logical and physical data assets; Application defines the individual applications and their interactions; Technology defines the software and hardware capabilities that support them. Security and other concerns cut across the domains rather than forming a fifth.
- How it shows up
- A 'which is NOT one of the four domains' question offers 'Security Architecture' or 'Information Systems Architecture' as the distractor.
- Common confusion
- Counting Information Systems Architecture as a separate domain; it is the Phase C umbrella for Data plus Application.
1.6 Describe how architecture abstraction can be used in EAMoving from why, to what, to how, to with-what.
- What it means
- Architecture abstraction separates levels of detail so stakeholders can reason without being swamped. The TOGAF Standard describes contextual (why), conceptual (what), logical (how) and physical (with what) levels.
- What to understand
- Higher abstraction is stable and technology-independent; lower abstraction names concrete products and implementations. This mirrors the move from Architecture Building Blocks to Solution Building Blocks and lets you change an implementation without redesigning the concept.
- How it shows up
- A stem says an architect describes required capabilities without naming any vendor product and asks which abstraction level this is: logical or conceptual, not physical.
- Common confusion
- Assuming 'logical' means 'detailed product design'; product selection belongs to the physical level.
1.7 Describe the Enterprise ContinuumA view of the repository that classifies assets from generic to specific.
- What it means
- The Enterprise Continuum is a way of classifying architecture and solution assets by how generic or specific they are. It runs from Foundation through Common Systems and Industry to Organization-Specific, and has two parts: the Architecture Continuum and the Solutions Continuum.
- What to understand
- Its purpose is reuse and communication: it helps architects find what can be leveraged and explain where a piece of work sits. It is a classification view of the contents of the Architecture Repository, not the store itself.
- How it shows up
- A question describes an industry reference model and asks where it sits on the continuum: Industry, between Common Systems and Organization-Specific.
- Common confusion
- Calling the Enterprise Continuum a repository or a tool; it is a classification view.
1.8 Explain the Architecture RepositoryThe store for all architecture outputs, with defined areas.
- What it means
- The Architecture Repository holds the outputs of architecture work in defined areas, including the Architecture Metamodel, Architecture Capability, Architecture Landscape, Standards Library, Reference Library, Governance Log, Architecture Requirements Repository and Solutions Landscape.
- What to understand
- Each area has one job: the Landscape holds architectural views of building blocks in use or planned; the Standards Library holds standards new work must comply with; the Reference Library holds guidelines, templates and patterns; the Governance Log records compliance decisions and dispensations. Matching an asset to its area is the testable skill.
- How it shows up
- A stem describes a record of an Architecture Board dispensation and asks where it is stored: the Governance Log.
- Common confusion
- Mixing up the Standards Library (mandatory) and the Reference Library (guiding material).
1.9 Explain the TOGAF Content Framework and Enterprise MetamodelA consistent structure for describing architecture outputs.
- What it means
- The Content Framework defines the types of architecture work product: deliverables (formally reviewed and signed off), artifacts (catalogs, matrices and diagrams) and building blocks. The Enterprise Metamodel defines the entities and relationships that artifacts describe, such as actors, roles, business services, data entities and application components.
- What to understand
- Using a common metamodel makes outputs consistent and comparable across projects and enables tooling. A deliverable contains artifacts, and artifacts describe building blocks; keeping that containment straight answers many content questions.
- How it shows up
- A stem asks which type of work product is formally reviewed, agreed and signed off by stakeholders: a deliverable.
- Common confusion
- Treating artifact and deliverable as interchangeable; a deliverable is a contractual output that typically contains artifacts.
1.10 Explain what an Architecture Capability isThe organization's ability to do and sustain EA.
- What it means
- An Architecture Capability is the ability of an organization to develop, use and sustain its Enterprise Architecture: the people, roles, processes, governance, tools and repository that make architecture work possible.
- What to understand
- The capability is established in the Preliminary Phase and maintained over time (Phase H checks it still meets needs). It is operated like any other business capability, with its own principles, governance structure and maturity target.
- How it shows up
- A stem asks which phase defines the organizational model for EA, selects tools and sets up governance processes: the Preliminary Phase, because that is where the Architecture Capability is established.
- Common confusion
- Confusing an Architecture Capability (ability to do EA) with a business capability (what the business can do).
1.11 Explain risk managementIdentify, classify, mitigate and monitor risks to the transformation.
- What it means
- Risk management in the TOGAF Standard identifies and handles risks to an architecture effort. It distinguishes initial risk (before mitigation) from residual risk (after mitigation) and classifies risks by effect and frequency.
- What to understand
- The flow is: classify risks, identify them, assess initial risk, mitigate and assess residual risk, then monitor. Mitigation rarely eliminates risk, so the decision-maker accepts the residual level, not the initial one.
- How it shows up
- A stem describes the level of risk remaining after mitigation actions and asks for its name: residual risk.
- Common confusion
- Assuming mitigation should reduce risk to zero, or reversing initial and residual.
1.12 Explain gap analysisComparing baseline and target to find what changes.
- What it means
- Gap analysis compares the Baseline Architecture with the Target Architecture to identify what must be added, kept or removed. It is typically recorded in a matrix with baseline building blocks on one axis and target building blocks on the other.
- What to understand
- Gaps show up as items that are new in the target (to be developed or procured) or items in the baseline that are absent from the target (deliberately eliminated or accidentally left out). The output feeds candidate roadmap components in Phases B to D and consolidation in Phase E.
- How it shows up
- A stem says a baseline service has no counterpart in the target and asks what this indicates: a gap that must be confirmed as intentional elimination or corrected.
- Common confusion
- Thinking gap analysis only finds missing new items; it also exposes things accidentally dropped.
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
Enterprise
The TOGAF Standard treats an enterprise as the highest-level scope chosen for an architecture, covering its missions and functions, and it may span several organizations.
- Remember
- Scope defines the enterprise, so one division or a multi-company partnership can each be an enterprise.
- Tested as
- Appears as a definition item and underpins scoping questions in the ADM unit.
- Trap
- Choosing an answer that limits an enterprise to one legal company.
-
Four architecture domains
Business, Data, Application and Technology Architecture together make up the overall Enterprise Architecture in the TOGAF Standard.
- Remember
- Data and Application are developed together in Phase C as the Information Systems Architectures, and Technology is Phase D.
- Tested as
- Classic 'which is NOT a domain' question.
- Trap
- Accepting Security or Information Systems as a fifth domain.
-
Enterprise Continuum
A classification view of architecture and solution assets that runs from Foundation through Common Systems and Industry to Organization-Specific.
- Remember
- It has two halves, the Architecture Continuum and the Solutions Continuum, and it classifies rather than stores.
- Tested as
- Placing a reference model or solution on the continuum is a frequent recall item.
- Trap
- Describing it as the repository itself.
-
Architecture Repository
The store for architecture outputs, organized into areas such as the Architecture Landscape, Standards Library, Reference Library and Governance Log.
- Remember
- Standards Library is what new work must comply with; Reference Library holds templates, patterns and guidelines that help.
- Tested as
- Asset-to-area matching questions.
- Trap
- Putting dispensations or compliance records anywhere other than the Governance Log.
-
Architecture Landscape
The repository area holding architectural representations of building blocks in use or planned, at three levels: Strategic, Segment and Capability Architecture.
- Remember
- Strategic is the broadest and longest-horizon view; Capability Architecture is the most detailed.
- Tested as
- Links Concepts to Unit 5, which asks you to list the three levels.
- Trap
- Listing the Enterprise Continuum levels (Foundation, Common Systems and so on) instead.
-
Deliverable, artifact, building block
A deliverable is a contractually specified, formally reviewed output; an artifact is a catalog, matrix or diagram describing part of the architecture; a building block is a reusable component of capability.
- Remember
- Deliverables contain artifacts, and artifacts describe building blocks.
- Tested as
- Content Framework definition questions.
- Trap
- Calling a single diagram a deliverable.
-
Architecture Capability
The organization's ability to develop, use and sustain EA, including people, processes, governance, tools and the repository.
- Remember
- Established in the Preliminary Phase and kept fit for purpose through Phase H.
- Tested as
- Phase-purpose questions often hinge on this term.
- Trap
- Confusing it with a business capability.
-
Architecture abstraction
Describing architecture at contextual (why), conceptual (what), logical (how) and physical (with what) levels.
- Remember
- Vendor products appear only at the physical level.
- Tested as
- Recognition of which level a description belongs to.
- Trap
- Treating logical design as product selection.
-
Initial vs. residual risk
Initial risk is assessed before any mitigation; residual risk is what remains after mitigation actions are applied.
- Remember
- Sponsors accept residual risk; mitigation seldom drives it to zero.
- Tested as
- Simple definition question that also reappears in Unit 4.
- Trap
- Reversing the two terms.
-
Gap analysis matrix
A matrix of baseline building blocks against target building blocks, with extra 'new' and 'eliminated' entries, that exposes what must change.
- Remember
- A baseline item missing from the target must be checked: deliberate elimination or accidental omission.
- Tested as
- Recall in Concepts and purpose questions in Unit 4.
- Trap
- Assuming gap analysis only lists new items to build.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
Enterprise Continuum vs. Architecture Repository
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Enterprise Continuum | A classification view of assets from generic (Foundation) to specific (Organization-Specific) | Organizes and positions assets to support reuse and communication | Called 'the place where architecture is stored' |
| Architecture Repository | The actual store of architecture outputs, divided into areas | Holds content; the continuum is one way of viewing that content | Confusing its areas (Landscape, Standards Library) with continuum levels |
Architecture Continuum vs. Solutions Continuum
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Architecture Continuum | Classifies architecture descriptions and models, from Foundation to Organization-Specific Architectures | Describes what is required (architecture) | Thinking it contains implemented products |
| Solutions Continuum | Classifies solutions that implement those architectures, from Foundation to Organization-Specific Solutions | Describes how requirements are realized (solutions) | Assuming it is a separate repository rather than the matching half of the Enterprise Continuum |
Standards Library vs. Reference Library vs. Governance Log
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Standards Library | Standards with which new architectures must comply | Mandatory | Storing optional templates here |
| Reference Library | Guidelines, templates, patterns and reference models | Helpful material for reuse, not compliance rules | Assuming everything in it is mandatory |
| Governance Log | Record of governance activity: decisions, compliance assessments, dispensations | Evidence of governance, not design content | Filing compliance results in the Architecture Landscape |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Continuum equals repository
- What candidates pick
- The Enterprise Continuum as the answer to 'where are architecture outputs stored'.
- Why it looks right
- Both terms describe all architecture assets and appear side by side in study material.
- Why it's wrong
- The Enterprise Continuum classifies assets by how generic they are; the Architecture Repository is where they are held.
Clue to watch for Verbs such as 'store', 'hold' or 'record' point to the repository; 'classify', 'position' or 'generic to specific' point to the continuum.
-
A fifth domain
- What candidates pick
- Information Systems Architecture listed as a separate domain alongside Data and Application.
- Why it looks right
- Phase C is titled Information Systems Architectures, so the phrase feels official.
- Why it's wrong
- Information Systems is the Phase C umbrella for two of the four domains, not a domain of its own.
Clue to watch for Count the domains: if the option set implies five, one of them is an umbrella or a cross-cutting concern.
-
Standards in the Reference Library
- What candidates pick
- Reference Library as the home for standards new architectures must follow.
- Why it looks right
- Standards are reference documents in everyday speech.
- Why it's wrong
- Mandatory standards belong in the Standards Library; the Reference Library holds guidance and patterns.
Clue to watch for Words such as 'must comply' or 'mandatory' indicate the Standards Library.
-
Zero residual risk
- What candidates pick
- An answer saying mitigation should continue until no risk remains.
- Why it looks right
- Eliminating risk sounds responsible.
- Why it's wrong
- TOGAF expects a residual level of risk after mitigation, which is then accepted and monitored.
Clue to watch for 'After mitigation' or 'remaining' signals residual risk that is accepted, not removed.
-
Benefits of a project, not of EA
- What candidates pick
- 'Faster delivery of a specific system' as the EA benefit.
- Why it looks right
- It is a real benefit that projects often claim.
- Why it's wrong
- EA benefits are enterprise-wide: efficient operations, better return on investment, reduced future investment risk, simpler procurement.
Clue to watch for If an option is about one project or one system, it is unlikely to be the EA benefit the question wants.
-
Products at the logical level
- What candidates pick
- Logical architecture as the level where specific vendor products are named.
- Why it looks right
- 'Logical' sounds like the detailed design step.
- Why it's wrong
- Product and vendor choices belong to the physical (with what) level; logical describes how, independent of products.
Clue to watch for Any named product or vendor places the description at the physical level.
Answer framework
Use this sequence when a Concepts question offers four genuine TOGAF terms and you must pick the one that fits.
- Underline the verb in the stem, such as classify, store, describe or comply, because each points to a different structure.
- Decide whether the stem is about a scope (enterprise, domain), a structure (continuum, repository, metamodel) or a technique (risk, gap analysis).
- Match the asset to its home: reference models to the continuum, mandatory standards to the Standards Library, decisions and dispensations to the Governance Log.
- Check the level of detail, using contextual, conceptual, logical or physical, and generic versus organization-specific.
- Eliminate options that are real terms from a different structure, then choose the one whose definition fits every word of the stem.
Practice question
Want more like this? The TOGAF EA Foundation practice test has questions for every domain.
Checklist
0 of 12
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
Start with the scope terms: enterprise, Enterprise Architecture, its benefits and the four domains. They are the quickest marks and they give you the frame for the rest of the syllabus. Then learn the structures as a set, because the exam tests them against each other: the Enterprise Continuum (classify), the Architecture Repository (store), the Content Framework and Enterprise Metamodel (describe), and the Architecture Capability (produce and sustain).
The areas most often underestimated are the repository areas and the continuum points. Draw the repository as a box with its areas labelled and add one sample item to each, such as a dispensation in the Governance Log and a pattern in the Reference Library. Draw the continuum as an arrow from Foundation to Organization-Specific, with the Architecture Continuum above and the Solutions Continuum below.
Risk management and gap analysis are briefly introduced here and covered again in Unit 4, so learn the definitions now (initial versus residual risk, baseline versus target) and leave their use in the ADM for later.
Afterwards, drill short definition-matching questions under time pressure. Forty questions in sixty minutes leaves about ninety seconds each, and Concepts items should take far less, which banks time for the ADM unit.
FAQ
How many Concepts questions are on the TOGAF EA Foundation exam?
The Open Group's OGEA-101 exam plan allocates 8 of the 40 questions to Concepts, which is 20% of the paper and the second-largest unit after Introduction to the ADM.
Are the 21 TOGAF definitions tested separately?
No. Definitions are a separate learning unit in the conformance requirements, but the exam plan has no Definitions allocation; terms such as Transition Architecture or Work Package are examined through the units that use them.
What is the difference between the Enterprise Continuum and the Architecture Repository?
The repository stores architecture outputs in defined areas. The continuum is a way of classifying those outputs from generic Foundation assets to Organization-Specific ones, to support reuse.
Is Security Architecture one of the TOGAF domains?
No. The four domains are Business, Data, Application and Technology. Security is treated as a concern that runs across all of them.
How hard are Concepts questions?
They are mostly recall and recognition, so they are short. The difficulty is that every option is usually a genuine TOGAF term, so you need exact definitions rather than a general feel.
How long should I spend on Concepts?
As a planning estimate, about 7 to 9 hours of a 40-hour study plan, mostly on the repository areas, the continuum and the domain definitions.
How does this unit connect to the ADM phases?
The ADM uses these structures throughout: the Preliminary Phase establishes the Architecture Capability, Phases B to D perform gap analysis per domain, and every phase reads from and writes to the Architecture Repository.
Other Enterprise Architecture & IT Governance certifications
Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.
Test your Domain 1 knowledge
You have just worked through the TOGAF vocabulary that the other units rely on, from the four domains to the repository areas. Check that you can match each term to its definition under exam timing.
Keep going
- Training Training Built on your Weak areas
- Practice test Questions by domain, with explanations
- Mock exam Full length, timed like the real exam
- Readiness test Find your weakest domain in minutes
- Cheat sheet Key terms and formulas on one page
- Ask the TOGAF EA Foundation AI tutor Get any concept explained your way