Exam tips & caveats

By this point you know the products. What separates a pass from a near-miss is discrimination — telling two similar controls apart quickly, under time pressure, when the question has been written specifically to make them look interchangeable. Everything below is organised around that.

How to read an SC-500 question

The master decision tree

flowchart TB
  Q["Read the requirement, then ask what it is really about"] --> A{"Is it about applying a control,<br/>or about knowing the state?"}

  A -->|"Applying<br/>a control"| CTRL{"What must the<br/>control govern?"}
  CTRL -->|"Who may act"| RBAC["Azure RBAC, or a<br/>Microsoft Entra role —<br/>PIM if it must be<br/>temporary or approved"]
  CTRL -->|"Its shape"| POL["Azure Policy<br/>Deny to prevent,<br/>DeployIfNotExists<br/>to remediate"]
  CTRL -->|"Reachability"| NET["Firewall rules, private<br/>endpoint, NSG, security<br/>admin rule, access<br/>restrictions"]
  CTRL -->|"Data at rest"| ENC["Encryption — TDE,<br/>customer-managed keys,<br/>Always Encrypted,<br/>disk encryption"]

  A -->|"Knowing<br/>the state"| KNOW{"Configuration,<br/>or live activity?"}
  KNOW -->|"Is the setup safe?"| CSPM["Defender for Cloud<br/>recommendations, secure<br/>score, compliance,<br/>attack paths"]
  KNOW -->|"Is something<br/>happening now?"| DET["A Defender workload<br/>protection plan, or a<br/>Microsoft Sentinel<br/>analytics rule"]

Which Defender feature?

flowchart TB
  Q["A Defender feature is the answer — but which one?"] --> A{"What is being protected<br/>or examined?"}
  A -->|"Configuration risk,<br/>attack paths, secrets,<br/>exposed data"| CSPM["Defender CSPM plan"]
  A -->|"A specific resource<br/>type at runtime"| CWP{"Which resource type?"}
  A -->|"Internet-facing assets<br/>you may not know<br/>you own"| EASM["Defender External Attack<br/>Surface Management"]
  A -->|"Cross-product incidents,<br/>hunting, agents"| XDR["Microsoft Defender XDR,<br/>in the Defender portal"]
  CWP -->|"Windows and<br/>Linux machines"| SRV["Defender for Servers<br/>P1 for EDR, P2 for<br/>agentless, JIT and FIM"]
  CWP -->|"Blobs and files"| STO["Defender for Storage"]
  CWP -->|"SQL, MySQL,<br/>PostgreSQL, Cosmos"| DB["Defender for Databases"]
  CWP -->|"Kubernetes<br/>and registries"| CON["Defender for Containers"]
  CWP -->|"Generative AI<br/>workloads"| AI["Defender for AI Services"]

Numbers worth memorising

Boundaries that are constantly confused

Traps that cost marks

Identity and governance

• Owner does not grant data access. Storage and Key Vault under RBAC need a separate data-plane role.
• There is no deny you can assign in Azure RBAC. To stop an action, use Azure Policy.
• A ReadOnly lock blocks listing storage account keys, because that call is a write.
• A lock never protects data — it is a control-plane control only.
• Locks cannot be applied at a management group.
• Security defaults and Conditional Access are mutually exclusive.
• Number matching in Microsoft Authenticator cannot be turned off.
• Authenticator push is not phishing-resistant. Passkeys, Windows Hello for Business and certificate-based authentication are.
• Application permissions always require admin consent; delegated ones may not.
• DeployIfNotExists needs a managed identity and a remediation task — creating the assignment fixes nothing that already exists.
• Purge protection cannot be turned off, and infrastructure encryption can only be chosen at creation.
• Break-glass accounts must be excluded from Conditional Access and left out of PIM.

Storage, data and network

• A private endpoint without a private DNS zone does nothing — clients still resolve the public address.
• A private endpoint does not disable the public path. Set public network access to Disabled as well.
• Storage firewall rules reject private IP ranges. Use a service endpoint or private endpoint for internal subnets.
• "Allow Azure services and resources to access this server" means any Azure tenant, not just yours.
• Private endpoints are per sub-resource — one for blob does nothing for file.
• Inbound is subnet NSG then NIC NSG; outbound is NIC then subnet. Both must allow.
• Security admin rules exempt several subnets — Application Gateway, Bastion, Azure Firewall, Route Server, VPN Gateway, Virtual WAN and ExpressRoute gateway.
• Only one security admin configuration per region per network manager.
• IDPS, TLS inspection and URL filtering are Azure Firewall Premium only, and are configured in a firewall policy, not on the firewall.
• Database-level SQL firewall rules are evaluated before server-level ones, and can only be created with T-SQL.
• NSG flow logs are retired on 30 September 2027; use virtual network flow logs.

Compute and applications

• Integrity monitoring requires vTPM, which requires trusted launch.
• Bastion SKUs upgrade but never downgrade. Session recording and private-only deployment are Premium only.
• JIT is Defender for Servers Plan 2, and it edits NSG and firewall rules rather than removing public IPs.
• Agentless malware scanning is Plan 2 only, even though other agentless capabilities come with Defender CSPM.
• File integrity monitoring is not on by default even in Plan 2.
• AKS local accounts bypass Microsoft Entra entirely. Disable them.
• The ACR admin user is a shared password. Disable it and use AcrPull.
• Function keys are not authentication, and the master key is administrative.
• Access restrictions must also be applied to the scm site, or the deployment endpoint stays open.
• WAF: tune with exclusions, not by disabling rules, and start in Detection mode.
• An APIM subscription key identifies a subscription, not a user.

Posture, monitoring and AI

• The compliance dashboard needs a paid plan; MCSB recommendations alone come free.
• Filter with a data collection rule at the agent — filtering in a query after ingestion has already cost you.
• CEF lands in CommonSecurityLog, with non-standard fields in AdditionalExtensions.
• Playbooks need their own managed identity and role assignments, and Sentinel needs Automation Contributor on their resource group.
• Security Copilot never exceeds the signed-in user's permissions. Fix the service role, not the Copilot role.
• An agent's guardrail overrides the model's, and Microsoft Default guardrails cannot be edited.
• Conditional Access for agents targets users for on-behalf-of flows and agent identities for app-only flows.
• 429 is the rate limit; 403 is the quota.
• Copilot Studio real-time protection covers generative orchestration agents only — classic agents are skipped.
• The Data and AI security dashboard stays empty without Defender CSPM with sensitive data discovery, Defender for Storage, Defender for Databases and AI threat protection.

Scenario-to-answer lookup

A final-two-weeks plan

On the day

• Case studies first or last, but decide beforehand. They carry several questions on one scenario; reading the exhibit twice costs less than switching context twice.
• Mark and move. 120 minutes is comfortable if you do not stall. Flag anything that takes more than ninety seconds and come back.
• Answer every question. There is no negative marking.
• On yes/no statement sets, evaluate each statement independently. They are deliberately written so that two look identical and one word differs.
• Watch for "least privilege", "minimal administrative effort" and "without affecting users". Those three phrases pick the answer more often than any technical detail.
• Trust the current name. If an option uses a name you only know from an old blog post, it is more likely to be the distractor.