HashiCorp Terraform Associate 003 Exam Dumps and Practice Test Questions Set 1 Q 1 – 20 

Visit here for our full HashiCorp Terraform Associate 003 exam dumps and practice test questions.

Question 1

Which of the following commands is used to initialize a Terraform working directory and install required providers?

A) terraform apply

B) terraform plan

C) terraform init

D) terraform validate

ANSWER: C) terraform init

EXPLANATION

The question asks about the command used to initialize a Terraform working directory and install the required providers. Each command listed has a specific purpose in the Terraform workflow, and it is important to understand their differences.

A) terraform apply
This command is used to apply the changes required to reach the desired state of the configuration. When you run terraform apply, Terraform reads the configuration files, compares the current state with the desired state, and then executes actions to make the real-world infrastructure match the configuration. While this is a critical command in Terraform’s lifecycle, it does not perform initialization or provider installation. Using terraform apply without initializing the directory may result in errors because the necessary provider plugins would not be installed. Therefore, this is not the correct answer.

B) terraform plan
The terraform plan command generates an execution plan, showing what actions Terraform will take to achieve the desired state described in the configuration files. This allows users to review changes before applying them. It does not initialize the directory or download provider plugins; it relies on an existing initialized working directory. Running terraform plan before initialization will produce errors because Terraform cannot access the required providers or backend configuration. Hence, this is not the correct choice.

C) terraform init
This command initializes a working directory containing Terraform configuration files. It sets up the backend, downloads and installs provider plugins, and prepares the working directory for use. Terraform init is the first command that should be run when setting up a new project or after cloning a repository containing Terraform configuration files. It ensures that all necessary plugins are available and that the state management backend is properly configured. This makes it the correct answer.

D) terraform validate
The terraform validate command checks the configuration files for syntax errors and verifies that the configuration is internally consistent. It ensures that Terraform can interpret the configuration correctly but does not initialize the working directory or install provider plugins. Running validate without initialization will still cause issues if provider references exist that are not yet installed. Therefore, this is not the correct answer.

 The core purpose of terraform init is to prepare a Terraform working directory for subsequent commands like plan and apply. Initialization ensures that all the providers required by the configuration are downloaded and installed locally, and that any backend configuration for storing state is set up correctly. Without running terraform init first, commands like terraform plan or terraform apply may fail. Understanding the workflow of Terraform—init, plan, apply, destroy—is crucial for the associate exam. This is why terraform init is the correct answer, as it specifically addresses initialization and provider setup.

Question 2

In Terraform, what is the primary purpose of the state file?

A) To store the Terraform configuration files

B) To maintain the mapping between resources in configuration and real-world infrastructure

C) To store provider binaries

D) To log Terraform command outputs

ANSWER: B) To maintain the mapping between resources in configuration and real-world infrastructure

EXPLANATION

This question focuses on understanding Terraform state management, which is a critical component of Terraform’s functioning. Each of the answers addresses a different aspect of Terraform, and it is important to analyze them individually.

A) To store the Terraform configuration files
Terraform configuration files are written in HCL (HashiCorp Configuration Language) and define the desired state of infrastructure. These files are stored separately in the working directory and are not part of the state file. The state file does not store the actual configuration; it tracks how the configuration maps to the deployed resources. Therefore, this is incorrect.

B) To maintain the mapping between resources in configuration and real-world infrastructure
This is the core purpose of the Terraform state file. It keeps a record of all resources that Terraform manages, including metadata, resource IDs, dependencies, and attributes. By maintaining this mapping, Terraform can detect changes, track resource drift, and determine which resources need to be created, updated, or deleted. The state file enables Terraform to manage infrastructure incrementally rather than recreating everything from scratch. This is why this answer is correct.

C) To store provider binaries
Provider binaries are downloaded to a local plugin directory during terraform init. They are not stored in the state file. The state file focuses on tracking resource metadata and infrastructure state, not on storing executable files. Therefore, this choice is incorrect.

