All practice questions

1198 questions

Question 961Question

A financial services firm is architecting a distributed transaction processing platform on Azure Virtual Machines. The platform requires high-speed inter-node communication with sub-millisecond latency. To meet compliance and business continuity mandates, the compute infrastructure must guarantee an uptime SLA of at least 99.99%99.99\% and withstand the failure of an entire datacenter facility within a region.

Which two actions should you include in the design? (Select two.)

Select all that apply

Show answer & explanation

Answer: Deploy the virtual machines across multiple Availability Zones; Create a separate Proximity Placement Group for each Availability Zone and associate the virtual machines in each zone with their respective Proximity Placement Group

Answer

To meet the requirements, you should deploy the virtual machines across multiple Availability Zones, and create a separate Proximity Placement Group (PPG) for each Availability Zone, associating the virtual machines in each zone with their respective PPG.
To satisfy the 99.99%99.99\% VM uptime SLA and ensure tolerance against datacenter outages, virtual machines must be distributed across multiple Availability Zones. To ensure the lowest possible latency within each zone's cluster subset, a separate Proximity Placement Group must be created for each Availability Zone. This strategy colocates the virtual machines within each zone while maintaining regional zone-redundancy.

Step-by-Step Solution

1
Evaluate the SLA and resiliency requirements
Determined that meeting a 99.99%99.99\% compute SLA and surviving a datacenter outage requires distributing the virtual machines across at least two Availability Zones within the region.
Azure guarantees a 99.99%99.99\% uptime SLA only when two or more VM instances are deployed across two or more Availability Zones in the same region.
2
Evaluate the latency requirements
Determined that achieving sub-millisecond inter-node latency requires using Proximity Placement Groups (PPGs) to physically colocate VM instances close together.
PPGs group virtual machines within the same physical datacenter to minimize network latency.
3
Integrate Availability Zones and Proximity Placement Groups
Establish one PPG per Availability Zone and associate the VMs accordingly.
Since Proximity Placement Groups are physically restricted to a single datacenter/zone to enforce proximity, spanning a single PPG across multiple zones is not recommended because it increases inter-zone latency. Creating a separate PPG for each zone ensures maximum colocation within each zone while preserving the high availability architecture across zones.

Key Concept

Designing compute high availability with Availability Zones and Proximity Placement Groups
Estimated Time:2m 30s
Question 962Question

A logistics company is designing a new cloud-native fleet tracking solution on Azure. The solution requires hosting two distinct workloads:

* A real-time telemetry service that processes GPS events from delivery vehicles. This service must scale out dynamically based on the number of pending messages in an Azure Service Bus queue using KEDA.
* A route optimization batch job that runs once per day, processes historical route data to completion, and then terminates.

The solution must minimize administrative effort.

Which two services should you recommend?

Select all that apply

Show answer & explanation

Answer: Azure Container Apps to host the real-time telemetry service; Azure Container Apps Jobs to run the daily route optimization batch job

Answer

Azure Container Apps to host the real-time telemetry service and Azure Container Apps Jobs to run the daily route optimization batch job
Azure Container Apps is a serverless container platform that allows running microservices and APIs with native KEDA integration for event-driven scaling, making it the ideal low-overhead choice for the real-time telemetry service. Azure Container Apps Jobs extends this capability by providing a managed environment for run-to-completion workloads, which is perfect for the daily route optimization batch task without introducing cluster management overhead.

Step-by-Step Solution

1
Analyze the workload requirements and administrative constraints.
The telemetry service requires event-driven scaling (KEDA) for continuous processing, while the route optimization task is a transient batch job. The overriding design goal is to minimize administrative effort.
This establishes the criteria for selecting serverless or managed hosting options over complex container orchestration platforms.
2
Evaluate the telemetry service hosting options.
Azure Container Apps supports serverless scale-to-zero and event-driven scaling with KEDA natively. Azure Kubernetes Service (AKS) also supports KEDA but requires cluster administration, violating the minimization of overhead.
This identifies the optimal solution for the continuous ingestion service.
3
Evaluate the batch job hosting options.
Azure Container Apps Jobs is designed explicitly for run-to-completion, scheduled, or event-triggered tasks. Azure Container Instances (ACI) would require custom scheduling scripts or external orchestration to run daily, increasing management overhead.
This completes the selection for the transient batch processing workload.

Key Concept

Selecting serverless container services (Azure Container Apps and Jobs) to minimize administrative overhead while supporting KEDA-based scaling and batch execution.
Estimated Time:1m 30s
Question 963Question

A financial services company hosts a transactional SQL Server database on an Azure virtual machine (VM) in the East US region. You are designing a disaster recovery (DR) solution to the West US region. The solution must meet a Recovery Time Objective (RTO) of 2 hours2\text{ hours} and a Recovery Point Objective (RPO) of 10 minutes10\text{ minutes}.

The database VM has the following storage configuration:
- One 128 GB128\text{ GB} OS disk
- One 512 GB512\text{ GB} Premium SSD disk for transaction logs, with a peak write churn of 65 MB/s65\text{ MB/s}
- Two 1 TB1\text{ TB} Premium SSD disks for database files, with a combined peak write churn of 40 MB/s40\text{ MB/s}

Which disaster recovery solution should you recommend?

Show answer & explanation

Answer: Configure SQL Server Always On Availability Groups to replicate the database to a target virtual machine in the West US region.

Answer

Configure SQL Server Always On Availability Groups to replicate the database to a target virtual machine in the West US region.
The transaction log disk has a peak write churn of 65 MB/s65\text{ MB/s}, and the total peak write churn of the virtual machine is 105 MB/s105\text{ MB/s}. Azure Site Recovery (ASR) has a maximum supported write churn limit of 54 MB/s54\text{ MB/s} per disk and 100 MB/s100\text{ MB/s} per virtual machine, even when using the High Churn policy. Since these limits are exceeded, ASR cannot be used. Implementing database-level replication such as SQL Server Always On Availability Groups is the correct design pattern because it operates at the database engine layer and is not bound by ASR's disk-level write churn replication limits.

