Career upgrade: Learn practical AI skills for better jobs and higher pay.
Level up
All Practice Exams

100+ Free DPBoK Foundation Practice Questions

Pass your DPBoK Foundation (OGD-001) exam on the first try — instant access, no signup required.

✓ No registration✓ No credit card✓ No hidden fees✓ Start practicing immediately
~75-80% Pass Rate
100+ Questions
100% Free
1 / 100
Question 1
Score: 0/0

What is a Docker container?

A
B
C
D
to track
2026 Statistics

Key Facts: DPBoK Foundation Exam

40

Exam Questions

The Open Group

65%

Passing Score (26/40)

The Open Group

60 min

Exam Duration

The Open Group

$320

Exam Fee

The Open Group 2026 retail schedule

Lifetime

Validity

The Open Group

4

Contexts of Scale

DPBoK Standard

The DPBoK Foundation exam (OGD-001) has 40 multiple-choice questions in 60 minutes, with a 65% (26/40) passing score. The body of knowledge is The Open Group's Digital Practitioner Body of Knowledge (DPBoK) Standard, organized by the Four Contexts of Scale: Individual, Team, Team of Teams, and Enduring Enterprise. DPBoK is a reference body of knowledge — not a prescriptive methodology — synthesizing Lean Startup, Agile, DevOps, SRE, cloud, security, adapted ITIL practices, enterprise architecture, governance, FinOps, and organizational design. Lifetime validity with no recertification. The exam is delivered at Pearson VUE test centers and via OnVUE remote proctoring; fee is $320 USD per The Open Group's 2026 retail schedule.

Sample DPBoK Foundation Practice Questions

Try these sample questions to test your DPBoK Foundation exam readiness. Each question includes a detailed explanation. Start the interactive quiz above for the full 100+ question experience with AI tutoring.

