← CCAR-P study guideNext domain
Domain 5 – Governance, Safety & Risk Management (14%)
5 lessons, each ending with a practice scenario (Pro)
Log in to save your progress.
- ✓5.1 — Guardrails, Safety Controls, and the Surface a Risk Belongs ToA guardrail is a control that stops a Claude system causing harm. Each risk belongs on the one surface that can hold it.Scenario: Pro
- ✓5.2 — Risks, Limitations, and the Failure Modes That Stay SilentA risk register is an architecture artefact. Every row has five fields: Mechanism — what goes wrong; Blast radius — how far, who bears it, whether undoable; Detection signal — what moves in the telemetry; Owning control — which 5.1 surface carries it; Residual, and who accepted it.Scenario: Pro
- ✓5.3 — Human-in-the-Loop Validation: Placement, Pattern, and ProofPlacement comes before pattern. The gate belongs where consequence is high and the action is hard to reverse.Scenario: Pro
- ✓5.4 — Regulatory Compliance as an Architecture ConstraintAn obligation becomes an architecture constraint when it changes what you build. Scope is the whole data path, not the application.Scenario: Pro
- ✓5.5 — Ethical AI: Bias, Fairness, and TransparencyBias is a gap in outcomes between groups. Dropping the protected attribute proves nothing — proxies carry the signal.Scenario: Pro
Domain recapQuick overview of all lessons
- Guardrails and safety controls (input/output filtering, refusal handling)
- Identify LLM-specific risks, limitations, and failure modes
- Human-in-the-loop validation patterns
- Regulatory compliance (GDPR, HIPAA, FedRAMP, etc.)
- Ethical considerations: bias, fairness, transparency, accountability
Domain 6: Stakeholder communication & lifecycle management →