rohitg00
devops-interview-questions

Creating this repository as a central hub for all DevOps interview questions to help you land your next job.

Last updated Jul 9, 2026
1.9k
Stars
991
Forks
8
Issues
+5
Stars/day
Attention Score
79
Language breakdown
No language data available.
Files click to expand
README

DevOps Interview Questions & Answers

Click :star: if you like the project. Pull Requests are highly appreciated.

Note: This repository contains DevOps interview questions and answers. Please check the different sections for specific topics like Docker, Kubernetes, CI/CD, etc.

Table of Contents

Hide/Show table of contents

| No. | Questions | | --- | --------- | | | Core DevOps Concepts | | 1 | What is DevOps? | | 2 | What are the benefits of DevOps? | | 3 | What is Continuous Integration? | | 4 | What is Continuous Delivery? | | 5 | What is Continuous Deployment? | | | Docker | | 6 | What is Docker? | | 7 | What is the difference between Docker Image and Docker Container? | | 8 | What is Dockerfile? | | 9 | What is Docker Compose? | | 10 | Explain Docker Architecture | | | Kubernetes | | 11 | What is Kubernetes? | | 12 | What are the main components of Kubernetes architecture? | | 13 | What is a Pod in Kubernetes? | | 14 | What is a Service in Kubernetes? | | 15 | Explain the difference between Docker Swarm and Kubernetes | | | CI/CD | | 16 | What is CI/CD Pipeline? | | 17 | What is Jenkins? | | 18 | What are Jenkins Pipelines? | | 19 | What is GitLab CI? | | 20 | What is the difference between Continuous Delivery and Continuous Deployment? | | | Cloud Platforms | | 21 | What is Cloud Computing? | | 22 | What is AWS (Amazon Web Services)? | | 23 | What is Azure? | | 24 | What is Google Cloud Platform (GCP)? | | 25 | What are the different types of cloud services? | | | Infrastructure as Code | | 26 | What is Infrastructure as Code? | | 27 | What is Terraform? | | 28 | What is Ansible? | | 29 | What is the difference between Ansible and Terraform? | | 30 | What are Terraform providers? | | | Monitoring and Logging | | 31 | What is monitoring in DevOps? | | 32 | What is ELK Stack? | | 33 | What is Prometheus? | | 34 | What is Grafana? | | 35 | Explain the difference between monitoring and logging | | | Security and Compliance | | 36 | What is DevSecOps? | | 37 | What is Infrastructure Security? | | 38 | What is Container Security? | | 39 | What is Compliance as Code? | | 40 | What are Security Best Practices in DevOps? | | | Linux Administration | | 41 | What are the basic Linux commands every DevOps engineer should know? | | 42 | What is Shell Scripting? | | 43 | What is systemd? | | 44 | How do you manage services in Linux? | | 45 | What is Linux File System Hierarchy? | | | Version Control | | 46 | What is Git? | | 47 | What is Git Branching Strategy? | | 48 | What is Git Flow? | | 49 | What is Trunk Based Development? | | 50 | How to handle merge conflicts in Git? | | | Configuration Management | | 51 | What is Configuration Management? | | 52 | What is Puppet? | | 53 | What is Chef? | | 54 | What is Salt (SaltStack)? | | 55 | Compare different Configuration Management tools | | | Scalability and High Availability | | 56 | What is Scalability in DevOps? | | 57 | What is High Availability? | | 58 | What is Load Balancing? | | 59 | What is Auto Scaling? | | 60 | What is Disaster Recovery? | | | Backup and Disaster Recovery | | 61 | What is Backup and Disaster Recovery? | | 62 | What are different types of backups? | | 63 | What is RPO and RTO? | | 64 | What is Business Continuity Planning? | | 65 | What are backup best practices? | | | Cloud Native Architecture | | 66 | What is Cloud Native Architecture? | | 67 | What are Microservices? | | 68 | What is Service Mesh? | | 69 | What is Event-Driven Architecture? | | 70 | What are the 12-Factor App principles? | | | Performance Testing | | 71 | What is Performance Testing? | | 72 | What are different types of Performance Tests? | | 73 | What are Performance Testing Tools? | | 74 | What are Performance Testing Best Practices? | | 75 | How to analyze Performance Test Results? | | | API Gateway and Service Mesh | | 76 | What is an API Gateway? | | 77 | What are the benefits of using API Gateway? | | 78 | What is API Security? | | 79 | What is Rate Limiting? | | 80 | What is API Documentation? | | | Container Orchestration Advanced | | 81 | What are StatefulSets in Kubernetes? | | 82 | What are DaemonSets in Kubernetes? | | 83 | What is Helm? | | 84 | What is Istio? | | 85 | What is Container Runtime Interface (CRI)? | | | DevOps Tools and Automation | | 86 | What is Infrastructure Automation? | | 87 | What is GitOps? | | 88 | What is ArgoCD? | | 89 | What is Tekton? | | 90 | What are Deployment Strategies? | | | Cloud Cost Optimization | | 91 | What is Cloud Cost Optimization? | | 92 | What are Reserved Instances? | | 93 | What is Spot Instance pricing? | | 94 | How to implement cost tagging strategy? | | 95 | What are cost allocation reports? | | | Site Reliability Engineering (SRE) | | 96 | What is Site Reliability Engineering? | | 97 | What are Service Level Objectives (SLOs)? | | 98 | What are Service Level Indicators (SLIs)? | | 99 | What is Error Budget? | | 100 | What is Toil in SRE? | | | DevOps Metrics and KPIs | | 101 | What are DevOps Metrics? | | 102 | What is Mean Time to Recovery (MTTR)? | | 103 | What is Change Failure Rate? | | 104 | What is Deployment Frequency? | | 105 | What is Lead Time for Changes? | | | Serverless Architecture | | 106 | What is Serverless Computing? | | 107 | What is AWS Lambda? | | 108 | What are the benefits of Serverless? | | 109 | What are Serverless Best Practices? | | 110 | What is Function as a Service (FaaS)? | | | Database Management in DevOps | | 111 | What is Database DevOps? | | 112 | What is Database Version Control? | | 113 | What are Database Migration Tools? | | 114 | What is Database Backup Strategy? | | 115 | What is Database Performance Tuning? | | | Network Security | | 116 | What is Network Security in DevOps? | | 117 | What is Zero Trust Security? | | 118 | What is SSL/TLS? | | 119 | What is a Web Application Firewall (WAF)? | | 120 | What is Network Segmentation? | | | Incident Management | | 121 | What is Incident Management? | | 122 | What is an Incident Response Plan? | | 123 | What is Post-Mortem Analysis? | | 124 | What are Incident Severity Levels? | | 125 | What is On-Call Management? | | | DevOps Culture and Practices | | 126 | What is DevOps Culture? | | 127 | What are DevOps Best Practices? | | 128 | What is Blameless Culture? | | 129 | What is Knowledge Sharing in DevOps? | | 130 | What is Team Collaboration in DevOps? | | | Infrastructure Monitoring | | 131 | What is Infrastructure Monitoring? | | 132 | What are Monitoring Tools? | | 133 | What are Monitoring Best Practices? | | 134 | What is Application Performance Monitoring? | | 135 | What is Log Management? | | | Cloud Migration | | 136 | What is Cloud Migration? | | 137 | What are Cloud Migration Strategies? | | 138 | What is Cloud Assessment? | | 139 | What is Application Modernization? | | 140 | What are Cloud Migration Tools? | | | Advanced DevOps & Cloud | | 141 | What is Platform Engineering? | | 142 | What is FinOps? | | 143 | What is Policy as Code? | | 144 | What is Chaos Engineering? | | 145 | What is Blue/Green Deployment? | | 146 | What is Feature Flagging? | | 147 | What is a Service Catalog? | | 148 | What is a Service Level Agreement (SLA)? | | 149 | What is a Service Level Objective (SLO)? | | 150 | What is a Service Level Indicator (SLI)? | | 151 | What is a Runbook? | | 152 | What is a Playbook in Incident Response? | | 153 | What is Observability? | | 154 | What is Tracing in Observability? | | 155 | What is a Sidecar Pattern? | | 156 | What is a Service Mesh Control Plane? | | 157 | What is GitHub Actions? | | 158 | What is a Self-Healing System? | | 159 | What is Canary Analysis? | | 160 | What is Infrastructure Drift? |

