AWS CloudFormation Interview Questions (Top 100 Questions with Answers)
Master AWS CloudFormation Interview Questions with production-oriented questions covering Infrastructure as Code (IaC), templates, stacks, change sets, nested stacks, stack policies, drift detection, rollback, deployments, CI/CD integration, and real-world production scenarios.
Module Navigation
Previous: AWS ECS vs EKS QA | Parent: AWS Learning Path | Next: AWS CloudWatch QA
Introduction
AWS CloudFormation is AWS's Infrastructure as Code (IaC) service that enables you to provision, update, and manage cloud infrastructure using code instead of manually creating resources.
CloudFormation is widely used for
- Infrastructure Automation
- DevOps
- CI/CD
- Disaster Recovery
- Multi-Environment Deployment
- Production Infrastructure
- Cloud Migration
Almost every DevOps and Solution Architect interview includes CloudFormation questions.
This guide contains the Top 100 AWS CloudFormation Interview Questions frequently asked in
- AWS Solution Architect
- DevOps Engineer
- Platform Engineer
- Cloud Engineer
- SRE
- Java Backend Engineer
CloudFormation Learning Roadmap
Infrastructure as Code
│
▼
Templates
│
▼
Stacks
│
▼
Parameters
│
▼
Resources
│
▼
Outputs
│
▼
Nested Stacks
│
▼
CI/CD
│
▼
Production Deployment
CloudFormation Fundamentals
1. What is AWS CloudFormation?
AWS CloudFormation is an Infrastructure as Code (IaC) service used to create and manage AWS resources using templates.
2. Why use CloudFormation?
- Infrastructure Automation
- Repeatability
- Version Control
- Faster Deployments
- Reduced Human Errors
3. What is Infrastructure as Code?
Managing infrastructure through code instead of manual configuration.
4. Which template formats are supported?
- YAML
- JSON
5. What can CloudFormation create?
Almost every AWS resource.
- EC2
- VPC
- RDS
- IAM
- Lambda
- S3
- ECS
- EKS
Templates
6. What is a CloudFormation Template?
A text file describing AWS infrastructure.
7. Main sections of a template?
- AWSTemplateFormatVersion
- Description
- Parameters
- Mappings
- Conditions
- Resources
- Outputs
8. Which section is mandatory?
Resources.
9. What are Parameters?
User inputs supplied during deployment.
10. Why Parameters?
Reusable templates.
11. What are Outputs?
Values returned after stack creation.
12. Common Outputs?
- VPC ID
- ALB DNS
- RDS Endpoint
- S3 Bucket Name
13. What are Mappings?
Static lookup values.
14. Conditions?
Deploy resources only when conditions are true.
15. Metadata?
Stores additional template information.
Stacks
16. What is a Stack?
Collection of AWS resources managed together.
17. Stack Lifecycle?
Create
│
Update
│
Delete
18. Stack Update?
Modifies existing infrastructure.
19. Stack Delete?
Removes managed resources.
20. Stack Events?
Show deployment progress.
Resources
21. What are Resources?
AWS services defined inside templates.
22. Can resources depend on each other?
Yes.
23. DependsOn?
Specifies creation order.
24. Resource Logical ID?
Template identifier.
25. Physical ID?
Actual AWS resource identifier.
Change Sets
26. What is a Change Set?
Preview of infrastructure changes before deployment.
27. Why Change Sets?
Avoid accidental changes.
28. Does Change Set modify resources?
No.
Only previews.
29. Benefits?
Safer production deployments.
30. Production recommendation?
Always review Change Sets.
Nested Stacks
31. What is a Nested Stack?
A CloudFormation stack called from another stack.
32. Why Nested Stacks?
Reuse infrastructure modules.
33. Common modules?
- VPC
- IAM
- Networking
- Security
34. Benefits?
- Reusability
- Smaller templates
- Easier maintenance
35. Parent Stack?
Controls nested stacks.
StackSets
36. What is StackSet?
Deploys CloudFormation stacks across multiple AWS accounts and Regions.
37. Benefits?
Enterprise deployments.
38. Multi-account deployment?
Supported.
39. Multi-region deployment?
Supported.
40. Common use cases?
- IAM
- Networking
- Security Baselines
Drift Detection
41. What is Drift Detection?
Identifies manual changes outside CloudFormation.
42. Why Drift Detection?
Maintain infrastructure consistency.
43. Drift Example?
Engineer manually modifies Security Group.
44. Can Drift fix changes automatically?
No.
It only reports differences.
45. Best Practice?
Avoid manual infrastructure changes.
Rollback
46. What happens when deployment fails?
CloudFormation automatically rolls back by default.
47. Rollback benefits?
Prevents partially deployed infrastructure.
48. Disable Rollback?
Supported for troubleshooting.
49. Stack Failure?
Review Events.
50. Common rollback reasons?
- Invalid IAM permissions
- Resource conflicts
- Quota exceeded
Security
51. IAM Role for CloudFormation?
Allows CloudFormation to create AWS resources securely.
52. Least Privilege?
Recommended.
53. Stack Policy?
Protects critical resources from updates.
54. Termination Protection?
Prevents accidental stack deletion.
55. Secrets?
Use AWS Secrets Manager or Systems Manager Parameter Store.
CI/CD
56. CloudFormation with CodePipeline?
Fully supported.
57. Infrastructure Deployment?
Automated.
58. Version Control?
Git.
59. Rollback Strategy?
Previous template version.
60. Blue-Green Infrastructure?
Supported using separate stacks.
Production Scenarios
61. Developer manually deletes EC2.
CloudFormation Drift Detection identifies differences.
62. Need identical Dev/Test/Prod.
Use reusable templates.
63. Deploy infrastructure in multiple Regions.
Use StackSets.
64. Database update fails.
Rollback protects existing infrastructure.
65. Need reusable VPC.
Use Nested Stack.
66. Parameterize environments.
Use Parameters.
67. Infrastructure changes require approval.
Use Change Sets.
68. Compliance requires infrastructure auditing.
Use CloudTrail and Drift Detection.
69. Multi-account deployment.
Use Organizations + StackSets.
70. Production deployment.
Use CI/CD pipeline.
Architect Questions
71. CloudFormation vs Terraform?
CloudFormation is AWS-native.
Terraform supports multiple cloud providers.
72. CloudFormation vs CDK?
CloudFormation uses declarative templates.
AWS CDK generates CloudFormation using programming languages.
73. CloudFormation vs Manual Deployment?
Automation is faster, repeatable, and less error-prone.
74. CloudFormation vs Elastic Beanstalk?
Beanstalk deploys applications.
CloudFormation provisions infrastructure.
75. CloudFormation vs OpsWorks?
OpsWorks focuses on configuration management.
Advanced Topics
76. Custom Resources?
Extend CloudFormation using Lambda.
77. Macros?
Transform templates before deployment.
78. Dynamic References?
Securely retrieve Secrets Manager or Parameter Store values.
79. Cross Stack References?
Share outputs between stacks.
80. Export/Import?
Used for sharing resources.
Senior Interview Questions
81. Common CloudFormation mistakes?
- Hardcoded values
- Large templates
- Manual changes
- Missing rollback strategy
82. Best Practices?
- Modular Templates
- Parameters
- Nested Stacks
- Version Control
83. Infrastructure Testing?
Deploy to lower environments first.
84. Cost Optimization?
Delete unused stacks.
85. Drift Prevention?
Avoid manual console changes.
86. Large Enterprise Deployment?
Use StackSets.
87. Infrastructure Reusability?
Use Nested Stacks and Modules.
88. CI/CD Best Practice?
Automate template validation and deployment.
89. What should be monitored?
- Stack Events
- Rollbacks
- Drift
- Failed Resources
90. Production Readiness Checklist?
- Parameters
- Change Sets
- Rollback
- Stack Policies
- Monitoring
91. Can CloudFormation create IAM resources?
Yes.
92. Can CloudFormation update existing resources?
Yes.
93. Can CloudFormation import existing resources?
Yes.
Supported for many AWS resource types.
94. CloudFormation Hooks?
Validate infrastructure changes before deployment.
95. Template Validation?
Use validation before deployment.
96. Linting?
Use cfn-lint to validate templates.
97. Common troubleshooting steps?
- Review Stack Events
- Check IAM Permissions
- Validate Template
- Inspect Rollback Logs
98. What do interviewers expect?
- IaC Knowledge
- Automation
- CI/CD Integration
- Production Experience
99. How does CloudFormation improve DevOps?
Infrastructure becomes version-controlled, repeatable, and fully automated.
100. How should you prepare?
- Create VPC templates
- Deploy EC2
- Create RDS
- Configure IAM
- Practice Nested Stacks
- Build CI/CD pipelines
CloudFormation Deployment Flow
Developer
│
▼
Git Repository
│
▼
CodePipeline
│
▼
CloudFormation
│
▼
Create / Update Stack
│
▼
AWS Resources
┌────┼─────┬─────┐
▼ ▼ ▼ ▼
VPC EC2 RDS S3
Production Infrastructure Architecture
CloudFormation Stack
│
┌────────┼─────────┐
▼ ▼ ▼
Network Compute Database
(VPC) (EC2) (RDS)
│ │ │
└────────┼─────────┘
▼
Monitoring
(CloudWatch/CloudTrail)
Quick Revision
| Topic | Key Point |
|---|---|
| CloudFormation | Infrastructure as Code |
| Template | YAML / JSON |
| Stack | Collection of Resources |
| Parameters | User Inputs |
| Outputs | Returned Values |
| Change Set | Preview Changes |
| Nested Stack | Reusable Infrastructure |
| StackSet | Multi-Account Deployment |
| Drift Detection | Detect Manual Changes |
| Rollback | Automatic Failure Recovery |
Interview Tips
During AWS CloudFormation interviews:
- Clearly explain Infrastructure as Code (IaC) and its advantages.
- Understand Templates, Stacks, Parameters, Outputs, and Resources.
- Know when to use Nested Stacks, StackSets, and Change Sets.
- Explain Rollback, Termination Protection, and Drift Detection.
- Discuss integration with CodePipeline, Git, and CI/CD.
- Mention production best practices such as modular templates, version control, parameterization, and avoiding manual infrastructure changes.
Summary
AWS CloudFormation is the foundation of Infrastructure as Code in AWS. Strong CloudFormation interview performance requires understanding templates, stacks, parameters, outputs, change sets, nested stacks, stack sets, rollback, drift detection, CI/CD integration, and production deployment strategies.
Mastering these 100 AWS CloudFormation interview questions prepares you for AWS Cloud Engineer, DevOps Engineer, Platform Engineer, Site Reliability Engineer, Infrastructure Engineer, and Solution Architect interviews.