nerdexam
HashiCorpHashiCorp

TERRAFORM-ASSOCIATE-004 · Question #88

TERRAFORM-ASSOCIATE-004 Question #88: Real Exam Question with Answer & Explanation

The correct answer is D: Golden images. The key principle of infrastructure as code that is not listed among the options is golden images. Golden images are pre-configured, ready-to-use virtual machine images that contain a specific set of software and configuration. They are often used to create multiple identical ins

Submitted by akirajp· Apr 18, 2026Understand Infrastructure as Code (IaC) Concepts

Question

Which of the following is not a key principle of infrastructure as code?

Options

  • ASelf-describing infrastructure
  • BIdempotence
  • CVersioned infrastructure
  • DGolden images

Explanation

The key principle of infrastructure as code that is not listed among the options is golden images. Golden images are pre-configured, ready-to-use virtual machine images that contain a specific set of software and configuration. They are often used to create multiple identical instances of the same environment, such as for testing or production. However, golden images are not a principle of infrastructure as code, but rather a technique that can be used with or without infrastructure as code. The other options are all key principles of infrastructure as code, as explained below: Self-describing infrastructure: This means that the infrastructure is defined in code that describes its desired state, rather than in scripts that describe the steps to create it. This makes the infrastructure easier to understand, maintain, and reproduce. Idempotence: This means that applying the same infrastructure code multiple times will always result in the same state, regardless of the initial state. This makes the infrastructure consistent and predictable, and avoids errors or conflicts caused by repeated actions. Versioned infrastructure: This means that the infrastructure code is stored in a version control system, such as Git, that tracks the changes and history of the code. This makes the infrastructure code reusable, auditable, and collaborative, and enables practices such as branching, merging, and

Topics

#Infrastructure as Code#IaC Principles#Idempotence#Version Control

Community Discussion

No community discussion yet for this question.

Full TERRAFORM-ASSOCIATE-004 PracticeBrowse All TERRAFORM-ASSOCIATE-004 Questions