Open Agile Architecture Practitioner Practice Test

Open Agile Architecture Practitioner focuses on architecture work inside agile product organizations: intentional architecture, value streams, governance, platform thinking, and enterprise-level change.

These 12 original questions are a public preview, not official Open Group questions.

What these questions test

• balancing intentional architecture with agile delivery
• aligning architecture to value streams, product teams, and enterprise outcomes
• using governance as lightweight guardrails rather than delivery-blocking bureaucracy

Official-source check

Verify current exam names, exam policies, and certification requirements with The Open Group Open Agile Architecture certification page .

Sample Exam Questions

Question 1

Topic: intentional architecture

What is intentional architecture in an agile context?

• A. No architecture work at all
• B. Enough architectural direction to guide teams without freezing all design up front
• C. A complete final design before any learning
• D. Only infrastructure diagrams

Best answer: B

Explanation: Agile architecture balances direction and adaptability. It avoids both chaos and heavy upfront overdesign.

Question 2

Topic: value streams

Why align architecture to value streams?

• A. To ignore customers
• B. To eliminate product ownership
• C. To support flow of value across teams, systems, data, and operational dependencies
• D. To model only servers

Best answer: C

Explanation: Value streams reveal where architecture must support customer outcomes and cross-team flow.

Question 3

Topic: governance

What is the best agile architecture governance pattern?

• A. Clear guardrails, standards, review points, and decision rights that enable responsible flow
• B. No standards or accountability
• C. Approval of every minor team decision by a central board
• D. Governance only after failure

Best answer: A

Explanation: Agile governance should protect enterprise outcomes without unnecessary friction.

Question 4

Topic: emergent design

How should teams handle design discoveries during delivery?

• A. Hide discoveries
• B. Ignore architecture intent
• C. Freeze the first design forever
• D. Feed learning back into architecture decisions through transparent review and adaptation

Best answer: D

Explanation: Agile architecture adapts based on learning while preserving alignment and governance.

Question 5

Topic: platform thinking

Why might a platform be valuable?

• A. It always eliminates business strategy
• B. It removes all product teams
• C. It blocks deployment forever
• D. It can provide reusable capabilities, standards, and developer experience that improve flow

Best answer: D

Explanation: Platforms can reduce duplicated effort and improve consistency when they are product-managed and outcome-focused.

Question 6

Topic: architecture runway

What does architecture runway support?

• A. Permanent waterfall delivery
• B. Future delivery by preparing enabling architecture work before teams hit major constraints
• C. Ignoring dependencies
• D. Stopping all product work

Best answer: B

Explanation: Architecture runway prepares enough technical and architectural foundation for near-term product delivery.

Question 7

Topic: decentralized decisions

Which architecture decision can often be decentralized?

• A. Local design choices that stay inside guardrails and do not create enterprise-wide risk
• B. Enterprise data-sharing principles
• C. Regulatory compliance accountability
• D. Strategic platform funding

Best answer: A

Explanation: Agile architecture should push decisions to teams when safe while preserving enterprise guardrails for systemic concerns.

Question 8

Topic: technical debt

How should architecture treat technical debt?

• A. Hide it until release
• B. Treat all debt as harmless
• C. Make debt visible, evaluate impact, and prioritize remediation based on value and risk
• D. Remove all product discovery

Best answer: C

Explanation: Technical debt affects adaptability, risk, and flow. Agile architecture makes it visible and manageable.

Question 9

Topic: stakeholder alignment

An architecture decision improves one product team but creates compliance risk for the enterprise. What should happen?

• A. Escalate through architecture guardrails and risk review
• B. Ignore enterprise risk
• C. Let the team decide privately
• D. Remove compliance from architecture

Best answer: A

Explanation: Some decisions have enterprise impact and require governed review.

Question 10

Topic: capability evolution

Why connect architecture work to capability evolution?

• A. It eliminates roadmap planning
• B. It focuses only on code syntax
• C. It removes stakeholder outcomes
• D. It shows how technical and organizational change supports business abilities over time

Best answer: D

Explanation: Capability evolution keeps architecture tied to business value and transformation outcomes.

Question 11

Topic: product-team autonomy

What is the healthy boundary for product-team autonomy?

• A. Teams ignore all enterprise constraints
• B. Teams cannot decide anything
• C. Teams can make local choices within shared principles, standards, risk limits, and integration expectations
• D. Teams avoid learning

Best answer: C

Explanation: Autonomy works best with clear guardrails. It enables speed without sacrificing enterprise coherence.

Question 12

Topic: common trap

Which statement is weakest?

• A. Agile architecture can provide guardrails and enable flow
• B. Agile architecture means architecture is unnecessary
• C. Architecture decisions should adapt to learning
• D. Value streams can reveal architecture dependencies

Best answer: B

Explanation: Agile architecture is not no architecture. It is adaptive, value-focused architecture work that supports product flow and enterprise outcomes.