🎯 New: Beginner Roadmap added  ·  Start Here →   ·   🗺️ Mind Map   ·   📸 Instagram   ·   ☕ Support
Advertisement
Free · No Login · Updated Weekly

Master DevOps & SRE
from Zero to Interview-Ready

Interactive mind maps, 90+ interview Q&As, real commands, and step-by-step guides across 19 tools — everything a new or experienced DevOps engineer needs, completely free.

🟢 New to DevOps? Start Here 🗺️ Interactive Mind Map 🎯 Interview Kit

No account needed · Works on mobile

19+
Tools Covered
90+
Interview Q&A
120+
Real Commands
10
Deep-Dive Guides
1.3K+
Community
// Start Here

New to DevOps? Follow This Roadmap

A step-by-step learning path from complete beginner to interview-ready. Each step links to a free guide.

🐧
Step 1 — Linux Fundamentals BEGINNER

File permissions, process management, shell scripting, SSH, cron jobs — the foundation everything else is built on.

🌿
Step 2 — Git & Version Control BEGINNER

Branching strategies, rebase vs merge, GitFlow vs trunk-based — the first tool every DevOps engineer needs.

🐳
Step 3 — Docker & Containers INTERMEDIATE

Dockerfiles, image layers, multi-stage builds, docker-compose, container security — containerise everything.

☸️
Step 4 — Kubernetes INTERMEDIATE

Pods, Deployments, Services, RBAC, health probes, HPA — the orchestrator that runs everything at scale.

⚙️
Step 5 — CI/CD Pipelines INTERMEDIATE

Jenkins, GitHub Actions, ArgoCD — automate build, test, and deploy so your team ships faster with confidence.

🏗️
Step 6 — Terraform & IaC ADVANCED

Infrastructure as Code with Terraform — provision cloud infra reproducibly. Remote state, modules, workspaces.

☁️
Step 7 — Cloud (AWS / Azure) ADVANCED

EC2, EKS, IAM, VPC, S3, CloudWatch — where real-world DevOps lives. Cloud is not optional.

📊
Step 8 — Monitoring & Observability ADVANCED · FINAL BOSS

Prometheus, Grafana, SLOs, error budgets — know when things break before your users do.

📖 Read the full DevOps Beginner Guide →

18-Tool Interview Quick Reference

Click any tool card for key concepts, real commands, and interview Q&A with full answers.

🎯 Crack Your Next DevOps / SRE Interview

Daily tips, mock interviews & community-driven prep resources.
Follow for free content. Book a session for focused prep.

Advertisement

🚀 DevOps & SRE Interview Quick Reference

Complete revision notes for all 18 tools — built by @master.devops. Click any card for key concepts, commands, and interview Q&A.
Follow @master.devops on Instagram for daily tips & new resources.

Revision progress 0 / 18 reviewed

Free DevOps & SRE Interview Reference Guide

DevOps Interview Kit is a free, comprehensive reference built for engineers preparing for DevOps, SRE, Platform Engineering, and Cloud Engineering interviews. Every section is written from real interview experience — not copied from documentation. Covers 18 tools with key concepts, important commands, architecture patterns, and curated interview Q&As with full answers.

Whether you're targeting a Senior SRE role, a Platform Engineer position, or a DevOps Engineer role at a product-based company, this guide covers the tools and concepts that consistently appear in technical interviews across all levels. Built and maintained by @master.devops — a DevOps education community sharing real production knowledge, free for everyone.

Tools & Topics Covered

Click any tool above to access the full reference. Below is a summary of what each section covers.

☸️
Kubernetes

Pod lifecycle, Deployments vs StatefulSets vs DaemonSets, Services and Ingress, RBAC and ServiceAccounts, HPA, liveness vs readiness probes, NetworkPolicy, PersistentVolumes, and common troubleshooting scenarios including CrashLoopBackOff and OOMKilled.

🐳
Docker

Dockerfile best practices, multi-stage builds, minimal base images (alpine, distroless), layer caching, CMD vs ENTRYPOINT, Docker networking (bridge, host, overlay), named volumes vs bind mounts, security hardening with non-root users and read-only filesystems.

☁️
AWS

EC2 instance types and placement groups, VPC design with subnets and NAT, IAM roles and policies, S3 storage classes and lifecycle rules, EKS cluster architecture, Lambda functions and event sources, RDS Multi-AZ vs Read Replicas, CloudWatch and Auto Scaling.

🔷
Azure

