CPSA Architecture Fundamentals and Roles 4 — Questions and Answers
Question 1: Which of the following best exemplifies the 'principle of least privilege' as an architectural concern?
- Granting all microservices full database admin rights to simplify access management
- Each system component is given only the permissions it needs to perform its function (Correct answer)
- Restricting junior developers from accessing production deployment pipelines
- Using a single shared API key for all external service integrations
Correct 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.
Question 2: A software architect is presenting to C-suite executives. Which type of architectural view is most appropriate?
- A detailed class diagram showing all method signatures
- A component interaction diagram with complete API specifications
- A high-level context diagram showing the system's role and key external relationships (Correct answer)
- A deployment diagram with exact server configurations and IP addresses
Correct 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.
Question 3: What distinguishes 'functional requirements' from 'quality requirements' in the context of architectural work?
- Functional requirements describe what the system does; quality requirements describe how well it does it (Correct answer)
- Functional requirements are optional; quality requirements are mandatory
- Functional requirements are written by architects; quality requirements are written by testers
- Functional requirements concern hardware; quality requirements concern software
Correct 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.
Question 4: In a large organization, which of the following BEST describes the relationship between enterprise architecture and solution architecture?
- Enterprise architecture replaces solution architecture in mature organizations
- Solution architecture operates within the constraints and standards set by enterprise architecture (Correct answer)
- Enterprise architecture focuses on a single project; solution architecture spans the whole organization
- They are interchangeable terms for the same role
Correct 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.
Question 5: Which of the following is an example of an architectural 'hotspot'?
- A wireless network access point used by developers in the office
- A component that is both highly complex and frequently changed, accumulating technical debt (Correct answer)
- A high-performance caching layer that handles peak traffic loads
- A configuration file that stores environment-specific settings
Correct 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.
Question 6: When should an architect prefer explicit over implicit architectural decisions?
- Only when the team has more than 10 developers
- Only during the initial design phase before coding begins
- Always — important decisions should be documented rather than assumed or left undiscovered (Correct answer)
- Only when the customer explicitly requests documentation
Correct 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.
Question 7: Which quality attribute is MOST directly threatened when a system has tightly coupled components with no clear interfaces?
- Security
- Performance
- Maintainability (Correct answer)
- Portability
Correct answer: Maintainability
Tight coupling without clear interfaces makes it difficult to modify, test, or replace components independently, directly harming the system's maintainability.
Which of the following best exemplifies the 'principle of least privilege' as an architectural concern?