Get the Preplance app for a seamless learning experience. Practice offline, get daily streaks, and stay ahead with real-time interview updates.
Get it on
Google Play
4.9/5 Rating on Store
Infrastructure as Code · Question Set
Terraform Fundamentals interview questions for placements and exams.
Questions
13
Included in this set
Subject
Infrastructure as Code
Explore more sets
Difficulty
Mixed
Level of this set
Go through each question and its explanation. Use this set as a focused practice pack for Infrastructure as Code.
The Terraform state file acts as a source of truth for the deployed infrastructure. It maps resources defined in configuration files to real-world infrastructure resources. The state file enables Terraform to detect changes, plan updates, and perform drift detection accurately. It should be secured and often stored remotely in S3 or similar backends.
For complete preparation, combine this set with full subject-wise practice for Infrastructure as Code. You can also explore other subjects and sets from the links below.
Variables in Terraform allow configuration to be parameterized and reused. They make code more flexible by externalizing values that can change across environments, such as instance types or region names. Variables can be defined in separate files, environment variables, or input prompts.
Providers are the foundation of Terraform’s plugin architecture. They define resources and data sources for specific cloud services or APIs such as AWS, Azure, GCP, or Kubernetes. Terraform uses providers to create, read, update, and delete infrastructure resources using the APIs of these platforms.
Terraform is an open-source tool developed by HashiCorp used for defining, provisioning, and managing cloud infrastructure using code. It allows teams to define infrastructure resources such as networks, virtual machines, and databases in configuration files, which can then be versioned, reviewed, and applied repeatedly in a predictable way.
A resource block defines a specific piece of infrastructure, such as a virtual machine, a subnet, or a storage bucket. Each resource block tells Terraform what infrastructure to create and how to configure it. Resources are the basic building blocks of a Terraform configuration.
The 'terraform init' command initializes the Terraform working directory. It downloads the required provider plugins, sets up backend configuration if defined, and prepares the environment for running Terraform commands. It must be executed before any other Terraform operation like plan or apply.
The 'terraform plan' command shows what Terraform will do before making any changes. It compares the current state file with the configuration files and generates an execution plan. This preview ensures that teams can review and verify infrastructure changes before applying them.
The 'terraform apply' command executes the actions outlined in the plan. It creates, updates, or deletes infrastructure resources to match the desired configuration. The command also updates the state file to reflect the latest deployed infrastructure state after a successful run.
The 'terraform.tfstate' file stores the current state of infrastructure managed by Terraform. It maps Terraform resources to their real cloud counterparts and tracks metadata such as resource IDs. Mishandling this file can cause Terraform to lose track of existing resources, potentially leading to accidental deletion or duplication. For collaboration, it should be stored remotely using secure backends like AWS S3 or Terraform Cloud with proper locking and encryption enabled.
A remote backend in Terraform is a configuration that stores the state file on an external service such as AWS S3, Azure Storage, or Terraform Cloud. It enables team collaboration by providing shared access to the same state file, supports state locking to avoid race conditions, and improves security through encryption. Using a remote backend is essential in production environments to ensure consistency and data safety across multiple users.
Modules in Terraform are reusable units of infrastructure code that group related resources together. They enable teams to define standard patterns such as VPCs, EC2 instances, or security groups once and reuse them across multiple projects. This promotes consistency, simplifies maintenance, and improves collaboration. Modules can be local or sourced from public registries such as the Terraform Registry.
Terraform automatically manages the lifecycle of infrastructure resources based on dependencies it infers from the configuration. When one resource references another, Terraform creates a dependency graph to ensure proper creation and destruction order. The lifecycle meta-argument allows customization of behavior, such as creating before destroying or ignoring certain changes. This precise orchestration makes Terraform safe and reliable for managing complex infrastructure.
A typical Terraform workflow begins with writing configuration files in HCL to define resources. The team initializes the working directory using 'terraform init', creates an execution plan using 'terraform plan', and reviews the changes through code review. Once approved, 'terraform apply' provisions the resources, and the state file is updated in a remote backend. The workflow often integrates with CI/CD pipelines for automated validation and deployment, ensuring traceability, collaboration, and compliance with DevOps practices.