D) To log Terraform command outputs
While Terraform generates logs and outputs during execution, these logs are not stored in the state file. Logging is typically managed separately via console output or external logging mechanisms. The state file is for tracking the current infrastructure state, not for logging command outputs. This is also incorrect.

 Understanding Terraform state is essential for proper infrastructure management. Without a state file, Terraform cannot reliably determine what changes need to be applied. The state file acts as a source of truth for Terraform, enabling it to maintain consistent and accurate control over infrastructure. This makes option B the correct choice, as it aligns with Terraform’s design principle of mapping configuration to real-world resources.

 

Question 3

Which Terraform feature allows you to create multiple similar resources without repeating code?

A) Modules

B) Workspaces

C) Loops (for_each and count)

D) Providers

ANSWER: C) Loops (for_each and count)

EXPLANATION

This question tests knowledge of Terraform’s features for code reusability and resource replication. Each choice has distinct functionality, and analyzing them helps clarify why loops are the correct answer.

A) Modules
Modules allow for grouping multiple resources and reusing them across configurations. While modules promote reusability, they are not primarily designed for creating multiple instances of a single resource without repeating code. Modules are more about structural organization and encapsulation. Thus, modules alone do not directly handle multiple similar resources efficiently.

B) Workspaces
Workspaces allow you to manage multiple instances of a single Terraform configuration in separate state files. They are useful for environments like dev, staging, and production but do not inherently replicate resources within a single workspace. Workspaces manage different deployments, not loops within a configuration. This makes workspaces an incorrect choice for this question.

C) Loops (for_each and count)
Loops using for_each and count allow you to create multiple instances of a resource dynamically based on input variables or a collection. The count parameter creates a specified number of resource instances, while for_each iterates over a map or set to create resources with unique keys. This mechanism avoids repeating code and ensures resources are generated efficiently. This makes loops the correct answer.

D) Providers
Providers define the infrastructure platform (e.g., AWS, Azure, Google Cloud) and are necessary for resource creation. However, they do not handle code repetition or dynamic resource generation. Providers are about connecting Terraform to the target platform, not managing multiple resource instances.

 Terraform provides two main mechanisms for dynamic resource creation: count and for_each. Count is an integer-based approach for creating N copies of a resource, while for_each is collection-based for key-value mapping. By leveraging these, users can manage hundreds of resources without duplicating configuration blocks. This capability is distinct from modules, workspaces, or providers, confirming that loops are the correct answer.

Question 4

What is the purpose of Terraform providers?

A) To store Terraform state

B) To define and manage infrastructure resources

C) To validate Terraform configuration

D) To output resource information

ANSWER: B) To define and manage infrastructure resources

EXPLANATION

Understanding Terraform providers is fundamental because they connect Terraform to external platforms. Analyzing each choice helps clarify their role.

A) To store Terraform state
Terraform state is managed locally or remotely via backends. Providers do not store state. Their role is focused on managing resource types and API interactions with the target platform. This makes storing state unrelated to providers.

B) To define and manage infrastructure resources
Providers are responsible for defining the available resource types and enabling Terraform to interact with APIs of infrastructure platforms like AWS, Azure, GCP, and more. They translate Terraform configurations into API calls, ensuring that resources are created, updated, or destroyed as specified. This is the correct choice because managing resources is the primary role of providers.

C) To validate Terraform configuration
Terraform validation checks the syntax and internal consistency of configurations. Providers themselves do not perform validation, though Terraform uses providers to verify resource-specific attributes during validation. This is not the main purpose of providers.

D) To output resource information
Terraform outputs are used to display values from resources or modules. Providers enable resource creation and management but are not responsible for outputting information directly. Outputs are a separate feature in Terraform configuration.

 Providers serve as the bridge between Terraform and external systems. Without a provider, Terraform cannot interact with infrastructure APIs, making it impossible to define or manage resources. They are essential for resource CRUD operations and are tailored to specific platforms, confirming that defining and managing infrastructure is their purpose.

Question 5

Which of the following commands would you use to destroy all infrastructure managed by Terraform?

