All practice questions

1198 questions

Question 981Question

You are designing a disaster recovery solution for a retail inventory system hosted on Azure virtual machines in the West US 2 region. The solution must replicate the workloads to the West Central US region.

The workload consists of the following virtual machines:
* VM-Web: Running web services with one OS disk (Premium SSD) experiencing a write churn of 2 MB/s2\text{ MB/s}.
* VM-Data: Running an inventory processing database with one OS disk (Premium SSD) experiencing a write churn of 3 MB/s3\text{ MB/s}, one database data disk (Premium SSD) experiencing a write churn of 14 MB/s14\text{ MB/s}, and one temporary cache disk (Premium SSD) experiencing a write churn of 22 MB/s22\text{ MB/s}.

You have a target Recovery Point Objective (RPO) of 4 hours4\text{ hours} and a Recovery Time Objective (RTO) of 1 hour1\text{ hour}.

Which two actions should you include in the disaster recovery design to ensure supportability and minimize replication costs? (Select two.)

Select all that apply

Show answer & explanation

Answer: Exclude the temporary cache disk from replication for VM-Data.; Select the High Churn replication policy tier for VM-Data.

Answer

To support VM-Data and minimize replication costs, you must exclude the temporary cache disk from replication and select the High Churn replication policy tier for VM-Data.
Excluding the temporary cache disk from replication reduces cost and removes the need to replicate transient data. Because the database data disk has a write churn of 14 MB/s14\text{ MB/s}, which exceeds the standard replication limit of 10 MB/s10\text{ MB/s} for Premium SSDs, configuring the High Churn replication policy tier is required to support replication of the remaining database data disk.

Step-by-Step Solution

1
Analyze the write churn for each disk on VM-Data.
The OS disk has a write churn of 3 MB/s3\text{ MB/s}, the database data disk has a write churn of 14 MB/s14\text{ MB/s}, and the temporary cache disk has a write churn of 22 MB/s22\text{ MB/s}.
Identifying the churn per disk allows comparison against Azure Site Recovery limits.
2
Identify cost optimization opportunities.
The temporary cache disk (22 MB/s22\text{ MB/s}) does not contain persistent data and should be excluded from replication.
Excluding temporary disks avoids unnecessary storage costs and replication traffic.
3
Select the correct replication tier for the remaining database data disk.
The remaining database disk has a write churn of 14 MB/s14\text{ MB/s}, which exceeds the standard limit of 10 MB/s10\text{ MB/s} for Premium SSDs but is supported under the High Churn replication policy tier (up to 54 MB/s54\text{ MB/s}).
Selecting the High Churn policy ensures replication stays healthy and supported.

Key Concept

Azure Site Recovery limits, disk exclusion, and High Churn replication policy tier configuration.
Question 982Question

