TOGAF 10 Exam Guide: Enterprise Architecture Syllabus Topics

Lena: Hey everyone! Welcome to today’s session. We’re diving into something that sounds incredibly formal but is actually the secret sauce behind how the world’s biggest companies stay organized—and more importantly, how you can get certified to lead that organization. We are talking about the TOGAF Standard, 10th Edition. Now, if you’ve ever looked at a massive corporation and wondered how they keep their IT strategy from crashing into their business goals, the answer is usually Enterprise Architecture. And today, we’re breaking down the exam syllabus so you can walk into that test center with total confidence.

Miles: It’s good to be here, Lena. And you’re right—TOGAF isn’t just a set of acronyms. It’s the world’s leading methodology for this stuff. Developed by The Open Group, it’s basically the de facto standard. There are over 100,000 certified practitioners out there right now. Think about that. That’s a massive community. And with today being April 19, 2026, we’re looking at a framework that has recently evolved to be much more modular and agile than the versions people were studying just a few years ago.

Lena: That’s the big hook for me. I think a lot of people hear "Enterprise Architecture" and they think of these dusty, thousand page manuals that nobody actually reads. But the 10th Edition—or TOGAF 10—is different, right? It’s not this monolithic block anymore.

Miles: Exactly. It’s shifted from being a "one size fits all" monster to a flexible, modular toolkit. If you’re coming from TOGAF 9.2, which was the standard for a long time, the first thing you’ll notice is that they’ve split the content. You’ve got your "Fundamental Content," which is the core stuff that doesn't change much, and then you have these "Series Guides" that are dynamic. They cover things like Agile, Digital Transformation, and specific industries. It’s much more about how you actually apply the framework in the real world rather than just memorizing a book.

Lena: And for our listeners who are eyeing those certification badges—maybe you're looking at that Foundation level or the Practitioner level—this shift is actually great news. It means the exam is testing your ability to be a "Practitioner" in a modern sense. We’re talking about high stakes here, too. I mean, looking at the data, an Enterprise Architect in the U.S. can command a salary between $130,000 and $180,000. In the UK, you’re looking at £75,000 to £120,000. If you hit that Chief Architect level, you’re soaring past $250,000.

Miles: The ROI is definitely there. But to get those numbers, you have to pass the exam. And the biggest mistake I see people make is trying to study for TOGAF 10 the same way they might have studied for older IT certifications—just rote memorization. That won't work here, especially for the Practitioner level. You need to understand the ADM—the Architecture Development Method—and how it breathes.

Lena: The ADM is really the heart of the whole thing, isn't it? It’s that circle diagram everyone sees. But before we get into the weeds of the phases, let’s talk about the structure of the exams themselves. Because whether you're doing the Foundation, the Practitioner, or the Combined exam, you need a strategy for the format.

Miles: Right, and that’s a perfect place to start our roadmap. We’ll look at why the Foundation exam is closed-book while the Practitioner exam lets you use the standard—and why that actually makes the Practitioner exam harder for some people. So, let’s get into the architecture of the certification itself.

Lena: Okay, Miles, let’s lay out the "battlefield," as you called it. If I’m a listener and I’m just starting out, I’m seeing a few different paths. I see Foundation, Practitioner, and then this "Bridge" exam. It’s a bit confusing. How do I know which door to walk through?

Miles: It really depends on where you’re starting from. If you’re brand new to TOGAF, you have two main levels. Level 1 is the Foundation. This is all about the "what." It’s the core concepts, the terminology, the basic structure of the ADM phases. It’s 40 questions, multiple choice, and it’s closed-book. You have 60 minutes, and the pass mark is 60%—which means you need 24 out of 40.

Lena: So Foundation is the "vocabulary test," basically? Making sure everyone is speaking the same language?

Miles: That’s a good way to put it. You need to know what a "Building Block" is and what happens in "Phase B." Now, Level 2 is the Practitioner. This is the "how." It’s for people who are actually going to develop and maintain the architecture. This exam is a different beast. It’s only 8 questions, but they are complex, scenario-based questions. And here’s the kicker—it’s open-book.

