Evidence-based DevOps interview bank
Interview Preparation
Practise concept, implementation, troubleshooting, and architecture questions for every learning-path submodule. Each answer explains the mechanism, production evidence, trade-offs, and safe recovery—not just a definition.
Interview domain
Core DevOps
DevOps Foundations
Expect questions that test whether you can connect delivery speed, reliability, security, and team ownership instead of defining DevOps as a list of tools.
Interview domain
Operating Systems
Linux Administration
Interviewers look for disciplined diagnosis: observe symptoms, form a hypothesis, collect system evidence, change the smallest safe element, and verify recovery.
Interview domain
Automation
Bash Scripting and Automation
Be ready to reason about quoting, exit status, pipes, idempotency, input validation, observability, and the difference between an interactive command and safe automation.
Python Automation for DevOps
Be ready to discuss virtual environments, dependencies, serialization, subprocess safety, timeouts, retries, pagination, authentication, idempotency, structured logs, exceptions, testing, and packaging.
PowerShell Automation for DevOps
Strong answers cover object versus text pipelines, parameter binding, scopes, modules, error action, try/catch/finally, authentication, output streams, remoting, idempotency, and secret-safe logs.
REST API and Azure DevOps Automation
Expect method idempotency, status codes, versioning, continuation tokens, throttling, retries, token scope and expiry, secure logging, API consistency, polling, and partial-failure recovery.
Interview domain
Networking
Networking Fundamentals
Strong answers follow a packet and clearly separate name resolution, Layer 3 routing, Layer 4 transport, TLS, and Layer 7 application behavior.
Interview domain
Source Control
Git Version Control
Interview questions often test the effect of commands on the working tree, index, local history, and shared history. State which layer changes and whether the operation is safe after push.
GitHub Collaboration and Security
Prepare to explain how identity, protected branches, reviews, status checks, environments, short-lived credentials, packages, and dependency scanning combine into a trusted change path.
Interview domain
Microsoft Azure
Azure Fundamentals and Governance
Good answers distinguish tenant, management group, subscription, resource group, and resource scopes, then explain policy enforcement, RBAC inheritance, locks, and cost ownership.
Azure Compute Services
Interviewers expect a decision framework: control versus operational burden, state, scaling, networking, deployment unit, availability, security, and price.
Azure Networking
Be precise about Layer 4 versus Layer 7, regional versus global services, inbound versus outbound flow, route precedence, NSG evaluation, and private DNS for private endpoints.
Azure Storage and Data Protection
Expect trade-off questions about service type, performance tier, redundancy scope, authorization method, network isolation, encryption ownership, lifecycle, and recovery.
Azure Identity and Security
Clearly separate authentication from authorization, human from workload identity, control-plane from data-plane access, and posture management from threat detection and response.
Interview domain
Azure DevOps
Azure DevOps Organizations and Boards
Interview answers should connect planning hierarchy, team topology, permissions, service connections, agents, and end-to-end traceability rather than discussing Boards in isolation.
Azure Repos and Pull-Request Governance
Prepare to justify reviewers, validation policies, bypass permissions, merge strategy, status checks, and how a branch policy supports both security and developer flow.
Azure Pipelines Architecture and YAML
Expect precise questions about compile time versus runtime, variable scope, template expansion, conditions, outputs, dependencies, agents, and reusable pipeline design.
CI/CD Execution and Deployment Controls
Strong candidates explain artifact immutability, gate placement, environment promotion, approval design, deployment strategy, health validation, and how rollback is triggered and proven.
Azure Artifacts and Package Management
Interviewers test whether you understand packages as immutable supply-chain inputs with provenance, scope, permissions, promotion, retention, and dependency risk.
Interview domain
Containers
Docker and Container Engineering
Be ready to explain layer cache, build context, PID 1, signals, entrypoints, environment configuration, persistent data, networks, non-root execution, image scanning, and common runtime failures.
Azure Container Registry
Good answers cover repository versus image versus tag versus digest, identity choices, network isolation, RBAC, retention, tasks, replication, and supply-chain evidence.
Interview domain
Kubernetes
Kubernetes Core Workloads
Expect questions about desired state, reconciliation, controller ownership, pod ephemerality, service discovery, selectors, rollout behavior, stateful identity, and node-level agents.
Kubernetes Storage, Networking, Security, and Scheduling
Strong candidates distinguish resource requests from limits, readiness from liveness, service-account identity from user access, affinity from taints, and scaling from disruption protection.
Azure Kubernetes Service Engineering
Interview questions focus on node-pool purpose, CNI address planning, private clusters, identity, registry pulls, secret injection, ingress, upgrades, observability, scaling, and division of responsibility.
Helm Package Management
Be ready to discuss chart versus release, template rendering, values precedence, hooks, dependency locking, immutable versions, upgrade safety, and rollback limitations when data changes.
Interview domain
Infrastructure as Code
Terraform Infrastructure as Code
Expect detailed questions about graph dependencies, plan versus apply, state sensitivity, locking, module contracts, workspaces, count versus for_each, import, lifecycle, provider aliases, drift, and recovery.
ARM Templates and Bicep
Strong answers distinguish ARM as Azure deployment engine from template languages, cover implicit dependencies, scopes, what-if, idempotency, modules, and the danger of complete mode.
Interview domain
Configuration Management
Ansible Configuration Automation
Interviewers test push-based execution, inventory, variable precedence, idempotency, handlers, roles, templating, secret protection, error handling, and why provisioners are not a configuration strategy.
Interview domain
Quality Engineering
SonarQube and Code Quality
Expect questions about scanner, server, database, quality profiles versus gates, new-code strategy, false positives, coverage meaning, and pipeline enforcement.
Interview domain
Security
DevSecOps Security Scanning
Good answers place each test at the right lifecycle stage, explain signal and limitations, reduce noise, protect reports, and use severity, exploitability, and exposure in gate decisions.
Key Vault Integration and Secret Rotation
Be prepared to distinguish management-plane from data-plane access, secret from key operations, RBAC from access policies, and rotation from simple replacement.
Interview domain
Observability
Azure Monitor and Application Observability
Interviewers look for signal choice, sampling and retention, correlation, KQL, alert quality, ownership, distributed tracing, and the difference between internal telemetry and outside-in availability.
Prometheus Monitoring and Alerting
Expect discussion of labels and cardinality, counters versus gauges, rate calculations, scrape failures, recording rules, alert evaluation, grouping, inhibition, retention, and highly available deployments.
Grafana Dashboards and Alerting
Strong candidates explain audience, query efficiency, variable cardinality, units, transformations, alert evaluation, data-source permissions, and dashboard-as-code.
Centralized Logging and Analysis
Interview answers should cover structure, timestamps, correlation, buffering, parsing, index design, retention, privacy, cost, access, search performance, and separation of logs from metrics and traces.
Interview domain
Delivery Engineering
Deployment Strategies and Release Safety
Prepare to compare capacity, traffic control, session behavior, database compatibility, observability, rollback speed, cost, and test realism across strategies.
GitOps with Argo CD and Flux
Good answers distinguish build from deploy, push pipelines from pull reconciliation, desired from actual state, sync from health, and normal operation from break-glass change.
Interview domain
Operations
Site Reliability Engineering
Interviewers look for precise measurement, multi-window burn rates, user impact, release policy, incident roles, blameless learning, sustainable on-call, capacity assumptions, and measurable toil reduction.
Production Troubleshooting and Recovery
Strong candidates investigate in order, use topic-native evidence, separate mitigation from root cause, communicate impact, and know when rollback is unsafe because of data or compatibility changes.
Interview domain
Delivery Governance
Release Management
Expect questions about version identity, separation of duties, approval evidence, change windows, freeze exceptions, smoke coverage, rollback triggers, hotfix reconciliation, and release metrics.
Delivery Security, Governance, and Compliance
Interview answers should name actor, resource, scope, token method, approver independence, audit source, policy effect, exception owner, and review frequency.
Interview domain
Data Engineering
Database CI/CD and Schema Evolution
Good answers compare state-based and migration-based delivery, transaction boundaries, locking, drift, compatibility, data transformation, secret access, backup, forward fix, and recovery testing.
Interview domain
Platform Engineering
Enterprise Pipeline Architecture
Interviewers test template boundaries, version compatibility, security ownership, artifact identity, fan-in and fan-out, target configuration, tenant isolation, progressive rollout, observability, and developer experience.
Interview domain
Resilience
Backup and Disaster Recovery
Expect clear distinction between high availability, replication, backup, and DR; objective measurement; consistency; immutable copies; orchestration; dependency order; split-brain prevention; and tested recovery.