Zero Trust, Defense in Depth & Defender for Cloud
AZ-900 AZ-900 · Describe Azure architecture and services
Zero Trust: never trust, always verify
The traditional security model trusted everything inside the corporate network — once you were through the firewall, you were trusted. That model breaks in the cloud, where users work from anywhere and applications live on the internet. Zero Trust replaces it with a simple rule: never trust by default, always verify. Every access request is authenticated, authorised, and encrypted, regardless of where it comes from — inside or outside the network. Location grants no trust; identity, device health, and risk do.
Microsoft describes Zero Trust through three principles, and the exam tests all three:
- Verify explicitly: always authenticate and authorise based on all available signals — user identity, location, device health, the service being accessed, and unusual behaviour. A sign-in from a new country on an unknown device gets more scrutiny than a routine one.
- Use least privilege access: give each user and application only the access it needs to do its job, and only for as long as it needs it. Just-in-time and just-enough access limit what an attacker can do with a compromised account.
- Assume breach: design as if an attacker is already inside. Segment the network so a breach in one area cannot spread, encrypt data everywhere, and monitor continuously so intrusions are detected quickly.
Zero Trust is a strategy, not a product — no single service "is" Zero Trust. Entra ID (identity verification), Conditional Access (risk-based decisions), MFA (strong authentication), RBAC (least privilege), and Defender for Cloud (threat detection) are the Azure tools that implement it. If a question describes verifying every request regardless of network location, the answer is Zero Trust.
Defense in depth: layers, not a single wall
Defense in depth is the strategy of protecting a system with multiple layers of security, so that if one layer fails, the next one still stands. A single firewall can be bypassed; seven layers rarely are. The exam expects you to describe the layers, from the outside in:
| Layer | What it protects | Example controls |
|---|---|---|
| Physical security | The datacenter building | Guards, locks, cameras, biometric access |
| Identity and access | Who can get in | Entra ID, MFA, Conditional Access, RBAC |
| Perimeter | The network edge | DDoS protection, firewalls |
| Network | Traffic between resources | Network security groups, private endpoints, segmentation |
| Compute | Servers and virtual machines | Endpoint protection, patching, disk encryption |
| Application | The software itself | Secure code, application firewalls, secrets management |
| Data | The information | Encryption at rest and in transit, access controls |
The layers work together: an attacker who gets past the perimeter firewall still faces network segmentation; one who reaches a VM still faces identity checks and encryption; one who reaches the data still faces encryption. The exam tests defense in depth with scenarios about "multiple layers" or with questions asking which layer a control belongs to — MFA belongs to identity and access, network security groups to the network layer, encryption to the data layer.
Microsoft Defender for Cloud
Microsoft Defender for Cloud is Azure's cloud security posture management and threat-protection service. It does two jobs. First, it assesses the security of your Azure (and connected on-premises and multi-cloud) resources and gives you a secure score — a percentage showing how closely your configuration matches security best practices — plus prioritised recommendations for improving it (enable MFA, encrypt disks, close open management ports). Second, it detects threats: it monitors for suspicious activity, such as a virtual machine communicating with a known malicious address, and raises security alerts with recommended actions.
Defender for Cloud has a free tier (secure score, recommendations, and the asset inventory) and paid Defender plans per resource type (servers, storage, databases, and more) that add threat detection. The exam does not test pricing tiers; it tests purpose: Defender for Cloud tells you how secure your environment is and warns you about threats. Do not confuse it with Microsoft Sentinel (a SIEM for collecting and analysing security events across an organisation — not in the AZ-900 objectives) or with Microsoft Defender for Endpoint (protection for individual devices). For AZ-900, Defender for Cloud is the cloud security posture and alerting service.
Worked example: one attack, three concepts
An attacker phishes an employee's password. Under Zero Trust, the password alone is not enough: Conditional Access sees a sign-in from an unusual location on an unknown device and requires MFA, which the attacker cannot complete. Suppose the attacker somehow gets in anyway. Defense in depth limits the damage: network segmentation keeps them away from the database subnet, RBAC least privilege means the stolen account can read only one application, and encryption means any data they reach is unreadable without keys. Meanwhile Defender for Cloud detects the anomalous sign-in pattern and raises an alert, and the security team disables the account. Three exam concepts — Zero Trust, defense in depth, Defender for Cloud — describe three lines of the same defence.
How the security topics connect
The identity guide and this guide are two halves of one domain area. Identity (Entra ID, MFA, Conditional Access, RBAC) answers "who are you and what can you do?"; this guide answers "what is the strategy, and how do we know we are secure?" In the exam, a question about verifying every request is Zero Trust; a question about layered protection is defense in depth; a question about a secure score or security recommendations is Defender for Cloud; and a question about who can do what is RBAC. Keep those four triggers straight and the security questions answer themselves.
The exam's security checklist
Before the exam, check you can answer these five questions without hesitation. What are the three Zero Trust principles, and what does each one mean in practice? Which defense-in-depth layer does each of these belong to: MFA, a network security group, disk encryption, a firewall, a security guard? What does Defender for Cloud give you — a secure score and recommendations — and what does it detect? What is the difference between Owner and Contributor, and why does least privilege matter? And what does Conditional Access use as signals — user, device, location, risk — and what controls can it enforce? If you can answer all five in your own words, the security portion of the exam is covered. The most common mistake is treating these as separate facts to memorise; they are one story — identity proves who you are, Zero Trust decides whether to believe it, defense in depth limits the damage if the answer is wrong, and Defender for Cloud watches the whole thing and tells you what to fix.
Exam traps to watch for
- Calling Zero Trust a product. Zero Trust is a security strategy (verify explicitly, least privilege, assume breach), implemented with Entra ID, Conditional Access, MFA, RBAC, and Defender for Cloud.
- Confusing Defender for Cloud with Sentinel. Defender for Cloud assesses cloud security posture and raises threat alerts; Sentinel is a SIEM and is not in the AZ-900 objectives.
- Putting a control in the wrong defense-in-depth layer. MFA is identity and access; network security groups are the network layer; encryption is the data layer.
- Thinking one strong layer is enough. Defense in depth exists precisely because any single layer can fail — the point is that the next layer still stands.
Practice questions
Test yourself on this guide. Answers are checked instantly, with a full explanation for each question.
Q1.A company adopts a security model in which every access request is verified based on identity, device, and location — whether the user is in the office or working remotely. No request is trusted just because it comes from inside the network. Which model is this?
Explanation: Zero Trust assumes no implicit trust: every request is verified explicitly based on signals such as identity, device, and location. Defense in depth is layered protection, not a trust model. Perimeter security is the old model of trusting everything inside the network — the opposite of this. RBAC controls what users can do to resources; it is one tool within a Zero Trust strategy, not the strategy itself.
Exam objective: AZ-900 Describe Azure identity, access, and security: describe the concept of Zero Trust
Q2.Which of the following is one of the three principles of Zero Trust?
Explanation: Assume breach — design as if an attacker is already inside, segmenting and monitoring accordingly — is one of the three Zero Trust principles (with verify explicitly and least privilege access). Trusting internal traffic is the old perimeter model Zero Trust replaces. Administrator access by default violates least privilege. Protecting only the perimeter is the opposite of the Zero Trust approach.
Exam objective: AZ-900 Describe Azure identity, access, and security: describe the concept of Zero Trust
Q3.A company protects its systems with a firewall at the network edge, network segmentation, endpoint protection on servers, and encryption of its data, so that if one control fails, the others still protect the system. Which strategy is the company using?
Explanation: Defense in depth is protection through multiple layers, so a failure in one layer does not compromise the system. Zero Trust is the verify-everything trust model, not the layering strategy. Single sign-on is an authentication convenience. Least privilege is about minimal access rights — one principle within Zero Trust, not the layered strategy.
Exam objective: AZ-900 Describe Azure identity, access, and security: describe the purpose of the defense-in-depth model
Q4.In the defense-in-depth model, which layer does multifactor authentication (MFA) belong to?
Explanation: MFA verifies who a user is, so it belongs to the identity and access layer. Physical security is the datacenter building. The perimeter is the network edge (firewalls, DDoS protection). The network layer covers traffic between resources (network security groups, segmentation).
Exam objective: AZ-900 Describe Azure identity, access, and security: describe the purpose of the defense-in-depth model
Q5.A security team wants a single view of how securely its Azure resources are configured, with a score and a prioritised list of improvements. Which service provides this?
Explanation: Defender for Cloud assesses security posture, gives a secure score, and provides prioritised recommendations. Azure Monitor collects metrics and logs for performance and operations, not a security score. Service Health reports the health of Azure services themselves. Entra ID manages identities and access, not security posture scoring.
Exam objective: AZ-900 Describe Azure identity, access, and security: describe the purpose of Microsoft Defender for Cloud
Q6.Defender for Cloud raises an alert that a virtual machine is communicating with a known malicious IP address. Which Defender for Cloud capability produced this alert?
Explanation: Threat detection monitors for suspicious activity — such as traffic to a known malicious address — and raises security alerts. The secure score measures configuration against best practices; it does not detect live threats. The compliance dashboard tracks regulatory compliance. Cost analysis belongs to Cost Management, not Defender for Cloud.
Exam objective: AZ-900 Describe Azure identity, access, and security: describe the purpose of Microsoft Defender for Cloud
Q7.According to the Zero Trust principle of least privilege, what access should a user receive?
Explanation: Least privilege means the minimum access needed to do the job, for the minimum time needed (just-in-time, just-enough access). Administrator access to everything is the opposite. Identical access for everyone ignores different job needs. No access until a daily request is not least privilege — it is no access at all.
Exam objective: AZ-900 Describe Azure identity, access, and security: describe the concept of Zero Trust
Q8.A company encrypts its databases and storage so that data is unreadable without the keys, even if an attacker gains access to the underlying files. Which defense-in-depth layer is this control part of?
Explanation: Encryption protects the data itself, so it belongs to the data layer — the innermost layer of defense in depth. The perimeter is the network edge. The compute layer covers servers and VMs (endpoint protection, patching). Physical security is the datacenter building.
Exam objective: AZ-900 Describe Azure identity, access, and security: describe the purpose of the defense-in-depth model