The Open Group · TOGAF-Agile-Specialist
Validates knowledge and understanding of how to adapt and use the TOGAF® framework to support an Agile enterprise. Covers applying the TOGAF ADM using Agile sprints, Agile Enterprise Architecture governance, and Agile Product Management techniques.
Questions
589
Duration
60 minutes
Passing Score
60%
Difficulty
SpecialtyLast Updated
Jun 2026
Use this TOGAF-Agile-Specialist practice exam to prepare for The Open Group Certified: TOGAF® Framework Agile Specialist with realistic questions, detailed explanations, and focused study modes. The practice bank includes 589 questions for The Open Group TOGAF-Agile-Specialist, so you can review the exam steadily instead of relying on one long cram session.
As you practice, pay extra attention to recurring topics such as Agility Concepts and Enterprise Architecture, Adapting the TOGAF Standard for Agile Environments, Applying the TOGAF ADM with Agile Sprints, Agile Enterprise Architecture Governance, and Agile Product Management Techniques. Start with short sessions to identify weak areas, then move into timed quizzes once your accuracy is consistent.
The explanations are especially useful when you want to connect exam wording to the responsibilities and scenarios described in the official certification guidance. Use the free preview first, then unlock the full question bank when you are ready to build a complete study routine.
The Open Group Certified: TOGAF® Framework Agile Specialist is a knowledge-based certification credential that validates an Enterprise Architect's ability to adapt and apply the TOGAF® Standard within Agile organizational contexts. It is aligned to The TOGAF® Standard, 10th Edition, and focuses specifically on reconciling the structured, phase-based nature of the TOGAF Architecture Development Method (ADM) with the iterative, sprint-driven practices characteristic of Agile delivery. The credential demonstrates that the holder understands how to reshape the TOGAF framework—including its governance and content metamodel—to support continuous, incremental architecture work rather than traditional waterfall-style engagements.
The certification covers a focused set of competencies: understanding Agile principles in the context of Enterprise Architecture, applying the TOGAF ADM through Agile sprints, implementing Agile EA governance, and leveraging Agile Product Management techniques. It is part of The Open Group's broader TOGAF Certification Portfolio, which includes specialist and leadership credentials that build on the foundational TOGAF Enterprise Architecture qualification. The credential is issued with an Open Badge and a certificate, and it does not expire—remaining tied indefinitely to the specific version of the Body of Knowledge against which it was earned.
This certification is designed for practicing Enterprise Architects who already hold a TOGAF certification at the Foundation level or higher and who work in, or are transitioning to, organizations that have adopted Agile delivery models. It is particularly relevant for architects embedded in Agile teams, Solution Architects operating within SAFe or Scrum environments, and EA practitioners tasked with modernizing their organization's architecture governance to align with iterative development cadences.
Professionals in roles such as Enterprise Architect, Solutions Architect, IT Architect, and Architecture Practice Lead will find this credential most directly applicable. It is also well-suited for Agile Coaches and transformation leads who want a formal understanding of how TOGAF frameworks can coexist with and enhance Agile methods, rather than conflict with them.
Candidates must hold a current TOGAF certification at the Foundation level or higher before pursuing this credential. This means a passing result on the TOGAF® Enterprise Architecture Part 1 exam (OGEA-101)—or an equivalent legacy TOGAF 9 Foundation qualification—is a hard requirement. There is no waiver or alternative pathway; the Foundation certification must be in place before attempting the Agile Specialist assessment.
Beyond the formal prerequisite, candidates are expected to have practical experience working as an Enterprise Architect and a working knowledge of Agile methodologies such as Scrum, Kanban, or Scaled Agile Framework (SAFe). Familiarity with the TOGAF ADM phases, architecture governance concepts, and the TOGAF content metamodel will significantly reduce the learning curve. The credential requires completion of the Learning Units defined in The Open Group's Conformance Requirements document before sitting the assessment.
The TOGAF Framework Agile Specialist is assessed through a knowledge-based examination administered via The Open Group's authorized examination platform, delivered by Pearson VUE at accredited test centers or online via Pearson VUE OnVUE proctored delivery. The exam has a time limit of 60 minutes and a passing score of 60%. The question format is multiple choice, consistent with other TOGAF credential-level assessments in the portfolio.
Candidates are required to complete the prescribed Learning Units—estimated at approximately 3 hours of structured self-study—prior to taking the assessment. The credential is a closed-book exam. Upon passing, candidates receive an Open Badge (issued via Credly) and a certificate from The Open Group. If a candidate does not pass, a 30-day waiting period applies before a retake is permitted. The credential does not expire once earned.
Earning the TOGAF Framework Agile Specialist credential signals to employers that an Enterprise Architect can operate effectively in modern Agile delivery environments—a capability increasingly demanded as organizations scale Agile practices beyond individual teams to enterprise-wide transformation programs. It directly complements certifications such as SAFe Architect or PMI-ACP by providing the TOGAF governance and framework layer that those credentials lack, making the combination particularly valuable for architects working within SAFe or LeSS implementations.
The credential strengthens candidacy for roles such as Enterprise Architect, Principal Architect, Agile Transformation Lead, and Architecture Practice Manager in organizations undergoing digital transformation. While The Open Group does not publish salary data, TOGAF-certified architects consistently command above-average compensation in the EA market; the Agile Specialist add-on increases marketability specifically in sectors—financial services, telecommunications, government IT modernization—where Agile at scale and rigorous architecture governance must coexist. The non-expiring nature of the credential means no ongoing recertification cost, and the Open Badge format enables straightforward verification by employers via Credly.
5 sample questions with answers and explanations. Start a practice session to test yourself across all 589 questions.
Preview — answers shown1. Contoso Retail is choosing an integration approach for a loyalty service, must keep payment-related decisions auditable, and has teams working in two-week sprints with limited tolerance for long design documents. When is lightweight architecture decision evidence MOST needed? (Select one!)
Explanation
Lightweight decision evidence is most needed for structurally significant or cross-team architecture decisions whose rationale must remain traceable. This supports Agile delivery by keeping documentation right-sized while preserving auditability and enterprise alignment. Capturing every standup comment creates waste. Cosmetic, easily reversible local changes usually do not require architecture-level evidence. Waiting until after release risks losing the rationale and weakens governance traceability.
2. Blue Yonder Media wants to align streaming-platform teams while keeping monthly cloud costs predictable and supporting teams with limited architecture skills. The CTO asks for principles that avoid both uncontrolled local choices and slow central approvals. Which TWO principles best apply? (Select two!)
Multiple correct answersExplanation
Apply just-enough governance based on risk and reversibility and shift governance left by giving teams early guardrails and acceptance criteria are correct because they help less-experienced teams make good decisions early while protecting cost and architectural coherence. Centralize every technology and design decision in the Architecture Board is wrong because it creates a bottleneck and ignores delegated authority for low-risk choices. Allow teams to bypass standards whenever a sprint commitment is at risk is wrong because speed does not remove governance obligations. Document only final production decisions after all releases are complete is wrong because traceability must be captured when decisions are made.
3. Contoso Bank is piloting fraud detection in two-week sprints. A sprint review shows that the team implemented a temporary data feed that is consistent with the business goal but does not fully match the target integration pattern. The pilot must continue, and the bank needs an auditable path to conformance. Which response is BEST? (Select one!)
Explanation
The best response is to keep the pilot moving while preserving iterative compliance control. Recording the compliance position and documenting a temporary exception with remediation work creates traceability and supports later review. A working increment does not automatically mean architectural conformance. A full enterprise redesign is disproportionate for a pilot exception. Waiting until production delays feedback and increases compliance risk.
4. A. Datum Travel is using sprints with the TOGAF ADM for disruption notifications that depend on partner API contracts. One architect supports four delivery teams, and teams are repeatedly blocked because integration assumptions are not clarified before sprint commitments. What should the architect do NEXT? (Select one!)
Explanation
Using backlog refinement and sprint planning to prioritize the most urgent architecture analysis is the best response because the immediate problem is that teams lack timely architecture guidance for dependent work. This keeps the ADM aligned with sprint delivery while managing the limited architect capacity. Stopping coordination would increase inconsistent assumptions and rework. Creating a comprehensive multi-year blueprint overcorrects into heavyweight upfront design. Waiting until the final sprint review is too late because teams need integration guidance before making implementation commitments.
5. Northwind Traders is replacing a supplier portal and discovers during Sprint 3 that a team has used a partner-authentication pattern that differs from the agreed target architecture. The pattern may be acceptable temporarily, but the contract requires traceable integration decisions. What is the BEST Agile-adapted governance response? (Select one!)
Explanation
Recording the deviation, rationale, impact, and agreed disposition is correct because Agile-adapted governance still preserves traceability while keeping feedback close to delivery. Local autonomy is appropriate only within agreed guardrails and does not remove the need to govern contractual integration decisions. Stopping all sprint work is too heavyweight and turns governance into a bottleneck. Deferring the issue until final readiness creates late rework risk and weakens evidence for a contract-relevant architecture decision.
$7.99
One-time access to this exam