A) terraform destroy

B) terraform plan

C) terraform apply

D) terraform refresh

ANSWER: A) terraform destroy

EXPLANATION

This question examines understanding of Terraform lifecycle commands. Each command has a unique purpose, and analyzing them individually clarifies the correct choice.

A) terraform destroy
This command is explicitly designed to remove all resources managed by Terraform in the current state. It calculates the actions required to delete the infrastructure, presents a plan, and then executes it. Destroy ensures that resources are removed safely and in a controlled manner, making it the correct choice.

B) terraform plan
Terraform plan shows the actions Terraform would take to apply changes but does not execute them. While it can show deletions if the configuration changes, it does not destroy resources on its own.

C) terraform apply
Terraform apply applies changes to match the desired state described in the configuration. It can create, update, or delete resources depending on differences in configuration, but it is not specifically for destroying all infrastructure unless the configuration is empty.

D) terraform refresh
Terraform refresh updates the state file to match the current real-world infrastructure without making any changes. It recalculates attributes but does not create, update, or destroy resources.

  Terraform destroy is a critical command for lifecycle management, especially for cleaning up temporary or test environments. It ensures all resources tracked by the state file are removed. Other commands, while important, serve different purposes, making destroy the only correct choice for removing infrastructure entirely.

Question 6

Which of the following Terraform commands is used to review the changes Terraform will make to your infrastructure before applying them?

A) terraform init

B) terraform plan

C) terraform apply

D) terraform validate

ANSWER: B) terraform plan

EXPLANATION

This question tests understanding of Terraform’s workflow, specifically the command used to preview infrastructure changes. Each of the listed commands serves a different purpose, and a detailed analysis is necessary to distinguish them.

A) terraform init
The terraform init command initializes a working directory by downloading the required provider plugins and configuring the backend for state storage. While this command is essential for starting any Terraform project, it does not show what changes will be applied to the infrastructure. Initialization prepares the environment but does not produce an execution plan or preview changes. Therefore, this is not the correct answer.

B) terraform plan
Terraform plan is designed specifically to generate an execution plan. It compares the current state of the infrastructure with the desired state defined in the configuration files. It then produces a detailed plan that shows exactly which resources will be created, modified, or destroyed. This command is critical because it allows users to verify that the intended changes align with expectations before making actual modifications. For example, if you accidentally delete a resource in your configuration, terraform plan will highlight it before execution, helping prevent unintended data loss. This makes terraform plan the correct choice.

C) terraform apply
Terraform apply executes the changes required to bring the infrastructure to the desired state. While it can optionally include a plan preview if run with the -auto-approve flag omitted, its primary function is to implement changes, not just to preview them. Applying changes without first reviewing them with terraform plan can lead to mistakes or unintentional disruptions. Therefore, apply is not the correct answer in the context of reviewing changes.

D) terraform validate
Terraform validate checks the syntax and internal consistency of Terraform configuration files. It ensures that the configuration is structurally correct and can be parsed, but it does not create, modify, or show any changes to infrastructure. This command is used primarily for error checking, not planning. Hence, it is incorrect for this question.

 Terraform plan plays a critical role in ensuring safe and predictable infrastructure management. It acts as a dry run, allowing teams to review proposed actions before execution. This prevents accidental deletion, modification, or creation of resources, which is particularly important in production environments. By examining all four choices, it becomes clear that plan is the only command explicitly intended for reviewing changes, confirming it as the correct answer.

Question 7

In Terraform, what is a module?

A) A set of reusable configuration files

B) A provider plugin

C) A Terraform workspace

D) A backend configuration

ANSWER: A) A set of reusable configuration files

EXPLANATION

Understanding modules is crucial for organizing and reusing Terraform configurations. Each choice represents a different concept in Terraform, and evaluating them carefully helps clarify the correct answer.

