ISQI ISAQB Certified Professional for Software Architecture - Foundation Level (CPSA-FL Deutsch Version) - CPSA-FL Deutsch Exam Practice Test

Explanation:
A) FalseB) TrueC) TrueD) False
A) Architectural objectives and project objectives need to be identical.
* This is false. Architectural objectives are concerned with the technical goals and quality attributes of the system, while project objectives are broader and include timelines, budgets, and overall project deliverables12.
B) Most of the time, architectural objectives are of a more long-term nature than project objectives.
* This is true. Architectural objectives often focus on the sustainability and maintainability of the system, which are long-term considerations, whereas project objectives may be more immediate and focused on the project's completion12.
C) Architectural objectives and project objectives need to be negotiated between the concerned parties.
* True. Both sets of objectives should align with the stakeholders' needs and the project's overall goals, and thus require negotiation to ensure that all parties' interests are addressed3.
D) Architectural objectives are a subset of project objectives.
* This is false. Architectural objectives are not necessarily a subset but are related and should support the project objectives. They deal specifically with the architecture of the system, which is one aspect of the project

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.

Explanation: Only visible for Fast2test members. You can sign-up / login (it's free).

Explanation: Only visible for Fast2test members. You can sign-up / login (it's free).

Explanation:
A) CorrectB) IncorrectC) CorrectD) CorrectE) IncorrectF) Incorrect
The concept of coupling between building blocks is crucial in software architecture, and the iSAQB SOFTWARE ARCHITECTURE - FOUNDATION LEVEL provides guidance on this topic. Here's an analysis of the statements based on the curriculum:
A) A high degree of coupling of a building block reduces its reusability: This is correct. High coupling means that a building block is heavily dependent on other components, which can limit its ability to be reused in different contexts1.
B) Low coupling of a building block improves the ability to meet functional requirements: This statement is incorrect. While low coupling can contribute to a more maintainable and flexible architecture, it does not directly improve the ability to meet functional requirements1.
C) Low cohesion often leads to high coupling: This is correct. Cohesion refers to how closely related the responsibilities of a module are. Low cohesion can result in modules that perform a wide range of actions, which often leads to higher coupling with many other modules1.
D) Loose coupling often leads to less effort for making changes: This is correct. Loose coupling allows for easier modification of a system with minimal impact on other components, thus reducing the effort required for changes1.
E) For call dependencies, the degree of coupling is independent of the direction of the call: This statement is incorrect. The degree of coupling can be affected by the direction of the call, as it determines which module controls the interaction1.
F) In object-oriented programming languages, inheritance reduces coupling: This statement is incorrect.
Inheritance can actually increase coupling because it creates a direct dependency between the superclass and the subclass1.
These insights are aligned with the principles outlined in the iSAQB SOFTWARE ARCHITECTURE - FOUNDATION LEVEL curriculum, which emphasizes the importance of understanding and managing coupling for effective software architecture design1.