Advanced
Enterprise Architecture
#TOGAF
#ADM
#framework
TOGAF Vocabulary
5 exercises — practice the vocabulary for TOGAF ADM phases, architecture building blocks, the architecture repository, and framework communication.
0 / 26 completed
1 / 26
An enterprise architect says: "We're in Phase B of the ADM."
What does Phase B cover in TOGAF?
What does Phase B cover in TOGAF?
Phase B — Business Architecture focuses on defining the target business architecture: processes, capabilities, organisational structures, and business goals. It follows Phase A (Architecture Vision) and precedes Phase C (Information Systems Architecture). The output of Phase B is a Business Architecture document showing the current (baseline) and target business states and gap analysis. Getting Phase B right is critical — it drives everything downstream.
2 / 26
What is the TOGAF ADM?
The Architecture Development Method (ADM) is the core of TOGAF — an iterative process for creating and managing enterprise architecture. The cycle begins with Preliminary phase (governance setup), then A (Vision) → B (Business) → C (Information Systems) → D (Technology) → E (Opportunities & Solutions) → F (Migration Planning) → G (Implementation Governance) → H (Architecture Change Management), then back to A. "Iterative" is key — organisations repeat the cycle as the business evolves.
3 / 26
Complete the sentence from an architecture review meeting:
"Before selecting Kafka as our event broker, we defined it as an Architecture _____ Block — a reusable, technology-neutral capability that any solution could fulfil."
"Before selecting Kafka as our event broker, we defined it as an Architecture _____ Block — a reusable, technology-neutral capability that any solution could fulfil."
An Architecture Building Block (ABB) defines a capability at a technology-independent level — for example, "Asynchronous Messaging Service" rather than "Kafka." When a specific product is chosen (Kafka), it becomes a Solution Building Block (SBB). ABBs promote reuse across architecture engagements: the same ABB can be satisfied by different SBBs in different contexts. This separation of "what" from "how" is fundamental to TOGAF's approach.
4 / 26
A TOGAF practitioner refers to the Architecture Repository. What does it contain?
The TOGAF Architecture Repository is the single source of truth for enterprise architecture assets. It includes: the Architecture Metamodel (how artefacts relate), the Architecture Landscape (current, transition, and target), the Standards Information Base (approved standards and patterns), the Reference Library (model architectures and examples), and the Governance Log (decisions and waivers). It enables reuse and prevents architectural drift across business units.
5 / 26
Which sentence correctly uses TOGAF vocabulary in a stakeholder presentation?
Option B correctly uses TOGAF vocabulary in sequence and context: Phase A (Architecture Vision) produces stakeholder alignment; Phase B develops the Business Architecture. The language "target business architecture" and "capability gap analysis" are correct outputs for Phase B. Option A incorrectly equates TOGAF with waterfall project planning. Option C misattributes CISO requirements to Phase D (which covers Technology Architecture, not security governance).
6 / 26
During a code review of the new microservice API, Sarah (the backend engineer) mentions using 'patterns' as part of the architecture. David (the senior architect) responds: "That's great, Sarah! We've been leveraging architectural patterns like Domain-Driven Design and CQRS to ensure loose coupling and scalability. Are you considering incorporating any specific patterns into this design?"
In TOGAF, 'patterns' represent reusable solutions to recurring architectural challenges. They're documented in Architectural Blueprints and form a core component of the ADM (Architecture Development Method). Using 'patterns' in this way reflects a deeper understanding of architectural principles beyond just code design patterns – it highlights the use of proven approaches for overall system structure and behavior. Option A is incorrect because TOGAF's 'patterns' are broader than just code design patterns.
7 / 26
Option A: A high-level business goal defined in the Enterprise Architecture Roadmap. Option B: A reusable, technology-neutral component of an architecture that can be deployed across multiple environments. Option C: A detailed technical specification for a specific software module. Option D: A formal document outlining the organization's strategic IT investments.
Mark is using the term 'Building Block' correctly as defined in TOGAF. Building Blocks are reusable components that represent technology-neutral capabilities – they aren't specific implementations but rather abstract descriptions of what a system needs to do. This contrasts with a business goal or strategic investment which are higher-level concepts. Option C is incorrect because it describes a technical specification, and Option D is too broad.
8 / 26
During a code review of the new user authentication service, Alex (the frontend engineer) asks Ben (the backend architect), "We're using the TOGAF concept of 'Architectural Views' to ensure we're meeting the business requirements at each layer. Can you elaborate on how these views relate to our API design?"
The TOGAF framework utilizes Architectural Views to provide different perspectives on an architecture. These include Business, Functional, Logical, and Physical views – each tailored to a specific audience and level of detail. The question highlights the importance of aligning API design with business requirements through these diverse viewpoints, correcting the misconception that views are solely focused on technical implementation or strategic goals.
9 / 26
During a sprint planning meeting for a new e-commerce platform, Liam (the product owner) asks the architecture team, "How do we ensure our services align with the overall business capabilities?" David (the senior architect) responds, "We're using TOGAF's concept of 'Architectural Domains' to organize these capabilities – they represent broad areas like Order Management and Customer Data. Each domain has specific deliverables and associated patterns that guide development. Are we focusing on the right domains for this new platform?"
The correct answer highlights the core function of TOGAF's Architectural Domains – they represent broad areas of business or IT responsibility. The other options misinterpret the domains as solely language selection, technical specifications, or simple document templates. Understanding Domains is crucial for aligning IT with business strategy, a key principle of enterprise architecture.
10 / 26
During a code review of the new microservice API, Sarah (the backend engineer) mentions using 'patterns' as part of the architecture. David (the senior architect) responds: "That's great, Sarah! We've been leveraging architectural patterns like Domain-Driven Design and CQRS to ensure loose coupling and scalability. Are you considering incorporating any specific patterns into this design?"
In TOGAF, 'patterns' represent reusable solutions to recurring architectural challenges. They're documented in Architectural Blueprints and form a core component of the ADM (Architecture Development Method). Using 'patterns' in this way reflects a deeper understanding of architectural principles beyond just code design patterns – it highlights the use of proven approaches for overall system structure and behavior. Option A is incorrect because TOGAF's 'patterns' are broader than just code design patterns.
11 / 26
Option A: A high-level business goal defined in the Enterprise Architecture Roadmap. Option B: A reusable, technology-neutral component of an architecture that can be deployed across multiple environments. Option C: A detailed technical specification for a specific software module. Option D: A formal document outlining the organization's strategic IT investments.
Mark is using the term 'Building Block' correctly as defined in TOGAF. Building Blocks are reusable components that represent technology-neutral capabilities – they aren't specific implementations but rather abstract descriptions of what a system needs to do. This contrasts with a business goal or strategic investment which are higher-level concepts. Option C is incorrect because it describes a technical specification, and Option D is too broad.
12 / 26
During a code review of the new user authentication service, Alex (the frontend engineer) asks Ben (the backend architect), "We're using the TOGAF concept of 'Architectural Views' to ensure we're meeting the business requirements at each layer. Can you elaborate on how these views relate to our API design?"
The TOGAF framework utilizes Architectural Views to provide different perspectives on an architecture. These include Business, Functional, Logical, and Physical views – each tailored to a specific audience and level of detail. The question highlights the importance of aligning API design with business requirements through these diverse viewpoints, correcting the misconception that views are solely focused on technical implementation or strategic goals.
13 / 26
During a sprint planning meeting for a new e-commerce platform, Liam (the product owner) asks the architecture team, "How do we ensure our services align with the overall business capabilities?" David (the senior architect) responds, "We're using TOGAF's concept of 'Architectural Domains' to organize these capabilities – they represent broad areas like Order Management and Customer Data. Each domain has specific deliverables and associated patterns that guide development. Are we focusing on the right domains for this new platform?"
The correct answer highlights the core function of TOGAF's Architectural Domains – they represent broad areas of business or IT responsibility. The other options misinterpret the domains as solely language selection, technical specifications, or simple document templates. Understanding Domains is crucial for aligning IT with business strategy, a key principle of enterprise architecture.
14 / 26
During a code review of the new microservice API, Sarah (the backend engineer) mentions using 'patterns' as part of the architecture. David (the senior architect) responds: "That's great, Sarah! We've been leveraging architectural patterns like Domain-Driven Design and CQRS to ensure loose coupling and scalability. Are you considering incorporating any specific patterns into this design?"
In TOGAF, 'patterns' represent reusable solutions to recurring architectural challenges. They're documented in Architectural Blueprints and form a core component of the ADM (Architecture Development Method). Using 'patterns' in this way reflects a deeper understanding of architectural principles beyond just code design patterns – it highlights the use of proven approaches for overall system structure and behavior. Option A is incorrect because TOGAF's 'patterns' are broader than just code design patterns.
15 / 26
Option A: A high-level business goal defined in the Enterprise Architecture Roadmap. Option B: A reusable, technology-neutral component of an architecture that can be deployed across multiple environments. Option C: A detailed technical specification for a specific software module. Option D: A formal document outlining the organization's strategic IT investments.
Mark is using the term 'Building Block' correctly as defined in TOGAF. Building Blocks are reusable components that represent technology-neutral capabilities – they aren't specific implementations but rather abstract descriptions of what a system needs to do. This contrasts with a business goal or strategic investment which are higher-level concepts. Option C is incorrect because it describes a technical specification, and Option D is too broad.
16 / 26
During a code review of the new user authentication service, Alex (the frontend engineer) asks Ben (the backend architect), "We're using the TOGAF concept of 'Architectural Views' to ensure we're meeting the business requirements at each layer. Can you elaborate on how these views relate to our API design?"
The TOGAF framework utilizes Architectural Views to provide different perspectives on an architecture. These include Business, Functional, Logical, and Physical views – each tailored to a specific audience and level of detail. The question highlights the importance of aligning API design with business requirements through these diverse viewpoints, correcting the misconception that views are solely focused on technical implementation or strategic goals.
17 / 26
During a sprint planning meeting for a new e-commerce platform, Liam (the product owner) asks the architecture team, "How do we ensure our services align with the overall business capabilities?" David (the senior architect) responds, "We're using TOGAF's concept of 'Architectural Domains' to organize these capabilities – they represent broad areas like Order Management and Customer Data. Each domain has specific deliverables and associated patterns that guide development. Are we focusing on the right domains for this new platform?"
The correct answer highlights the core function of TOGAF's Architectural Domains – they represent broad areas of business or IT responsibility. The other options misinterpret the domains as solely language selection, technical specifications, or simple document templates. Understanding Domains is crucial for aligning IT with business strategy, a key principle of enterprise architecture.
18 / 26
During a code review of the new microservice API, Sarah (the backend engineer) mentions using 'patterns' as part of the architecture. David (the senior architect) responds: "That's great, Sarah! We've been leveraging architectural patterns like Domain-Driven Design and CQRS to ensure loose coupling and scalability. Are you considering incorporating any specific patterns into this design?"
In TOGAF, 'patterns' represent reusable solutions to recurring architectural challenges. They're documented in Architectural Blueprints and form a core component of the ADM (Architecture Development Method). Using 'patterns' in this way reflects a deeper understanding of architectural principles beyond just code design patterns – it highlights the use of proven approaches for overall system structure and behavior. Option A is incorrect because TOGAF's 'patterns' are broader than just code design patterns.
19 / 26
Option A: A high-level business goal defined in the Enterprise Architecture Roadmap. Option B: A reusable, technology-neutral component of an architecture that can be deployed across multiple environments. Option C: A detailed technical specification for a specific software module. Option D: A formal document outlining the organization's strategic IT investments.
Mark is using the term 'Building Block' correctly as defined in TOGAF. Building Blocks are reusable components that represent technology-neutral capabilities – they aren't specific implementations but rather abstract descriptions of what a system needs to do. This contrasts with a business goal or strategic investment which are higher-level concepts. Option C is incorrect because it describes a technical specification, and Option D is too broad.
20 / 26
During a code review of the new user authentication service, Alex (the frontend engineer) asks Ben (the backend architect), "We're using the TOGAF concept of 'Architectural Views' to ensure we're meeting the business requirements at each layer. Can you elaborate on how these views relate to our API design?"
The TOGAF framework utilizes Architectural Views to provide different perspectives on an architecture. These include Business, Functional, Logical, and Physical views – each tailored to a specific audience and level of detail. The question highlights the importance of aligning API design with business requirements through these diverse viewpoints, correcting the misconception that views are solely focused on technical implementation or strategic goals.
21 / 26
During a sprint planning meeting for a new e-commerce platform, Liam (the product owner) asks the architecture team, "How do we ensure our services align with the overall business capabilities?" David (the senior architect) responds, "We're using TOGAF's concept of 'Architectural Domains' to organize these capabilities – they represent broad areas like Order Management and Customer Data. Each domain has specific deliverables and associated patterns that guide development. Are we focusing on the right domains for this new platform?"
The correct answer highlights the core function of TOGAF's Architectural Domains – they represent broad areas of business or IT responsibility. The other options misinterpret the domains as solely language selection, technical specifications, or simple document templates. Understanding Domains is crucial for aligning IT with business strategy, a key principle of enterprise architecture.
22 / 26
During a Slack discussion about refactoring the payment processing microservice, Emily (the lead developer) writes: 'We're documenting the architecture using 'Architectural Views' to ensure alignment with the business requirements. Specifically, we've created a view focused on the user journey and another highlighting key data flows.' Which of the following best describes the purpose of this approach?
Architectural Views are designed for communication and alignment. They provide a simplified representation of the architecture focused on specific perspectives – in this case, the user journey and data flows. This contrasts with technical specifications which detail implementation; rigid enforcement is not the goal; and automated documentation is a secondary benefit.
23 / 26
In a PR review comment for a new API endpoint, David (the backend engineer) says: 'We're using TOGAF 'Building Blocks' to ensure our services are modular and reusable. By defining these blocks upfront, we can accelerate development and reduce redundancy.' What is the primary benefit of applying Building Blocks in this scenario?
TOGAF Building Blocks are about modularity and reusability. Using them allows services to be developed and deployed independently – crucial in microservice architectures – without causing unintended dependencies or requiring constant redesign. It's not about enforcing a tech stack or eliminating design work.
24 / 26
During a standup meeting, John (the project manager) asks the architecture team: 'We need to ensure our new feature aligns with the overall business capabilities outlined in the TOGAF Architecture Development Method. How can we best demonstrate this alignment?' Which of the following is the MOST appropriate response?
The key to aligning with business capabilities is to visualize that connection. A Capability Map directly maps features to their corresponding business capabilities, allowing stakeholders to quickly understand how the work supports strategic goals. The other options are important but don't specifically address alignment to business capability.
25 / 26
Sarah (the frontend developer) is discussing the architectural design for a new web application with Ben (the backend architect). She mentions 'patterns' as part of their approach. What does Sarah likely mean in this context?
Architectural patterns are established solutions for recurring design challenges – things like microservice communication or data access. Using them promotes efficiency and reduces the risk of reinventing the wheel. The other options describe different aspects of software development but don't relate to TOGAF vocabulary.
26 / 26
During a code review, Maria (the security engineer) asks Carlos (the architect): 'How are we ensuring that our system adheres to the TOGAF 'Stakeholder Management' principles?' What is the primary goal of this principle?
Stakeholder Management in TOGAF emphasizes proactive engagement. It's about identifying *who* is affected by the architecture (users, operations, management, etc.) and incorporating their needs into the design process – this ensures a more robust and successful outcome.
Frequently Asked Questions
What does the "TOGAF Vocabulary — Enterprise Architecture English Exercise" exercise cover?
Practice English vocabulary for TOGAF: ADM phases, Architecture Building Blocks, the Architecture Repository, and enterprise architecture framework language. 5 exercises.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall.
How many questions are in "TOGAF Vocabulary — Enterprise Architecture English Exercise"?
This exercise has 26 questions. Each one gives instant feedback with an explanation, so you can see exactly why an answer is right or wrong.
Do I need to create an account to save my progress?
No account is required. The progress bar and score are tracked in your browser for the current session -- the exercise is designed to be a quick, repeatable drill rather than something you resume later.
What happens if I get an answer wrong?
You'll see the correct answer highlighted immediately, along with a short explanation of why it's correct. Wrong answers aren't penalized beyond your score, and you can keep going through every question.
How is this exercise different from reading an article?
Articles explain vocabulary and concepts through prose, while exercises like this one are interactive drills -- multiple-choice questions -- that test and reinforce your recall of specific terms and phrasing.
Can I retry this exercise?
Yes -- use the "Try again" button on the results screen to reset your score and go through all the questions again from the start.
Where can I find more Enterprise Architecture Language exercises?
Browse the full Enterprise Architecture Language hub for related drills, or check the site-wide exercises index for other IT English topics.
Is this exercise suitable for beginners?
This exercise assumes basic familiarity with IT terminology. If a term feels unfamiliar, check the site Glossary for a plain-English definition before attempting the questions.
How often is new content like this published?
New exercises are added regularly across all categories, alongside new vocabulary sets and articles. Check back on the exercises hub to see what's new.