AZ-900 Practice Worksheets & Answer Key

Answer: Adjust rented resource quantities to the campaign’s actual demand

1. The requirement concerns how capacity and spending exposure follow demand, not a promised lower lifetime bill.
2. A consumption model permits changing the resources used rather than purchasing all peak capacity up front.
3. A fixed average quantity does not follow peaks; a fixed maximum quantity retains idle-capacity exposure when demand is lower.

Answer: The resource location properties for X and Y

1. A resource group organizes management and lifecycle; it is not a physical datacenter or zone.
2. Azure Resource Manager documentation explicitly permits resources in a group to be located in different regions.
3. Therefore the stated group membership establishes an administrative relationship, while the geographic and zone claims require additional deployment evidence.

Answer: $14.00

1. Multiply each usage amount by its matching rate: compute is 50 × $0.18 = $9.00; outbound data is 2 × $0.50 = $1.00.
2. The fixed storage charge is $4.00 for the supplied interval; it is not multiplied by the VM-hours.
3. Add the three specified charges once: $9.00 + $4.00 + $1.00 = $14.00.
4. This is only the subtotal of the deliberately complete toy model. Real Azure pricing, billing terms, taxes and omitted services are not inferred from these invented rates.

Answer: Use Microsoft Purview Data Map/Unified Catalog for the data estate

1. The requested object is a data estate and the missing outcome is a data map/unified catalog.
2. Purview directly supplies the data-governance/catalog purpose in this comparison.
3. Roles, posture recommendations and external-server inventory are genuine neighboring governance concerns, but their stated outcomes do not establish a map/catalog of data assets. Connector support and metadata coverage still need verification.

Answer: Put one copy behind an independent dependency that does not fail with F

1. Both running copies share the same stated failure cause, so copy count alone does not satisfy the requirement.
2. Moving one copy to an explicitly independent dependency leaves a running copy outside F’s failure in this simplified model.
3. Memory, more F-dependent copies and recovery copies can serve other purposes, but they do not remove F from both active paths. This is not an Azure SLA claim.

Answer: A container

1. The decisive condition is an application/dependency package rather than a complete guest operating-system image.
2. Containers provide isolated application execution with packaged dependencies; Azure Container Instances is one supported Azure way to run containers.
3. A VM image includes a guest OS, SaaS supplies finished application functionality, and a management template describes resources rather than being the running application package.

Answer: Assign an allowed-locations deny policy at the deployment scope

1. The condition to evaluate is the proposed resource location, not whether the deployer already has an action permission. Authorized deployers must still be able to create compliant resources.
2. Azure Policy can evaluate resource properties against a rule; the official overview gives allowed regions as a governance use case. An appropriately assigned deny policy directly addresses this creation-time location condition.
3. Adding Contributor permission does not impose the location condition. A CanNotDelete lock protects against deletion of existing resources, not the location of a newly created resource.
4. A budget notification reports a cost threshold; it does not by itself reject out-of-list resource locations. This does not claim that every possible Azure Policy effect has the same purpose—only that this specific deny rule matches the requirement.

Answer: Azure App Service with a provider-maintained web platform

1. The school needs to deploy its own application, so a finished SaaS collaboration application does not meet the hosting task.
2. It also requires the provider to maintain the OS and platform runtime. Azure App Service is a PaaS example that supports this managed-platform relationship.
3. A customer-administered Azure VM retains guest-OS work with the school; moving a VM into Azure does not by itself meet the provider-managed-platform condition.
4. An on-premises VM retains even more of the stack with the organization. The decision follows the stated responsibility boundary, not an assumption that one option is always cheaper.