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
Infosys · Infrastructure as Code
Practice Infrastructure as Code questions specifically asked in Infosys interviews – ideal for online test preparation, technical rounds and final HR discussions.
Questions
32
Tagged for this company + subject
Company
Infosys
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 Infosys Infrastructure as Code round.
The '-debug' flag provides detailed logs of Terraform's execution process. It helps developers trace variable evaluations, provider interactions, and API requests. This is useful when diagnosing issues with resource dependencies or unexpected provisioning behavior.
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.
Azure Resource Manager (ARM) templates are JSON files that declaratively define Azure resources and configurations. They enable consistent, repeatable deployments of cloud infrastructure and integrate with Azure DevOps pipelines for automation and governance.
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.
Playbooks are YAML-formatted files that describe the automation tasks Ansible performs on hosts. They contain plays, which map groups of hosts to roles, and tasks, which define the steps required to reach the desired system state. Playbooks are human-readable and form the foundation of Ansible automation.
Chef and Puppet are configuration management tools that automate the setup, deployment, and management of servers. They define system states either declaratively (Puppet) or through recipes (Chef), ensuring consistent environments and reducing manual configuration drift.
Policy as Code ensures that security and compliance requirements are automated and consistent. Tools like HashiCorp Sentinel or Open Policy Agent evaluate infrastructure plans against organizational rules, such as enforcing encryption, disallowing public buckets, or requiring tags. This helps prevent misconfigurations before reaching production.
Configuration drift occurs when manual or external changes alter the infrastructure outside of IaC control. This can create security vulnerabilities if outdated or unauthorized configurations remain active. Regular drift detection ensures infrastructure remains compliant with declared, secure baselines.
Kustomize allows developers to reuse and modify existing Kubernetes YAML files without creating separate copies. By layering configurations, it supports environment-specific customization (for example, dev, staging, production) while maintaining a single source of truth for base templates.
Infrastructure as Code, or IaC, is a DevOps practice that automates infrastructure provisioning through machine-readable configuration files or code. Instead of manual setup, engineers define and manage environments programmatically, ensuring consistency, scalability, and reproducibility across all deployments.
Idempotency ensures that executing IaC repeatedly results in the same final infrastructure without unwanted changes. This makes automation safe and predictable. Tools like Terraform and Ansible enforce idempotency to prevent resource duplication or accidental modification of existing configurations.
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.
Jenkins is a continuous integration and delivery tool, not an IaC tool. Terraform, Ansible, and CloudFormation are examples of Infrastructure as Code tools used to define and manage infrastructure resources programmatically.
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.
Modules in Terraform help encapsulate reusable infrastructure components like networks, security groups, or compute instances. They simplify large configurations, enforce best practices, and ensure consistency across multiple environments. Teams can publish modules internally or use verified public modules from the Terraform Registry.
Terraform workspaces allow managing multiple environments from the same configuration code by maintaining separate state files. This approach simplifies environment isolation without duplicating code, making it easier to manage lifecycle changes and reduce errors in environment promotion pipelines.
The 'prevent_destroy' lifecycle argument in Terraform ensures that critical resources cannot be deleted accidentally. When this argument is set to true, any attempt to delete the resource will fail unless explicitly overridden. It is commonly used for protecting production databases or key infrastructure components.
Ansible is an open-source automation tool used for configuration management, software provisioning, and application deployment. It allows teams to define desired infrastructure and system states through YAML-based playbooks, ensuring consistent, repeatable, and error-free operations across multiple servers.
Idempotency ensures that running the same Ansible task multiple times does not change the system after it reaches the target state. This guarantees predictability and safety, as repeated executions of playbooks will not break or reconfigure systems unnecessarily.
Handlers are special tasks in Ansible that run only when notified by other tasks. They are typically used to restart or reload services after a configuration change. This mechanism ensures that updates happen only when necessary, improving efficiency and reliability of deployments.
AWS CloudFormation is a service that enables users to define and provision AWS resources in a declarative way using templates. It automates resource creation, updates, and deletion, ensuring consistency and repeatability across environments. Templates can be written in JSON or YAML and represent the desired infrastructure state.
A CloudFormation stack is a collection of AWS resources that are created, updated, and deleted as a single unit. Stacks simplify lifecycle management by linking related resources through one template. Updating or deleting a stack ensures consistent changes across the defined environment.
The Outputs section in CloudFormation defines key information that users might need after stack deployment. For example, it can output a load balancer DNS name or an S3 bucket URL. Outputs help integrate stacks or provide references for dependent infrastructure components.
Infrastructure as Code integrates into CI/CD pipelines by automating the provisioning, validation, and deployment of infrastructure components. This ensures that both application and infrastructure changes are version-controlled, tested, and deployed together, achieving full end-to-end automation and environment consistency.
GitHub Actions enable automation of Infrastructure as Code tasks directly in the repository. Developers can trigger workflows on pull requests or commits to validate Terraform plans, deploy CloudFormation stacks, or run Ansible playbooks. This provides a lightweight CI/CD solution integrated with version control.
Terraform plan validation in CI/CD pipelines ensures infrastructure changes are reviewed before they are applied. The plan step compares current and desired states, helping teams catch misconfigurations early. This improves quality control and reduces production risks during automated deployments.
In CI/CD pipelines, the apply or deploy stage is responsible for executing Terraform apply or equivalent commands. It performs actual infrastructure changes after successful validation and approvals, ensuring predictable and automated deployment workflows.
IaC automates the deployment of large infrastructure environments, which includes security-sensitive resources such as networks, IAM roles, and databases. Without proper governance, automated configurations can accidentally expose data, weaken access controls, or create unmonitored resources. Therefore, integrating security into every stage of the IaC lifecycle is essential.
IaC enables organizations to define infrastructure configurations once and deploy them across multiple cloud environments consistently. This reduces vendor lock-in and improves flexibility by standardizing provisioning processes across AWS, Azure, and GCP, ensuring portability and reproducibility.
The Ansible 'debug' module prints variables or custom messages during playbook execution. It helps troubleshoot variable values, task outputs, and logical conditions, making it easier to diagnose playbook behavior and fix configuration issues.
Storing Infrastructure as Code in version control enables collaboration, code review, and history tracking. It ensures every infrastructure change is auditable and reversible, aligning infrastructure management with software development best practices.