How do versioned artifacts support deployment rollbacks?

How do versioned artifacts support deployment rollbacks?

• A. They prevent rollbacks
• B. They allow rollback to known good versions
• C. They make rollbacks harder
• D. They have no impact on rollback

Answer: (B)

Versioned artifacts provide a reliable rollback mechanism because each build is stored as an immutable artifact with a unique version or build number. This means you can always retrieve the exact binary, container image, or package that was validated in production. When something goes wrong after deployment, you can roll back by redeploying a known good version, ensuring the runtime environment matches what was previously tested and approved. The versioning also preserves traceability—you can see exactly which version was deployed, when, and with which dependencies—so you can reproduce the fix or diagnose issues quickly. So the best choice is that versioned artifacts allow rollback to known good versions. They don’t prevent rollbacks or make them harder, and they have a direct impact by enabling precise, repeatable redeployments.

Versioned artifacts provide a reliable rollback mechanism because each build is stored as an immutable artifact with a unique version or build number. This means you can always retrieve the exact binary, container image, or package that was validated in production. When something goes wrong after deployment, you can roll back by redeploying a known good version, ensuring the runtime environment matches what was previously tested and approved. The versioning also preserves traceability—you can see exactly which version was deployed, when, and with which dependencies—so you can reproduce the fix or diagnose issues quickly.

So the best choice is that versioned artifacts allow rollback to known good versions. They don’t prevent rollbacks or make them harder, and they have a direct impact by enabling precise, repeatable redeployments.