Why Study with PlanetCert?
The Latest Questions
Practice questions and exam topics aligned with the current exam objectives.
Detailed Explanations
Go beyond the answer. Master the material with comprehensive learning and professional explanations for every concept.

AI-Powered Insights
Personalized preparation guidance that adapts to your performance and identifies weak spots automatically.
Exam Information
Official specifications published by iSAQB
Exam Format
Registration
Validity
Skills this practice test covers
- Explain what software architecture is and which tasks an architect owns in a development team.
- Turn vague quality requirements into quality scenarios based on ISO 25010.
- Apply information hiding, loose coupling and high cohesion when cutting a system into parts.
- Choose between layers, pipes and filters, and microservices for a given set of requirements.
- Document an architecture with a context view and other views, and record decisions as ADRs.
- Assess an architecture with scenario-based reviews, metrics and a look at technical debt.
Explore related topics
CPSA-F exam content
6 domains · 37 topics · 151 of 153 questions sorted by domain
Basic Concepts of Software Architecture15 questions
This domain defines software architecture and the architect's job. Candidates compare definitions, explain the goals and benefits of architecture, and describe how architects work with developers, testers, project managers and other stakeholders.
Skills tested
- Explain what most definitions share: building blocks, their interfaces and their relationships.
- Distinguish architecture decisions from detailed design.
- Describe an architect's tasks and responsibilities within a development team.
Questions by topic
- LG 01-02: Understand and Explain the Goals and Benefits of Software Architecture4
- LG 01-04: Understand the Tasks and Responsibilities of Software Architects3
- LG 01-03: Know Long-term Impact of Software Architecture3
- LG 02-05: Prefer Explicit Statements over Implicit Assumptions1
- LG 01-06: Relate the Role of Software Architects to Other Stakeholders2
- LG 01-10: Challenges of Distributed Systems2
Requirements and Constraints16 questions
Architecture starts from what a system must do and how well. Candidates identify stakeholder concerns, sharpen quality requirements with scenarios and handle constraints from the organization, technology and law.
Skills tested
- Use the ISO 25010 quality characteristics to name what stakeholders expect.
- Rewrite a vague wish for speed or safety as a testable quality scenario.
- Make implicit assumptions explicit and record the constraints that limit design.
Questions by topic
- LG 02-06: Influence of the Organizational Context4
- LG 02-03: Clarify and Scrutinize Quality Requirements4
- LG 02-07: Know Typical Categories of Constraints3
- LG 02-02: Understand and Consider Quality Attributes3
- LG 02-05: Prefer Explicit Statements over Implicit Assumptions2
Design and Development of Software Architectures76 questions
The largest domain is where the structure is designed. Candidates apply design principles, manage dependencies and cohesion, choose patterns, design interfaces and plan cross-cutting concerns and deployment.
Skills tested
- Apply information hiding and loose coupling when cutting a system into building blocks.
- Explain the layers, pipes and filters, and microservices patterns, and when each one fits.
- Use domain-driven design to align building blocks with the business domain.
- Plan cross-cutting concerns such as logging and error handling once for the whole system.
Questions by topic
- LG 03-09: Decide and Design Appropriate Architectures7
- LG 03-10: Identify, Design and Implement Cross-Cutting Concerns4
- LG 03-10: Know and Apply Architectural Patterns22
- LG 03-06: Know and Apply Design Principles11
- LG 03-04: Identify, Explain and Avoid Dependencies and Coupling7
- LG 03-07: Design and Define Interfaces4
- LG 03-05: Creating and Maintaining Cohesion4
- LG 03-03: Understand and Apply Basic Design Principles3
- LG 01-10: Challenges of Distributed Systems1
- LG 03-11: Know and Apply Design Patterns3
- LG 03-02: Know Approaches to Architecture Design2
- LG 03-12: Principles of Software Deployment4
- LG 03-01: Understand Domain-Driven Design4
Specification and Communication of Software Architectures29 questions
An architecture helps only if others understand it. Candidates write documentation that fits its readers, use architectural views and notations such as UML, and document interfaces, cross-cutting concepts and decisions.
Skills tested
- Create a context view that shows the system boundary and its external interfaces.
- Choose the views and UML diagrams that a given stakeholder needs.
- Record a decision with its context, options and consequences as an ADR.
- Structure documentation with a template such as arc42.
Questions by topic
- LG 04-05: Context View5
- LG 04-08: Document and Communicate Architecture Decisions3
- LG 04-02: Describe and Communicate Software Architectures3
- LG 04-04: Explain and Apply Architectural Views8
- LG 04-03: Models and Notations to Describe Software Architecture3
- LG 04-06: Document Cross-Cutting Concepts4
- LG 04-01: Explain and Consider Quality Requirements of Technical Documentation3
Analysis and Assessment of Software Architectures15 questions
This domain checks whether an architecture meets its goals. Candidates name reasons for an analysis, run qualitative reviews with scenarios, read metrics such as coupling and complexity, and recognize technical debt.
Skills tested
- Run a scenario-based qualitative review to find risks in a design.
- Read coupling and complexity metrics and explain their limits.
- Identify technical debt and judge how it slows future change.
Questions by topic
- LG 05-02: Know and Apply Qualitative Analysis5
- LG 05-03: Using Quantitative Analysis/Metrics4
- LG 05-04: Recognizing and Assessing Technical Debt3
- LG 05-01: Reasons for Architectural Analysis3
Examples of Software Architectures
The last chapter links requirements to real solutions through example architectures. The curriculum marks its learning goals R3, so they help understanding but are not examined.
Skills tested
- Trace how a requirement or constraint led to a decision in an example system.
- Explain how an example solution is put into practice technically.
Official topics
- Relation Between Requirements and Solutions
- Understanding Technical Implementations
Requirements
- No formal prerequisites: anyone can book the exam, with or without accredited training.
- Recommended: more than 18 months of team-based software development experience.
- Recommended: skill in at least one higher programming language, plus basic modeling and abstraction.
- Recommended: familiarity with UML class, package, component and sequence diagrams; iSAQB may test these prerequisites.
About the CPSA-F exam
CPSA-F is the Foundation Level exam in software architecture from the International Software Architecture Qualification Board (iSAQB). It is meant for developers who have begun to shape the structure of the systems they build. It checks whether a candidate can turn requirements and quality goals into a design, explain that design to others and judge whether it works. The curriculum marks each learning goal R1, R2 or R3, and only R1 and R2 goals can appear in the exam. Passing earns the CPSA-F certificate, the first step toward the iSAQB Advanced Level.
Design and Development of Software Architectures fills the biggest share of the PlanetCert practice test, with architectural patterns as its largest topic. On trade-off questions, such as layers against microservices for one quality goal, the explanation behind each answer matters as much as the answer. Study Mode works well for the documentation domain, where views and notations need a careful read. Brainy AI Assistant can sketch a context view for a described system or compare two ways of splitting it into building blocks.
How to earn the certification
- Earns
- Certified Professional for Software Architecture – Foundation Level (CPSA-F)Foundation
How to prepare for CPSA-F
- 1
Read the curriculum by relevance
The iSAQB curriculum marks each learning goal R1, R2 or R3. R1 content is examined, R2 content may be, and R3 content is not, so study the R1 goals first.
- 2
Document a system from work
Take a familiar project and write its context view, its building block view and one runtime scenario. Then record two past decisions as ADRs.
- 3
Design one problem three ways
Design and Development of Software Architectures is the largest domain. Sketch one small system as layers, as pipes and filters and as microservices, and list what each option gains and loses.
- 4
Turn qualities into scenarios
Pick three ISO 25010 qualities for a familiar system. Write one scenario for each, with a stimulus, an environment and a measurable response.
- 5
Close with mock and timed runs
Answer iSAQB's published mock exam first, then sit the CPSA-F practice test in Timed Mode. Ask Brainy AI Assistant to explain any missed pattern or principle question.
Start a timed CPSA-Frun
iSAQB accredits training providers that teach Foundation Level courses based on the curriculum. The training is recommended but not required.
Who CPSA-F is for
- Software developers with real team-project experience who now make design decisions.
- Technical leads who design a system's structure and explain it to their team.
- Architects who want a shared vocabulary and method for work they already do.
- Developers in Europe, and in German-speaking countries in particular, where the certificate is best known.
Typical job titles: Software architect · Senior software developer · Technical lead · Solution architect · Software engineer
CPSA-F glossary
17 terms from the exam objectives and the vendor's official material, each defined in a sentence.
- 4+1 view model
- Philippe Kruchten's set of four architecture views, tied together by a fifth set of scenarios.
- ADRs (Architecture Decision Records)
- Short documents that each record one architecture decision, with its context and its consequences.
- arc42
- An open-source template for documenting and communicating a software architecture in a fixed set of sections.
- C4 model
- Simon Brown's way of drawing software architecture at four zoom levels: context, containers, components and code.
- Cohesion
- How closely the responsibilities inside one building block belong together; high cohesion keeps related things in one place.
- Context view
- The architectural view that shows the system as one box, with its users, neighboring systems and external interfaces.
- CQRS
- Command Query Responsibility Segregation: a pattern that uses separate models for changing data and for reading it.
- Dependency Inversion
- The SOLID principle that high-level and low-level parts should both depend on abstractions rather than on each other's details.
- Domain-Driven Design
- An approach that shapes the software around the business domain and the language its experts use.
- Hexagonal Architecture
- A pattern that keeps the domain logic at the center and connects it to the outside world only through ports and adapters.
- Information hiding
- A design principle in which a building block hides its inner details behind an interface, so other parts depend only on that interface.
- ISO 25010
- The international standard that defines a model of software quality characteristics, such as performance efficiency, security and maintainability.
- Layered architecture
- A pattern that splits a system into layers, where each layer offers services to the layer above it.
- Microservices
- An architectural style that builds a system from small services that are deployed independently and talk over a network.
- Pipes and Filters
- A pattern in which data flows through a chain of independent processing steps (filters) joined by connectors (pipes).
- Quality attribute scenarios
- Short, testable statements of how a system must respond to a stimulus, for example how fast a search must answer under peak load.
- Technical debt
- The future cost of design or code shortcuts that make a system harder to change.