OGB-001 TOGAF Business Architecture Level 1: Version 9.2 Credential and the Newer Foundation Path

OGB-001 is the English TOGAF Business Architecture Part 1 examination from The Open Group. It leads to the TOGAF Business Architecture Level 1 certification credential based on the TOGAF Standard, Version 9.2. The exam contains 30 simple multiple-choice questions, allows 45 minutes, is closed book, and requires 18 correct answers for a 60% pass. There are no prerequisites.

The credential remains part of the TOGAF certification portfolio, but candidates should understand the version context. The Open Group has also introduced TOGAF Business Architecture Foundation based on the TOGAF Standard, 10th Edition and provides a transition path for Level 1 holders. The newer exam is OGBA-101. OGB-001 should therefore be chosen deliberately when the Version 9.2 Level 1 credential is the intended target.

Business Architecture connects strategy to the structures that realize it

Business Architecture helps an organization describe what it does, where value is created, which capabilities are needed, how information supports the work, and how those pieces relate to strategic direction. The discipline provides a bridge between high-level intent and the portfolio of changes needed to alter how the enterprise operates. It is especially useful when multiple programs claim to support the same strategy but use inconsistent language to describe business needs.

OGB-001 preparation should keep this purpose visible. The exam is knowledge-based, yet the topics make more sense when connected to a real business problem. Choose an organization or product and ask what value it delivers, what capabilities make that value possible, what information is essential, and what changes are needed. Then map the official concepts to that example without letting the example replace TOGAF definitions.

Business modeling provides representations for understanding the enterprise

The Level 1 body of knowledge includes Business Modeling and its relationship to Enterprise Architecture in a TOGAF context. Candidates should understand why different modeling techniques exist and what questions a model can answer. A model is valuable when it reduces ambiguity about the business, exposes relationships, and supports decisions; it is not valuable simply because it is detailed.

When studying a modeling technique, write down its purpose, the kind of information it emphasizes, and what decision it can inform. Compare techniques that appear similar. This prevents a common Foundation-level mistake in which a candidate recognizes a familiar diagram type but cannot distinguish why one representation is appropriate for a capability question and another for value, information, organization, or process analysis.

Business Capabilities describe what the enterprise must be able to do

A capability expresses an ability the organization needs in order to achieve an outcome. It should not be confused automatically with a department, an application, or a process. Organizational ownership can change while the underlying capability remains necessary; technologies can be replaced while the business still needs the ability. That stability makes capabilities useful for planning and investment conversations.

Practice separating “what” from “how.” If the business must be able to assess credit risk, manage suppliers, fulfill orders, or analyze customer behavior, identify the capability before describing the process steps, organizational unit, or technology implementation. Then consider how capability mapping can show maturity, importance, gaps, or investment priorities. Clear boundaries make capability questions much easier than memorizing a list of diagram labels.

Capability decomposition should preserve the same “what the business can do” perspective at different levels of detail. Candidates can practice by taking a broad capability and decomposing it into more specific abilities without accidentally switching into workflow steps or organization charts. This is useful for portfolio planning because gaps can be discussed consistently even when responsibility is distributed across several teams or enabled by several systems.

Value Streams show how value is produced for a stakeholder

Value Streams provide a value-oriented view of the business. They help architecture teams examine the sequence of value-creating stages from a stakeholder perspective without reducing the analysis to a departmental process map. This is important because value frequently crosses organizational boundaries. A customer outcome can depend on sales, operations, finance, technology, service, and partners even when none of those functions owns the whole stream.

Build study examples around a specific triggering need and resulting value. Identify the stages through which that value is progressively created, then connect supporting capabilities. The exercise clarifies why value streams and capability maps are powerful together: one describes the progression of value, while the other describes the abilities needed to make that progression possible. Keeping their roles distinct is a useful exam distinction.

Value-stream stages and capabilities can then be cross-mapped. One capability may support several stages, and one stage may depend on several capabilities. This many-to-many relationship helps architects identify where an important capability has broad impact or where a critical stage depends on weak abilities. For exam preparation, the exercise reinforces why the two views are complementary rather than interchangeable and why architecture teams often use them together during transformation analysis.

