The correct answer is Keeping documents current and auditable while preserving prior revisions.

Version control creates a recorded history of changes so auditors and teams can see who made each change and when. It lets teams update governance and policy files while preserving earlier revisions for comparison and for rollback when needed. This combination of current documents and an auditable revision history is the primary reason organizations apply version control to governance documents.

Cloud Storage lifecycle rules govern retention and automatic deletion of stored objects and they do not by themselves provide a human readable edit history or an audit trail of document edits. Lifecycle rules can work with versioning but they are not the core purpose of version control.

Allowing all staff to edit the live copy without recording revisions is the opposite of version control because it removes accountability and prevents restoring prior states. Version control requires recording revisions rather than discarding them.

Restricting document access solely to senior executives is an access control decision and not the primary function of version control. Access restrictions limit who can view or change files but they do not create the sequential, auditable history that version control provides.

Full AWS Practitioner Certification Question