Lena: Open-book sounds like a relief, but I have a feeling there’s a catch.

Miles: Oh, there’s a major catch. Because it’s open-book, the questions don't ask you for definitions. They give you a paragraph describing a messy, real-world business situation—like a company merging or a digital transformation failing—and ask you what the best move is. They use "gradient scoring" too. The best answer gets you 5 points, the second-best is 3, the third-best is 1, and the "distractor" answer gets you zero. You need 24 points out of 40 to pass.

Lena: Wow, so you can be "kind of right" and still get points? That’s interesting. But it also means you can’t just guess. You have to understand the logic of the framework.

Miles: Exactly. And then there’s the Combined exam. This is for the bold. You sit for both Part 1 and Part 2 in one three-hour session. It’s 150 minutes total—60 for the closed-book Part 1 and 90 for the open-book Part 2. But be careful—if you fail one part, you don’t get the certification, though you only have to retake the part you failed.

Lena: And what about our veterans? I know there are people listening who have been TOGAF 9 certified for years. Do they have to start from scratch?

Miles: No, and that’s where the Bridge exam comes in—the OGEA-10B. This is specifically for TOGAF 9 Certified professionals who want to upgrade to the 10th Edition Practitioner status. It’s a hybrid exam. Section 1 is 10 simple multiple-choice questions, closed-book. Section 2 is 4 complex scenarios, open-book. It’s only 60 minutes long, so the time pressure is intense.

Lena: It sounds like the Bridge exam is really focusing on the "delta"—the changes between version 9 and 10. Which makes sense. If you already know the basics, they want to see if you understand the new modular structure and the emphasis on things like Agile and Digital.

Miles: Precisely. Whether you're doing the full path or the bridge, the goal is the same: proving you can apply the TOGAF Standard to modern business problems. It’s about moving from being a "theorist" to a "practitioner." And to do that, you have to master the engine that drives everything—the ADM.

Lena: The ADM—the Architecture Development Method. It’s the core of the syllabus. I want to really break that down because I think people see the diagram and get overwhelmed by all the letters. Phase A, B, C, D... it feels like alphabet soup until you see the logic behind it.

Miles: It really is a logical flow once you see it as a story of a business problem being solved. So, why don't we start at the very beginning—even before Phase A? Because there’s a crucial step that people often overlook in their study.

Lena: Alright, let’s talk about the "Preliminary Phase." It’s not even Phase A yet, but it’s on the exam. Why is it so important to establish the "capability" before you even start building anything?

Miles: Think of it like this: if you’re going to build a skyscraper, you don’t just start pouring concrete. You have to set up the construction office, hire the right people, and decide what building codes you’re following. In the Preliminary Phase, you’re defining the "where, what, why, who, and how" of the architecture itself. You’re tailoring the ADM to fit your specific organization.

Lena: So, it’s about setting the rules of the game. You’re identifying stakeholders, defining architecture principles, and establishing the "Architecture Capability." I noticed the syllabus mentions "tailoring" a lot. That’s a big theme in TOGAF 10, right?

Miles: Huge. The 10th Edition is all about not being a slave to the framework. You adapt it. In the Preliminary Phase, you ask, "Does our company use Agile? Are we a small startup or a global bank?" You adjust the process accordingly. If you miss this on the exam, you’re missing the "why" behind everything else.

Lena: Okay, so once the office is set up and the rules are clear, we move into Phase A: Architecture Vision. This feels like the "sales pitch" phase.

Miles: It is! Phase A is where you create a high-level vision of the capabilities the business wants to achieve. You’re looking for that "Statement of Architecture Work." This is the document that gets everyone to agree on the scope and the constraints. If you don't have a clear vision, your architecture will eventually drift off into irrelevance.

Lena: On the exam, what should people look for in Phase A? I imagine identifying stakeholders and their concerns is a big part of it.