Core DevOps Concepts

  • ### What is DevOps?
DevOps is a set of practices that combines software development (Dev) and IT operations (Ops). It aims to shorten the systems development life cycle and provide continuous delivery with high software quality. DevOps is complementary with Agile software development; several DevOps aspects came from Agile methodology.

⬆ Back to Top

  • ### What are the benefits of DevOps?
The main benefits of DevOps include:

1. Faster delivery of features 2. More stable operating environments 3. Improved communication and collaboration 4. More time to innovate (rather than fix/maintain) 5. Reduced deployment failures and rollbacks 6. Shorter mean time to recovery

⬆ Back to Top

  • ### What is Continuous Integration?
Continuous Integration (CI) is a development practice where developers integrate code into a shared repository frequently, preferably several times a day. Each integration can then be verified by an automated build and automated tests.

Key aspects of CI include: - Maintaining a single source repository - Automating the build - Making the build self-testing - Everyone commits to the baseline every day - Every commit builds on an integration machine - Keep the build fast - Test in a clone of the production environment - Make it easy to get the latest deliverables - Everyone can see the results of the latest build - Automate deployment

⬆ Back to Top

Docker

  • ### What is Docker?
Docker is a platform for developing, shipping, and running applications in containers. Containers allow developers to package up an application with all the parts it needs, such as libraries and other dependencies, and ship it all out as one package.

⬆ Back to Top

  • ### What is the difference between Docker Image and Docker Container?
- Docker Image: A Docker image is a read-only template containing a set of instructions for creating a Docker container. It includes the application code, runtime, libraries, dependencies, and system tools. - Docker Container: A container is a runnable instance of an image. You can create, start, stop, move, or delete a container using the Docker API or CLI. A container is isolated from other containers and the host machine.

⬆ Back to Top

  • ### What is Dockerfile?
A Dockerfile is a text document that contains all the commands a user could call on the command line to assemble an image. Using docker build, users can create an automated build that executes several command-line instructions in succession.

Example of a simple Dockerfile:

FROM node:14    WORKDIR /app    COPY package*.json ./    RUN npm install    COPY . .    EXPOSE 3000    CMD ["npm", "start"]

⬆ Back to Top

