nerdexam
HashiCorp

TA-002-P · Question #178

Why is it a good idea to declare the required version of a provider in a Terraform configuration file? 1. terraform 2. { 3. required_providers 4. { 5. aws = "~> 1.0" 6. } 7. }

The correct answer is C. Providers are released on a separate schedule from Terraform itself; therefore a newer. Declaring a required provider version is important because providers are released independently from Terraform itself, and pinning a version ensures your configuration uses the provider release with the exact features and fixes it needs.

Read, generate, and modify configuration

Question

Why is it a good idea to declare the required version of a provider in a Terraform configuration file? 1. terraform 2. { 3. required_providers 4. { 5. aws = "~> 1.0" 6. } 7. }

Options

  • ATo remove older versions of the provider.
  • BTo ensure that the provider version matches the version of Terraform you are using.
  • CProviders are released on a separate schedule from Terraform itself; therefore a newer
  • DTo match the version number of your application being deployed via Terraform.

How the community answered

(29 responses)
  • A
    7% (2)
  • B
    3% (1)
  • C
    90% (26)

Why each option

Declaring a required provider version is important because providers are released independently from Terraform itself, and pinning a version ensures your configuration uses the provider release with the exact features and fixes it needs.

ATo remove older versions of the provider.

Declaring required_providers constrains which version Terraform selects for use; it does not remove or uninstall older versions from the system.

BTo ensure that the provider version matches the version of Terraform you are using.

Terraform core and provider versions are managed independently; required_providers version constraints do not enforce matching the Terraform binary version.

CProviders are released on a separate schedule from Terraform itself; therefore a newerCorrect

Providers have their own release cadence separate from the Terraform CLI; a newer provider version may introduce breaking changes, new resources, or required bug fixes, so declaring a version constraint in required_providers ensures deterministic behavior regardless of which provider version happens to be installed locally.

DTo match the version number of your application being deployed via Terraform.

Provider version constraints relate to the provider's own API compatibility with your configuration and have no connection to the version of the application being deployed.

Concept tested: Terraform provider version constraints and independent release schedules

Source: https://developer.hashicorp.com/terraform/language/providers/requirements

Topics

#Provider Versioning#Required Providers#Dependency Management#Configuration Best Practices

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full TA-002-P Practice