Miles: Definitely. You have to show that you’ve identified the key players and that you understand what keeps them up at night. You’re also looking for "approval." You can't move to the next phase without a signed-off Statement of Architecture Work. That’s a common exam question—what is the key output of Phase A?

Lena: And it’s also where you define the scope. I’ve seen projects fail because they tried to "boil the ocean." Phase A is where you say, "We are fixing this specific part of the business, not everything all at once."

Miles: Exactly. It sets the boundaries. And once those boundaries are set, you can finally dive into the actual design work. This is where we hit the "BDAT" domains.

Lena: B-D-A-T. Business, Data, Application, and Technology. These are Phases B, C, and D. I think this is where the "meat" of the architecture happens. But I’ve noticed that people often get confused about the order or why they are separate.

Miles: It’s a logical stack. You start with the Business—Phase B—because technology should serve the business, not the other way around. If you don't know the business processes or value streams, how can you design the IT to support them?

Lena: That makes total sense. So, Phase B is about the "Business Architecture." We’re talking about strategy, governance, and organization. Let’s dig into that "BDAT" stack a bit deeper, because that’s a huge chunk of the Foundation exam.

Miles: BDAT is the acronym you’ll probably repeat in your sleep by the time you take the exam. Phase B is Business Architecture. This is where you develop the "Baseline" and the "Target." In fact, that’s a term you’ll see in every BDAT phase. Where are we now—the Baseline—and where do we want to be—the Target?

Lena: And the "Gap Analysis" happens here too, right? You look at the two versions and figure out what’s missing.

Miles: Spot on. In Phase B, you’re looking at business capabilities and value streams. You’re asking, "What does the company actually do to create value?" Once you have that mapped out, you move to Phase C. Now, Phase C is a bit of a "two-for-one" deal. It’s Information Systems Architecture, which is split into Data Architecture and Application Architecture.

Lena: I’ve seen some people try to do Data first, others do Applications first. Does TOGAF care which one comes first?

Miles: It’s flexible, but usually, they go hand-in-hand. Data Architecture is about the logical and physical data assets. How is information managed? Application Architecture is about the software components and how they interact. You’re mapping these back to the business requirements you found in Phase B.

Lena: It’s like building a puzzle. You have the business needs, now you’re figuring out what software and what data "pieces" are required to fulfill those needs. And then, finally, we get to the "bottom" of the stack—Phase D: Technology Architecture.

Miles: Right. This is the hardware, the networks, the platforms, the middleware. The "stuff" that everything else runs on. Again, you do a Baseline and a Target. You identify technology standards. This is where you're defining the IT infrastructure that supports the applications and data from Phase C.

Lena: So, by the end of Phase D, we have a complete blueprint. We know the business goals, the data we need, the apps that use it, and the tech that powers it. But we haven't actually built anything yet. We just have a "Target Architecture."

Miles: Correct. And this is a major "pivot point" in the ADM. You’ve done all this design work, and now you have to figure out how to actually make it happen. This leads us into Phases E and F, which are all about the "Realization."

Lena: I think these phases—E and F—are where the Practitioner exam really tests you. Because this is where the messy reality of budgets, priorities, and "Transition Architectures" comes in. You can't just flip a switch and have the Target Architecture appear overnight.

Miles: Never. It’s a journey. And Phases E and F are the roadmap for that journey. You’re looking at "Opportunities and Solutions" and "Migration Planning." This is where you group projects into work packages. It’s where the "Architecture Roadmap" is born.

Lena: I love the term "Opportunities and Solutions." It sounds so optimistic! But I know it’s actually about making hard choices. "Do we buy this? Do we build it? Do we reuse what we have?"

Miles: Exactly. It’s about assessing the gaps you found in BDAT and deciding how to fill them. And then Phase F is where you finalize the plan and get the business to agree on the value of those "transition states." You’re confirming that the first step of the move is actually worth the money.

