A team uses a custom Terraform provider that talks to an internal API. After migrating the API to a new domain, all `terraform plan` runs fail with `Error: Failed to reach API endpoint`. The provider configuration still points to the old domain. What should you do first?

Enable TF_LOG=TRACE to see the exact URL being requested.

Update the provider configuration to use the new API endpoint.

Check the provider version and update it.

Run `terraform init` to reinitialize the provider.

A team uses the AWS provider. `terraform apply` fails with `Error: Throttling: Rate exceeded` on an EC2 instance creation. The team has many resources in the configuration. What is the best approach to resolve this?

Implement retry logic in the provider configuration.

Use `-parallelism=1` to reduce concurrent API requests.

Reduce the number of resources in the configuration.

Switch to a different AWS region.

A Terraform configuration uses the AWS provider with `region = "us-east-1"` in the provider block. The apply fails with: "Error: configuring Terraform AWS Provider: no valid credential sources for Terraform AWS Provider found." What is the most likely cause of this provider configuration error?

Missing or invalid AWS credentials

The resource type is not supported

A team has a configuration that works in the staging environment but fails in production with an authentication error. The provider configuration uses environment variables for credentials. What is the most likely cause?

The production state file is corrupted.

The production Terraform version is different.

The production provider version is different.

The production environment has different environment variables set.

HashiCorp Certified:Terraform Authoring and Operations Professional

Domain 5Objective 4

5d TERRAFORM-AUTHORING-AND-OPERATIONS-PROFESSIONAL Practice Questions (Page 5)

Part of the Configure and use Terraform providers 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 28 practice questions to prepare you well beyond it. (estimate)

28questions here

6free pages

6concepts

Questions 21–25

21application · medium
A team uses a custom Terraform provider that talks to an internal API. After migrating the API to a new domain, all `terraform plan` runs fail with `Error: Failed to reach API endpoint`. The provider configuration still points to the old domain. What should you do first?
Select an answer first
22foundation · easy
A Terraform apply fails with the error: "Error: error creating instance: InvalidAuthenticationTokenTenant: The access token is invalid, expired, or does not have the correct permissions." Which category of provider error does this represent?
Select an answer first
23expert · hard
A team uses the AWS provider. `terraform apply` fails with `Error: Throttling: Rate exceeded` on an EC2 instance creation. The team has many resources in the configuration. What is the best approach to resolve this?
Select an answer first
24foundation · easy
A Terraform configuration uses the AWS provider with `region = "us-east-1"` in the provider block. The apply fails with: "Error: configuring Terraform AWS Provider: no valid credential sources for Terraform AWS Provider found." What is the most likely cause of this provider configuration error?
Select an answer first
25expert · hard
A team has a configuration that works in the staging environment but fails in production with an authentication error. The provider configuration uses environment variables for credentials. What is the most likely cause?
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.