AZ-900 Practice Exam — AZ-900: Azure Fundamentals

" target="_blank" rel="nofollow noopener">https://img.examtopics.com/az-900/image617.png">

The question outlines three mandatory storage requirements: data stored on multiple nodes, data stored in separate geographic locations, and read access to both primary and secondary storage locations. The suggested answer B, Read-only geo-redundant storage (RA-GRS), satisfies all three requirements and aligns with AZ-900 core objectives for Azure storage resiliency and disaster recovery. First, all Azure storage redundancy options including RA-GRS store data across multiple redundant nodes to protect against local hardware failures, meeting the first requirement. Second, RA-GRS asynchronously replicates data to a secondary Azure region that is geographically separated from the primary region by hundreds of miles, satisfying the separate geographic location requirement for site resiliency between the Los Angeles and New York datacenters. Third, RA-GRS provides a dedicated read-only endpoint for the secondary region, allowing users to read data from the secondary location at any time without waiting for a failover event, which meets the final access requirement. Option Analysis: A. Geo-redundant storage: This option meets the first two requirements, as it stores data on multiple nodes and replicates to a geographically separate secondary region. However, it does not allow regular read access to the secondary region; the secondary is only accessible if Microsoft triggers a regional failover due to a primary region outage. This fails the requirement to read data from the secondary location alongside the primary, so this option is incorrect. B. Read-only geo-redundant storage: This option meets all three stated requirements. It stores data across multiple redundant nodes in both primary and secondary regions, replicates data to a geographically isolated secondary Azure region, and provides permanent read-only access to the secondary region endpoint alongside full read-write access to the primary region. This matches the site resiliency and access needs of the scenario, so this option is correct. C. Zone-redundant storage: This option replicates data across three availability zones within a single Azure region. While it stores data on multiple nodes, it does not replicate data to separate geographic locations, as all availability zones reside in the same regional geography. This fails the separate geographic location requirement, so this option is incorrect. D. Locally redundant storage: This option replicates data three times within a single datacenter in the primary region. It does not use separate geographic locations for replication, and has no secondary region to read from, so it fails both the separate geographic location and secondary read access requirements. This option is incorrect. Key Concepts: 1. Azure Storage Redundancy Tiers: AZ-900 requires candidates to understand the four core Azure storage redundancy options (LRS, ZRS, GRS, RA-GRS) and their respective resiliency scopes, ranging from single datacenter to cross-region, to appropriately match use cases for availability and disaster recovery. 2. Geo-Redundant Storage Access Models: A core differentiator between GRS and RA-GRS tested in AZ-900 is secondary region access permissions: GRS restricts secondary access to official failover events only, while RA-GRS provides always-available read access to the secondary region, making it suitable for use cases that require low-latency reads from multiple geographies or continuous access during primary region outages. 3. Resiliency Scope Classification: LRS and ZRS are single-region redundancy options designed to protect against local and availability zone failures within one region, while GRS and RA-GRS are cross-region redundancy options designed for site resiliency against entire regional outages, a key classification for AZ-900 disaster recovery objectives. References: Azure Storage redundancy, https://learn.microsoft.com/en-us/azure/storage/common/storage-redundancy Microsoft Azure Fundamentals (AZ-900) Study Guide, https://learn.microsoft.com/en-us/certifications/resources/study-guides/az-900#describe-azure-storage-services

The scenario requires selecting the lowest-cost Azure support plan that enables Microsoft-led assessments of an Azure environment's design, moving from the existing Basic support plan. Core AZ-900 knowledge covers the specific benefits included in each Azure public support tier. The proposed solution recommends the Professional Direct support plan, but this tier does not include formal design assessments of Azure environments as an included benefit. Professional Direct offers enhanced break-fix support, faster response times for critical issues, and access to senior technical resources for reactive support, but the required proactive design assessment service is exclusively available in the Premier support tier. As a result, the proposed solution fails to meet the stated goal, so the correct answer is No. Option Analysis: A. Yes is incorrect. The Professional Direct support tier does not include the ability to request Microsoft-led Azure environment design assessments. While this tier offers higher priority operational support and access to senior Azure technical resources for break-fix scenarios, it lacks the proactive design assessment capability required in the scenario, so recommending this plan does not satisfy the requirement. B. No is correct. The proposed Professional Direct support plan does not deliver the required design assessment functionality, which is only available in the higher-cost Premier support tier. Since the solution fails to meet the requirement of enabling Microsoft design assessment requests, this is the correct answer. Key Concepts: 1. Azure Support Tier Capabilities: Azure offers five primary public support tiers (Basic, Developer, Standard, Professional Direct, Premier) with escalating benefits and costs, each tailored to different organizational support needs, a core AZ-900 knowledge domain. 2. Proactive vs Reactive Support Benefits: Lower and mid-tier Azure support plans primarily cover reactive break-fix support for operational issues, while premium tiers like Premier add proactive services including environment design assessments, architecture reviews, and cost optimization guidance. 3. Support Plan Cost Optimization: Selecting an appropriate Azure support plan requires matching required functional capabilities to tier benefits to ensure all requirements are met while minimizing unnecessary expenditure, a key cloud cost management concept for AZ-900. References: Azure Support Plans Overview, Compare Azure Support Plan Features

