A team is automating Terraform in a CI/CD pipeline. They want to ensure that the pipeline does not require any interactive input, such as confirming the apply. Which command should they use for the apply step?

`terraform apply -auto-approve`

A company is moving from local Terraform state to remote state stored in an S3 bucket. They want to ensure that state is encrypted at rest and that access is restricted to the CI/CD pipeline and authorized engineers. What should they configure?

Store the state in a Git repository instead of S3.

Enable S3 server-side encryption and use IAM policies to restrict access to the bucket.

Use a public S3 bucket to allow easy access from the pipeline.

Use a local backend and rely on the CI/CD system's security.

An organization wants to enforce a policy that all AWS S3 buckets created by Terraform must have encryption enabled. They use Terraform Cloud and want to enforce this policy before any apply is executed. What should they implement?

Add a Sentinel policy that checks for `aws_s3_bucket` resources and verifies that encryption is configured.

Use `terraform plan -out=tfplan` and manually review the plan for encryption.

Add a `precondition` block in the Terraform configuration to check encryption.

Use `terraform validate` to check the configuration for encryption settings.

In an automated Terraform workflow, how can you programmatically review the changes that `terraform plan` would make without applying them?

By reading the output of `terraform plan` and storing it as an artifact

By running `terraform validate` to check for errors

By running `terraform apply` with the `-dry-run` flag

By using `terraform show` on the state file

In an automated Terraform pipeline, what is a common strategy to handle transient errors, such as network timeouts or provider throttling?

Immediately roll back all changes

Delete the state file and start over

Retry the failed step with exponential backoff

Ignore the error and continue the pipeline

HashiCorp Certified:Terraform Authoring and Operations Professional

Domain 3Objective 3

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

Part of the Develop collaborative Terraform workflows domain, which makes up ~16% of our current practice bank. HashiCorp does not publish an official question count, but from its 240-minute exam (~95–160 total, ~15–26 in this domain), expect 4–7 from this objective — we provide 29 practice questions to prepare you well beyond it. (estimate)

29questions here

6free pages

8concepts

Questions 1–5

1application · medium
A team is automating Terraform in a CI/CD pipeline. They want to ensure that the pipeline does not require any interactive input, such as confirming the apply. Which command should they use for the apply step?
Select an answer first
2application · medium
A company is moving from local Terraform state to remote state stored in an S3 bucket. They want to ensure that state is encrypted at rest and that access is restricted to the CI/CD pipeline and authorized engineers. What should they configure?
Select an answer first
3application · medium
An organization wants to enforce a policy that all AWS S3 buckets created by Terraform must have encryption enabled. They use Terraform Cloud and want to enforce this policy before any apply is executed. What should they implement?
Select an answer first
4foundation · easy
In an automated Terraform workflow, how can you programmatically review the changes that `terraform plan` would make without applying them?
Select an answer first
5foundation · easy
In an automated Terraform pipeline, what is a common strategy to handle transient errors, such as network timeouts or provider throttling?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to TERRAFORM-AUTHORING-AND-OPERATIONS-PROFESSIONAL

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by HashiCorp. “TERRAFORM-AUTHORING-AND-OPERATIONS-PROFESSIONAL” is a trademark of its owner, used for identification only.