All practice questions

1198 questions

Question 1001Question

A cloud architect needs to select appropriate Azure networking services to satisfy load balancing and failover requirements for different application types. Match each operational scenario to the optimal Azure service that meets the requirements.

Click a left item, then click its matching right item

Items

A global HTTP/S application requiring URL path-based routing, TLS offloading, and immediate failover via Anycast IP routing.
A global TCP-based gaming application on port 7777 requiring client traffic redirection to the nearest region using DNS name resolution.
A regional web service requiring cookie-based session affinity, TLS offloading, and URL path-based routing within a virtual network.
A global application requiring Layer 4 load balancing to route non-HTTP TCP/UDP traffic to different regions using a single static Anycast IP.

Matches

Show answer & explanation

Answer

The correct matches are: 1) The global HTTP/S application matches Azure Front Door. 2) The global TCP-based gaming application matches Azure Traffic Manager. 3) The regional web service matches Azure Application Gateway. 4) The global Layer 4 Anycast application matches Azure Cross-region Load Balancer.
The correct matches map the specific technical characteristics (layer, scope, protocol) of each scenario to the capabilities of Azure's load balancing services.

Step-by-Step Solution

1
Analyze the scope (global vs. regional) and protocol layer (Layer 4, Layer 7, or DNS) for each scenario.
Two scenarios are global Layer 7/DNS HTTP/S, one is regional Layer 7 HTTP/S, and two are global Layer 4 TCP/UDP.
Categorizing the requirements by network layer and geographic scope immediately filters down the available Azure load balancing services.
2
Differentiate the Layer 7 requirements based on regional vs. global requirements.
The regional HTTP/S requirement inside a virtual network maps to Azure Application Gateway. The global HTTP/S application requiring fast failover and Anycast maps to Azure Front Door.
Azure Application Gateway operates within a region and virtual network, whereas Azure Front Door operates at the edge globally.
3
Differentiate the global Layer 4/DNS requirements.
The TCP port 7777 scenario requiring DNS resolution maps to Azure Traffic Manager. The global TCP/UDP scenario requiring a static Anycast IP maps to Azure Cross-region Load Balancer.
Azure Traffic Manager uses DNS redirection and supports custom TCP ports, while Azure Cross-region Load Balancer operates at Layer 4 using Anycast IP routing.

Key Concept

Selecting the correct Azure load balancing service involves evaluating regional vs. global scope, Layer 4 vs. Layer 7 routing capabilities, and DNS vs. Anycast IP architectures.
Question 1002Question

A company is modernizing a web application that will be hosted in a single Azure region. The solution must meet the following requirements:
- Support SSL/TLS termination at the load balancer.
- Support URL path-based routing (HTTP/HTTPS).
- Provide regional zone-redundant high availability.
- Ensure the configuration does not fail validation due to SKU mismatches.

Which load balancing configuration should you recommend?

Show answer & explanation

Answer: Azure Application Gateway (Standard v2) with backend virtual machines distributed across multiple Availability Zones

Answer

Azure Application Gateway (Standard v2) with backend virtual machines distributed across multiple Availability Zones
The correct configuration is the Azure Application Gateway (Standard v2) with backend virtual machines distributed across multiple Availability Zones. This service operates at Layer 7, providing the required SSL/TLS termination and URL path-based routing. Distributing the virtual machines across multiple Availability Zones satisfies the zone-redundant high availability requirement.

Step-by-Step Solution

1
Identify the protocol and routing requirements.
The application requires HTTP/HTTPS routing, SSL/TLS termination, and path-based routing, which necessitates a Layer 7 load balancer.
Layer 4 load balancers like Azure Load Balancer and DNS-based service routing like Traffic Manager do not inspect HTTP/HTTPS payloads.
2
Evaluate the high availability and regional constraints.
The solution must be regional and zone-redundant, meaning backend virtual machines must be distributed across multiple Availability Zones.
Placing all instances in a single Availability Zone fails zone-redundancy requirements.
3
Check validation and SKU constraints.
Avoid mixing Basic and Standard SKU configurations.
A Standard Load Balancer cannot connect to resources with Basic SKU public IP addresses, whereas Application Gateway v2 works seamlessly with standard configurations.

Key Concept

Application Load Balancing and Delivery
Question 1003Question

A healthcare technology provider is designing a SaaS application on Azure that will process patient telemetry data across two different regions: Germany and the United States.

The solution must meet the following requirements:
- Host a containerized processing microservice that scales dynamically based on the queue depth of an Azure Service Bus queue.
- Separate the logging and monitoring data of patient events to comply with strict regional data sovereignty laws in each country.
- Minimize administrative effort and infrastructure management overhead.

Which two components should you include in the design?

Select all that apply

Show answer & explanation

Answer: Azure Container Apps to host the processing microservice; Separate Azure Log Analytics workspaces in Germany and the United States to isolate monitoring data

Answer

Azure Container Apps to host the processing microservice, and separate Azure Log Analytics workspaces in Germany and the United States to isolate monitoring data.
The correct design incorporates Azure Container Apps because it natively integrates with KEDA to scale workloads based on queue metrics without the administrative overhead of managing a Kubernetes cluster. Additionally, separate Log Analytics workspaces in each region ensure strict regional data isolation to meet sovereignty compliance regulations.

Step-by-Step Solution

1
Evaluate compute options for hosting containerized microservices scaling on queue depth with minimal administrative effort.
Identify that Azure Container Apps supports KEDA scaling out-of-the-box and handles underlying infrastructure management, making it superior to Azure Kubernetes Service for low-overhead needs.
This meets the requirement of hosting containers with dynamic scaling while minimizing administrative effort.
2
Evaluate monitoring options for strict regional data sovereignty across Germany and the United States.
Determine that separate Log Analytics workspaces are required in each region to ensure physical boundary separation and compliance.
This meets the strict compliance and data sovereignty rules by avoiding co-mingling patient logs in a single central workspace.

Key Concept

Selecting container hosting and monitoring strategies that balance scaling capabilities, operational overhead, and compliance constraints in Azure.
Question 1004Question

