Online Access Free CPSA-FL Practice Test

How does management and architects work together? Decide which statements are true and which are false.
(Assign all answers.)

Correct Answer:

Explanation:
A) TrueB) FalseC) TrueD) True
A) The project plan from management is influenced by architectural decisions.
* True. Architectural decisions often have significant implications on the project plan, including timelines, resource allocation, and technical approaches1.
B) Cost estimates are primarily the responsibility of the architect.
* False. While architects may contribute to cost estimates, especially regarding design-related expenses, it is typically the management's responsibility to oversee and finalize cost estimates for the entire project2.
C) Architects advise project management on the definition of work packages.
* True. Architects play a crucial role in defining work packages, particularly in ensuring that the technical aspects of the project are accurately captured and planned for1.
D) Management and architects cooperate on handling of technical risks.
* True. Both management and architects need to work closely to identify, assess, and manage technical risks throughout the project2.

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

Correct Answer:

Explanation:
As an architect, you can specify the following characteristics of a black-box building block:
* Compliance with functional requirements (A)
* Compliance with non-functional requirements (B)
* Purpose and/or responsibility (D)
* Method signature of public interfaces (E)
* Data formats of public interfaces (F)
In software architecture, a black-box building block is a component whose internal structure is not exposed to or understood by other components. It is defined only by its provided functionality and the services it offers.
Here's a detailed explanation of each characteristic:
* Compliance with Functional Requirements (A): This refers to the ability of the building block to perform the functions it was designed to do, which are often captured in a functional specification document.
* Compliance with Non-functional Requirements (B): These are criteria that can be used to judge the operation of a system, rather than specific behaviors. This includes requirements related to scalability, performance, security, and reliability.
* Purpose and/or Responsibility (D): This defines the role the building block plays in the overall system architecture, including its responsibilities and the services it provides.
* Method Signature of Public Interfaces (E): The method signature defines the interface that other components can use to interact with the building block. It includes the method name, parameters, and return type.
* Data Formats of Public Interfaces (F): This specifies the format and structure of the data that is accepted or returned by the building block's public interfaces.
These characteristics are essential for ensuring that the building block can be effectively integrated into a larger system and interact with other components as expected.
References:
* Bass, L., Clements, P., & Kazman, R. (2012). Software Architecture in Practice (3rd ed.).
Addison-Wesley Professional.
* Martin, R. C. (2003). Agile Software Development: Principles, Patterns, and Practices. Prentice Hall.
* Fowler, M. (2002). Patterns of Enterprise Application Architecture. Addison-Wesley.

You are the software architect on a large development project and are entrusted with the task of building a tool chain for continuous architecture evaluation and analysis.
Which of the following statements regarding this tool selection are correct/incorrect? (Assign all answers.)

Correct Answer:

Explanation:
A) IncorrectB) CorrectC) IncorrectD) IncorrectE) Incorrect
In the context of building a tool chain for continuous architecture evaluation and analysis, the following statements can be assessed:
A) Tools for static code analysis do not find all dependencies in the source code. They can find many, but not necessarily all, especially if dynamic programming techniques are used1.
B) Several tools for static code analysis can be used to verify compliance with architectural rules. This is one of the primary uses of static code analysis tools1.
C) Tools for static code analysis cannot reliably measure cohesion because cohesion is a qualitative aspect of modules that depends on the context and design intent, which static analysis alone cannot fully capture1.
D) Tools for static code analysis are not typically used to optimize runtime efficiency. They are more focused on code quality, security, and compliance with coding standards1.
E) Tools for dynamic analysis, such as profilers, can be used to optimize static structures. They provide runtime information that can inform decisions about the static structure of the code1.
These assessments are based on the iSAQB SOFTWARE ARCHITECTURE - FOUNDATION LEVEL documents, which provide guidelines on the selection and use of tools for software architecture evaluation and analysis1.

Decide if the following statements are true or false. The performance of a system (response time or throughput) often competes with its... (Assign all answers.)

Correct Answer:

Explanation:
The performance of a system often competes with its:
* Flexibility (A) - True1
* Memory usage (B) - True1
* On-time completion of the project C - False
* Adaptability (D) - True1
* Usability (E) - True1
* Security (F) - True1
* Testability (G) - True
In system design, performance trade-offs are a critical consideration. Here's an explanation of how each listed aspect competes with system performance:
* Flexibility (A): Systems designed for high performance may be less flexible because they are optimized for specific tasks or conditions1.
* Memory Usage (B): High-performance systems may require more memory to store data and instructions for rapid access, which can be at odds with limited memory resources1.
* On-time Completion of the Project : While performance considerations can impact project timelines, they do not inherently compete with the on-time completion of a project.
* Adaptability (D): Systems that need to perform well under varying conditions may sacrifice adaptability, as they are tightly coupled with their performance optimizations1.
* Usability (E): Sometimes, the pursuit of performance can lead to complex user interfaces or workflows, affecting usability negatively1.
* Security (F): Security measures can introduce additional processing and checks, potentially slowing down system performance1.
* Testability (G): High-performance systems may be harder to test due to their complexity and the need for specialized testing environments or tools1.
These trade-offs highlight the importance of balancing different system attributes to meet the overall goals and constraints of a project.
References:
* CodingDrills article on Trade-Offs in System Design1

Which of the following statements about (crosscutting) concepts are most appropriate? (Select four.)

• A.Uniform usage of concepts reduces coupling between building blocks.
• B.Concepts are a means to increase consistency.
• C.The definition of appropriate concepts ensures the conceptual integrity of the architecture.
• D.A concept might be implemented by a single building block.
• E.A concept can define constraints for the implementation of many building blocks.
• F.For each quality goal there should be an explicitly documented concept.
• G.Uniform exception handling is most easily achieved when architects agree with developers upon a suitable concept prior to implementation.