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.

• ✗

  Reducing unnecessary resource provisioning to minimize costs

  Why it's wrong here

  Reducing unnecessary resource provisioning is a hallmark of the Cost Optimization pillar, which drives right-sizing, scaling down idle resources, and eliminating waste to lower Azure spend. In contrast, the Reliability pillar focuses on designing systems to withstand failures, incorporate redundancy, and meet availability targets; cutting provisioning too aggressively can actually undermine recovery capabilities. Thus, this choice misattributes a cost-focused activity to a resilience-focused pillar.

• ✓

  Ensuring workloads recover from failures and meet availability requirements

  Why this is correct

  This option precisely defines the Reliability pillar of the Azure Well-Architected Framework, which emphasizes building workloads that can recover from component, regional, or application failures and continue to operate within agreed availability SLAs. Implementing reliability requires redundancy across availability zones/regions, automated failover, robust backup and restore processes, and capacity planning to absorb spikes. By directly addressing failure recovery and availability requirements, it captures the core objective of the Reliability pillar.

• ✗

  Encrypting all data and managing access identities

  Why it's wrong here

  Encrypting data and managing identities are fundamental responsibilities of the Security pillar, which safeguards confidentiality, integrity, and access control. The Reliability pillar, by contrast, is concerned with availability and resilience—ensuring workloads are always accessible and recover quickly from disruptions. Though a secure design can indirectly support reliability, these are distinct architectural concerns, so this option conflates security with reliability.

• ✗

  Monitoring resource performance and responding to performance alerts

  Why it's wrong here

  Monitoring performance and responding to alerts is a cross-cutting operational practice that primarily maps to the Operational Excellence pillar (for continuous improvement and incident response) and the Performance Efficiency pillar (for scaling and tuning to meet demand). In the Reliability pillar, the focus is narrow: ensuring systems stay available and recover from failures rather than optimizing performance metrics like CPU or latency. While alerting can support reliability by detecting outages, it is not the defining action of that pillar.