AKS architecture, Azure DevOps pipelines vs GitHub Actions, App Service plans, Virtual Networks and NSGs, Azure Key Vault and Managed Identity, Azure Load Balancer vs Application Gateway, Azure Monitor and Log Analytics, Entra ID (formerly Azure AD) and RBAC.

🏔️
Terraform

Providers, resources, data sources, and variables. Remote state with S3 and DynamoDB locking. Modules for reusability. Workspaces for environment isolation. Import existing infrastructure. Terraform plan/apply/destroy lifecycle. State manipulation and taint commands.

🔄
ArgoCD

GitOps principles and ArgoCD architecture. Application CRD, sync policies (auto vs manual), self-healing, and pruning. App-of-apps pattern for multi-cluster management. Image Updater for automated tag promotion. Handling secrets in GitOps pipelines with External Secrets Operator.

⚙️
GitHub Actions

Workflow YAML structure, triggers (push, pull_request, schedule, workflow_dispatch), jobs and steps, secrets and OIDC for passwordless cloud auth, actions/cache for speed, matrix builds for parallel testing, reusable workflows, and concurrency controls.

🏗️
Jenkins

Declarative vs Scripted Pipelines, Jenkinsfile structure, agents and node labels, shared libraries for DRY pipelines, credential binding, upstream/downstream jobs, Blue Ocean UI, parallel stages, and integration with SonarQube, Nexus, and Kubernetes agents.

Helm

Chart structure (Chart.yaml, values.yaml, templates), Go templating syntax, values override hierarchy (--set vs -f vs defaults), helm upgrade --install for idempotent CI deploys, rollback via helm history, lifecycle hooks for database migrations, and OCI chart repositories.

📊
Prometheus & Grafana

Prometheus data model (metrics, labels, timestamps), scrape configurations, PromQL query language, recording rules for expensive queries, Alertmanager routing and inhibition, Grafana dashboards and data sources, and the four golden signals: latency, traffic, errors, saturation.

🌿
Git

Branching strategies (GitFlow vs trunk-based development), rebase vs merge and when to use each, interactive rebase for squashing commits, git reflog as a safety net, cherry-pick, bisect for bug hunting, and branch protection rules for team workflows.

🐧
Linux

File permissions and ownership (chmod, chown, umask), process management (ps, kill signals, systemctl), networking tools (ss, ip, dig, curl), log analysis with journalctl, cron jobs and scheduling, performance analysis with top/vmstat/iostat, and shell scripting fundamentals.

🔍
SonarQube

SAST analysis, quality gates and quality profiles, bugs vs vulnerabilities vs code smells vs security hotspots, test coverage integration with JaCoCo and pytest-cov, Jenkins and GitHub Actions integration, branch analysis, and technical debt measurement.

🛡️
OWASP / DevSecOps

OWASP Top 10 with mitigations, shift-left security principles, SAST vs DAST, complete DevSecOps pipeline stages: Gitleaks for secret scanning, SonarQube for SAST, OWASP Dependency-Check for SCA, Trivy for image scanning, and OWASP ZAP for DAST.

📦
JFrog Artifactory

Binary repository management, repository types (local, remote, virtual), artifact promotion from snapshot to release, retention policies, integration with Maven, Docker, npm and pip, Xray scanning for CVEs, and build information for full traceability.

🔭
Splunk

SPL (Search Processing Language) for log analysis, Universal and Heavy Forwarders for log collection, index management, dashboards and visualizations, saved searches and scheduled alerts, field extractions, and Splunk as a SIEM for security event correlation.

🎯
SRE Concepts

SLI, SLO, SLA definitions and relationships, error budget calculation and usage, burn rate alerting, MTTR and MTBF, blameless post-mortem structure, toil definition and reduction strategies, deployment strategies (blue-green, canary, rolling), and incident management workflows.

🏗️
Maven & Build Tools

Maven build lifecycle phases, dependency scopes (compile, runtime, provided, test), BOM (Bill of Materials) for version management, multi-module projects, SNAPSHOT vs RELEASE artifact promotion, plugin configuration, and Gradle comparison for DevOps interviews.

Sample Interview Questions & Answers

The following are representative questions from the reference guide, shown in full to illustrate the depth of coverage.

Kubernetes — Liveness vs Readiness Probes
Q: What is the difference between liveness and readiness probes, and what happens when each fails?