Kubernetes

  • ### What is Kubernetes?
Kubernetes (K8s) is an open-source container orchestration platform that automates the deployment, scaling, and management of containerized applications. It was originally developed by Google and is now maintained by the Cloud Native Computing Foundation (CNCF).

⬆ Back to Top

  • ### What are the main components of Kubernetes architecture?
Kubernetes architecture consists of the following main components:

1. Master Node Components: - API Server - etcd - Controller Manager - Scheduler

2. Worker Node Components: - Kubelet - Container Runtime - Kube Proxy

⬆ Back to Top

  • ### What is a Pod in Kubernetes?
A Pod is the smallest deployable unit in Kubernetes. It represents a single instance of a running process in your cluster. Pods can contain one or more containers, storage resources, a unique network IP, and options that govern how the container(s) should run.

Example of a simple Pod YAML:

apiVersion: v1     kind: Pod     metadata:       name: nginx-pod     spec:       containers:       - name: nginx         image: nginx:1.14.2         ports:         - containerPort: 80

⬆ Back to Top

CI/CD

  • ### What is CI/CD Pipeline?
A CI/CD Pipeline is a series of steps that must be performed in order to deliver a new version of software. A pipeline typically includes stages for: 1. Building the code 2. Running automated tests 3. Deploying to staging/production environments Example of a basic Jenkins Pipeline:
pipeline {
        agent any
        stages {
            stage('Build') {
                steps {
                    sh 'npm install'
                    sh 'npm run build'
                }
            }
            stage('Test') {
                steps {
                    sh 'npm run test'
                }
            }
            stage('Deploy') {
                steps {
                    sh './deploy.sh'
                }
            }
        }
    }

⬆ Back to Top

  • ### What is Jenkins?
Jenkins is an open-source automation server that helps automate parts of software development related to building, testing, and deploying, facilitating continuous integration and continuous delivery (CI/CD).

Key features include: - Easy installation and configuration - Hundreds of plugins available - Built-in GUI tool for easy updates - Supports distributed builds with master-slave architecture - Extensible with a huge number of plugins

⬆ Back to Top

Cloud Platforms

  • ### What is Cloud Computing?
Cloud computing is the delivery of computing services—including servers, storage, databases, networking, software, analytics, and intelligence—over the Internet ("the cloud") to offer faster innovation, flexible resources, and economies of scale.

⬆ Back to Top

  • ### What is AWS (Amazon Web Services)?
AWS is a comprehensive and widely adopted cloud platform, offering over 200 fully featured services from data centers globally. Key services include:

1. Compute: - EC2 (Elastic Compute Cloud) - Lambda (Serverless Computing) - ECS (Elastic Container Service)

2. Storage: - S3 (Simple Storage Service) - EBS (Elastic Block Store) - EFS (Elastic File System)

3. Database: - RDS (Relational Database Service) - DynamoDB (NoSQL Database) - Redshift (Data Warehouse)

⬆ Back to Top

  • ### What is Azure?
Azure is Microsoft's cloud computing platform that provides a wide variety of services including:

1. Compute Services: - Virtual Machines - App Services - Azure Functions

2. Storage Services: - Blob Storage - File Storage - Queue Storage

3. Network Services: - Virtual Network - Load Balancer - Application Gateway

⬆ Back to Top

  • ### What are the different types of cloud services?
The main types of cloud services are:

1. IaaS (Infrastructure as a Service): - Provides virtualized computing resources - Examples: AWS EC2, Azure VMs

2. PaaS (Platform as a Service): - Provides platform allowing customers to develop, run, and manage applications - Examples: Heroku, Google App Engine

3. SaaS (Software as a Service): - Provides software applications over the internet - Examples: Salesforce, Google Workspace

4. FaaS (Function as a Service): - Provides serverless computing capabilities - Examples: AWS Lambda, Azure Functions

⬆ Back to Top

Infrastructure as Code

  • ### What is Infrastructure as Code?
Infrastructure as Code (IaC) is the practice of managing and provisioning infrastructure through machine-readable definition files rather than physical hardware configuration or interactive configuration tools.

Benefits of IaC: - Version Control - Reproducibility - Automation - Documentation - Consistency - Scalability

⬆ Back to Top

  • ### What is Terraform?
Terraform is an open-source IaC software tool that enables you to safely and predictably create, change, and improve infrastructure. It codifies cloud APIs into declarative configuration files.

Example of a simple Terraform configuration:

provider "aws" {       region = "us-west-2"     }

resource "aws_instance" "example" { ami = "ami-0c55b159cbfafe1f0" instance_type = "t2.micro"

tags = { Name = "example-instance" } }

⬆ Back to Top

  • ### What is Ansible?
Ansible is an open-source automation tool that automates software provisioning, configuration management, and application deployment. It uses YAML syntax for expressing automation jobs.

Example of an Ansible playbook:

---     - name: Install and configure web server       hosts: webservers       become: yes              tasks:         - name: Install nginx           apt:             name: nginx             state: present                      - name: Start nginx service           service:             name: nginx             state: started

⬆ Back to Top

Monitoring and Logging

  • ### What is monitoring in DevOps?
Monitoring in DevOps is the practice of collecting and analyzing data about the performance and stability of services and infrastructure to improve the system's reliability. Key aspects include:

1. Infrastructure Monitoring: - Server health - Network performance - Resource utilization

