AZ-900 Describe Azure management and governance Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Achieving maximum performance for Azure workloads

  Why it's wrong here

  Achieving maximum performance for Azure workloads is an operational and architectural goal focused on throughput, latency, and scalability, typically measured via Azure Monitor and Application Insights. Compliance, by contrast, is a regulatory and audit requirement independent of speed or efficiency; a workload can be extremely fast while still failing data-handling mandates such as GDPR data minimization or residency rules. Maximizing performance may even trade against compliance controls, such as disabling encryption or logging to reduce overhead, so it is not the definition of compliance.

• ✓

  Meeting regulatory standards, laws, and organizational policies for data and security

  Why this is correct

  In Azure, compliance is the state of adhering to binding regulatory standards, statutory laws, and internal organizational policies that govern data handling, access, and security. Azure provides certifications and attestations such as GDPR, HIPAA, ISO/IEC 27001, and FedRAMP, with services like Azure Policy and Microsoft Purview to enforce and evidence that adherence. This broad definition covers both legal obligations and enterprise governance criteria, which is why it precisely matches the meaning of compliance.

• ✗

  Ensuring all Azure resources are running without errors

  Why it's wrong here

  Ensuring all Azure resources are running without errors describes operational health monitoring and availability management, using tools like Azure Monitor and Service Health to detect faults and maintain uptime. Compliance is a distinct discipline centered on meeting external legal and regulatory standards; a resource might be healthy and error-free yet non-compliant because it stores sensitive data in an unapproved region or lacks required audit logs. Conversely, a compliant environment can still experience transient errors, so this option confuses operational reliability with regulatory adherence.

• ✗

  Using only Microsoft-approved Azure services in your environment

  Why it's wrong here

  Using only Microsoft-approved Azure services in your environment is about restricting service adoption, but compliance is not a matter of service selection or vendor endorsement. Regulatory frameworks like ISO 27001 or HIPAA do not certify individual Azure services; rather, compliance depends on how any service is configured, what data it processes, and where that data resides. Microsoft offers many compliant services, but choosing only 'approved' ones does not automatically satisfy regulations, and non-Microsoft or third-party tools can be part of a compliant architecture if properly governed.

Go deeper

Related to this question