Which practice is enabled by Infrastructure as Code in terms of reproducibility?

Which practice is enabled by Infrastructure as Code in terms of reproducibility?

• A. Manual configuration through the cloud console
• B. Maintaining infrastructure state as code for reproducible deployments
• C. Prohibiting version control
• D. Running infrastructure changes without approvals

Answer: (B)

Reproducible deployments come from treating infrastructure as code, where the exact desired state of the environment is captured in files that can be stored, versioned, and applied consistently. By describing resources, dependencies, and configurations in code, you can re-create the same environment anywhere at any time—every resource ends up in the same state, reliably and deterministically. This approach also supports drift detection and safe rollbacks, since the code defines the intended configuration. In contrast, configuring resources manually through a cloud console is error-prone and hard to reproduce exactly; lacking version control prevents sharing and reverting changes; and executing changes without approvals undermines governance and reliability.

Reproducible deployments come from treating infrastructure as code, where the exact desired state of the environment is captured in files that can be stored, versioned, and applied consistently. By describing resources, dependencies, and configurations in code, you can re-create the same environment anywhere at any time—every resource ends up in the same state, reliably and deterministically. This approach also supports drift detection and safe rollbacks, since the code defines the intended configuration. In contrast, configuring resources manually through a cloud console is error-prone and hard to reproduce exactly; lacking version control prevents sharing and reverting changes; and executing changes without approvals undermines governance and reliability.