2. Application Monitoring: - Response times - Error rates - Request rates

3. User Experience Monitoring: - Page load times - User interactions - Conversion rates

⬆ Back to Top

  • ### What is ELK Stack?
ELK Stack is a collection of three open-source products: 1. Elasticsearch: A search and analytics engine 2. Logstash: A server‑side data processing pipeline 3. Kibana: A visualization tool for Elasticsearch data

Common use cases: - Log aggregation - Security analytics - Application performance monitoring - Website search - Business analytics

⬆ Back to Top

  • ### What is Prometheus?
Prometheus is an open-source systems monitoring and alerting toolkit. Key features include:

1. Time series database 2. Flexible query language (PromQL) 3. Pull-based metrics collection 4. Alert management 5. Visualization capabilities

Example of Prometheus configuration:

global:       scrape_interval: 15s

scrape_configs: - job_name: 'prometheus' static_configs: - targets: ['localhost:9090'] - job_name: 'node' static_configs: - targets: ['localhost:9100']

⬆ Back to Top

  • ### What is Grafana?
Grafana is an open-source analytics and monitoring solution that allows you to query, visualize, and alert on your metrics no matter where they are stored. Key features include:

1. Data source integration 2. Dashboard creation 3. Alerting 4. Visualization 5. User interface

⬆ Back to Top

  • ### Explain the difference between monitoring and logging
Monitoring and logging are two different practices in DevOps:

1. Monitoring: - Focuses on collecting and analyzing data about the performance and stability of services and infrastructure to improve the system's reliability. - Key aspects include: - Infrastructure Monitoring - Application Monitoring - User Experience Monitoring

2. Logging: - Focuses on collecting and analyzing log data to help diagnose and troubleshoot issues. - Key aspects include: - Log aggregation - Security analytics - Application performance monitoring - Website search - Business analytics

⬆ Back to Top

Security and Compliance

  • ### What is DevSecOps?
DevSecOps is the practice of integrating security practices within the DevOps process. It creates a 'security as code' culture with ongoing, flexible collaboration between release engineers and security teams.

Key principles include: - Security automation - Early security testing - Continuous security monitoring - Security as part of CI/CD pipeline - Rapid security feedback

⬆ Back to Top

  • ### What is Infrastructure Security?
Infrastructure Security involves securing all infrastructure components including:

1. Network Security: - Firewalls - VPNs - Network segmentation - DDoS protection

2. Cloud Security: - Identity and Access Management (IAM) - Encryption - Security groups - Network ACLs

3. Host Security: - OS hardening - Patch management - Antivirus - Host-based firewalls

⬆ Back to Top

Linux Administration

  • ### What are the basic Linux commands every DevOps engineer should know?
Essential Linux commands include:

1. File Operations:

ls      # List files and directories     cd      # Change directory     pwd     # Print working directory     cp      # Copy files     mv      # Move/rename files     rm      # Remove files     mkdir   # Create directory

2. System Information:

top     # Show processes     df      # Show disk usage     free    # Show memory usage     ps      # Show process status

3. Text Processing:

grep    # Search text     sed     # Stream editor     awk     # Text processing     cat     # View file contents

⬆ Back to Top

Version Control

  • ### What is Git?
Git is a distributed version control system that tracks changes in source code during software development. It's designed for coordinating work among programmers, but it can be used to track changes in any set of files.

Key concepts include: - Repository - Commit - Branch - Merge - Pull Request - Clone - Push/Pull

⬆ Back to Top

  • ### What is Git Branching Strategy?
A Git branching strategy is a convention or set of rules that specify how and when branches should be created and merged. Common strategies include:

1. Git Flow: - Main branches: master, develop - Supporting branches: feature, release, hotfix

2. Trunk-Based Development: - Single main branch (trunk) - Short-lived feature branches - Frequent integration

Example of creating a feature branch:

# Create and switch to a new feature branch     git checkout -b feature/new-feature

# Make changes and commit git add . git commit -m "Add new feature"

# Push to remote git push origin feature/new-feature

⬆ Back to Top

Configuration Management

  • ### What is Configuration Management?
Configuration Management is the process of maintaining systems, such as computer systems and servers, in a desired state. It's a way to make sure that a system performs as it's supposed to as changes are made over time.

Key aspects include: - System configuration - Application configuration - Dependencies management - Version control - Compliance and security

⬆ Back to Top

  • ### What is Puppet?
Puppet is a configuration management tool that helps you automate the provisioning and management of your infrastructure. It uses a declarative language to describe system configurations.

Example of a Puppet manifest:

class apache {       package { 'apache2':         ensure => installed,       }              service { 'apache2':         ensure => running,         enable => true,         require => Package['apache2'],       }              file { '/var/www/html/index.html':         ensure => file,         content => 'Hello, World!',         require => Package['apache2'],       }     }

⬆ Back to Top

Scalability and High Availability

  • ### What is Scalability in DevOps?
Scalability is the capability of a system to handle a growing amount of work by adding resources to the system. There are two types of scaling:

1. Vertical Scaling (Scale Up): - Adding more power to existing resources - Example: Upgrading CPU/RAM

2. Horizontal Scaling (Scale Out): - Adding more resources - Example: Adding more servers

⬆ Back to Top

  • ### What is High Availability?