A: A liveness probe answers: "Is this container still alive?" If it fails, Kubernetes restarts the container. It protects against deadlocks and hung processes that are running but not making progress. A readiness probe answers: "Is this container ready to receive traffic?" If it fails, the pod is removed from the Service's endpoint list — no traffic is routed to it, but the container is not restarted. Use readiness probes for slow-starting apps or apps that need time to warm up caches. A startup probe disables the liveness check for a configurable period to give slow-starting applications time to initialise before the liveness probe takes over. Misconfiguring probes is one of the most common sources of production incidents in Kubernetes.
Terraform — Remote State and Locking
Q: Why do you need remote state in Terraform and how does state locking work?

A: Terraform state (terraform.tfstate) is the source of truth that maps your configuration to real infrastructure. By default it's stored locally, which breaks team workflows — two engineers running apply simultaneously would corrupt state or make conflicting changes. Remote state on S3 solves the storage problem; DynamoDB state locking solves the concurrency problem. When any Terraform operation that modifies state begins, it writes a lock record to DynamoDB. If another operation tries to start, it finds the lock and waits or errors out. This prevents race conditions. Important: state files often contain sensitive values in plaintext, so restrict S3 bucket access with strict IAM policies and enable versioning so you can recover from accidental state corruption.
SRE — SLO, Error Budgets, and Deployment Decisions
Q: What is an error budget and how does it influence deployment decisions?

A: An error budget is the allowed failure quota derived from your SLO. For a 99.9% SLO, the error budget is 0.1% — approximately 43.8 minutes of downtime per month. When your error budget is healthy (budget remaining), your team has room to take risk: ship features faster, experiment with larger deploys, try new technologies. When the budget is exhausted, you freeze non-critical feature work and direct all effort toward reliability improvements. This framework is powerful because it gives both Dev and Ops a shared quantitative language for risk — instead of arguing about whether to deploy, you check the budget. Example: "We used 60% of our error budget this month on the payment service rollout, so we're pausing the next feature release until the budget recovers."
Docker — CMD vs ENTRYPOINT
Q: What is the difference between CMD and ENTRYPOINT in a Dockerfile, and why does it matter in Kubernetes?

A: ENTRYPOINT defines the executable that always runs when the container starts. CMD provides default arguments to that executable — and can be overridden at runtime with docker run args. When both are set, CMD is appended to ENTRYPOINT. The critical production detail: always use exec form (["java", "-jar", "app.jar"]) not shell form (java -jar app.jar). Shell form wraps your process in /bin/sh -c, making your app a child process of the shell. When Kubernetes sends SIGTERM for graceful shutdown, the signal goes to the shell — not your app — so your app never gets the shutdown signal and always waits for the full terminationGracePeriodSeconds before being force-killed. This causes slow rolling updates and can disrupt in-flight requests.
GitOps — ArgoCD CI vs CD Separation
Q: How do CI and CD responsibilities split in a GitOps workflow with ArgoCD?

A: In GitOps, CI and CD are explicitly separated. CI (GitHub Actions, Jenkins) handles: running tests, building the Docker image, pushing to a registry, and updating the image tag in the GitOps repository (typically via a commit to a values.yaml or Kustomize overlay). ArgoCD then detects that Git change and handles the actual Kubernetes deployment — applying manifests, managing rollouts, and reporting sync status. This separation means your CI pipeline never needs kubectl access or cloud credentials for deployment. Rollback is a git revert, not a pipeline re-run. Audit history is Git history. This clean boundary is what interviewers are testing when they ask about GitOps architecture.
Security — DevSecOps Pipeline Stages
Q: Walk me through a complete DevSecOps pipeline and which security tool you'd use at each stage.

A: A complete shift-left security pipeline has a tool at every stage: Pre-commit: Gitleaks or truffleHog to catch secrets before they hit the repo. SAST: SonarQube or Semgrep to analyze source code for vulnerabilities without running it. SCA (Software Composition Analysis): OWASP Dependency-Check or Snyk to scan third-party libraries for known CVEs. Image scanning: Trivy or Grype to scan Docker image layers — fail the build on HIGH/CRITICAL CVEs. DAST: OWASP ZAP to test the running application via actual HTTP requests, finding runtime configuration issues SAST can't detect. Runtime: Falco for real-time anomaly detection in production containers. The key interview phrase: "shift-left" means finding vulnerabilities earlier in the pipeline where they're cheaper and faster to fix.