A) A set of reusable configuration files
Modules are self-contained packages of Terraform configurations that can be reused across projects. They consist of multiple resources, variables, and outputs, allowing teams to standardize infrastructure patterns. Using modules improves maintainability, reduces duplication, and promotes best practices. For instance, a network module could define VPCs, subnets, and security groups, and it can be used in multiple projects without rewriting the same configuration. This makes A the correct answer.

B) A provider plugin
Providers define the platform APIs and resources Terraform interacts with. While essential for resource creation and management, they do not represent a reusable package of configuration files. They are specific to platforms like AWS, Azure, or GCP. This makes B incorrect.

C) A Terraform workspace
Workspaces allow multiple state files to coexist for the same configuration, facilitating separate environments such as dev, staging, and production. Workspaces do not encapsulate reusable code or configuration blocks; they are used to isolate state, making C incorrect.

D) A backend configuration
Backends define where and how Terraform stores its state file, enabling remote storage and collaboration. They are not a mechanism for code reuse and therefore do not qualify as modules. D is incorrect.

 Modules are central to Terraform’s philosophy of reusability and modular infrastructure design. They allow for encapsulation of complex resource sets into manageable units that can be consistently applied across environments. By comparing the options, it is clear that only a set of reusable configuration files correctly describes a Terraform module, making A the correct answer.

Question 8

Which command would you use to check whether your Terraform configuration files are syntactically valid?

A) terraform validate

B) terraform plan

C) terraform apply

D) terraform init

ANSWER: A) terraform validate

EXPLANATION

Terraform validate is designed to verify the correctness of configuration syntax and internal consistency. Each choice has a different role, and analyzing them helps clarify why validate is correct.

A) terraform validate
This command checks that the configuration files are syntactically correct and internally consistent. It ensures that required attributes are present, data types are correct, and references are valid. Validation helps prevent errors during plan or apply operations. Unlike plan or apply, it does not require actual infrastructure to exist or be reachable. This makes it the correct answer.

B) terraform plan
Terraform plan generates an execution plan showing what changes would be applied to infrastructure. While plan will fail if the configuration contains syntax errors, its primary purpose is to preview changes rather than validate syntax. Therefore, it is not the most accurate answer.

C) terraform apply
Terraform apply executes the changes necessary to reach the desired infrastructure state. Although it also performs implicit validation, its main function is execution, not syntax checking. Using apply just to validate is inefficient and risky in production environments. Hence, it is incorrect.

D) terraform init
Terraform init initializes the working directory and installs provider plugins. Initialization is crucial before planning or applying changes, but it does not validate syntax or internal consistency. D is therefore incorrect.

 Terraform validate is a safeguard against configuration errors, allowing users to catch syntax mistakes and misconfigurations before planning or applying changes. This is especially important in teams or automated pipelines to ensure reliability. By understanding the distinct purposes of plan, apply, and init, it becomes evident that validate is the only command specifically designed for syntactic and semantic checks, confirming it as the correct answer.

Question 9

Which of the following describes a Terraform backend?

A) A mechanism for storing the Terraform state

B) A way to create multiple similar resources

C) A reusable module

D) A provider plugin

ANSWER: A) A mechanism for storing the Terraform state

EXPLANATION

Backends are a core concept for state management in Terraform. Each choice corresponds to a different Terraform concept, so detailed analysis is required.

A) A mechanism for storing the Terraform state
Backends control how and where Terraform stores its state file. They can store state locally or remotely in cloud storage solutions like AWS S3, Azure Blob Storage, or Terraform Cloud. Remote backends enable collaboration, locking, and versioning of the state file. Proper backend configuration ensures consistency across teams and prevents conflicts when multiple people manage the same infrastructure. This makes A the correct answer.

B) A way to create multiple similar resources
Creating multiple resources without repeating code is handled by loops such as count or for_each, not by backends. Backends focus exclusively on state storage. Therefore, B is incorrect.

C) A reusable module
Modules encapsulate sets of resources for reuse but are unrelated to state storage or backend configuration. C is incorrect.

