Software architecture practice assessment. Applied

Practice assessment: scenario judgement for architecture decisions. Not timed.

12 questions

Why record architectural decisions (ADRs)?

adrs

Choosing between consistency and availability is defensible when:

tradeoffs

Scenario: A component has three unrelated reasons to change. What does that suggest?

boundaries

Scenario: You adopt event-driven architecture. What risk must be made explicit?

operations

An ADR should include a review trigger because:

adrs

Scenario: A system is 'reliable' on paper but incidents are frequent. What evidence is missing?

operations

Scenario: Latency is acceptable, but cost is exploding. What is the correct architecture move?

tradeoffs

Scenario: A decision is controversial. What makes the ADR most useful later?

adrs

Scenario: You introduce retries to reduce errors. What risk must be addressed?

operations

Scenario: APIs are stable but teams still break each other. What is missing?

boundaries

Scenario: You want faster delivery but incidents increase. What is the most defensible response?

tradeoffs

Scenario: You can’t debug a distributed issue. What capability is missing?

operations

Add CPD reflection (optional)

One short paragraph makes your CPD evidence much stronger.

Draft one ADR for a decision you have seen at work. Include constraints, trade-offs, and a review trigger.

Quick feedback