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
CloudFormation & Others 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.
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.
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.
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.
Pulumi allows engineers to define infrastructure using real programming languages like TypeScript or Python. Benefits include strong integration with existing development workflows, use of familiar programming constructs, and enhanced testability. However, challenges include a steeper learning curve for operations teams and less simplicity compared to purely declarative tools like Terraform. Pulumi is well-suited for DevOps teams with strong software engineering backgrounds.
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 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.
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.
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 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.
CloudFormation StackSets enable centralized deployment of stacks across multiple accounts and regions. They allow consistent infrastructure configuration at scale and simplify enterprise-wide governance. StackSets are especially valuable for multi-account or multi-region AWS architectures.
Terraform and CloudFormation are both powerful Infrastructure as Code tools, but they differ in scope and flexibility. Terraform is cloud-agnostic and supports multiple providers such as AWS, Azure, and GCP using HashiCorp Configuration Language (HCL). CloudFormation, on the other hand, is AWS-specific and uses YAML or JSON templates. Terraform offers greater modularity, reusability, and portability across platforms, while CloudFormation provides deeper native integration with AWS services.
Drift detection in CloudFormation identifies differences between the actual state of resources and their declared configuration in the template. It ensures infrastructure remains consistent with the defined specifications. Drift can occur due to manual changes or external updates. Detecting and correcting drift maintains compliance, reliability, and predictable behavior of automated deployments.
Chef uses a procedural approach through 'recipes' and 'cookbooks' written in Ruby, describing how systems should be configured step by step. Puppet follows a declarative model, where the desired system state is defined, and the engine determines how to achieve it. Puppet's model-driven design is often easier to maintain at scale, while Chef offers more control and flexibility for complex workflows.
Enterprises often combine IaC tools based on their strengths and ecosystem compatibility. Terraform can be used for provisioning multi-cloud resources, CloudFormation for AWS-specific environments, and Ansible for configuration management after resource creation. By defining clear boundaries between provisioning, configuration, and deployment, teams maintain flexibility while ensuring unified governance and automation consistency.