# DevOps and Cloud Concepts > Chapter 47 of the Courseiva AZ-900 curriculum — https://courseiva.com/learn/az-900/devops-cloud-concepts **Official objective:** 1.5 — Cloud Concepts ## Introduction This chapter introduces DevOps as a cloud-relevant concept — the cultural and practical shift toward developers and operations teams working closely together. AZ-900 tests this under objective 1.5. ## One Team, Not Two Separate Relay Racers Imagine a relay race where the person who builds the baton and the person who runs with it never speak to each other, each blaming the other when something goes wrong. DevOps is like replacing that awkward handoff with a single, coordinated team that builds and runs together — developers (who build software) and operations (who run and maintain it) working closely together throughout, instead of operating as separate, disconnected groups. ## Core explanation ### What DevOps is DevOps is a set of practices and a cultural approach that brings development and operations teams closer together, aiming to deliver software more quickly, reliably, and collaboratively than when those functions operate as separate, disconnected teams. ### Key DevOps practices - **Continuous integration**: regularly merging code changes and automatically testing them, catching issues early. - **Continuous delivery/deployment**: automating the process of getting tested code into production reliably and frequently. - **Infrastructure as code**: managing infrastructure through code and templates (connecting to the ARM/Bicep concepts covered elsewhere) rather than manual configuration. - **Monitoring and feedback**: using monitoring tools (like Azure Monitor) to continuously understand how an application is performing in production, feeding that information back into development. ### Why cloud computing supports DevOps well Cloud platforms provide the automation-friendly infrastructure (APIs, templates, managed services) that DevOps practices rely on — provisioning and managing infrastructure through code and automated pipelines is much more practical in a cloud environment than with traditional, manually configured on-premises infrastructure. ### DevOps is a practice and culture, not a specific tool While various Azure tools support DevOps practices, DevOps itself refers to the broader approach and culture, not any single specific tool or service. ## Real-world context A software team adopts DevOps practices, automatically testing and deploying code changes multiple times a day, with production monitoring data feeding directly back to developers — a much faster, more collaborative cycle than a traditional approach where development and operations worked in separate, disconnected phases. ## Exam focus Objective 1.5 expects a conceptual understanding of DevOps as a practice and cultural approach bringing development and operations together, supported well by cloud infrastructure. A common wrong answer is describing DevOps as a specific tool or single Azure service — it's a broader practice and culture, which various tools can support. Stable terms: **DevOps**, **continuous integration**, **continuous delivery**. Memory trick: DevOps = development + operations, working together continuously, rather than as separate, disconnected phases. ## Step by step 1. **Bring development and operations together** — Rather than operating as separate, disconnected teams, development and operations collaborate closely throughout the software lifecycle. 2. **Automate integration and delivery** — Continuous integration and continuous delivery practices automate testing and deployment, reducing manual effort and the risk of inconsistency. 3. **Manage infrastructure as code** — Infrastructure is defined and managed through code and templates, rather than manual, ad hoc configuration. 4. **Monitor and feed insights back** — Production monitoring data feeds back into the development process, supporting continuous improvement rather than a one-time release-and-forget approach. ## Common misconceptions - **Misconception:** DevOps is a specific tool or Azure service. **Reality:** DevOps is a broader set of practices and a cultural approach, not a single specific tool — various Azure tools can support DevOps practices, but DevOps itself is the approach. - **Misconception:** DevOps only applies to very large organizations. **Reality:** DevOps practices can benefit organizations of any size that want faster, more reliable, more collaborative software delivery, not just large enterprises. ## Key takeaways - DevOps is a set of practices and a cultural approach bringing development and operations teams closer together. - Key practices include continuous integration, continuous delivery, infrastructure as code, and continuous monitoring/feedback. - Cloud platforms support DevOps well, since automation-friendly infrastructure fits naturally with DevOps practices. - DevOps is a broader practice and culture, not a single specific tool or service. ## FAQ **What is DevOps?** It's a set of practices and a cultural approach that brings development and operations teams closer together, aiming to deliver software more quickly, reliably, and collaboratively than when those functions operate separately. **Is DevOps a specific Azure tool?** No — DevOps is a broader practice and cultural approach, not a single tool. Various Azure services can support DevOps practices, but DevOps itself refers to the overall approach, not any one specific service. --- Interactive version with quiz and diagrams: https://courseiva.com/learn/az-900/devops-cloud-concepts