Weight: 14%. About 9 of the 63 exam questions.
This domain tests how an architect works with people across the life of a system.
| Objective | What it tests |
|---|---|
| 6.1 Discovery and requirements | Stakeholders, baselines, data, constraints, success criteria |
| 6.2 Communicating decisions and trade-offs | Business framing, decision records, honest risk |
| 6.3 Feedback loops and expectations | SLAs, exit criteria, change control, reporting |
| 6.4 Documentation and implementation guidance | Runbooks, data flows, contracts, reference implementations |
| 6.5 Lifecycle phases | Discovery → design → handoff → monitoring → iteration (and retirement) |
Mental model
- Make expectations explicit and measurable early; revisit them with evidence.
- Tailor communication to what each audience decides.
- Hand over a system that others can run, measure and change.
Exam heuristics
- The right answer is rarely "promise more" or "avoid the topic".
- Look for measurable criteria, named owners, recorded decisions and evidence-based gates.
- Probabilistic systems need realistic quality targets plus review and escalation paths.