AWS provider Practice Test 6 — 10 Questions

Question 1

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 2

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 3

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 4

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 5

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 6

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 7

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 8

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 9

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 10

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.