Mohamed Ibrahim

I once asked this in a Terraform / IaC interview... Q: Your Terraform apply fails with “Error acquiring the state lock”. How do you troubleshoot? A: I’d check if another Terraform process is running or if a previous run crashed. For remote state, I’d verify the backend (like S3 + DynamoDB) and manually release the lock if needed. Q: Terraform keeps recreating a resource even though nothing changed. What’s going on? A: It’s usually caused by drift, computed fields, or improper lifecycle settings. I’d run terraform plan, inspect diffs, and use lifecycle { ignore_changes = [] } if required. Q: Your Terraform apply fails due to dependency issues between resources. Why might that happen? A: Terraform may not infer dependencies automatically. I’d explicitly define them using depends_on to ensure correct resource creation order. Q: Terraform state doesn’t match the real infrastructure. How do you fix it? A: I’d use terraform refresh or terraform import to sync existing resources into state instead of recreating them. Q: You changed a variable value, but Terraform isn’t picking it up. What’s wrong? A: The variable might be overridden by a .tfvars file, environment variable, or default value. I’d check variable precedence and confirm the correct values are being passed. Q: A Terraform module works locally but fails in CI/CD. Why? A: The CI environment might be missing provider credentials, backend configuration, or required environment variables. I’d compare local and pipeline configs. Q: Terraform apply is slow when managing large infrastructure. How do you optimize it? A: I’d split the configuration into smaller modules, use targeted applies carefully, and store state remotely to improve performance and collaboration. Q: Someone manually modified a resource created by Terraform. How do you handle it? A: I’d detect the drift using terraform plan, decide whether to keep or revert the change, and either update the code or let Terraform reapply the desired state. What is covered: DevSecOps, Cloud, Containerization, IaC, GitOps, MLOps

18

Is Terraform the Backbone of Modern Infrastructure as Code? If you work with cloud infrastructure, chances are you’ve come across Terraform. It’s one of the most widely used tools for managing environments. Everything starts with a few simple files: main.tf, variables.tf, provider.tf, outputs.tf, and more. The terraform state file usually stored securely in the cloud keeps track of what’s actually deployed. What really makes Terraform powerful is its cloud-agnostic nature. Whether you’re using AWS, Azure, or GCP, you can manage everything through a single workflow without being tied to one provider. Why It Matters? 1.Consistency Infrastructure is defined as code, no manual setup or “it works on my machine” issues. 2.Version Control All changes are tracked in Git for easy collaboration and rollback. 3.Scalability  Adjust resources or environments in minutes as business needs evolve. 4.Cloud Agnostic  One tool and syntax for multiple clouds. 5.Modularisation Terraform encourages reusable, composable modules meaning teams can define a standard building block (like a VPC, Database, or Kubernetes cluster) once and reuse it across multiple projects. This saves time, reduces duplication, and ensures every environment follows the same best practices something that’s harder to achieve with tools like CloudFormation or ARM templates, where reuse and portability are more limited. What to take? Whether you’re spinning up a new Kubernetes cluster, testing disaster recovery, onboarding a client environment, or rolling out a multi-cloud strategy. Terraform makes it simple, repeatable, and reliable. At the end of the day, whether it’s a small tweak or a full-scale deployment. Terraform just works. Do you agree? #DevOps #Learning #Terraform #Infrastructure #Consistency #VersionControl #Scalability #Resilience #CoderCo #SystemsThinking

12

🚀 Scaling Terraform? You Need Terragrunt. As Terraform projects grow, code duplication, state management, and environment sprawl become real challenges. That’s where Terragrunt comes in. In this video, I explain: ✅ How Terragrunt enforces the DRY principle ✅ Centralized provider & backend configuration ✅ Separate state files to reduce blast radius ✅ Managing dependencies (VPC → EC2) cleanly ✅ Running infrastructure changes across environments at scale If you’re working on production-grade cloud infrastructure, this is a must-watch. 🎥 Watch the full video here: 👉 https://lnkd.in/gzpEVYyx #Terraform #Terragrunt #DevOps #InfrastructureAsCode #AWS #CloudEngineering

9

1 Comment

Struggling to explain a Terraform-based production infrastructure pipeline in your DevOps or SRE interviews? You’re not alone. I just dropped a new video that walks you through a real-world Terraform + Terragrunt workflow, fully integrated with GitLab CI/CD and Atlantis, so you can confidently explain how production infrastructure is built, reviewed, and deployed. In this video, you’ll see exactly how to: ✅ Connect Terraform, Terragrunt, and Atlantis in a production-grade setup ✅ Map out GitLab CI pipeline stages for infrastructure provisioning ✅ Demonstrate code review, plan, and apply workflows via merge requests ✅ Set up multi-environment IaC (Dev, Staging, Prod) following best practices Whether you’re preparing for a DevOps, SRE, or Cloud Engineer interview, this walkthrough gives you the perfect terraform implementation on an enterprise level. 🎥 Watch the full video and get interview-ready: https://lnkd.in/g4_8-khX If you’re serious about nailing your DevOps interviews, this video is a must-watch. #DevOps #SRE #SiteReliabilityEngineering #Terraform #Terragrunt #Atlantis #GitLabCI #InfrastructureAsCode #IaC #CloudEngineering #CloudInfrastructure #DevOpsInterview

2

Nobody told me #DevOps wasn’t just pipelines and YAML files. It’s convincing a team to trust your automation. It’s chasing bugs at 2 AM that weren’t your fault. It’s explaining to non tech leads why downtime isn’t just “a quick fix.” #DevOps isn’t a toolset. It’s a mindset, calm under pressure, clarity in chaos. So if you’re in this field and feel invisible or overwhelmed, you’re not alone. The smartest #DevOps #engineers I know aren’t the loudest. They’re the ones holding the system together quietly. Keep building. You’re seen. #DevOps #SRE #CloudEngineering #TechLife #Infra #DevOpsEngineer #Observability #BuildInPublic

26

3 Comments