A logistics company hosts a legacy portal on-premises on VMware. The application tier consists of three stateless web virtual machines (VMs) with minimal write activity. The data tier consists of a single high-transaction SQL Server VM. The SQL Server VM has a system disk, a data disk averaging 8 MB/s8 \text{ MB/s} write churn, and a transaction log disk averaging 32 MB/s32 \text{ MB/s} write churn. The company requires a disaster recovery (DR) solution to Azure with a Recovery Point Objective (RPO) of under 10 seconds for the database and under 4 hours for the web tier.

Which disaster recovery design should you recommend?

Show answer & explanation

Answer: Replicate the application VMs using Azure Site Recovery, and replicate the database using SQL Server Always On Availability Groups to SQL Server on Azure VMs.

Answer

Replicate the application VMs using Azure Site Recovery, and replicate the database using SQL Server Always On Availability Groups to SQL Server on Azure VMs.
The correct design replicates the stateless application VMs using Azure Site Recovery and utilizes SQL Server Always On Availability Groups to replicate the database. The database's transaction log disk churn of 32 MB/s32 \text{ MB/s} exceeds the 25 MB/s25 \text{ MB/s} limit per Premium SSD disk for Azure Site Recovery VMware-to-Azure replication. Replicating the database natively via Always On Availability Groups bypasses this limit and meets the low RPO of under 10 seconds.

Step-by-Step Solution

1
Evaluate the database write churn requirements against Azure Site Recovery limits.
The SQL Server VM has a transaction log disk experiencing 32 MB/s32 \text{ MB/s} write churn, which exceeds the Azure Site Recovery limit of 25 MB/s25 \text{ MB/s} per Premium SSD disk for VMware-to-Azure replication.
Identifying capacity limits prevents replication failures and unhealthy replication states in Azure Site Recovery.
2
Evaluate the Recovery Point Objective (RPO) requirements for both tiers.
The web tier requires an RPO under 4 hours, which is easily met by Azure Site Recovery. The database tier requires an RPO of under 10 seconds, which Azure Site Recovery cannot guarantee.
Choosing the replication technology must align with the target business continuity and disaster recovery metrics.
3
Determine the optimal replication strategy for the hybrid architecture.
Combine Azure Site Recovery for the application tier with native SQL Server Always On Availability Groups (configured for asynchronous or synchronous commit) for the database tier.
This hybrid approach ensures high-churn databases are replicated via application-native mechanisms to satisfy both churn limits and low RPO requirements, while web VMs leverage standard VM replication.

Key Concept

Designing disaster recovery solutions by aligning workload write churn metrics and RPO requirements with Azure Site Recovery support limits and native replication alternatives.
Question 1005Question

An enterprise is designing a serverless data processing pipeline in Azure to support a telemetry analysis system. The solution must host the following workloads:

- Workload 1: An event-driven API endpoint that ingests telemetry data. The workload must scale rapidly from 00 to handle unpredictable traffic spikes, incur 00 cost when idle, and route outbound traffic through an Azure Virtual Network to securely access a private database.
- Workload 2: A batch processing job that runs containerized custom simulation code triggered by telemetry events. The job must run for up to 4545 minutes per execution and dynamically scale down to 00 instances when no simulations are active.

The architecture must minimize operational management overhead and monthly hosting costs.

Which two compute solutions should you recommend? (Select two.)

Select all that apply

Show answer & explanation

Answer: Azure Functions on a Flex Consumption plan for Workload 1; Azure Container Apps Jobs for Workload 2

Answer

Azure Functions on a Flex Consumption plan should be recommended for Workload 1, and Azure Container Apps Jobs should be recommended for Workload 2.
Azure Functions on a Flex Consumption plan is the correct choice for the event-driven ingestion workload because it combines event-driven serverless scaling and scale-to-zero capabilities with native virtual network integration. Azure Container Apps Jobs is the correct choice for the batch simulation workload because it is serverless, scales to zero when no jobs are active, supports custom containerized runtimes, and allows jobs to execute for up to 2424 hours, which easily accommodates the 4545-minute runtime without timeout failures.

Step-by-Step Solution

1
Evaluate the requirements for Workload 1.
Workload 1 requires rapid scale-out from 00, zero cost when idle, and outbound virtual network integration to reach a private database. Azure Functions on a Flex Consumption plan meets all these needs.
Standard Consumption plans lack virtual network integration, while App Service plans do not scale to zero or scale out as rapidly.
2
Evaluate the requirements for Workload 2.
Workload 2 requires containerized execution, dynamic scale-to-zero behavior, and support for a 4545-minute execution duration. Azure Container Apps Jobs meets these constraints.
Azure Functions on Consumption plans are limited by a 1010-minute timeout, and deploying an Azure Kubernetes Service cluster would introduce excessive operational management overhead.
3
Select the correct combination.
Azure Functions on a Flex Consumption plan for Workload 1 and Azure Container Apps Jobs for Workload 2.
This combination satisfies all networking, execution duration, and cost/overhead constraints.

Key Concept

Selecting serverless compute resources based on scaling behaviors, networking requirements, execution timeouts, and operational overhead.
Question 1006Question

An organization has deployed a virtual network named `vnet-prod-uswest` (10.110.0.0/1610.110.0.0/16) that contains two subnets: `subnet-web` (10.110.1.0/2410.110.1.0/24) and `subnet-data` (10.110.2.0/2410.110.2.0/24). A Network Virtual Appliance (NVA) is deployed in a peered hub virtual network at 10.120.1.410.120.1.4.

The organization needs to inspect all traffic sent from `subnet-web` to `subnet-data` using the NVA. The solution must ensure that virtual machines within `subnet-web` can still communicate directly with each other without routing through the NVA.

Which route should be added to the route table associated with `subnet-web`?

Show answer & explanation

Answer: Address prefix: 10.110.2.0/2410.110.2.0/24, Next hop type: Virtual appliance, Next hop address: 10.120.1.410.120.1.4

Answer