How to Use This Guide

  • Click any tool card in the nav bar to open the full reference for that tool
  • Each tool page has: key concepts, important commands, architecture notes, and interview Q&As with full answers
  • Click any question to expand the answer — practice closing the answer first and testing yourself
  • Use the Revision Tracker to check off tools as you complete them
  • Check the "How to Answer" page for the universal interview answer framework
  • Progress is saved in your browser's localStorage — no account needed

About master.devops

This site is run by master.devops — a faceless DevOps education brand helping engineers master the skills and interview techniques needed for DevOps, SRE, and cloud engineering roles.

Content is written by the master.devops community — engineers with real production experience in DevOps, SRE, and cloud infrastructure.

Follow for daily interview tips, real commands, and career advice: @master.devops on Instagram · YouTube Shorts · LinkedIn

Revision Tracker

Check off tools as you complete revision.

0 / 18

💡 How to Answer Any Interview Question

The universal framework for DevOps/SRE interviews — especially security and availability questions.

The 4-Step Answer Formula

  • 1. State the risk/problem — "The main concern with X is..."
  • 2. Name the mechanism — "We handle this using Y feature/tool"
  • 3. Real example — "In production, we handle this by..."
  • 4. Trade-off — "The downside is cost/complexity, balanced by..."
When you blank: Say "Let me think through this from first principles..." — buys 5 seconds and signals structured thinking.

Security Answer Template

"To secure X, I focus on three layers: authentication/authorization, data in transit and at rest, and audit logging. For Kubernetes, RBAC for auth, TLS/mTLS for in-cluster traffic, audit logs enabled. Secrets go through Vault — never in plain manifests."

Availability Answer Template

"Availability depends on eliminating single points of failure + fast recovery. For Kubernetes: multi-AZ node pools, PodDisruptionBudgets, readiness probes, HPA. For databases: read replicas + automated failover. RTO/RPO targets drive which mechanisms I pick."

Deployment Strategy Cheat Sheet

StrategyHow it worksProsCons
RollingReplace pods gradually, N at a timeZero downtime, low costMixed versions temporarily
Blue/GreenTwo identical envs, instant LB switchInstant rollbackDoubles infra cost
CanaryRoute 5%→25%→100% to new versionMinimal blast radiusComplex, slower
RecreateStop all, deploy newSimpleHas downtime
Feature flagsDeploy disabled, enable per userDecouple deploy from releaseCode complexity

SLI / SLO / SLA Quick Reference

TermWhat it isExample
SLIThe metric you measure% requests returning 200
SLOYour internal target99.9% success rate
SLAContract with customers99.5% guaranteed (with penalties)
Error Budget1 - SLO0.1% = 43.8 min/month downtime allowed
// Interactive Tool

Explore the DevOps Ecosystem

Click any node to see tool details, real-world commands, use cases, alternatives, and interview questions.

Launch →
☸️
🌿
Git
⚙️
GitHub
☸️
K8s
🐳
Docker
📊
Prom.
🛡️
Trivy
DevOps Ecosystem Mind Map
Fully interactive canvas — pan, zoom, pinch. Click any tool to explore interview Q&A, key commands, use cases, and how tools connect to each other.
#interactive #mobile-ready #interview-prep #19-tools #free
Advertisement
// How It Works

Study Smarter, Not Harder

Designed specifically for Senior DevOps and SRE interview preparation.

01
🗺️
Open the Mind Map
Launch the interactive canvas directly in your browser — no install, no account needed.
02
👆
Click Any Tool
Tap any node to instantly see descriptions, use cases, real commands, and connections to other tools.
03
🎯
Read Interview Q&A
Every tool has 4 curated interview questions asked at real Senior DevOps / SRE interviews.
04
🔗
Follow Connections
Click "Connects to" pills to trace how tools in a pipeline relate — like Git → GitHub Actions → Docker → Kubernetes.
// Interview Topics

What's Covered

Every category you need to prepare for — from source control to SRE philosophy.

🌿
Source Control & GitOps
Git internals, branching strategies, GitFlow vs Trunk-Based, GitOps principles.
  • What is the difference between merge and rebase?
  • What is a detached HEAD state?
  • How does GitOps differ from traditional CD?
⚙️
CI/CD Pipelines
GitHub Actions, Jenkins, ArgoCD, pipeline design, OIDC, shared libraries.
  • How does OIDC eliminate stored cloud credentials?
  • Declarative vs Scripted Jenkins Pipeline?
  • What is the App-of-Apps pattern in ArgoCD?