Lena: So, E and F take the abstract design and turn it into a concrete project plan. But the ADM doesn't stop there. We still have to govern the implementation and manage change.

Miles: This is where the "Architecture" part of the role really shifts into "Leadership." Phase G is Implementation Governance. This is the architect’s job while the developers and engineers are actually building the systems. You’re making sure that what they build actually matches the architecture you designed.

Lena: I imagine this is where "Architecture Contracts" come in. You’re essentially holding the implementation teams accountable to the plan.

Miles: Exactly. You’re performing compliance reviews. If the team decides to use a different database because it’s "easier," you have to step in and say, "Wait, does this align with our standards and our Target?" Phase G is about maintaining the integrity of the vision.

Lena: And then we have Phase H—Architecture Change Management. This one is interesting because it’s about the fact that the world doesn't stop moving just because you finished a project.

Miles: Right. New technologies emerge—like AI or new cloud models—and business goals shift. Phase H is about monitoring those changes and deciding if they require a new cycle of the ADM. Do we need to go back to the Preliminary Phase and start again? It’s about keeping the architecture "living."

Lena: I noticed that in the middle of that ADM circle, there’s a box called "Requirements Management." It’s not a phase, it’s just... there. In the center.

Miles: That’s because it’s constant. It’s the "hub." Requirements management happens during every single phase. You’re constantly identifying, storing, and managing requirements. If a requirement changes in Phase C, you have to see how it affects Phase B and D. It’s the thread that ties all the phases together.

Lena: It’s a lot to keep track of! For the exam, do I need to know every single output of every single phase? That sounds like a lot of memorization.

Miles: For the Foundation exam, you do need to know the primary deliverables. Things like the "Architecture Definition Document," the "Architecture Requirements Specification," and the "Architecture Roadmap." But for the Practitioner, you need to understand the purpose of these documents. Why would you use a "Transition Architecture" description? When do you need an "Architecture Contract"?

Lena: That "why" is so important. And it leads us to the "Content Framework." TOGAF isn't just a process; it’s also a way of organizing all the "stuff" you create during that process.

Miles: Exactly. The "Architecture Repository" is a big part of the syllabus. It’s where you store the metamodels, the standards, the governance logs. It’s the "library" of the enterprise. And understanding how to navigate that library—and the building blocks inside it—is key to passing.

Lena: "Building Blocks." That’s a classic TOGAF term. ABBs and SBBs. I remember struggling with those at first. Architecture Building Blocks vs. Solution Building Blocks.

Miles: It’s actually a simple distinction once you get it. ABBs are "logical." They describe what is needed. An SBB is "physical." It’s the specific product or component that does it. An ABB might be "A Customer Relationship Management System." The SBB would be "Salesforce."

Lena: Ah, that’s a perfect analogy. The ABB is the "job description," and the SBB is the "person you hired" to do the job.

Miles: Exactly! And the exam loves to test that distinction. If you’re in the BDAT phases, you’re mostly working with ABBs. When you get to Phase E—Opportunities and Solutions—that’s when you start picking your SBBs.

Lena: Okay, Miles, let’s get tactical. We’ve covered the "what." Now let’s talk about the "how." If I’m a listener and I want to pass the Foundation exam in, say, two or three weeks, what is my daily drill?

Miles: First, you have to accept that the Foundation exam is a "breadth, not depth" game. You need to know a little bit about everything. My "Action-First" advice? Start with the ADM cycle. Draw it from memory every day until you can do it with your eyes closed. Not just the phases, but the main goal of each phase.

Lena: I love that. It’s a physical way to get the structure into your brain. What about the documentation? There’s so much of it.

Miles: Don't read the whole TOGAF standard like a novel. You’ll fall asleep by page fifty. Instead, focus on the "Fundamental Content." Use the syllabus as your checklist. The Open Group actually tells you how many questions come from each section. For example, the "Introduction to the ADM" is huge—14 questions out of 40. "Concepts" is 8 questions. If you master those two areas, you’re already more than halfway to a passing score.

