AWS provider Practice Test 5 — 10 Questions

Question 1

What is the impact of using 'sensitive = true' in a module output?

Accepted Answer

It prevents the value from being printed in the CLI output.. It marks the output as sensitive, preventing it from being printed to the console during 'terraform apply' or 'plan'.

Answer

It disables the ability to use that output in other modules.

Answer

It encrypts the data in the state file.

Answer

It automatically rotates the sensitive credentials.

Question 2

Which TWO meta-arguments can be used within a module block?

Accepted Answer

'count'. 'count' and 'for_each' are the two meta-arguments available for module blocks.

Answer

'provisioner'

Answer

'depends_on'

Answer

'lifecycle'

Question 3

When should you use the 'for_each' meta-argument within a module?

Accepted Answer

To instantiate multiple copies of a module based on a map or set.. 'for_each' is used to create multiple instances of a module based on a map or set of strings.

Answer

To iterate over a list of variables inside a resource block.

Answer

To replace the 'count' meta-argument when you only need one instance.

Answer

To speed up the execution of the provider.

Question 4

Which THREE of the following are valid sources for a Terraform module?

Accepted Answer

The Terraform Registry.. Terraform supports modules from local paths, the Terraform Registry, and version control providers like Git.

Answer

A directly linked SQL database.

Answer

A raw HTTP file download link.

Question 5

Which TWO of the following are true about the '.terraform' directory?

Accepted Answer

It contains the module source code downloaded from registries.. The '.terraform' directory is used locally by Terraform to store module files and provider plugins.

Answer

It should be committed to version control.

Answer

It contains the permanent state file.

Answer

It is where custom provider binaries are compiled.

Question 6

Which THREE actions are best practices when publishing a module to a private registry?

Accepted Answer

Use Semantic Versioning (SemVer) for all releases.. Best practices include versioning, documentation, and specific naming conventions.

Answer

Keep all files in the root folder, including tests.

Answer

Prefix the repository name with 'terraform-provider-'.

Question 7

You are managing state in a multi-region deployment. You need to ensure that simultaneous terraform apply operations do not corrupt the state file. Which backend configuration parameter primarily enables this functionality?

Accepted Answer

dynamodb_table. The 'dynamodb_table' parameter is used with the S3 backend to enable state locking, preventing concurrent operations.

Answer

workspace_key_prefix

Answer

kms_key_id

Answer

acl

Question 8

A resource has an attribute 'tags' that is managed by an external script. You want Terraform to ignore any changes made to 'tags' after the initial creation. How should you configure the 'lifecycle' block?

Accepted Answer

ignore_changes = [tags]. The ignore_changes meta-argument allows you to specify a list of attributes that Terraform should skip during the refresh and plan phases.

Answer

lifecycle { tags = ignore }

Answer

prevent_destroy = [tags]

Answer

ignore_changes = [all]

Question 9

What is the purpose of the 'terraform state refresh' command?

Accepted Answer

To update the state file with current real-world resource attributes.. This command reconciles the state file with the actual infrastructure in the real world to detect drift.

Answer

To delete orphaned resources.

Answer

To apply changes to the cloud provider.

Answer

To upgrade the Terraform version.

Question 10

If you need to share output values between workspaces, what is the best practice in HCP Terraform?

Accepted Answer

Using the 'terraform_remote_state' data source. Using a workspace data source allows one workspace to read outputs from another safely.

Answer

Emailing the values

Answer

Hardcoding the IDs

Answer

Exporting to a flat file