🐳
Containers & Docker
Image layers, multi-stage builds, networking modes, security hardening.
  • CMD vs ENTRYPOINT — what is the difference?
  • How do you reduce Docker image size?
  • Explain Docker networking modes (bridge/host/overlay)
☸️
Kubernetes & Orchestration
Control plane, scheduling, HPA, RBAC, NetworkPolicy, Helm, Istio service mesh.
  • Explain the journey of a Pod from creation to running
  • Liveness vs Readiness vs Startup probes?
  • How does Kubernetes service networking work?
🛡️
DevSecOps & Security
SAST, DAST, SCA, Vault, Trivy, OWASP, Gitleaks, shift-left security.
  • What is the difference between SAST, DAST, and SCA?
  • How does Vault dynamic secrets engine work?
  • Walk me through a DevSecOps pipeline
📊
Observability & Monitoring
Prometheus, Grafana, Loki, Splunk, PromQL, three pillars of observability.
  • Counter vs Gauge vs Histogram — when to use each?
  • How do you write a p99 latency PromQL query?
  • How does Grafana Loki differ from Elasticsearch?
☁️
Cloud (AWS & Azure)
EKS, AKS, IRSA, Workload Identity, VPC, networking, IAM, multi-AZ HA.
  • Security Group vs NACL — what is the difference?
  • How does IRSA work under the hood?
  • EBS vs EFS vs S3 — when to use each?
🗂️
Infrastructure as Code
Terraform state, modules, workspaces, Ansible playbooks, idempotency.
  • What is Terraform state and why is it important?
  • Terraform modules vs workspaces?
  • When would you use Ansible vs Terraform?
🎯
SRE Concepts
SLIs, SLOs, error budgets, burn rate alerts, toil, post-mortems, chaos engineering.
  • How would you define SLIs and SLOs for a new service?
  • What is an error budget and how do you use it?
  • Walk me through a blameless post-mortem structure
Advertisement
// Tools Covered

19 Essential DevOps Tools

Every tool you need to know for modern DevOps and SRE roles.

🌿
Git
Source Control
⚙️
GitHub Actions
CI/CD
🏗️
Jenkins
CI/CD
🔄
ArgoCD
GitOps / CD
🐳
Docker
Container
☸️
Kubernetes
Orchestration
Helm
K8s Package Mgr
Istio
Service Mesh
🔍
SonarQube
Security / SAST
🛡️
Trivy / OWASP
DevSecOps
🔐
HashiCorp Vault
Secrets Mgmt
📦
JFrog Artifactory
Artifacts
📊
Prometheus
Observability
📈
Grafana
Visualization
🔭
Splunk
SIEM / Logs
☁️
AWS (EKS, IAM, S3…)
Cloud
🔷
Azure (AKS, Entra…)
Cloud
🗂️
Terraform
IaC
🤖
Ansible
Config Mgmt
// Free Resources

More Prep Material

Everything on this page is free. No paywalls, no email required.

🗺️
Interactive Mind Map
Visual DevOps ecosystem explorer with 19 tools, commands & interview Q&A.
▶️
YouTube Shorts
Quick DevOps concepts in under 60 seconds — perfect for daily revision.
📸
Instagram Tips
Daily DevOps interview tips, diagrams, and cheat sheets on @master.devops.
🤖
Automation Scripts
Ready-to-use shell, Python & Terraform scripts on @automation.script.
💼
LinkedIn Updates
Career advice, tool comparisons, and industry trends for DevOps engineers.
🎯
Interview Q&A Bank
90+ interview questions across 10 DevOps categories — all in the mind map.
// FAQ

Frequently Asked Questions

Common questions about using this platform.

Is this completely free?
Yes, 100% free. No login, no email, no paywall. The mind map, interview questions, commands, and all resources on this site are free forever for the DevOps community.
Does the mind map work on mobile?
Yes. Use one finger to pan the canvas, two fingers to pinch-zoom. Tap any node to open the detail panel. The search bar and category filters work on mobile too.
What experience level is this for?
Primarily targeting engineers with 2–5 years of experience preparing for Senior DevOps, Senior SRE, or Platform Engineer roles at product-based companies. The tool coverage and interview questions reflect real senior-level interviews.
How often is content updated?
The mind map and resources are updated regularly as tools evolve. Follow @master.devops on YouTube and Instagram for the latest content drops.
Can I suggest a tool to be added?
Absolutely. DM @master.devops on Instagram or LinkedIn with your suggestions. The community's input directly shapes what gets added next.
What topics should I focus on for interviews?
For Senior DevOps roles: Kubernetes internals, CI/CD pipeline design, IaC best practices, and cloud architecture. For SRE roles: additionally focus on SLOs/SLIs/error budgets, observability with Prometheus+Grafana, and incident management. The mind map covers all of these.
Advertisement