You are designing a high-availability infrastructure for a multi-tier web application deployed across the East US and West US regions. The design must meet the following requirements:
- Route incoming client requests to the closest regional endpoint with low latency using Anycast routing.
- Terminate SSL/TLS sessions at the global routing layer.
- Within each region, distribute client requests to different backend pools based on the URL path (e.g., routing /api/* to an API tier and /web/* to a web tier).

Which two Azure services should you include in your traffic routing and failover design to meet these requirements?

Select all that apply

Show answer & explanation

Answer: Azure Front Door; Azure Application Gateway

Answer

Azure Front Door and Azure Application Gateway
Azure Front Door provides global Anycast-based routing and edge SSL termination, satisfying the requirement to handle global traffic at the edge. Azure Application Gateway operates regionally at Layer 7 and supports URL path-based routing, satisfying the requirement to distribute traffic to specific backend pools based on paths within each region. Together, they form a complete multi-tier routing architecture.

Step-by-Step Solution

1
Evaluate the requirement for global load balancing, low-latency Anycast routing, and SSL termination at the edge.
This requires a global Layer 7 load balancer. Azure Front Door meets these criteria.
Traffic Manager is DNS-based and cannot offload SSL, while regional load balancers cannot provide Anycast routing globally.
2
Evaluate the requirement for regional routing based on URL paths (such as /api/* and /web/*).
This requires a regional Layer 7 load balancer inside the VNets. Azure Application Gateway meets these criteria.
URL path-based routing requires application-layer (Layer 7) packet inspection, which is a native capability of Application Gateway.
3
Combine the services to form the end-to-end design.
Azure Front Door acts as the entry point for global clients and routes traffic to Azure Application Gateways in each region.
This tiering provides global routing and protection at the edge (Front Door) and fine-grained internal routing within VNets (Application Gateway).

Key Concept

Combining global and regional Layer 7 load balancing for optimal routing, SSL offloading, and path-based delivery.
Estimated Time:1m 30s
Question 983Question

An educational technology company is designing a system that automatically executes and grades programming assignments submitted by students.

The grading process has the following requirements:
* Each submission must run in an isolated, sandboxed container.
* The execution of a grading job takes between 2 and 15 minutes to complete.
* The system must dynamically scale the number of running containers based on the queue depth of an Azure Service Bus queue containing the submissions.
* To meet strict audit requirements for regional data sovereignty, student execution logs must be isolated within their respective geographic regions and not cross regional boundaries.
* The company wants to minimize the administrative effort required to manage infrastructure, container orchestration, and virtual machine nodes.

You need to design the compute and monitoring solution for the grading system.

Which solution should you recommend?

Show answer & explanation

Answer: Azure Container Apps jobs configured with event-driven scaling based on the Service Bus queue and separate Log Analytics workspaces in each region.

Answer

Azure Container Apps jobs configured with event-driven scaling based on the Service Bus queue and separate Log Analytics workspaces in each region.
The design utilizing Azure Container Apps jobs with separate regional Log Analytics workspaces is correct because Container Apps jobs run containerized tasks to completion, scale serverlessly based on event triggers (like Service Bus queue depth using KEDA) with zero virtual machine or cluster management overhead, and can handle execution times up to the container job configuration limit (which easily supports 15 minutes). Implementing separate regional Log Analytics workspaces ensures compliance with strict data sovereignty requirements by keeping student execution logs within their respective geographic regions.

Step-by-Step Solution

1
Evaluate the execution duration and scaling triggers for the workload.
The grading workload takes up to 15 minutes to run and needs to scale dynamically based on the message count of an Azure Service Bus queue.
This rules out Azure Functions on a Consumption plan, which is restricted to a maximum 10-minute timeout.
2
Compare container orchestration options against the administrative effort constraint.
Azure Container Apps jobs provide serverless execution of containerized tasks that run to completion with native KEDA queue-based scaling and no cluster management. Azure Kubernetes Service (AKS) requires node and cluster lifecycle management.
Choosing Azure Container Apps jobs satisfies the requirement to minimize infrastructure administration effort.
3
Evaluate logging configuration in relation to the regulatory audit requirements.
Separate regional Log Analytics workspaces keep execution logs isolated within their geographic boundaries, whereas a single central workspace aggregates data across regions.
Separate regional workspaces are required to satisfy the strict data sovereignty constraints.

Key Concept

Container-Based Workloads
Question 984Question

An enterprise is modernizing a regional database application that uses TCP port 1433 for replication. The application is hosted on a pool of Azure Virtual Machines within a single region. The design requires a regional load balancer to distribute the TCP traffic without needing SSL/TLS termination or application-layer (HTTP/HTTPS) routing. You plan to deploy an Azure Standard Load Balancer.

Which two configurations are required to ensure the virtual machines can be successfully associated with the backend pool of the Standard Load Balancer? (Choose two.)

Select all that apply

Show answer & explanation

Answer: Deploy the virtual machines using Standard SKU public IP addresses if public IPs are assigned.; Configure the virtual machines within the same virtual network as the Standard Load Balancer.

Answer

To associate virtual machines with the backend pool of an Azure Standard Load Balancer, the virtual machines must be configured to use Standard SKU public IP addresses (if public IPs are assigned) and must be located in the same virtual network as the Standard Load Balancer.
The correct configurations are deploying the virtual machines using Standard SKU public IP addresses and placing the virtual machines in the same virtual network as the load balancer. The Azure Standard Load Balancer has strict SKU matching rules: any public IP addresses assigned to the backend virtual machines must be of the Standard SKU. In addition, the virtual machines must exist in the same virtual network as the load balancer.

Step-by-Step Solution

1
Determine the load balancing layer and SKU requirement.
The scenario specifies a regional TCP application utilizing an Azure Standard Load Balancer.
This establishes that the backend pool configuration must adhere to the Standard Load Balancer's requirements.
2
Evaluate the IP configuration requirements for the backend pool.
Virtual machines connected to the Standard Load Balancer's backend pool must not use Basic SKU public IP addresses.
Azure enforces SKU matching, meaning Standard Load Balancers require Standard SKU public IPs for any backend virtual machines that possess public IPs.
3
Determine the network boundary requirements.
The virtual machines and the Standard Load Balancer must reside within the same virtual network boundary.
This is a network connectivity prerequisite for the backend pool of an Azure Standard Load Balancer.

Key Concept

Azure Standard Load Balancer SKU alignment and virtual network requirements
Question 985Question

You are designing the compute infrastructure for a high-frequency financial trading API gateway on Azure. The gateway will run on three virtual machines that must replicate state in memory. The replication protocol requires network latency between the virtual machines to be less than 1 millisecond. The business requires a minimum compute uptime SLA of 99.95% for the gateway. You need to design the compute deployment topology to meet both the availability and latency requirements. Which configuration should you recommend?

Show answer & explanation

Answer: Deploy the virtual machines in a single Availability Zone, associated with a single Proximity Placement Group, and distributed across multiple fault domains using a Virtual Machine Scale Set in Flexible orchestration mode.

Answer

Deploy the virtual machines in a single Availability Zone, associated with a single Proximity Placement Group, and distributed across multiple fault domains using a Virtual Machine Scale Set in Flexible orchestration mode.
The correct configuration deploys the virtual machines in a single Availability Zone, inside a Proximity Placement Group, and distributed across multiple fault domains using a Virtual Machine Scale Set in Flexible orchestration mode. This ensures that all VMs are co-located in the same datacenter to meet the sub-millisecond latency requirement, while still being separated across different physical racks to satisfy the 99.95% VM uptime SLA.

Step-by-Step Solution

1
Analyze the latency requirement (< 1 ms).
Determine that the virtual machines must be co-located within the same physical datacenter, which requires a Proximity Placement Group restricted to a single Availability Zone.
Deploying across multiple Availability Zones introduces inter-zone physical distance, causing latency to exceed the 1 millisecond threshold.
2
Analyze the uptime SLA requirement (99.95%).
Identify that the virtual machines must be distributed across different hardware racks (fault domains) within the selected Availability Zone.
An Availability Set or a Virtual Machine Scale Set in Flexible orchestration mode with a fault domain count greater than 1 provides the required 99.95% SLA for a multi-instance VM deployment.
3
Combine the placement and redundancy configurations.
Recommend deploying the VMs within a single Availability Zone, inside a Proximity Placement Group, and distributed across fault domains using a Virtual Machine Scale Set in Flexible orchestration mode.
This combination guarantees both sub-millisecond latency (via the single-zone PPG) and 99.95% availability (via fault domain isolation within that zone).

Key Concept

Balancing compute high availability SLAs with low-latency placement constraints in Azure using Proximity Placement Groups and Fault Domains.
Estimated Time:2m 30s
Question 986Question

A company is planning to migrate two containerized workloads to Azure:

* Workload 1: A workflow orchestrator engine that requires direct access to the Kubernetes API and uses custom resource definitions (CRDs) to manage external resources.
* Workload 2: A set of background processing microservices that process messages from Azure Service Bus queues and must scale to zero when no messages are present. The operations team wants to minimize cluster administration and infrastructure management effort for this workload.

Which two Azure container hosting services should you recommend?

Select all that apply

Show answer & explanation

Answer: Azure Container Apps; Azure Kubernetes Service (AKS)

Answer

Azure Kubernetes Service (AKS) and Azure Container Apps
Azure Kubernetes Service is correct for Workload 1 because it allows full control over the Kubernetes cluster, API, and the ability to register Custom Resource Definitions. Azure Container Apps is correct for Workload 2 because it abstract cluster management, drastically lowering administrative effort, and features built-in KEDA integration that supports scaling down to zero replicas based on queue depth.

Step-by-Step Solution

1
Analyze the requirements for Workload 1.
Workload 1 requires custom resource definitions (CRDs) and direct Kubernetes API access. This necessitates a hosting environment with access to the underlying control plane, which points to Azure Kubernetes Service.
Only Azure Kubernetes Service provides full access to the Kubernetes API and control plane to deploy CRDs and custom operators.
2
Analyze the requirements for Workload 2.
Workload 2 requires queue-based autoscaling (Service Bus) that scales to zero, while minimizing administrative overhead. This aligns with Azure Container Apps, which uses KEDA under the hood to scale workloads dynamically.
Azure Container Apps provides a managed, serverless platform that simplifies operational tasks like patching and upgrading while supporting KEDA natively.

Key Concept

Selecting Azure container hosting services based on control plane access needs and operational overhead requirements.
Question 987Question

An energy exploration company is designing the Azure compute virtualization infrastructure for a seismic modeling platform. The platform consists of two primary workloads:

* Database Engine: A stateful, steady-state data store containing sensitive telemetry data. It must run on physical hardware isolated at the host level to meet compliance requirements. It requires a high memory-to-vCPU ratio and must maintain an uptime SLA of 99.99%.
* Simulation Pipeline: A massive batch-oriented parallel simulation runner. The pipeline is stateless, highly fault-tolerant, can resume from checkpoints, and must run at the lowest possible cost.

Which two compute virtualization configurations should you recommend to meet these requirements? (Select two.)

Select all that apply

Show answer & explanation

Answer: Deploy the Database Engine on Azure Dedicated Hosts using Esv5-series virtual machines allocated across multiple Availability Zones.; Deploy the Simulation Pipeline on Azure Spot Virtual Machines using Dsv5-series instances.

Answer

Deploy the Database Engine on Azure Dedicated Hosts using Esv5-series virtual machines allocated across multiple Availability Zones, and deploy the Simulation Pipeline on Azure Spot Virtual Machines using Dsv5-series instances.
Deploying the Database Engine on Azure Dedicated Hosts with Esv5-series VMs across multiple Availability Zones guarantees host-level isolation, provides the required memory-to-vCPU ratio, and satisfies the 99.99% availability SLA. Deploying the Simulation Pipeline on Azure Spot VMs using Dsv5-series instances satisfies the requirement for the lowest cost compute, since the workload is stateless and capable of handling capacity eviction.

Step-by-Step Solution

1
Analyze host isolation and memory requirements for the database workload.
Azure Dedicated Hosts are required to meet physical host isolation. E-series (such as Esv5) virtual machines must be used because they are memory-optimized.
This satisfies both the compliance requirement for hardware isolation and the technical requirement for a high memory-to-vCPU ratio.
2
Determine the high availability layout for the database engine to meet the SLA.
Distribute the Azure Dedicated Hosts across multiple Availability Zones.
Deploying dedicated hosts across multiple zones guarantees a 99.99% uptime SLA for the virtual machines running on those hosts.
3
Analyze the workload characteristics and cost requirements of the simulation pipeline.
Recommend Azure Spot VMs (e.g., using general-purpose Dsv5-series instances) for the Simulation Pipeline.
Since the simulation pipeline is stateless, fault-tolerant, and must run at the lowest possible cost, Spot VMs provide the optimal cost-saving mechanism despite their eviction model.

Key Concept

Selecting and configuring Azure compute virtualization components (Dedicated Hosts, Spot VMs, and VM series) to meet physical isolation, high availability SLA, hardware-profile, and cost constraints.
Question 988Question

A healthtech platform is designing an Azure architecture to ingest and analyze genomic sequencing datasets. The solution must support the following workloads:

* Workload A: An API endpoint that receives webhook notifications from external partners. The workload must scale dynamically from zero to handle high bursts of traffic, support custom domain names, and connect securely to an Azure SQL Database using virtual network integration.

* Workload B: A CPU-intensive file processing application packaged as a container image. Each processing run takes between 20 to 45 minutes depending on the file size. The compute resource must scale to zero when no files are available for processing, and it must minimize administrative overhead.

Which two Azure hosting services should you include in the design to meet these requirements?

Select all that apply

Show answer & explanation

Answer: Azure Functions on a Flex Consumption plan for Workload A; Azure Container Apps Jobs for Workload B

Answer

The hosting services that should be included are Azure Functions on a Flex Consumption plan for Workload A, and Azure Container Apps Jobs for Workload B.
Azure Functions on a Flex Consumption plan is correct for Workload A because it supports fast scaling, virtual network integration, and low cold starts. Azure Container Apps Jobs is correct for Workload B because it is designed for containerized, run-to-completion execution paths that run for hours (bypassing function timeout limits) and scale to zero when not active, without the overhead of AKS.

Step-by-Step Solution

1
Analyze the scaling, networking, and security requirements for Workload A.
Workload A needs to scale dynamically from zero to handle bursts, support custom domains, and connect securely to Azure SQL Database using virtual network integration.
Virtual network integration is a key security requirement for accessing the database privately.
2
Evaluate hosting options for Workload A.
The standard Consumption plan for Azure Functions does not support virtual network integration. Flex Consumption supports both scale-to-zero and virtual network integration, satisfying all criteria for Workload A.
Choosing Flex Consumption meets the requirement of serverless scaling and private networking.
3
Analyze the execution duration, packaging, and management requirements for Workload B.
Workload B runs as a containerized application, takes between 20 and 45 minutes, must scale to zero when idle, and must minimize administrative overhead.
The 45-minute duration is a strict constraint that rules out standard serverless function timeouts.
4
Evaluate hosting options for Workload B.
Azure Functions on Consumption (10 minutes) and Elastic Premium (30 minutes) plans will timeout. Azure Kubernetes Service (AKS) supports the execution but violates the low administrative overhead constraint. Azure Container Apps Jobs supports run-to-completion containers, executes up to 24 hours, scales to zero, and has minimal administrative overhead.
Selecting Azure Container Apps Jobs provides the correct execution environment without exceeding timeout limits or adding excessive operational overhead.

Key Concept

Selecting serverless and container hosting solutions in Azure based on execution timeouts, networking needs, and operational overhead.
Question 989Question

A smart utilities company is designing a production telemetry processing system on Azure. The system will ingest continuous data streams from regional water meters and place them in an Azure Service Bus queue. A containerized backend application will retrieve the messages and perform complex data analysis.

The system must meet the following requirements:
* Scale container instances dynamically based on the queue length using Kubernetes Event-driven Autoscaling (KEDA).
* Support execution times of up to 25 minutes per data analysis task.
* Maintain continuous availability for this critical workload without risk of unexpected eviction.
* Minimize administrative and operational infrastructure overhead.

Which compute solution should you recommend?

Show answer & explanation

Answer: Azure Container Apps

Answer

Azure Container Apps
Azure Container Apps is the ideal solution because it is a serverless container platform that natively supports Kubernetes Event-driven Autoscaling (KEDA) out of the box, allowing container instances to scale dynamically based on the queue length. It minimizes administrative and operational overhead by removing the need to manage nodes, control planes, or cluster upgrades. It also supports long-running execution times beyond 10 minutes and provides stable, continuous availability suitable for production workloads without the eviction risks associated with Spot VM priority.

Step-by-Step Solution

1
Analyze the scaling and infrastructure management requirements.
Identify that the solution must scale based on queue length using KEDA and minimize operational overhead.
This narrows the candidate services to managed container platforms that support event-driven scaling via KEDA.
2
Evaluate the execution timeout constraint against serverless options.
Determine that Azure Functions on a Consumption plan is ruled out due to its 10-minute maximum timeout since tasks can take up to 25 minutes.
Ensures the selected service can support long-running tasks without interruption.
3
Assess availability requirements and SLA constraints.
Rule out Azure Spot Virtual Machines because they do not guarantee continuous availability and are subject to eviction.
Ensures the workload is hosted on stable compute resources appropriate for production workloads.
4
Select the compute service that minimizes administrative overhead while meeting all technical requirements.
Azure Container Apps is selected over Azure Kubernetes Service (AKS) because AKS introduces excessive management overhead.
Aligns with Microsoft best practices for serverless container workloads when custom Kubernetes API access is not required.

Key Concept

Selecting container-based hosting solutions based on operational overhead, scaling, and execution duration
Estimated Time:1m 30s
Question 990Question

A healthcare provider is designing the Azure compute virtualization infrastructure for a clinical trial analysis application that processes sensitive patient data. The solution must satisfy the following requirements:

* Confidentiality: The patient data must be encrypted in memory during processing to prevent access by hypervisor administrators or other tenants.
* Resilience: The application virtual machines must be distributed across multiple physical hardware racks (fault domains) within an Azure region to guarantee high availability without allocating dedicated physical servers.
* Availability: The compute tier must support a 99.95%99.95\% availability SLA.
* Storage: The application requires high-performance disk storage supporting at least 5,000 IOPS5,000\text{ IOPS} per virtual machine instance for transaction logging.
* Licensing Costs: The solution must leverage existing Windows Server licenses to minimize operational expenses.

Which of the following compute virtualization designs should you recommend?

Show answer & explanation

Answer: Deploy a Virtual Machine Scale Set in Flexible orchestration mode using DCasv5-series confidential virtual machines with Premium SSD disks, and enable Azure Hybrid Benefit.

Answer

Deploy a Virtual Machine Scale Set in Flexible orchestration mode using DCasv5-series confidential virtual machines with Premium SSD disks, and enable Azure Hybrid Benefit.
The correct design uses a Virtual Machine Scale Set in Flexible orchestration mode with DCasv5-series confidential VMs and Premium SSD disks. The DCasv5-series virtual machines provide hardware-based memory encryption using AMD SEV-SNP to meet the confidentiality requirement. Flexible orchestration mode allows distributing virtual machines across multiple physical fault domains to ensure high availability without the overhead of renting dedicated physical hardware. Premium SSDs satisfy the storage requirement of 5,000 IOPS5,000\text{ IOPS} for transaction logging, and Azure Hybrid Benefit allows the reuse of existing Windows Server licenses to minimize operational costs.

Step-by-Step Solution

1
Evaluate the confidentiality and licensing requirements to select the appropriate virtual machine configuration.
Select DCasv5-series confidential virtual machines and enable Azure Hybrid Benefit.
DCasv5-series VMs utilize AMD SEV-SNP to provide hardware-based memory encryption. Azure Hybrid Benefit allows the customer to reuse existing Windows Server licenses to minimize compute costs.
2
Determine the scale-out compute structure and resilience requirements.
Choose a Virtual Machine Scale Set (VMSS) in Flexible orchestration mode.
Flexible orchestration mode allows spreading VMs across fault domains without dedicated physical hardware, providing a 99.95%99.95\% SLA for individual VM instances, which meets the resilience and availability targets.
3
Evaluate the disk performance parameters.
Select Premium SSD storage.
Premium SSDs support the required 5,000 IOPS5,000\text{ IOPS} target with low latency, unlike Standard HDDs which fail to meet the performance threshold.

Key Concept

Designing secure, high-availability virtualized workloads on Azure using Virtual Machine Scale Sets in Flexible orchestration mode and Confidential VMs (DCasv5-series).
Question 991Question

An enterprise is designing a hub-and-spoke virtual network topology in Azure. The transit hub virtual network, `vnet-hub-transit` (172.16.0.0/16172.16.0.0/16), contains a firewall subnet, `AzureFirewallSubnet` (172.16.0.0/24172.16.0.0/24), hosting an Azure Firewall with a private IP address of 172.16.0.4172.16.0.4. The application virtual network, `vnet-spoke-app` (172.17.0.0/16172.17.0.0/16), is peered with `vnet-hub-transit` and contains two subnets: `snet-web` (172.17.1.0/24172.17.1.0/24) and `snet-biz` (172.17.2.0/24172.17.2.0/24). Another virtual network, `vnet-spoke-db` (172.18.0.0/16172.18.0.0/16), contains the database tier and is also peered with `vnet-hub-transit`.

You need to configure a route table associated with `snet-web`. The routing configuration must meet the following requirements:
- Route all outbound internet traffic from `snet-web` through the Azure Firewall.
- Route all database-bound traffic from `snet-web` to `vnet-spoke-db` through the Azure Firewall.
- Ensure that VMs within `snet-web` can communicate directly with VMs in `snet-biz` without routing traffic through the firewall.

Which route configuration should you apply to the route table associated with `snet-web`?

Show answer & explanation

Answer: A route for 0.0.0.0/00.0.0.0/0 pointing to the virtual appliance at 172.16.0.4172.16.0.4, and a route for 172.18.0.0/16172.18.0.0/16 pointing to the virtual appliance at 172.16.0.4172.16.0.4.

Answer

Configure a route for 0.0.0.0/00.0.0.0/0 pointing to the virtual appliance at 172.16.0.4172.16.0.4, and a route for 172.18.0.0/16172.18.0.0/16 pointing to the virtual appliance at 172.16.0.4172.16.0.4.
The correct configuration applies two specific User Defined Routes (UDRs) to the route table for the web subnet. The first route (0.0.0.0/00.0.0.0/0 to 172.16.0.4172.16.0.4) handles all default egress to the internet. The second route (172.18.0.0/16172.18.0.0/16 to 172.16.0.4172.16.0.4) targets the peered database network. Because no user-defined route is configured for the local virtual network range (172.17.0.0/16172.17.0.0/16), the default local system route remains active. This allows traffic between the web and business subnets to route directly without traversing the firewall, satisfying all requirements.

Step-by-Step Solution

1
Identify the destinations that require transit through the Azure Firewall.
Internet traffic corresponds to prefix 0.0.0.0/00.0.0.0/0. Traffic to the database virtual network corresponds to prefix 172.18.0.0/16172.18.0.0/16. Both require a next hop of the virtual appliance IP 172.16.0.4172.16.0.4.
This establishes the necessary forwarding rules to send the external traffic to the firewall.
2
Analyze how local subnet-to-subnet traffic within the application virtual network is routed.
By default, Azure creates a system route for the local virtual network prefix (172.17.0.0/16172.17.0.0/16 -> Local) which allows subnets like `snet-web` and `snet-biz` to communicate directly.
Understanding default system routes helps determine if any user-defined routes will interfere with them.
3
Evaluate user-defined routes to ensure they do not overlap with and override the local system route.
The configured routes (0.0.0.0/00.0.0.0/0 and 172.18.0.0/16172.18.0.0/16) do not overlap with the local 172.17.0.0/16172.17.0.0/16 address space. Therefore, local communication between `snet-web` and `snet-biz` remains direct and does not go to the firewall.
Ensures the design meets the requirement to keep local traffic direct and avoid firewall overhead.

Key Concept

Azure route selection behavior, User Defined Routes (UDR) override precedence, and Longest Prefix Match (LPM) logic for local virtual network traffic.
Estimated Time:1m 30s
Question 992Question

An enterprise is designing a data lifecycle management policy for a General-purpose v2 (GPv2) Azure Blob storage account that stores daily transactional logs. The storage strategy must meet the following requirements:
- Logs are frequently accessed and modified during the first 3030 days after creation.
- Between 3131 and 9090 days, logs are accessed occasionally but must remain available for immediate, sub-second retrieval.
- After 9090 days, logs are rarely accessed, and a retrieval latency of up to 1515 hours is acceptable.
- Logs must be retained for a total of 365365 days and then deleted to minimize costs.
- The lifecycle policy must minimize costs without violating any access or latency requirements.

Which two actions should you configure in the lifecycle management policy? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Transition blobs to the cool tier 3030 days after creation.; Transition blobs to the archive tier 9090 days after creation.

Answer

To meet the requirements, the lifecycle policy must transition the blobs to the cool tier 3030 days after creation, and transition the blobs to the archive tier 9090 days after creation.
The correct lifecycle policy actions are transitioning blobs to the cool tier after 3030 days and transitioning blobs to the archive tier after 9090 days. Transitioning to the cool tier at day 3030 optimizes costs when the data is no longer accessed frequently, but still allows immediate sub-second access for the next 6060 days. Transitioning to the archive tier at day 9090 is optimal because the data is rarely accessed, and the 1515-hour rehydration latency matches the enterprise's allowed retrieval time. Since the blobs stay in the archive tier for 275275 days (from day 9090 to day 365365), they exceed the 180180-day minimum archive storage duration, avoiding any early deletion penalties.

Step-by-Step Solution

1
Analyze access patterns and latency requirements for the first phase (00-9090 days).
Identify that data must be in the Hot tier for the first 3030 days to support frequent access, and must transition to the Cool tier at 3030 days to support occasional access with sub-second retrieval latency until day 9090.
Data in the Archive tier cannot be retrieved in sub-seconds, so transitioning to Archive at day 3030 is ruled out.
2
Analyze access patterns, latency requirements, and minimum retention constraints for the second phase (9090-365365 days).
Identify that data can transition to the Archive tier at day 9090 because it is rarely accessed and the 1515-hour rehydration latency is acceptable. The data will remain in the Archive tier for 275275 days before deletion at day 365365.
Transitioning to Archive at day 9090 satisfies the 180180-day minimum retention threshold for the Archive tier, avoiding early deletion penalties. Transitioning at day 300300 would violate this threshold.

Key Concept

Azure Storage lifecycle management allows automating transitions between Hot, Cool, and Archive tiers based on file age to optimize costs while respecting latency and retrieval constraints, including minimum retention periods.
Estimated Time:2m 0s
Question 993Question

A company hosts a global web application across the North Europe and East US regions. During testing of a disaster recovery scenario, the team notices that when they simulate a regional outage, some external clients continue to send traffic to the failed region for several minutes. Investigation reveals that these clients ignore the low Time-to-Live (TTL) settings on DNS records. The company wants to migrate to a global routing solution that eliminates reliance on client-side DNS caching and provides SSL termination at the edge. Which Azure service should you recommend to meet these requirements?

Show answer & explanation

Answer: Azure Front Door

Answer

Azure Front Door
Azure Front Door uses Anycast routing to advertise a single virtual IP address globally. When a regional backend fails, Front Door updates its internal routing path and directs subsequent requests to the healthy region over the Microsoft backbone. The client's connection point remains the same, eliminating failover latency introduced by client-side DNS caching. It also natively supports SSL termination.

Step-by-Step Solution

1
Identify the primary root cause of the failover delay, which is client-side DNS caching behavior that ignores TTL settings.
This rules out DNS-based traffic routing solutions such as Azure Traffic Manager.
DNS-based solutions rely on the client resolving DNS records to find new endpoints, which fails if the client caches the previous endpoint IP.
2
Evaluate the remaining global and regional routing options against the need for global routing and SSL termination.
This rules out regional solutions like Azure Application Gateway and Layer 4 solutions like Azure Load Balancer.
Application Gateway cannot route between multiple regions natively, and Load Balancer cannot perform SSL termination at the edge.
3
Select the service that utilizes Anycast-based routing and operates at Layer 7.
Azure Front Door is chosen.
Azure Front Door uses Anycast routing to handle client connections at the nearest edge PoP and routes traffic across the Microsoft network, avoiding client DNS updates during a backend failover.

Key Concept

Contrasting Anycast-based routing (Azure Front Door) with DNS-based routing (Azure Traffic Manager) for global failover scenario designs.

Alternative Method

Alternatively, you could combine Azure Traffic Manager with regional Azure Application Gateways to achieve path-based routing, but this would still suffer from client-side DNS caching delays during failover, failing the primary requirement.
Estimated Time:1m 30s
Question 994Question

A financial services company stores customer transaction logs in a General-purpose v2 (GPv2) storage account. The logs must be managed according to the following requirements:

* Logs are frequently accessed and analyzed for the first 30 days after creation.
* From day 31 to day 180, logs are rarely accessed but must be available for immediate, real-time security audits with sub-second retrieval times.
* After 180 days, logs must be retained for 5 years to meet regulatory compliance. A retrieval latency of up to 15 hours is acceptable during this period.
* Storage costs must be minimized.

Which lifecycle management policy should you recommend?

Show answer & explanation

Answer: Transition blobs to cool storage after 30 days, transition blobs to archive storage after 180 days, and delete blobs after 1825 days.

Answer

Transition blobs to cool storage after 30 days, transition blobs to archive storage after 180 days, and delete blobs after 1825 days.
The optimal policy transitions logs to cool storage after 30 days, which lowers costs while ensuring the data remains online and accessible with sub-second latency for security audits. After 180 days, the logs transition to archive storage to minimize long-term retention costs, as the allowed 15-hour retrieval latency aligns with standard Archive rehydration times. Finally, deleting the blobs after 5 years (1825 days) satisfies the regulatory requirement without incurring extra costs.

Step-by-Step Solution

1
Identify the storage requirements for the initial 30 days.
Logs are frequently accessed during this period, requiring them to remain in the Hot storage tier.
Hot storage is optimized for active and frequent read/write access.
2
Determine the optimal storage tier for logs between days 31 and 180.
Transition the logs to the Cool storage tier after 30 days.
The logs are rarely accessed but require immediate, sub-second retrieval times for security audits. The Cool tier meets this latency requirement at a lower storage cost than Hot, whereas the Archive tier introduces hours of latency due to rehydration.
3
Determine the optimal storage tier for logs after 180 days.
Transition the logs to the Archive storage tier after 180 days.
After 180 days, a retrieval latency of up to 15 hours is acceptable. The Archive tier offers the lowest storage costs for long-term retention and accommodates this latency.
4
Identify the cleanup action after the retention period of 5 years (1825 days).
Delete the blobs after 1825 days.
Regulatory compliance only requires retention for 5 years, so deleting the logs after this period avoids unnecessary storage charges.

Key Concept

Azure Storage lifecycle management allows you to automate the transition of blobs to cooler storage tiers or delete them based on their age to optimize costs while satisfying application latency and retention requirements.
Estimated Time:1m 30s
Question 995Question

An administrator is configuring a high-availability backend pool for a Standard SKU Azure Load Balancer. The backend pool contains several Azure Virtual Machines, but each virtual machine currently has a Basic SKU public IP address associated with its network interface. During deployment, the administrator encounters a validation failure. Which of the following configuration changes can resolve this validation mismatch? (Select two.)

Select all that apply

Show answer & explanation

Answer: Upgrade the public IP addresses of the virtual machines to the Standard SKU.; Remove the Basic SKU public IP addresses from the network interfaces of the virtual machines.

Answer

To resolve the validation failure, you must either upgrade the virtual machines' public IP addresses to the Standard SKU or remove the Basic SKU public IP addresses from their network interfaces entirely.
The Standard Azure Load Balancer requires that all virtual machines in its backend pool use Standard SKU public IP addresses or have no public IP addresses assigned at all. Therefore, upgrading the virtual machines' public IPs to the Standard SKU or removing the Basic SKU public IPs entirely satisfies the SKU alignment constraints and resolves the validation failure.

Step-by-Step Solution

1
Identify the cause of the validation failure
The failure is due to a SKU mismatch between the Standard Load Balancer and the Basic SKU public IPs attached to the backend virtual machines.
Standard Azure Load Balancer backend pools require all member virtual machines to use either Standard SKU public IPs or no public IPs at all.
2
Determine valid resolution methods that maintain the Standard Load Balancer
We can either upgrade the public IPs to the Standard SKU to match the load balancer, or disassociate the Basic public IPs from the virtual machines.
These actions satisfy the Standard SKU constraints of the Azure Load Balancer.

Key Concept

Azure Load Balancer SKU alignment constraints
Question 996Question

An organization is designing a disaster recovery (DR) solution from the East US region (primary) to the West US region (secondary) for a multi-tier application. The solution must achieve a Recovery Point Objective (RPO) of under 4 hours4\text{ hours} and a Recovery Time Objective (RTO) of under 2 hours2\text{ hours} for all workloads. The application consists of the following virtual machines (VMs):

1. AppVM1 (Application Tier):
- Disk 1 (OS, Premium SSD): 5 MB/s5\text{ MB/s} average write churn
- Disk 2 (Data, Premium SSD): 25 MB/s25\text{ MB/s} average write churn
- Total VM write churn: 30 MB/s30\text{ MB/s}

2. DBVM1 (Database Tier running SQL Server):
- Disk 1 (OS, Premium SSD): 10 MB/s10\text{ MB/s} average write churn
- Disk 2 (Data, Premium SSD): 65 MB/s65\text{ MB/s} average write churn
- Disk 3 (Logs, Premium SSD): 45 MB/s45\text{ MB/s} average write churn
- Total VM write churn: 120 MB/s120\text{ MB/s}

Which two configurations should you include in the disaster recovery design to meet the requirements while staying within supported limits?

Select all that apply

Show answer & explanation

Answer: Replicate AppVM1 to the secondary region using Azure Site Recovery with High Churn replication enabled.; Configure a SQL Server Always On Availability Group with an asynchronous replica on a VM in the secondary region for the databases on DBVM1.

Answer

Replicate AppVM1 using Azure Site Recovery with High Churn replication enabled, and configure a SQL Server Always On Availability Group with an asynchronous replica in the secondary region for DBVM1.
For AppVM1, the data disk's write churn of 25 MB/s25\text{ MB/s} requires the configuration of Azure Site Recovery's High Churn replication tier since it exceeds the standard limit of 20 MB/s20\text{ MB/s} per disk. For DBVM1, the combined disk write churn of 120 MB/s120\text{ MB/s} is above the maximum capacity threshold of 100 MB/s100\text{ MB/s} for Azure Site Recovery (even with High Churn enabled). Therefore, a database-level replication method such as SQL Server Always On Availability Groups must be utilized for DBVM1 to achieve the designated objectives.

Step-by-Step Solution

1
Analyze the write churn for AppVM1.
AppVM1 has one disk at 25 MB/s25\text{ MB/s} write churn and a total VM churn of 30 MB/s30\text{ MB/s}.
This exceeds the standard 20 MB/s20\text{ MB/s} per-disk limit for Premium SSDs but is within the 100 MB/s100\text{ MB/s} per-disk and per-VM limits supported by the High Churn replication tier in Azure Site Recovery.
2
Analyze the write churn for DBVM1.
DBVM1 has a total VM write churn of 10 MB/s+65 MB/s+45 MB/s=120 MB/s10\text{ MB/s} + 65\text{ MB/s} + 45\text{ MB/s} = 120\text{ MB/s}.
Because the total VM write churn (120 MB/s120\text{ MB/s}) exceeds the absolute ASR support threshold of 100 MB/s100\text{ MB/s} per VM, replication via ASR is not viable. An alternative application-level replication method is required.
3
Select the appropriate alternative replication for the database VM.
Deploy an asynchronous replica using SQL Server Always On Availability Groups on a database VM in the target region.
This offloads database replication to the native application level, bypassing virtual machine-level replication limits and successfully meeting the database RPO/RTO objectives.

Key Concept

Determining Azure Site Recovery limits and matching workloads to ASR replication tiers versus native application replication.
Question 997Question

A financial services company uses a General-purpose v2 (GPv2) storage account to store transactional record files. The files are frequently accessed during the first 30 days after creation to process active client requests. Between day 31 and day 365, the records are rarely accessed but must remain online to support regulatory compliance audits that require a retrieval latency of less than one second. After one year (365 days), the records must be permanently deleted. Which lifecycle management policy rule configuration meets these requirements while minimizing storage costs?

Show answer & explanation

Answer: Transition the blobs to the Cool tier 30 days after creation, and delete the blobs 365 days after creation.

Answer

Transition the blobs to the Cool tier 30 days after creation, and delete the blobs 365 days after creation.
Transitioning the blobs to the Cool tier 30 days after creation and deleting them after 365 days satisfies all constraints. The Cool tier offers lower storage costs than the Hot tier while keeping the data online and accessible within milliseconds, ensuring compliance audits requiring sub-second latency are successful. Deletion at day 365 aligns with the retention rules.

Step-by-Step Solution

1
Analyze the access pattern and latency requirement during the first 30 days.
The files are frequently accessed and require fast retrieval, meaning they must start in the Hot tier.
The Hot tier is optimized for active use and avoids access charges associated with cooler tiers.
2
Determine the optimal tier for the audit period from day 31 to day 365.
The data must remain online with sub-second retrieval latency, which points to the Cool tier.
The Archive tier is offline and takes hours to rehydrate, failing the latency constraint. Cool tier offers immediate access at lower storage costs.
3
Apply the cleanup rule at the end of the compliance cycle.
Configure deletion 365 days after blob creation.
This matches the requirement to permanently delete records after one year, minimizing ongoing storage costs.

Key Concept

Azure Blob Storage lifecycle management policies automate tier transitions and deletion. While Hot and Cool tiers are online and offer sub-second retrieval times, the Archive tier is offline and requires a rehydration process that takes several hours. Therefore, data with low-latency access requirements must not be transitioned to the Archive tier.
Estimated Time:1m 30s
Question 998Question

A digital marketing agency is designing the compute infrastructure for a new campaign analytics platform. The platform must support two distinct workloads:

1. **Workload 11**: A public-facing REST API that collects clickstream events from active marketing campaigns. The API is containerized, requires outbound virtual network (VNet) integration to access an Azure SQL Database via private endpoints, and experiences highly unpredictable demand, scaling down to 00 instances during off-peak hours to eliminate idle costs. Minimal infrastructure management is a key priority.
2. **Workload 22**: A data processing worker that aggregates campaign metrics daily. The worker is packaged as a container, runs as a single batch job that executes for approximately 4040 minutes, and requires access to local scratch disk storage for temporary data processing.

Which compute hosting architecture should you recommend to meet these requirements?

Show answer & explanation

Answer: Azure Container Apps for Workload 11, and Azure Container Apps Jobs for Workload 22.

Answer

Azure Container Apps for Workload 11, and Azure Container Apps Jobs for Workload 22
The compute architecture recommending Azure Container Apps for Workload 11 and Azure Container Apps Jobs for Workload 22 is correct because Azure Container Apps provides a serverless platform that supports scaling to 00 instances, VNet integration, and minimum administrative overhead. Azure Container Apps Jobs is purpose-built for run-to-completion, long-running (up to several hours) containerized execution, fully accommodating the 4040-minute duration of the daily aggregation job.

Step-by-Step Solution

1
Analyze the scaling and cost constraints of Workload 11.
Workload 11 requires containerized hosting, outbound VNet integration, minimal management overhead, and must scale to 00 instances during idle periods to avoid costs.
This rules out Azure App Service Premium v 33 because it does not scale to zero cost, and rules out Azure Kubernetes Service (AKS) due to high administrative overhead.
2
Analyze the execution duration and environment constraints of Workload 22.
Workload 22 runs as a single batch container for 4040 minutes and requires scratch disk space.
This rules out Azure Functions on a Consumption plan because its maximum execution duration is restricted to 1010 minutes.
3
Identify the service combinations that satisfy both workloads.
Azure Container Apps (ACA) satisfies Workload 11's requirements. Azure Container Apps Jobs (ACA Jobs) supports long-running (up to several hours) containerized batch execution and local storage, satisfying Workload 22.
Combining ACA and ACA Jobs delivers a fully serverless, containerized solution with minimal management overhead, VNet support, and scale-to-zero capabilities for both components.

Key Concept

Selecting optimal serverless and web hosting architectures in Azure based on execution timeouts, scaling constraints, and operational overhead.
Estimated Time:2m 0s
Question 999Question

An enterprise is designing a data storage solution for a medical genomics platform. Raw DNA sequencing files are uploaded to an Azure Blob Storage account configured with the Hot access tier.

* The sequencing files are processed by an analysis application immediately upon upload. The analysis requires sub-second retrieval latency and is guaranteed to complete within 7 days of upload.
* Once analyzed, the raw files are rarely accessed but must be retained for 365 days to meet regulatory compliance requirements.
* During the compliance retention period, a retrieval latency of up to 15 hours is acceptable.

You need to design a cost-effective data lifecycle management policy for the storage account.

Which two actions should you include in the lifecycle management policy?

Select all that apply

Show answer & explanation

Answer: Transition the blobs to the Archive tier 7 days after blob creation; Delete the blobs 365 days after blob creation

Answer

To meet the requirements at the lowest cost, you should configure the lifecycle policy to transition the blobs to the Archive tier 7 days after blob creation, and delete the blobs 365 days after blob creation.
Transitioning the blobs to the Archive tier 7 days after creation ensures the analysis application can access the files from the Hot tier with sub-second latency during the first 7 days, while minimizing costs for the remaining retention period. Deleting the blobs 365 days after creation satisfies the regulatory retention period and stops further storage costs.

Step-by-Step Solution

1
Identify the latency and access requirements for the initial processing phase.
The files require sub-second latency for up to 7 days, meaning they must remain in the Hot tier for at least 7 days.
Accessing files from the Archive tier is not possible without rehydration, which takes hours and violates the sub-second latency constraint.
2
Determine the optimal tier for the retention phase.
The Archive tier is selected because the data is rarely accessed, must be kept for 365 days (which exceeds the Archive tier's 180-day minimum retention period), and can tolerate retrieval times up to 15 hours.
Transitioning to the Archive tier 7 days after creation minimizes storage costs while complying with the 15-hour retrieval limit.
3
Identify the end-of-lifecycle requirements.
The blobs must be deleted 365 days after creation.
This satisfies the 365-day regulatory retention period and prevents ongoing storage charges after the requirement expires.

Key Concept

Azure Blob Storage lifecycle management allows automating transitions between Hot, Cool, and Archive tiers, as well as expiration/deletion, based on the age of the blob. Designing these rules requires balancing access latency requirements against storage costs and minimum retention periods.
Question 1000Question

An organization is designing a hub-and-spoke virtual network topology in Azure. The hub virtual network, `vnet-neure-hub-01` (10.240.0.0/1610.240.0.0/16), contains an Azure Route Server in the `RouteServerSubnet` (10.240.2.0/2410.240.2.0/24) and a pair of Network Virtual Appliances (NVAs) in `snet-nva` (10.240.1.0/2410.240.1.0/24) that establish BGP sessions with the Route Server. The NVAs advertise on-premises network routes (192.168.0.0/16192.168.0.0/16). You peer a spoke virtual network named `vnet-neure-spoke-app` (10.241.0.0/2410.241.0.0/24) with `vnet-neure-hub-01`. You must ensure that virtual machines in `vnet-neure-spoke-app` can dynamically learn the routes advertised by the NVAs via Azure Route Server, without using User-Defined Routes (UDRs). Which two configurations should you implement?

Select all that apply

Show answer & explanation

Answer: Configure the peering from `vnet-neure-spoke-app` to `vnet-neure-hub-01` to use the remote virtual network's gateway or Route Server.; Configure the peering from `vnet-neure-hub-01` to `vnet-neure-spoke-app` to use this virtual network's gateway or Route Server.

Answer

Configure the peering from `vnet-neure-spoke-app` to `vnet-neure-hub-01` to use the remote virtual network's gateway or Route Server, and configure the peering from `vnet-neure-hub-01` to `vnet-neure-spoke-app` to use this virtual network's gateway or Route Server.
The correct configurations involve enabling gateway and Route Server transit on both ends of the Virtual Network Peering. Specifically, you must configure the peering from the spoke VNet to the hub VNet to use the remote virtual network's gateway or Route Server, and configure the peering from the hub VNet to the spoke VNet to use this virtual network's gateway or Route Server. These settings allow the routing table of the spoke VNet to be dynamically updated with the BGP routes exchanged between the Route Server and the NVAs.

Step-by-Step Solution

1
Analyze Azure Route Server routing requirements for spoke virtual networks.
Identify that spoke VNets peered with a hub VNet containing Azure Route Server do not automatically receive advertised BGP routes unless transit peering settings are enabled.
By default, Route Server does not propagate learned routes to spoke virtual networks unless transit routing settings are configured on the virtual network peering.
2
Configure the spoke-to-hub peering properties.
Enable 'Use the remote virtual network's gateway or Route Server' on the peering configuration from the spoke VNet to the hub VNet.
This allows the spoke VNet to consume the routing services provided by the Azure Route Server located in the peered hub VNet.
3
Configure the hub-to-spoke peering properties.
Enable 'Use this virtual network's gateway or Route Server' on the peering configuration from the hub VNet to the spoke VNet.
This grants permission for the hub VNet to propagate its gateway and Route Server routes to the peered spoke VNet.

Key Concept

Azure Route Server facilitates dynamic route exchange between NVAs and virtual networks using BGP. To allow peered spoke VNets to dynamically learn routes propagated by the Route Server in a hub VNet, transit options must be enabled on both sides of the VNet peering (specifically `useRemoteGateways` on the spoke side and `allowGatewayTransit` on the hub side).
PreviousPage 50 / 60Next
All practice questions — Microsoft Azure Solutions Architect (AZ-305) | Examkin