D) A provider plugin
Providers allow Terraform to communicate with infrastructure platforms and APIs but do not store state. Backends and providers serve entirely different purposes. D is incorrect.

 Backends are essential for Terraform’s ability to collaborate and manage state reliably. By storing the state in a centralized or remote location, teams can avoid conflicts, implement locking, and maintain consistent infrastructure management. This makes A the correct answer.

Question 10

When using Terraform, which feature allows you to manage multiple environments (e.g., dev, staging, production) using the same configuration?

A) Providers

B) Workspaces

C) Modules

D) State files

ANSWER: B) Workspaces

EXPLANATION

Managing multiple environments with a single configuration is a common requirement in Terraform. Each choice serves a different purpose, so careful analysis is necessary.

A) Providers
Providers allow Terraform to interact with different platforms like AWS, Azure, or GCP. While providers define resources for a particular platform, they do not inherently manage multiple environments. This makes A incorrect.

B) Workspaces
Workspaces provide separate instances of state for the same configuration. Each workspace maintains its own state file, enabling separate environments such as dev, staging, and production. This allows teams to deploy the same configuration with environment-specific data without duplicating code. Terraform automatically switches state files when changing workspaces, simplifying multi-environment management. This makes B the correct answer.

C) Modules
Modules encapsulate resources for reusability but do not manage multiple environments directly. They are used to reduce duplication but cannot isolate state across environments. C is incorrect.

D) State files
State files track resource mappings for a specific deployment but do not by themselves manage multiple environments. While multiple state files can exist, workspaces are the mechanism that organizes them efficiently. D is incorrect.

 Workspaces are designed specifically for multi-environment management within Terraform. They allow teams to use a single configuration while isolating environment-specific states. This ensures consistency across environments and prevents accidental resource interference, making B the only correct choice.

Question 11

Which of the following statements about Terraform providers is correct?

A) Providers store the Terraform state file

B) Providers define the APIs and resources Terraform can interact with

C) Providers are used to group multiple resources into reusable units

D) Providers are used to manage multiple environments

ANSWER: B) Providers define the APIs and resources Terraform can interact with

EXPLANATION

Terraform providers are essential components that enable Terraform to interact with external systems such as cloud platforms, SaaS providers, or custom APIs. Each choice listed describes a potential function, but understanding the core role of providers clarifies which one is correct.

A) Providers store the Terraform state file
The state file contains information about the current state of infrastructure resources and is stored locally or in a remote backend. Providers do not store state; their function is to define and manage resource interactions with the API of the platform. This choice is incorrect.

B) Providers define the APIs and resources Terraform can interact with
Providers act as the bridge between Terraform configurations and the real-world infrastructure. They expose specific resource types, data sources, and functionalities for a given platform. For example, the AWS provider allows Terraform to manage EC2 instances, S3 buckets, IAM roles, and other AWS resources. Providers handle authentication, API calls, and mapping of Terraform resources to real-world objects. Without providers, Terraform cannot create or modify resources on any platform. This makes B the correct answer.

C) Providers are used to group multiple resources into reusable units
Grouping multiple resources into reusable units is the purpose of modules, not providers. Modules allow for encapsulation and reuse, which helps organize infrastructure efficiently. Providers do not encapsulate resources but provide the interface to manage them. This makes C incorrect.

D) Providers are used to manage multiple environments
Multiple environments, such as dev, staging, and production, are typically managed using workspaces or separate state files. Providers define resource types and APIs but do not inherently handle environment separation. D is incorrect.

Question 12

What is the purpose of the Terraform for_each construct?

A) To define multiple providers

B) To iterate over a collection to create multiple resource instances

C) To initialize the Terraform working directory

D) To store state files in multiple locations

ANSWER: B) To iterate over a collection to create multiple resource instances

EXPLANATION

The for_each construct in Terraform is used to simplify the creation of multiple resources based on a collection of data. Each choice provided suggests a different purpose, and a detailed understanding helps identify the correct function.

A) To define multiple providers
Defining multiple providers allows resources to interact with different platforms or regions, but it is unrelated to the for_each construct. for_each focuses on duplicating resource blocks dynamically based on a collection of values. This makes A incorrect.

