If you add a new resource using the same provider and do not update the version constraint, and a lock file exists, which version will Terraform use?

• A. The latest version of the provider for the new resource and the version in the lock file to manage existing resources
• B. The version recorded in your lock file
• C. The version recorded in your state file
• D. The latest version of the provider available at provisioning time

Answer: (B)

Terraform pins the exact provider versions with a lock file to ensure reproducible runs. When you add a new resource with the same provider and you don’t change the version constraint, Terraform will install and use the exact version recorded in the lock file. That lock file reflects the version that was resolved and installed during the last terraform init, so it governs all subsequent operations for consistency across resources, not the latest available version.

The state file tracks resources and their attributes, not which provider version to use for new resources. If you want to upgrade to a newer provider version, you’d need to update the constraint and refresh the lock file (for example, with an init -upgrade).