ISQI certification practice

CPSA-FL Practice Questions

Try 10 free CPSA-FL exam-style questions for ISQI Cpsa Fl certification exam. Check each answer and review the explanation and source references.

Exam code: CPSA-FL
Provider: ISQI
Free questions: 10
Full set: 43 questions
Last update check: October 18, 2026

Start the free questions Browse ISQI exams

The CPSA-FL exam validates your ability to implement and manage core solutions related to this framework. This certification is designed for professionals who design, deploy, and troubleshoot complex environments. On this page, we map the exam syllabus, explain the question formats, and guide your preparation strategy. We have included free CPSA-FL sample questions with answer explanations so you can approach the test with total confidence.

Get Full Access

What are the four key terms in common definitions of software architecture? (Choose four.)

Answer options

Correct Answer:

B, D, E, F

Explanation

Common definitions of software architecture, as outlined in the ISAQB curriculum, consistently revolve around four key concepts. These are the primary structural elements, which are referred to abstractly as Building Blocks (B) and more formally as Components (E). These elements are interconnected through Relationships (D), which define their interactions, dependencies, and communication pathways. The entire architectural structure is purposefully designed to address stakeholder concerns and achieve specific quality attributes, which are derived from Requirements (F). Together, these four terms describe the fundamental structural elements of a system, their interconnections, and the rationale for their design.

Why Incorrect

A. Source code: This is a detailed implementation artifact. Architecture is an abstraction that intentionally hides such details.

C. Functionality: This describes what the system does, which is a result enabled by the architecture, not a core term in the definition of the structure itself.

G. Interfaces: While crucial, interfaces are a specific means of realizing relationships. "Relationships" is the broader and more fundamental term encompassing all types of connections.

References

1. iSAQB® Certified Professional for Software Architecture

Foundation Level Syllabus

Version 3.0.1 EN (2023-03-21): Section 2.1.1

"What is Software Architecture?"

states that most definitions have commonalities

including: "structures consist of parts or components

" "parts interact with each other via interfaces or connections (relationships)

" and "Architecture addresses the concerns of stakeholders (requirements)." The term "parts" is synonymous with Building Blocks.

2. ISO/IEC/IEEE 42010:2011

Systems and software engineering — Architecture description: The standard defines architecture as "The fundamental concepts or properties of a system in its environment embodied in its elements [Components/Building Blocks]

their relationships

and in the principles of its design and evolution." The stakeholder concerns (derived from Requirements) are the primary drivers for defining these concepts and properties.

3. Bass

Clements

& Kazman

R. (2021). Software Architecture in Practice (4th ed.). Addison-Wesley Professional: In Chapter 1

the authors define software architecture as comprising "software elements [Components/Building Blocks]

the relations among them

and the properties of both." The properties are dictated by the system's requirements

particularly quality attribute requirements.

Open this question on its own page

Which of the following principles apply to testing? (Choose two.)

Answer options

Correct Answer:

A, B

Explanation

This question assesses knowledge of the seven fundamental principles of software testing.

A. In general, exhaustive testing is not possible: This is Principle 2. Testing all possible combinations of inputs, preconditions, and execution paths is infeasible for any non-trivial software. Testers must use risk analysis and prioritization to focus efforts.

B. Where many errors exist, more errors are usually hidden: This is a direct consequence of Principle 4, "Defects cluster together." This principle observes that a small number of modules or components usually contain most of the defects, so finding several defects in one area makes it a good place to look for more.

Why Incorrect

C. This contradicts Principle 1, "Testing shows the presence of defects, not their absence." Testing can reveal that defects exist but cannot prove that no defects remain.

D. This is Principle 7, the "Absence-of-errors fallacy." Finding and fixing defects does not guarantee the system is useful or meets user needs if the requirements were incorrect.

References

1. International Software Testing Qualifications Board (ISTQB®). (2018). Certified Tester Foundation Level Syllabus Version 2018. Section 1.3

"Seven Testing Principles (K2)"

pp. 8-9.

Page 8

Principle 2: "Exhaustive testing is impossible. Testing everything (all combinations of inputs and preconditions) is not feasible except for trivial cases." (Supports answer A).

Page 9

Principle 4: "Defects cluster together. A small number of modules or components usually contains most of the defects discovered during pre-release testing

or is responsible for most of the operational failures." (Supports answer B).

Page 8

Principle 1: "Testing shows the presence of defects

not their absence. Testing can show that defects are present

but cannot prove that there are no defects." (Refutes option C).

Page 9

Principle 7: "Absence-of-errors fallacy. Some organizations expect that testers can run all possible tests and find all possible defects

but Principles 2 and 1

respectively

tell us that this is impossible. Further

it is a fallacy to expect that just finding and fixing a large number of defects will ensure the success of a system. For example

thoroughly testing all the specified requirements and fixing all the defects found could still produce a system that is difficult to use

that does not fulfill the users’ needs and expectations..." (Refutes option D).

Open this question on its own page

For which quality characteristics is the software architect responsible? Please name the two characteristics that best match the role of the software architect. (Choose two.)

Answer options

Correct Answer:

A, C

Explanation

A software architect is fundamentally responsible for translating requirements into a viable technical solution. This involves making key decisions that determine the system's quality attributes.

Performance (A) is a critical quality attribute (a non-functional requirement) directly shaped by architectural choices like technology stack, component interaction, data management, and concurrency strategies.

The suitability of the software design for its purpose (C) is the essence of the architect's role. The architect must create a design that not only fulfills functional requirements but also satisfies all quality attributes and constraints, making it fit for its intended purpose. This is the primary goal and responsibility of the architectural design process.

Why Incorrect

