Comprehensive DevOps Interview Guide: Key Concepts, Tools, and Practices

In recent years, the number of DevOps engineer job postings has surged, leading to over 500,000 clicks on "DevOps interview questions"; multinational companies often have multiple specialist roles, and interview topics can be broad and complex.

1. What is DevOps?

DevOps combines "Developer" and "Operator" to bridge the gap between development and operations teams, enabling continuous delivery (CI/CD) of high‑quality software.

2. Difference between DevOps and Agile

DevOps focuses on collaboration across the entire software lifecycle, while Agile emphasizes iterative, customer‑feedback‑driven development.

3. Most widely used DevOps tools

Saltstack

Puppet

Chef

Git

Jenkins

Ansible

Docker

SonarQube

Nexus/Artifactory

Harbor

Kubernetes

Maven/Gradle

4. DevOps lifecycle stages

Plan

Code

Build

Test

Integrate

Deploy

Operate

Monitor

5. Main advantages of DevOps

Continuous software delivery

Fewer complex problems

Earlier defect detection and faster fixes

Faster feature delivery

Reliable work conditions

Enhanced team collaboration and communication

6. What is Continuous Integration (CI)?

Developers merge code into a main repository where each integration is automatically built and tested, allowing early detection of errors.

7. Difference between Continuous Delivery and Continuous Deployment

Continuous Delivery

Continuous Deployment

Ensures code can be safely released to production.

Every update that passes automated tests is automatically deployed.

Guarantees expected functionality of applications and services.

Improves speed and reliability of software release.

Delivers each change to a production‑like environment via strict automated testing.

Establishes monitoring practices even without explicit developer approval.

8. Role of AWS in DevOps

Flexible services without needing to install/configure software.

Scalable from single to multiple instances.

Automation of tasks and workflows.

Security via IAM for permissions and policies.

Large partner ecosystem for integration and extension.

9. What is version control?

Version control (source‑code control) monitors and manages changes to software code, allowing restoration, comparison, and audit of modifications.

10. Benefits of using version control

Enables independent work on files and later merging.

Organizes all iterations for easy retrieval.

Tracks changes with commit messages and author information.

Provides redundancy via distributed systems like Git.

11. Purpose of SSH

Secure Shell (SSH) is a command‑line protocol that provides encrypted remote server access, replacing insecure protocols like Telnet.

12. How to push files from local machine to GitHub using Git

Step 1: Link local repository to remote: git remote add origin [web addr.] (e.g., git remote add https://github.com/file.git) Step 2: Push files:

git push origin master

13. Concept of Git branches

New features are developed on separate branches; the default branch is master. After changes are complete, they are merged back into the main branch.

14. Three most important DevOps KPIs

Mean Time to Recovery (MTTR)

Deployment frequency

Deployment failure rate

15. How Ansible works

Ansible uses a control machine (with SSH) to manage nodes without agents; playbooks written in YAML define tasks.

16. What is Continuous Testing (CT)?

CT runs automated test cases as part of the DevOps pipeline, providing immediate feedback on code quality and business risk.

17. Difference between Continuous Testing and Automated Testing

Continuous Testing

Automated Testing

All automated test cases run as part of the delivery process.

Automated testing replaces manual testing by enabling repeatable test execution.

Focuses on early commercial risk detection.

Uses pass/fail results to indicate functional correctness.

18. Jenkins master‑slave architecture

When code is committed, the Jenkins master pulls updates from the remote repository and distributes build, test, and reporting tasks to slave agents.

19. Key concepts in a Jenkins pipeline

Pipeline: defines the CD workflow.

Agent: execution environment for pipeline steps.

Steps: individual tasks.

Stage: logical grouping of steps (e.g., build, test, deploy).

20. Basic Git commands

Command

Purpose

git init

Initialize a new repository.

git config --global user.name "[name]"

git config --global user.email "[email]"

Set user identity.

git clone <repo‑path>

Clone a repository locally.

git add .

Add files to the staging area.

git commit -m "message"

Create a snapshot of staged changes.

git diff

Show differences between versions.

git status

List files needing commit.

git rm <file>

Remove files and stage the removal.

git show <commit>

Display commit metadata and changes.

git branch [name] / git branch -d [name]

Create or delete branches, list all branches.

21. Copying Jenkins from one server to another

1) Copy the job directories. 2) Clone a job directory and rename it for the new job. 3) Rename directories as needed.

22. Resources in Puppet

Fundamental components of configuration‑management tools.

Represent node characteristics such as software or services.

Declared in manifests to enforce desired state.

23. What are Ansible roles?

Ansible roles are collections of tasks, variables, files, and templates embedded in a playbook.

24. Purpose of a Dockerfile

Defines instructions to build Docker images.

Images can be run as containers.

Images are stored in registries for reuse.

25. Running multiple containers as a single service

Docker Compose allows multiple containers to be defined in a YAML file and run together as one service.

26. Top DevOps tools (author’s experience)

Git (version control)

Jenkins (CI)

Selenium (continuous testing)

Puppet, Chef, Ansible (configuration management)

Prometheus (monitoring)

Docker (containerization)

27. How these tools work together

Developers write code and push to Git.

Jenkins pulls code, builds with Ant/Maven.

Puppet sets up test environments; Selenium runs tests.

Successful builds are deployed to production.

Prometheus monitors deployed services.

Docker containers provide isolated test environments.

28. Difference between Puppet modules and manifests

Modules contain manifests, data, and a defined directory structure; manifests are the code files (PP) that describe configurations.

29. Configuring systems with Puppet

Use Puppet Agent and Master in a client‑server model.

Or use standalone Puppet applications.

30. Difference between Ansible playbook and ad‑hoc commands

Playbooks are reusable scripts for repeatable configuration tasks.

Ad‑hoc commands are quick, one‑off tasks.

31. Ansible vs. Puppet

Ansible

Puppet

Agentless installation

Agent‑based installation

Written in Python

Written in Ruby

Configuration files in YAML

Configuration files in DSL

32. Why Chef uses SSL certificates

Ensures secure communication between Chef server and clients.

Clients have private/public key pairs; server stores public keys.

SSL certificates embed client private keys for authentication.

33. Difference between Chef Cookbooks and Recipes

Recipes are collections of resources written in Ruby to configure software.

Cookbooks contain recipes plus additional files to achieve the desired node state.

34. Docker architecture

Client‑server model with Docker client issuing commands to the Docker daemon via REST API.

Docker daemon builds images and runs containers.

Images are built from Dockerfiles; containers package applications and dependencies.

Docker registry stores and distributes images.

35. What is kubectl?

kubectl is a command‑line tool for interacting with Kubernetes clusters, allowing deployment, inspection, and management of resources.

36. Selenium components

IDE – Firefox plugin for rapid prototyping.

RemoteControl (RC) – Language‑agnostic test automation platform.

WebDriver – Browser‑agnostic automation without JavaScript reliance.

Grid – Enables concurrent testing across multiple nodes.

37. How containers communicate in Kubernetes

Pods map containers together; within the flat overlay network, any pod can communicate with any other pod.

38. IaC and configuration management

Infrastructure as Code stores infrastructure definitions in version‑controlled files, enabling collaborative, repeatable, and auditable configuration; tools like Ansible use YAML and SSH to apply desired state without a central server.

Conclusion

As a DevOps engineer, deep knowledge of processes, tools, and technologies is essential; mastering the topics covered above will greatly improve interview performance and career prospects.