B) To iterate over a collection to create multiple resource instances
for_each enables dynamic resource creation by iterating over a map or set. Each key-value pair can generate a distinct resource with its own attributes. For instance, if you have a map of server names and configurations, for_each will create one resource for each map entry. This approach avoids repeating resource blocks manually, improves maintainability, and ensures that updates to the collection automatically adjust the created resources. This makes B the correct answer.

C) To initialize the Terraform working directory
Initialization is performed using terraform init, not for_each. for_each is purely a mechanism for dynamic resource generation and has no role in initialization. C is incorrect.

D) To store state files in multiple locations
State management is controlled through backends, which determine where Terraform stores the state. for_each does not influence state storage or backend configuration, making D incorrect.

Question 13

Which Terraform command would you use to remove resources defined in your configuration?

A) terraform destroy

B) terraform plan

C) terraform init

D) terraform validate

ANSWER: A) terraform destroy

EXPLANATION

Terraform provides commands to manage the lifecycle of infrastructure resources, including creation, updating, and deletion. Understanding the differences between commands is essential to identify the correct one for resource removal.

A) terraform destroy
The terraform destroy command is designed specifically to remove all resources managed by Terraform in the current state. It calculates the dependencies and generates a plan to delete the resources safely. When executed, it ensures that resources are destroyed in the correct order, preventing dependency errors. Users can review the destroy plan before execution to confirm that only the intended resources will be deleted. This makes A the correct answer.

B) terraform plan
The terraform plan command shows the changes that will occur based on the configuration but does not execute them. While it may indicate resources that will be deleted if the configuration is modified, it does not perform actual deletion. B is incorrect.

C) terraform init
terraform init prepares a working directory by downloading required providers and configuring the backend. It does not create, modify, or delete resources. C is incorrect.

D) terraform validate
terraform validate checks the configuration for syntax errors and internal consistency but does not apply or destroy resources. D is incorrect.

Question 14

Which Terraform feature allows you to encapsulate multiple resources for reuse across different projects?

A) Workspaces

B) Providers

C) Modules

D) State files

ANSWER: C) Modules

EXPLANATION

Modules in Terraform are a key concept for code reuse and maintainability. Each choice represents a different Terraform construct, and understanding their purposes clarifies which one enables resource encapsulation.

A) Workspaces
Workspaces allow you to manage multiple environments by maintaining separate state files for the same configuration. They do not encapsulate multiple resources for reuse. This makes A incorrect.

B) Providers
Providers define the API and resource interactions with external platforms. They do not encapsulate resource groups or facilitate reuse. B is incorrect.

C) Modules
Modules are reusable containers of Terraform resources, variables, and outputs. They allow developers to define a set of infrastructure components once and reuse them across different projects or environments. Modules promote maintainability, reduce duplication, and ensure consistent implementation of best practices. For example, a network module could include VPCs, subnets, security groups, and route tables, which can be reused across multiple projects without rewriting configurations. This makes C the correct answer.

D) State files
State files track the current infrastructure status but do not provide a mechanism for encapsulating or reusing resources. D is incorrect.

Question 15

What is the primary purpose of a Terraform state file?

A) To store provider binaries

B) To maintain a mapping between Terraform configurations and real-world infrastructure

C) To execute Terraform commands

D) To manage workspaces

ANSWER: B) To maintain a mapping between Terraform configurations and real-world infrastructure

EXPLANATION

The Terraform state file is a critical component for maintaining infrastructure consistency and enabling incremental updates. Each choice relates to a different aspect of Terraform’s functionality.

A) To store provider binaries
Provider binaries are downloaded during initialization and stored separately. The state file does not contain executable provider files. A is incorrect.

B) To maintain a mapping between Terraform configurations and real-world infrastructure
The state file keeps track of the resources Terraform manages, including their attributes, IDs, dependencies, and relationships. It allows Terraform to determine what changes need to be applied to reach the desired state. By maintaining this mapping, Terraform can perform incremental updates, detect drift, and ensure accurate resource management. This makes B the correct answer.

