Documentation is being trimmed from the current plan to speed up delivery. Why is removing documentation to move faster a poor trade-off in AI governance?
Select an answer to reveal the explanation.
Short Explanation
Cutting documentation doesn't remove the requirement; it just removes your proof that you met it. When governance asks for evidence, you need records.
Full Explanation
Documentation is the record that connects a governance activity to the specific law, standard, or policy requirement it satisfies; without it, there is nothing to show a reviewer or auditor that the requirement was actually addressed. The claim that documentation has no effect on delivery speed either way, so removing it achieves nothing, is incorrect because the trade-off described, faster delivery for less documentation, is a real one, even if it is a poor one to make. The claim that documentation is only useful for training new engineers, not for governance purposes, is incorrect because documentation serves compliance and audit purposes well beyond onboarding. The claim that removing documentation is acceptable as long as the underlying code is well commented is incorrect because code comments describe implementation, not whether a legal or policy requirement was met. For the exam, treat documentation as required evidence, not as optional overhead to cut for speed.