HashiCorp Certified: Terraform Associate (004) practice questions

Question 1

An architect is leading the review. a SRE at a fintech IaC platform is being asked at a design review how Terraform schedules independent versus dependent resources during an apply against the resource graph. Per the HashiCorp documentation, which option matches?

Accepted Answer

Independent resources launch simultaneously while dependent resources wait for their prerequisites to complete.

Answer

Terraform runs every resource strictly serially regardless of dependency information, with no concept of independent or dependent resources at apply time.

Answer

Terraform always serializes resource creation in strict alphabetical order regardless of dependency information and has no documented prerequisite-wait mechanism.

Answer

Terraform launches every resource at the same instant and immediately aborts the apply if any dependency ordering is violated, with no waiting mechanism documented at all.

Question 2

An architect is rolling out the design. a fintech platform team is rolling out an Infrastructure as Code platform across its AWS and on-prem footprint and the IaC lead must explain to leadership what Terraform actually is at the product level. Per the HashiCorp documentation, which option matches the published definition?

Accepted Answer

Terraform is an infrastructure as code tool that lets you build, change, and version cloud and on-prem resources safely and efficiently by using human-readable configuration files.

Answer

Terraform is a managed runtime that ships with every cloud account at sign-up and is administered exclusively through that cloud's web console, never from a workstation.

Answer

Terraform is a continuous-integration server replacement that schedules build pipelines for application source code and never interacts with cloud or on-prem infrastructure APIs.

Answer

Terraform is a per-resource imperative shell script executor and ships only as a deprecated component of older configuration-management agents installed on managed hosts.

Question 3

An architect is leading the review. a platform engineer at a fintech IaC platform is being asked at a knowledge share how Terraform allows the same module source code to be reused across staging and production with different inputs. Per the HashiCorp documentation, which option matches?

Accepted Answer

A variable block lets module consumers customize module behavior without altering the module's source code.

Answer

Terraform supports customization only by editing the resource blocks inside the module before each apply, with no concept of a separate variable block in HCL.

Answer

Terraform requires consumers to fork the entire module source code for every new environment, since there is no documented mechanism to pass values into a module.

Answer

Terraform variables are documented as runtime-only constructs that exist solely inside HCP Terraform's web console and cannot be expressed in HCL files.

Question 4

An architect is leading the review. a SRE at a SaaS multi-tenant platform is being asked at a design review what Terraform does before it computes a plan or apply to synchronize state with the live cloud. Per the HashiCorp documentation, which option matches?

Accepted Answer

Before executing any operation, Terraform performs a refresh cycle to synchronize the current state with actual infrastructure conditions.

Answer

Terraform refuses to reconcile state with reality and treats the stored state file as authoritative for every operation, regardless of the cloud's actual contents.

Answer

Terraform refreshes state by deleting and recreating every managed resource at the start of each run as the only documented way to reconcile state with reality.

Answer

Terraform refreshes state only when the operator passes a special -refresh flag and never performs synchronization automatically as part of plan or apply.

Question 5

An architect is leading the review. a platform engineer at a manufacturing edge platform is being asked at a knowledge share what the public Terraform Registry actually contains and who maintains those modules. Per the HashiCorp documentation, which option matches?

Accepted Answer

The public Terraform Registry at registry.terraform.io maintains an extensive collection of community-contributed and HashiCorp-maintained modules covering common infrastructure configurations.

Answer

The public Terraform Registry is documented as a private development sandbox and contains no consumable modules for any production scenario.

Answer

The public Terraform Registry contains only paid third-party modules that require a subscription to download and is empty of any HashiCorp-maintained or community-contributed module.

Answer

The public Terraform Registry contains only firmware images for IoT devices and has no Terraform-language modules of any kind.

Question 6

An architect is designing the controls. a government compliance officer is being asked at an audit how HCP Terraform supports recovering to a previous Terraform state if an incorrect apply has corrupted the current state. Per the HashiCorp documentation, which option matches?

Accepted Answer

When using HCP Terraform, state versions are preserved automatically, enabling rollback to previous states if needed.

Answer

HCP Terraform overwrites the prior state on every apply and the documentation states that no previous version is ever retained for any workspace.

Answer

HCP Terraform preserves prior state versions only when the operator explicitly clicks a per-apply 'Snapshot' button in the web UI, with no automatic behavior.

Answer

HCP Terraform preserves prior state versions for HCP Terraform Premium only and the documentation excludes any rollback capability from the standard tier.

Question 7

An architect is leading the review. a SRE at a SaaS multi-tenant team is being asked at a design review how HCP Terraform handles plan and apply execution relative to a developer's local workstation. Per the HashiCorp documentation, which option matches?

Accepted Answer

Rather than running Terraform locally, teams submit configurations to HCP Terraform which executes plan and apply operations in managed environments with consistent versions, credentials, and policies.

Answer

HCP Terraform supports only manual operator-driven planning, since the documentation does not include any automated managed-execution capability for any tier.

Answer

HCP Terraform requires every plan and apply to run on the developer's laptop and serves only as a result-storage system, with no documented managed-execution role.

Answer

HCP Terraform runs all plan and apply in the developer's local browser through WebAssembly, with no documented server-side execution layer.

Question 8

An architect is leading the review. a platform team at a healthcare hybrid-cloud organization is being asked at a code review how to read the symbols that Terraform plan output uses to describe each proposed change. Per the HashiCorp documentation, which option matches?

Accepted Answer

Terraform plan output uses symbols to indicate change types: + for create, - for destroy, ~ for update in-place, and -/+ for destroy and recreate.

Answer