C) To execute Terraform commands
Commands like plan, apply, or destroy execute changes, but the state file itself does not execute commands. Its role is to store metadata about infrastructure. C is incorrect.

D) To manage workspaces
Workspaces allow multiple instances of state files for separate environments, but the state file itself does not manage workspace logic. Workspaces provide the organizational layer, while the state file tracks resource mappings. D is incorrect.

Question 16

Which of the following commands is used to upgrade the provider versions in your Terraform configuration?

A) terraform plan

B) terraform apply

C) terraform init -upgrade

D) terraform validate

ANSWER: C) terraform init -upgrade

EXPLANATION

Terraform providers are the interface through which Terraform interacts with infrastructure platforms. Providers are versioned, and periodically, upgrades are needed to access new features, bug fixes, or security improvements. The command to handle upgrades is often misunderstood because multiple commands in Terraform involve initialization, planning, or applying changes, and each serves a different purpose.

A) terraform plan
Terraform plan generates an execution plan, showing what changes Terraform will perform to match the desired state in the configuration. Although plan checks the existing state and current configuration, it does not interact with provider versions. Plan relies on providers already installed in the local environment, so it does not perform upgrades. Using plan alone will not fetch the latest provider versions. Therefore, this is incorrect.

B) terraform apply
Terraform apply executes changes to reach the desired infrastructure state. Like plan, it requires providers to be installed, but it does not update provider versions automatically. If the configuration specifies a newer version than what is installed, apply will fail unless the providers have been upgraded manually or through an init command. Hence, apply is not the correct choice.

C) terraform init -upgrade
Terraform init is used to initialize a working directory, download provider plugins, and set up backend configurations. Adding the -upgrade flag ensures that Terraform checks for newer versions of providers, ignoring the cached versions installed locally. This command updates the installed providers to meet version constraints defined in the configuration. This is the correct answer because it explicitly performs the function of upgrading provider versions safely. It allows Terraform to use the latest features or patches without manually modifying plugin directories.

D) terraform validate
Terraform validate checks the configuration files for syntax errors and internal consistency. It does not perform any actions related to provider installation or upgrades. Validation ensures the configuration is correct, but it does not modify or upgrade dependencies. Therefore, validate is not the correct answer.

Question 17

In Terraform, which construct allows dynamic computation of values using expressions?

A) Variables

B) Locals

C) Outputs

D) Providers

ANSWER: B) Locals

EXPLANATION

Terraform provides multiple constructs for managing data and computing values. Understanding the distinction between variables, locals, outputs, and providers is essential for using Terraform effectively.

A) Variables
Variables allow you to pass external input values into Terraform configurations, enabling flexibility and parameterization. While variables can influence computed values, they themselves are not used to dynamically compute values internally. They serve primarily as inputs rather than mechanisms for calculation. Therefore, variables alone do not satisfy the requirement of dynamic computation within a configuration.

B) Locals
Locals are a Terraform construct designed to define local values within a module or configuration. They allow dynamic computation using expressions, functions, and data references. For example, you can concatenate strings, compute derived values, or combine map and list data into a single local variable. Locals improve readability, reduce repetition, and centralize computations, making configurations more maintainable. This is the correct answer because it provides a way to compute and reuse values dynamically within a module.

C) Outputs
Outputs are used to expose values from a configuration or module after Terraform operations. Outputs are primarily for visibility and passing values to other configurations, not for computing values internally. While outputs can reference locals or variables for their values, they do not perform dynamic computation themselves. Therefore, outputs are not correct in this context.

D) Providers
Providers define the APIs and resources Terraform can interact with. They do not compute values or manage local expressions; their role is resource interaction. Providers cannot dynamically compute values for configuration use, making this choice incorrect.

Question 18

Which Terraform command is used to copy the state of resources from one configuration to another?

A) terraform state mv

B) terraform plan

C) terraform apply

D) terraform import