Step-by-Step Solution

1
Evaluate the write churn metrics of the workload against Azure Site Recovery limits.
The log disk churn (65 MB/s65\text{ MB/s}) exceeds the 54 MB/s54\text{ MB/s} High Churn limit, and the total VM churn (105 MB/s105\text{ MB/s}) exceeds the 100 MB/s100\text{ MB/s} limit.
Determines whether Azure Site Recovery is a viable technology for replicating this virtual machine.
2
Evaluate the backup solution against the RPO requirement.
Azure Backup cannot meet a 10-minute10\text{-minute} RPO as it operates on scheduled snapshots.
Rules out backup-based replication for low-RPO transactional requirements.
3
Select a database-native replication strategy that bypasses infrastructure-level disk churn limits.
SQL Server Always On Availability Groups replicates transactions at the database tier and is not subject to Azure Site Recovery's block-level replication limits.
Provides a compliant disaster recovery solution that meets the RPO, RTO, and workload limits.

Key Concept

Azure Site Recovery write churn limits and database-level replication alternatives
Estimated Time:1m 30s
Question 964Question

An enterprise plans to migrate a legacy batch processing utility to Azure. The utility is currently packaged as a Linux container. The migrated workload must meet the following requirements:
- It must execute once a day, triggered by a message in an Azure Queue Storage queue.
- Each execution takes between 25 and 45 minutes to complete.
- It must securely access an Azure SQL Database that is restricted to a private endpoint within a virtual network.
- To minimize costs, no compute charges must be incurred when the utility is idle.
- Administrative and infrastructure management overhead must be minimized.

Which Azure compute solution should you recommend?

Show answer & explanation

Answer: An Azure Container Apps job deployed in a custom virtual network

Answer

An Azure Container Apps job deployed in a custom virtual network
The correct answer is the solution specifying Azure Container Apps jobs. Azure Container Apps jobs are purpose-built for executing containerized tasks that run to completion. They support long-running processes (exceeding the 10-minute serverless function limit), can be triggered by queue messages, support virtual network integration to secure connection to the database private endpoint, and scale down to zero instances when idle, ensuring no compute costs are incurred. This serverless container offering also requires very low administrative overhead.

Step-by-Step Solution

1
Analyze the execution duration requirement of 25 to 45 minutes.
Azure Functions on a Consumption plan is ruled out due to its maximum 10-minute timeout constraint.
Selecting a compute option that cannot accommodate the workload's execution duration will lead to task failures.
2
Evaluate the scaling and cost requirement to incur zero compute charges when idle.
Azure Functions on a Premium plan is ruled out because it requires a minimum of one active instance, which incurs baseline costs even when no tasks are running.
The solution must support scaling to absolute zero instance count to meet the zero-cost idle requirement.
3
Assess the administrative overhead and workload type.
Azure Container Apps jobs are selected over Azure Kubernetes Service because Container Apps jobs run containerized run-to-completion tasks with serverless management, avoiding the high operational overhead of maintaining an AKS cluster.
The scenario requires minimizing infrastructure management and operational overhead.

Key Concept

Selecting serverless compute hosting options based on execution duration, cost limits, container support, and virtual network connectivity constraints.
Question 965Question

An organization has an on-premises virtual machine named VM1 running SQL Server that hosts a critical sales database. You are designing a disaster recovery (DR) solution to Azure. VM1 has the following disk configuration:

* Disk 0 (OS): 120 GB120\text{ GB} Standard HDD with a write disk churn rate of 1.2 MB/s1.2\text{ MB/s}
* Disk 1 (Application): 250 GB250\text{ GB} Premium SSD with a write disk churn rate of 4.5 MB/s4.5\text{ MB/s}
* Disk 2 (Database Log): 500 GB500\text{ GB} Premium SSD with a write disk churn rate of 18 MB/s18\text{ MB/s}

The DR solution must meet an RPO of 1 hour1\text{ hour} and an RTO of 2 hours2\text{ hours}. Which two actions should you include in the disaster recovery design? (Select two.)

Select all that apply

Show answer & explanation

Answer: Replicate Disk 0 and Disk 1 to Azure by using Azure Site Recovery.; Configure SQL Server Always On Availability Groups to replicate the database to a SQL Server instance running on an Azure virtual machine.

Answer

Replicate Disk 0 and Disk 1 to Azure by using Azure Site Recovery, and configure SQL Server Always On Availability Groups to replicate the database to a SQL Server instance running on an Azure virtual machine.
The correct options recommend replicating the lower-churn OS and application disks (Disk 0 and Disk 1) using Azure Site Recovery while using SQL Server Always On Availability Groups for the high-churn database workloads on Disk 2. This satisfies the Azure Site Recovery limits (where Standard HDD is limited to 2 MB/s2\text{ MB/s} and Premium SSD is limited to 10 MB/s10\text{ MB/s} write churn per disk) and ensures a supported, reliable disaster recovery topology.

Step-by-Step Solution

1
Analyze the write churn of each disk on VM1 against Azure Site Recovery limits.
Disk 0 (1.2 MB/s1.2\text{ MB/s}) is under the 2 MB/s2\text{ MB/s} limit for Standard HDD. Disk 1 (4.5 MB/s4.5\text{ MB/s}) is under the 10 MB/s10\text{ MB/s} limit for Premium SSD. Disk 2 (18 MB/s18\text{ MB/s}) exceeds the standard 10 MB/s10\text{ MB/s} limit per Premium SSD disk.
To determine which disks can be replicated using ASR without replication failures.
2
Select the appropriate disaster recovery mechanism for the high-churn database disk.
Exclude Disk 2 from Azure Site Recovery and use native database replication (SQL Server Always On Availability Groups) to replicate the database logs and data to Azure.
High-transaction workloads exceeding ASR limits require application-level replication to meet low RPO/RTO goals.
3
Combine the solutions to design the hybrid disaster recovery plan.
ASR replicates the OS and application disks, while SQL Server Always On replicates the database tier.
This combination ensures all VM components are protected within supported limits while satisfying RPO and RTO constraints.