Lena: That’s a great tip. Focus your energy where the points are. What’s a common pitfall for the Foundation level?

Miles: Over-thinking. Since it’s simple multiple choice, people often look for "trick" answers. Usually, there aren't any. The correct answer is often a literal definition from the standard. If you’ve memorized the terminology, you’ll see it.

Lena: And practice exams! I’ve seen that the recommendation is to keep taking practice tests until you’re hitting 70% or 80% consistently.

Miles: Absolutely. But don't just memorize the practice questions. When you get a question wrong, go back to the standard and read the section around that topic. Understand the context. For Foundation, you’re building a mental map. You want to know that "Architecture Governance" is part of the "Architecture Capability Framework" and that it involves things like the "Architecture Board."

Lena: Speaking of the Architecture Board, that’s a common entity that pops up. It’s essentially the group of people who make the final decisions, right?

Miles: Right. They’re the "judges." They handle "dispensations"—which is a fancy word for when a project says, "We can't follow the standard for this specific reason, can we have an exception?" Understanding those roles—the Board, the Architect, the Stakeholder—is crucial.

Lena: So, the Foundation strategy is: 1. Draw the ADM daily. 2. Target the high-point sections of the syllabus. 3. Use practice exams to find your "blind spots" in the terminology.

Miles: And do it fast. Don't let the study drag on for months. Two to three weeks of focused study is plenty for Foundation. You want that terminology fresh in your mind.

Lena: But then... then comes the Practitioner exam. And that’s where the "two-week sprint" might not be enough. You need a different mindset for Level 2.

Miles: Definitely. Level 2 is about "analytical rigor." You’re not just a student anymore; you’re an architect in a simulation. So let’s talk about how to tackle those scenarios without getting lost in the weeds.

Lena: Miles, the Level 2 exam sounds like a "choose your own adventure" book, but one where your career depends on the ending. Eight scenarios, 90 minutes. That’s only about 11 minutes per scenario. That feels incredibly tight for reading a long paragraph and four complex options.

Miles: It is tight. And the biggest mistake people make is reading the scenario five times before looking at the answers. My strategy? Read the answers first.

Lena: Wait, really? Why?

Miles: Because the answers tell you what the question is actually looking for. Usually, the four options will follow a pattern. One will focus on "Business Architecture," one will focus on "Governance," one will focus on "Migration Planning," and one will be a "distractor" that sounds good but uses non-TOGAF language.

Lena: That’s brilliant. If you look at the answers first, you can go back to the scenario and look for specific clues. "Oh, the scenario mentions a budget constraint—I should look for the answer that prioritizes Phase E and F."

Miles: Exactly! And remember that "gradient scoring." Your goal isn't necessarily to find the "perfect" answer—it’s to eliminate the zero-point "distractor." The distractor usually suggests something "un-TOGAF"—like skipping a phase or ignoring a stakeholder. Once you eliminate that, you’re guaranteed at least 1 point.

Lena: What about the open-book aspect? You have the PDF of the standard right there in the exam interface. How do you use it without wasting all your time searching?

Miles: This is a vital skill. You have to practice your "PDF search" game. Don't look for whole sentences. Look for keywords. If the scenario is about "Architecture Maturity," search for "Maturity Model" and find the table that lists the levels. If it’s about "Stakeholder Management," find the "Power/Interest" matrix.

Lena: So the open-book isn't for "learning" the material during the exam. it’s for "verifying" specific details like tables, lists, or steps in a phase.

Miles: Exactly. You should already know where the information is in the standard. The open-book is just your "safety net" to make sure you get the 5-point answer instead of the 3-point one.

Lena: I love the "Practitioner" shift in TOGAF 10. It feels like they really want to see if you can handle the complexity. Like, how to adapt the ADM for "Agile" environments. That’s a big part of the new Series Guides, right?