Address prefix: 10.110.2.0/2410.110.2.0/24, Next hop type: Virtual appliance, Next hop address: 10.120.1.410.120.1.4
The correct route uses the destination prefix 10.110.2.0/2410.110.2.0/24, which matches only the database subnet. Because Azure uses the Longest Prefix Match algorithm, traffic destined for the database subnet will match this route and be forwarded to the NVA. Traffic destined for other resources within the same web subnet (10.110.1.0/2410.110.1.0/24) will not match this route and will instead use the system-defined local route (10.110.0.0/1610.110.0.0/16) with next hop 'Virtual Network', keeping the local communication direct.

Step-by-Step Solution

1
Identify the destination subnet of the traffic that requires inspection.
The target traffic is destined for `subnet-data` which uses the prefix 10.110.2.0/2410.110.2.0/24.
Routing policies in Azure should target the most specific prefix possible to avoid affecting unrelated traffic paths.
2
Evaluate the priority and behavior of Azure system routes versus User-Defined Routes (UDRs).
Azure uses Longest Prefix Match (LPM) to select routes. If a UDR and a system route have identical prefixes, the UDR is preferred.
Understanding route selection order ensures the custom route is selected over the default system route.
3
Create a route that targets only the destination subnet and routes it to the NVA IP address.
A route with prefix 10.110.2.0/2410.110.2.0/24 pointing to next hop 10.120.1.410.120.1.4 is associated with `subnet-web`.
Traffic to `subnet-data` (10.110.2.0/2410.110.2.0/24) matches the UDR and goes to the NVA. Traffic within `subnet-web` (10.110.1.x10.110.1.x) does not match the UDR prefix and falls back to the system route (10.110.0.0/1610.110.0.0/16, next hop Virtual Network), keeping local traffic direct.

Key Concept

Azure route precedence rules and Longest Prefix Match (LPM) behavior with User-Defined Routes (UDRs)
Estimated Time:1m 30s
Question 1007Question

An organization is designing a hub-and-spoke network topology in Azure. The hub virtual network, `vnet-hub-shared`, has an address space of 10.100.0.0/1610.100.0.0/16 and contains an Azure VPN Gateway in `GatewaySubnet` (10.100.0.0/2410.100.0.0/24) and a Network Virtual Appliance (NVA) at IP address 10.100.10.410.100.10.4. The spoke virtual network, `vnet-spoke-app`, has an address space of 10.101.0.0/1610.101.0.0/16. The networks are connected via virtual network peering.

The design must meet the following requirements:
- Spoke virtual machines must route all internet-bound traffic through the NVA in the hub.
- Spoke virtual machines must communicate with an on-premises network (172.16.0.0/12172.16.0.0/12) through the VPN Gateway.
- Spoke virtual machines must communicate directly with resources in the hub virtual network (10.100.0.0/1610.100.0.0/16) without passing through the NVA.

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

Select all that apply

Show answer & explanation

Answer: Configure the virtual network peering to allow gateway transit on `vnet-hub-shared` and use the remote virtual network's gateway on `vnet-spoke-app`.; Create a route table associated with the subnets in `vnet-spoke-app` that contains a route for 0.0.0.0/00.0.0.0/0 with the next hop set to the virtual appliance at 10.100.10.410.100.10.4.

Answer

Configure virtual network peering to allow gateway transit on the hub and use remote gateways on the spoke, and create a route table associated with the spoke subnets containing a route for 0.0.0.0/00.0.0.0/0 with the next hop set to the virtual appliance.
The correct configurations involve setting up virtual network peering to allow gateway transit and use remote gateways, combined with a user-defined default route (0.0.0.0/00.0.0.0/0) pointing to the network virtual appliance (NVA). Gateway transit allows the spoke virtual network to learn on-premises routes via BGP propagation. The default route redirects internet-bound traffic to the NVA. Because the peering system route for the hub (10.100.0.0/1610.100.0.0/16) and the propagated BGP routes for the on-premises network (172.16.0.0/12172.16.0.0/12) are more specific than the default route, they take precedence under Azure's longest prefix match algorithm, ensuring direct traffic to the hub and correct routing to the VPN gateway.

Step-by-Step Solution

1
Configure gateway transit settings on the virtual network peering connections.
The peering connection allows the spoke virtual network to route traffic through the hub's VPN gateway to access on-premises networks.
By default, peering connections do not allow gateway transit. Enabling 'allow gateway transit' on the hub and 'use remote gateways' on the spoke enables BGP route propagation from the gateway to the spoke.
2
Ensure BGP route propagation is enabled on the spoke's route table and add a default route (0.0.0.0/00.0.0.0/0) to the NVA.
All internet-bound traffic is redirected to the NVA, while on-premises traffic (172.16.0.0/12172.16.0.0/12) and local hub traffic (10.100.0.0/1610.100.0.0/16) route directly via BGP and peering system routes.
Azure's routing selection algorithm uses Longest Prefix Match (LPM). More specific routes (such as 10.100.0.0/1610.100.0.0/16 for the hub and 172.16.0.0/12172.16.0.0/12 for on-premises) will always take precedence over the default route (0.0.0.0/00.0.0.0/0) to the NVA.

Key Concept

Azure virtual network routing priority, virtual network peering gateway transit, and the longest prefix match algorithm.
Estimated Time:2m 0s
Question 1008Question

An organization is designing a disaster recovery strategy for a web-based portal hosted in the West Europe and North Europe regions. The solution must support SSL/TLS offloading at the routing layer to reduce decryption overhead on the backend web servers, and it must achieve the lowest possible recovery time objective (RTO) for traffic redirection during a regional failover. Which routing service and configuration should you recommend?

Show answer & explanation

Answer: Azure Front Door, because it uses Anycast routing to terminate SSL/TLS at the edge and immediately redirects client traffic to the healthy region without relying on client DNS cache updates.

Answer