Key Concept

Azure Site Recovery write churn limits require workload separation or application-level replication for high-transaction database disks.
Estimated Time:2m 0s
Question 966Question

A company is planning to deploy a web application on Azure and requires a load balancing solution. The solution must support SSL/TLS termination at the load balancer level and URL path-based routing (such as routing requests for '/video/*' to a specific backend pool).

Which of the following Azure services support these requirements? (Select TWO)

Select all that apply

Show answer & explanation

Answer: Azure Application Gateway; Azure Front Door

Answer

Azure Application Gateway and Azure Front Door are the services that support both SSL/TLS termination and URL path-based routing.
Azure Application Gateway and Azure Front Door both operate at Layer 7 (HTTP/HTTPS) and support SSL/TLS termination and URL-based path routing to backend pools.

Step-by-Step Solution

1
Identify the required routing capabilities.
The requirements specify SSL/TLS termination and URL path-based routing, which require Layer 7 (application-layer) capabilities.
This allows us to filter out services that do not operate at the application layer.
2
Evaluate the capabilities of Azure Front Door and Azure Application Gateway.
Both services operate at Layer 7 and natively support SSL/TLS offloading and URL path-based routing.
This identifies the correct services meeting the application requirements.
3
Evaluate the incorrect options based on limitations and SKU constraints.
Azure Traffic Manager is DNS-based and cannot inspect URL paths or terminate SSL. Azure Load Balancer operates at Layer 4, lacks these Layer 7 features, and cannot mix Basic and Standard SKUs in its configuration.
This confirms why the other options fail to meet the requirements.

Key Concept

Azure Layer 7 load balancing services (Application Gateway and Front Door) support application-layer features like SSL/TLS offloading and path-based routing, unlike Layer 4 or DNS-based balancers.
Question 967Question

An enterprise is designing a lifecycle management policy for audit logs stored in a General-purpose v2 (GPv2) Azure Blob Storage account. The logs must adhere to the following requirements:
- The logs must be frequently accessed and analyzed for the first 3030 days after creation.
- Between day 3131 and day 180180, the logs are rarely accessed but must remain available for immediate, sub-second retrieval to support unexpected security audits.
- After 180180 days, the logs are only retained for historical compliance, can tolerate retrieval latencies of up to 1515 hours, and must be stored at the lowest possible cost.
- The logs must be automatically deleted 365365 days after creation.

Which two actions should you include in the lifecycle management policy? (Choose two.)

Select all that apply

Show answer & explanation

Answer: Transition blobs to the Cool tier 3030 days after last modification; Transition blobs to the Archive tier 180180 days after last modification

Answer

The correct configuration transitions blobs to the Cool tier 3030 days after modification, and transitions blobs to the Archive tier 180180 days after modification.
The correct configuration transitions blobs to the Cool tier 3030 days after modification to save costs while maintaining sub-second retrieval times, and then transitions them to the Archive tier 180180 days after modification when high retrieval latency is acceptable. This ensures that the blobs spend 185185 days in the Archive tier before deletion at day 365365, satisfying the 180180-day minimum retention threshold and avoiding early deletion fees.

Step-by-Step Solution

1
Determine the optimal transition timing for the Cool tier based on latency requirements.
Transition to the Cool tier must occur 3030 days after modification because the data is rarely accessed starting on day 3131, but still requires sub-second retrieval times, which the Cool tier supports.
The Hot tier is too expensive for rarely accessed data, and the Archive tier does not support sub-second retrieval times.
2
Determine the optimal transition timing for the Archive tier based on latency and cost requirements.
Transition to the Archive tier must occur 180180 days after modification when the data no longer requires sub-second retrieval times.
The Archive tier offers the lowest storage cost and is acceptable since a retrieval latency of up to 1515 hours is tolerated after 180180 days.
3
Calculate the duration spent in the Archive tier to avoid early deletion charges.
If transitioned to Archive at day 180180 and deleted at day 365365, the blobs remain in the Archive tier for 185185 days (365180=185365 - 180 = 185).
This exceeds the Archive tier's 180180-day minimum retention requirement, avoiding any early deletion penalties.

Key Concept

Azure Storage lifecycle management allows automated tier transitions (Hot to Cool, Cool to Archive) and deletion based on blob modification or creation age. The design must balance access tier latency, storage costs, and minimum retention periods (such as 180180 days for the Archive tier) to avoid early deletion penalties.
Question 968Question

An organization is migrating a legacy SQL Server failover cluster instance (FCI) to Azure Virtual Machines. The workload requires a compute uptime SLA of 99.99%99.99\% and must remain operational even in the event of an entire datacenter outage within the region. The database nodes require access to a shared block storage volume for the cluster resources. Which of the following compute and storage deployment strategies should you recommend to meet these requirements?

Show answer & explanation

Answer: Deploy the cluster virtual machines in different Availability Zones within the same Azure region, and attach a zone-redundant storage (ZRS) Premium SSD shared disk to both virtual machines.

Answer

Deploying the cluster virtual machines in different Availability Zones within the same Azure region, and attaching a zone-redundant storage (ZRS) Premium SSD shared disk to both virtual machines.
To achieve a 99.99%99.99\% virtual machine connectivity SLA and survive a datacenter outage, virtual machines must be deployed across two or more Availability Zones in the same region. Because the legacy cluster requires shared block storage, a zone-redundant storage (ZRS) Premium SSD shared disk must be used so that the shared volume can be attached to virtual machines residing in different zones.

Step-by-Step Solution

