All practice questions

1198 questions

Question 581Question

An organization is deploying a latency-sensitive public web API using Azure Functions. The API experiences unpredictable traffic spikes but must respond to all requests with minimal delay. The organization wants to use a serverless billing model that scales dynamically while completely avoiding latency spikes caused by cold starts. Which Azure Functions hosting plan should you recommend?

Show answer & explanation

Answer: Premium plan

Answer

Premium plan
The Premium plan provides pre-warmed instances that prevent cold starts while still offering dynamic scaling and serverless billing features.

Step-by-Step Solution

1
Analyze the scaling and latency requirements.
The application requires dynamic auto-scaling to handle unpredictable spikes, but must avoid cold-start latency.
This rules out hosting plans that either suffer from cold starts or do not support event-driven scaling.
2
Evaluate the hosting options against the cold-start constraint.
The Consumption plan is eliminated due to cold starts. The Dedicated plan and Azure Kubernetes Service are eliminated because they lack native serverless scaling behavior or add significant management overhead.
To prevent latency on initial requests, pre-warmed instances are required.
3
Select the plan that combines serverless scaling with pre-warmed instances.
The Premium plan is chosen because it keeps instances warm to avoid cold starts while scaling out dynamically.
The Premium plan is specifically designed for serverless workloads that cannot tolerate cold starts.

Key Concept

Azure Functions hosting plans features and cold start mitigation
Estimated Time:45s
Question 582Question

A healthtech company is designing a containerized genomic analysis system on Azure. The system has the following requirements:
- A front-end web portal and internal API microservices must scale dynamically based on HTTP traffic and queue-based events using KEDA.
- Background worker containers must process genomic sequences, taking up to 3 hours per execution. These workers must run to completion and automatically release resources when idle.
- The compute hosting solution must minimize administrative overhead and avoid managing container orchestrators.
- For compliance and data sovereignty, the application logs of the genomic background workers must be strictly segregated from the front-end portal logs, ensuring complete data isolation, separate lifecycle retention, and regional isolation.

Which three recommendations should you include in the solution?

Select all that apply

Show answer & explanation

Answer: Deploy the front-end web portal and API microservices to Azure Container Apps.; Deploy the background worker containers as Azure Container Apps jobs.; Create separate Log Analytics workspaces to store the logs of the front-end portal and the background workers.

Answer

To host the front-end portal and API microservices, deploy them to Azure Container Apps. To host the background worker containers, deploy them as Azure Container Apps jobs. For logging, create separate Log Analytics workspaces to satisfy strict compliance and data isolation requirements.
The correct recommendations involve using Azure Container Apps for the front-end and microservices to support serverless KEDA-based scaling with low administrative overhead, using Azure Container Apps jobs for the 3-hour run-to-completion background workers to avoid timeouts, and utilizing separate Log Analytics workspaces to ensure strict compliance, sovereignty, and data isolation boundaries for genomic logs.

Step-by-Step Solution

1
Analyze the compute requirements for the web portal and microservices.
Identify that KEDA scaling is required, and administrative overhead must be minimized.
Azure Container Apps provides serverless container hosting with native KEDA integration, satisfying these requirements without the overhead of AKS.
2
Analyze the compute requirements for the genomic background workers.
Identify that the tasks take up to 3 hours to process and must run to completion.
Standard Azure Container Apps are suited for continuous services, whereas Azure Container Apps jobs are designed for run-to-completion batch processing and support execution times up to 24 hours. Azure Functions on a Consumption plan is ruled out due to its 10-minute timeout limit.
3
Analyze the compliance and data isolation logging requirements.
Identify that strict segregation, regional sovereignty, and separate data lifecycle retention policies are required.
A single Log Analytics workspace cannot guarantee compliance boundaries at a sovereignty level; separate workspaces are required.
4
Synthesize the design recommendations.
Azure Container Apps for services, Azure Container Apps jobs for the background workers, and separate Log Analytics workspaces for logging.
This combination satisfies all requirements, respects the 3-hour processing constraint, enforces log segregation, and minimizes management overhead.

Key Concept

Selecting the appropriate Azure container hosting and monitoring architectures based on operational overhead, scaling behavior, execution duration, and compliance requirements.
Question 583Question

A logistics company is designing a global traffic routing and high-availability architecture for its hybrid fleet management platform deployed in the East US and North Europe regions.

The platform includes two distinct workloads:
1. A web application that requires edge-based SSL/TLS termination, URL path-based routing, and immediate session failover.
2. A high-throughput telemetry ingestion endpoint that communicates over a custom TCP port 88838883 (MQTT) and must route clients to the lowest-latency active datacenter.

Which global routing configuration should you recommend to meet these requirements with the lowest operational complexity?

Show answer & explanation

Answer: Configure Azure Front Door to route traffic for the web application, and configure Azure Traffic Manager using performance routing to resolve the endpoint for the telemetry ingestion service.

Answer

Configure Azure Front Door to route traffic for the web application, and configure Azure Traffic Manager using performance routing to resolve the endpoint for the telemetry ingestion service.
The correct option correctly pairs Azure Front Door with Azure Traffic Manager. Azure Front Door handles the HTTP/HTTPS web application, providing required Layer 77 capabilities like SSL/TLS termination at the edge and URL path-based routing. Azure Traffic Manager resolves the DNS queries for the custom TCP port 88838883 (MQTT) telemetry ingestion service, routing clients to the lowest-latency healthy regional endpoint. Since Traffic Manager works at the DNS level, it is protocol-agnostic and supports non-HTTP TCP traffic.

Step-by-Step Solution

