Domain 1: Describe Cloud Concepts
Sample objective from the AZ-900 study guide MS Exam Prep generates — sourced exclusively from Microsoft Docs.
The Shared Responsibility Model
In Azure, security and compliance responsibilities are divided between Microsoft and the customer. The split depends on the service type (IaaS, PaaS, or SaaS) — understanding this model is a core AZ-900 exam objective.
Microsoft is always responsible for:
- Physical datacentre security and hardware
- Network infrastructure and host hypervisor
- Physical hosts and the physical network
The customer is always responsible for:
- Data stored in the cloud
- Identity and access management (who has access to what)
- Devices connecting to the cloud (endpoints)
- Accounts and identities of internal users
Responsibility shifts by service model: With IaaS you manage the OS, middleware, and applications. With PaaS, Microsoft manages the underlying platform — you manage your data and applications. With SaaS, Microsoft manages almost everything.
The exam often tests the boundary between Microsoft and customer responsibility in a given scenario. Remember: Microsoft always owns the physical infrastructure; the customer always owns their data and identities. The OS and application layers shift depending on the service model.
Cloud Deployment Models
Azure supports three deployment models, each suited to different organisational needs:
Public cloud: Resources are owned and operated by a third-party provider (Microsoft) and delivered over the internet. You share infrastructure with other organisations but have logical isolation. No upfront capital expenditure required.
Private cloud: Cloud resources used exclusively by one organisation. Can be hosted on-premises or by a third party. Gives maximum control and customisation, but carries the full cost and responsibility of maintaining hardware.
Hybrid cloud: Combines public and private cloud. Allows data and apps to be shared between them. Useful for regulatory requirements, gradual migration, or burst scenarios (extending capacity to the public cloud when on-premises resources are exhausted).
Questions about deployment models often describe a scenario — look for the key constraint. Regulatory or data-sovereignty requirement? → Private or hybrid. Cost sensitivity, no existing hardware? → Public. Keep some workloads on-premises but extend to the cloud? → Hybrid.
CapEx vs OpEx: The Consumption-Based Model
Traditional on-premises IT uses Capital Expenditure (CapEx) — large upfront purchases for servers and infrastructure. Azure uses an Operational Expenditure (OpEx) model.
The consumption-based model means:
- No upfront cost for infrastructure
- You pay only for what you use
- Resources can be provisioned quickly and deprovisioned when no longer needed
- Predictable billing based on actual consumption
AZ-900 frequently asks why cloud computing is described as OpEx. The key phrase is "no upfront cost" and "pay for what you use." Contrast this with CapEx where you purchase and maintain your own hardware — even if utilisation is low.
AZ-900 Practice MCQ
5 questions from the Cloud Concepts domain. Click an answer to check. Your full course includes 2–3 questions per objective.
AZ-900 Flashcards
Click a card to reveal the answer. Use the arrows to move between cards.
Ready for your full AZ-900 course?
Sign in free to generate your complete personalised course — study guide, 60+ practice questions, flashcard deck, and slide deck. All from Microsoft Docs.