1
Identify the compute high availability requirement.
A 99.99%99.99\% VM uptime SLA requires deploying VMs across multiple Availability Zones in the same region.
Single-zone deployments like Availability Sets only provide up to a 99.95%99.95\% SLA.
2
Evaluate the shared storage requirement for the failover cluster.
The shared block storage volume must be accessible by VMs located in different Availability Zones.
Locally redundant storage (LRS) shared disks are restricted to a single zone, whereas zone-redundant storage (ZRS) shared disks can span multiple zones in a region.
3
Combine compute and storage configurations to form the final architecture.
Cross-zone VM placement paired with a ZRS Premium SSD shared disk meets both the 99.99%99.99\% SLA and shared-disk requirements.
This is the only configuration that provides zone-redundant compute and storage, fulfilling the high availability and cluster requirements.

Key Concept

Designing zone-redundant compute architectures with shared storage for high availability.
Estimated Time:2m 0s
Question 969Question

You are designing the serverless compute architecture for a telemetry processing solution. The solution must support two workloads:

* Workload 1: An HTTPS ingestion endpoint that receives telemetry data in unpredictable spikes. The endpoint must scale to zero when idle, support outbound virtual network (VNet) integration to connect to a private backend database, and minimize cold-start latency.
* Workload 2: A batch processing job that runs whenever a new raw data file is uploaded to Azure Blob Storage. Each execution performs complex transformations and takes approximately 1515 minutes to complete.

Which two hosting plans should you recommend to meet the requirements for the workloads? (Select two.)

Select all that apply

Show answer & explanation

Answer: An Azure Functions App on the Flex Consumption plan to host Workload 1; An Azure Container Apps Job to host Workload 2

Answer

To meet the requirements, you should recommend hosting Workload 1 on an Azure Functions App using the Flex Consumption plan and hosting Workload 2 on an Azure Container Apps Job.
The Azure Functions Flex Consumption plan is the correct choice for the ingestion endpoint because it provides serverless scaling to zero and built-in virtual network integration to access the private database securely. Azure Container Apps Jobs are correct for the batch processing job because they execute tasks to completion on demand and support execution times that exceed the ten-minute limit of standard serverless functions.

Step-by-Step Solution

1
Evaluate the requirements of Workload 1.
Workload 1 requires serverless scaling (scale to zero), low cold start latency, and outbound VNet integration to access a private database.
Identifying these key networking and performance constraints narrow down the choices from standard consumption plans.
2
Select the hosting plan for Workload 1.
The Azure Functions Flex Consumption plan supports scale-to-zero and outbound VNet integration, whereas the standard Consumption plan does not support VNet integration.
Matching VNet support and scale-to-zero capabilities ensures secure database connectivity and cost-efficiency.
3
Evaluate the requirements of Workload 2.
Workload 2 requires running a batch processing job triggered by file uploads that takes approximately 1515 minutes to complete.
Understanding the execution duration is critical for avoiding serverless timeout limitations.
4
Select the hosting plan for Workload 2.
An Azure Container Apps Job is selected because it runs on-demand tasks to completion without the 1010-minute execution timeout limit of standard Azure Functions Consumption plans.
This prevents execution timeouts while maintaining serverless execution semantics.

Key Concept

Architecting serverless solutions in Azure based on network isolation, scaling, and execution duration constraints.
Question 970Question

A retail logistics company is designing the compute infrastructure for a new real-time inventory routing engine. The system has the following requirements:
- Must run continuously 24/7 as a steady-state production workload with a guaranteed virtual machine uptime SLA of 99.99%.
- Requires memory-optimized compute resources offering at least 8 GB of RAM per vCPU.
- Requires high-performance storage capable of sustaining at least 50,000 IOPS.
- Must ensure that data is encrypted in memory during execution to comply with strict internal data security standards.

Which compute and storage architecture should you recommend to meet these requirements?

Show answer & explanation

Answer: Deploy ECesv5-series confidential virtual machines across two or more Availability Zones with Premium SSD v2 storage.

Answer

Deploy ECesv5-series confidential virtual machines across two or more Availability Zones with Premium SSD v2 storage.
The correct architecture uses ECesv5-series VMs which utilize AMD SEV-SNP technology to encrypt data in use, satisfying the security requirement, and provide 8 GB RAM per vCPU, satisfying the memory-optimized requirement. Distributing these VMs across multiple Availability Zones guarantees a 99.99% uptime SLA. Attaching Premium SSD v2 disks easily meets the 50,000 IOPS threshold.

Step-by-Step Solution

1
Analyze security and memory requirements.
Identify that the system requires confidential computing (in-memory encryption) and memory-optimized resources (8 GB RAM per vCPU). The ECesv5-series meets both criteria.
This filters out general-purpose options like DCesv5-series and standard non-confidential options.
2
Analyze SLA and availability requirements.
To meet the 99.99% virtual machine uptime SLA, the virtual machines must be deployed across two or more Availability Zones in the same region. Deploying in a single zone or using Spot VMs is ruled out.
Single zone deployments offer up to 99.9% SLA, and Spot VMs offer no SLA due to eviction risk.
3
Analyze storage performance requirements.
Verify that Premium SSD v2 can sustain the required 50,000 IOPS.
Standard SSDs cannot scale to 50,000 IOPS, which eliminates options using lower-tier storage.

Key Concept

Designing high-availability confidential compute solutions with memory-optimized workloads and high-performance storage.
Estimated Time:2m 30s
Question 971Question

A healthcare provider ingests patient monitoring telemetry into an Azure Blob Storage account. The storage solution must remain resilient against a primary datacenter outage. The data lifecycle and access patterns are defined as follows:

* The telemetry is highly active and requires sub-second retrieval latency for the first 1414 days.
* From day 1515 through day 9090, the telemetry is accessed infrequently but must be available for immediate, sub-second querying.
* After 9090 days, the telemetry is only accessed for regulatory compliance audits that tolerate a retrieval latency of up to 1515 hours.
* All telemetry must be retained for 77 years (2,5552,555 days) and then deleted.

