Most Asked DevOps Interview Questions

261. How terraform contribute to managing resources in different cloud platforms or infrastructure providers?

Terraform simplifies managing resources across different cloud platforms or infrastructure providers by providing a unified way to define infrastructure configurations. With Terraform, users can use a single set of configuration files to provision and manage resources on AWS, Azure, Google Cloud, and other providers. This allows for consistency, scalability, and ease of management, as changes can be applied uniformly across diverse environments without the need for platform-specific tools or scripts.

262. What is the best way to store cloud providers (ex: AWS, GCP or Azure) Access Key and Secrect Key?

The best way to store cloud provider access keys and secret keys is to use a secure and centralized secrets management service provided by the respective cloud platform. For example, AWS provides AWS Secrets Manager, Google Cloud offers Secret Manager, and Azure offers Azure Key Vault. These services encrypt and store sensitive credentials, allowing for secure access and management while ensuring compliance with security best practices.

263. Describe the basic structure of a Terraform configuration file?

Terraform configuration file define the infrastructure resources that Terraform will manage.
Example:
resource "aws_instance" "example" {
    ami = "ami-0c55b159cbfafe1f0"
    instance_type = "t2.micro"
}

264. What language is used to write terraform configurations file?

Terraform configuration files are primarily written in HashiCorp Configuration Language (HCL).

265. What is 'state' in terraform?

In Terraform, "state" refers to a snapshot of your infrastructure's current status and configuration. It's stored in a file named 'terraform.tfstate' by default and helps Terraform to keep track of what resources are created and how they're configured.

266. How does Terraform maintain state?

Terraform maintains state by keeping track of the current state of your infrastructure in a state file. This file is usually stored locally or remotely (e.g., in cloud storage) and records the mapping between the resources in your configuration files and the real-world infrastructure. This state file allows Terraform to understand what changes need to be made to your infrastructure when you run commands like terraform apply or terraform destroy.

267. How will you manage state and how it impacts on managing infrastructure?

Managing state in Terraform involves storing information about your infrastructure in a file (commonly terraform.tfstate) and ensuring it's handled securely and consistently. The suggested way to manage Terraform state files is by using Terraform's built-in support for remote backends, such as Amazon S3, Azure Blob Storage, or Terraform Cloud. This approach provides improved collaboration, increased security, and better data protection for your infrastructure resources.

This impacts infrastructure management by providing a reliable record of the deployed resources, enabling Terraform to accurately plan and execute changes, and facilitating collaboration among team members.

268. List the purpose of some terraform commands.

• init: Initializes Terraform in a directory.
• plan: Shows changes Terraform will make.
• apply: Applies changes to infrastructure.
• destroy: Destroys Terraform-managed infrastructure.
• validate: Validates Terraform configuration files.
• output: Shows output values from Terraform configuration.

269. What is the purpose of the Terraform plan, and how is it generated?

Terraform generates the plan by comparing the desired state defined in your configuration files with the current state of your infrastructure. It analyzes the differences and presents them in a human-readable format, detailing what resources will be created, modified, or deleted.

270. Explain the significance of the "terraform apply" command and the steps involved in applying changes to the infrastructure.

• Planning: Terraform generates a plan to show what changes will be made.
• Confirmation: You confirm to proceed with the changes.
• Execution: Terraform applies the changes, creating, modifying, or deleting resources as necessary.
• Completion: Terraform provides a summary of the actions taken and any outputs generated from the changes.