High Availability (HA) is a characteristic of a system that aims to ensure an agreed level of operational performance, usually uptime, for a higher than normal period.

Key components: 1. Redundancy: - Multiple instances - No single point of failure

2. Monitoring: - Health checks - Automated failover

3. Load Balancing: - Traffic distribution - Resource optimization

⬆ Back to Top

  • ### What is Load Balancing?
Load Balancing is the process of distributing network traffic across multiple servers to ensure no single server bears too much demand.

Common Load Balancing algorithms: 1. Round Robin 2. Least Connections 3. IP Hash 4. Weighted Round Robin 5. Resource-Based

Example of Nginx Load Balancer configuration:

http {         upstream backend {             server backend1.example.com;             server backend2.example.com;             server backend3.example.com;         }

server { listen 80; location / { proxy_pass http://backend; } } }

⬆ Back to Top

  • ### What is Auto Scaling?
Auto Scaling is a feature that automatically adjusts the number of compute resources based on the current demand.

Key concepts: 1. Scaling Policies: - Target tracking - Step scaling - Simple scaling

2. Metrics: - CPU utilization - Memory usage - Request count - Custom metrics

Example of AWS Auto Scaling configuration:

AutoScalingGroup:       MinSize: 1       MaxSize: 10       DesiredCapacity: 2       HealthCheckType: ELB       HealthCheckGracePeriod: 300       LaunchTemplate:         LaunchTemplateId: !Ref LaunchTemplate         Version: !GetAtt LaunchTemplate.LatestVersionNumber

⬆ Back to Top

Backup and Disaster Recovery

  • ### What is Backup and Disaster Recovery?
Backup and Disaster Recovery (BDR) is a combination of data backup and disaster recovery solutions that work together to ensure an organization's business continuity.

Key components: 1. Data Backup: - Regular data copies - Multiple backup locations - Automated backup processes

2. Disaster Recovery: - Recovery procedures - Failover systems - Business continuity plans

⬆ Back to Top

  • ### What are different types of backups?
Common backup types include:

1. Full Backup: - Complete copy of all data - Most time and space consuming - Fastest restore time

2. Incremental Backup: - Only backs up changes since last backup - Faster and requires less storage - Longer restore time

3. Differential Backup: - Backs up changes since last full backup - Balance between full and incremental - Medium restore time

⬆ Back to Top

Cloud Native Architecture

  • ### What is Cloud Native Architecture?
Cloud Native Architecture is an approach to designing and building applications that exploits the advantages of the cloud computing delivery model. It emphasizes:

1. Characteristics: - Scalability - Containerization - Automation - Orchestration - Microservices

2. Key Principles: - Design for automation - Build for resilience - Enable scalability - Embrace containerization - Practice continuous delivery

⬆ Back to Top

  • ### What are Microservices?
Microservices is an architectural style that structures an application as a collection of small autonomous services, modeled around a business domain.

Key characteristics: 1. Independence: - Separate codebases - Independent deployment - Different technology stacks

2. Communication: - API-based interaction - Event-driven - Service discovery

Example of a microservice API:

openapi: 3.0.0     info:       title: User Service API       version: 1.0.0     paths:       /users:         get:           summary: List users           responses:             '200':               description: List of users         post:           summary: Create user           responses:             '201':               description: User created

⬆ Back to Top

  • ### What is Service Mesh?
A service mesh is a dedicated infrastructure layer for handling service-to-service communication in microservices architectures.

Key components: 1. Data Plane: - Service proxies (sidecars) - Traffic handling - Security enforcement

2. Control Plane: - Configuration management - Policy enforcement - Service discovery

Example of Istio configuration:

apiVersion: networking.istio.io/v1alpha3     kind: VirtualService     metadata:       name: reviews-route     spec:       hosts:       - reviews       http:       - route:         - destination:             host: reviews             subset: v1           weight: 75         - destination:             host: reviews             subset: v2           weight: 25

⬆ Back to Top

Performance Testing

  • ### What is Performance Testing?
Performance Testing is a type of testing to determine how a system performs in terms of responsiveness and stability under various workload conditions.

Key aspects include: 1. Performance Metrics: - Response time - Throughput - Resource utilization - Scalability - Reliability

2. Testing Goals: - Identify bottlenecks - Determine system capacity - Validate performance requirements - Benchmark performance

⬆ Back to Top

  • ### What are different types of Performance Tests?
Common types of performance tests include:

1. Load Testing: - Tests system behavior under specific load - Validates system performance under expected conditions 2. Stress Testing: - Tests system behavior under peak load - Identifies breaking points 3. Endurance Testing: - Tests system behavior over extended periods - Identifies memory leaks and resource issues

Example of JMeter test plan:

<?xml version="1.0" encoding="UTF-8"?>     <jmeterTestPlan version="1.2">       <hashTree>         <TestPlan>           <elementProp name="TestPlan.userdefinedvariables">             <collectionProp name="Arguments.arguments"/>           </elementProp>           <stringProp name="TestPlan.comments"></stringProp>           <boolProp name="TestPlan.functional_mode">false</boolProp>           <boolProp name="TestPlan.serialize_threadgroups">false</boolProp>         </TestPlan>       </hashTree>     </jmeterTestPlan>

⬆ Back to Top

API Gateway and Service Mesh

  • ### What is an API Gateway?
An API Gateway acts as a reverse proxy to accept all API calls, aggregate various services, and return the appropriate result.

Key features: 1. Request Handling: - Authentication - SSL termination - Rate limiting 2. Integration: - Service discovery - Request routing - Response transformation

Example of Kong API Gateway configuration:

services:       - name: user-service         url: http://user-service:8000         routes:           - name: user-route             paths:               - /users         plugins:           - name: rate-limiting             config:               minute: 5               policy: local

⬆ Back to Top

  • ### What are the benefits of using API Gateway?
Key benefits include:

1. Security: - Centralized authentication - Authorization - SSL/TLS termination 2. Performance: - Caching - Request/Response transformation - Load balancing 3. Monitoring: - Analytics - Logging - Rate limiting

⬆ Back to Top

  • ### What is API Security?
API Security involves protecting APIs from threats and vulnerabilities while ensuring they remain accessible to authorized users.

Key security measures: 1. Authentication: - API keys - OAuth 2.0 - JWT tokens 2. Authorization: - Role-based access control - Scope-based access - Resource-level permissions

Example of OAuth2 configuration:

security:       oauth2:         client:           clientId: ${CLIENT_ID}           clientSecret: ${CLIENT_SECRET}         resource:           tokenInfoUri: https://api.auth.com/oauth/check_token

⬆ Back to Top

  • ### What is Rate Limiting?
Rate Limiting is a technique used to control the rate at which requests are processed or transmitted.

Key concepts: 1. Token Bucket Algorithm: - Fixed number of tokens - Tokens are replenished at a fixed rate - Tokens are consumed at a variable rate

2. Leaky Bucket Algorithm: - Fixed size bucket - Water leaks out at a fixed rate - Water is added at a variable rate

Example of Nginx Rate Limiting configuration:

http {         limitreqzone $binaryremoteaddr zone=one:10m rate=1r/s;

server { location / { limit_req burst=5 nodelay; } } }

⬆ Back to Top

  • ### What is API Documentation?
API Documentation is a set of documents that describe how to use an API. It includes:

1. API Reference: - Detailed description of each API endpoint - Request and response formats - Example requests and responses

2. API Usage Examples: - Code samples - API client libraries - API testing tools

Example of Swagger API Documentation:

swagger: '2.0'     info:       title: User Service API       version: 1.0.0     paths:       /users:         get:           summary: List users           responses:             '200':               description: List of users         post:           summary: Create user           responses:             '201':               description: User created

⬆ Back to Top

Container Orchestration Advanced

  • ### What are StatefulSets in Kubernetes?
StatefulSets are used to manage stateful applications, providing guarantees about the ordering and uniqueness of Pods.

Key features: 1. Stable Network Identity: - Predictable Pod names - Stable hostnames 2. Ordered Deployment: - Sequential creation - Sequential scaling - Sequential deletion

Example of StatefulSet:

apiVersion: apps/v1     kind: StatefulSet     metadata:       name: web     spec:       serviceName: "nginx"       replicas: 3       selector:         matchLabels:           app: nginx       template:         metadata:           labels:             app: nginx         spec:           containers:           - name: nginx             image: nginx:1.14.2             ports:             - containerPort: 80             volumeMounts:             - name: www               mountPath: /usr/share/nginx/html       volumeClaimTemplates:       - metadata:           name: www         spec:           accessModes: [ "ReadWriteOnce" ]           resources:             requests:               storage: 1Gi

⬆ Back to Top

  • ### What are DaemonSets in Kubernetes?
DaemonSets ensure that all (or some) nodes run a copy of a Pod. As nodes are added to the cluster, Pods are added to them.

Use cases: 1. Monitoring Agents 2. Log Collectors 3. Node-level Storage 4. Network Plugins

Example of DaemonSet:

apiVersion: apps/v1     kind: DaemonSet     metadata:       name: fluentd-elasticsearch     spec:       selector:         matchLabels:           name: fluentd-elasticsearch       template:         metadata:           labels:             name: fluentd-elasticsearch         spec:           containers:           - name: fluentd-elasticsearch             image: quay.io/fluentd_elasticsearch/fluentd:v2.5.2

⬆ Back to Top

  • ### What is Helm?
Helm is a package manager for Kubernetes that helps you manage Kubernetes applications through Helm Charts.

Key concepts: 1. Charts: - Package format - Collection of files - Template mechanism

2. Repositories: - Chart storage - Version control - Distribution

Example of Helm Chart:

apiVersion: v2     name: my-app     description: A Helm chart for my application     version: 0.1.0     dependencies:       - name: mysql         version: 8.8.3         repository: https://charts.bitnami.com/bitnami

⬆ Back to Top

  • ### What is Istio?
Istio is an open-source service mesh that provides a way to control how services communicate with one another. It includes:

1. Traffic Management: - Load balancing - Traffic routing - Fault injection - Traffic mirroring

2. Security: - Authentication - Authorization - Encryption - Mutual TLS

3. Observability: - Telemetry - Metrics - Tracing - Logging

⬆ Back to Top

  • ### What is Container Runtime Interface (CRI)?
Container Runtime Interface (CRI) is an API that allows container runtimes to interact with the container orchestrator. It includes:

1. Image Management: - Pulling images - Pushing images - Listing images - Deleting images

2. Container Management: - Creating containers - Starting containers - Stopping containers - Killing containers - Inspecting containers

3. Container Runtime: - Running containers - Pausing containers - Resuming containers - Executing commands in containers

⬆ Back to Top

DevOps Tools and Automation

  • ### What is Infrastructure Automation?
Infrastructure Automation is the process of scripting environments - from installing an operating system, to installing and configuring servers on instances, to configuring how the instances and software communicate with one another.

Key components: 1. Provisioning: - Resource creation - Configuration management - Application deployment

2. Orchestration: - Workflow automation - Service coordination - Resource scheduling

⬆ Back to Top

  • ### What is GitOps?
GitOps is a way of implementing Continuous Deployment for cloud native applications. It focuses on a developer-centric experience when operating infrastructure, by using tools developers are already familiar with, including Git and Continuous Deployment tools.

Principles: 1. Declarative: - Infrastructure as code - Application configuration as code 2. Version Controlled: - Git as single source of truth - Audit trail for changes 3. Automated: - Pull-based deployment - Continuous reconciliation

⬆ Back to Top

  • ### What is ArgoCD?
ArgoCD is a declarative, GitOps continuous delivery tool for Kubernetes. It allows you to declaratively manage your Kubernetes applications by using Git repositories as the source of truth.

Key features: 1. Declarative: - Infrastructure as code - Application configuration as code 2. Version Controlled: - Git as single source of truth - Audit trail for changes 3. Automated: - Pull-based deployment - Continuous reconciliation

⬆ Back to Top

  • ### What is Tekton?
Tekton is an open-source, cloud-native CI/CD framework that allows you to define, run, and observe CI/CD pipelines. It's designed to be extensible and can be used with any container runtime.

Key features: 1. Extensible: - Custom tasks - Custom resources - Custom pipelines

2. Cloud-native: - Container-based - Kubernetes-native - Serverless-friendly

⬆ Back to Top

  • ### What are Deployment Strategies?
Deployment Strategies are methods used to deploy applications to Kubernetes clusters. Common strategies include:

1. Blue-Green Deployment: - Deploy a new version of the application - Traffic is routed to the new version - Old version is kept running

2. Canary Deployment: - Deploy a new version of the application - Traffic is routed to the new version - Old version is kept running

3. Rolling Update: - Deploy a new version of the application - Old version is gradually replaced - Traffic is routed to the new version

4. Blue-Green with Rolling Update: - Deploy a new version of the application - Traffic is routed to the new version - Old version is gradually replaced

⬆ Back to Top

Cloud Cost Optimization

  • ### What is Cloud Cost Optimization?
Cloud Cost Optimization is the process of reducing your overall cloud spend by identifying mismanaged resources, eliminating waste, reserving capacity for higher discounts, and right-sizing computing services to scale.

Key strategies include: 1. Resource Optimization: - Right-sizing instances - Shutting down unused resources - Using auto-scaling effectively

2. Pricing Optimization: - Reserved Instances - Spot Instances - Savings Plans

⬆ Back to Top

  • ### What are Reserved Instances?
Reserved Instances (RIs) provide a significant discount compared to On-Demand pricing in exchange for a commitment to use a specific instance configuration for a one or three-year term.

Types of RIs:

Standard RIs:       - Highest discount (up to 75%)       - Least flexibility       - Best for steady-state workloads

Convertible RIs: - Lower discount (up to 54%) - More flexibility - Can change instance family, OS, tenancy

Scheduled RIs: - For predictable recurring schedules - Match capacity reservation to usage pattern

⬆ Back to Top

Site Reliability Engineering (SRE)

  • ### What is Site Reliability Engineering?
Site Reliability Engineering (SRE) is a discipline that incorporates aspects of software engineering and applies them to infrastructure and operations problems to create scalable and highly reliable software systems.

Key principles: 1. Embrace Risk: - Define acceptable risk levels - Use error budgets - Balance reliability and innovation

2. Eliminate Toil: - Automate manual tasks - Reduce operational overhead - Focus on engineering work

⬆ Back to Top

  • ### What are Service Level Objectives (SLOs)?
Service Level Objectives (SLOs) are specific, measurable targets for service performance that you set and agree to meet.

Example SLO definition:

Service: User Authentication     SLO:       Metric: Availability       Target: 99.9%       Window: 30 days       Measurement:         - Success rate of authentication requests         - Latency under 300ms for 99% of requests

⬆ Back to Top

  • ### What are Service Level Indicators (SLIs)?
Service Level Indicators (SLIs) are quantitative measures of service level aspects such as latency, throughput, availability, and error rate.

Common SLIs: 1. Request Latency: - Time to handle a request - Distribution of response times

2. Error Rate: - Failed requests/total requests - Error budget consumption

3. System Throughput: - Requests per second - Transactions per second

⬆ Back to Top

  • ### What is Error Budget?
An Error Budget is the maximum amount of time that a technical system can fail without contractual consequences. It's the difference between the SLO target and 100% reliability.

Example calculation:

SLO Target: 99.9% uptime     Error Budget: 100% - 99.9% = 0.1%     Monthly Error Budget: 43.2 minutes (0.1% of 30 days)

Key concepts: 1. Budget Calculation: - Based on SLO targets - Measured over time windows - Reset periodically

2. Budget Usage: - Track incidents - Monitor consumption - Alert on budget burn

⬆ Back to Top

  • ### What is Toil in SRE?
Toil is the kind of work tied to running a production service that tends to be manual, repetitive, automatable, tactical, devoid of enduring value, and that scales linearly as a service grows.

Characteristics of toil: 1. Manual work: - No automation - Human intervention required - Repetitive tasks

2. Impact: - Reduces time for project work - Increases operational overhead - Affects team morale

3. Solutions:

Automation: - Script repetitive tasks - Implement self-service tools - Create automated workflows

Process Improvement: - Identify toil sources - Set toil budgets - Track toil metrics

Engineering Solutions: - Design for automation - Build self-healing systems - Implement proper monitoring

⬆ Back to Top

DevOps Metrics and KPIs

  • ### What are DevOps Metrics?
DevOps metrics are measurements used to evaluate the performance and efficiency of DevOps practices and processes.

Key categories: 1. Velocity Metrics: - Deployment frequency - Lead time for changes - Time to market

2. Quality Metrics: - Change failure rate - Bug detection rate - Test coverage

3. Operational Metrics:

Performance:           - Application response time           - Error rates           - Resource utilization

Reliability: - System uptime - MTTR - MTBF

⬆ Back to Top

  • ### What is Mean Time to Recovery (MTTR)?
MTTR is the average time it takes to recover from a system failure or incident.

Calculation:

MTTR = Total Recovery Time / Number of Incidents

Components of MTTR: 1. Detection Time: - Time to identify the issue - Monitoring alerts

2. Response Time: - Time to begin addressing the issue - Team mobilization

3. Resolution Time: - Time to fix the issue - System restoration

⬆ Back to Top

Serverless Architecture

  • ### What is Serverless Computing?
Serverless computing is a cloud computing execution model where the cloud provider manages the infrastructure and automatically allocates resources based on demand.

Key characteristics: 1. No Server Management: - Zero infrastructure maintenance - Automatic scaling - Pay-per-use billing

2. Event-Driven: - Function triggers - Automatic execution - Stateless operations

Example AWS Lambda function:

exports.handler = async (event) => {         try {             const result = await processEvent(event);             return {                 statusCode: 200,                 body: JSON.stringify(result)             };         } catch (error) {             return {                 statusCode: 500,                 body: JSON.stringify({ error: error.message })             };         }     };

⬆ Back to Top

Database Management in DevOps

  • ### What is Database DevOps?
Database DevOps is the practice of applying DevOps principles to database development and management.

Key practices: 1. Version Control: - Schema versioning - Code-first approach - Migration scripts

2. Automation:

Continuous Integration:           - Automated testing           - Schema validation           - Data consistency checks

Continuous Delivery: - Automated deployments - Rollback procedures - Data synchronization

⬆ Back to Top

Network Security

  • ### What is Network Security in DevOps?
Network Security in DevOps involves implementing security measures throughout the development and deployment pipeline to protect applications and infrastructure.

Key components: 1. Infrastructure Security: - Firewalls - VPNs - Network segmentation

2. Application Security: - TLS encryption - API security - Authentication/Authorization

Example of security group configuration:

SecurityGroup:       Type: AWS::EC2::SecurityGroup       Properties:         GroupDescription: Web tier security group         SecurityGroupIngress:           - IpProtocol: tcp             FromPort: 443             ToPort: 443             CidrIp: 0.0.0.0/0           - IpProtocol: tcp             FromPort: 80             ToPort: 80             CidrIp: 0.0.0.0/0

⬆ Back to Top

  • ### What is Zero Trust Security?
Zero Trust Security is a security model that requires strict identity verification for every person and device trying to access resources in a private network.

Principles: 1. Never Trust, Always Verify: - Identity-based access - Continuous verification - Least privilege access

2. Implementation:

Access Control:           - Multi-factor authentication           - Identity and access management           - Device verification

Network Security: - Micro-segmentation - Network isolation - Encrypted communications

⬆ Back to Top

  • ### What is SSL/TLS?
SSL/TLS is a cryptographic protocol used to secure communications between a client and a server.

Key concepts: 1. Encryption: - Data is encrypted before transmission - Data is decrypted after transmission

2. Authentication: - Verifies the identity of the communicating parties

Example of SSL/TLS configuration:

security:       ssl:         enabled: true         protocol: TLSv1.2         ciphers:           - ECDHE-RSA-AES256-GCM-SHA384           - ECDHE-RSA-AES128-GCM-SHA256

⬆ Back to Top

  • ### What is a Web Application Firewall (WAF)?
A Web Application Firewall (WAF) is a security device that monitors incoming traffic to a web application and blocks malicious traffic.

Key features: 1. Filtering: - Filters out malicious traffic - Allows legitimate traffic

2. Authentication: - Verifies the identity of the communicating parties

Example of WAF configuration:

security:       waf:         enabled: true         rules:           - rule1           - rule2

⬆ Back to Top

  • ### What is Network Segmentation?
Network Segmentation is the practice of dividing a network into smaller, more manageable segments to improve security and performance.

Key concepts: 1. Segmentation: - Divides the network into smaller segments - Each segment is isolated from other segments

2. Security: - Prevents unauthorized access to sensitive data - Improves network performance

Example of network


README truncated. View on GitHub
🔗 More in this category

© 2026 GitRepoTrend · rohitg00/devops-interview-questions · Updated daily from GitHub