Terraform Fundamentals Questions

What is the primary purpose of the .terraform.lock.hcl file?

Which dependency selection does Terraform record in .terraform.lock.hcl?

What information does a provider requirement in required_providers contain?

Why should a team commit .terraform.lock.hcl to version control?

Which provider address is associated with the built-in provider used for terraform_remote_state?

A module declares required_providers with a local name and version constraint but omits source. Which provider source does Terraform imply?

Which provider version strategy follows HashiCorp's documented best practice?

If a configuration already has a dependency lock file committed, how do Terraform CLI and HCP Terraform normally select provider versions?

A root module must use two different providers that both have the type name http. What naming approach does HashiCorp recommend in required_providers?

An organization distributes an internal provider from a filesystem mirror instead of a public registry. What source address can its modules use?

Why is using a provider's preferred local name such as aws usually recommended?

A reusable module will be shared across many root modules. What provider version strategy follows official best practice?

Which statement about a provider source address is correct?

Your root module must use two different providers that both have the type name http. What naming pattern does HashiCorp recommend?

A team first installs a provider from a filesystem mirror and then commits the lock file. Why might a coworker on another platform still have trouble ...