1What does the acronym DPBoK stand for?
A.Digital Practitioner Body of Knowledge
B.Digital Product Backlog of Knowledge
C.DevOps Practice Book of Knowledge
D.Digital Platform Body of Knowledge
Explanation: DPBoK stands for Digital Practitioner Body of Knowledge. It is The Open Group's reference standard synthesizing digital practitioner concepts across product, Agile, DevOps, SRE, cloud, EA, and governance — organized by the Four Contexts of Scale.
2Which organization publishes the DPBoK Standard?
A.The Open Group
B.ISACA
C.Project Management Institute (PMI)
D.Scaled Agile, Inc.
Explanation: The Open Group publishes the DPBoK Standard alongside its other reference standards (TOGAF, IT4IT, ArchiMate, Open Agile Architecture). The certification authority is therefore The Open Group, with Pearson VUE administering the OGD-001 exam.
3How many Contexts of Scale does the DPBoK Standard use to organize its body of knowledge?
A.Four
B.Three
C.Five
D.Seven
Explanation: DPBoK organizes its content into Four Contexts of Scale: Individual (Context I), Team (Context II), Team of Teams (Context III), and Enduring Enterprise (Context IV). Each context reflects how concerns evolve as the digital organization grows.
4Which DPBoK context is associated with the founder, solo practitioner, or earliest stage of a digital product?
A.Context I — Individual
B.Context II — Team
C.Context III — Team of Teams
D.Context IV — Enduring Enterprise
Explanation: Context I — Individual is the founder or single-practitioner context. It is where a digital product idea is generated, hypotheses are formed, and the earliest experiments (MVPs) are run. Lean Startup and customer development concepts dominate this context.
5Which DPBoK context covers a single co-located team adopting Agile and DevOps practices?
A.Context II — Team
B.Context I — Individual
C.Context III — Team of Teams
D.Context IV — Enduring Enterprise
Explanation: Context II — Team covers the single team. Practices such as Scrum, Kanban, CI/CD, DevOps CALMS, version control, IaC, and SRE basics live in this context. It is the first context where coordination of multiple people becomes a concern.
6Which DPBoK context introduces the need to coordinate multiple teams via scaling frameworks like SAFe or LeSS?
A.Context III — Team of Teams
B.Context I — Individual
C.Context II — Team
D.Context IV — Enduring Enterprise
Explanation: Context III — Team of Teams is where multiple teams must coordinate their work. Scaling frameworks (SAFe, LeSS, Spotify Tribes/Squads), product portfolio management, pipeline orchestration, and Lean budgeting all appear in this context.
7Which DPBoK context covers governance, regulatory compliance, and enterprise-wide architecture concerns?
A.Context IV — Enduring Enterprise
B.Context II — Team
C.Context I — Individual
D.Context III — Team of Teams
Explanation: Context IV — Enduring Enterprise is the long-lived organization. Governance, risk, and compliance (GRC); enterprise architecture (informed by TOGAF); FinOps; SIAM; regulatory and sustainability concerns — these all live in Context IV.
8DPBoK is best described as which of the following?
A.A reference body of knowledge that synthesizes existing digital practices
B.A prescriptive methodology that tells organizations exactly how to work
C.A software product sold by The Open Group
D.A certification scheme without underlying standard content
Explanation: DPBoK is a reference body of knowledge — it describes WHAT digital practitioners need to know, not HOW they must work. It synthesizes practices from Lean Startup, Agile, DevOps, SRE, ITIL, TOGAF, and other sources rather than prescribing a single methodology.
9What does the 'C' in the DevOps CALMS model stand for?
A.Culture
B.Collaboration
C.Continuous
D.Compliance
Explanation: CALMS stands for Culture, Automation, Lean, Measurement, and Sharing. 'Culture' (the C) is listed first because DevOps adoption is fundamentally a cultural shift before it is a tooling change. 'Collaboration' is a common distractor.
10Which letters in the CALMS DevOps model are correctly expanded?
A.Culture, Automation, Lean, Measurement, Sharing
B.Continuous, Agile, Lean, Management, Scaling
C.Cloud, Automation, Lean, Microservices, Security
D.Culture, Agile, Lean, Metrics, Stakeholders
Explanation: CALMS = Culture, Automation, Lean, Measurement, Sharing. The acronym was popularized by Jez Humble and is the canonical framing used by DPBoK to describe DevOps as a sociotechnical movement.

About the DPBoK Foundation Exam

The DPBoK Foundation certification (OGD-001) validates understanding of the Digital Practitioner Body of Knowledge — The Open Group's reference body of knowledge that synthesizes digital practice across product management, Agile, DevOps, SRE, cloud, security, governance, and operating-model design. The body of knowledge is organized by the Four Contexts of Scale (Individual, Team, Team of Teams, Enduring Enterprise), reflecting how concerns evolve as a digital organization grows.

Assessment

40 multiple-choice questions distributed across the DPBoK Standard syllabus: Digital Transformation Context, the Four Contexts of Scale, Context I (Individual/Founder), Context II (Team), Context III (Team of Teams), Context IV (Enduring Enterprise), cross-cutting themes, and DPBoK standard positioning. Closed-book, 60 minutes.

Time Limit

60 minutes

Passing Score

65%

Exam Fee

$320 USD (The Open Group / Pearson VUE)

DPBoK Foundation Exam Content Outline

10%

Digital Transformation Context

Digital transformation forces, the definition of digital value, value streams, customer-centricity, and continuous improvement. DPBoK's positioning as a reference body of knowledge that synthesizes existing practices rather than introducing a new methodology.

10%

Four Contexts of Scale

Individual (founder/solo practitioner), Team (small co-located group), Team of Teams (multiple coordinating teams), and Enduring Enterprise (long-lived organization with governance and regulation). What each context optimizes for and how concerns evolve as the organization scales.

15%

Context I — Individual / Founder

Digital product idea generation, product vs project distinction, Lean Startup (Build-Measure-Learn loop, Minimum Viable Product, pivot), hypothesis-driven development, Steve Blank's customer development, product/market fit as a milestone before scaling.