Azure Front Door, because it uses Anycast routing to terminate SSL/TLS at the edge and immediately redirects client traffic to the healthy region without relying on client DNS cache updates.
The correct choice is the option that recommends Azure Front Door for SSL/TLS termination and edge-based failover. Azure Front Door utilizes Anycast routing to direct client traffic to the nearest Point of Presence (PoP), where SSL/TLS handshakes are completed (offloading decryption from backend servers). Because it routes traffic at Layer 7 and uses split-TCP, it detects backend failures via health probes and immediately diverts traffic to the healthy region at the network level, avoiding the latency associated with DNS client caching and TTL expiration.

Step-by-Step Solution

1
Analyze the requirements for global traffic routing, SSL/TLS offloading, and low failover recovery time objective (RTO).
Identified that the solution must handle global routing, terminate SSL sessions at the network edge, and bypass DNS-based replication delays during failover.
Establishing clear design criteria allows for the elimination of solutions that fail to meet these requirements.
2
Evaluate Azure Traffic Manager against the SSL offloading and RTO requirements.
Determined that Azure Traffic Manager is a DNS-based service that does not intercept HTTP traffic, meaning it cannot offload SSL/TLS. Furthermore, its failover speed is limited by client-side DNS caching and TTL settings.
DNS-based failover is not instantaneous and does not support Layer 7 application features like SSL termination.
3
Evaluate Azure Front Door against the requirements.
Confirmed that Azure Front Door is an Anycast-based Layer 7 service that terminates SSL/TLS closer to the user (at edge PoPs) and handles failover at the network level rather than relying on DNS TTL expiration, enabling near-instantaneous failover.
Anycast routing and edge-termination support both the security offloading and fast-failover requirements.

Key Concept

Anycast-based Layer 7 routing (Azure Front Door) vs DNS-based routing (Azure Traffic Manager) for global load balancing and disaster recovery.
Estimated Time:1m 30s
Question 1009Question

An enterprise is designing a hub-and-spoke network topology in Azure for a multi-tier application. The architecture includes:

* A hub virtual network named `vnet-prod-hub` with an address space of 10.150.0.0/1610.150.0.0/16.
* `AzureFirewallSubnet` (10.150.1.0/2410.150.1.0/24) containing an Azure Firewall with private IP 10.150.1.410.150.1.4.
* `GatewaySubnet` (10.150.2.0/2410.150.2.0/24) containing a Virtual Network Gateway connected to on-premises via ExpressRoute.
* A spoke virtual network named `vnet-prod-spoke` with an address space of 10.160.0.0/1610.160.0.0/16.
* Subnet `snet-compute` (10.160.10.0/2410.160.10.0/24) hosting virtual machines.

The hub and spoke virtual networks are peered. The peering is configured to allow gateway transit on the hub and use remote gateways on the spoke.

The security requirements are:
1. All traffic from `snet-compute` destined for the internet must be routed through the Azure Firewall.
2. All traffic from `snet-compute` destined for the on-premises network (172.16.0.0/12172.16.0.0/12) must be routed through the Virtual Network Gateway.
3. All traffic from `snet-compute` destined for the hub virtual network (`vnet-prod-hub`) must be routed through the Azure Firewall for security inspection.

To implement these requirements, a network architect creates a route table named `rt-spoke-routing` with the following user-defined routes (UDRs):
* Route 1: 0.0.0.0/00.0.0.0/0 \rightarrow Next hop: Virtual appliance (10.150.1.410.150.1.4)
* Route 2: 10.150.0.0/1610.150.0.0/16 \rightarrow Next hop: Virtual appliance (10.150.1.410.150.1.4)

The architect associates `rt-spoke-routing` with the `snet-compute` subnet. To ensure symmetric inspection for return traffic, the architect also associates the same `rt-spoke-routing` route table with the `AzureFirewallSubnet`.

During post-deployment validation, VMs in `snet-compute` can successfully access the internet, but they cannot establish any connections to resources in the hub virtual network, and the Azure Firewall fails to pass traffic to the Gateway Subnet.

Which configuration change should the architect perform to resolve the connectivity issue while satisfying all design requirements?

Show answer & explanation

Answer: Remove the association of the `rt-spoke-routing` route table from the `AzureFirewallSubnet`, and allow the firewall to use default system routes for local hub destinations.

Answer

Remove the association of the `rt-spoke-routing` route table from the `AzureFirewallSubnet`, allowing the firewall to rely on default system routes for local hub destinations.
The correct option is the one suggesting to remove the association of the route table from the firewall subnet. In Azure, User-Defined Routes (UDRs) override system-defined routes of the same prefix length. By applying the route table containing the 10.150.0.0/1610.150.0.0/16 prefix (pointing to the firewall itself as a virtual appliance) to the firewall's own subnet, a routing loop is created. Any packet the firewall attempts to forward to other subnets in the hub virtual network matches the UDR and is routed back to the firewall. Removing this association allows the firewall to use the default system route (10.150.0.0/1610.150.0.0/16 -> Virtual Network) to successfully route traffic to other hub subnets, while the spoke still routes hub-bound traffic to the firewall.

Step-by-Step Solution

1
Analyze the route table configuration and its associations.
The route table `rt-spoke-routing` contains a route for 10.150.0.0/1610.150.0.0/16 pointing to the firewall at 10.150.1.410.150.1.4. This route table is associated with both the spoke subnet `snet-compute` and the hub `AzureFirewallSubnet`.
Understanding which subnets are bound to the routing rules determines how next hops are resolved for transit traffic.
2
Determine the impact of the UDR on the firewall's own subnet.
The firewall subnet resides within the 10.150.0.0/1610.150.0.0/16 VNet range. When the firewall tries to forward traffic to a hub destination (like the gateway at 10.150.2.x10.150.2.x), the matching route is the UDR 10.150.0.0/1610.150.0.0/16 pointing to 10.150.1.410.150.1.4.
Azure evaluates User-Defined Routes (UDRs) over default system routes of the same prefix length, which overrides the local VNet system route.
3
Identify the routing loop.
The next hop for the destination in the hub is resolved to the firewall itself (10.150.1.410.150.1.4), creating a loop where the packet repeatedly routes back to the firewall and is eventually dropped.
This explains why VMs in the spoke cannot communicate with resources in the hub and why firewall traffic fails to reach the gateway.
4
Select the correct remediation strategy.
Dissociate the `rt-spoke-routing` route table from the `AzureFirewallSubnet`. The firewall will now use default system routing, which contains a system route for 10.150.0.0/1610.150.0.0/16 pointing to 'Virtual Network'.
This allows the firewall to successfully forward traffic to other hub subnets while maintaining the required traffic inspection on the spoke subnet where the route table remains associated.