ANSWER: D) terraform import

EXPLANATION

Terraform provides several commands to manage the state and real-world resources. The ability to incorporate existing resources into Terraform’s state is a common requirement, and understanding the distinctions between commands is critical.

A) terraform state mv
The state mv command is used to move or rename resources within Terraform’s state file. It does not create new entries from existing infrastructure; it only changes the mapping of already tracked resources in the state. Therefore, this command does not import external resources and is incorrect.

B) terraform plan
Terraform plan generates an execution plan, showing what changes will be made based on differences between configuration and state. It does not import external resources into Terraform’s management. Hence, plan is not correct.

C) terraform apply
Terraform apply executes the plan to create, update, or destroy resources to match the configuration. Like plan, apply cannot import existing resources into the state unless they are explicitly imported beforehand. Apply alone cannot bring external resources under Terraform management, making it incorrect.

D) terraform import
Terraform import allows you to bring existing real-world infrastructure into Terraform’s state. It maps resources in the external system to Terraform resource definitions. Once imported, Terraform can manage the resource as part of the configuration. This is the correct answer because it enables you to adopt resources created outside Terraform or previously unmanaged resources into Terraform management without recreating them.

Question 19

Which Terraform feature allows sharing and reusing configurations across teams or projects?

A) Modules

B) Workspaces

C) Providers

D) State files

ANSWER: A) Modules

EXPLANATION

Sharing and reusing infrastructure configurations is a critical practice in Terraform, enabling standardization and best practices. Each choice addresses a different part of Terraform’s functionality.

A) Modules
Modules encapsulate resources, variables, and outputs into reusable packages. They can be shared internally within a team or externally through the Terraform Registry. By using modules, teams can apply consistent configurations across multiple projects or environments, reducing duplication and improving maintainability. Modules can include complex patterns such as networking setups, compute clusters, or application deployments, which can be reused without rewriting configuration files. This makes modules the correct answer.

B) Workspaces
Workspaces allow multiple instances of the same configuration with isolated states. They help manage different environments but do not directly facilitate code sharing or reuse across projects. Workspaces are environment-focused rather than configuration-sharing constructs. B is incorrect.

C) Providers
Providers define how Terraform interacts with infrastructure platforms. While essential for resource management, they do not encapsulate reusable configurations or promote sharing of resource patterns. Providers are platform-specific, not a method for reusing configurations across teams. C is incorrect.

D) State files
State files track the current status of infrastructure resources but do not enable configuration reuse. They are a representation of the deployed resources, not a reusable or shareable configuration artifact. D is incorrect.

Question 20

In Terraform, what is the difference between count and for_each when creating multiple resources?

A) count creates resources dynamically, for_each cannot

B) count requires an integer, for_each can iterate over maps or sets

C) count is used for modules, for_each is used for providers

D) count and for_each perform the same function with no difference

ANSWER: B) count requires an integer, for_each can iterate over maps or sets

EXPLANATION

Terraform provides constructs to create multiple instances of resources efficiently. Understanding the difference between count and for_each is essential for writing flexible configurations.

A) count creates resources dynamically, for_each cannot
Both count and for_each are capable of dynamically creating multiple resources. Saying that for_each cannot create resources dynamically is incorrect, making this choice wrong.

B) count requires an integer, for_each can iterate over maps or sets
The count parameter uses an integer to specify the number of identical resource instances to create. Each instance is referenced by an index. In contrast, for_each iterates over a collection such as a map or set, allowing resources to be created with unique keys and attributes. for_each is more flexible for complex data-driven resource creation, whereas count is simpler for identical copies. This makes B the correct answer.

C) count is used for modules, for_each is used for providers
This statement is incorrect. Both count and for_each can be used on resources, data sources, or module blocks. They are not specific to modules or providers. C is incorrect.

D) count and for_each perform the same function with no difference
While both are used for creating multiple resources, their mechanisms and use cases differ. Count relies on integer indexing, whereas for_each iterates over collections with unique keys. They are not functionally identical, making D incorrect.