1
Analyze the web application requirements.
The web application requires Layer 77 capabilities including SSL/TLS termination, URL path-based routing, and immediate failover.
Azure Front Door is a global Layer 77 Anycast-based load balancer designed for HTTP/HTTPS workloads, making it the correct choice for this workload.
2
Analyze the telemetry ingestion service requirements.
The telemetry service uses custom TCP port 88838883 (MQTT) and requires global routing to the lowest-latency active datacenter.
Azure Front Door only supports HTTP/HTTPS protocols and cannot ingest or route custom TCP port traffic.
3
Select the routing mechanism for the telemetry ingestion service.
Azure Traffic Manager resolves the endpoint DNS requests based on performance (latency).
Traffic Manager operates at the DNS level and is protocol-agnostic, allowing it to route clients on custom ports like port 88838883 to the closest healthy regional endpoint.

Key Concept

Selecting and combining global Azure load balancing services based on protocol support (Layer 77 HTTP/HTTPS vs. protocol-agnostic DNS routing).
Estimated Time:2m 30s
Question 584Question

An energy utility company is designing an analytical platform to process smart meter readings. The platform receives approximately 1010 million telemetry payloads per day, which are consolidated and written as Parquet files every hour to an Azure Data Lake Storage (ADLS) Gen2 account. Analysts need to perform occasional, ad-hoc exploratory SQL queries on the historical Parquet data to identify usage anomalies. The solution must survive a primary region datacenter outage, minimize operational costs, and avoid the use of credentials with a lifetime exceeding 3030 days. Which analytical and storage configuration should you recommend?

Show answer & explanation

Answer: Use Azure Synapse Analytics serverless SQL pools to query the Parquet files directly, store the data in an ADLS Gen2 account configured with Geo-Redundant Storage (GRS), and control access using Microsoft Entra ID authentication.

Answer

Use Azure Synapse Analytics serverless SQL pools to query the Parquet files directly, store the data in an ADLS Gen2 account configured with Geo-Redundant Storage (GRS), and control access using Microsoft Entra ID authentication.
The correct solution uses Azure Synapse Analytics serverless SQL pools, which are ideal for ad-hoc, cost-effective exploratory queries since charges are based on the volume of data processed by each query. Using Geo-Redundant Storage (GRS) ensures the data is replicated to a secondary region to survive a primary region outage. Utilizing Microsoft Entra ID authentication provides secure access control without the risk of long-lived Shared Access Signatures.

Step-by-Step Solution

1
Analyze the query pattern and compute model.
Identify that occasional, ad-hoc queries are best served by a serverless SQL pool rather than a dedicated SQL pool to avoid continuous running costs.
Serverless SQL pools charge only per query based on data processed, whereas dedicated SQL pools charge for provisioned compute running continuously.
2
Evaluate the storage redundancy requirement for disaster recovery.
Select Geo-Redundant Storage (GRS) over Locally Redundant Storage (LRS).
The system must survive a primary region datacenter outage, which requires replicating data to a paired secondary region.
3
Evaluate the security and access control mechanism.
Choose Microsoft Entra ID authentication instead of a long-lived SAS token.
Microsoft Entra ID provides identity-based, token-controlled access that aligns with credential lifetime and rotation best practices, whereas a long-lived SAS token presents high security risks.

Key Concept

Selecting cost-effective analytics services (serverless vs dedicated pools), appropriate storage redundancy (GRS vs LRS), and secure access mechanisms (Entra ID vs SAS) for data lake integration.
Question 585Question

A retail company is designing a container-based solution to process inventory updates from an Azure Service Bus queue. The application consists of a single containerized worker that must scale dynamically based on the number of messages in the queue, including scaling to zero when the queue is empty. Each message takes up to 12 minutes to process due to dependencies on legacy external systems. The company requires a solution that minimizes administrative overhead and infrastructure management. Which hosting option should you recommend for the containerized worker?

Show answer & explanation

Answer: Azure Container Apps

Answer

Azure Container Apps
Azure Container Apps provides a serverless platform for hosting containerized applications and background workers with no complex infrastructure management, directly satisfying the requirement to minimize administrative overhead. It features native integration with KEDA, enabling it to scale replicas from zero up to many instances based on the Azure Service Bus queue depth. Additionally, standard container apps running in Azure Container Apps do not have the 10-minute timeout limitation that applies to Azure Functions on a Consumption plan, making it the correct service for tasks that take up to 12 minutes to process.

Step-by-Step Solution

1
Analyze the execution duration requirements of the queue processing container.
The message processing can take up to 12 minutes.
This rules out Azure Functions on a Consumption plan, which enforces a strict 10-minute maximum execution timeout limit.
2
Evaluate the infrastructure management and administrative effort constraints.
The company wants to minimize infrastructure management and administrative overhead.
This rules out Azure Kubernetes Service (AKS), as it requires managing Kubernetes control planes, node pools, routing, and updates.
3
Assess the remaining serverless container hosting platforms for native auto-scaling capabilities.
Azure Container Apps supports serverless hosting with native KEDA scale rules to scale to zero based on Service Bus queue length, whereas Azure Container Instances (ACI) requires custom orchestration to scale dynamically.
This identifies Azure Container Apps as the optimal solution that meets both the scaling and administrative constraints.

Key Concept

Selecting Azure container hosting platforms based on administrative effort, scaling triggers, and execution duration limits.
Question 586Question

An enterprise is designing a hub-and-spoke network topology in Azure. The hub virtual network, `vnet-weur-hub` (10.10.0.0/1610.10.0.0/16), hosts a central network virtual appliance (NVA) at IP address 10.10.1.410.10.1.4 to inspect outbound internet traffic. The spoke virtual network, `vnet-prod-spoke` (10.20.0.0/1610.20.0.0/16), contains a subnet named `snet-prod-web` (10.20.1.0/2410.20.1.0/24) that hosts web servers. You need to configure the routing so that all outbound internet traffic from `snet-prod-web` is routed through the NVA, while internal communication within the spoke virtual network remains uninterrupted. Which two configurations should you implement? (Select two.)

Select all that apply

Show answer & explanation

Answer: Associate a route table with the `snet-prod-web` subnet containing a route for `0.0.0.0/00.0.0.0/0` with a next hop type of Virtual Appliance and IP address 10.10.1.410.10.1.4.; Enable the 'Allow forwarded traffic' setting on the virtual network peering connection in `vnet-weur-hub` to accept traffic from the spoke.

