Terraform-Associate-004 Exam Dumps - HashiCorp Terraform Associate Questions and Answers

Detailed Explanation:

Rationale for Correct Answer: A failed Terraform check block assertion does not block the current operation from executing. check blocks are used for non-blocking validation. If an assertion fails, Terraform reports a warning, but it does not stop the plan or apply operation. This is a common exam trap: check blocks differ from variable validation, preconditions, and postconditions, which can block execution when they fail.

Analysis of Incorrect Options (Distractors):

A. True. Incorrect. Terraform does not block execution because of a failed check block assertion.

Key Concept: Terraform check blocks perform non-blocking assertions and report failures as warnings.

Rationale for Correct Answer:Terraform detects drift by refreshing state during terraform apply. Since the VM no longer exists but is still declared in configuration, Terraform will plan and recreate the missing resource.

Analysis of Incorrect Options (Distractors):

B. Error: Terraform treats this as drift, not an error.

C. Remove from state: Terraform does not remove resources automatically unless instructed.

D. No changes: Incorrect because drift is detected and corrected.

Key Concept:Terraform enforces the desired state defined in configuration, correcting drift automatically.

Rationale for Correct Answer: A parent/root module can only read values from a child module if the child module exports them via an output block. The error indicates vnet_id is not an exported output from module.my_network. Defining output " vnet_id " { value = ... } inside the networking (child) module makes module.my_network.vnet_id valid.

Analysis of Incorrect Options (Distractors):

A: Incorrect—Terraform does not use module. < name > .outputs. < output > ; module outputs are referenced directly as module. < name > . < output > .

B: Incorrect—variables are inputs to a module, not values exported from it.

C: Incorrect—missing the module. prefix and still uses an invalid .outputs path.

Key Concept: Module outputs are the contract for exposing child module values to the root/parent.

Detailed Explanation:

Rationale for Correct Answer:Run triggers in HCP Terraform allow you to automatically initiate runs in one workspace based on changes in another workspace. In this scenario, when the networking workspace is updated, a run trigger ensures that the compute workspace automatically runs plan and apply, keeping dependent infrastructure in sync.

Analysis of Incorrect Options (Distractors):

B. Policy — Incorrect because policies (e.g., Sentinel) enforce rules and compliance but do not trigger runs between workspaces.

C. Run tasks — Incorrect because run tasks integrate external tools into the Terraform workflow (e.g., security scanning), not for chaining workspace executions.

D. Projects — Incorrect because projects are used for organizing workspaces, not for triggering operations.

Key Concept:Run triggersandIn in HCP Terraform.

This is how Terraform manages most dependencies between resources, by using the references between them in the configuration files. For example, if resource A depends on resource B, Terraform will create resource B first and then pass its attributes to resource A.

Detailed Explanation:

Rationale for Correct Answer:Module input variables are set by providing arguments in the module block whose names match the module’s declared variables. Since the module expects servers, you pass it directly as servers = 3. This is the standard Terraform module input pattern.

Analysis of Incorrect Options (Distractors):

A: Incorrect. var.servers is how you reference an input variable in expressions, not how you assign a module input. Module inputs are set as arguments, not through the var. namespace.

B: Incorrect. Terraform module blocks do not use an inputs = { ... } argument (that pattern is common in some other tools, but not Terraform).

D: Incorrect. inputs.servers is not valid HCL syntax for setting module input arguments.

Key Concept:Passing input variables to modules by setting arguments on the module block.

To see all the resources that Terraform will delete, you can use either of these two commands:

terraform destroy will show the plan of destruction and ask for your confirmation before proceeding. You can cancel the command if you do not want to destroy the resources.

terraform plan -destroy will show the plan of destruction without asking for confirmation. You can use this command to review the changes before running terraform destroy. References = : Destroy Infrastructure : Plan Command: Options

Detailed Explanation:

Rationale for Correct Answer:HCP Terraform health assessments focus on evaluating the overall state and efficiency of infrastructure. Key components include:

C. Estimate infrastructure cost – HCP Terraform integrates cost estimation (via Infracost) to provide visibility into infrastructure spending.

D. Resource drift detection – It checks whether the real infrastructure has drifted from the Terraform state, which is critical for maintaining consistency and reliability.

These capabilities align with Terraform Cloud’s goal of improving visibility, governance, and operational health of managed infrastructure.

Analysis of Incorrect Options (Distractors):

A. Terraform test execution Incorrect because terraform test is a CLI feature and not part of workspace health assessments.

B. Check block validation Incorrect because check blocks are evaluated during plan/apply runs, not specifically as part of health assessments.

E. Sentinel policy checks Incorrect because Sentinel policies are enforced during runs (plan/apply), not during health assessments.

Key Concept: HCP Terraform health assessments include cost estimation and drift detection to monitor infrastructure health.

This is not a valid Terraform collection type, as Terraform only supports three collection types: list, map, and set. A tree is a data structure that consists of nodes with parent-child relationships, which is not supported by Terraform.

Terraform is built on a plugin-based architecture, enabling developers to extend Terraform by writing new plugins or compiling modified versions of existing plugins1. Terraform plugins are executable binaries written in Go that expose an implementation for a specific service, such as a cloud resource, SaaS platform, or API2. If there is no existing provider for your API, you can create one using the Terraform Plugin SDK3 or the Terraform Plugin Framework4. References =

•1: Plugin Development - How Terraform Works With Plugins | Terraform | HashiCorp Developer

•2: Lab: Terraform Plug-in Based Architecture - GitHub

•3: Terraform Plugin SDK - Terraform by HashiCorp

•4: HashiCorp Terraform Plugin Framework Now Generally Available