Architecture Fundamentals and Roles Flashcards
7 cards from real CPSA practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 7 Architecture Fundamentals and Roles flashcards as text
Which of the following best exemplifies the 'principle of least privilege' as an architectural concern?
Answer: Each system component is given only the permissions it needs to perform its function
The principle of least privilege means each component or user is granted only the minimum permissions required for its intended function, reducing the attack surface.
A software architect is presenting to C-suite executives. Which type of architectural view is most appropriate?
Answer: A high-level context diagram showing the system's role and key external relationships
Executives need a high-level context view that conveys business value and system boundaries rather than technical implementation details.
What distinguishes 'functional requirements' from 'quality requirements' in the context of architectural work?
Answer: Functional requirements describe what the system does; quality requirements describe how well it does it
Functional requirements define the system's behaviors and capabilities, while quality requirements (non-functional requirements) specify how well those behaviors must be performed.
In a large organization, which of the following BEST describes the relationship between enterprise architecture and solution architecture?
Answer: Solution architecture operates within the constraints and standards set by enterprise architecture
Solution architecture defines the architecture for a specific project or system, operating within the broader standards, patterns, and constraints established by enterprise architecture.
Which of the following is an example of an architectural 'hotspot'?
Answer: A component that is both highly complex and frequently changed, accumulating technical debt
An architectural hotspot is a component combining high complexity with high change frequency, making it a primary source of defects and maintenance burden.
When should an architect prefer explicit over implicit architectural decisions?
Answer: Always — important decisions should be documented rather than assumed or left undiscovered
Explicit decisions are documented with rationale, making them visible, reviewable, and understandable to current and future team members; implicit assumptions are a source of architectural risk.
Which quality attribute is MOST directly threatened when a system has tightly coupled components with no clear interfaces?
Answer: Maintainability
Tight coupling without clear interfaces makes it difficult to modify, test, or replace components independently, directly harming the system's maintainability.