ExamNova

TERRAFORM-004 · Associate

Terraform Associate (004)

Apply Terraform 1.12 configuration, state safety, module composition and collaborative infrastructure workflows.

Start Free

Your free account includes a full TERRAFORM-004 practice exam.

ExamNova practice

Your first session

Questions
60
Time limit
60 min
Coverage
8 domains

Practise, review your answers and see where to focus next.

Is TERRAFORM-004 your next step?

Explore the coverage below to see how this certification fits your study goals.

What you’ll study

Your TERRAFORM-004 practice covers every domain on the exam.

  1. Infrastructure as Code (IaC) with Terraform
  2. Terraform fundamentals
  3. Core Terraform workflow
  4. Terraform configuration
  5. Terraform modules
  6. Terraform state management
  7. Maintain infrastructure with Terraform
  8. HCP Terraform

Consult the official guide for the vendor’s current exam outline.

Put it into practice.

Explore hands-on tasks connected to TERRAFORM-004. These are real Labs from the catalogue.

Lab

Repair deployment ordering and changing schema values

Repair deployment.tf.json using its four terraform_data resources. Keep schema.input = orders-v2, role.input = orders-reader and audit.input = security-log. Application input must evaluate to an object with schema = orders-v2 and role = orders-reader for the current producer values. Application must wait for both schema and role, and its schema field must track schema.output when the producer changes to orders-v3 or orders-v4. Audit must not become a prerequisite for application, directly or transitively. Use actual Terraform JSON: an input reference is a string such as ${terraform_data.schema.output}, while depends_on is an array of static resource addresses such as terraform_data.role. You may express the role prerequisite with an explicit dependency while keeping the known role name literal, or consume role.output to establish an implicit dependency and the same effective value. Supported input expressions are exact output traversals, literals, lists and objects; the editor rejects functions, concatenated templates, ID references, extra attributes and provider resource types. Keep exactly the supplied four resources. Run tests and inspect the dependency edges, ready sets and changing-producer probes. File order alone cannot guarantee application readiness. Repair mistakes through normal edits and rerun without Reset.

medium · About 20 min

Lab

Route an ephemeral credential through a write-only consumer

Edit secret.tf.json. Keep required string password and numeric epoch inputs with no defaults. Mark password sensitive and ephemeral. Route the supplied password to password_wo, directly or through ./secret-bridge (input password, ephemeral/sensitive output secret). Remove ordinary password. Keep epoch non-ephemeral and bind password_wo_version to it so probes 2 and 3 both work. Publish only rotation_version with that changing normal counter. Preserve the supplied resource settings and Owner. The editor supports primitive variable declarations, static literals, direct var references, the declared module output and the counter resource attribute; it rejects other expressions. Run tests, inspect each independent failing concern and repair without Reset.

hard · About 30 min

Make TERRAFORM-004 your next step.

Create your free account. Start practising.

Start Free