Answer

To configure routing through the NVA, associate a route table with the spoke subnet containing a route for all traffic pointing to the NVA as a virtual appliance, and enable the forwarded traffic setting on the peering link to permit transit traffic.
The correct configurations involve creating a route table with a route of `0.0.0.0/00.0.0.0/0` pointing to the NVA's IP (10.10.1.410.10.1.4) as a Virtual Appliance and associating it with the spoke subnet, and configuring the peering connection to allow forwarded traffic. The route table directs all non-local outbound traffic to the NVA. Allowing forwarded traffic on the peering ensures that the hub VNet accepts and routes transit traffic received from the spoke.

Step-by-Step Solution

1
Define a route table for the spoke subnet `snet-prod-web` and add a default route of `0.0.0.0/00.0.0.0/0` directed to the NVA's IP address (10.10.1.410.10.1.4).
Outbound internet traffic from the subnet is directed to the hub's NVA.
By default, Azure routes internet-bound traffic directly to the internet. A User Defined Route (UDR) is required to override this system route.
2
Enable the 'Allow forwarded traffic' configuration on the peering connection between the hub and spoke.
Peering allows packets originating outside the local VNet (the spoke) to be forwarded through the hub VNet.
Without enabling forwarded traffic, Azure's virtual network peering will drop packets where the source IP address does not match the peered network space.

Key Concept

Azure Virtual Network Peering and User Defined Routes (UDR) transit configuration.
Question 587Question

A logistics company is designing a container-based processing solution for IoT telematics data. The solution requires:
- A public-facing API that receives sensor telemetry, which must scale dynamically based on concurrent HTTP requests.
- A batch processing workload that aggregates telemetry data every evening, which takes between 15 and 45 minutes to execute.
- All workloads must run in a secure environment with no public internet access for the backend processing components.
- The design must minimize administrative and operational effort.

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

Select all that apply

Show answer & explanation

Answer: An Azure Container Apps container app to host the public-facing API; An Azure Container Apps job to host the batch processing workload

Answer

To satisfy the requirements with the lowest operational overhead, you should recommend deploying the public-facing API as an Azure Container Apps container app and the batch processing workload as an Azure Container Apps job.
The correct recommendation is to use an Azure Container Apps container app for the public-facing API and an Azure Container Apps job for the batch processing workload. Both resources run within the same Azure Container Apps environment, allowing them to share a secure private virtual network. This satisfies the requirement to minimize administrative effort by utilizing serverless container hosting, while accommodating the 45-minute execution duration of the batch job.

Step-by-Step Solution

1
Evaluate the administrative overhead requirements for the containerized workloads.
Azure Kubernetes Service (AKS) is eliminated because it introduces significant operational and cluster management overhead, which fails the requirement to minimize administrative effort.
Azure Container Apps provides a serverless platform that simplifies container deployments compared to full Kubernetes cluster management.
2
Analyze the execution lifetime constraint of the nightly batch processor.
An Azure Functions Consumption plan is ruled out because its execution timeout limit is 10 minutes, whereas the batch processor runs for 15 to 45 minutes.
Workloads must be matched to hosting options that support their execution durations without timing out.
3
Identify the appropriate Azure Container Apps deployment types for the two workloads.
The public-facing API is mapped to a standard container app (which scales based on HTTP traffic), and the nightly batch process is mapped to a container apps job (which is optimized for run-to-completion batch tasks).
This configuration utilizes the appropriate built-in features of Azure Container Apps for both transactional and batch processing workloads.

Key Concept

Selecting the appropriate Azure container service and workload type based on operational overhead, scale triggers, and execution lifetime.
Estimated Time:2m 0s
Question 588Question

You are designing a backup solution for an Azure Virtual Machine that hosts a critical database. The virtual machine has the following characteristics:
* Uses Standard Premium SSD managed disks.
* Requires backups to be retained in a vault for 180180 days.
* Requires the ability to perform instant recoveries (near-zero Recovery Time Objective (RTO)) using local snapshots for any recovery point from the last 77 days.
* The backup data must be resilient against a zone outage in the primary region.

Which backup configuration should you recommend?

Show answer & explanation

Answer: An Enhanced backup policy with instant restore retention set to 77 days, and a Recovery Services vault configured with Zone-Redundant Storage (ZRS).

Answer

An Enhanced backup policy with instant restore retention set to 77 days, and a Recovery Services vault configured with Zone-Redundant Storage (ZRS).
The correct configuration uses an Enhanced backup policy configured with 77 days of instant restore retention and a Recovery Services vault set to Zone-Redundant Storage (ZRS). The Enhanced policy is required because the Standard policy restricts the instant restore retention range to between 11 and 55 days, which would fail the requirement to support instant recoveries within 77 days. Furthermore, ZRS is required to ensure the backups remain available in the event of an availability zone outage within the primary region.

Step-by-Step Solution

1
Analyze the instant recovery requirement.
The requirement states that the solution must support instant recovery (near-zero RTO) for any recovery point from the last 77 days. This means local snapshots must be retained for at least 77 days.
Instant recovery in Azure Backup relies on the snapshots stored in the source storage account/disk layer rather than the vault tier.
2
Determine the required backup policy type based on instant restore limits.
Standard backup policies support instant restore retention for only 11 to 55 days. Enhanced backup policies support configurable instant restore retention from 11 to 3030 days. Therefore, an Enhanced policy is required to meet the 77-day instant recovery window.
A Standard policy cannot be configured to hold snapshots for more than 55 days.
3
Identify the vault redundancy requirement.
The backups must survive a zone outage within the primary region. This requires selecting Zone-Redundant Storage (ZRS) for the Recovery Services vault.
Locally Redundant Storage (LRS) replicates data only within a single datacenter, failing to protect against a zone outage.

Key Concept