You need to design a storage and lifecycle management strategy that meets these requirements at the lowest possible cost.

Which strategy should you recommend?

Show answer & explanation

Answer: Configure a Zone-Redundant Storage (ZRS) account. Create a lifecycle policy to transition blobs from the Hot tier to the Cool tier after 14 days, transition them to the Archive tier after 90 days, and delete them after 2555 days.

Answer

Configure a Zone-Redundant Storage (ZRS) account. Create a lifecycle policy to transition blobs from the Hot tier to the Cool tier after 14 days, transition them to the Archive tier after 90 days, and delete them after 2555 days.
The correct strategy uses Zone-Redundant Storage (ZRS) to protect against a primary datacenter outage by replicating data across three availability zones. It uses the Cool tier from day 15 to day 90 to meet the requirement for immediate, sub-second query access at a lower storage cost compared to the Hot tier. Moving the telemetry to the Archive tier after 90 days achieves the lowest storage cost while satisfying the regulatory audit requirement, which tolerates the latency associated with Archive rehydration. Deleting the data after 2555 days satisfies the 7-year retention limit.

Step-by-Step Solution

1
Analyze the redundancy requirement to ensure survival during a primary datacenter outage.
Eliminate Locally Redundant Storage (LRS) options as they replicate data within a single datacenter, and select Zone-Redundant Storage (ZRS) which replicates data across three separate zones in the region.
This guarantees data availability even if a primary datacenter experiences an outage.
2
Evaluate access frequency and retrieval latency constraints for each timeline window.
Determine that the first 1414 days require Hot tier, days 1515 to 9090 require Cool tier (since sub-second query latency is needed and Cool tier keeps the data online), and after 9090 days the data can transition to Archive tier.
Archive tier data is offline and cannot be queried with sub-second latency, meaning the transition to Archive must be deferred until day 9191 when the 1515-hour latency limit for compliance audits applies.
3
Calculate retention and deletion constraints.
Configure the final action to delete the blobs after 2,5552,555 days (77 years).
This minimizes long-term storage costs once the compliance retention period expires.

Key Concept

Selecting Azure storage redundancy and lifecycle management transition policies based on redundancy needs, latency constraints, and cost optimization.
Question 972Question

A media company is designing a new cloud-native video processing platform on Azure. The platform must host containerized microservices that perform video encoding. The microservices must scale dynamically based on the number of messages in an Azure Service Bus queue using Kubernetes Event-driven Autoscaling (KEDA). The design must minimize the administrative and operational effort of managing container infrastructure. Which Azure service should you recommend?

Show answer & explanation

Answer: Azure Container Apps

Answer

Azure Container Apps
Azure Container Apps is the correct choice because it is a serverless container platform that provides built-in integration with Kubernetes Event-driven Autoscaling (KEDA). This allows microservices to scale dynamically based on Service Bus queue length while abstracting the underlying Kubernetes infrastructure, satisfying the requirement to minimize administrative and operational overhead.

Step-by-Step Solution

1
Analyze the requirements
The solution requires hosting containerized microservices, using KEDA-based event-driven scaling (Azure Service Bus queue metrics), and minimizing administrative and operational overhead.
This establishes the constraints and capability requirements for the target Azure compute service.
2
Evaluate candidate Azure services against KEDA support and management overhead
Azure Container Apps natively supports KEDA and is fully managed (serverless). Azure Kubernetes Service (AKS) supports KEDA but requires high administrative overhead. Azure Container Instances and Azure App Service do not natively support KEDA scaling for microservices.
This rules out AKS due to the overhead constraint and rules out ACI and App Service due to the functional constraint (native KEDA support).
3
Select the optimal service
Azure Container Apps satisfies all constraints by offering serverless containers with native KEDA integration and minimal management overhead.
It aligns with the Microsoft Best Practice of selecting Azure Container Apps over AKS for microservices when custom Kubernetes API access is not required and low administrative overhead is preferred.

Key Concept

Selecting the appropriate Azure container hosting service based on scaling requirements (KEDA) and operational overhead constraints.
Question 973Question

You are designing a data retention strategy for database backup files stored in a General-purpose v2 (GPv2) Azure Blob storage account.

The backups must be managed according to the following requirements:
- For the first 14 days after creation, backups are frequently accessed for testing and must remain in the Hot tier.
- From day 15 to day 90, backups are rarely accessed but must be available with sub-second retrieval latency if a restore is needed.
- After 90 days, backups are only kept for compliance audits and can tolerate a retrieval time of up to 15 hours.
- All backups must be deleted exactly 365 days after creation.

Which lifecycle management policy ruleset minimizes storage costs without incurring early deletion charges or violating the latency requirements?

Show answer & explanation

Answer: Transition blobs to the Cool tier 14 days after creation, transition to the Archive tier 90 days after creation, and delete blobs 365 days after creation.

Answer

Transition blobs to the Cool tier 14 days after creation, transition to the Archive tier 90 days after creation, and delete blobs 365 days after creation.
The correct option transitions blobs to the Cool tier 14 days after creation, meeting the sub-second retrieval requirement for days 15 to 90. It then transitions them to the Archive tier 90 days after creation, minimizing storage costs for the remaining period since 15-hour latency is acceptable. Finally, it deletes them 365 days after creation. This ruleset avoids early deletion fees because the blobs spend 76 days in the Cool tier (exceeding the 30-day minimum) and 275 days in the Archive tier (exceeding the 180-day minimum).

Step-by-Step Solution