Join the Community

Free DevOps content every week. Follow for interview tips, cheat sheets, scripts, and career advice.

Built by DevOps Engineers, for DevOps Engineers

Master DevOps is a free, community-driven learning platform created to help engineers break into DevOps and SRE roles. Whether you're preparing for your first cloud interview or levelling up from junior to senior, this platform gives you hands-on tools — not just theory.

Every resource here — the interactive mind map, interview simulators, command references, and study guides — is 100% free. No subscriptions, no paywalls, no fluff. Just real-world DevOps knowledge built from real-world DevOps practice.

🗺️ Explore Mind Map 📖 Learn DevOps Basics

What is DevOps?

DevOps is a software engineering culture and practice that unifies software development (Dev) and IT operations (Ops). The goal is to shorten the development lifecycle and deliver high-quality software continuously. DevOps achieves this through automation, collaboration, and continuous feedback. Before DevOps, development and operations teams worked in silos — developers wrote code and "threw it over the wall" to operations for deployment, leading to slow releases, frequent failures, and finger-pointing between teams.

Modern DevOps organisations deploy code hundreds of times per day using automated CI/CD pipelines. Every code change triggers automated tests, security scans, container builds, and deployment to production — all without manual intervention. Tools like Docker, Kubernetes, Terraform, Jenkins, GitHub Actions, Prometheus, and Grafana form the backbone of this automation.

Site Reliability Engineering (SRE) is the operations discipline born from DevOps — applying software engineering principles to infrastructure problems. SRE teams use SLOs (Service Level Objectives), error budgets, and blameless post-mortems to balance feature velocity with system reliability. This site covers all the tools, concepts, and interview Q&A you need to succeed in DevOps and SRE roles.

Free DevOps Guides & Articles

📖
What is DevOps?
Complete beginner guide — CI/CD, IaC, SRE, observability, and how tools fit together. 10 min read.
☸️
Kubernetes Complete Guide
Pods, Deployments, RBAC, real YAML, health probes, debugging, 6 interview Q&As. 15 min read.
🐳
Docker Complete Guide
Multi-stage builds, networking, volumes, security hardening, CMD vs ENTRYPOINT. 12 min read.
⚙️
CI/CD Pipeline Explained
GitHub Actions, Jenkins, ArgoCD GitOps — real pipeline YAML from production. 12 min read.
🗂️
Terraform Hands-On Guide
State, remote backends, modules, real VPC + EKS Terraform code. 13 min read.
🐧
Linux Commands for DevOps
Permissions, processes, networking, log analysis, systemd, performance tuning. 10 min read.
🌿
Git Interview Questions
Rebase vs merge, branching strategies, reflog, cherry-pick, GitOps patterns. 10 min read.
☁️
AWS DevOps Roadmap
EKS, IRSA, VPC design, IAM, S3 vs EBS vs EFS, RDS HA — real interview answers. 12 min read.
📊
Prometheus & Grafana Guide
PromQL, Alertmanager, SLO burn rate alerting, Grafana dashboards. 12 min read.

Written by master.devops — Free DevOps & SRE interview prep.

📚 Recommended Courses

Affiliate links — courses that pair well with this free prep guide. No extra cost to you.

🚀
DevOps Bootcamp — CI/CD, Docker, Kubernetes, AWS
Udemy · Highest rated DevOps bootcamp
☸️
Kubernetes CKA Exam Prep
Udemy · Certified Kubernetes Administrator
🗂️
Terraform + AWS — Infrastructure as Code
Udemy · HashiCorp Terraform + AWS

🔗 Related DevOps Topics

🐳 Docker ☸️ Kubernetes 🗂️ Terraform 🐧 Linux ⚙️ CI/CD ☁️ AWS 📊 Prometheus 🌿 Git 🗺️ Mind Map 🏠 Home
🎯

Ready to Crack Your DevOps Interview?

Access 90+ interview Q&As, real commands, SRE frameworks, and 18-tool reference cards — all free, no login required. Used by 1,300+ DevOps engineers.

🎯 Open Interview Kit → 🗺️ Explore Mind Map

No account needed · Works on mobile · Updated weekly

🌙