It evidences compliance and supports risk management: Which rationale most accurately captures the governance

Design-and-build documentation exists to evidence compliance and support risk management through a traceable, reviewable record of decisions and controls.

The question

Preparing for AIGP? Take the free 5-min readiness quiz →

1. It exists mainly to satisfy investors, so a high-level summary of the product's features and benefits will suffice for the record.

   Plausible since stakeholders read documentation, but a marketing summary omits the traceable design record governance needs.
2. It replaces the need for testing, because a well-written design record demonstrates that the system will behave exactly as intended.

   Plausible as documentation adds assurance, but records describe intent and cannot substitute for empirical testing.
3. It evidences compliance and supports risk management by making design choices, trade-offs, and controls traceable and reviewable later. ✓

   Correct: documentation exists to demonstrate compliance and enable risk management by preserving a traceable record of decisions and controls.
4. It is required only after an incident occurs, so the documentation can simply be reconstructed retrospectively from the code commit history.

   Plausible because incidents prompt reviews, but contemporaneous records, not reconstructions, provide reliable evidence.

How to remember it

Design-and-build documentation exists to evidence compliance and support risk management through a traceable, reviewable record of decisions and controls.

More Understanding How to Govern AI Development questions

• Prioritize eliminating or avoiding the risk at its source: What does the mitigation hierarchy direct them to →
• Confirm the lawful rights to reuse the data for this new: Which action best satisfies data-governance →
• Recording data lineage and provenance: Which practice would have prevented this gap? →
• All 426 Understanding How to Govern AI Development questions →