When initializing a configuration that uses a remote backend, what does terraform init do by default?

It only initializes the backend if the -reconfigure flag is provided.

It requires the -backend-config flag to be specified for any remote backend.

It prompts for confirmation before copying any existing state to the remote backend.

It automatically deletes the local state file to avoid conflicts.

A developer is working on a Terraform configuration that uses modules from a public registry. They run `terraform init` and it succeeds. Later, they add a new module to the configuration. What should they do?

Run `terraform validate` to check the module syntax.

Run `terraform plan` and it will automatically download the new module.

Run `terraform get` to download the new module.

Run `terraform init` again to download the new module.

During terraform init, where does Terraform download provider plugins from by default?

The provider's official website

The local plugin cache directory

During terraform init, a warning is displayed about a provider version constraint. What does this warning typically indicate?

The state file is corrupted and needs to be recreated.

The backend configuration is invalid and needs to be corrected.

The provider version constraint may be incompatible with the installed version, but initialization can still proceed.

The provider installation failed and must be retried.

A team has a Terraform configuration that requires a specific version of the AWS provider. They have a `required_providers` block that specifies `version = "~> 4.0"`. When a new team member runs `terraform init`, Terraform installs the latest 4.x version. The team wants to ensure all team members use the exact same provider version. What should they do?

Change the version constraint to `version = "= 4.0.0"`.

Run `terraform init -upgrade` to ensure the latest version is installed.

Add a `terraform.lock.hcl` file to the repository and commit it.

Tell each team member to manually install the provider version.

HashiCorp Certified:Terraform Authoring and Operations Professional

Domain 1Objective 1

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

Part of the Manage resource lifecycle domain, which makes up ~18% of our current practice bank. HashiCorp does not publish an official question count, but from its 240-minute exam (~95–160 total, ~17–29 in this domain), expect 3–6 from this objective — we provide 17 practice questions to prepare you well beyond it. (estimate)

17questions here

4free pages

5concepts

Questions 11–15

11foundation · easy
When initializing a configuration that uses a remote backend, what does terraform init do by default?
Select an answer first
12application · easy
A developer is working on a Terraform configuration that uses modules from a public registry. They run `terraform init` and it succeeds. Later, they add a new module to the configuration. What should they do?
Select an answer first
13foundation · easy
During terraform init, where does Terraform download provider plugins from by default?
Select an answer first
14foundation · easy
During terraform init, a warning is displayed about a provider version constraint. What does this warning typically indicate?
Select an answer first
15application · medium
A team has a Terraform configuration that requires a specific version of the AWS provider. They have a `required_providers` block that specifies `version = "~> 4.0"`. When a new team member runs `terraform init`, Terraform installs the latest 4.x version. The team wants to ensure all team members use the exact same provider version. What should they do?
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.