AWS provider Practice Exam 3 — 20 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

Question 11

You have a workspace configured for 'CLI-driven' workflow. What does this mean for how you apply changes?

Accepted Answer

The user triggers operations via the CLI. CLI-driven workflows require the user to trigger the plan/apply locally, while the state is managed remotely.

Answer

Operations are always automatic

Answer

It disables remote state

Answer

The plan happens locally, apply remotely

Question 12

Which of these is a valid use case for a dynamic block?

Accepted Answer

Defining nested repeatable blocks. Dynamic blocks are specifically intended to generate nested, repeatable blocks within a resource, such as 'ingress' rules in a security group or 'tags' in an instance.

Answer

Conditional module inclusion

Answer

Changing the provider configuration dynamically

Answer

Defining multiple separate resources

Question 13

In a dynamic block, you need to access the current iteration item. What is the default label assigned to the iterator object?

Accepted Answer

The name of the block. By default, the iterator name is the same as the name of the dynamic block, unless an 'iterator' argument is explicitly provided.

Answer

count.index

Answer

each.value

Answer

item

Question 14

You are using a dynamic block to define multiple 'tag' blocks inside an AWS resource. The dynamic block is failing because it expects a set of objects but receives a flat list. Which function best prepares your data?

Accepted Answer

toset(). The toset() function converts a list of strings or objects into a set, which is required by for_each to avoid index-based dependencies.

Answer

keys()

Answer

distinct()

Answer

compact()

Question 15

A downstream workspace in HCP Terraform needs to automatically trigger a plan after a successful apply in an upstream workspace. How do you configure this?

Accepted Answer

Configuring Run Triggers in the downstream workspace. Run triggers are configured in the downstream workspace settings to listen for successful outputs from an upstream workspace.

Answer

Enabling 'Auto-apply' in the upstream

Answer

Setting a 'TF_VAR' environment variable

Answer

Using a local variable

Question 16

You want to automate the approval process for non-production environments in HCP Terraform. Which setting enables this?

Accepted Answer

Enable Auto-apply. Auto-apply in workspace settings allows runs to proceed to completion without manual intervention.

Answer

Configure Run Triggers

Answer

Set Sentinel policy to advisory

Answer

Use API-driven workflows

Question 17

Which of the following is an advantage of using HCP Terraform over local state for team collaboration?

Accepted Answer

It provides state locking and run history. HCP Terraform provides centralized state management, locking, and a history of runs, which are critical for teams.

Answer

It converts HCL to JSON

Answer

It eliminates the need for AWS providers

Answer

It is always free

Question 18

Which THREE factors influence the choice of using an HCP Terraform Agent?

Accepted Answer

Need for private network connectivity. Agents are used for private network connectivity, compliance requirements, and accessing resources that don't allow public internet access.

Answer

To increase the speed of the provider download

Answer

To remove the need for a VCS

Question 19

Which TWO types of variables can be set in HCP Terraform?

Accepted Answer

Environment variables. HCP Terraform supports both Terraform variables (HCL) and environment variables (for provider configuration).

Answer

Policy-level variables

Answer

State-level variables

Answer

Hardcoded module variables

Question 20

Which TWO factors must be considered when using 'replace_triggered_by' with multiple resources?

Accepted Answer

The trigger cannot cause a circular dependency loop.. You must ensure the resources exist and that you are not creating circular replacement dependencies.

Answer

The trigger only works on the 'tags' attribute.

Answer

The trigger requires 'create_before_destroy' to be false.

Answer

The trigger only works with AWS resources.