20%

Context II — Team

Agile core (Scrum, Kanban), DevOps origin and CALMS (Culture, Automation, Lean, Measurement, Sharing), CI/CD, version control, Infrastructure as Code, cloud service models (IaaS, PaaS, SaaS, FaaS/Serverless), application architecture (monolith, modular monolith, microservices), Site Reliability Engineering (SLO, SLI, SLA, error budgets), containers (Docker, Kubernetes basics), DevSecOps and shift-left security.

20%

Context III — Team of Teams

Coordination across teams: scaling frameworks (SAFe, LeSS, Spotify Tribes/Squads), product portfolio management, pipeline orchestration at scale, Lean budgeting (beyond traditional capex/opex), service management (ITIL processes adapted for Agile), service catalog, incident response, blameless postmortems, federated architecture, architecture runway, Communities of Practice, Center for Enablement (C4E).

15%

Context IV — Enduring Enterprise

Governance, risk, compliance (GRC); the Enterprise Architecture role (informed by TOGAF); strategy alignment; information and data architecture at enterprise scale; regulatory environment; security and risk at scale; business process management; sustainability and digital responsibility; talent and organizational change management; M&A integration; sourcing strategy; vendor management; Service Integration and Management (SIAM); FinOps and IT financial management; OKRs and balanced scorecards; continuous innovation.

5%

Cross-Cutting Themes

People themes throughout the Four Contexts: psychological safety, T-shaped teams, hiring, learning organizations. Technical themes: cybersecurity, data ethics, AI/ML, automation. Relationships between DPBoK and other Open Group standards (TOGAF, IT4IT, Open Agile Architecture) and external standards (ITIL 4, COBIT, BIZBOK).

5%

DPBoK Standard Positioning

DPBoK is a reference body of knowledge — it describes WHAT digital practitioners need to know, not HOW they must work. It synthesizes practices from many sources rather than prescribing a methodology, allowing organizations to map their own approaches into the Four Contexts framework.

How to Pass the DPBoK Foundation Exam

What You Need to Know

  • Passing score: 65%
  • Assessment: 40 multiple-choice questions distributed across the DPBoK Standard syllabus: Digital Transformation Context, the Four Contexts of Scale, Context I (Individual/Founder), Context II (Team), Context III (Team of Teams), Context IV (Enduring Enterprise), cross-cutting themes, and DPBoK standard positioning. Closed-book, 60 minutes.
  • Time limit: 60 minutes
  • Exam fee: $320 USD

Keys to Passing

  • Complete 500+ practice questions
  • Score 80%+ consistently before scheduling
  • Focus on highest-weighted sections
  • Use our AI tutor for tough concepts

DPBoK Foundation Study Tips from Top Performers

1Memorize the Four Contexts of Scale by name and order — Individual, Team, Team of Teams, Enduring Enterprise. Every DPBoK topic maps to one (or sometimes more) of these contexts; many exam questions test which context a given practice belongs to.
2Master CALMS letter-by-letter: Culture, Automation, Lean, Measurement, Sharing. DevOps distractors often replace one letter (e.g., 'Collaboration' instead of 'Culture') — DPBoK uses the canonical version.
3Learn the SRE terminology cold: SLI (Service Level Indicator — a metric), SLO (Service Level Objective — a target), SLA (Service Level Agreement — a contract with consequences), error budget (1 minus SLO, the acceptable failure budget). These are commonly tested.
4Understand that DPBoK is a reference body of knowledge, NOT a methodology. It does not prescribe how to work; it describes what digital practitioners need to know. Questions framing DPBoK as a 'methodology' or 'framework you implement' are usually wrong.
5Know Lean Startup vocabulary: Build-Measure-Learn loop, MVP (Minimum Viable Product — smallest experiment to validate a hypothesis), pivot (changing direction after learning), product/market fit. Customer development is Steve Blank's separate but related model.
6Distinguish product vs project: product is a persistent value-delivering thing with a team that owns it long-term; project is time-bounded work with a defined start and end. DPBoK emphasizes the product orientation.
7Learn cloud service models in order of decreasing customer responsibility: IaaS (you manage OS and up) → PaaS (you manage app and data) → SaaS (you just use it) → FaaS/Serverless (you provide function code only). Foundation-level questions test these boundaries.
8For Context IV, recognize concepts even if they overlap with TOGAF or ITIL — DPBoK is intentionally synthetic. FinOps, OKRs, balanced scorecard, SIAM, federated architecture, C4E, Communities of Practice are all common targets.

