In ECMS, attaching documentation to revision levels primarily supports what objective?

• A. Traceability
• B. Audit trails
• C. Compliance reporting
• D. Security hardening

Answer: (D)

Attaching documentation to revision levels primarily creates a traceable history of changes. By associating the rationale, requirements, tests, and approvals with each revision, you can see exactly what was changed, why it was changed, who authorized it, and how it fits with other items over time. This makes it possible to reconstruct the evolution of the configuration and understand the decision path behind every revision, which is the core of traceability. In practice, this traceability also supports audit trails and compliance reporting because you have a documented record of actions and justifications, but the fundamental goal is to be able to trace the lineage and context of each revision. Security hardening isn’t the primary objective of attaching documentation to revisions, as the practice is about documenting change history rather than directly enforcing security controls.