Which tool manages infrastructure state locally by default, requiring explicit remote backend configuration for team collaboration?
Think about which tool uses a state file that can be stored locally or remotely.
Terraform stores state locally by default in a file called terraform.tfstate. Remote backends must be configured for team use. CloudFormation and Pulumi manage state differently.
Which tool allows you to write infrastructure code using general-purpose programming languages like TypeScript, Python, or Go?
Consider which tool integrates with common programming languages for infrastructure definitions.
Pulumi supports writing infrastructure code in languages like TypeScript, Python, Go, and C#. Terraform and CloudFormation use domain-specific languages.
What happens if you update a CloudFormation stack with a template that removes a resource without specifying a deletion policy?
Think about default behavior when a resource is removed from the template.
By default, CloudFormation deletes resources removed from the template during stack update unless a DeletionPolicy is set to retain or snapshot.
Which statement correctly describes secret handling differences between Terraform and Pulumi?
Consider which tool has built-in secret encryption in its backend.
Pulumi encrypts secrets automatically in its backend. Terraform requires configuring remote backends with encryption or using external secret managers.
You need to manage infrastructure across AWS, Azure, and Google Cloud with a single codebase using familiar programming languages. Which tool is best suited for this requirement?
Think about multi-cloud support and language flexibility.
Pulumi supports multiple clouds and lets you write infrastructure code in general-purpose languages, making it ideal for multi-cloud with one codebase. Terraform supports multi-cloud but uses its own language. CloudFormation is AWS-only.