Terraform plan output uses only the word 'change' before every proposed change and the documentation includes no symbol-based legend for any release.

Answer

Terraform plan output uses 'CREATE', 'DESTROY', and 'UPDATE' as long-form prefixes and the documentation explicitly rejects any single-character symbol prefix.

Answer

Terraform plan output is documented as HCP Terraform-only and the open-source CLI rejects any per-change legend in every release.

Question 9

An architect is asked to weigh in. a SaaS multi-tenant platform's IaC lead is being asked why Terraform's intelligent dependency resolution matters when managing dozens or hundreds of resources in the same apply. Per the HashiCorp documentation, which option matches?

Accepted Answer

This capability dramatically accelerates infrastructure provisioning when managing dozens or hundreds of resources.

Answer

The capability is documented as actively slower than serial provisioning on any cloud provider and HashiCorp recommends disabling parallelism for any large apply.

Answer

The documentation states that parallelism is irrelevant for any workload below the ten-thousand-resource threshold and provides no acceleration for typical deployments.

Answer

The capability is documented as an experimental preview feature available only inside HCP Terraform Premium and is never enabled in the open-source CLI.

Question 10

An architect is asked to weigh in. a healthcare hybrid-cloud architect is being asked which cross-platform workflow patterns Terraform actually supports for a deployment that spans AWS, Azure, an on-prem data center, and several SaaS providers. Per the HashiCorp documentation, which option matches?

Accepted Answer

Terraform manages multi-cloud, hybrid cloud, and service-agnostic workflows through its provider architecture, allowing resources across many platforms in a single configuration.

Answer

Terraform supports only single-cloud deployments and requires a separate fork of the Terraform binary per cloud, with no cross-provider configurations permitted within one workspace.

Answer

Terraform supports multi-cloud only by exporting a CSV of resources from one cloud and importing it into another, requiring an out-of-band manual step between providers.

Answer

Terraform automatically translates AWS ARNs into Azure resource IDs through a built-in cross-cloud translation layer and never requires a per-platform provider declaration.

Question 11

An architect is designing the controls. a SRE at a healthcare hybrid-cloud organization is being asked at an audit whether marking a variable sensitive removes its value from the Terraform state file as well. Per the HashiCorp documentation, which option matches?

Accepted Answer

However, sensitive variables still persist in state files, which must be stored securely.

Answer

The sensitive argument scrubs the variable from the state file entirely and the documentation states it is a complete replacement for any backend encryption.

Answer

Sensitive variables are documented as never reaching the state file at all and the operator can therefore commit state files to public Git without risk.

Answer

Sensitive variables are documented as encrypted in state with a per-workspace passphrase generated by Terraform on each apply, so no further secure-storage practice is required.

Question 12

An architect is asked to weigh in. a SRE at a manufacturing edge platform is being asked how to reduce repeated provider downloads across CI workers without changing the configuration. Per the HashiCorp documentation, which option matches?

Accepted Answer

The system supports plugin caching via the plugin_cache_dir setting to optimize bandwidth and performance.

Answer

Provider caching is permitted only when running inside a HashiCorp-hosted CI runner and is explicitly disabled when terraform init runs on a customer-managed CI worker.

Answer

The Terraform CLI hard-codes a single in-memory cache that lives only for the lifetime of one process and cannot be tuned by the operator in any environment.

Answer

Terraform requires the operator to rebuild every provider plugin from source on each CI worker every run, and the documentation rejects any caching scheme as unsafe.

Question 13

An architect is designing the controls. a government compliance officer is being asked how an organization can distribute internal modules without exposing them in the public Terraform Registry. Per the HashiCorp documentation, which option matches?

Accepted Answer

For organizational needs, HCP Terraform and Terraform Enterprise provide private module registries enabling internal distribution of organization-specific modules without public exposure.

Answer

Organizations must publish all modules to a public S3 bucket and rely on bucket-policy obscurity for privacy, since HashiCorp does not document any private registry.

Answer

Organizations must rebuild the Terraform CLI from source with internal patches to support private modules, since no documented private registry exists.

Answer

Organizations cannot keep modules private and HashiCorp documentation explicitly states that every module must be published to the public registry.

Question 14

An architect is designing the recovery. a retail store-ops SRE is being asked at a hardening review which of the documented limitations of the local backend disqualify it from team-shared production use. Per the HashiCorp documentation, which option matches?

Accepted Answer

While suitable for individual use and learning, local state does not support team collaboration, locking across team members, or encrypted storage.

Answer

The local backend is documented as supporting team collaboration only when paired with NFS, and HashiCorp recommends it as the default team backend on Linux workstations.

Answer

The local backend supports team-shared locking and encrypted-at-rest storage out of the box and is documented as the recommended production-grade backend.

Answer

The local backend is documented as fully encrypted and team-aware on every supported operating system, with no documented restrictions for production use.

Question 15

An architect is designing the controls. a government compliance officer is being asked which TWO of the listed policy engines HCP Terraform documents as supported for governing configuration contents before deployment. Per the HashiCorp documentation, select the two correct options.

Accepted Answer

Sentinel policies are written in HashiCorp's Sentinel language and can enforce rules such as requiring specific tags on resources, restricting instance types, or mandating encryption.

Accepted Answer

OPA policies use the Rego language for similar governance capabilities.

Answer

HCP Terraform documents an in-product Stripe billing-policy engine that overrides cloud-provider invoices in real time during plan.

Answer

HCP Terraform documents a native OCR-only image-classification engine for governing Terraform configurations before deployment.

HashiCorp Certified: Terraform Associate (004)

Sample questions

Sources

Similar exams