Azure VM backup policy tier limits and vault storage redundancy.
Question 589Question

Aetherius Manufacturing plans to integrate its on-premises Active Directory Domain Services (AD DS) directory with a Microsoft Entra ID tenant.

You need to design the identity and access management architecture. The solution must satisfy the following requirements:
- Ensure that users can authenticate to cloud services using their on-premises passwords, even if the on-premises domain controllers are offline.
- Enforce multi-factor authentication (MFA) for all administrative sessions to the Azure portal, while ensuring that dedicated emergency-access accounts remain accessible in the event of an MFA service disruption.
- Minimize the administrative overhead and the physical server footprint required for the identity sync solution.

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

Select all that apply

Show answer & explanation

Answer: Configure Microsoft Entra Connect with Password Hash Synchronization (PHS).; Create a Conditional Access policy that requires multi-factor authentication (MFA) for the Microsoft Azure Management app, and configure a group exclusion for the emergency-access accounts.

Answer

To satisfy the requirements, you should configure Microsoft Entra Connect with Password Hash Synchronization (PHS) and create a Conditional Access policy that requires multi-factor authentication (MFA) for the Microsoft Azure Management app with an exclusion group configured for emergency-access accounts.
Password Hash Synchronization (PHS) meets the resiliency and minimal overhead requirements because it authenticates users directly in Microsoft Entra ID using stored password hashes, eliminating reliance on on-premises domain controller availability during login and requiring no extra on-premises infrastructure. Additionally, configuring a Conditional Access policy for the Microsoft Azure Management app that enforces MFA ensures administrative sessions are secure, while excluding emergency-access accounts from the policy prevents administrative lockout in the event of an MFA service disruption.

Step-by-Step Solution

1
Evaluate the hybrid authentication options against the offline authentication and minimal infrastructure requirements.
Password Hash Synchronization (PHS) is selected.
PHS copies password hashes to Microsoft Entra ID, allowing authentication to occur in the cloud when local domain controllers are offline, and requires only the basic sync agent footprint without AD FS servers.
2
Evaluate the Conditional Access policy design for protecting the Azure portal while preventing tenant lockout.
A Conditional Access policy targeting the Microsoft Azure Management app with MFA required and a group exclusion for emergency-access accounts is selected.
This configuration enforces MFA for administrative operations while avoiding lockout risks for break-glass accounts during an MFA outage.

Key Concept

Microsoft Entra ID hybrid authentication architecture and resilient Conditional Access design
Question 590Question

SolisTransport is designing a disaster recovery and business continuity solution for its maritime cargo tracking system. The tracking system writes voyage telemetry logs to a general-purpose v2 storage account in the East US region.

The solution must meet the following requirements:
- Recovery Point Objective (RPO): Under 15 minutes.
- Recovery Time Objective (RTO) for reads: Near 0 minutes. The application must be able to read tracking data from a secondary region (West US) immediately during a primary region outage, without waiting for Microsoft to declare a disaster or initiate a failover.
- Write Availability: Write capability in the secondary region is only required if the outage is prolonged and a failover is officially declared.
- Cost Constraints: Minimize storage costs and avoid the overhead of zone redundancy in the primary region.

Which storage configuration and recovery strategy should you recommend?

Show answer & explanation

Answer: Configure the storage account to use Read-Access Geo-Redundant Storage (RA-GRS). Direct read requests to the secondary endpoint during the outage, and initiate a customer-managed failover if write capability is required.

Answer

Configure the storage account to use Read-Access Geo-Redundant Storage (RA-GRS), direct read requests to the secondary endpoint during the outage, and initiate a customer-managed failover if write capability is required.
The correct configuration uses Read-Access Geo-Redundant Storage (RA-GRS). RA-GRS provides a secondary read-only endpoint that allows the application to read the tracking data immediately during a primary outage, meeting the near-zero RTO requirement. It only supports write operations to the secondary region after a customer-managed failover is triggered, which meets the requirement of allowing writes only when a failover is officially declared. Furthermore, RA-GRS uses locally redundant storage (LRS) in both the primary and secondary regions, satisfying the cost constraint of avoiding zone-redundancy overhead in the primary region.

Step-by-Step Solution

1
Evaluate read availability requirements during a primary region outage.
The RTO for reads must be near 0 minutes without waiting for a failover, which means the secondary region must be readable. This requires a read-access geo-redundant option (RA-GRS or RA-GZRS), ruling out standard GRS and LRS.
Standard GRS does not expose a secondary read endpoint until failover occurs.
2
Evaluate write availability and failover requirements.
Writes to the secondary region are only needed if a failover is declared. Prior to failover, writes must not go to the secondary endpoint because it is read-only.
Both GRS and RA-GRS secondary endpoints do not support writes before failover.
3
Evaluate cost and zone-redundancy constraints.
The requirements specify minimizing costs and avoiding zone redundancy in the primary region. This rules out RA-GZRS (which uses zone redundancy in the primary region) in favor of RA-GRS (which uses local redundancy in both primary and secondary regions).
RA-GRS is the most cost-effective option that satisfies the geo-redundant read availability requirements.

Key Concept

Azure Storage replication options, focusing on the differences between GRS and RA-GRS, read/write endpoint availability, and the failover process.
Question 591Question

A financial technology (fintech) corporation is designing a container-based credit scoring engine. The engine will run as regional microservices deployed in both the Azure North Europe and US East regions to process local credit profiles.

The design must satisfy the following requirements:
* The compute platform must automatically scale replicas based on CPU utilization and must scale down to zero replicas during off-peak hours to minimize idle costs.
* The administrative effort required to manage host operating systems, Kubernetes control planes, and orchestrator upgrades must be minimized.
* Container logs must be collected and segregated to comply with strict regional data sovereignty regulations, ensuring that European credit profile logs are never stored in or co-mingled with US-based logs.

Which solution should you recommend?

Show answer & explanation

