AZ-900 Describe cloud concepts 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.

• ✗

  The ability to automatically replace failed resources without human intervention

  Why it's wrong here

  Automatically replacing failed resources is a self-healing reliability behavior, not a predictability property. In Azure, constructs such as virtual machine scale sets, Azure Service Fabric, and Azure Site Recovery detect node failures and redeploy or repair the workload without human action. That recovery capability belongs to the reliability pillar of the Azure Well-Architected Framework. Predictability, by contrast, is about knowing how the system will perform and what it will cost under normal operation, not about reactive replacement after failure.

• ✓

  Confidence in consistent performance and the ability to forecast costs accurately

  Why this is correct

  Predictability in the cloud means you can depend on consistent performance and can accurately estimate future spending. On Azure, performance predictability is achieved through autoscaling, Azure Load Balancer, and Azure Monitor to maintain steady throughput during changing demand, while cost predictability is supported by tools such as Azure Pricing Calculator, Azure Cost Management + Billing, and budgets/alerts to track and forecast spend. This dual focus on behavior and expense is what the correct answer indicates. It does not refer to a single operational mechanic like deployment parity or data placement.

• ✗

  The guarantee that all data is stored within a specific geographic region

  Why it's wrong here

  Ensuring data is stored in a specific geographic region is a data residency and compliance feature, not a predictability feature. Azure regions and Azure Policy let you restrict data placement to satisfy regulatory frameworks like GDPR or industry-specific requirements. This is about where and how data is held, not about confidence in performance levels or forecasting cloud spending. As such, it does not describe the cloud predictability benefit tested here.

• ✗

  The ability to deploy identical environments for development and production

  Why it's wrong here

  Creating identical dev and production environments is a repeatability and consistency benefit, typically enabled by infrastructure as code tools such as Bicep and ARM templates. This ensures that a workload behaves the same across stages, reducing integration defects, but it says nothing about how predictable the running workload's performance or pricing will be. Predictability is an operational characteristic of the live service, whereas environment parity is a deployment governance practice. Therefore this option is incorrect.

Go deeper

Related to this question