Key Concept

Azure User Defined Routes (UDR) precedence and routing loops in firewall subnets.
Estimated Time:3m 0s
Question 1010Question

An administrator needs to configure a Network Security Group (NSG) to allow outbound traffic from an Azure Virtual Network subnet to Azure SQL Database. The IP addresses for Azure SQL Database might change over time. The solution must minimize administrative overhead. Which NSG rule configuration should you recommend?

Show answer & explanation

Answer: Set the destination of the outbound security rule to the Sql service tag.

Answer

Set the destination of the outbound security rule to the Sql service tag.
Using the Sql service tag as the destination in the Network Security Group (NSG) outbound rule allows access to the Azure SQL Database service. Service tags represent a group of IP address prefixes from a given Azure service and are managed automatically by Microsoft, which minimizes administrative overhead.

Step-by-Step Solution

1
Identify the destination service that the virtual machines need to access.
Azure SQL Database
The virtual machines must establish outbound connections to Azure SQL Database.
2
Determine the network security mechanism to control outbound traffic with minimal administrative overhead.
Network Security Group (NSG) rule using a Service Tag.
Microsoft manages the IP prefixes associated with Service Tags, preventing the need to manually update rules when IPs change.
3
Select the specific Service Tag for Azure SQL Database.
The Sql service tag.
The Sql service tag represents Azure SQL Database, Azure SQL Managed Instance, and Azure Synapse Analytics.

Key Concept

Azure NSG Service Tags
Question 1011Question

An enterprise is designing a disaster recovery (DR) solution using Azure Site Recovery (ASR) to replicate workloads from the East US region to the West US region. The target Recovery Point Objective (RPO) is 2 hours, and the Recovery Time Objective (RTO) is 4 hours.

The infrastructure consists of four virtual machines (VMs) using Premium SSD storage. The write churn metrics for each VM are detailed in the table below:

Virtual MachineDisk Churn DetailsTotal VM Churn
VM1 (Web Server)Disk 1: 5 MB/s5\text{ MB/s}, Disk 2: 8 MB/s8\text{ MB/s}13 MB/s13\text{ MB/s}
VM2 (Database Server)Disk 1: 45 MB/s45\text{ MB/s}, Disk 2: 48 MB/s48\text{ MB/s}93 MB/s93\text{ MB/s}
VM3 (App Server)Disk 1: 60 MB/s60\text{ MB/s}60 MB/s60\text{ MB/s}
VM4 (Analytics Server)Disk 1: 15 MB/s15\text{ MB/s}, Disk 2: 20 MB/s20\text{ MB/s}, Disk 3: 10 MB/s10\text{ MB/s}45 MB/s45\text{ MB/s}

Which of the following virtual machines can be successfully replicated to the target region using the Standard replication tier of Azure Site Recovery?

Select all that apply

Show answer & explanation

Answer: VM1 (Web Server); VM4 (Analytics Server)

Answer

VM1 (Web Server) and VM4 (Analytics Server) can be successfully replicated using the Standard replication tier of Azure Site Recovery.
VM1 and VM4 are correct because they satisfy the Azure Site Recovery Standard replication tier constraints: the maximum write churn per Premium SSD disk is less than or equal to 54 MB/s54\text{ MB/s} and the total write churn per VM is less than or equal to 80 MB/s80\text{ MB/s}. Specifically, VM1 has a maximum disk churn of 8 MB/s8\text{ MB/s} (with a total of 13 MB/s13\text{ MB/s}) and VM4 has a maximum disk churn of 20 MB/s20\text{ MB/s} (with a total of 45 MB/s45\text{ MB/s}).

Step-by-Step Solution

1
Identify the limits of the Standard replication tier of Azure Site Recovery (ASR) for Azure VMs.
The limits for Standard ASR are 54 MB/s54\text{ MB/s} write churn per Premium SSD disk and 80 MB/s80\text{ MB/s} total write churn per virtual machine.
These limits dictate which VM workloads can be replicated without experiencing replication failures or requiring the High-Churn tier.
2
Evaluate the disk-level and VM-level churn for each virtual machine against the ASR Standard tier limits.
VM1 (max disk 8 MB/s8\text{ MB/s}, total 13 MB/s13\text{ MB/s}) is within limits. VM2 (max disk 48 MB/s48\text{ MB/s}, total 93 MB/s93\text{ MB/s}) violates the VM-level limit of 80 MB/s80\text{ MB/s}. VM3 (max disk 60 MB/s60\text{ MB/s}, total 60 MB/s60\text{ MB/s}) violates the disk-level limit of 54 MB/s54\text{ MB/s}. VM4 (max disk 20 MB/s20\text{ MB/s}, total 45 MB/s45\text{ MB/s}) is within limits.
This step determines which specific VMs exceed either the individual disk threshold or the aggregate VM threshold.
3
Select the compliant virtual machines.
VM1 (Web Server) and VM4 (Analytics Server) are the only virtual machines that satisfy both constraints.
Only virtual machines satisfying both disk and VM-level limits are supported under the Standard ASR replication tier.

Key Concept

Azure Site Recovery VM replication limit validation
Question 1012Question

A logistics company is designing an event-driven system to generate end-of-day shipping manifests. The generation process reads transaction logs, formats reports, and takes between 12 and 18 minutes to complete per run. The process is triggered by a scheduler message in an Azure Service Bus queue. The company requires a compute solution that minimizes operational overhead and incurs costs only when executing. Which compute option should you recommend?

Show answer & explanation

Answer: Azure Container Apps Jobs

Answer

