iSAQB CPSA Foundation Practice Test

iSAQB CPSA Foundation preparation focuses on practical software architecture vocabulary: role, communication, design, quality attributes, documentation, constraints, and tradeoffs.

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

What these questions test

• explaining software architecture decisions, constraints, and tradeoffs
• connecting quality attributes to design and documentation choices
• distinguishing architecture views, patterns, risks, and implementation detail

Official-source check

Verify current certification levels, curricula, and examination rules with the iSAQB CPSA certification page .

Sample Exam Questions

Question 1

Topic: architecture role

What is a core responsibility of software architecture?

• A. Choosing every variable name personally
• B. Structuring important design decisions so quality, constraints, and stakeholder concerns are addressed
• C. Avoiding communication
• D. Replacing all testing

Best answer: B

Explanation: Architecture focuses on significant design decisions, quality attributes, constraints, and stakeholder concerns.

Question 2

Topic: quality attributes

Which requirement is a quality attribute concern?

• A. The system should recover service within an agreed time after a node failure
• B. The login button should say “Sign in”
• C. The product name should be short
• D. The meeting should start at 10

Best answer: A

Explanation: Recovery behavior relates to availability and resilience. Quality attributes describe system qualities beyond individual functional features.

Question 3

Topic: documentation

Why use multiple architecture views?

• A. Different stakeholders need different perspectives on structure, behavior, deployment, and decisions
• B. Views make systems harder to understand by default
• C. Every view must show the same details
• D. Views replace implementation

Best answer: A

Explanation: Multiple views help communicate the architecture to different stakeholders and decision contexts.

Question 4

Topic: tradeoffs

A design improves performance but increases operational complexity. What should the architect do?

• A. Hide the complexity
• B. Reject all performance work
• C. Document and evaluate the tradeoff against stakeholder priorities and constraints
• D. Ignore operations

Best answer: C

Explanation: Architecture work often involves tradeoffs. The strongest answer makes the tradeoff explicit and evaluates it in context.

Question 5

Topic: constraints

Which item is an architecture constraint?

• A. A regulatory requirement that customer data must be stored in a specific region
• B. A preferred coffee brand
• C. A lunch schedule
• D. A slide theme

Best answer: A

Explanation: Constraints limit design choices. Regulatory data residency can materially shape architecture.

Question 6

Topic: patterns

What is the best use of an architecture pattern?

• A. Use it as a proven design idea, then evaluate fit and tradeoffs in context
• B. Apply it blindly
• C. Use it to remove all requirements
• D. Treat it as a vendor contract

Best answer: A

Explanation: Patterns are reusable solutions, but they must be evaluated for context, constraints, and quality goals.

Question 7

Topic: technical debt

Why is technical debt an architecture concern?

• A. It can affect maintainability, modifiability, risk, cost, and future delivery speed
• B. It never affects architecture
• C. It is always harmless
• D. It belongs only to finance

Best answer: A

Explanation: Technical debt can limit architecture quality and future change. It should be visible and managed.

Question 8

Topic: interfaces

What makes an interface decision architecturally significant?

• A. It shapes coupling, integration, deployability, performance, security, or evolution between components
• B. It is always trivial
• C. It never affects testing
• D. It removes quality concerns

Best answer: A

Explanation: Interfaces influence system structure and cross-component qualities.

Question 9

Topic: stakeholder concerns

Which stakeholder concern is most architecture-relevant?

• A. Operations needs observable failure modes and manageable deployment rollback
• B. Someone dislikes a meeting title
• C. A slide has a typo
• D. A desk is near a window

Best answer: A

Explanation: Operational concerns such as observability and rollback affect architecture decisions.

Question 10

Topic: decision records

Why record architecture decisions?

• A. To preserve rationale, alternatives, consequences, and context for future review
• B. To stop teams from learning
• C. To avoid documentation entirely
• D. To hide assumptions

Best answer: A

Explanation: Decision records help teams understand why choices were made and when they should be revisited.

Question 11

Topic: modifiability

Which design choice can improve modifiability?

• A. Clear boundaries and lower coupling between parts that change for different reasons
• B. One giant module for all features
• C. Hidden dependencies
• D. No tests or documentation

Best answer: A

Explanation: Modifiability often improves when responsibilities and dependencies are clear.

Question 12

Topic: common trap

Which statement is weakest?

• A. Architecture is only drawing diagrams after coding is done.
• B. Architecture addresses significant design decisions.
• C. Architecture should consider quality attributes.
• D. Architecture communication depends on stakeholder needs.

Best answer: A

Explanation: Diagrams can help, but architecture is about decisions, rationale, structure, constraints, qualities, and communication.