AWS provider Provider Management — 10 Questions

Question 1

Which attributes can be configured within a provider block? (Select THREE)

Accepted Answer

shared_credentials_file. Region, profile, and credentials (like shared_credentials_file) are all valid provider arguments.

Answer

source

Answer

version

Question 2

What is the purpose of the 'terraform providers lock' command?

Accepted Answer

To secure the provider versions and checksums.. It updates the .terraform.lock.hcl file to include all necessary provider checksums for the current configuration.

Answer

To encrypt the state file.

Answer

To prevent others from running init.

Answer

To download all providers.

Question 3

You are creating a custom provider. What is the standard language used to write Terraform providers?

Accepted Answer

Go. Terraform providers are written in Go (Golang) using the Terraform Plugin SDK.

Answer

Python

Answer

Ruby

Answer

HCL

Question 4

You need to manage resources in two different AWS regions using the same provider configuration. How do you achieve this?

Accepted Answer

Use an alias in the provider block and reference it in the resource using the provider meta-argument.. Using alias in the provider block allows you to define multiple configurations for the same provider.

Answer

Define the region twice in a single provider block.

Answer

Define two separate aws providers in the same file without aliases.

Answer

Create two separate Terraform projects.

Question 5

If you want to use a provider that is not published in the Terraform Registry, how do you install it?

Accepted Answer

Use a filesystem mirror in the .terraformrc file.. Local provider mirrors can be configured by placing the binary in specific directory structures and using a CLI configuration file.

Answer

You cannot use private providers.

Answer

Rename the file to provider.tf.

Answer

Copy it to the root of the project.

Question 6

A team wants to ensure their Terraform configuration uses a specific major version of the AWS provider to prevent breaking changes. Which block should they use?

Accepted Answer

terraform { required_providers { aws = { source = "hashicorp/aws", version = "~> 4.0" } } }. The required_providers block within the terraform block is the standard way to constrain provider versions.

Answer

provider "aws" { version = "~> 4.0" }

Answer

terraform { version = "~> 4.0" }

Answer

provider_version = "4.0"

Question 7

Where are providers physically stored by default when running 'terraform init'?

Accepted Answer

.terraform/providers/. Terraform downloads providers into the .terraform/providers directory within your project working directory.

Answer

The root module directory

Answer

~/.terraformrc

Answer

/usr/local/bin/terraform

Question 8

Which meta-argument is used to explicitly associate a resource with a non-default provider instance?

Accepted Answer

provider. The 'provider' meta-argument allows you to select a specific aliased provider configuration.

Answer

configuration

Answer

alias

Answer

instance

Question 9

A provider binary is not found in the local Terraform registry cache. What command should you run to force Terraform to download the provider again?

Accepted Answer

terraform init -upgrade. terraform init -upgrade forces Terraform to re-evaluate and download the latest allowed versions of providers.

Answer

terraform plan -refresh-only

Answer

terraform providers install

Answer

terraform refresh

Question 10

Which file is automatically generated to lock provider versions and their checksums?

Accepted Answer

.terraform.lock.hcl. .terraform.lock.hcl is the dependency lock file.

Answer

terraform.tfstate

Answer

terraform.tfvars

Answer

provider.tf