The scenario requires deploying Azure virtual machines, which requires access to and control over virtualized cloud infrastructure resources. Software as a Service (SaaS) is a cloud deployment model where the cloud provider fully manages all underlying infrastructure, platform layers, and end-user applications. Customers only access pre-built, ready-to-use software via a client interface, with no ability to provision, configure, or manage underlying infrastructure assets such as virtual machines. The proposed solution of using SaaS does not provide the level of infrastructure access required to deploy custom virtual machines, so it fails to meet the stated goal. Option Analysis: A. This option is incorrect. SaaS offerings are purpose-built for end-user consumption of fully managed applications, with no customer access to virtualized compute resources for custom VM deployment. Using SaaS would not allow you to provision or manage Azure virtual machines as required, so the solution does not meet the goal, making the Yes answer invalid. B. This option is correct. The appropriate cloud deployment model for deploying custom virtual machines is Infrastructure as a Service (IaaS), which grants customers control over virtualized compute, storage, and networking resources to provision and manage VMs. Since SaaS does not support VM deployment, the proposed solution does not satisfy the requirement, so the No answer is correct. Key Concepts: 1. Cloud Service Model Responsibility Boundaries: A core AZ-900 domain concept that defines the split of management tasks between cloud providers and customers across IaaS, PaaS, and SaaS. For SaaS, providers handle all infrastructure, platform, and application management, eliminating customer access to deploy custom infrastructure resources like VMs. 2. Azure Virtual Machine Service Classification: Azure Virtual Machines are a native IaaS offering, which aligns with the requirement to deploy custom virtual server instances, as IaaS provides the necessary level of infrastructure control for this use case. 3. Cloud Service Model Use Case Alignment: Each service model is designed for specific workloads: SaaS for end-user applications, PaaS for application development without infrastructure management overhead, and IaaS for lift-and-shift workloads and custom infrastructure deployment such as VMs. References: Describe cloud service types, Microsoft Learn, https://learn.microsoft.com/en-us/training/modules/describe-cloud-service-types/ Azure Virtual Machines overview, Microsoft Learn, https://learn.microsoft.com/en-us/azure/virtual-machines/overview

The scenario requires deploying Azure virtual machines, which are infrastructure-level resources that grant users full control over the guest operating system, installed software, network configurations, and attached storage. The proposed solution uses Platform as a Service (PaaS), a cloud service model where the cloud provider manages all underlying infrastructure, operating systems, middleware, and runtime environments, while users only manage their applications and associated data. PaaS offerings abstract the infrastructure layer completely from end users, so they do not support direct deployment and full management of dedicated virtual machines. As a result, the proposed PaaS solution does not meet the stated requirement to deploy Azure virtual machines, so the correct answer is No. Option Analysis: A. This option is incorrect. PaaS is designed for users who want to build, deploy, and run applications without managing underlying server infrastructure. PaaS offerings such as Azure App Service or Azure Functions do not allow users to provision and manage full, customizable virtual machine instances, so using PaaS cannot satisfy the requirement to deploy Azure VMs. B. This option is correct. Azure Virtual Machines are classified as Infrastructure as a Service (IaaS) resources, which is the appropriate service model for deploying and managing virtualized server instances with full OS and workload control. Since the solution incorrectly uses PaaS instead of the required IaaS model, it does not meet the stated goal. Key Concepts: 1. Cloud Service Models: The three core cloud service models covered in AZ-900 are IaaS, PaaS, and SaaS. IaaS delivers virtualized compute, storage, and networking resources where customers manage the operating system, applications, and data, while the cloud provider manages physical hardware. PaaS abstracts infrastructure and OS management to let customers focus only on application development, and SaaS delivers fully managed end-user applications. 2. Azure Virtual Machine Classification: Azure Virtual Machines are explicitly categorized as IaaS resources. They provide full administrative control over the guest operating system, enabling users to run custom software, apply custom OS configurations, and manage workloads that require direct access to server infrastructure, which is not supported by PaaS offerings. 3. Shared Responsibility Model: For IaaS resources like VMs, the customer is responsible for managing the guest operating system, security patches, middleware, and data. For PaaS resources, the cloud provider manages the operating system, patches, and middleware, which reduces customer management overhead but eliminates the ability to control underlying server instances. References: Cloud service models, Azure Virtual Machines overview, https://learn.microsoft.com/en-us/azure/virtual-machines/overview