Frequently Asked Questions

What is the DPBoK Foundation certification?

OGD-001 (DPBoK Part 1) is The Open Group's foundation-level certification for digital practitioners. It validates understanding of the Digital Practitioner Body of Knowledge — a reference body of knowledge that synthesizes product management, Agile, DevOps, SRE, cloud, security, governance, and operating-model design across the Four Contexts of Scale: Individual, Team, Team of Teams, and Enduring Enterprise.

What are the Four Contexts of Scale?

The Four Contexts of Scale are DPBoK's organizing structure: Context I — Individual (founder/solo practitioner, Lean Startup); Context II — Team (small co-located team, Agile and DevOps); Context III — Team of Teams (multiple coordinating teams, scaling frameworks and product portfolio); Context IV — Enduring Enterprise (long-lived organization with governance, EA, FinOps, regulatory concerns). Each context optimizes for different concerns as the organization grows.

How is the OGD-001 exam structured?

40 multiple-choice questions in 60 minutes; passing score is 65% (26 correct). Closed-book. Distributed across the DPBoK syllabus: Digital Transformation Context, the Four Contexts of Scale and each individual context (I, II, III, IV), cross-cutting themes, and DPBoK standard positioning. Delivered at Pearson VUE test centers or remotely via OnVUE.

How much does the OGD-001 exam cost?

Per The Open Group's exam fee schedule effective from February 2026, OGD-001 costs USD $320 (retail voucher). Accredited training providers may bundle exam vouchers with their courses at a discount. There is no application fee — just the exam fee. The credential carries lifetime validity with no recertification cost.

How hard is the OGD-001 exam?

OGD-001 is foundation-level — well-prepared candidates pass on the first attempt at a high rate (industry estimates ~75-80%). The breadth is the challenge: DPBoK spans many sources synthesized in one body of knowledge. Plan for 25-40 hours of study, with at least one read of the DPBoK Standard plus 100+ practice questions. Watch for terminology distinctions (CALMS letters, SLI vs SLO vs SLA, Four Contexts boundaries, ITIL processes vs DPBoK adapted practices).

What study materials are recommended?

The DPBoK Standard (free download from opengroup.org) is the primary source. Because DPBoK synthesizes other practices, supplement weak areas with the source bodies: 'The Lean Startup' (Ries) for Context I, 'The Phoenix Project' or DevOps Handbook for Context II, 'Team Topologies' for Context III, and TOGAF Series Guides for Context IV. Practice with 100+ concept questions and aim for 85%+ on practice tests before scheduling the exam.

Is DPBoK Foundation valid for life?

Yes — Open Group certifications carry lifetime validity, including OGD-001. There is no recertification or continuing education requirement. If the DPBoK Standard is updated to a new version, The Open Group typically offers a bridging exam so existing credential holders can update without retaking the full exam.

How does DPBoK relate to TOGAF and ITIL?

DPBoK is a reference body of knowledge — it draws on TOGAF for enterprise architecture content (most relevant in Context IV — Enduring Enterprise), and on ITIL for service management practices (adapted for Agile in Context III — Team of Teams). DPBoK does not replace these standards; it synthesizes them into a single body of knowledge organized by the Four Contexts of Scale, so a digital practitioner can see how product, Agile, DevOps, SRE, EA, and ITIL practices fit together.