APURV
  • Home
  • Journey
  • Projects
  • Blogs
  • Interview
  • Exams
Resume
APURV

Building scalable, secure, and production-ready cloud infrastructure. Automation first.

NAVIGATION

HomeExperienceProjectsCertificationsSkills

TECH STACK

AWSGCPK8sCI/CDLinuxDocker

CONNECT

LinkedInGitHubEmailResume

© 2026 Apurv Gujjar. All rights reserved.
Apurv Gujjar
Apurv GujjarDevOps & Cloud Engineer
|Interview Documentation
Portfolio
Handbooks
🎯Linux🐙Git & GitHub🤖GitHub Actions🌐Networking☁AWS🛠Terraform🐳Docker☸Kubernetes📊Monitoring🛡DevSecOps💰Cost Optimization🚨Incident Scenarios👤HR & Behavioral☁GCP🐍Python
Interview DocumentationIncident Scenarios

Incident Scenarios

Production Incident Triage & Root Cause Analysis Scenarios

Q1

Incident: CPU is at 100% utilization. How do you troubleshoot?

💬Answer
  1. Identify Bottleneck Process: Run top or htop to identify the processes consuming the most CPU.
  2. Investigate Thread Details: Press H in top to view individual threads.
  3. Trace System Calls: Run strace -p <PID> to see system calls made by the process.
  4. Identify Core Source: Match the process ID against logs. If it is Java, run jstack <PID> to dump threads and identify code bottlenecks.
  5. Mitigate: If the process is not critical, kill it (kill -9 <PID>). Otherwise, scale up or restart the service.
Q2

Incident: Memory leak investigation. How do you diagnose?

Q3

Incident: Disk is 100% full. How do you recover?

Q4

Incident: Database connection exhaustion. How do you resolve?

Q5

Incident: Kubernetes Pod is in CrashLoopBackOff. How do you debug?

Q6

Incident: Kubernetes Node is in NotReady state. How do you troubleshoot?

Q7

Incident: Kubernetes Pod is stuck in Pending state. Why?

Q8

Incident: High API latency. How do you identify the bottleneck?

Q9

Incident: DNS resolution failure. How do you diagnose?

Q10

Incident: Load balancer unhealthy backends. How do you resolve?

Q11

Incident: Terraform state corruption. How do you recover?

Q12

Incident: CI/CD pipeline failure. How do you troubleshoot?

Q13

Incident: Application 502 Bad Gateway. How do you resolve?

Q14

Incident: Application 504 Gateway Timeout. How do you troubleshoot?

Q15

Incident: SSL certificate expiry. How do you quickly resolve?

Q16

Incident: Production deployment failed. How do you execute a rollback?

Q17

Incident: Data corruption in database. What is the DR recovery flow?

Q18

Incident: Region outage. How do you execute disaster recovery?

Q19

Incident: Ransomware attack. How do you recover?

Q20

Incident: Secrets leaked to public GitHub repository. What do you do?

Q21

Describe your approach to handling data migrations in a continuous deployment pipeline.

Apurv Gujjar - DevOps & Cloud Engineer
Created by

Apurv Gujjar

DevOps & Cloud Engineer

Specialized in:DevOpsAWSGCPKubernetesTerraformDocker
View Portfolio