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
Tech Mahindra · Infrastructure as Code
Practice Infrastructure as Code questions specifically asked in Tech Mahindra interviews – ideal for online test preparation, technical rounds and final HR discussions.
Questions
20
Tagged for this company + subject
Company
Tech Mahindra
View company-wise questions
Subject
Infrastructure as Code
Explore topic-wise practice
Go through each question and its explanation. Use this page for targeted revision just before your Tech Mahindra Infrastructure as Code round.
Remote backends allow teams to store state files in a shared location like AWS S3 or Terraform Cloud. They enable collaboration by preventing concurrent updates through state locking and ensure secure, versioned, and centralized management of Terraform state. This avoids conflicts and inconsistencies during team operations.
For complete preparation, combine this company + subject page with full company-wise practice and subject-wise practice. You can also explore other companies and topics from the links below.
Pulumi is a modern IaC tool that lets developers define infrastructure using general-purpose languages such as TypeScript, Python, or Go. Unlike Terraform or CloudFormation, which rely on declarative syntax, Pulumi embraces imperative programming constructs, making it attractive for developer-centric workflows.
Terraform interacts with AWS using the AWS provider, which communicates via AWS APIs. The provider plugin translates Terraform configuration into API requests that create, update, or delete resources in AWS, ensuring accurate and secure provisioning through programmatic interfaces.
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.
Declarative IaC tools describe the desired end state of infrastructure, letting the system handle the process to reach it (for example Terraform or CloudFormation). Imperative tools describe step-by-step procedures to create resources (for example Ansible or shell scripts). Understanding this difference helps choose tools based on control versus simplicity.
Configuration drift occurs when the actual infrastructure state changes without being reflected in the IaC definitions. It often happens due to manual changes or failed updates. Detecting and correcting drift ensures reliability and consistency across environments.
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 'depends_on' meta-argument is used when Terraform cannot automatically infer dependencies from code. It explicitly defines the order in which resources should be created or destroyed. This ensures Terraform builds infrastructure in a safe and predictable manner, avoiding resource conflicts.
Ansible is agentless because it connects to target systems using standard protocols like SSH or WinRM instead of installing and maintaining separate agents. This simplifies setup, reduces maintenance overhead, and improves security by minimizing running processes on managed nodes.
The inventory file is a key component in Ansible that defines which hosts or groups of hosts the automation will target. It can be static (written in INI or YAML) or dynamic (generated from cloud APIs). Inventory files make it easy to manage servers at scale and apply playbooks selectively.
Roles help structure Ansible projects by organizing related automation content. Each role contains tasks, variables, templates, files, and handlers. Roles promote modularity and reusability, allowing teams to share and maintain clean, maintainable code bases across multiple playbooks or environments.
A CloudFormation template is a declarative JSON or YAML file that defines the structure and configuration of AWS resources. It describes parameters, resources, mappings, conditions, and outputs to create complete infrastructure stacks in a consistent, automated manner.
Parameters in CloudFormation templates make templates dynamic and reusable. They allow users to provide input values during stack creation, such as instance types, region names, or key pairs. This promotes reusability and reduces duplication of templates across environments.
The 'terraform validate' command checks whether configuration files are syntactically correct and internally consistent. It helps catch simple mistakes before running a plan or apply, preventing runtime errors and failed deployments.
Jenkins is widely used to automate Infrastructure as Code workflows. Pipelines can execute Terraform commands such as init, plan, and apply, or run Ansible playbooks for configuration management. Jenkins integrates with version control and approval gates, enabling automated, reliable, and auditable infrastructure delivery.
GitLab CI/CD automates IaC workflows using YAML-defined pipelines that execute Terraform or Ansible commands. It supports pipeline stages for validation, planning, approval, and apply, enabling policy control and audit trails. GitLab Runners execute jobs in isolated environments, maintaining security and reliability.
Sensitive data must never be stored in plaintext or version control. Instead, organizations use secret management tools such as HashiCorp Vault, AWS Secrets Manager, or Azure Key Vault. These systems store credentials securely and integrate with IaC pipelines to inject secrets dynamically at runtime, maintaining security compliance.
Open Policy Agent is an open-source framework for writing and enforcing policies across systems. OPA integrates with IaC tools like Terraform and Kubernetes to evaluate configurations against predefined compliance and security policies. It allows teams to automate enforcement of security standards during build or deployment stages.
Helm is a package manager for Kubernetes that simplifies deployment and management of applications. Helm uses versioned templates called charts to define complex Kubernetes applications as reusable, parameterized packages, improving maintainability and deployment speed.
Ansible uses 'block', 'rescue', and 'always' blocks to handle errors gracefully. Tasks in the block are executed normally; if a failure occurs, the rescue section runs recovery steps. The always section executes regardless of success or failure, ensuring predictable cleanup operations.