A team is designing a custom provider that must support both Terraform CLI and Terraform Cloud. The provider uses a feature that is only available in the Plugin Framework. The team is concerned about compatibility with Terraform Cloud's execution environment. What should they verify?

Terraform Cloud supports providers built with the Plugin Framework as long as they are published to a private registry.

The Plugin Framework is incompatible with Terraform Cloud's remote execution.

The provider must be recompiled specifically for Terraform Cloud.

Terraform Cloud only supports providers built with SDK v2.

How does Terraform core interact with provider plugins during an operation such as plan or apply?

It sends HTTP requests to a remote provider API endpoint.

It loads the plugin into the same process and calls its functions directly.

It executes the plugin as a container and uses Docker's API.

It launches the plugin as a separate process and communicates over a local RPC protocol.

A developer is working on a Terraform configuration that uses a provider from the public registry. They want to ensure that the exact same provider version is used across all team members and CI runs. What should they do?

Set the provider version in the provider block using the version argument.

Add a version constraint in the required_providers block and commit the .terraform.lock.hcl file.

Manually download the provider binary and place it in the plugin cache on every machine.

Use the terraform providers pin command to lock the provider version.

A team manages Terraform state from a central CI runner. They need to use a custom in-house provider that is not published to the public registry. The provider binary is built for linux_amd64 and stored in an internal artifact store. What is the correct way to make this provider available to Terraform on the CI runner?

Place the binary directly in the current working directory and reference it with source = "./example" in the required_providers block.

Set the environment variable TF_PROVIDER_PATH to the artifact store URL and run terraform init.

Place the binary in ~/.terraform.d/plugins/registry.example.com/examplecorp/example/1.0.0/linux_amd64/ and add a required_providers block with source = "registry.example.com/examplecorp/example".

Copy the binary to /usr/local/bin/terraform-provider-example and run terraform init.

HashiCorp Certified:Terraform Authoring and Operations Professional

Domain 5Objective 1

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

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 24 practice questions to prepare you well beyond it. (estimate)

24questions here

5free pages

4concepts

Questions 16–20

16expert · hard
A team is designing a custom provider that must support both Terraform CLI and Terraform Cloud. The provider uses a feature that is only available in the Plugin Framework. The team is concerned about compatibility with Terraform Cloud's execution environment. What should they verify?
Select an answer first
17foundation · easy
How does Terraform core interact with provider plugins during an operation such as plan or apply?
Select an answer first
18foundation · easy
What protocol does Terraform core use to communicate with provider plugins?
Select an answer first
19application · medium
A developer is working on a Terraform configuration that uses a provider from the public registry. They want to ensure that the exact same provider version is used across all team members and CI runs. What should they do?
Select an answer first
20application · medium
A team manages Terraform state from a central CI runner. They need to use a custom in-house provider that is not published to the public registry. The provider binary is built for linux_amd64 and stored in an internal artifact store. What is the correct way to make this provider available to Terraform on the CI runner?
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.

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

Questions 16–20

A team is designing a custom provider that must support both Terraform CLI and Terraform Cloud. The provider uses a feature that is only available in the Plugin Framework. The team is concerned about compatibility with Terraform Cloud's execution environment. What should they verify?

How does Terraform core interact with provider plugins during an operation such as plan or apply?

What protocol does Terraform core use to communicate with provider plugins?

A developer is working on a Terraform configuration that uses a provider from the public registry. They want to ensure that the exact same provider version is used across all team members and CI runs. What should they do?

Keep studying — Configure and use Terraform providers