Answer: Deploy the regional microservices to internal Azure Container Apps environments in their respective regions. Configure separate Log Analytics workspaces in each region to store and isolate the container logs.

Answer

Deploy the regional microservices to internal Azure Container Apps environments in their respective regions and configure separate Log Analytics workspaces in each region to store and isolate the container logs.
Deploying the microservices to internal Azure Container Apps (ACA) environments in their respective regions combined with separate regional Log Analytics workspaces meets all design constraints. ACA is a serverless hosting platform that minimizes administrative overhead by eliminating Kubernetes control plane and VM host management, and natively supports scaling to zero based on CPU utilization. Regional Log Analytics workspaces ensure that European logs are kept completely separate from US logs, satisfying data sovereignty requirements.

Step-by-Step Solution

1
Evaluate the compute hosting requirements.
Identify that the solution requires microservices hosting with automatic scaling based on CPU utilization, scale-to-zero capability, and minimal administrative overhead (no VM host or control plane patching).
This rules out Azure Kubernetes Service (AKS) due to high management overhead, and rules out Azure Container Instances (ACI) since it lacks native metric-based scaling to zero.
2
Evaluate the regulatory and compliance logging requirements.
Identify that data sovereignty regulations prohibit co-mingling or storing European logs in the US region (or vice versa).
This mandates the use of separate Log Analytics workspaces in each region rather than a centralized single workspace, regardless of access control mechanisms like RBAC.
3
Synthesize the compute and logging components to select the best option.
Select the combination of regional internal Azure Container Apps environments and separate regional Log Analytics workspaces.
This combination satisfies both the serverless compute scaling requirements and the strict regional log segregation compliance requirements.

Key Concept

Selecting container hosting platforms and designing regional monitoring boundaries for compliance and operational efficiency.
Question 592Question

An organization is designing a privileged access and governance strategy for its Azure tenant. The strategy must enforce Multi-Factor Authentication (MFA) for all administrative roles using Microsoft Entra Privileged Identity Management (PIM) and Conditional Access policies, while ensuring that the organization does not get locked out of the tenant during an Entra ID MFA service outage.

Which of the following configurations should you recommend?

Show answer & explanation

Answer: Create a Microsoft Entra security group for the administrators, configure the group as eligible for PIM roles requiring MFA on activation, and exclude a dedicated emergency access account from the Conditional Access MFA policy.

Answer

Create a Microsoft Entra security group for the administrators, configure the group as eligible for PIM roles requiring MFA on activation, and exclude a dedicated emergency access account from the Conditional Access MFA policy.
The correct strategy utilizes Microsoft Entra security groups for scalable role management (addressing RBAC best practices), configures the PIM assignment as eligible to enforce just-in-time (JIT) access, and excludes a dedicated emergency access account from the Conditional Access MFA policy to mitigate tenant lockout risks during an MFA outage.

Step-by-Step Solution

1
Define administrative role assignment strategy using Microsoft Entra security groups.
Ensures role assignments are scalable and manageable by avoiding direct user assignments.
Direct user assignments violate RBAC governance best practices.
2
Configure Microsoft Entra Privileged Identity Management (PIM) eligibility rules.
Enforces just-in-time (JIT) access by marking assignments as eligible rather than permanently active.
Permanently active roles bypass access controls and increase the attack surface.
3
Enforce Multi-Factor Authentication (MFA) via Conditional Access while excluding emergency accounts.
Secures administrative sessions while preventing lockout during MFA outages.
Failing to exclude emergency glass-breaker accounts leaves the tenant vulnerable to total lockout.

Key Concept

Designing privileged access and governance solutions using Entra ID PIM, group-based assignments, and emergency access strategies.
Question 593Question

You need to configure a Network Security Group (NSG) to allow outbound traffic from an Azure virtual network subnet to Azure SQL Database instances. The solution must block all other traffic to the internet, minimize administrative effort, and avoid manual IP address management when Azure services update their IP address ranges. Which destination setting should you specify in the outbound security rule of the Network Security Group?

Show answer & explanation

Answer: The Sql Service Tag

Answer

The Sql Service Tag
The correct solution is to use the 'Sql' Service Tag as the destination. A Service Tag represents a group of IP address prefixes from a given Azure service. Using service tags eliminates the need to manually update security rules when IP addresses change, minimizing administrative effort.

Step-by-Step Solution

1
Identify the target service requiring outbound connectivity and the administrative constraint.
The target is Azure SQL Database, and the solution must avoid manual IP updates.
This establishes that we need a dynamic referencing mechanism rather than static IP configurations.
2
Select the appropriate Network Security Group destination option that groups the target service's IP addresses.
The built-in 'Sql' Service Tag is selected.
Service tags abstract IP prefixes for specific Azure services and are managed automatically by Microsoft, fulfilling all constraints.

Key Concept

Using Service Tags in Network Security Groups to simplify security rules and eliminate manual IP address maintenance for Azure services.
Estimated Time:45s
Question 594Question

A logistics company is designing the data redundancy strategy for two different storage workloads in Azure:

1. Workload A (Configuration Files): Requires protection against zone failures within the primary region, and must also be replicated to a secondary region to protect against regional disasters. Read-only access to the secondary region is not required.
2. Workload B (User Profile Images): Must survive a regional outage, and the application must be able to retrieve these images from the secondary region at all times (including during a primary region outage) without waiting for a customer-initiated or Microsoft-initiated failover. Zone redundancy is not required in the primary region.

Which two redundancy options should you select to meet the requirements of each workload? (Select two.)

Select all that apply

Show answer & explanation

Answer: Geo-zone-redundant storage (GZRS) for Workload A; Read-access geo-redundant storage (RA-GRS) for Workload B

Answer

Geo-zone-redundant storage (GZRS) for Workload A and Read-access geo-redundant storage (RA-GRS) for Workload B
Geo-zone-redundant storage (GZRS) for Workload A is correct because it synchronously replicates data across three availability zones in the primary region and asynchronously replicates it to the secondary region. Read-access geo-redundant storage (RA-GRS) for Workload B is correct because it provides read-only access to the secondary region without a failover, while avoiding the cost of zone redundancy in the primary region.

