You see the error: `Error: reading Azure Resource Group: resources.GroupClient#Get: Failure responding to request: StatusCode=404 -- Original Error: autorest/azure: Service returned an error. Status=404 Code=ResourceGroupNotFound`. The resource group was created by another team and you have the correct name. What is the most likely cause?

The resource group is in a different Azure subscription than configured in the provider.

The provider version is incompatible with the Azure API.

The provider credentials lack permission to read the resource group.

The resource group name is case-sensitive and misspelled.

A team uses the Google Cloud provider. After upgrading from version 4.0 to 5.0, `terraform plan` fails with `Error: Invalid provider configuration: Provider configured with a deprecated field`. The configuration uses `credentials` field which was valid in 4.0. What is the best approach?

Remove the `credentials` field and rely on environment variables.

Revert to provider version 4.0.

Set `TF_LOG=TRACE` to see the exact deprecation message.

Use `terraform state replace-provider` to update the provider in state.

A team uses a custom provider that connects to an internal API. The API recently moved from HTTP to HTTPS with a self-signed certificate. `terraform apply` now fails with `Error: x509: certificate signed by unknown authority`. What is the best way to resolve this?

Add the self-signed certificate to the system trust store.

Use `TF_LOG=TRACE` to see the certificate details.

Configure the provider to skip TLS verification.

A developer runs `terraform plan` and receives an error: `Error: Failed to query available provider packages. Could not retrieve the list of available versions for provider hashicorp/aws: 403 Forbidden`. The developer has valid AWS credentials and the AWS provider is pinned to a version that exists. What is the most likely cause of this error?

The AWS credentials are invalid or expired.

The AWS region is misconfigured in the provider block.

The Terraform CLI is configured to use a private registry that requires authentication.

The provider version constraint is incompatible with the Terraform core version.

During a systematic troubleshooting workflow for a provider error, you have reproduced the issue with a minimal configuration. What is the NEXT logical step?

Change the provider version to the latest release

Run terraform destroy to clean up all resources

Check the state file to ensure it matches the actual infrastructure

Immediately contact the cloud provider support team

HashiCorp Certified:Terraform Authoring and Operations Professional

Domain 5Objective 4

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

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 11–15

11expert · hard
You see the error: `Error: reading Azure Resource Group: resources.GroupClient#Get: Failure responding to request: StatusCode=404 -- Original Error: autorest/azure: Service returned an error. Status=404 Code=ResourceGroupNotFound`. The resource group was created by another team and you have the correct name. What is the most likely cause?
Select an answer first
12expert · hard
A team uses the Google Cloud provider. After upgrading from version 4.0 to 5.0, `terraform plan` fails with `Error: Invalid provider configuration: Provider configured with a deprecated field`. The configuration uses `credentials` field which was valid in 4.0. What is the best approach?
Select an answer first
13expert · hard
A team uses a custom provider that connects to an internal API. The API recently moved from HTTP to HTTPS with a self-signed certificate. `terraform apply` now fails with `Error: x509: certificate signed by unknown authority`. What is the best way to resolve this?
Select an answer first
14application · medium
A developer runs `terraform plan` and receives an error: `Error: Failed to query available provider packages. Could not retrieve the list of available versions for provider hashicorp/aws: 403 Forbidden`. The developer has valid AWS credentials and the AWS provider is pinned to a version that exists. What is the most likely cause of this error?
Select an answer first
15foundation · easy
During a systematic troubleshooting workflow for a provider error, you have reproduced the issue with a minimal configuration. What is the NEXT logical step?
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 3)

Questions 11–15

A team uses the Google Cloud provider. After upgrading from version 4.0 to 5.0, `terraform plan` fails with `Error: Invalid provider configuration: Provider configured with a deprecated field`. The configuration uses `credentials` field which was valid in 4.0. What is the best approach?

A team uses a custom provider that connects to an internal API. The API recently moved from HTTP to HTTPS with a self-signed certificate. `terraform apply` now fails with `Error: x509: certificate signed by unknown authority`. What is the best way to resolve this?

During a systematic troubleshooting workflow for a provider error, you have reproduced the issue with a minimal configuration. What is the NEXT logical step?

Keep studying — Configure and use Terraform providers