AWS provider Multiple Select — 50 Questions

Question 1

Which of the following are valid provider version constraint operators? (Select TWO)

Accepted Answer

=. = and ~> are both standard operators for version constraints.

Answer

||

Answer

&&

Answer

!!

Question 2

Which TWO features help maintain consistency across multiple workspaces?

Accepted Answer

Shared modules. Shared modules and variable sets ensure that configurations and inputs remain consistent across teams and workspaces.

Answer

Unique state files for every module

Answer

Using local execution only

Answer

Manual copy-pasting of code

Question 3

When troubleshooting a failed plan in HCP Terraform, which THREE sources should you check?

Accepted Answer

Policy check results. Logs, policy evaluation results, and the terraform init output are essential for debugging.

Answer

The provider source code

Answer

Organization billing page

Question 4

Which TWO of the following are valid uses of the 'for' expression?

Accepted Answer

Generating a list. for expressions can be used to generate lists (using brackets) or maps (using braces).

Answer

Defining a resource

Answer

Managing provider blocks

Answer

Creating dynamic blocks

Question 5

Which TWO of the following are standard stages of an HCP Terraform run pipeline?

Accepted Answer

Policy Check.. The pipeline consists of Plan, Policy Check, and Apply stages.

Answer

Code linting.

Answer

Automatic refactoring.

Answer

State migration.

Question 6

Which THREE of the following are required components of a Sentinel Policy Set?

Accepted Answer

A list of policies.. Policy sets require a name, a link to the policy code (VCS), and a definition of which workspaces apply to the policies.

Answer

A paid subscription license key.

Answer

A list of allowed IP addresses.

Question 7

Which THREE of the following are components of the 'source' string when using the Terraform Registry?

Accepted Answer

Provider.. The registry source string format is 'namespace/name/provider'.

Answer

Git branch name.

Answer

Operating system.

Question 8

Which THREE of these are benefits of using modules in Terraform?

Accepted Answer

Enforcing standardized configurations across teams.. Modules improve code reuse, organization, and standardization.

Answer

Increasing the execution speed of API calls.

Answer

Automatically preventing all resource drift.

Question 9

Which THREE of the following are true about 'lifecycle' blocks?

Accepted Answer

They are defined inside the resource configuration block.. They are per-resource, support specific arguments, and are defined inside the resource body.

Answer

They allow changing the provider version dynamically.

Answer

They are inherited from the provider block.

Question 10

Which TWO of the following are valid ways to pass a provider configuration to a child module?

Accepted Answer

Using the 'providers' meta-argument inside the module block.. Providers are either inherited from the root or passed explicitly using the 'providers' map in the module block.

Answer

Defining the provider inside the module's 'main.tf'.

Answer

Passing the provider as a string input variable.

Answer

Using a global variable for provider credentials.

Question 11

Which TWO of the following are true regarding variable validation in modules?

Accepted Answer

Validation blocks must return a boolean value.. Validation blocks and type constraints are the primary mechanisms for ensuring valid inputs.

Answer

Validation errors will only show during 'terraform apply'.

Answer

Validation blocks can read from other modules.

Answer

You can only validate string variables.

Question 12

Which THREE items should be included in a well-documented Terraform module?

Accepted Answer

Clear documentation for each output.. Documentation should cover how to use the module, its inputs, and its outputs.

Answer

A list of all possible provider configurations.

Answer

The raw state file of the module's resources.

Question 13

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 14

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 15

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 16

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 17

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 18

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 19

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.

Question 20

Which TWO actions can be taken to resolve issues where a resource must be replaced, but 'prevent_destroy' is enabled?

Accepted Answer

Run 'terraform state rm' to remove the resource from state and re-import.. You must either remove the meta-argument from the code or use the state management to remove the resource constraint before re-applying.

Answer

Use 'terraform apply -auto-approve'.

Answer

Use 'terraform refresh' to update the constraint.

Answer

Set the prevent_destroy argument to false in the CLI.