Step-by-Step Solution

1
Analyze the requirements for Workload A.
Workload A requires zone redundancy in the primary region (ZRS) and replication to a secondary region (GRS). Combining these requires Geo-zone-redundant storage (GZRS).
GZRS replicates data across three zones in the primary region and then copies it to a secondary region.
2
Analyze the requirements for Workload B.
Workload B requires survival of regional outages and immediate read-only access to the secondary region without initiating failover. It does not require zone redundancy in the primary region.
Read-access geo-redundant storage (RA-GRS) replicates data to a secondary region and exposes a read-only endpoint, satisfying the requirement without the higher cost of zone redundancy.

Key Concept

Selecting the appropriate Azure Storage redundancy tier (GZRS and RA-GRS) based on high availability, zone resilience, regional recovery, and secondary read requirements.
Question 595Question

A financial services company is designing a global document-sharing platform. The architecture stores document metadata in Azure Cosmos DB for NoSQL and the PDF files in Azure Blob Storage. The system expects a 70:3070:30 read-to-write ratio, requires a 99.999%99.999\% read and write availability SLA, and must survive a regional datacenter outage. The PDF files must be accessible to external clients using temporary, revocable links. Which design combination should you recommend to meet these requirements?

Show answer & explanation

Answer: Set the Cosmos DB partition key to `contractId`, configure Geo-Zone-Redundant Storage (GZRS) for Blob Storage, and generate short-lived Shared Access Signatures (SAS) associated with a stored access policy.

Answer

To meet all design requirements, the partition key for Azure Cosmos DB must be a high-cardinality field such as `contractId`. Azure Blob Storage should be configured with Geo-Zone-Redundant Storage (GZRS) to withstand regional disasters. Finally, secure document links must be generated using short-lived Shared Access Signatures (SAS) associated with a stored access policy to support immediate revocation.
The correct design uses a high-cardinality partition key (`contractId`) for Azure Cosmos DB to prevent hot partitions and ensure even distribution of requests. To survive a regional outage, GZRS provides zone-redundancy and geo-redundancy, ensuring data is resilient to regional disasters. For secure and revocable client access, generating short-lived SAS tokens that reference a stored access policy allows the security key to be revoked easily if compromised.

Step-by-Step Solution

1
Select a Cosmos DB partition key that distributes workload evenly.
Using `contractId` instead of a low-cardinality property like `documentStatus` distributes logical partitions uniformly and avoids hot partitions.
Azure Cosmos DB partitions data horizontally based on the key. Low-cardinality keys group data together, leading to throughput limitations.
2
Select the storage replication tier that supports regional failover.
Select Geo-Zone-Redundant Storage (GZRS) instead of Locally Redundant Storage (LRS).
LRS replicates data only within a single physical location. To survive a regional disaster, data must be geo-replicated.
3
Establish a secure mechanism for temporary file access that supports revocation.
Generate short-lived SAS tokens that reference a stored access policy.
Stored access policies allow immediate revocation of permissions by modifying the policy, whereas direct ad-hoc SAS URIs cannot be easily revoked.

Key Concept

Designing highly scalable, disaster-resilient, and secure storage solutions using Azure Cosmos DB and Azure Blob Storage.
Question 596Question

An organization wants to delegate custom permissions to a development team. The team needs the ability to restart and manage virtual machines across all subscriptions nested under the 'R&D' management group. You must design a custom role that permits virtual machine management operations but explicitly prevents virtual network configuration modifications. The custom role must be scope-constrained so it can only be assigned to subscriptions under the 'R&D' management group. You need to create this custom role and assign it to the development team's Microsoft Entra ID group. Which sequence of actions should you perform?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

Retrieve the resource ID of the 'R&D' management group, create a JSON definition file containing the custom role's permissions and specifying the management group's resource ID in the AssignableScopes list, register the custom role in the tenant by importing the JSON definition file using the Azure CLI or Azure PowerShell, and finally assign the registered custom role to the development team's Microsoft Entra ID group at the 'R&D' management group scope.
The correct sequence begins with identifying the resource ID of the 'R&D' management group. This ID must be included in the AssignableScopes property of the custom role JSON definition. Once the JSON file is fully configured, the custom role is registered in the Azure Active Directory (Microsoft Entra ID) tenant. Only after the custom role is successfully registered can it be assigned to the target security group at the management group scope.

Step-by-Step Solution

1
Retrieve the resource ID of the 'R&D' management group.
You obtain the precise resource path of the target management group.
The custom role's AssignableScopes property requires the exact resource path of the management group to restrict where the role can be defined and used.
2
Create a JSON definition file detailing permissions and scopes.
A complete JSON role definition document with Actions, NotActions, and AssignableScopes is drafted.
This file establishes the actual configuration of the custom role, ensuring the exclusion of network permissions and target scope restrictions.
3
Import the JSON definition file to register the role.
The custom role definition is registered in the Azure tenant database.
The role must be registered in Azure before Azure Resource Manager can process assignments for it.
4
Assign the custom role to the Microsoft Entra ID group.
The security group is granted the permissions defined in the custom role at the management group scope.
Assigning the role at the management group scope ensures all nested subscriptions inherit the permissions automatically.

Key Concept

Azure Custom RBAC Role Lifecycle and Scope Inheritance
Question 597Question

A manufacturing company is designing an analytical data platform to monitor and analyze assembly line operations. The platform must meet the following requirements:
- Store 55 TB of historical machine telemetry in CSV format.
- Ingest real-time sensor streams at a rate of 10,00010,000 events per second (1010 MB/s).
- Perform real-time anomaly detection with a processing latency of less than 22 seconds.
- Support ad-hoc exploratory SQL queries over the historical CSV data with execution times under 3030 seconds, without the operational overhead of a running cluster.
- Ensure the storage solution remains available if a primary zone within the Azure region experiences an outage.

