3c TERRAFORM-AUTHORING-AND-OPERATIONS-PROFESSIONAL Practice Questions (Page 4)

Questions 16–20

1. 16foundation · easy

   Which CI/CD pipeline stage is most appropriate for running `terraform plan` to check for infrastructure changes without applying them?

   • ATest stage
   • BA dedicated infrastructure stage before apply
   • CDeployment stage
   • DBuild stage
   Reveal Solution Discussion Select an answer first
2. 17foundation · easy

   Which Terraform command is used to check the syntax and internal consistency of configuration files without accessing remote services?

   • Aterraform apply
   • Bterraform plan
   • Cterraform validate
   • Dterraform fmt
   Reveal Solution Discussion Select an answer first
4. 18foundation · easy

   What is the main benefit of using remote state storage over local state storage in automated Terraform workflows?

   • AIt speeds up Terraform operations by caching state locally
   • BIt eliminates the need for state locking
   • CIt allows multiple team members and CI/CD systems to access the same state
   • DIt automatically encrypts all sensitive data in the state
   Reveal Solution Discussion Select an answer first
5. 19application · medium

   A DevOps engineer is designing a CI/CD pipeline for Terraform that must automatically apply changes to a production environment after a plan is approved. The pipeline should fail safely if the plan contains destructive changes (e.g., resource deletion). Which approach best meets this requirement?

   • ARun `terraform plan -out=tfplan` and then `terraform apply tfplan` only if the plan output does not contain ' - destroy'.
   • BRun `terraform apply -auto-approve` directly in the pipeline without a separate plan step.
   • CRun `terraform apply -target=...` to apply only specific resources.
   • DUse `terraform plan -destroy` to generate a plan and then apply it.
   Reveal Solution Discussion Select an answer first
6. 20application · medium

   A platform team runs Terraform in a CI/CD pipeline to manage shared AWS infrastructure. The pipeline executes `terraform init`, `terraform plan`, and `terraform apply` in separate jobs. Occasionally, two pipeline runs for different feature branches execute concurrently and both attempt to modify the same state. The team wants to prevent concurrent modifications without changing the pipeline's job structure. What should they do?

   • ASet the `TF_DATA_DIR` environment variable to a unique path per pipeline run.
   • BAdd a `-lock=false` flag to the `terraform apply` command in the pipeline.
   • CUse `terraform workspace select` to switch to a separate workspace for each branch.
   • DConfigure the backend to use an S3 bucket with DynamoDB table for state locking.
   Reveal Solution Discussion Select an answer first