Interview Preparation
DevOps Interview Questions and Answers for Freshers — 2026
These are the most commonly asked DevOps interview questions for freshers in 2026 — compiled by Vtricks faculty based on real interview feedback from students placed at companies like IBM, Cisco, Amazon AWS, Microsoft, Infosys, Wipro in Bangalore.
There are currently 3,500+ active DevOps job openings in Bangalore. Freshers can expect ₹5–8 LPA at companies across Bangalore's tech corridor — Whitefield, Electronic City, Koramangala, and the CBD. Preparation matters: candidates who practise these questions consistently perform significantly better in technical rounds.
Interview Tips from Vtricks Faculty
- Always explain your reasoning process — interviewers want to see how you think, not just the final answer.
- Use real examples from projects you have worked on when answering scenario-based questions.
- If you don't know the answer, say so honestly and describe how you would find the answer — this is better than guessing.
- For Bangalore companies specifically: be ready to answer follow-up questions — they often go 2-3 levels deep on any concept.
- Always ask clarifying questions before answering complex scenario-based questions — this demonstrates professional problem-solving approach.
Easy — basic concept check
Medium — applied knowledge
All 21 Questions
DevOps Interview Questions — Freshers
Q1. What is DevOps and what problem does it solve?
Conceptual
Easy
ANSWER
DevOps is a culture and set of practices that combines software Development and IT Operations to shorten the software delivery lifecycle and continuously deliver high-quality software. It solves the traditional problem of Dev and Ops teams working in silos — developers write code and throw it over the wall to operations, leading to slow releases, finger-pointing when things break, and inconsistent environments. DevOps practices include CI/CD pipelines, infrastructure as code, monitoring, and collaboration tools that allow organisations to release software faster and more reliably.
Q2. What is the difference between Continuous Integration, Continuous Delivery, and Continuous Deployment?
Conceptual
Easy
ANSWER
Continuous Integration (CI) — developers merge code changes frequently (daily) and automated builds and tests run on every merge to catch integration issues early. Continuous Delivery (CD) — all code changes that pass CI are automatically prepared and tested for production release, but deployment to production requires manual approval. Continuous Deployment — goes one step further: every change that passes automated tests is automatically deployed to production without manual approval. Most companies practice CI/CD (continuous integration + continuous delivery) rather than full continuous deployment.
Q3. What is Docker and what problem does it solve?
Technical
Easy
ANSWER
Docker is a containerisation platform that packages an application and all its dependencies (libraries, runtime, configuration) into a standardised container that runs consistently across any environment. It solves the 'it works on my machine' problem — if it runs in a Docker container on your laptop, it runs the same way on the server. Containers are lighter than virtual machines because they share the host OS kernel instead of running a full OS. Docker components: Dockerfile (instructions to build image), Docker image (read-only template), Docker container (running instance of an image), Docker Hub (registry for sharing images).
Q4. What is the difference between a Docker image and a Docker container?
Technical
Easy
ANSWER
A Docker image is a read-only template containing the application code, dependencies, and configuration — like a blueprint or class definition. A Docker container is a running instance of an image — like an object created from a class. You can create multiple containers from the same image, each running independently. Images are built from Dockerfiles using docker build. Containers are started using docker run. Images are stored in registries (Docker Hub, AWS ECR). Containers are ephemeral — they can be started, stopped, and deleted without affecting the image.
Master These Questions
Practice DevOps with Live Mentors at Vtricks
300+ students placed · 82% placement rate · Starts at ₹35,000
Free Demo Class →
Q5. What is Kubernetes and why do organisations use it?
Conceptual
Easy
ANSWER
Kubernetes (K8s) is an open-source container orchestration platform that automates deployment, scaling, and management of containerised applications. Organisations use it because: it automatically restarts failed containers; it scales applications up or down based on load; it distributes traffic across multiple container instances (load balancing); it enables zero-downtime deployments with rolling updates; it manages secrets and configuration. Docker runs individual containers; Kubernetes manages clusters of containers across multiple machines. Kubernetes is the industry standard for running containers at scale.
Q6. What is Jenkins and how is it used in CI/CD?
Technical
Easy
ANSWER
Jenkins is an open-source automation server used to build CI/CD pipelines. It automates the steps of building, testing, and deploying software. In a typical Jenkins pipeline: Developer pushes code to Git → Jenkins detects the change via webhook → Jenkins pulls the code, runs the build (Maven, Gradle, npm) → runs automated tests (unit, integration) → if tests pass, builds a Docker image → pushes to container registry → deploys to staging or production. Jenkins uses Jenkinsfile to define pipelines as code. Alternatives to Jenkins include GitLab CI, GitHub Actions, CircleCI, and AWS CodePipeline.
Q7. What is Infrastructure as Code (IaC) and what tools are used?
Conceptual
Easy
ANSWER
Infrastructure as Code is the practice of managing and provisioning computing infrastructure through machine-readable configuration files rather than manual processes. Benefits: consistency (same infrastructure every time), version control (track changes in Git), reproducibility (recreate environments easily), automation (no manual clicking in consoles). Main IaC tools: Terraform (cloud-agnostic, works with AWS, Azure, GCP), AWS CloudFormation (AWS-specific), Ansible (configuration management and provisioning), Pulumi (uses programming languages like Python and JavaScript for IaC).
Q8. What is the difference between Git merge and Git rebase?
Technical
Easy
ANSWER
Git merge combines two branches by creating a new merge commit that ties together the histories of both branches — preserves complete history with branch structure. Git rebase moves or replays commits from one branch onto another — creates a linear, cleaner history by rewriting commit history. Use merge for: public branches, when you want to preserve complete history. Use rebase for: private feature branches to clean up commits before merging, keeping a linear history. Golden rule: never rebase commits that have been pushed to a shared repository — it rewrites history and causes problems for other developers.
Q9. What is a Kubernetes pod?
Technical
Easy
ANSWER
A pod is the smallest deployable unit in Kubernetes — it wraps one or more containers that share the same network namespace, storage, and lifecycle. Containers in the same pod communicate via localhost. Pods are ephemeral — they can be created, killed, and replaced automatically. In practice, you rarely create pods directly — you use higher-level abstractions: Deployment (for stateless applications), StatefulSet (for stateful applications like databases), DaemonSet (runs one pod per node). A pod is like a logical host for containers that need to work together closely.
Master These Questions
Practice DevOps with Live Mentors at Vtricks
300+ students placed · 82% placement rate · Starts at ₹35,000
Free Demo Class →
Q10. What is a load balancer and why is it important in DevOps?
Conceptual
Easy
ANSWER
A load balancer distributes incoming network traffic across multiple servers to ensure no single server becomes overwhelmed — improving availability, reliability, and performance. In DevOps context: Kubernetes Service of type LoadBalancer exposes applications externally with automatic traffic distribution. AWS Elastic Load Balancer routes traffic across EC2 instances or containers. Load balancers also enable zero-downtime deployments — traffic is shifted gradually from old to new instances. Types: Application Load Balancer (HTTP/HTTPS, path-based routing), Network Load Balancer (TCP, ultra-low latency), Classic Load Balancer (legacy).
Q11. What is the purpose of a Dockerfile?
Technical
Easy
ANSWER
A Dockerfile is a text file containing instructions to build a Docker image. Each instruction creates a layer in the image. Key instructions: FROM — specifies the base image; WORKDIR — sets the working directory inside the container; COPY — copies files from host to container; RUN — executes commands during build (install packages); ENV — sets environment variables; EXPOSE — documents which port the container listens on; CMD — specifies the default command to run when container starts; ENTRYPOINT — configures the container to run as an executable. Best practices: use official base images, minimise layers, use .dockerignore, avoid running as root.
Q12. What is Ansible and how does it differ from Terraform?
Technical
Medium
ANSWER
Ansible is a configuration management tool that automates application deployment, configuration, and task automation on existing servers using YAML playbooks. It is agentless — uses SSH. Terraform is an infrastructure provisioning tool that creates and manages cloud resources (VMs, networks, databases). The key difference: Terraform provisions infrastructure (creates the servers). Ansible configures what's on those servers (installs software, sets up config files). They are often used together: Terraform creates AWS EC2 instances, Ansible then installs and configures the application on them.
Q13. What is the difference between blue-green deployment and canary deployment?
Conceptual
Medium
ANSWER
Blue-green deployment maintains two identical production environments — blue (current live) and green (new version). Traffic is switched all at once from blue to green after testing. Rollback is instant — switch back to blue. Requires double the infrastructure. Canary deployment releases the new version to a small percentage of users first (1–5%), monitors for errors, then gradually increases traffic. If issues arise, only a few users are affected before rollback. Canary is better for catching unexpected production issues at scale. Blue-green is better for strict compliance requirements where you need an instant rollback option.
Q14. What is monitoring and observability in DevOps?
Conceptual
Easy
ANSWER
Monitoring tracks predefined metrics and alerts when thresholds are breached — it answers 'is the system healthy?'. Observability is the ability to understand the internal state of a system from its external outputs (logs, metrics, traces) — it answers 'why is the system unhealthy?'. The three pillars of observability: Metrics (Prometheus + Grafana for dashboards), Logs (ELK Stack — Elasticsearch, Logstash, Kibana — or Loki), Traces (distributed request tracing with Jaeger or Zipkin). Modern DevOps teams use all three together to quickly diagnose production issues.
Master These Questions
Practice DevOps with Live Mentors at Vtricks
300+ students placed · 82% placement rate · Starts at ₹35,000
Free Demo Class →
Q15. What is the purpose of .gitignore?
Technical
Easy
ANSWER
.gitignore is a file in a Git repository that specifies intentionally untracked files that Git should ignore — they are never staged or committed. Common patterns to ignore: node_modules/ (dependencies — can be regenerated), __pycache__/ and *.pyc (Python bytecode), .env (environment variables with secrets), *.log (log files), dist/ or build/ (compiled output), .DS_Store (macOS system files), *.tfstate (Terraform state files). Always add .env to .gitignore before initialising a repository to prevent accidentally committing secrets to version control.
Q16. What is SSH and how do you use it securely?
Technical
Easy
ANSWER
SSH (Secure Shell) is a cryptographic network protocol for securely accessing remote servers over an unsecured network. It provides encrypted communication, authentication, and secure file transfer (SCP, SFTP). Secure SSH practices: Disable password authentication — use SSH key pairs instead (ssh-keygen generates public/private key pair). Disable root login (PermitRootLogin no in sshd_config). Change default port from 22 to a non-standard port. Use fail2ban to block IPs with failed login attempts. Restrict access by IP with firewall rules. Rotate SSH keys regularly. Use bastion hosts for accessing private network resources.
Q17. Explain the concept of immutable infrastructure.
Conceptual
Medium
ANSWER
Immutable infrastructure means servers are never modified after deployment — instead of updating software on running servers, you replace them with new servers running updated images. Benefits: consistency (no configuration drift), reliability (new servers always start from a known state), easier rollbacks (keep previous image versions), security (limits attack surface). Implemented using tools like Docker + Kubernetes (replace containers, not update them), Packer (build machine images), Terraform (recreate infrastructure). Contrast with mutable infrastructure where servers are updated in-place using configuration management tools, which can lead to configuration drift over time.
Q18. What is a reverse proxy and why is Nginx commonly used?
Technical
Medium
ANSWER
A reverse proxy sits in front of web servers and forwards client requests to the appropriate backend server. It hides the backend infrastructure, distributes load, handles SSL termination, caches static content, and compresses responses. Nginx is commonly used as a reverse proxy because it is lightweight, high-performance (handles 10,000+ concurrent connections with low memory), and highly configurable. Common Nginx use cases: serve static files directly (images, CSS, JS), proxy requests to application servers (Django, Node.js), terminate HTTPS and forward HTTP to backend, rate limiting, and as a load balancer across multiple application instances.
Q19. What is the difference between TCP and UDP?
Technical
Easy
ANSWER
TCP (Transmission Control Protocol) is connection-oriented — it establishes a connection via a 3-way handshake, guarantees packet delivery and order, provides error checking and retransmission. Slower but reliable. Used for: HTTP/HTTPS, SSH, FTP, email. UDP (User Datagram Protocol) is connectionless — sends packets without establishing a connection, does not guarantee delivery or order, no retransmission. Faster but unreliable. Used for: video streaming, online gaming, DNS lookups, VoIP — situations where speed matters more than perfect reliability and occasional packet loss is acceptable.
Q20. What is container orchestration and why is it needed?
Conceptual
Easy
ANSWER
Container orchestration automates the deployment, scaling, networking, and management of containers across a cluster of machines. It is needed because running containers at scale in production manually is impractical — you need to manage hundreds or thousands of containers across multiple servers. Container orchestration handles: scheduling containers to appropriate nodes, health monitoring and automatic restart of failed containers, horizontal scaling based on CPU/memory metrics, service discovery so containers find each other, rolling updates with zero downtime, secret and configuration management. Kubernetes is the dominant container orchestration platform; alternatives include Docker Swarm and Apache Mesos.
Q21. How would you troubleshoot a failing deployment in a CI/CD pipeline?
Scenario
Medium
ANSWER
Structured troubleshooting approach: 1) Check pipeline logs — identify which stage failed (build, test, deploy). 2) Check the error message — is it a code error, dependency issue, or infrastructure problem? 3) If build failed — check if dependencies are available, check Dockerfile syntax, verify base image is accessible. 4) If tests failed — check which tests failed and why, check if test environment is configured correctly. 5) If deployment failed — check target environment health, check secrets and credentials, verify network access. 6) Check recent changes — what changed in code, config, or infrastructure since the last successful deployment? 7) Reproduce in local environment if possible. 8) Fix, verify in staging, then re-deploy.
Company Insights
What DevOps Companies in Bangalore Actually Ask
Based on interview feedback from Vtricks students placed at Bangalore companies in 2026:
Round 1 — Written/Online Test
Most Bangalore companies start with a written or online test covering devops fundamentals, multiple choice questions on Docker and Kubernetes, and basic problem-solving questions. Duration: 30–60 minutes. Companies like IBM and Cisco use platforms like HackerRank or their own internal assessments.
Round 2 — Technical Interview (Most Important)
This is where most candidates are filtered. Expect: direct questions from this list, hands-on tasks (write a SQL query, debug a piece of code, explain a dashboard you built), and scenario-based questions where you walk through how you would solve a real problem. Be prepared to share your screen and code live.
Round 3 — Managerial / HR Round
Focuses on: why you chose devops as a career, how you handle ambiguous requirements, a project you are proud of (have this ready in detail — situation, what you did, result), and salary expectations. Research the company's tech stack and recent news before this round.
Tools You Must Be Able to Demonstrate
- Docker — be ready to use this live in an interview
- Kubernetes — be ready to use this live in an interview
- Jenkins — be ready to use this live in an interview
- Terraform — be ready to use this live in an interview
- AWS — be ready to use this live in an interview
- Azure — be ready to use this live in an interview
More Resources
More DevOps Interview Preparation
Prepare for Your DevOps Interview at Vtricks
Our students practise all these questions with live mentors and get placed at top Bangalore companies. Join 300+ students already working in DevOps.
Mock interviews with mentors
Live daily classes
82% placement rate
Starts at ₹35,000
Book Free Demo Class at Vtricks →
Vijayanagar, Bangalore · Online also available · No payment required