Which two components should you include in the design to meet these requirements? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Azure Synapse Analytics serverless SQL pools to query the historical telemetry data directly from Azure Data Lake Storage Gen2.; Azure Stream Analytics to process real-time sensor streams ingested through Azure Event Hubs.

Answer

Azure Synapse Analytics serverless SQL pools to query the historical telemetry data directly from Azure Data Lake Storage Gen2, and Azure Stream Analytics to process real-time sensor streams ingested through Azure Event Hubs.
The correct architecture uses Azure Synapse Analytics serverless SQL pools to run ad-hoc queries on the CSV data stored in Azure Data Lake Storage Gen2, as it avoids persistent cluster costs and management. Additionally, Azure Stream Analytics paired with Azure Event Hubs handles the hot path streaming analytics and real-time anomaly detection under the 2-second latency requirement.

Step-by-Step Solution

1
Analyze cold path analytical query requirements
Identified the need to run ad-hoc SQL queries directly on CSV data in Azure Data Lake Storage Gen2 with zero persistent cluster overhead.
Azure Synapse Analytics serverless SQL pools are paid per query and require no cluster provisioning, satisfying the cost and low operational overhead constraint.
2
Analyze hot path streaming and ingestion requirements
Identified the need for an ingestion event broker and a stream processing engine capable of sub-2-second latency.
Azure Event Hubs combined with Azure Stream Analytics provides a managed, scalable solution for real-time anomaly detection.
3
Evaluate redundancy and security requirements
Ruled out Locally Redundant Storage (LRS) since the data must survive a zone outage, and rejected long-lived SAS tokens due to operational security risks.
Zone-Redundant Storage (ZRS) is required to survive a zone outage, and Shared Access Signatures with long lifetimes should use stored access policies for easy revocation.

Key Concept

Data Integration and Analytical Storage
Estimated Time:2m 0s
Question 598Question

An enterprise is designing a secure hub-and-spoke network topology in Azure. The topology consists of the following components:

* A hub virtual network named `vnet-prod-hub` (10.100.0.0/1610.100.0.0/16) containing:
* A subnet named `snet-nva` (10.100.1.0/2410.100.1.0/24) that hosts a Network Virtual Appliance (NVA) at IP address 10.100.1.410.100.1.4.
* A subnet named `GatewaySubnet` (10.100.2.0/2410.100.2.0/24) that hosts an ExpressRoute Virtual Network Gateway.
* A peered spoke virtual network named `vnet-prod-spoke` (10.200.0.0/1610.200.0.0/16) containing a subnet named `snet-app` (10.200.1.0/2410.200.1.0/24).

The ExpressRoute gateway connects to an on-premises network (192.168.0.0/16192.168.0.0/16). Virtual network peering is configured to allow gateway transit.

You need to design a routing solution that meets the following requirements:
1. All traffic from `snet-app` destined for the on-premises network must be inspected by the NVA.
2. All traffic from the on-premises network destined for `snet-app` must be inspected by the NVA.
3. The NVA must be able to forward inspected traffic to its final destination without routing loops or losing connectivity.

Which two configurations should you include in the design?

Select all that apply

Show answer & explanation

Answer: Associate a route table with the GatewaySubnet that contains a route for 10.200.0.0/16 with the next hop set to Virtual appliance (10.100.1.4).; Associate a route table with snet-app that contains a route for 192.168.0.0/16 with the next hop set to Virtual appliance (10.100.1.4), and disable BGP route propagation on the route table.

Answer

The correct configurations are to: 1) Associate a route table with the GatewaySubnet that contains a route for the spoke network space pointing to the NVA as a virtual appliance, and 2) Associate a route table with the spoke subnet containing a route for the on-premises network space pointing to the NVA as a virtual appliance, while disabling BGP route propagation on that route table.
To inspect traffic in both directions, custom routing must be applied to both the spoke subnet and the gateway subnet. Outbound traffic is redirected by associating a route table to the spoke subnet with a UDR for the on-premises network range pointing to the NVA. BGP route propagation must be disabled on the spoke subnet's route table to prevent dynamically advertised routes from on-premises from bypassing the UDR. Inbound traffic is redirected by associating a route table with the GatewaySubnet that contains a UDR for the spoke network range pointing to the NVA, overriding the default system peering route.

Step-by-Step Solution

1
Configure outbound routing from the spoke to the NVA.
Associate a route table with the spoke subnet (`snet-app`) containing a UDR for `192.168.0.0/16` pointing to the NVA (`10.100.1.4`) as the next hop.
This ensures that traffic originating from the application tier destined for on-premises is sent to the NVA for inspection instead of using the default system-propagated route.
2
Ensure BGP routes do not override the outbound UDR.
Disable BGP route propagation on the route table associated with `snet-app`.
By default, Azure system routes learned via BGP (such as specific subnets advertised by the on-premises edge router) take precedence over broader UDRs if they represent a more specific prefix. Disabling route propagation prevents the subnet from dynamically learning these routes, forcing all traffic to follow the custom UDR.
3
Configure inbound routing from the gateway to the NVA.
Associate a route table with `GatewaySubnet` containing a UDR for `10.200.0.0/16` pointing to the NVA (`10.100.1.4`) as the next hop.
When traffic returns from the on-premises network, the gateway would normally route it directly to the spoke via the default VNet Peering system route. A UDR on the `GatewaySubnet` overrides the default peering path and forces the gateway to send the traffic to the NVA first.

Key Concept

Azure Custom Routing, Gateway Subnet UDRs, and BGP Route Propagation Controls
Estimated Time:2m 30s
Question 599Question

An enterprise is designing a multi-region disaster recovery and traffic routing architecture for several distinct workloads. Match each traffic routing and failover requirement to the most appropriate Azure service.

Click a left item, then click its matching right item

Items

