Q: Provide three immutable infrastructure practices.
Never SSH and patch: If an EC2 instance needs a security update or a configuration change, you never SSH into the live server to run apt-get upgrade or edit a config file. This creates "snowflakes".
Want to master this scenario in a live sandbox? The Linux Foundation's Certified System Administrator (LFCS) & SRE Track covers this exact problem with hands-on terminal drills.
🛠️ Production Runbook & Step-by-Step Resolution
Direct Answer: "Senior DevOps is about building reliable automated feedback loops between code commit and production observability. The interviewer is testing: Pet vs Cattle concept, Configuration Management vs Baking AMIs.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."
Initial Diagnostics & Root Cause Analysis
- Never SSH and patch: If an EC2 instance needs a security update or a configuration change, you never SSH into the live server to run
apt-get upgradeor edit a config file. This creates "snowflakes". - Bake Images (AMI Builder/Packer): The new configuration is scripted via Packer or Docker. A fresh, fully-configured Amazon Machine Image (AMI) or Docker Image is stamped out into an artifact registry.
- Replace, don't update: The infrastructure orchestrator (Terraform/Auto Scaling Group) terminates the old instances completely and spawns identical fresh instances from the newly baked image.
Remediation & Permanent Safeguards
Execute the resolution runbook and verify workload health:
- Never SSH and patch: If an EC2 instance needs a security update or a configuration change, you ne...
- Bake Images (AMI Builder/Packer): The new configuration is scripted via Packer or Docker. A fresh...
- Replace, don't update: The infrastructure orchestrator (Terraform/Auto Scaling Group) terminates ...
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
- Engineering bespoke in-house developer tools instead of adopting standardized platform Golden Paths when configuring General Provide three Bespoke internal tools create long-term maintenance debt and fragmented workflows, whereas standardized Golden Paths accelerate delivery.
- Overlooking infrastructure cost visibility and FinOps allocation tagging across multi-tenant environments when configuring General Provide three Without granular resource tagging, engineering organizations cannot attribute cloud infrastructure costs to specific teams or business units.
- Failing to define explicit Service Level Objectives (SLOs) and Error Budgets to balance feature velocity with reliability when configuring General Provide three Without agreed SLOs, engineering and product teams lack an objective data-driven framework to prioritize technical debt over new features.
- Neglecting automated continuous drift detection between declarative configuration and deployed cloud state when configuring General Provide three Unmanaged drift accumulates over time, causing future automated deployments to fail or overwrite emergency manual adjustments.