B. The technical quality of the software implementation: While the architect sets guidelines and reviews the implementation, the primary responsibility for the line-by-line code quality rests with the development team. The architect is more concerned with the design's quality and its correct realization.

D. The software is free of errors: Ensuring the software is free of functional defects (correctness) is a shared responsibility of the entire team, particularly developers and quality assurance (QA) engineers, through coding and testing. It is not a sole responsibility of the architect.

References

1. ISAQB e.V. (2020). Certified Professional for Software Architecture

Foundation Level

Syllabus

Version 3.0.1.

Page 10

Section 2.2

"Tasks of Software Architects": This section lists key tasks

including "Designing the software architecture

i.e. the fundamental organization of a system..." which directly supports the responsibility for the design's suitability (C). It also lists "Defining

documenting and communicating non-functional requirements (quality requirements) for the system (e.g. reliability

performance

security)

" which directly supports responsibility for performance (A).

2. Bass

Clements

& Kazman

R. (2021). Software Architecture in Practice (4th ed.). Addison-Wesley Professional.

Page 4

Chapter 1

"What is Software Architecture?": "The architectural design decisions are the ones that are hardest to change later. They are the decisions that determine the system’s ability to meet its requirements for performance

reliability

security

and so on." This highlights the architect's responsibility for performance (A).

Page 5

Chapter 1

"What is Software Architecture?": "Architecture is the set of principal design decisions made about the system... The purpose of these decisions is to satisfy the system’s requirements." This statement encapsulates the architect's core responsibility for ensuring the design is suitable for its purpose (C).

3. Hofmeister

Kruchten

Nord

R. L.

& Obbink

H. (2007). A general model of software architecture design derived from five industrial approaches. Journal of Systems and Software

80(1)

106-126.

Section 3.1

"Architectural Drivers": The paper emphasizes that architecture design is driven by functional requirements

quality attributes

and constraints. The architect's job is to create a design that balances these drivers

thus ensuring its suitability for the purpose (C). It explicitly identifies performance as a key quality attribute driver (A). (DOI: https://doi.org/10.1016/j.jss.2006.05.024)

Open this question on its own page

Which three artifacts does the assessment team create when conducting an ATAM evaluation? (Choose three.)

Answer options

Correct Answer:

B, C, G

Explanation

The Architecture Tradeoff Analysis Method (ATAM) is a structured technique for evaluating a software architecture's fitness concerning its quality attribute goals. During an ATAM evaluation, the assessment team collaborates with stakeholders to create several key artifacts. The primary outputs include a utility tree (also called a quality tree) which captures and prioritizes quality attribute requirements as concrete scenarios. These scenarios are then used to analyze the architecture, leading to the identification of risks, non-risks, sensitivity points, and tradeoff points. Therefore, the quality tree, the scenarios, and the list of architectural risks are all core artifacts created by the assessment team during the evaluation.

Why Incorrect

A. This is a general quality management task, not a specific output of an ATAM evaluation, which focuses on architectural analysis.

D. The ATAM process uses the concept of quality models to build a specific utility tree, but it does not create a new, generic quality model.

E. Architecture documentation is a primary input to the ATAM process. It is created by the architect and provided to the assessment team for analysis.

F. This describes an analysis activity rather than a final, documented artifact. The results of this activity are captured in the risk list and utility tree.

References

1. Clements

Kazman

& Klein

M. (2002). Evaluating Software Architectures: Methods and Case Studies. Addison-Wesley Professional. In Chapter 5

"The Outputs of an ATAM Evaluation

" the key outputs are listed as the utility tree

a set of scenarios

and the identified architectural risks

non-risks

sensitivity points

and tradeoffs (pp. 87-89).

2. Software Engineering Institute

Carnegie Mellon University. (2006). Architecture Tradeoff Analysis Method (ATAM). The ATAM process description explicitly lists the utility tree

scenarios

and risks as primary outputs created during the evaluation. Architecture documentation is listed as a required input.

3. International Software Architecture Qualification Board (ISAQB). (2023). Curriculum for Certified Professional for Software Architecture - Foundation Level (CPSA-F). Section 4.3.2

"Architecture Tradeoff Analysis Method (ATAM)

" describes the method's results

which include "documented risks and non-risks" and the use of a "utility tree" to document quality requirements in the form of scenarios.

Open this question on its own page

HOTSPOT Which characteristics of a black-box building block are you able to specify as an architect? (Assign all answers.)

Your Answer

HOTSPOT Which statements regarding top-down and bottom-up design are true? (Assign all answers.)

Your Answer

HOTSPOT You are responsible for the documentation of the software architecture of a large development project. The project consists of three teams, each with its own architect, but with you as the person having overall responsibility of the entire project's software architecture. Which of the following measures are beneficial? (Assign all answers.)

Your Answer

HOTSPOT Which of the following statements regarding the design principle ‘information hiding’ are true and which are false? (Assign all answers.)

Your Answer

HOTSPOT Which information is presented in the building-block view? Rate the alternatives below as either true or false. (Assign all answers.)

Your Answer

HOTSPOT Conway’s law sometimes is referred to as “If you have four teams working on the compiler, you’ll get a 4-pass compiler.” Which interpretations of this law are true, which are false? (Assign all answers.)

Your Answer

Question 1 of 10

Source context

How this practice set is maintained

Maintained by the CertMage content team, this page loads questions from the exam dataset connected to its preparation resource. When an answer includes a supporting reference, it is shown with that answer so you can review the underlying vendor documentation.

Certification objectives, interfaces, and vendor services can change. Verify important details against the provider's current exam guide and documentation before your exam.

How this practice set is maintained

UXQB Certified Professional for Usability and User Experience - Foundation Level

ISQI IREB_CPRE_FL certification exam

TMMi Test Maturity Model Integration Professional