Azure Container Apps Jobs
Azure Container Apps Jobs are designed specifically for tasks that run to completion, support executions up to 24 hours, scale to zero when idle, and run as serverless resources with minimal operational overhead.

Step-by-Step Solution

1
Analyze the execution duration requirement.
The workload runs for 12 to 18 minutes, which exceeds the 10-minute maximum execution timeout limit of the Azure Functions Consumption plan.
This rules out standard consumption-based Azure Functions.
2
Evaluate the cost and scaling requirements.
The solution must scale to zero and incur costs only during execution. Dedicated hosting plans are billed continuously and do not meet this constraint.
This rules out App Service plans and Dedicated Function plans.
3
Assess the operational overhead constraints.
Azure Container Apps Jobs manage container orchestration automatically and support long-running event-driven tasks, whereas Azure Kubernetes Service (AKS) requires managing nodes, clusters, and complex configurations.
This identifies Azure Container Apps Jobs as the option that minimizes operational overhead while meeting all timeout and cost requirements.

Key Concept

Selecting serverless compute hosting options based on execution timeout, scaling characteristics, and operational overhead constraints.
Estimated Time:1m 30s
Question 1013Question

A financial firm is designing a secure network environment for a pool of virtual machines in a virtual network subnet named Subnet1. The design must meet the following requirements:
- The virtual machines must retrieve cryptographic keys from an Azure Key Vault.
- The virtual machines must be isolated behind a load balancer that distributes incoming traffic.
- All outbound traffic to the internet must be blocked except for connections to Azure Key Vault.
- The configuration must minimize administrative maintenance.

Which security and load balancing configuration should you recommend?

Show answer & explanation

Answer: Configure an outbound security rule in the Network Security Group (NSG) that allows traffic to the AzureKeyVault Service Tag, and associate a Standard Load Balancer with Standard SKU public IP addresses.

Answer

Configure an outbound security rule in the Network Security Group (NSG) that allows traffic to the AzureKeyVault Service Tag, and associate a Standard Load Balancer with Standard SKU public IP addresses.
The correct choice is to configure an outbound security rule allowing traffic to the AzureKeyVault Service Tag combined with a Standard Load Balancer utilizing Standard SKU public IP addresses. This minimizes administrative overhead because Azure manages the IP address updates for the Service Tag, and matches the SKUs required for the load balancer.

Step-by-Step Solution

1
Identify the service tag requirement.
Azure Key Vault public endpoints are represented by the AzureKeyVault service tag, which updates automatically and eliminates the need for manual IP list maintenance.
This satisfies the requirement to minimize administrative maintenance.
2
Select the correct Load Balancer SKU combination.
Standard Load Balancer requires Standard SKU public IP addresses; mixing them with Basic SKU public IP addresses is not supported.
This ensures compatibility and successful resource deployment.
3
Verify routing requirements.
Avoid configuring custom routes that override system-defined local routes to ensure internal virtual network communications remain operational.
This prevents network connectivity loss within the VNet.

Key Concept

Configuring secure service access using Service Tags in NSGs while maintaining Standard SKU compatibility across network resources.
Question 1014Question

An organization is designing a high-availability solution for an enterprise web application deployed across the East US and West US regions. The design must meet the following requirements:
- Web traffic must be routed to the closest region to minimize latency for users.
- Secure Sockets Layer (SSL) termination must be handled at the global entry point to offload cryptographic processing from the backend servers.
- The solution must support URL path-based routing to direct traffic for `/static/*` and `/api/*` to different backend pools.
- Health monitoring must detect a regional outage and failover traffic within 30 seconds.

Which two actions should you include in the design to meet these requirements?

Select all that apply

Show answer & explanation

Answer: Deploy Azure Front Door to route client requests globally and perform SSL termination at the edge.; Configure Azure Front Door health probes with a probe interval of 20 seconds.

Answer

Deploy Azure Front Door to route client requests globally and perform SSL termination at the edge, and configure Azure Front Door health probes with a probe interval of 20 seconds.
Deploying Azure Front Door satisfies the Layer 7 requirements, including SSL termination at the edge and URL path-based routing, because Front Door is a global HTTP/HTTPS load balancer. In addition, setting the health probe interval to 20 seconds allows Azure Front Door to detect backend failures and failover traffic within the 30-second requirement.

Step-by-Step Solution

1
Evaluate the requirement for SSL termination and URL path-based routing at the global load balancing layer.
Identify that Azure Front Door operates at Layer 7 (HTTP/HTTPS) and natively supports both SSL offloading and path-based routing, whereas Azure Traffic Manager operates at the DNS level and cannot perform these functions.
This allows for the elimination of DNS-based routing solutions for Layer 7 features.
2
Determine the configuration needed to meet the failover time constraint of under 30 seconds.
Select a health probe interval of 20 seconds for the global load balancer to ensure unhealthy endpoints are detected and bypassed within 30 seconds.
Fast detection requires frequent health probe intervals so that the system reacts quickly to regional failures.

Key Concept

Azure Front Door provides Layer 7 global routing, SSL offloading, and rapid failover via Anycast and customizable health probes, whereas Azure Traffic Manager is a DNS-level routing mechanism that does not inspect HTTP traffic.
Question 1015Question

An enterprise is designing a hub-and-spoke network topology in Azure. The hub virtual network, `vnet-weur-hub` (10.100.0.0/1610.100.0.0/16), contains an ExpressRoute Gateway in `GatewaySubnet`, an Azure Route Server in `RouteServerSubnet` (10.100.1.0/2410.100.1.0/24), and a pair of active-passive Network Virtual Appliances (NVAs) in `NvaSubnet` (10.100.2.0/2410.100.2.0/24). The spoke virtual network, `vnet-weur-spoke-prod` (10.101.0.0/1610.101.0.0/16), is peered directly with the hub.

To implement security inspection, all egress traffic to the internet (0.0.0.0/00.0.0.0/0) from both the spoke and the hub must be routed through the NVA (10.100.2.410.100.2.4). The NVA advertises the 0.0.0.0/00.0.0.0/0 route to the Azure Route Server via BGP.

