Azure Fundamentals (AZ-900) Study Guide (Jack Lee) (z-library.sk, 1lib.sk, z-lib.sk)

# Azure Fundamentals (AZ-900) Study Guide — Reading Guide ## 【One-Line Pitch】 A practical, exam-focused walkthrough of Microsoft Azure's foundational concepts—cloud models, core services, architecture, and management tools—designed for absolute beginners and career-switchers preparing for the AZ-900 certification. If you want to pass the exam *and* actually understand what you're deploying, this guide bridges both goals with clear analogies and real-world examples. --- ## 【Book Arc】 - **Opening (~0%–10%)**: Introduces cloud computing fundamentals—what it is, why it matters, and the core benefits (high availability, scalability, cost efficiency). Establishes the shared responsibility model and the three primary service types (IaaS, PaaS, SaaS) that anchor the entire exam. - **Early (~10%–23%)**: Dives into cloud deployment models—public, private, hybrid, and multi-cloud—with practical guidance on when each makes sense. Also demystifies Azure accounts, subscriptions, and management groups, giving you the administrative scaffolding needed before touching any service. - **Early (~23%–32%)**: Explores Azure's physical architecture—regions, availability zones, and sovereign clouds (government and China regions)—explaining why geographic redundancy matters for compliance, performance, and disaster recovery. - **Middle (~32%–48%)**: Walks through core Azure compute services (VMs, containers, Azure Functions, App Services) and storage options (Blob, Files, Queue, Table), comparing trade-offs between IaaS control and PaaS convenience. Includes practical guidance on choosing the right service for specific workloads. - **Late (~48%–end)**: Covers networking and integration services—Azure DNS, Traffic Manager, API Management, Logic Apps—mapped to the OSI model. The book closes with a high-level recap and a full practice exam in the appendix to test your readiness. --- ## 【Key Takeaways】 - **Cloud service types form a responsibility spectrum** (Early): As you move from IaaS to PaaS to SaaS, the customer's management burden decreases while the provider's increases. This single rule of thumb answers dozens of AZ-900 questions—memorize the boundary shifts for each model. - **High availability is engineered, not guaranteed** (Early): Azure provides redundant infrastructure and SLAs, but achieving end-to-end reliability requires your architectural choices. The book stresses that customers own the design responsibility for meeting their own service-level objectives. - **Cloud models solve different business problems** (Early): Public cloud offers scale and speed; private cloud provides control and compliance; hybrid balances both; multi-cloud avoids vendor lock-in. Each has distinct trade-offs around cost, security, and operational complexity. - **Azure's hierarchy is onion-like and purposeful** (Early): Management groups → subscriptions → resource groups → resources form a nested structure (up to six levels deep) that enables organized cost tracking, policy application, and access control at scale. - **Regions and availability zones are not the same thing** (Early): Regions are geographic areas with multiple datacenters; availability zones are physically isolated facilities *within* a region. Understanding this distinction is critical for designing fault-tolerant architectures. - **Serverless doesn't mean no servers—it means no server management** (Middle): Azure Functions runs code in response to events, auto-scales, and bills only for execution time. The "on-demand plumber" analogy clarifies when serverless shines versus when you need persistent infrastructure. - **Container services exist on a management spectrum** (Middle): Azure Container Instances offers quick, cost-effective deployment for simple workloads, while Azure Kubernetes Service provides advanced orchestration—choose based on your need for scalability and control. - **Networking services map to the OSI model** (Late): Azure DNS handles name resolution at Layer 7, Traffic Manager routes traffic globally based on health and performance rules, and API Management acts as a secure gateway for exposing services—each solves a distinct connectivity problem. --- ## 【Reading Tips】 - **Skim the exam tips but don't skip them**: The book flags high-yield exam facts (like the responsibility shift across service types) in dedicated callouts. These are your fastest path to passing—read them twice. - **Deep-read Chapters 3–5 and 7**: The shared responsibility model, cloud deployment types, and Azure's regional architecture are the conceptual core of AZ-900. Understanding these deeply makes the rest of the book feel like applied examples rather than disconnected facts. - **Use the tables as cheat sheets**: Storage types, OSI model mappings, and service comparisons are presented in tabular form. Recreate these tables from memory as a self-test before moving to the practice exam. - **Skip ahead if you already know cloud basics**: The author explicitly notes that readers familiar with cloud models can jump to Part II (Azure Architecture and Services). Don't waste time on concepts you've mastered elsewhere. - **Take the practice exam in Appendix A seriously**: It's designed to mirror the real AZ-900 format. Time yourself, review every wrong answer against the answer key in Appendix B, and revisit the corresponding chapters before retaking. --- ## 【Coverage Limits】 This guide is based on a stratified sample of the book's content (roughly the first half through networking services). The excerpts do not cover the final chapters on security, identity, governance, or cost management in detail, nor the complete practice exam—though the book's structure indicates these are addressed in Parts III–VI and the appendices. --- ##