Terraform-Associate-004 Questions Bank

Rationale for Correct Answers:

C. terraform.tfvars securely managed: Acceptable if distributed securely outside version control.

D. HCP Terraform/Terraform Cloud sensitive variables: Official best practice for team-based workflows.

E. Vault: HashiCorp Vault is designed for secret management and integrates well with Terraform.

Analysis of Incorrect Options:

A: Storing plaintext secrets on shared drives is insecure.

B: Checking secrets into version control is a major security risk.

Key Concept:

Sensitive values should be managed securely in Vault, HCP Terraform, or securely shared .tfvars files — never in plaintext or version control.

Rationale for Correct Answer: The pessimistic constraint operator ~ > allows updates that do not change the leftmost specified digits beyond what’s declared. With ~ > 11.0, Terraform allows any version that is > = 11.0 but < 12.0 (i.e., any 11.x release). This pins to the major version while allowing minor/patch updates.

Analysis of Incorrect Options (Distractors):

A: Incorrect—this excludes exactly 11.0 and doesn’t express the upper bound that ~ > imposes.

B: Incorrect—missing the upper bound; ~ > always implies an upper limit.

D: Incorrect— > = 11.0.0 and < 11.1.0 corresponds to ~ > 11.0.0, not ~ > 11.0.

Key Concept: Module version constraints using the pessimistic (~ > ) operator.

Module version is optional to reference a module on the Terraform Module Registry. If you omit the version constraint, Terraform will automatically use the latest available version of the module

Rationale for Correct Answer:By default, terraform fmt modifies files in place to match Terraform’s canonical formatting. The -check flag is required to only check formatting without making changes.

Analysis of Incorrect Options (Distractors):

A: Incorrect because formatting changes are applied automatically by default.

Key Concept:terraform fmt enforces consistent formatting by rewriting files unless instructed otherwise.