Which two configurations must you implement to ensure routing functions correctly without routing loops or unsupported configurations?

Select all that apply

Show answer & explanation

Answer: Associate a route table to the `NvaSubnet` containing a User Defined Route (UDR) for 0.0.0.0/00.0.0.0/0 with a next hop type of `Internet`.; Configure the virtual network peering on `vnet-weur-spoke-prod` to use the remote virtual network's gateway or route server, and configure the peering on `vnet-weur-hub` to allow gateway transit.

Answer

Associate a User Defined Route (UDR) for 0.0.0.0/00.0.0.0/0 pointing to the next hop type of `Internet` on the `NvaSubnet` route table, and configure the virtual network peering on `vnet-weur-spoke-prod` to use the remote gateway/route server while allowing gateway transit on the `vnet-weur-hub` peering.
When an NVA advertises a default route (0.0.0.0/00.0.0.0/0) via BGP to Azure Route Server, the Route Server propagates this default route to all subnets in the hub VNet and peered spoke VNets. To prevent a routing loop where the NVA forwards traffic back to itself, you must override the BGP route on the NVA's subnet by associating a UDR for 0.0.0.0/00.0.0.0/0 with a next hop type of `Internet`. Additionally, for the spoke VNet to receive this dynamic default route from the Route Server in the hub VNet, the VNet peering must be configured to support gateway transit (allowing gateway transit on the hub VNet side and using the remote gateway or route server on the spoke VNet side).

Step-by-Step Solution

1
Analyze the route propagation behavior of Azure Route Server (ARS).
ARS dynamically advertises BGP routes learned from the NVA (including the default route 0.0.0.0/00.0.0.0/0) to all subnets in the hub VNet and peered spoke VNets.
This is standard behavior of ARS to ensure dynamic routing propagation across the topology.
2
Identify potential routing loops at the NVA.
Since ARS propagates the 0.0.0.0/00.0.0.0/0 route to the NvaSubnet, the NVA would attempt to forward outgoing internet traffic to itself, causing a loop.
A more specific route or a local User Defined Route (UDR) is required to override the BGP-learned route on the NVA's own interface.
3
Apply a UDR to the NVA's subnet.
Create a route table with 0.0.0.0/00.0.0.0/0 pointing to the next hop type `Internet` and associate it with the `NvaSubnet`.
UDRs always take precedence over BGP routes, ensuring the NVA can send clean egress packets directly to Azure's physical internet boundary.
4
Configure the virtual network peerings for route transit.
Enable 'Use remote virtual network's gateways' on the spoke peering and 'Allow gateway transit' on the hub peering.
Without these peering settings enabled, ARS cannot propagate the dynamically learned routes to the peered spoke VNets, rendering the spoke isolated from the egress design.

Key Concept

Azure Route Server routing loop prevention and transit peering configuration.
Question 1016Question

An organization is designing a secure network architecture in Azure. The design includes:
- A subnet named Subnet-App hosting virtual machines that run an application.
- An Azure Key Vault that stores cryptographic keys.
- A Private Endpoint for the Key Vault deployed in a subnet named Subnet-Private with a private IP address of 10.10.2.4.

A Network Security Group (NSG) associated with Subnet-App must allow the virtual machines to access the Key Vault via the Private Endpoint. To meet security compliance, you must block all other outbound traffic from Subnet-App to both the internet and other resources within the virtual network.

Which configuration should you specify for the destination in the NSG outbound security rule on Subnet-App to meet the requirements with the least administrative effort?

Show answer & explanation

Answer: The private IP address of the Private Endpoint (10.10.2.4)

Answer

The private IP address of the Private Endpoint (10.10.2.4)
When accessing Azure services via Private Endpoints, all network traffic is directed to the private IP address of the endpoint. Therefore, any outbound Network Security Group (NSG) rule intended to permit this traffic must specify the Private Endpoint's private IP address as the destination. This allows the application subnet to communicate with the specific Private Endpoint while enabling other rules to block all other outbound traffic to the virtual network and the internet.

Step-by-Step Solution

1
Analyze how client virtual machines communicate with an Azure service when a Private Endpoint is implemented.
Clients communicate with the service using the private IP address assigned to the Private Endpoint (10.10.2.4) within the virtual network.
Private Endpoints project the Azure service into the virtual network as a local resource with a private IP address.
2
Evaluate the behavior of Azure Service Tags in Network Security Groups (NSGs) for outbound rules.
Service tags such as AzureKeyVault represent the public IP ranges of Azure services and do not encompass private IP addresses.
This determines that service tags cannot be used to permit traffic destined for private endpoints.
3
Determine the rule destination that satisfies the security constraint of blocking all other outbound virtual network and internet traffic.
The destination must be restricted to the specific private IP address of the Private Endpoint (10.10.2.4). Using broader tags like VirtualNetwork would allow access to unintended internal resources.
This ensures the rule adheres to the principle of least privilege and satisfies all technical constraints.

Key Concept

Configuring NSGs for Private Endpoint Access
Estimated Time:2m 0s
Question 1017Question

A media broadcasting company stores high-resolution raw video footage in a General-purpose v2 (GPv2) Azure Blob storage account. The data access patterns and requirements are as follows:

* Newly uploaded footage is frequently accessed and edited for the first 30 days.
* Between 30 and 90 days, the footage is rarely accessed but must be available for immediate playback (sub-second retrieval latency) if requested by editors.
* After 90 days, the footage is preserved for long-term compliance for a total of 365 days from the upload date. For compliance audits, retrieval latency of up to 15 hours is acceptable.
* After 365 days, the footage must be permanently deleted.

Which of the following lifecycle management configurations meets the requirements while minimizing storage costs?

Show answer & explanation

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

Answer

Transition blobs to cool storage after 30 days, transition blobs to archive storage after 90 days, and delete blobs after 365 days.
The correct configuration utilizes the absolute time elapsed since blob creation to trigger the lifecycle actions. Moving the blobs to the Cool tier after 30 days maintains sub-second retrieval latency for immediate playback. Transitioning the blobs to the Archive tier after 90 days matches the latency tolerance of up to 15 hours for compliance. Deleting the blobs after 365 days fulfills the retention policy requirement.