Miles: It’s a huge focus. If the scenario mentions "Agile," your brain should immediately go to the "Agile Architecture" Series Guide. You’re looking for keywords like "Sprints," "Minimum Viable Architecture," and "Just-in-Time design." The standard way of doing things might be too slow for an Agile scenario, so you have to choose the "adapted" path.

Lena: This is where the modularity of TOGAF 10 really shines. It’s not a rigid wall; it’s a set of building blocks you can rearrange. And the exam wants to see if you’re a "master builder" who knows which blocks to use when.

Miles: And that brings us to the most important mindset shift for Level 2: You are the lead architect. The scenario will often ask, "What should the lead architect do next?" You have to think about the process. Did you finish the baseline? Did you do the gap analysis? Did you get the stakeholder sign-off? If you skipped a step, that’s a red flag.

Lena: It’s about the "integrity" of the ADM. Even if you’re being agile and flexible, you still have to follow the logical flow. You can't build the solution until you understand the problem.

Lena: We have to talk about the Bridge exam—the OGEA-10B. Because for our listeners who are already TOGAF 9 certified, this is the most efficient path. But it’s also a "hybrid" exam, which sounds like it could be a bit of a mental gear-shift in the middle of the test.

Miles: It’s 60 minutes for 14 questions. That sounds easy, but it’s actually very intense because of that Section 1 / Section 2 split. Section 1 is 10 simple questions, closed-book, and you only have about 20 minutes for it. Once you finish it and move to Section 2, you cannot go back.

Lena: That’s a huge "Pitfall Alert." You have to be sure of your Section 1 answers before you click next. And Section 2 gives you 40 minutes for just 4 scenarios.

Miles: Right. And Section 2 is open-book. The Bridge exam is essentially testing your knowledge of the "New Stuff" in TOGAF 10. You need to focus on the "delta." What has changed since version 9.2?

Lena: We’ve mentioned a few—the modular structure, the shift from "monolithic" to "series guides." What else should a TOGAF 9 veteran look out for?

Miles: The terminology changes are subtle but important. "Standards Information Base" is now the "Standards Library." "Governance Log" is now the "Governance Repository." Even the versioning of deliverables changed—instead of "0.1" and "1.0," they use "draft" and "approved."

Lena: Those feel like "easy points" if you just memorize the new names. But what about the bigger structural changes?

Miles: The most significant change is the separation between "Fundamental Content" and "Series Guides." In the exam, you need to know which guides to reference for specific contexts—like the "Leader’s Guide" for establishing an EA capability, or the "Digital Enterprise" guide for transformation projects.

Lena: And they removed the arrows from the ADM diagram! I found that so interesting. It used to look like a strict sequence, but now it’s more "fluid."

Miles: It’s a psychological shift. The removal of arrows conveys that you can move between phases more flexibly. If you’re in Phase C and realize you missed something in Phase B, you just go back. It’s an iterative process, not a linear one.

Lena: So, for the Bridge exam, the strategy is: 1. Master the new terminology. 2. Understand the modular "Fundamental vs. Series" structure. 3. Practice the 40-minute scenario block using the PDF search.

Miles: And specifically, read the "TOGAF Leader’s Guide to Establishing and Evolving an EA Capability." That’s a huge focus for the Practitioner level. It’s all about the "human element"—stakeholder management, team roles, and organizational maturity.

Lena: It’s moving the architect from being a "tech person" to being a "business leader." Which, honestly, is where the high salaries are. You’re not just drawing diagrams; you’re guiding the entire enterprise through change.

Miles: Exactly. It’s about "Applied Architecture." And that’s a perfect segue into our final practical playbook. How do you take all of this—the BDAT, the ADM, the modular guides—and actually turn it into a study plan that works?

Lena: Alright, Miles, let’s wrap all this up into a "Practical Playbook" for our listeners. If someone is starting today, April 19, 2026, what are their next three steps?

Miles: Step one: The "ADM Audit." Take a blank sheet of paper and write down all the ADM phases from Preliminary to Phase H. Under each one, write down its primary goal and its main output. If you can’t do that, you aren’t ready for either exam. This is your "Foundation."