Information Mapping clarifies the business information needed for decisions and work

Business Architecture is not complete if it describes capabilities and value while ignoring the information the business depends on. Information Mapping helps create a business-oriented understanding of important information concepts and their relationships. This supports alignment between business meaning and the systems or data structures that later implement that meaning.

Candidates should resist turning the topic immediately into database design. Business information concepts describe what the enterprise needs to know, not the physical schema used by one application. Practice by identifying information required to perform a capability or progress through a value stream. Then ask how inconsistent definitions could create operational or transformation problems. This keeps the topic at the appropriate architecture level.

Business Scenarios provide a structured way to clarify a business problem

The TOGAF Business Scenario method helps develop and refine requirements by working from a business problem through the environment, actors, desired outcomes, and measures or constraints that shape the solution. For Level 1 preparation, candidates should know the purpose and logic of the method rather than treating it as a generic brainstorming exercise.

Use one transformation problem and work through it systematically. Identify who is affected, what the current difficulty is, what successful change would look like, and which requirements emerge. Then compare that reasoning with the official method. The exercise shows why scenarios are useful to architecture: they connect stakeholder language and business needs to requirements that can guide later architecture work.

Quality matters more than narrative length in a business scenario. The description should be specific enough to expose actors, environment, objectives, and measurable expectations without becoming a fictional case study full of irrelevant detail. When reviewing practice examples, remove sentences that do not change a requirement or decision. This sharpens the candidate’s understanding of how the method turns a business problem into architecture-relevant information rather than merely documenting the problem in prose.

Business Architecture is developed within the broader TOGAF ADM context

The credential also expects understanding of how Business Architecture can be developed using the TOGAF Architecture Development Method. Business Architecture is not an isolated catalog of capabilities. It participates in an architecture cycle where vision, requirements, other architecture domains, opportunities, migration, governance, and change management interact.

Candidates who already know TOGAF 9 should use that context without assuming the specialization exam is redundant. The Open Group describes Business Architecture Level 1 as a specialization that goes into more detail than the TOGAF 9 Certified syllabus. The exam can therefore stand alone, but it also deepens a capability that general enterprise-architecture study only introduces.

The 10th-Edition Foundation path is a newer option, not proof that Level 1 vanished

The current portfolio includes the Version 9.2 Business Architecture Level 1 credential and the newer TOGAF Business Architecture Foundation certification based on the 10th Edition. The newer Foundation exam uses 40 questions in 60 minutes with a 60% pass mark. Its presence changes the choice available to new learners but does not justify describing OGB-001 as retired when The Open Group still lists the Level 1 credential and a transition pathway.

Candidates should compare the credential their employer recognizes, the body of knowledge used by their training, and whether they expect to continue in the newer portfolio. Someone specifically asked to earn Level 1 should prepare for OGB-001. Someone starting fresh without that requirement should inspect OGBA-101 and the current Foundation path before committing to Version 9.2 materials.

Thirty questions in 45 minutes creates a compact knowledge exam. Efficient preparation should focus on distinctions among the five major business-architecture areas highlighted by The Open Group: business modeling, capabilities, value streams, information mapping, and business scenarios, plus their use in a TOGAF architecture context. Each topic should have a purpose, a small example, and a clear boundary from neighboring concepts.

Finish with timed mixed sets and an error log that records the distinction that failed. If a process is repeatedly confused with a capability, practice “how” versus “what.” If value streams and process models blur together, return to stakeholder value. If information mapping drifts into physical data design, re-establish the business level. OGB-001 rewards clean conceptual boundaries, and those same boundaries make the credential useful beyond the exam.

A useful capstone is a one-page transformation map that links a strategic objective to a value stream, the capabilities that enable its stages, the business information those capabilities require, and a scenario that clarifies a change requirement. The map is not an official exam artifact; it is a study device that forces the main topics to coexist coherently. If the candidate can explain every connection without sliding into process or system detail, the core Level 1 distinctions are usually becoming stable.