HashiCorp Terraform-Associate-003 Exam Practice Test Instant Access

Question 1

A module block is shown in the Exhibit space of this page. When you use a module block to reference a module from the Terraform Registry such as the one in the example, how do you specify version 1.0.0 of the module?

AAppend ?ref=v1.0.0 argument to the source path.

BYou cannot. Modules stored on the public Terraform Registry do not support versioning.

CAdd a version = '1.0.0' attribute to the module block.

DNothing. Modules stored on the public Terraform module Registry always default to version 1.0.0.

Answer : C

Module Versioning: To specify a version in a module block for modules in the Terraform Registry, you add the version attribute, e.g., version = '1.0.0'.

Terraform Registry Support: The public registry supports versioning by enabling semantic constraints, allowing users to define specific versions compatible with their infrastructure requirements.

Refer to the module versioning documentation in Terraform's official registry guide.

Question 2

When do you need to explicitly execute Terraform in refresh-only mode?

ABefore every terraform plan.

BBefore every terraform apply.

CBefore every terraform import.

DNone of the above.

Answer : C

Purpose of Refresh-Only Mode: Running Terraform in refresh-only mode updates Terraform's state file with the current state of resources in your infrastructure without making changes to the resources themselves.

Context of Terraform Import: When using terraform import, you're adding existing resources to the state file, and running Terraform in refresh-only mode before this operation can ensure that any initial configuration syncs precisely with the actual state.

For more on refresh-only mode in relation to terraform import, refer to Terraform's import documentation.

Question 3

Which method for sharing Terraform modules fulfills the following criteria:

Keeps the module configurations confidential within your organization.

Supports Terraform's semantic version constraints.

Provides a browsable directory of your modules.

AA Git repository containing your modules.

BPublic Terraform module registry.

CA subfolder within your workspace.

DHCP Terraform/Terraform Cloud private registry.

Answer : D

Confidentiality: Using HCP Terraform/Terraform Cloud's private registry keeps the module configurations within your organization, ensuring privacy and access control.

Browsable Directory: The private registry offers a user interface to browse modules, making it easy for users within the organization to locate and manage modules.

This setup aligns with HashiCorp's design for private registry support in Terraform, meeting all listed requirements for secure, version-controlled, and searchable module storage.

Question 4

Your root module contains a variable named num_servers. Which is the correct way to pass its value to a child module with an input named servers?

Aservers = num_servers

Bservers = var(num_servers)

Cservers = var.num_servers

Dservers = ${var.num_servers}

Answer : C

The correct syntax to pass a variable from the root module to a child module is servers = var.num_servers. Terraform uses dot notation to reference variables.

References:

Terraform Variables

Question 5

When you include a module block in your configuration that references a module from the Terraform Registry, the "version" attribute is required.

ATrue

BFalse

Answer : B

The 'version' attribute is optional when referencing a module from the Terraform Registry. If not specified, the latest version will be used, but it is often recommended to specify a version to ensure consistency across environments.

References:

Terraform Module Versioning

Question 6

Where in your Terraform configuration do you specify a state backend?

AThe resource block

BThe data source block

CThe terraform block

DThe provider block

Answer : C

In Terraform, the backend configuration, which includes details about where and how state is stored, is specified within the terraform block of your configuration. This block is the correct place to define the backend type and its configuration parameters, such as the location of the state file for a local backend or the bucket details for a remote backend like S3.

References = This practice is outlined in Terraform's core documentation, which provides examples and guidelines on how to configure various aspects of Terraform's behavior, including state backends .

Question 7

In a Terraform Cloud workspace linked to a version control repository, speculative plan runs start automatically when you merge or commit changes to version control.

ATrue

BFalse

Answer : B

In Terraform Cloud, speculative plan runs are not automatically started when changes are merged or committed to the version control repository linked to a workspace. Instead, speculative plans are typically triggered as part of proposed changes in merge requests or pull requests to give an indication of what would happen if the changes were applied, without making any real changes to the infrastructure. Actual plan and apply operations in Terraform Cloud workspaces are usually triggered by specific events or configurations defined within the Terraform Cloud workspace settings.

References = This behavior is part of how Terraform Cloud integrates with version control systems and is documented in Terraform Cloud's usage guidelines and best practices, especially in the context of VCS-driven workflows.

HashiCorp Terraform-Associate-003 HashiCorp Certified: Terraform Associate (003) Exam Practice Test