1
Map the access requirements and latency tolerances to storage tiers for each period.
Days 1-14 require Hot tier; days 15-90 require sub-second latency (Cool tier); days 91-365 can tolerate 15 hours latency (Archive tier); day 366+ requires deletion.
This establishes the transition timeline based on access frequency and retrieval latency.
2
Verify if the proposed transitions satisfy the minimum retention periods of the respective tiers.
Cool tier duration: 90 - 14 = 76 days (minimum is 30). Archive tier duration: 365 - 90 = 275 days (minimum is 180). Both conditions are met.
Ensuring the minimum retention periods are met avoids incurring early deletion charges.
3
Identify the ruleset that matches the tier transitions and durations.
The correct lifecycle policy transitions blobs to Cool at day 14, Archive at day 90, and deletes at day 365.
This configuration satisfies all constraints at the lowest possible cost.

Key Concept

Azure Blob Storage Lifecycle Management Tiers and Retention Constraints
Estimated Time:1m 30s
Question 974Question

Match each architectural routing and failover requirement with the most appropriate Azure load balancing or traffic routing service.

Click a left item, then click its matching right item

Items

A global web application requires path-based routing, SSL offloading, and web application firewall protection at the edge before traffic enters Azure regions.
A gaming platform needs to route low-latency UDP traffic globally to regional backends using a single static IP address acting as the entry point.
A legacy retail application in a single region requires cookie-based session affinity to ensure users stay connected to the same backend virtual machine instance.
An enterprise requires global failover for a hybrid environment where traffic must be directed to external non-Azure endpoints without proxying the network payload.

Matches

Show answer & explanation

Answer

The architectural requirements match as follows: Global SSL offloading and WAF routing maps to Azure Front Door; global UDP routing via a single static IP maps to Azure Cross-region Load Balancer; single-region cookie session affinity maps to Azure Application Gateway; and DNS-based hybrid routing to external endpoints without proxying maps to Azure Traffic Manager.
Each matching pair aligns a specific application layer, scope, and feature requirement with the correct Azure service. Azure Front Door handles global HTTP/HTTPS with SSL offloading and WAF. Azure Cross-region Load Balancer provides global Layer 4 Anycast routing for TCP/UDP. Azure Application Gateway provides regional Layer 7 capabilities like session affinity. Azure Traffic Manager provides DNS-based redirection, making it suitable for hybrid endpoints without proxying.

Step-by-Step Solution

1
Analyze the layer and scope for the first scenario.
The requirement involves global HTTP/HTTPS traffic, path-based routing, SSL offloading, and WAF protection. This indicates a Layer 7 global service, which matches Azure Front Door.
Azure Front Door is the only service that combines global scope, Layer 7 HTTP/HTTPS features, SSL termination, and native WAF integration.
2
Analyze the protocol and IP configuration for the second scenario.
The requirement involves low-latency UDP traffic globally using a single static IP address. This points to a Layer 4 global load balancing solution.
Azure Cross-region Load Balancer uses Anycast IP to route Layer 4 (TCP/UDP) traffic globally with ultra-low latency.
3
Analyze the regional requirements for the third scenario.
The requirement is for a single-region HTTP/HTTPS application needing cookie-based session affinity for backend virtual machines.
Azure Application Gateway is a regional Layer 7 load balancer that provides cookie-based session affinity, unlike global services which route between regions.
4
Analyze the routing mechanism for the fourth scenario.
The requirement is global failover for a hybrid environment to external endpoints without proxying the network payload.
Azure Traffic Manager uses DNS-based routing to return client endpoints directly, bypassing the network proxy layer and supporting external hybrid endpoints.

Key Concept

Selecting the appropriate global or regional Azure load balancing service based on protocol (Layer 4 vs Layer 7), routing method (DNS vs Anycast), and features (session affinity, SSL offloading, WAF).
Question 975Question

A healthcare organization hosts a patient record application on an Azure virtual machine named VM1 in the East US region. The application uses a SQL Server database. You are designing a disaster recovery (DR) solution to replicate the workload to the West US region while meeting a Recovery Point Objective (RPO) of 10 minutes and a Recovery Time Objective (RTO) of 2 hours. VM1 has the following disk configuration:

- Disk 0 (OS): Peak write churn of 3 MB/s3\text{ MB/s}
- Disk 1 (Application Binaries): Peak write churn of 8 MB/s8\text{ MB/s}
- Disk 2 (Database Data and Logs): Peak write churn of 95 MB/s95\text{ MB/s}

Which disaster recovery design should you recommend?

Show answer & explanation

Answer: Configure Azure Site Recovery to replicate Disk 0 and Disk 1, exclude Disk 2 from replication, and use SQL Server Always On Availability Groups to replicate the database to the target region.

Answer

Configure Azure Site Recovery to replicate Disk 0 and Disk 1, exclude Disk 2 from replication, and use SQL Server Always On Availability Groups to replicate the database to the target region.
The correct option proposes replicating Disk 0 and Disk 1 using Azure Site Recovery while excluding Disk 2, and utilizing SQL Server Always On Availability Groups for the database. This design successfully accommodates the 95 MB/s95\text{ MB/s} write churn on Disk 2, which exceeds the maximum Azure Site Recovery High Churn limit of 80 MB/s80\text{ MB/s} per disk, while ensuring that the OS and application binaries are protected and RPO/RTO targets are met.

Step-by-Step Solution

1
Analyze the write churn limits for Azure Site Recovery.
Identify that Azure Site Recovery has a standard write churn limit of 54 MB/s54\text{ MB/s} per disk and a High Churn limit of 80 MB/s80\text{ MB/s} per disk.
To determine if all VM disks can be replicated using Azure Site Recovery.
2
Compare VM1's disk churn metrics against the identified limits.
Disk 0 (3 MB/s3\text{ MB/s}) and Disk 1 (8 MB/s8\text{ MB/s}) are within limits, but Disk 2 (95 MB/s95\text{ MB/s}) exceeds the maximum ASR limit of 80 MB/s80\text{ MB/s}.
To isolate which disks are unsupported by Azure Site Recovery.
3
Determine the alternative replication method for the unsupported database disk.
Exclude Disk 2 from Azure Site Recovery replication and implement SQL Server Always On Availability Groups to replicate the database to the target region.
To ensure database replication meets the RPO and RTO requirements without exceeding Azure Site Recovery disk limits.

