CPSA Architectural Goals and Constraints 2 — Questions and Answers
Question 1: Which technique best helps architects identify conflicting quality goals early in a project?
- Quality attribute scenario workshops (Correct answer)
- Writing unit tests for components
- Creating entity-relationship diagrams
- Defining database schemas first
Correct answer: Quality attribute scenario workshops
Quality attribute scenario workshops surface conflicts between competing goals like performance vs. security before design decisions are locked in.
Question 2: A system must handle both real-time trading and batch reporting. These requirements create what type of architectural tension?
- A tradeoff between latency and throughput (Correct answer)
- A conflict between security and availability
- A contradiction between scalability and portability
- An incompatibility between modifiability and reliability
Correct answer: A tradeoff between latency and throughput
Real-time trading demands low latency while batch reporting benefits from high throughput, creating a classic latency-vs-throughput tradeoff.
Question 3: What does a binding time constraint specify in software architecture?
- When a design decision can be changed or must be fixed (Correct answer)
- How long a system session can remain active
- The maximum time allowed to build a component
- The deadline for stakeholder review meetings
Correct answer: When a design decision can be changed or must be fixed
Binding time constraints define whether a design decision is fixed at compile time, deployment time, or can be changed at runtime.
Question 4: A regulatory constraint requires all data to remain within a specific country's borders. How does this most directly affect architectural decisions?
- It restricts deployment topology and cloud region selection (Correct answer)
- It mandates a specific programming language
- It requires synchronous communication between all services
- It forces use of a monolithic architecture
Correct answer: It restricts deployment topology and cloud region selection
Data residency regulations directly constrain where infrastructure can be hosted, limiting cloud regions and deployment topology choices.
Question 5: In CPSA terminology, what distinguishes an architectural goal from a functional requirement?
- Architectural goals address quality properties; functional requirements describe system behavior (Correct answer)
- Architectural goals are set by developers; functional requirements by managers
- Architectural goals apply only to databases; functional requirements to UI
- Architectural goals are optional; functional requirements are mandatory
Correct answer: Architectural goals address quality properties; functional requirements describe system behavior
Architectural goals focus on quality attributes like performance, security, and maintainability, while functional requirements describe what the system must do.
Question 6: Which stakeholder group most commonly introduces compliance-based architectural constraints?
- Legal and regulatory bodies (Correct answer)
- End users and customers
- Development team leads
- Database administrators
Correct answer: Legal and regulatory bodies
Legal and regulatory bodies impose compliance constraints such as GDPR, HIPAA, or SOX that architects must incorporate into system design.
Question 7: What is the primary purpose of documenting architectural constraints explicitly in architecture documentation?
- To prevent future architects from making decisions that violate non-negotiable boundaries (Correct answer)
- To satisfy project managers with detailed paperwork
- To provide a list of features for the product roadmap
- To describe the user interface design patterns
Correct answer: To prevent future architects from making decisions that violate non-negotiable boundaries
Explicit constraint documentation ensures that future architects and developers understand which boundaries cannot be crossed during evolution or maintenance.
Which technique best helps architects identify conflicting quality goals early in a project?