Repair deployment ordering and changing schema values
A hands-on TERRAFORM-004 lab. You produce the real artefact and 10 automated checks verify it behaves the way the exam expects.
Try this labAll TERRAFORM-004 practice
- Certification
- TERRAFORM-004
- Format
- Structured configuration
- Difficulty
- medium
- Estimated time
- 20 min
- Automated checks
- 10
The brief
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.
What the checks verify
Your work is graded on 10 independent properties, not on matching one reference answer.
- The artifact uses supported Terraform JSON resource blocks and expressions.
- Exactly the four supplied resources remain declared.
- All dependency references resolve and the graph is acyclic.
- The schema producer keeps its required input orders-v2.
- The role producer keeps its required input orders-reader.
- The current application input evaluates to the required schema and role values.
- Reader role is a guaranteed predecessor of application.
- Schema is a guaranteed predecessor and application follows its output under two changed-producer probes.
- Audit keeps its independent security-log input.
- Audit is outside application's direct and transitive prerequisite chain.
Where this sits in the TERRAFORM-004 blueprint
- Domain
- Terraform configuration
- Objective
- Dependency and Conditions
- Skill
- Ordering, Lifecycle and Custom Conditions
Part of TERRAFORM-004 preparation
Labs are written by ExamNova to teach the decisions the exam tests. They are not reproductions of vendor lab content.