Step-by-Step Solution

1
Analyze the access and latency requirements for the first 90 days.
Frequent access for 30 days requires the Hot tier. Between 30 and 90 days, the footage must support sub-second retrieval latency, meaning it must stay in the Cool tier (Archive cannot be used here).
Ensures immediate playback remains possible while lowering costs after the initial 30 days.
2
Analyze the requirements after 90 days and calculate the Archive transition point.
After 90 days, a 15-hour retrieval delay is acceptable, allowing a transition to the Archive tier. Since lifecycle policy rules evaluate days relative to the creation date, the Archive transition is set to 90 days.
Minimizes storage costs for the compliance retention period.
3
Determine the deletion policy day parameter.
The total retention period is 365 days from the upload date. The deletion action is configured for 365 days since creation.
Satisfies the compliance deletion mandate without keeping data longer than necessary.

Key Concept

Azure Blob Storage lifecycle management policy rules evaluate time elapsed since blob creation as an absolute value rather than a cumulative sequence. Transitions must follow a unidirectional flow from warmer to cooler tiers (Hot to Cool to Archive), and the Archive tier is not suitable for workloads requiring sub-second or immediate access.
Question 1018Question

An enterprise is designing a multi-tier application in an Azure virtual network named VNet1. The application consists of web servers, application servers, and database servers.

You need to design a network security strategy using Network Security Groups (NSGs) to isolate the traffic between these tiers. The strategy must meet the following requirements:
- Allow web servers to communicate only with the application servers.
- Allow application servers to communicate only with the database servers.
- Minimize administrative effort as virtual machines (VMs) are added or removed from each tier.
- Avoid the use of individual IP addresses in the security rules.

Which two actions should you include in the design?

Select all that apply

Show answer & explanation

Answer: Create Application Security Groups (ASGs) and associate the network interfaces of the virtual machines with their respective ASG.; Configure NSG rules that reference the Application Security Groups as the source and destination.

Answer

Create Application Security Groups (ASGs), associate the network interfaces of the virtual machines with their respective ASG, and configure NSG rules that reference the ASGs as the source and destination.
Defining Application Security Groups (ASGs) and referencing them in Network Security Group (NSG) rules allows you to secure traffic between application tiers logically. As virtual machines are added or removed, associating their network interfaces with the correct ASG automatically applies the defined rules, satisfying all technical constraints and minimizing administrative overhead.

Step-by-Step Solution

1
Define logical groupings for the multi-tier application.
Three Application Security Groups (ASGs) are planned: one for web servers, one for application servers, and one for database servers.
This establishes a logical boundary for each tier without relying on static IP addresses.
2
Associate VM network interfaces (NICs) with the appropriate ASGs.
NICs of the web, application, and database VMs are associated with their corresponding ASG.
This ensures that any security rule applied to the ASG automatically applies to the member network interfaces.
3
Create NSG rules referencing the ASGs as sources and destinations.
Outbound and inbound rules are configured to permit traffic only between the designated ASGs (Web to App, App to Database), while denying other inter-tier traffic.
This dynamically secures the traffic flow while minimizing administrative effort as VMs are added or removed.

Key Concept

Application Security Groups (ASGs) allow you to configure network security as a natural extension of an application's structure, grouping virtual machines and defining security policies based on those groups rather than individual IP addresses.
Estimated Time:1m 30s
Question 1019Question

You are planning to migrate several physical on-premises application servers to Azure. To prevent application downtime and network latency issues post-migration, you need to identify which servers have active network connections with each other so that they can be migrated in the same group. Which Azure Migrate feature should you use to map these server relationships?

Show answer & explanation

Answer: Dependency analysis

Answer

Dependency analysis
Dependency analysis is designed specifically to visualize and identify network connections between on-premises servers, which allows administrators to group dependent servers and minimize migration risks.

Step-by-Step Solution

1
Determine the migration assessment requirement.
The requirement is to identify active network connections between on-premises physical servers to group them properly for migration.
Grouping dependent servers together prevents connection failures and latency issues post-migration.
2
Evaluate Azure Migrate discovery options.
Basic discovery collects metadata like CPU and memory, whereas dependency analysis actively maps network communication between servers.
Only dependency analysis captures the network traffic flows needed to establish server-to-server relationships.

Key Concept

Using Azure Migrate dependency analysis to identify server relationships prior to migration.
Question 1020Question

An organization is designing an event-driven system to process data files uploaded to Azure Blob Storage. The file sizes range from 1010 MB to 500500 MB, and the processing time for a single file can take up to 1515 minutes to complete. The system must process files as they are uploaded, scale down to zero instances when no files are present to minimize costs, and require the lowest possible administrative overhead. Which Azure compute solution should you recommend?

Show answer & explanation

Answer: Azure Container Apps Jobs

Answer

Azure Container Apps Jobs
Azure Container Apps Jobs are optimized for run-to-completion event-driven tasks, can scale down to zero when there are no jobs to process, support execution times longer than 1010 minutes, and are fully managed, ensuring low administrative overhead.

Step-by-Step Solution

1
Analyze the execution duration constraints.
The file processing workload can take up to 1515 minutes.
This rules out basic Azure Functions Consumption plans which enforce a hard maximum timeout of 1010 minutes.
2
Evaluate the scaling and billing constraints.
The solution must support scaling down to zero when idle.
This ensures no billing charges are incurred when no files are being uploaded, eliminating always-on hosting models.
3
Evaluate operational overhead.
The organization needs the lowest possible administrative overhead.
This favors serverless platform-as-a-service (PaaS) offerings like Azure Container Apps over fully managed Kubernetes services (AKS) or Virtual Machine Scale Sets.

Key Concept

Selecting serverless hosting options based on execution limits, scale-to-zero capability, and administrative overhead.
Estimated Time:2m 0s
PreviousPage 51 / 60Next
All practice questions — Microsoft Azure Solutions Architect (AZ-305) | Examkin