Key Concept

Azure Site Recovery has strict write churn limits per disk (54 MB/s54\text{ MB/s} for standard and 80 MB/s80\text{ MB/s} for High Churn). Workloads exceeding these limits must be replicated using alternative, native application-level replication methods like SQL Server Always On Availability Groups.
Question 976Question

You are designing the compute infrastructure for a media streaming company's transcoder service. The service uses stateless virtual machines that dynamically scale based on CPU utilization. The design must satisfy the following requirements:
- Maintain an uptime SLA of 99.99% for the compute instances.
- Support both Spot VMs for cost-effective scaling and On-Demand VMs for baseline capacity within the same logical group.
- Allow the operations team to interact with and manage the individual underlying virtual machines using standard VM APIs.

Which two configurations should you include in the design?

Select all that apply

Show answer & explanation

Answer: A Virtual Machine Scale Set configured in Flexible orchestration mode; Instance distribution across multiple Availability Zones within the region

Answer

To meet the requirements, you must use a Virtual Machine Scale Set in Flexible orchestration mode and distribute the instances across multiple Availability Zones.
To achieve a 99.99% SLA, virtual machines must be distributed across two or more Availability Zones in the same region. Additionally, using a Virtual Machine Scale Set in Flexible orchestration mode allows mixing Spot VMs and On-Demand VMs within the same scale set while maintaining standard VM API management for individual instances.

Step-by-Step Solution

1
Analyze the virtual machine uptime SLA requirements.
Identify that a 99.99% VM uptime SLA is required.
SLA requirements dictate whether VMs can be regional, zonal, or must span multiple Availability Zones.
2
Select the deployment topology that supports the 99.99% SLA.
Choose to distribute the virtual machines across multiple Availability Zones within the region.
In Azure, a 99.99% VM uptime SLA is only guaranteed when two or more VMs are deployed across two or more Availability Zones in the same region.
3
Evaluate the orchestration mode needed to support VM mixing and management requirements.
Select a Virtual Machine Scale Set (VMSS) in Flexible orchestration mode.
Flexible orchestration mode allows mixing Spot and On-Demand VMs in the same scale set, and permits managing individual instances using standard VM APIs.

Key Concept

Designing High Availability compute architecture using Virtual Machine Scale Sets in Flexible orchestration mode distributed across Availability Zones.
Question 977Question

An agricultural technology company is designing the compute virtualization infrastructure for two distinct workloads:

* Workload A: A continuous, time-sensitive telemetry ingestion service that processes real-time sensor data from global farms. It must run 24/7, guarantee 99.99%99.99\% availability, and maintain low, predictable disk and network latency.
* Workload B: A batch-processing machine learning model that analyzes historical weather patterns to generate seasonal yield predictions. The model runs once a week, takes approximately 66 hours to complete, and can resume from checkpoints if interrupted.

The company wants to minimize compute costs for Workload B while ensuring Workload A meets its performance and availability SLAs. Which two compute configurations should you recommend to meet these requirements?

Select all that apply

Show answer & explanation

Answer: Deploy Workload A on Azure Virtual Machines distributed across multiple Availability Zones using Premium SSDs.; Deploy Workload B on Azure Spot Virtual Machines.

Answer

Deploy Workload A on Azure Virtual Machines distributed across multiple Availability Zones using Premium SSDs, and deploy Workload B on Azure Spot Virtual Machines.
To meet the requirements of both workloads, Workload A must be deployed on standard Virtual Machines across multiple Availability Zones with Premium SSDs to guarantee a 99.99%99.99\% availability SLA and low-latency performance. Workload B must be deployed on Azure Spot Virtual Machines to achieve the lowest possible compute cost while accommodating the interruptible nature of the weekly batch run.

Step-by-Step Solution

1
Analyze the availability and latency requirements for Workload A.
Workload A requires 24/7 availability with a 99.99%99.99\% SLA and low, predictable disk latency.
This establishes the baseline infrastructure tier needed to prevent service interruption.
2
Select the appropriate compute and storage configuration for Workload A.
Distributing standard Virtual Machines across multiple Availability Zones provides a 99.99%99.99\% SLA. Configuring them with Premium SSDs meets the low-latency storage requirements.
This meets the SLA requirements without the eviction risk associated with Spot VMs.
3
Analyze the run frequency, duration, and cost requirements for Workload B.
Workload B runs weekly for 66 hours, can resume from checkpoints if interrupted, and must have the lowest possible compute cost.
This identifies the tolerance for interruption and the primary optimization goal.
4
Evaluate and select the cost-effective compute option for Workload B.
Azure Spot VMs offer the lowest compute cost. Since the workload can tolerate interruptions, the eviction policy is acceptable. Serverless Consumption plans are ruled out due to execution timeouts.
This maximizes cost savings while avoiding execution failures due to timeout limits.

Key Concept

Selecting Azure compute solutions based on availability SLAs, workload interruption tolerance, and execution durations.
Estimated Time:2m 30s
Question 978Question

A financial technology company is designing a container-based background processing service on Azure. The service must retrieve and process transaction records from an Azure Service Bus queue. Each transaction record takes up to 1212 minutes to process.

The solution must meet the following requirements:
- Automatically scale down to zero instances when no messages are in the queue.
- Scale out dynamically based on the queue depth using Kubernetes Event-driven Autoscaling (KEDA).
- Support strict regulatory compliance requiring complete administrative and network isolation between production and development environments.
- Minimize administrative effort and operational overhead.

Which two configurations should you recommend as part of the architecture? (Select two.)

Select all that apply

Show answer & explanation

Answer: Azure Container Apps to host the background processing service; Separate Azure Container Apps environments, each connected to a dedicated Log Analytics workspace, for production and development

Answer

