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.

• ✗

  Regions determine the maximum number of VMs you can run

  Why it's wrong here

  VM capacity boundaries are governed by subscription quotas and vCPU limits, not by the chosen region itself. While quotas are enforced per region, the maximum number of VMs is set by Azure policy for your subscription and can be increased via a support request. Different VM series have their own quota limits, and you can have separate quota allocations in different regions, but the region does not inherently 'determine' a maximum. Thus, the statement confuses subscription-level quota management with regional infrastructure.

• ✓

  Regions are geographic areas affecting data residency, latency, and disaster recovery

  Why this is correct

  An Azure region is a set of datacenters deployed within a defined geographic boundary, and choosing one has three major implications. Data residency: the region determines where your data is physically stored, which is crucial for compliance and data sovereignty. Latency: locating resources in a region close to your users reduces network latency and improves response times. Disaster recovery: regions are paired with another region (region pair) to provide failover and geo-redundant storage, enabling resilience against regional outages.

• ✗

  Regions only matter for compliance with local laws and have no performance impact

  Why it's wrong here

  Compliance is only one consequence of region selection; latency is directly affected as well. Data and resources hosted in a region far from end users experience higher network round-trip times, which degrades application responsiveness. For real-time workloads, the geographic placement of a region is a primary performance factor, independent of any legal or regulatory requirements. Therefore, the statement that regions have no performance impact is false.

• ✗

  All Azure regions offer identical service availability and performance

  Why it's wrong here

  Azure regions are not uniform in service availability — many services are only offered in specific regions, and even when a service exists, performance can differ due to network distance, local infrastructure, and capacity. Core services like virtual machines are broadly available, but preview or specialized services (e.g., certain AI or compliance-specific offerings) may be absent from many regions. Performance is also influenced by the physical distance between the user and the region, so a region close to users generally yields lower latency. Thus, claiming identical availability and performance is incorrect.