To automatically enforce Terraform code conventions in a CI/CD workflow, which command should be run?

To automatically enforce Terraform code conventions in a CI/CD workflow, which command should be run?

• A. Terraform fmt during the code linting phase of the CI/CD process
• B. Manually apply two spaces indentation and align equal signs in every Terraform file
• C. Terraform validate prior to executing plan or apply
• D. Terraform plan or apply

Answer: (A)

Enforcing consistent code style automatically in CI/CD is about applying a formatter to the Terraform configurations. Terraform fmt is the tool that rewrites files into a canonical, standardized format, handling indentation, spacing, and alignment so all configs look the same across the project. In a CI/CD pipeline, you place this in the linting phase so any deviations are caught automatically—often by using a check mode so the build fails if formatting is off, which enforces the convention without requiring manual fixes. The other options don’t address formatting: manual edits are not automated, validation checks syntax but not style, and plan/apply are about execution, not style enforcement.

Enforcing consistent code style automatically in CI/CD is about applying a formatter to the Terraform configurations. Terraform fmt is the tool that rewrites files into a canonical, standardized format, handling indentation, spacing, and alignment so all configs look the same across the project. In a CI/CD pipeline, you place this in the linting phase so any deviations are caught automatically—often by using a check mode so the build fails if formatting is off, which enforces the convention without requiring manual fixes. The other options don’t address formatting: manual edits are not automated, validation checks syntax but not style, and plan/apply are about execution, not style enforcement.