You add a new resource to an existing Terraform configuration, but do not update the version constraint in the configuration. The existing and new resources use the same provider. The working contains a .terraform.lock, hc1 file.
How will Terraform choose which version of the provider to use?

• A.Terraform will use the version recorded in your lock file
• B.Terraform will use the latest version of the provider for the new resource and the version recorded in the lock file to manage existing resources
• C.Terraform will check your state file to determine the provider version to use
• D.Terraform will use the latest version of the provider available at the time you provision your new resource

Comment: *

Name: *

Email: *

Verification: *

What is the purpose of the terraform.lock.hcl file in Terraform?

• A.There is no such file.
• B.Storing references to workspaces, which are locked.
• C.Preventing Terraform runs from occurring.
• D.Tracking specific provider dependencies.

Comment: *

Name: *

Email: *

Verification: *

What does terraform import do?

• A.Imports existing resources into the state file
• B.Imports all infrastructure from a given cloud provider
• C.Imports a new Terraform module
• D.Imports clean copies of tainted resources
• E.None of the above

Comment: *

Name: *

Email: *

Verification: *

Outside of the required_providers block, Terraform configurations always refer to providers by their local names.

• A.True
• B.False

Comment: *

Name: *

Email: *

Verification: *

Before you can use a new backend or HCP Terraform/Terraform Cloud integration, you must first execute terraform init.

• A.True
• B.False

Comment: *

Name: *

Email: *

Verification: *