Lena: Step two: The "Resource Filter." Don't try to learn everything at once. If you’re going for Foundation, stick to the "Fundamental Content." If you’re going for Practitioner, start diving into the "Series Guides"—specifically the ones on Agile, Digital, and the Leader’s Guide.

Miles: And Step three: The "Scenario Simulation." This is for everyone. Go to a site like ProcessExam or use official sample questions from The Open Group. Don't just look for the right answer—practice the "Gradient Scoring" mindset. Why is the 5-point answer better than the 3-point one? Usually, it’s because it addresses more of the stakeholder’s concerns or follows the ADM more strictly.

Lena: I love the idea of a "Stakeholder Lens." When you read a scenario, ask yourself: "Who is the most important person in this story, and what are they afraid of?" If the answer addresses that fear, it’s probably the 5-point answer.

Miles: That’s a pro tip right there. And for those taking the Bridge exam, your "Action-First" move is to download the "delta" documents—the ones that specifically list the changes from 9.2 to 10. Focus your study on those "new" areas like the modular structure and the revamped content framework.

Lena: And don't forget the "Open Book Strategy." Practice using the search function in a PDF reader with a timer running. See how long it takes you to find the "Architecture Metamodel" or the "ADM cycle steps." In the exam, every second counts.

Miles: One final piece of advice: watch out for "Un-TOGAF" language. The exam is written by people who live and breathe this standard. If an answer uses slang or non-standard terms, it’s probably a distractor. Stick to the vocabulary of the framework—words like "Capability," "Value Stream," "Building Block," and "Governance."

Lena: It’s like learning a new language. Once you’re fluent, the answers start to jump out at you. And the rewards—as we’ve seen—are massive. You’re not just passing an exam; you’re joining an elite group of professionals who can navigate the most complex business environments on the planet.

Miles: It’s a badge of honor. It proves you have the strategic foresight and the tactical skills to lead digital transformation in 2026 and beyond. It’s a challenge, yes, but it’s a manageable one if you respect the process and study the "why" as much as the "what."

Lena: Well said. I think we’ve given everyone a really solid roadmap here. From the BDAT stack to the gradient scoring of Level 2, the path is clear. It’s just about taking that first step—drawing that ADM circle.

Miles: As we bring this to a close, I want to leave everyone with one thought. Enterprise Architecture isn't about creating the "perfect" plan that never changes. It’s about creating a "resilient" framework that allows a business to evolve without falling apart. That’s why the ADM is a circle—it never truly ends.

Lena: That’s such a powerful way to look at it. You’re not just building a static structure; you’re building an "organism" that can grow and adapt. And by studying for this TOGAF certification, you’re essentially learning the "DNA" of that organism.

Miles: Exactly. So as you go through your study materials this week, don’t just look at them as facts to be memorized for a test. Look at them as tools for your future career. When you read about "Phase G" and implementation governance, imagine yourself in that room, helping a team stay on track. When you look at "Phase B" and value streams, think about how you can help a company find its true purpose.

Lena: I love that shift in perspective. It makes the study process feel so much more meaningful. It’s not just a hurdle; it’s an apprenticeship.

Miles: Well, we’ve covered a lot of ground today. We’ve looked at the exam formats, the ADM phases, the BDAT domains, and the specific strategies for Foundation, Practitioner, and Bridge candidates. I hope this has been a helpful guide for everyone embarking on this journey.

Lena: It’s been a blast diving into this with you, Miles. To everyone listening—thank you so much for joining us. We know your time is valuable, and we hope these insights give you that extra edge you need to ace your TOGAF 10 exam.

Miles: Take a moment today to reflect on which part of the ADM feels most intuitive to you—and which part feels like a "blind spot." That’s your starting point. Focus on the gaps, just like a good architect would.

Lena: Thanks again for listening, and best of luck on your certification journey! You’ve got this.

Miles: Cheers, everyone. Go build something great.