Online Access Free CPSA-FL Exam Questions

Which elements should be defined in the white-box view of a software building block 'foo'? Select the three most important elements. (Choose three.).

• A.The internal building blocks of 'foo'
• B.The algorithms of the internal building blocks of 'foo'
• C.The rationale for the decomposition of the building block
• D.The legal contracts with the suppliers of the internal building blocks of 'foo'
• E.The dependencies of the internal building blocks of 'foo'
• F.The sizes (in lines of code) of the internal building blocks of 'foo'

Choose the most desirable characteristics of interfaces. (Choose three.)

• A.Scalable to many consumers
• B.Remotely callable
• C.As few parameters as possible
• D.Geared towards the capabilities of the provider
• E.Clear descriptions of assertions and prerequisites
• F.Easy to extend
• G.Hard to misuse

Which characteristics of a building block are only visible in the whitebox view, and for which characteristics does the blackbox view suffice? (Assign all answers.)

Correct Answer:

Explanation:
For a building block, the characteristics visible only in the whitebox view are:
* Code structure of the building block (D)
* Algorithms used in the building block (E)
* Implementation details for the security requirements of the building blocks (G) The blackbox view suffices for:
* Public interfaces of the building block (A)
* Test coverage based on unit tests for sub building blocks contained in the building block (B)
* Test coverage based on integration tests
* Security requirements of the building blocks (F)
In software architecture, the whitebox view reveals the internal workings of a building block, including its code structure, algorithms, and specific implementation details1. This view is essential when the internal structure and behavior of the component need to be understood or modified.
On the other hand, the blackbox view treats the building block as an opaque entity, focusing on its exposed interfaces and observable behaviors without revealing its internal structure2. This view is sufficient for understanding what the building block does from an external perspective, such as its public interfaces and how well it performs its functions as determined by testing.
Here's a breakdown of the characteristics:
* Whitebox View:
* Code Structure (D): This includes the organization of code within the building block, such as classes, interfaces, and other components.
* Algorithms (E): The specific algorithms used within the building block to perform its functions.
* Implementation Details for Security (G): The actual code and strategies used to fulfill the security requirements.
* Blackbox View:
* Public Interfaces (A): The interfaces that are exposed to other building blocks or systems.
* Test Coverage for Sub Building Blocks (B): The extent to which the unit tests cover the sub-components within the building block.
* Test Coverage for Integration Tests : The coverage of tests that verify the interactions between building blocks.
* Security Requirements (F): The security objectives and criteria that the building block must meet.
References:
* arc42 Documentation on Building Block View1.
* Stack Overflow discussion on the difference between black box and white box in component diagrams2.
* Flylib Section on Black-Box and White-Box Component Views3.

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.

Concerning external interfaces, Postel's law suggests: "Be conservative in what you do, be liberal in what you accept from others." Assume that Postel's law has been consistently applied in your system. (Assign all answers.)

Correct Answer:

Explanation:
A) FalseB) FalseC) FalseD) TrueE) TrueF) False
Postel's law, also known as the robustness principle, is a guideline in software engineering that advises to "be conservative in what you do, be liberal in what you accept from others"1. This principle has implications for system design and interaction with external interfaces:
A) Response time of the system is reduced: This is false. Postel's law does not directly relate to the response time of a system1.
B) Implementation effort increases: This is false. Being liberal in what is accepted can actually simplify implementation because the system is designed to handle a wider range of inputs without failure1.
C) Usability of the system is reduced: This is false. Postel's law aims to increase robustness and interoperability, which can enhance usability by making the system more resilient and accommodating1.
D) Robustness of the system is increased: This is true. By being conservative in outputs and liberal in inputs, the system becomes more robust, handling a variety of inputs without error1.
E) The integrity of the data transferred via interfaces is increased: This is true. Accepting a wide range of inputs and adhering strictly to output specifications helps maintain data integrity across different systems1.
F) Availability of the system is reduced due to potentially bad quality of input data: This is false. Postel's law suggests that the system should be designed to handle poor quality input data gracefully, thus maintaining availability1.
Applying Postel's law helps create systems that are more tolerant of input variations and strict in their outputs, contributing to overall system robustness and reliability1.