Which practice improves audit trails by capturing exact deployment artifacts and times rather than making in-place changes?

• A. Frequent ad-hoc changes
• B. Versioned images and automated rollbacks
• C. Shadow IT usage
• D. Manual server reloads

Answer: (B)

Using versioned images and automated rollbacks creates an auditable deployment history by tying each release to a specific artifact and timestamp. When every deployment uses a unique image (with a digest or tag) stored in a registry, you capture exactly which artifact was deployed and when, providing a precise, verifiable record. Automated rollbacks maintain that history by reverting to a known good state without manual edits, preserving the trace of what changed rather than overwriting it with in-place updates. This makes it easy to reproduce deployments, verify compliance, and respond to incidents.

In contrast, frequent ad-hoc changes cloud the trail with undocumented tweaks; Shadow IT introduces unmanaged components that aren’t tracked; and manual server reloads may update systems without a clear link to the exact artifact or deployment time, weakening the auditability.