Question 290 A service must tolerate loss of a datacenter site within one supported Azure region. Which construct helps? Resource tags A single large virtual machine A shared resource group name Availability zones Explanation Correct Answer D:Zones are physically separated locations within supported regions. Incorrect Answers A:Metadata does not provide datacenter separation. B:One VM is still one runtime failure point. C:Grouping does not force physical redundancy.
Question 291 An architect says an availability zone is another global region. Which correction is accurate? Zones are names for management groups Zones are Azure billing accounts Zones mean every resource is replicated worldwide Zones are isolated locations within one supported Azure region Explanation Correct Answer D:Zones offer local fault-domain separation rather than a separate region geography. Incorrect Answers A:Management groups organize subscriptions, not datacenters. B:Billing boundaries are managed through subscriptions. C:Zone redundancy is not globally replicated by default.
Question 292 An engineer cannot select a desired zone for a specific resource SKU. What should be checked? Only the resource group's naming convention A billing tag stating highly available Zone and SKU support in that region Only the operator's Entra display name Explanation Correct Answer C:Availability zones and zonal deployments vary across products and regions. Incorrect Answers A:Names do not make unsupported zone features available. B:Metadata cannot create unavailable physical placement. D:Identity names do not establish zone support.
Question 293 A web workload uses several zone-capable instances but all are placed in a single zone. What change addresses a whole-zone outage? Distribute compatible instances and dependencies across zones Give the instances unique tags within the same zone Place all data backups on the same failed VM Increase only the memory of the current zone's VMs Explanation Correct Answer A:Spreading failure domains reduces reliance on one zone. Incorrect Answers B:Tags do not change their shared outage risk. C:Local backups do not create separate capacity. D:Larger machines remain exposed to the same zone outage.
Question 294 A VM workload needs protection from host and update-domain failures within a datacenter rather than site-level isolation. Which older VM placement feature may be relevant? Resource group tags Azure availability zones exclusively Availability sets Management group policy names Explanation Correct Answer C:Availability sets distribute supported VMs across fault and update domains within a datacenter context. Incorrect Answers A:Tags do not enforce VM fault domains. B:Zones address datacenter-level separation, a different failure boundary. D:Management groups are organizational scopes, not a VM placement mechanism.
Question 295 A legacy VM availability set is deployed within a region. What should an architect NOT claim solely from that design? It concerns how supported VMs are placed and maintained It can use fault and update domain separation for eligible VMs It is a regional VM availability construct rather than a billing container It guarantees survival of an entire region outage Explanation Correct Answer D:Availability sets do not create a second-region deployment. Incorrect Answers A:Placement is part of the feature. B:That is the purpose of availability sets. C:Billing is separate from availability sets.
Question 296 What is an Azure datacenter in a cloud architecture discussion? A resource tag used for cost allocation A JSON deployment template A physical facility that houses computing, storage and networking infrastructure A billing subscription record Explanation Correct Answer C:Datacenters contain the physical equipment that supports hosted Azure services. Incorrect Answers A:Metadata labels do not contain physical servers. B:Templates describe resources but are not physical facilities. D:Subscriptions organize resource consumption, not physical racks.
Question 297 A tenant asks who normally controls badges and entry screening at an Azure datacenter. Which party owns that physical operation? Every tenant's VM guest administrator The customer's application developers All users assigned Azure Reader Microsoft as the cloud provider Explanation Correct Answer D:The provider protects access to its physical facilities. Incorrect Answers A:Guest OS rights do not grant facility operation. B:Developers manage custom code, not datacenter entrances. C:Read access to resources is not physical building security.
Question 298 A team is confused by the terms region and datacenter. Which statement is correct? A region is a geographic deployment area that can contain multiple datacenters Every virtual network is a physical datacenter A management group is a physical power domain Each resource group is a datacenter building Explanation Correct Answer A:Regions describe a broader placement scope than an individual facility. Incorrect Answers B:A virtual network is a logical network abstraction. C:Management groups organize subscriptions administratively. D:Resource groups are logical management containers.
Question 299 A platform administrator creates an Azure storage account. What is it in the Azure management hierarchy? An Azure resource An Azure region pair A tenant-wide identity directory A management group Explanation Correct Answer A:A deployed service instance such as a storage account is a resource. Incorrect Answers B:A storage account is not a geographic region relationship. C:The storage account is a service resource, not Microsoft Entra ID. D:A management group contains subscription governance scope, not the account itself.
Question 300 An engineering team wants to organize a web app, database and associated network components that share an application lifecycle. Which container should it evaluate? A datacenter building A region pair An Azure role assignment by itself An Azure resource group Explanation Correct Answer D:Resource groups logically organize related resources for management and deployment. Incorrect Answers A:Tenants don't group their resources by owning provider facilities. B:Region pairing is geographic, not an application resource container. C:RBAC grants permissions but does not organize resource objects into a lifecycle container.