Route HTTPS traffic globally, enforce web application firewall (WAF) policies at the edge, offload SSL certificates, and failover within seconds without waiting for DNS client caching to expire.
Route custom TCP/UDP traffic globally to regional endpoints using a single, static Anycast IP address, ensuring low-latency routing without DNS resolution overhead.
Route TCP/UDP traffic globally using geographic or performance-based routing policies, where clients can tolerate failover times governed by DNS TTL values.
Route HTTP/HTTPS traffic regionally within a single Azure virtual network, providing private path-based routing, SSL termination, and cookie-based session affinity.

Matches

Show answer & explanation

Answer

The correct matches are: (1) Route HTTPS traffic globally with edge WAF, SSL offloading, and near-instant failover matches with Azure Front Door. (2) Route custom TCP/UDP traffic globally using a static Anycast IP without DNS overhead matches with Azure Cross-Region Load Balancer. (3) Route TCP/UDP traffic globally using DNS-based geographic/performance policies matches with Azure Traffic Manager. (4) Route HTTP/HTTPS traffic regionally within a single virtual network with SSL termination and session affinity matches with Azure Application Gateway.
Azure Front Door matches global Layer 7 requirements because it offers Anycast-based HTTP/HTTPS routing, SSL offloading, and edge WAF integration with near-instantaneous backend failover. Azure Cross-Region Load Balancer matches global Layer 4 requirements using a single static Anycast IP address to route TCP/UDP packets. Azure Traffic Manager provides DNS-based routing for any protocol globally, which depends on TTL for failover. Azure Application Gateway provides regional, private-network Layer 7 routing, cookie-based session affinity, and SSL termination.

Step-by-Step Solution

1
Analyze the operational scope (global vs. regional) and layers (Layer 4 vs. Layer 7) of the requirements.
Requirements 1 and 4 need Layer 7 features (WAF, SSL offloading, path routing). Requirements 2 and 3 need Layer 4 or general protocol routing. Requirement 4 is regional, whereas the others are global.
This categorizes the services: Azure Front Door and Application Gateway are Layer 7; Traffic Manager and Cross-Region Load Balancer operate at Layer 4 or DNS level. Application Gateway is regional.
2
Distinguish between the global Layer 7 solution and the regional Layer 7 solution.
The regional HTTP/HTTPS path routing and session affinity requirement maps to Azure Application Gateway. The global HTTPS requirement with WAF at the edge maps to Azure Front Door.
Azure Application Gateway cannot route traffic globally across regions natively, while Azure Front Door is designed for global edge delivery.
3
Differentiate between the global Layer 4 traffic routing mechanisms (Anycast IP routing vs. DNS-based routing).
The custom TCP/UDP workload requiring a single static Anycast IP maps to Azure Cross-Region Load Balancer. The TCP/UDP workload where DNS TTL-based failover is acceptable maps to Azure Traffic Manager.
Azure Cross-Region Load Balancer uses Anycast to route packets over the Microsoft backbone without DNS changes, while Azure Traffic Manager is purely DNS-based.

Key Concept

Selecting the optimal Azure load balancing and traffic routing service based on application scope (global vs. regional), protocol layer (Layer 4 vs. Layer 7), WAF/SSL requirements, and failover latency tolerance (DNS cache vs. Anycast routing).
Estimated Time:2m 30s
Question 600Question

A digital media publishing company is designing a new platform on Azure to manage content delivery and media transformation. The platform has the following components:

* A set of front-end and back-end API microservices that experience highly variable HTTP traffic and must scale to zero instances during idle periods to minimize costs.
* A video-rendering service that requires deploying custom Kubernetes Custom Resource Definitions (CRDs) and custom operators to orchestrate rendering tasks.
* A background analytics worker that must process message queues and requires Event-Driven Autoscaling (KEDA) integration.

The design must minimize administrative overhead where possible.

Which two container hosting solutions should you recommend? (Select two.)

Select all that apply

Show answer & explanation

Answer: Azure Container Apps for the API microservices and the background analytics worker; Azure Kubernetes Service (AKS) for the video-rendering service

Answer

Azure Container Apps for the API microservices and the background analytics worker, and Azure Kubernetes Service (AKS) for the video-rendering service.
The correct solution uses Azure Container Apps for the API microservices and background worker, and Azure Kubernetes Service (AKS) for the video-rendering service. Azure Container Apps is designed to minimize administrative overhead by abstracting Kubernetes management, and it natively supports scaling to zero and event-driven scaling (KEDA). However, because Azure Container Apps does not expose the Kubernetes API or support the deployment of custom Kubernetes Custom Resource Definitions (CRDs) and custom operators, the video-rendering service must be hosted on Azure Kubernetes Service (AKS), which provides full access to the Kubernetes control plane.

Step-by-Step Solution

1
Evaluate the requirements of the API microservices and background analytics worker.
These components require rapid scaling, scale-to-zero capabilities, and KEDA integration, and the organization wishes to minimize administrative overhead.
Azure Container Apps is a fully managed serverless platform that natively supports scaling to zero and event-driven scaling (KEDA) without the operational overhead of managing a Kubernetes cluster.
2
Evaluate the requirements of the video-rendering service.
The video-rendering service requires deploying custom Kubernetes Custom Resource Definitions (CRDs) and custom operators.
Deploying custom CRDs and operators requires direct access to the Kubernetes API. Since Azure Container Apps completely abstracts the Kubernetes control plane, Azure Kubernetes Service (AKS) must be used to provide direct API access.
3
Select the correct combination of container hosting options.
Recommend Azure Container Apps for the API microservices and analytics worker, and Azure Kubernetes Service (AKS) for the video-rendering service.
This design satisfies all requirements while minimizing administrative overhead where possible by utilizing serverless containers where appropriate.

Key Concept

Determining when to use Azure Container Apps versus Azure Kubernetes Service (AKS) based on operational overhead, scale-to-zero requirements, and the need for direct Kubernetes API access (CRDs/operators).
PreviousPage 30 / 60Next