Day-18 | Azure DevOps Scenario Based Interview Questions with Answers #abhishekveeramalla #azure

Episode 18 of the Azure Zero to Hero series covers Azure DevOps interview questions. Topics include: end-to-end CICD pipeline explanation (CI with Azure Pipelines, CD with GitOps), securing sensitive information (Azure Key Vault), integrating Azure Container Registry, debugging pipeline failures, handling code merges/rollbacks, using self-hosted runners, implementing RBAC, automating infrastructure provisioning, and maintaining pipeline security (DevSecOps). Scenario-based questions and answers are provided. This segment details a comprehensive explanation of a CI/CD pipeline, emphasizing its importance in a DevOps role and providing a structured approach to describing the process in an interview setting, including stages like static code analysis, unit testing, building Docker images, scanning, pushing to a container registry, and updating Kubernetes manifests. This segment focuses on securing API keys and secrets within Azure DevOps pipelines. It contrasts insecure practices with secure methods, such as using Azure Key Vault or similar secret management solutions, and discusses the importance of integrating these security measures into the CI/CD process.This segment explains how to integrate Azure Container Registry (ACR) with Azure pipelines for building, pushing, and deploying container images. It details the process of creating stages and jobs within the pipeline, using Docker tasks, and securely storing connection strings using Azure Key Vault or pipeline variables.This segment provides a practical approach to troubleshooting pipeline failures. Using a real-world example of a failed pipeline, the speaker demonstrates how to identify the root cause by examining logs, pinpointing the failing stage, and tracing the issue back to its origin in a previous stage. This showcases a systematic debugging methodology. This segment addresses the critical scenario of handling critical bugs in a production environment. It explains two strategies: reverting to a previous stable version using Git revert and fixing the bug and redeploying. The discussion emphasizes the importance of a well-defined CI/CD pipeline for efficient rollbacks and safe merging of fixes.This segment addresses the use of self-hosted Azure runners for companies with specific infrastructure needs. It explains the reasons for using self-hosted runners and provides a concise overview of how to leverage them within the Azure DevOps environment. This segment details setting up self-hosted runners in Azure DevOps for CI/CD pipelines, addressing limitations of Azure runners in free subscriptions. It explains the process of creating a virtual machine in Azure, adding it as an agent pool in Azure DevOps, and configuring pipelines to utilize the self-hosted agent, providing a practical, step-by-step guide. This segment focuses on managing infrastructure as code (IaC) using CI/CD pipelines. It emphasizes the importance of integrating IaC (using tools like Terraform or ARM templates) into the CI/CD process, mirroring the approach used for application code. The explanation includes storing IaC scripts in a Git repository, creating dedicated pipelines for infrastructure changes, and tracking modifications for better management and collaboration.