AWS provider Practice Test 4 — 10 Questions

Question 1

Your team publishes an internal Terraform module to a private registry. A consumer wants to pin the module to a specific version to avoid unexpected changes. The module source is `app.terraform.io/example-org/vpc/aws`. Which source argument correctly pins the module to version 2.3.0?

Choose an answer to begin — your selection is scored in the full session.

Accepted Answer

source = "app.terraform.io/example-org/vpc/aws" version = "2.3.0". Registry modules require the version argument to be set separately from the source string. Pinning to an exact version such as "2.3.0" ensures that the same module code is used across all runs, which is critical for reproducibility and preventing unintended changes. The source format for a registry module is hostname/namespace/name/provider without any version embedded.

Answer

source = "git::https://app.terraform.io/example-org/vpc/aws.git?ref=v2.3.0"

Answer

source = "app.terraform.io/example-org/vpc/aws/2.3.0"

Answer

source = "app.terraform.io/example-org/vpc/aws?version=2.3.0"

Question 2

Your team uses HCP Terraform to manage AWS resources. You need to ensure that all workspaces in a project automatically inherit a set of AWS region and tagging variables. What is the most efficient way to achieve this?

Accepted Answer

Create a variable set and assign it to the project.. Variable sets are designed to share variables across multiple workspaces. Assigning a variable set to a project ensures all workspaces in that project inherit the variables, including future ones. This is more efficient than per-workspace definitions and is the recommended practice for organization-wide or project-wide variables.

Answer

Use a Terraform module to set the variables in each workspace.

Answer

Define the variables in each workspace individually.

Answer

Store the variables in a version control system and reference them via a remote backend.

Question 3

You are using a module that depends on a specific provider version. Where should this constraint be defined?

Accepted Answer

In the 'required_providers' block within the module's 'terraform' block.. Provider version constraints belong in the 'required_providers' block inside the module's 'terraform' block. This ensures the module declares its own compatibility requirements, which Terraform merges with the root module's constraints during initialization. It makes the module self-contained and portable.

Answer

In the 'provider' block of the calling root module.

Answer

In the root module only.

Answer

In a shell environment variable.

Question 4

A team uses the AWS provider to manage resources in three accounts: development, staging, and production. The root module must create an `aws_iam_role` in the production account while all other resources remain in the default development account. The production account's provider configuration is already declared with `alias = "prod"`. Which change to the production `aws_iam_role` resource is required?

Accepted Answer

Add `provider = aws.prod` to the resource block so it uses the aliased production provider configuration.. The provider meta-argument on a resource names the exact provider configuration to use, expressed as the provider type and alias, such as aws.prod. Because the production configuration is already declared with alias = "prod", adding provider = aws.prod to the aws_iam_role routes only that resource to the production account while everything else continues using the default development configuration.

Answer

Declare a second aws provider block without an alias and place it after the default provider block.

Answer

Set `region = "<prod-region>"` directly on the aws_iam_role resource block.

Answer

Move the aws_iam_role resource into a child module and pass the production provider via the module's providers argument.

Question 5

You have a root module that calls a child module to create an AWS VPC. The child module defines an output named `vpc_id`. After running `terraform apply`, where can you find the value of `vpc_id`?

Accepted Answer

In the root module's state file, under the child module's outputs, and accessible via `terraform output` if the root module also declares an output that references it.. Child module outputs are stored in the state file under the module's address, but they are only displayed by `terraform output` if the root module declares an output that references them. This explicit referencing is how Terraform maintains a clear contract between modules and the root configuration, and it allows consumers to control what is exposed.

Answer

Only in the child module's source directory as a generated file named `outputs.tfstate`.

Answer

Automatically in the root module's outputs, because Terraform promotes all child module outputs to the root level.

Answer

In the AWS provider's response to the `terraform apply` command, which lists all outputs from all modules.

Question 6

Which TWO of the following are benefits of using HCP Terraform for teams?

Accepted Answer

Centralized state management. Option A (Centralized state management) is correct because HCP Terraform stores Terraform state remotely in a shared, versioned workspace, enabling team members to collaborate on the same infrastructure without manually passing around terraform.tfstate files or configuring their own remote backends, and it provides state locking to prevent concurrent runs from corrupting state. Option B (Automated run triggers) is correct because HCP Terraform supports run triggers that automatically queue a dependent workspace's run when an upstream workspace completes successfully, as well as VCS-driven runs triggered by commits and API-driven runs, which streamlines multi-workspace and CI/CD workflows for teams. Option C (Local execution only) is incorrect because HCP Terraform's value comes from remote execution of runs in its managed environment, not from restricting execution to a single local machine. Option D (No need for version control) is incorrect because HCP Terraform integrates with VCS providers like GitHub, GitLab, and Bitbucket and relies on version-controlled configurations to drive runs. Option E (Lower costs) is incorrect because HCP Terraform is a paid platform with tiered pricing based on resources and seats, so it is not inherently a cost-reduction benefit.

Answer

Local execution only

Answer

No need for version control

Answer

Lower costs

Question 7

If a module has a required variable but you do not provide it in the calling configuration, what happens?

Accepted Answer

Terraform fails with an error during the planning phase.. If a module declares a variable without a default and the calling configuration does not supply a value, Terraform raises an error during the planning phase, stating that the required variable has not been set. Terraform does not invent a value or fall back to prior state. This fail-fast behavior ensures module contracts are honored.

Answer

Terraform uses 'null' for the value.

Answer

Terraform uses the variable value from the previous state.

Answer

Terraform automatically sets the value to an empty string.

Question 8

If a user omits the 'version' in 'required_providers', what version does Terraform use?

Accepted Answer

The latest available version.. When the 'version' argument is omitted inside a required_providers block, Terraform does not pin the provider to any specific release and instead resolves to the newest version available in the configured registry (public Terraform Registry or private registry). This is why HashiCorp strongly recommends always pinning versions in production to avoid unexpected breaking changes.

Answer

It will fail to initialize.

Answer

Version 1.0.0.

Answer

The oldest available version.

Question 9

How can you view the detailed breakdown of cost estimates for a specific Terraform plan?

Accepted Answer

Open the run page in the HCP Terraform UI.. The run details page in the HCP Terraform UI displays the cost estimation summary, which can be expanded for details.

Answer

Run the 'terraform show' command on the state file.

Answer

Check the cloud provider's billing dashboard.

Answer

Use the Sentinel CLI tool.

Question 10

A team is using Terraform to manage an aws_s3_bucket. They want Terraform to ignore any changes made to the bucket's tags outside of Terraform, but they still want Terraform to manage the bucket policy and versioning configuration. Which lifecycle configuration should they add?

Accepted Answer

Add lifecycle { ignore_changes = [tags] } to the aws_s3_bucket resource.. ignore_changes = [tags] excludes only the tags attribute from diff evaluation, so external tag edits are tolerated while policy and versioning remain under Terraform management. The other lifecycle meta-arguments address deletion protection, full drift suppression, or replacement ordering, none of which match the stated requirement.

Answer

Add lifecycle { ignore_changes = all } to the aws_s3_bucket resource.

Answer

Add lifecycle { create_before_destroy = true } to the aws_s3_bucket resource.

Answer

Add lifecycle { prevent_destroy = true } to the aws_s3_bucket resource.