HOTSPOT (Drag and Drop is not supported)You design a solution for the web tier of WebApp1 as shown in the exhibit.For each of the following statements, select Yes if the statement is true. Otherwise, select No.Note: Each correct selection is worth one point.Hot Area:
Answer(s): A
Box 1: YesAny new deployments to Azure must be redundant in case an Azure region fails.Traffic Manager is resilient to failure, including the failure of an entire Azure region.Box 2: NoTraffic Manager provides load balancing, but not auto-scaling.Box 3: NoAutomatic failover using Azure Traffic Manager: when you have complex architectures and multiple sets of resources capable of performing the same function, you can configure Azure Traffic Manager (based on DNS) to check the health of your resources and route the traffic from the non-healthy resource to the healthy resource.
https://docs.microsoft.com/en-us/azure/traffic-manager/traffic-manager-overview https://docs.microsoft.com/en-us/azure/networking/disaster-recovery-dns-traffic-manager
You have an Azure subscription that contains an Azure Data Lake Storage Gen2 account named storage1 and an Azure Synapse Analytics workspace named Workspace1. Workspace1 contains a serverless SQL pool and an Apache Spark pool.You need to recommend a disaster recovery solution for storage1.What should you include in the recommendation?
Answer(s): C
To implement a disaster recovery (DR) solution for your Azure Synapse Analytics environment and Azure Data Lake Storage (ADLS) Gen2 account, you must combine storage-level redundancy with Synapse-specific backup features.1. Storage Account Disaster RecoveryFor the Azure Data Lake Storage Gen2 account, use geo-redundant options to ensure data remains durable during a regional outage.*-> Replication Type: Configure the account for Geo-redundant storage (GRS) or Geo-zone-redundant storage (GZRS). This asynchronously replicates data to a secondary paired region.Failover: In a disaster, you can initiate a customer-managed failover, which updates DNS entries to make the secondary endpoint the new primary.Read Access: For better availability, use Read-access geo-redundant storage (RA-GRS), which allows read-only operations from the secondary region even before a failover is initiated.*-> 2. Azure Synapse Analytics Geo-BackupAzure Synapse includes built-in geo-backup capabilities, primarily focused on the data warehouse components.Standard Geo-Backup: Synapse automatically performs a geo-backup once every 24 hours to the paired region. This ensures a Recovery Point Objective (RPO) of 24 hours.Restoration: In a DR event, you can restore these backups to a new workspace in a different region using the Azure portal or PowerShell.Serverless SQL Pool: Since serverless SQL pools do not persist data (only metadata like views and external tables), they rely heavily on the ADLS Gen2 recovery described above. You should maintain your DDL scripts (schema) in source control (e.g., Git) to quickly recreate metadata in the secondary region.3. Apache Spark Pool Recovery
https://learn.microsoft.com/en-us/azure/synapse-analytics/sql-data-warehouse/backup-and-restore
You have an Azure virtual machine named VM1 that contains a third-party application named App1. App1 is installed in a folder named D:\App1.You back up the files on VM1 by using the Microsoft Azure Recovery Services (MARS) agent and include only D:\App1 in the backup.You discover that the OS disk of VM1 is corrupted, and the virtual machine cannot start.You need to recover VM1. The solution must minimize how long it takes to recover VM1.What should you do?
The best action to keep the recovery time low is to create a new virtual machine from an Azure Marketplace image, and then restore the application folder from the backup using the MARS agent.This method is faster and more efficient because the MARS agent only backs up individual files and folders, not full system volumes or disks.Backup Scope Limitations: The Microsoft Azure Recovery Services (MARS) agent was configured to back up only the specific third-party application folder, not the entire virtual machine or the OS disk.Impossible Alternative [Not D]: You cannot create a new VHD from a Recovery Services vault if you did not perform an Azure VM-level backup. Because the OS disk was never backed up into the vault, there is no disk image or OS VHD available to restore.Low Recovery Time: Deploying a fresh, pre-configured image directly from the Azure Marketplace and pulling just the isolated application folder is the only functional path to recovery.
https://learn.microsoft.com/en-us/azure/backup/backup-azure-file-folder-backup-faq
DRAG DROP (Drag and Drop is not supported)You have an Azure subscription.As part of a highly available deployment, you plan to deploy 30 virtual machines to an Azure region that contains three availability zones.You need to recommend a deployment solution for the virtual machines, availability sets, and availability zones. The solution must maximize the availability of the deployment.Which four actions should you recommend be performed in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.Note: More than one order of answer choices is correct. You will receive credit for any of the correct orders you select.Select and Place:
Step 1: Create availability setsStep 2: Create proximity placement groupsA Proximity Placement Group (PPG) in Azure is a logical grouping that ensures your Azure compute resources (like VMs, Availability Sets, or VM Scale Sets) are physically located close together in the same data center, minimizing network latency between them, which is crucial for low-latency, high-performance applications like SAP or HPC. While Availability Zones provide resiliency across different data centers, PPGs prioritize colocation for faster communication, even within a single zone, by pinning resources to one physical facility.Incorrect:* Create capacity placement groupsAn Azure Capacity Reservation Group (CRG) is a container that holds one or more Capacity Reservations, allowing you to reserve specific compute capacity (VM size, region, zone) and ensure it's available for your virtual machines, even during peak demand, providing a guaranteed SLA for critical workloads without long-term commitments.Step 3: Deploy one virtual machine to each availability zone.You deploy one VM to each Azure Availability Zone (AZ) first to establish fundamental High Availability (HA) by spreading across physically isolated data centers, ensuring resilience against zone-wide failures, then add remaining VMs (perhaps to an Availability Set within zones or spread across zones/sets) and leverage Proximity Placement Groups (PPGs) to keep low-latency dependent VMs co-located, optimizing performance while maintaining the HA foundation set by the initial zone distribution. This strategy balances broad availability with tight latency for specific workloads.Step 4: Deploy the remaining virtual machines
https://learn.microsoft.com/en-us/azure/virtual-machines/co-location
You have an Azure subscription.You plan to deploy a virtual machine scale set that will contain five virtual machines in a single zone of an Azure region. The virtual machines will use managed disks.You need to recommend an orchestration mode for the scale sets. The solution must ensure that each virtual machine will reside in its own update domain and fault domain.What should you recommend?
Orchestration modes for Virtual Machine Scale Sets in AzureSupported by Uniform orchestration for scale sets* 5 update domainsIncorrect:Not B:Supported by Flexible orchestration for scale sets* Update DomainsDepreciated (platform maintenance performed FD by FD)Not C:Flexible orchestration with Fixed SpreadingMemory Preserving Updates Not Supported and Fixed Spreading (platformFaultDomainCount > 1) Does not support update domains.Not D:Memory Preserving Updates Supported or Scale set with Max Spreading (platformFaultDomainCount=1) Does not support update domains.Note:Scale Sets with Flexible Orchestration (Recommended)Optimized for high availability and scalability with identical or mixed virtual machine types. Flexible Orchestration is the reccomended orchestration mode when deploying scale sets in Azure.Uniform orchestration ensures consistency by using a predefined virtual machine profile to deploy identical instances within a scale set.
https://learn.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-orchestration-mo des
Post your Comments and Discuss Microsoft AZ-305 exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the AZ-305 content, but please register or login to continue.