{"id":79858,"date":"2025-05-17T18:09:14","date_gmt":"2025-05-17T12:39:14","guid":{"rendered":"https:\/\/www.guvi.in\/blog\/?p=79858"},"modified":"2026-02-18T19:31:57","modified_gmt":"2026-02-18T14:01:57","slug":"devops-interview-questions-and-answers","status":"publish","type":"post","link":"https:\/\/www.guvi.in\/blog\/devops-interview-questions-and-answers\/","title":{"rendered":"35 Important DevOps Interview Questions and Answers [Includes All 3 Levels]"},"content":{"rendered":"\n<p>Are you preparing for a DevOps interview and becoming nervous as you are unsure of what questions to expect? In today\u2019s fast-paced tech world, DevOps professionals are expected to be not only strong in coding and automation but also skilled in system reliability, container orchestration, and CI\/CD practices.&nbsp;<\/p>\n\n\n\n<p>Whether you&#8217;re a fresher stepping into your first DevOps role or a seasoned engineer aiming for a senior position, understanding the types of questions interviewers ask and how to answer them confidently can give you a competitive edge.<\/p>\n\n\n\n<p>This article covers the top 35 DevOps interview questions, divided into Beginner, Intermediate, and Advanced levels, to help you structure your preparation effectively. So, without further ado, let us get started!<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Quick Answer<\/strong><\/h2>\n\n\n\n<p>DevOps interviews focus on CI\/CD pipelines, automation, version control, containers, orchestration, infrastructure as code, monitoring, and troubleshooting. They also test how you handle deployments, rollbacks, scaling, incident management, and real-world pipeline issues.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Beginner Level DevOps Interview Questions And Answers<\/strong><\/h2>\n\n\n\n<figure class=\"wp-block-image size-full\"><img decoding=\"async\" width=\"1200\" height=\"628\" src=\"https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2025\/05\/2087394688.png\" alt=\"Beginner Level DevOps Interview Questions And Answers\" class=\"wp-image-79966\" srcset=\"https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2025\/05\/2087394688.png 1200w, https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2025\/05\/2087394688-300x157.png 300w, https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2025\/05\/2087394688-768x402.png 768w, https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2025\/05\/2087394688-150x79.png 150w\" sizes=\"(max-width: 1200px) 100vw, 1200px\" title=\"\"><\/figure>\n\n\n\n<p>If you&#8217;re new to <a href=\"https:\/\/www.guvi.in\/blog\/what-is-devops\/\" target=\"_blank\" rel=\"noreferrer noopener\">DevOps<\/a> or coming from a traditional IT or software development background, it\u2019s important to get a solid grasp of the foundational concepts first.&nbsp;<\/p>\n\n\n\n<p>These beginner-level questions cover the core principles, basic tools, and essential terminology that every DevOps professional should understand before progressing further.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>1. What is DevOps?<\/strong><\/h3>\n\n\n\n<figure class=\"wp-block-image size-full\"><img decoding=\"async\" width=\"1200\" height=\"628\" src=\"https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2025\/05\/2087394689.png\" alt=\"What is DevOps\" class=\"wp-image-79967\" srcset=\"https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2025\/05\/2087394689.png 1200w, https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2025\/05\/2087394689-300x157.png 300w, https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2025\/05\/2087394689-768x402.png 768w, https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2025\/05\/2087394689-150x79.png 150w\" sizes=\"(max-width: 1200px) 100vw, 1200px\" title=\"\"><\/figure>\n\n\n\n<p>DevOps is a set of practices that bridges the gap between software development (Dev) and IT operations (Ops). The goal is to shorten the software development lifecycle while delivering high-quality software continuously.<\/p>\n\n\n\n<p><strong>Key Features:<\/strong><\/p>\n\n\n\n<ul>\n<li>Emphasizes automation, <a href=\"https:\/\/www.guvi.in\/blog\/continuous-integration-vs-continuous-deployment\/\" target=\"_blank\" rel=\"noreferrer noopener\">continuous integration<\/a>, and collaboration.<\/li>\n\n\n\n<li>Promotes shared responsibility for software delivery and infrastructure.<\/li>\n\n\n\n<li>Encourages iterative improvements through feedback loops.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>2. What are the key benefits of DevOps?<\/strong><\/h3>\n\n\n\n<p>DevOps offers a range of technical and business benefits:<\/p>\n\n\n\n<ul>\n<li><strong>Faster Time to Market<\/strong>: Automated testing and deployment speed up releases.<\/li>\n\n\n\n<li><strong>Improved Collaboration<\/strong>: Teams share responsibilities and work together better.<\/li>\n\n\n\n<li><strong>Stable Environments<\/strong>: Frequent, small updates reduce risks and errors.<\/li>\n\n\n\n<li><strong>Rapid Recovery<\/strong>: Easy rollback and monitoring improve uptime.<\/li>\n\n\n\n<li><strong>Increased Efficiency<\/strong>: Automation removes manual, repetitive tasks.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>3. What is the difference between Agile and DevOps?<\/strong><\/h3>\n\n\n\n<p><a href=\"https:\/\/www.guvi.in\/courses\/project-management\/agile-fundamentals\/?utm_source=blog&amp;utm_medium=hyperlink&amp;utm_campaign=devops-interview-questions-and-answers\" target=\"_blank\" rel=\"noreferrer noopener\">Agile<\/a> and DevOps complement each other but focus on different aspects of development.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><tbody><tr><td><strong>Aspect<\/strong><\/td><td><strong>Agile<\/strong><\/td><td><strong>DevOps<\/strong><\/td><\/tr><tr><td>Focus<\/td><td>Development process<\/td><td>End-to-end software delivery<\/td><\/tr><tr><td>Teams<\/td><td>Developers<\/td><td>Dev + Ops (cross-functional)<\/td><\/tr><tr><td>Goal<\/td><td>Faster iteration of features<\/td><td>Faster, reliable delivery<\/td><\/tr><\/tbody><\/table><figcaption class=\"wp-element-caption\"><strong>Difference between Agile and D<\/strong><\/figcaption><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>4. What is Continuous Integration (CI)?<\/strong><\/h3>\n\n\n\n<p>Continuous Integration is a practice where developers frequently push code to a shared repository. Each integration triggers an automated build and test process.<\/p>\n\n\n\n<p><strong>Why it\u2019s important:<\/strong><\/p>\n\n\n\n<ul>\n<li>Helps catch bugs early<\/li>\n\n\n\n<li>Reduces integration issues<\/li>\n\n\n\n<li>Promotes faster feedback<\/li>\n<\/ul>\n\n\n\n<p><strong>Tools<\/strong>: Jenkins, Travis CI, GitHub Actions<\/p>\n\n\n\n<p><strong>Example Flow<\/strong>:<\/p>\n\n\n\n<ol>\n<li>The developer commits code to <a href=\"https:\/\/www.guvi.in\/blog\/git-flow-and-version-control-best-practices\/\" target=\"_blank\" rel=\"noreferrer noopener\">Git.<\/a><\/li>\n\n\n\n<li>Jenkins detects the change and runs the build + tests.<\/li>\n\n\n\n<li>Feedback is sent instantly.<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>5. What is Continuous Delivery (CD)?<\/strong><\/h3>\n\n\n\n<p>Continuous Delivery builds on CI. It ensures that your code is always in a deployable state and can be pushed to production at any time \u2014 manually or automatically.<\/p>\n\n\n\n<p><strong>Key Characteristics:<\/strong><\/p>\n\n\n\n<ul>\n<li>Every build is production-ready<\/li>\n\n\n\n<li>Automated testing at each stage<\/li>\n\n\n\n<li>Reduces deployment risks<\/li>\n<\/ul>\n\n\n\n<p><em>Read More: <\/em><a href=\"https:\/\/www.guvi.in\/blog\/understanding-ci-cd\/\" target=\"_blank\" rel=\"noreferrer noopener\"><em>Understanding CI\/CD: A Simple Guide for Beginners<\/em><\/a><\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>6. What is version control, and why is it important?<\/strong><\/h3>\n\n\n\n<p><a href=\"https:\/\/www.guvi.in\/blog\/guide-for-advanced-git-techniques\/\" target=\"_blank\" rel=\"noreferrer noopener\">Version control<\/a> is a system that tracks changes to code over time. It enables developers to collaborate, manage revisions, and restore previous versions if needed.<\/p>\n\n\n\n<p><strong>Why it matters<\/strong>:<\/p>\n\n\n\n<ul>\n<li>Prevents overwriting others&#8217; work<\/li>\n\n\n\n<li>Enables branching and merging<\/li>\n\n\n\n<li>Supports rollback and auditing<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>7. What are some popular DevOps tools?<\/strong><\/h3>\n\n\n\n<p><a href=\"https:\/\/www.guvi.in\/blog\/best-devops-tools\/\" target=\"_blank\" rel=\"noreferrer noopener\">DevOps tools<\/a> support automation across development, deployment, and operations.<\/p>\n\n\n\n<p><strong>Categories and Examples:<\/strong><\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><tbody><tr><td><strong>Area<\/strong><\/td><td><strong>Tools<\/strong><\/td><\/tr><tr><td>Version Control<\/td><td>Git<\/td><\/tr><tr><td>CI\/CD<\/td><td>Jenkins, GitLab CI<\/td><\/tr><tr><td>Configuration Management<\/td><td>Ansible, Puppet<\/td><\/tr><tr><td>Containerization<\/td><td>Docker<\/td><\/tr><tr><td>Orchestration<\/td><td>Kubernetes<\/td><\/tr><tr><td>Monitoring<\/td><td>Prometheus, Grafana<\/td><\/tr><\/tbody><\/table><figcaption class=\"wp-element-caption\"><strong>Popular DevOps tools<\/strong><\/figcaption><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>8. What is a build pipeline?<\/strong><\/h3>\n\n\n\n<figure class=\"wp-block-image size-full\"><img decoding=\"async\" width=\"1200\" height=\"628\" src=\"https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2025\/05\/2087394690.png\" alt=\"What is a build pipeline\" class=\"wp-image-79968\" srcset=\"https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2025\/05\/2087394690.png 1200w, https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2025\/05\/2087394690-300x157.png 300w, https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2025\/05\/2087394690-768x402.png 768w, https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2025\/05\/2087394690-150x79.png 150w\" sizes=\"(max-width: 1200px) 100vw, 1200px\" title=\"\"><\/figure>\n\n\n\n<p>A build pipeline is a set of automated steps that transform source code into deployable software.<\/p>\n\n\n\n<p><strong>Common Stages:<\/strong><\/p>\n\n\n\n<ol>\n<li>Code Checkout<\/li>\n\n\n\n<li>Build<\/li>\n\n\n\n<li>Test<\/li>\n\n\n\n<li>Package<\/li>\n\n\n\n<li>Deploy<\/li>\n<\/ol>\n\n\n\n<p><strong>Benefits:<\/strong><\/p>\n\n\n\n<ul>\n<li>Eliminates manual errors<\/li>\n\n\n\n<li>Ensures consistency<\/li>\n\n\n\n<li>Enables fast, reliable releases<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>9. What is infrastructure as code (IaC)?<\/strong><\/h3>\n\n\n\n<p><a href=\"https:\/\/www.guvi.in\/blog\/infrastructure-as-code-iac\/\" target=\"_blank\" rel=\"noreferrer noopener\">Infrastructure as Code (IaC) <\/a>is the practice of managing and provisioning infrastructure using code, rather than manual processes.<\/p>\n\n\n\n<p><strong>Benefits:<\/strong><\/p>\n\n\n\n<ul>\n<li>Consistency across environments<\/li>\n\n\n\n<li>Version-controlled infra<\/li>\n\n\n\n<li>Easy rollback and scalability<\/li>\n<\/ul>\n\n\n\n<p><strong>Tools<\/strong>: Terraform, <a href=\"https:\/\/www.guvi.in\/blog\/guide-for-amazon-web-services\/\" target=\"_blank\" rel=\"noreferrer noopener\">AWS<\/a> CloudFormation, Ansible<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>10. What is a container?<\/strong><\/h3>\n\n\n\n<p>A container is a lightweight, standalone package that includes everything needed to run an application: code, runtime, libraries, and configs.<\/p>\n\n\n\n<p><strong>Benefits:<\/strong><\/p>\n\n\n\n<ul>\n<li>Platform-independent<\/li>\n\n\n\n<li>Fast startup<\/li>\n\n\n\n<li>Efficient resource usage<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Intermediate Level DevOps Interview Questions and Answers<\/strong><\/h2>\n\n\n\n<figure class=\"wp-block-image size-full\"><img decoding=\"async\" width=\"1200\" height=\"628\" src=\"https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2025\/05\/2087394691.png\" alt=\"Intermediate Level DevOps Interview Questions and Answers\" class=\"wp-image-79969\" srcset=\"https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2025\/05\/2087394691.png 1200w, https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2025\/05\/2087394691-300x157.png 300w, https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2025\/05\/2087394691-768x402.png 768w, https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2025\/05\/2087394691-150x79.png 150w\" sizes=\"(max-width: 1200px) 100vw, 1200px\" title=\"\"><\/figure>\n\n\n\n<p>Once you&#8217;re comfortable with the basics, it&#8217;s time to explore how DevOps practices are applied in real-world scenarios.&nbsp;<\/p>\n\n\n\n<p>The following questions will test your hands-on experience with popular tools like Jenkins, Docker, Kubernetes, and your understanding of CI\/CD pipelines, automation, and monitoring strategies.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>11. How does Jenkins work in a CI\/CD pipeline?<\/strong><\/h3>\n\n\n\n<p>Jenkins is an open-source automation server that helps automate parts of the software development lifecycle, especially <strong>Continuous Integration<\/strong> and <strong>Continuous Delivery<\/strong>.<\/p>\n\n\n\n<p><strong>How Jenkins Works:<\/strong><\/p>\n\n\n\n<ul>\n<li>Developers push code to a Git repository.<\/li>\n\n\n\n<li>Jenkins polls the repository or listens for webhooks.<\/li>\n\n\n\n<li>On detecting changes, Jenkins triggers:<br>\n<ul>\n<li>Build (compile the code)<\/li>\n\n\n\n<li>Test (unit\/integration tests)<\/li>\n\n\n\n<li>Deploy (to staging or production)<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>12. What is a Jenkinsfile?<\/strong><\/h3>\n\n\n\n<p>A Jenkinsfile is a text file that contains the definition of a Jenkins pipeline and is stored in the source code repository.<\/p>\n\n\n\n<p><strong>Types of Pipelines:<\/strong><\/p>\n\n\n\n<ul>\n<li>Declarative (structured, beginner-friendly)<\/li>\n\n\n\n<li>Scripted (Groovy-based, more flexible)<\/li>\n<\/ul>\n\n\n\n<p><strong>Example Jenkinsfile (Declarative):<\/strong><\/p>\n\n\n\n<p><em>groovy<\/em> <\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>pipeline {\n\n&nbsp;&nbsp;agent any\n\n&nbsp;&nbsp;stages {\n\n&nbsp;&nbsp;&nbsp;&nbsp;stage('Build') {\n\n&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;steps {\n\n&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;echo 'Building...'\n\n&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;}\n\n&nbsp;&nbsp;&nbsp;&nbsp;}\n\n&nbsp;&nbsp;&nbsp;&nbsp;stage('Test') {\n\n&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;steps {\n\n&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;echo 'Testing...'\n\n&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;}\n\n&nbsp;&nbsp;&nbsp;&nbsp;}\n\n&nbsp;&nbsp;&nbsp;&nbsp;stage('Deploy') {\n\n&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;steps {\n\n&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;echo 'Deploying...'\n\n&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;}\n\n&nbsp;&nbsp;&nbsp;&nbsp;}\n\n&nbsp;&nbsp;}\n\n}<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>13. What are the differences between Docker and a Virtual Machine?<\/strong><\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table><tbody><tr><td><strong>Aspect<\/strong><\/td><td><strong>Docker (Container)<\/strong><\/td><td><strong>Virtual Machine<\/strong><\/td><\/tr><tr><td>OS Layer<\/td><td>Shares host OS<\/td><td>Includes guest OS<\/td><\/tr><tr><td>Boot Time<\/td><td>Seconds<\/td><td>Minutes<\/td><\/tr><tr><td>Size<\/td><td>MBs<\/td><td>GBs<\/td><\/tr><tr><td>Performance<\/td><td>High<\/td><td>Comparatively lower<\/td><\/tr><tr><td>Use Case<\/td><td>Lightweight app environments<\/td><td>Full OS emulation<\/td><\/tr><\/tbody><\/table><figcaption class=\"wp-element-caption\">D<strong>ifferences between Docker and a Virtual Machine<\/strong><\/figcaption><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>14. How do you monitor applications in a DevOps environment?<\/strong><\/h3>\n\n\n\n<p>Monitoring is essential to ensure performance, reliability, and uptime.<\/p>\n\n\n\n<p><strong>Common Monitoring Stack:<\/strong><\/p>\n\n\n\n<ul>\n<li><strong>Metrics<\/strong>: Prometheus + Grafana<\/li>\n\n\n\n<li><strong>Logs<\/strong>: ELK Stack (Elasticsearch, Logstash, Kibana)<\/li>\n\n\n\n<li><strong>APM<\/strong>: Datadog, New Relic<\/li>\n<\/ul>\n\n\n\n<p><strong>Key Metrics to Monitor<\/strong>:<\/p>\n\n\n\n<ul>\n<li>CPU &amp; memory usage<\/li>\n\n\n\n<li>Request latency<\/li>\n\n\n\n<li>Error rates<\/li>\n\n\n\n<li>Uptime\/downtime<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>15. Explain the concept of \u201cshift left\u201d in DevOps.<\/strong><\/h3>\n\n\n\n<p>&#8220;Shift left&#8221; refers to moving critical tasks \u2014 like testing, security, and performance checks \u2014 earlier in the software development lifecycle.<\/p>\n\n\n\n<p><strong>Why Shift Left Matters:<\/strong><\/p>\n\n\n\n<ul>\n<li>Catch bugs earlier = cheaper fixes<\/li>\n\n\n\n<li>Improve development speed<\/li>\n\n\n\n<li>Reduce deployment failures<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>16. What is the role of Kubernetes in DevOps?<\/strong><\/h3>\n\n\n\n<p><a href=\"https:\/\/kubernetes.io\/\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">Kubernetes<\/a> (K8s) is a container orchestration tool used to automate the deployment, scaling, and management of containerized applications.<\/p>\n\n\n\n<p><strong>Key Features:<\/strong><\/p>\n\n\n\n<ul>\n<li>Self-healing (auto-restart failed containers)<\/li>\n\n\n\n<li>Load balancing<\/li>\n\n\n\n<li>Rolling updates<\/li>\n\n\n\n<li>Horizontal scaling<\/li>\n\n\n\n<li>Secrets and config management<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>17. How would you secure a DevOps pipeline?<\/strong><\/h3>\n\n\n\n<p>Securing a DevOps pipeline involves protecting the flow of code from commit to deployment.<\/p>\n\n\n\n<p><strong>Best Practices:<\/strong><\/p>\n\n\n\n<ul>\n<li>Use <strong>secret managers<\/strong> (e.g., Vault, AWS Secrets Manager)<\/li>\n\n\n\n<li>Enable <strong>RBAC (Role-Based Access Control)<\/strong><\/li>\n\n\n\n<li>Enforce <strong>code signing and image scanning<\/strong><\/li>\n\n\n\n<li>Run <strong>automated security tests<\/strong> (e.g., Snyk, OWASP ZAP)<\/li>\n\n\n\n<li>Encrypt data at rest and in transit<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>18. What are blue-green deployments?<\/strong><\/h3>\n\n\n\n<p>Blue-Green deployment is a <strong>release strategy<\/strong> where two identical environments are used:<\/p>\n\n\n\n<ul>\n<li><strong>Blue<\/strong>: Active production<\/li>\n\n\n\n<li><strong>Green<\/strong>: New version to be deployed<\/li>\n<\/ul>\n\n\n\n<p><strong>Steps:<\/strong><\/p>\n\n\n\n<ol>\n<li>Deploy the new version to Green.<\/li>\n\n\n\n<li>Run tests on Green.<\/li>\n\n\n\n<li>Switch traffic from Blue to Green (via load balancer).<\/li>\n\n\n\n<li>If anything breaks, switch back to Blue instantly.<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>19. What is the difference between push-based and pull-based deployments?<\/strong><\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table><tbody><tr><td><strong>Deployment Type<\/strong><\/td><td><strong>Push-Based<\/strong><\/td><td><strong>Pull-Based<\/strong><\/td><\/tr><tr><td>Flow<\/td><td>Central server pushes updates<\/td><td>Nodes pull updates<\/td><\/tr><tr><td>Tools<\/td><td>Ansible<\/td><td>Puppet, Chef<\/td><\/tr><tr><td>Control<\/td><td>Centralized<\/td><td>Decentralized<\/td><\/tr><tr><td>Complexity<\/td><td>Simple<\/td><td>Requires agent setup<\/td><\/tr><\/tbody><\/table><figcaption class=\"wp-element-caption\"><strong>Difference between push-based and pull-based deployments<\/strong><\/figcaption><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>20. Can you write a basic Dockerfile?<\/strong><\/h3>\n\n\n\n<p>Yes! A Dockerfile defines how to build a Docker image.<\/p>\n\n\n\n<p><strong>Sample Dockerfile (Node.js app)<\/strong>:<\/p>\n\n\n\n<p><em>Dockerfile<\/em><\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># Base image\n\nFROM node:16-alpine\n\n# Set working directory\n\nWORKDIR \/app\n\n# Copy package files and install dependencies\n\nCOPY package*.json .\/\n\nRUN npm install\n\n# Copy app code\n\nCOPY . .\n\n# Expose port and start app\n\nEXPOSE 3000\n\nCMD &#91;\"npm\", \"start\"]<\/code><\/pre>\n\n\n\n<p><strong>Steps Explained:<\/strong><\/p>\n\n\n\n<ol>\n<li><strong>FROM<\/strong>: Specifies the base image.<\/li>\n\n\n\n<li><strong>WORKDIR<\/strong>: Sets the working directory inside the container.<\/li>\n\n\n\n<li><strong>COPY &amp; RUN<\/strong>: Copies package files and installs dependencies.<\/li>\n\n\n\n<li><strong>COPY. :  Add<\/strong> your source code.<\/li>\n\n\n\n<li><strong>CMD<\/strong>: Command to run when the container starts.<\/li>\n<\/ol>\n\n\n\n<p>This Dockerfile can be used to containerize and run a simple Node.js app.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Advanced Level DevOps Interview Questions and Answers<\/strong><\/h2>\n\n\n\n<figure class=\"wp-block-image size-full\"><img decoding=\"async\" width=\"1200\" height=\"628\" src=\"https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2025\/05\/2087394692.png\" alt=\"Advanced Level DevOps Interview Questions and Answers\" class=\"wp-image-79970\" srcset=\"https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2025\/05\/2087394692.png 1200w, https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2025\/05\/2087394692-300x157.png 300w, https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2025\/05\/2087394692-768x402.png 768w, https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2025\/05\/2087394692-150x79.png 150w\" sizes=\"(max-width: 1200px) 100vw, 1200px\" title=\"\"><\/figure>\n\n\n\n<p>At this level, you&#8217;re expected to think like a DevOps architect or senior engineer. These advanced questions focus on deployment strategies, scaling, disaster recovery, cost optimization, and security best practices.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>21. What\u2019s the difference between CI, CD, and CD?<\/strong><\/h3>\n\n\n\n<p>These three are closely related in DevOps, but they refer to different stages:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><tbody><tr><td><strong>Acronym<\/strong><\/td><td><strong>Full Form<\/strong><\/td><td><strong>Meaning<\/strong><\/td><\/tr><tr><td>CI<\/td><td>Continuous Integration<\/td><td>Developers frequently merge code, triggering automated builds &amp; tests<\/td><\/tr><tr><td>CD<\/td><td>Continuous Delivery<\/td><td>Code is always in a deployable state; release is manual<\/td><\/tr><tr><td>CD<\/td><td>Continuous Deployment<\/td><td>Every code change that passes tests is automatically deployed to production<\/td><\/tr><\/tbody><\/table><figcaption class=\"wp-element-caption\"><strong>Difference between CI, CD, and CD<\/strong><\/figcaption><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>22. How do you handle secrets in a CI\/CD pipeline?<\/strong><\/h3>\n\n\n\n<p>Exposing secrets in your pipeline is a major security risk. Best practice is to manage secrets securely using tools and techniques like:<\/p>\n\n\n\n<p><strong>Best Practices:<\/strong><\/p>\n\n\n\n<ul>\n<li>Store credentials in <strong>Secret Managers<\/strong> (e.g., HashiCorp Vault, AWS Secrets Manager, Azure Key Vault)<\/li>\n\n\n\n<li>Avoid hardcoding passwords or API keys in scripts or config files<\/li>\n\n\n\n<li>Use <strong>environment variables<\/strong> securely injected at runtime<\/li>\n\n\n\n<li>Encrypt secrets at rest and in transit<\/li>\n\n\n\n<li>Audit access to secrets<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>23. How would you scale a microservices-based architecture?<\/strong><\/h3>\n\n\n\n<p>Scaling microservices is both a technical and architectural challenge. Here&#8217;s how you do it:<\/p>\n\n\n\n<p><strong>Scaling Approaches:<\/strong><\/p>\n\n\n\n<ul>\n<li>Use <strong>Kubernetes<\/strong> for container orchestration and auto-scaling<\/li>\n\n\n\n<li>Deploy microservices independently so each scales based on its demand<\/li>\n\n\n\n<li>Implement <strong>Horizontal Pod Autoscaling<\/strong> (HPA) based on CPU, memory, or custom metrics<\/li>\n\n\n\n<li>Use a <strong>service mesh<\/strong> (like Istio) for traffic control and monitoring<\/li>\n\n\n\n<li>Apply <strong>load balancing<\/strong> with ingress controllers<\/li>\n<\/ul>\n\n\n\n<p><strong>Bonus Tip<\/strong>: Use caching (e.g., Redis) and message queues (e.g., RabbitMQ, Kafka) for better scalability.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>24. What is canary deployment, and how is it different from blue-green?<\/strong><\/h3>\n\n\n\n<p><strong>Canary deployment<\/strong> gradually rolls out a new version to a small subset of users to observe system behavior before releasing it to everyone.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><tbody><tr><td><strong>Feature<\/strong><\/td><td><strong>Canary<\/strong><\/td><td><strong>Blue-Green<\/strong><\/td><\/tr><tr><td>Rollout Type<\/td><td>Gradual<\/td><td>All-at-once<\/td><\/tr><tr><td>Rollback<\/td><td>Easy (just stop rollout)<\/td><td>Easy (flip traffic back)<\/td><\/tr><tr><td>Risk<\/td><td>Lower<\/td><td>Medium<\/td><\/tr><tr><td>Use Case<\/td><td>Testing real traffic<\/td><td>Instant environment swap<\/td><\/tr><\/tbody><\/table><figcaption class=\"wp-element-caption\">Canary and Blue-Green<\/figcaption><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>25. How do you ensure zero-downtime deployments?<\/strong><\/h3>\n\n\n\n<p>Zero-downtime deployments mean users aren\u2019t affected during software updates.<\/p>\n\n\n\n<p><strong>Strategies:<\/strong><\/p>\n\n\n\n<ul>\n<li>Use <strong>rolling updates<\/strong> (Kubernetes handles this natively)<\/li>\n\n\n\n<li>Implement <strong>blue-green<\/strong> or <strong>canary<\/strong> deployments<\/li>\n\n\n\n<li>Keep database changes <strong>backward-compatible<\/strong><\/li>\n\n\n\n<li>Use <strong>feature toggles<\/strong> to hide incomplete features<\/li>\n\n\n\n<li>Ensure proper <strong>health checks<\/strong> and <strong>readiness probes<\/strong><\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Bonus: Scenario-Based DevOps Questions and Answers<\/strong><\/h2>\n\n\n\n<p>While theoretical knowledge is important, real-world DevOps roles demand quick thinking and practical problem-solving. Scenario-based questions test your ability to respond to incidents, optimize systems, and make strategic decisions under pressure. Here are some basic questions to get you started:<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>1. Scenario: Deployment Failure in Production<\/strong><\/h3>\n\n\n\n<p><strong>Question:<br><\/strong>Your CI\/CD pipeline just deployed a new version to production, but users are reporting issues, and the app is crashing. How would you handle this situation?<\/p>\n\n\n\n<p><strong>Answer:<\/strong><strong><br><\/strong>First, I would stop further deployments to avoid worsening the issue. Then, I\u2019d check the pipeline logs, container logs (e.g., from Kubernetes or Docker), and monitoring dashboards (like Prometheus\/Grafana) to identify what caused the crash.&nbsp;<\/p>\n\n\n\n<p>If a recent code commit is the cause, I\u2019d initiate a rollback using a previous stable deployment (via Git tag or container version). For zero-downtime rollback, I might use a blue-green or canary rollback strategy. Once stabilized, I\u2019d run a root cause analysis and improve test coverage or health checks to prevent recurrence.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>2. Scenario: High CPU Usage in One Microservice<\/strong><\/h3>\n\n\n\n<p><strong>Question:<\/strong><strong><br><\/strong>You observe unusually high CPU usage in one of the microservices running on Kubernetes. What steps would you take to troubleshoot and resolve this?<\/p>\n\n\n\n<p><strong>Answer:<\/strong><strong><br><\/strong>I\u2019d first confirm the high CPU usage via Kubernetes metrics (e.g., kubectl top pod) and cloud monitoring tools. Then I\u2019d:<\/p>\n\n\n\n<ul>\n<li>Identify the pod(s) affected and check logs for exceptions or memory leaks.<\/li>\n\n\n\n<li>Use resource limits and requests in the pod configuration to control overconsumption.<\/li>\n\n\n\n<li>Investigate recent code or dependency changes in that microservice.<\/li>\n\n\n\n<li>If scaling is appropriate, apply a Horizontal Pod Autoscaler (HPA) to distribute the load.<\/li>\n<\/ul>\n\n\n\n<p>This ensures stability while enabling deeper performance analysis for a long-term fix.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>3. Scenario: You\u2019re Asked to Set Up CI\/CD for a New Project<\/strong><\/h3>\n\n\n\n<p><strong>Question:<\/strong><strong><br><\/strong>You\u2019re starting on a greenfield project and need to set up a CI\/CD pipeline from scratch. What would your approach be?<\/p>\n\n\n\n<p><strong>Answer:<\/strong><strong><br><\/strong> My approach would include:<\/p>\n\n\n\n<ol>\n<li>Version control setup using Git (GitHub\/GitLab).<br><\/li>\n\n\n\n<li>CI\/CD tool selection \u2014 Jenkins, GitHub Actions, or GitLab CI.<br><\/li>\n\n\n\n<li>Define a Jenkinsfile or YAML-based pipeline to:<br>\n<ul>\n<li>Checkout code<\/li>\n\n\n\n<li>Run unit tests<\/li>\n\n\n\n<li>Build artifacts (e.g., Docker image)<\/li>\n\n\n\n<li>Run static code analysis and security scans<\/li>\n\n\n\n<li>Deploy to the dev\/staging environment<br><\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Configure notifications (e.g., Slack, email) for pipeline failures.<br><\/li>\n\n\n\n<li>Integrate approval gates for production deployments.<br><\/li>\n\n\n\n<li>Set up monitoring and rollback strategies post-deployment.<\/li>\n<\/ol>\n\n\n\n<p>This ensures an automated, test-driven, and secure release cycle from day one.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>4. Scenario: Sensitive Data in Codebase Detected<\/strong><\/h3>\n\n\n\n<p><strong>Question:<\/strong><strong><br><\/strong>During a security audit, your team discovers that API keys were accidentally committed to the Git repository. What steps would you take?<\/p>\n\n\n\n<p><strong>Answer:<\/strong><strong><br><\/strong>First, I\u2019d <strong>revoke the exposed API keys<\/strong> to prevent misuse. Then:<\/p>\n\n\n\n<ul>\n<li>Remove the secrets from the Git history using tools like git filter-branch or BFG Repo-Cleaner.<\/li>\n\n\n\n<li>Force-push the cleaned branch and inform all contributors to re-clone the repo.<\/li>\n\n\n\n<li>Introduce .gitignore rules to prevent committing secrets in the future.<\/li>\n\n\n\n<li>Shift to using a secret manager (e.g., HashiCorp Vault, AWS Secrets Manager).<\/li>\n\n\n\n<li>Integrate pre-commit hooks and security scanners like GitLeaks in the CI pipeline.<\/li>\n<\/ul>\n\n\n\n<p>Security hygiene is critical in DevOps\u2014automation helps enforce it consistently.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>5. Scenario: Cost Spike in Cloud Bill<\/strong><\/h3>\n\n\n\n<p><strong>Question:<\/strong><strong><br><\/strong>Your company\u2019s monthly cloud bill has suddenly spiked. As a DevOps engineer, how would you investigate and reduce costs?<\/p>\n\n\n\n<p><strong>Answer:<\/strong><strong><br><\/strong>I\u2019d start by analyzing the cloud billing dashboard to identify which services are responsible for the cost increase. Then:<\/p>\n\n\n\n<ul>\n<li>Check for idle or orphaned resources (unused VMs, volumes, or load balancers).<\/li>\n\n\n\n<li>Audit auto-scaling policies and set limits if over-provisioning is detected.<\/li>\n\n\n\n<li>Identify expensive resources (e.g., large EC2 instances or premium storage) and consider downsizing.<\/li>\n\n\n\n<li>Enable <strong>auto-shutdown<\/strong> schedules for non-prod environments.<\/li>\n\n\n\n<li>Move appropriate workloads to <strong>spot\/preemptible instances<\/strong>.<\/li>\n\n\n\n<li>Implement <strong>budget alerts<\/strong> and cost monitoring tools like AWS Budgets or GCP Cost Management.<\/li>\n<\/ul>\n\n\n\n<p>After cost reduction, I\u2019d prepare a report and establish ongoing monitoring.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>6. Scenario: Frequent Deployment Failures in Staging<\/strong><\/h3>\n\n\n\n<p><strong>Question:<\/strong><br>Your staging environment deployments are failing intermittently, and the team can\u2019t identify the cause. How would you troubleshoot and resolve this?<\/p>\n\n\n\n<p><strong>Answer:<\/strong><br>First, I\u2019d analyze CI\/CD pipeline logs and staging server logs to pinpoint errors. Then:<\/p>\n\n\n\n<ul>\n<li>Check for recent changes in build scripts, dependencies, or configuration files.<\/li>\n\n\n\n<li>Validate that environment variables and secrets are correctly set.<\/li>\n\n\n\n<li>Ensure container images or artifacts are properly built and versioned.<\/li>\n\n\n\n<li>Implement automated integration tests in the pipeline to catch failures early.<\/li>\n\n\n\n<li>Once resolved, add monitoring and alerting for future staging failures to prevent repeated issues.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>7. Scenario: Memory Leak in Production Microservice<\/strong><\/h3>\n\n\n\n<p><strong>Question:<\/strong><br>A microservice in production is consuming increasing memory over time, eventually crashing. How would you handle this?<\/p>\n\n\n\n<p><strong>Answer:<\/strong><br>I\u2019d first confirm the issue using metrics from monitoring tools like Prometheus or cloud dashboards. Then:<\/p>\n\n\n\n<ul>\n<li>Identify the affected pod\/container and review logs for memory-intensive operations.<\/li>\n\n\n\n<li>Use profiling tools to locate memory leaks in the application.<\/li>\n\n\n\n<li>Apply resource limits in Kubernetes to prevent full node crashes.<\/li>\n\n\n\n<li>Roll out fixes with a canary deployment to validate the patch.<\/li>\n\n\n\n<li>Monitor memory usage post-deployment and add automated alerts for abnormal patterns.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>8. Scenario: Rolling Out a New Feature Without Downtime<\/strong><\/h3>\n\n\n\n<p><strong>Question:<\/strong><br>You need to deploy a major feature update to production, but cannot afford downtime. How would you do it?<\/p>\n\n\n\n<p><strong>Answer:<\/strong><br>I\u2019d plan a zero-downtime deployment using strategies like:<\/p>\n\n\n\n<ul>\n<li>Blue-green deployment to switch traffic to a new environment after testing.<\/li>\n\n\n\n<li>Canary releases to gradually expose the feature to a subset of users.<\/li>\n\n\n\n<li>Use feature flags to toggle functionality on\/off without redeploying.<\/li>\n\n\n\n<li>Monitor logs, metrics, and user feedback during rollout.<\/li>\n\n\n\n<li>Have a rollback plan ready in case errors occur during deployment.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>9. Scenario: CI\/CD Pipeline Security Breach<\/strong><\/h3>\n\n\n\n<p><strong>Question:<\/strong><br>During a pipeline audit, you discover that build artifacts are being exposed publicly, risking production credentials. How do you mitigate this?<\/p>\n\n\n\n<p><strong>Answer:<\/strong><br>Immediate steps:<\/p>\n\n\n\n<ul>\n<li>Restrict artifact storage access and update IAM permissions.<\/li>\n\n\n\n<li>Rotate any exposed credentials or API keys.<\/li>\n\n\n\n<li>Integrate secret scanning tools into the pipeline (e.g., GitLeaks, TruffleHog).<\/li>\n\n\n\n<li>Encrypt sensitive files and use secret managers (AWS Secrets Manager, HashiCorp Vault).<\/li>\n\n\n\n<li>Review pipeline configurations for misconfigurations and enforce strict access control for future builds.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>10. Scenario: Slow CI\/CD Pipeline Causing Delays<\/strong><\/h3>\n\n\n\n<p><strong>Question:<\/strong><br>The CI\/CD pipeline is taking hours to complete, slowing down feature delivery. How would you optimize it?<\/p>\n\n\n\n<p><strong>Answer:<\/strong><br>I\u2019d first profile the pipeline to identify bottlenecks. Then:<\/p>\n\n\n\n<ul>\n<li>Parallelize independent jobs like tests and builds.<\/li>\n\n\n\n<li>Cache dependencies to avoid repeated downloads.<\/li>\n\n\n\n<li>Split monolithic pipelines into smaller, faster pipelines per service or module.<\/li>\n\n\n\n<li>Use incremental builds to rebuild only changed components.<\/li>\n\n\n\n<li>Evaluate CI\/CD tooling and infrastructure for performance improvements.<\/li>\n\n\n\n<li>Add monitoring to continuously track pipeline efficiency.<\/li>\n<\/ul>\n\n\n\n<p>If you want to learn more about DevOps and get NSDC certification along with it, then you must sign up for the<a href=\"https:\/\/www.guvi.in\/zen-class\/full-stack-development-course\/?utm_source=blog&amp;utm_medium=hyperlink&amp;utm_campaign=project+ideas+for+frontend+development\"> <\/a><a href=\"https:\/\/www.guvi.in\/zen-class\/devops-course\/?utm_source=blog&amp;utm_medium=hyperlink&amp;utm_campaign=devops-interview-questions-and-answers\" target=\"_blank\" rel=\"noreferrer noopener\"><strong>DevOps Course<\/strong><\/a><span style=\"margin: 0px; padding: 0px;\"> <\/span><strong>with NSDC Certification <\/strong>offered by HCL GUVI<strong>,<\/strong> which gives you in-depth knowledge and hands-on training with top tools like Git, Jenkins, Docker, and Kubernetes under the guidance of an industry expert.&nbsp;<\/p>\n\n\n\n<div style=\"background-color: #099f4e; border: 3px solid #110053; border-radius: 12px; padding: 18px 22px; color: #FFFFFF; font-size: 18px; font-family: Montserrat, Helvetica, sans-serif; line-height: 1.6; box-shadow: 0 4px 12px rgba(0, 0, 0, 0.15); max-width: 750px; margin: 22px auto;\">\n  <h3 style=\"margin-top: 0; font-size: 22px; font-weight: 700; color: #ffffff;\">\ud83d\udca1 Did You Know?<\/h3>\n  <ul style=\"padding-left: 20px; margin: 10px 0;\">\n    <li>Companies using DevOps practices often deploy faster while reducing production failures because testing is built into automated pipelines.<\/li>\n    <li>Interviewers frequently check whether you understand DevOps principles, not just tools, since tools can change but practices remain.<\/li>\n  <\/ul>\n<\/div>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Conclusion<\/strong><\/h2>\n\n\n\n<p>In conclusion, DevOps isn&#8217;t just a buzzword; it&#8217;s a mindset that transforms how teams build, ship, and manage software.&nbsp;<\/p>\n\n\n\n<p>From understanding the fundamentals of CI\/CD to handling advanced challenges like canary deployments, disaster recovery, and cost optimization, being well-prepared for these questions ensures you&#8217;re interview-ready for real-world DevOps roles.&nbsp;<\/p>\n\n\n\n<p>Use these 30 questions as both a self-checklist and a study guide to sharpen your knowledge, refine your approach, and walk into your next interview with confidence. Keep learning, stay hands-on, and embrace the continuous improvement that DevOps stands for.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Are you preparing for a DevOps interview and becoming nervous as you are unsure of what questions to expect? In today\u2019s fast-paced tech world, DevOps professionals are expected to be not only strong in coding and automation but also skilled in system reliability, container orchestration, and CI\/CD practices.&nbsp; Whether you&#8217;re a fresher stepping into your [&hellip;]<\/p>\n","protected":false},"author":65,"featured_media":101617,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[621,719],"tags":[],"views":"5464","authorinfo":{"name":"Jebasta","url":"https:\/\/www.guvi.in\/blog\/author\/jebasta\/"},"thumbnailURL":"https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2025\/05\/35-Important-DevOps-Interview-Questions-and-Answers-300x116.png","jetpack_featured_media_url":"https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2025\/05\/35-Important-DevOps-Interview-Questions-and-Answers.png","_links":{"self":[{"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/posts\/79858"}],"collection":[{"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/users\/65"}],"replies":[{"embeddable":true,"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/comments?post=79858"}],"version-history":[{"count":13,"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/posts\/79858\/revisions"}],"predecessor-version":[{"id":97908,"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/posts\/79858\/revisions\/97908"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/media\/101617"}],"wp:attachment":[{"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/media?parent=79858"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/categories?post=79858"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/tags?post=79858"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}