Cloud Engineer interview question · Most asked
How would you use infrastructure as code across clouds?
Summary
Terraform (or OpenTofu) for multi-cloud with provider-specific modules behind consistent interfaces; native tools (CloudFormation/CDK, Bicep, Google Infrastructure Manager) when staying on one cloud. Keep state remote and locked, pin versions, plan in CI, apply the reviewed plan, and split state by component.
Longer Answer
Don't try to abstract all clouds into one module; share conventions (naming, tagging, structure) instead.
Key Points
- Terraform for multi-cloud.
- Native tools for single-cloud.
- Remote locked state, CI plans.
- Share conventions, not abstractions.
Deep dive: Terraform in Production
Explanation
What interviewers look for
Practical IaC operating model.
More most-asked Cloud Engineer questions
- What do Multi-AZ deployments and read replicas give you for managed databases?
- Explain RTO and RPO and the four disaster recovery strategies.
- What are regions and availability zones, and how do you use them for resilience?
- How do you eliminate long-lived credentials in a cloud environment?
- How do you keep object storage buckets from being exposed publicly?
- How do you approach cloud cost optimisation?
- How is an AWS IAM request evaluated when several policies apply?
- What security services and settings belong in every cloud account from day one?