During `terraform init`, you see: "Error: Failed to query available provider packages. Could not retrieve the list of available versions for provider hashicorp/aws: locked provider registry.terraform.io/hashicorp/aws 4.67.0 does not match configured version constraint >= 5.0.0." What is the root cause of this error?

The provider version in the lock file does not satisfy the version constraint in the configuration

The AWS credentials are invalid

The Terraform core version is too old

A Google Cloud provider configuration specifies `project = "my-project"` and `region = "us-central1"`. The apply fails with: "Error: google: could not find project my-project." What is the most likely cause of this provider configuration error?

The credentials file is missing

The provider version is incompatible

The project ID is incorrect or the project does not exist

A provider returns: "Error: creating storage account: storage.AccountsClient#Create: Failure sending request: StatusCode=403 -- Original Error: autorest/azure: Service returned an error. Status=403 Code="AuthorizationFailed" Message="The client 'user@example.com' with object id 'xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx' does not have authorization to perform action 'Microsoft.Storage/storageAccounts/write' over scope '/subscriptions/yyyyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyyyy/resourceGroups/rg-prod'." What actionable detail can be extracted from this error?

The user lacks write permission on the resource group

The resource group does not exist

The storage account name is already in use

You run `terraform init` and get: `Error: Unsupported Terraform Core version. This provider requires Terraform >= 1.2.0, but you are using 1.1.9.` Your team cannot upgrade Terraform core immediately. What is the best way to resolve this?

Pin the provider to an older version that supports Terraform 1.1.x.

Use `terraform state replace-provider` to change the provider.

Ignore the error and run `terraform apply` anyway.

Set the provider version constraint to `>= 1.2.0` to force the latest version.

A terraform apply fails with a provider error. Following a systematic troubleshooting workflow, what is the FIRST step you should take?

Reproduce the error with a minimal configuration

Modify the state file to remove the failing resource

Delete the entire infrastructure and recreate it

Upgrade all providers to the latest version

HashiCorp Certified:Terraform Authoring and Operations Professional

Domain 5Objective 4

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

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 6–10

6foundation · easy
During `terraform init`, you see: "Error: Failed to query available provider packages. Could not retrieve the list of available versions for provider hashicorp/aws: locked provider registry.terraform.io/hashicorp/aws 4.67.0 does not match configured version constraint >= 5.0.0." What is the root cause of this error?
Select an answer first
7foundation · easy
A Google Cloud provider configuration specifies `project = "my-project"` and `region = "us-central1"`. The apply fails with: "Error: google: could not find project my-project." What is the most likely cause of this provider configuration error?
Select an answer first
8foundation · easy
A provider returns: "Error: creating storage account: storage.AccountsClient#Create: Failure sending request: StatusCode=403 -- Original Error: autorest/azure: Service returned an error. Status=403 Code="AuthorizationFailed" Message="The client 'user@example.com' with object id 'xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx' does not have authorization to perform action 'Microsoft.Storage/storageAccounts/write' over scope '/subscriptions/yyyyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyyyy/resourceGroups/rg-prod'." What actionable detail can be extracted from this error?
Select an answer first
9application · medium
You run `terraform init` and get: `Error: Unsupported Terraform Core version. This provider requires Terraform >= 1.2.0, but you are using 1.1.9.` Your team cannot upgrade Terraform core immediately. What is the best way to resolve this?
Select an answer first
10foundation · easy
A terraform apply fails with a provider error. Following a systematic troubleshooting workflow, what is the FIRST step you should take?
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.

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

Questions 6–10

A Google Cloud provider configuration specifies `project = "my-project"` and `region = "us-central1"`. The apply fails with: "Error: google: could not find project my-project." What is the most likely cause of this provider configuration error?

You run `terraform init` and get: `Error: Unsupported Terraform Core version. This provider requires Terraform >= 1.2.0, but you are using 1.1.9.` Your team cannot upgrade Terraform core immediately. What is the best way to resolve this?

A terraform apply fails with a provider error. Following a systematic troubleshooting workflow, what is the FIRST step you should take?

Keep studying — Configure and use Terraform providers