Your team keeps provisioning environments by clicking through the cloud console, and configurations drift between staging and production. Which IaC benefit most directly fixes this?
- AConsole click-ops simply becomes faster with practice, so environment drift resolves itself over time.
- BInfrastructure defined in code removes any need to store credentials.
- CDefining infrastructure as versioned code makes environments repeatable and consistent from the same source.
- DWriting code guarantees the infrastructure can never change after creation.
Repeatability and consistency come from provisioning every environment from the same versioned configuration, which removes manual-step drift. Click-ops causes drift, IaC does not remove credential needs, and it manages change rather than freezing it.
Why each option is right or wrong.
- C (correct). One reviewed configuration provisions each environment identically, eliminating drift from manual steps.
- A. Manual click-ops is the cause of drift, not a fix for it.
- B. IaC still needs provider credentials; that is unrelated to environment consistency.
- D. Infrastructure still changes; IaC manages change consistently rather than freezing it.
Reference: Terraform Associate 004 objective 1b - describe the advantages of IaC patterns