Deploy the background processing service on Azure Container Apps, and isolate production and development workloads by running them in separate Azure Container Apps environments configured with dedicated Log Analytics workspaces.
Deploying the workload to Azure Container Apps is correct because it is a serverless platform that supports containerized workloads, scales dynamically to zero, and integrates natively with KEDA out of the box, fulfilling all scaling and management requirements with minimal administrative overhead. Using separate environments, each with its own Log Analytics workspace, fulfills the compliance requirement by enforcing strict administrative and network isolation boundaries between production and development.

Step-by-Step Solution

1
Evaluate the hosting requirements for container workloads that scale to zero and leverage KEDA while minimizing administrative overhead.
Azure Container Apps is identified as the best fit because it provides serverless containers with native KEDA integration, avoiding the cluster management overhead of Azure Kubernetes Service (AKS).
This filters out AKS as it increases administrative effort, and highlights Azure Container Apps as the primary compute candidate.
2
Check the execution time constraints against the serverless hosting options.
Since processing a record can take up to 12 minutes, Azure Functions on a Consumption plan is ruled out because it enforces a maximum timeout of 10 minutes.
This prevents runtime failures caused by system-level execution timeout limits.
3
Determine the isolation configuration needed to meet regulatory compliance for separate environments.
Separate Azure Container Apps environments and separate Log Analytics workspaces must be deployed.
A single environment or shared workspace violates compliance requirements for absolute administrative and network boundary isolation.

Key Concept

Selecting the optimal Azure container hosting option (Azure Container Apps vs. AKS vs. Azure Functions) based on scaling mechanisms, execution timeouts, operational overhead, and compliance isolation boundaries.
Question 979Question

A healthcare provider is deploying a regional medical records synchronization service on virtual machines in a single Azure region. The service requires low-latency TCP communication on port 5000, does not require SSL/TLS termination, and does not require URL-based routing. To distribute traffic, the provider attempts to configure an Azure Standard Load Balancer. However, the deployment fails because the backend virtual machines are associated with Basic SKU public IP addresses.

Which action should you recommend to resolve the deployment failure while meeting all service requirements?

Show answer & explanation

Answer: Upgrade the public IP addresses of the virtual machines to the Standard SKU.

Answer

Upgrade the public IP addresses of the virtual machines to the Standard SKU.
Upgrading the public IP addresses of the virtual machines to the Standard SKU is the correct solution. Standard Load Balancer backend pools require Standard SKU IP addresses. This change satisfies the validation constraint while keeping the layer-4 TCP load balancing architecture intact to support the port 5000 service requirement.

Step-by-Step Solution

1
Identify the protocol and routing requirements of the service.
The service requires regional distribution of low-latency TCP traffic on port 5000 with no HTTP/S layer-7 routing or SSL/TLS termination.
This limits the suitable load balancers to Layer 4 solutions (Azure Load Balancer) and excludes Layer 7 options (Application Gateway, Front Door) and DNS-based routing (Traffic Manager).
2
Analyze the cause of the deployment failure.
Azure Standard Load Balancer is incompatible with Basic SKU public IP addresses on the backend virtual machines.
Azure resource rules mandate that all resources connected to a Standard Load Balancer must use the Standard SKU to ensure security and predictability.
3
Determine the resolution that maintains the required service architecture.
Upgrading the virtual machines' public IP addresses to the Standard SKU resolves the validation error.
This allows the Standard Load Balancer to successfully bind to the virtual machines while satisfying the TCP port 5000 and regional distribution requirements.

Key Concept

Azure Load Balancer SKU alignment and protocol routing constraints
Question 980Question

An enterprise is designing a disaster recovery and business continuity solution for a web application deployed across the East US and West US regions. The application consists of an HTTPS-based frontend and an Azure SQL Database backend.

The architecture must meet the following requirements:
- Automatically route client requests to the region with the lowest latency.
- Offload SSL/TLS decryption from the backend web servers to a centralized global entry point.
- Provide automatic failover for the database layer with a single connection string that automatically redirects write operations to the new primary server.
- Ensure that the primary web application can survive a regional outage with minimal manual intervention.

Which design should you recommend?

Show answer & explanation

Answer: Deploy Azure Front Door for global routing and SSL termination, and configure Azure SQL Database auto-failover groups.

Answer

Deploy Azure Front Door for global routing and SSL termination, and configure Azure SQL Database auto-failover groups.
The correct architecture uses Azure Front Door at the ingress layer to provide global Anycast routing, lowest-latency path optimization, and centralized SSL termination. For the data layer, it uses Azure SQL Database auto-failover groups to automate database failover and present a single read-write endpoint, eliminating the need to update database connection strings in the web app during a failover event.

Step-by-Step Solution

1
Analyze global routing and SSL termination requirements.
Identify that Azure Front Door is an Anycast-based routing service that operates at Layer 7, allowing it to perform centralized SSL/TLS termination and route HTTP/S requests with minimal failover latency. In contrast, Azure Traffic Manager works at the DNS level (Layer 4) and cannot decrypt or terminate SSL traffic.
This determines the correct ingress and routing service for HTTP-based workloads needing SSL offloading.
2
Analyze database HA/DR and listener requirements.
Select Azure SQL Database auto-failover groups because they provide a read-write listener endpoint (a single connection string) and automate the failover process to the secondary region. In contrast, active geo-replication requires manual initiation of failover and client-side connection string changes, while RA-GRS is a storage redundancy option that is read-only in the secondary region.
This satisfies the requirement for automatic database failover with a single connection string.
3
Synthesize the components into a single architecture.
Combine Azure Front Door and Azure SQL Database auto-failover groups to form a complete, automated end-to-end failover solution for the global application.
This guarantees that both front-end and back-end layers meet the high-availability and business continuity requirements.

Key Concept

Design Traffic Routing and Failover Strategies
PreviousPage 49 / 60Next
All practice questions — Microsoft Azure Solutions Architect (AZ-305) | Examkin