All practice questions

1198 questions

Question 461Question

An organization deploys a critical application that uses an Azure SQL Database. You need to design a high availability and disaster recovery (HA/DR) solution for the database to meet the following requirements:
- The database must support automatic failover to a partner region.
- The recovery time objective (RTO) must be less than 1 hour.
- The recovery point objective (RPO) must be less than 10 seconds.
- The application must connect to the database using unified endpoints that automatically route read-write and read-only traffic to the correct replicas without requiring connection string updates after a failover.

Which two configurations should you include in the design?

Select all that apply

Show answer & explanation

Answer: An Azure SQL Database failover group containing the primary database and a secondary database on a partner logical server; A read-write listener and a read-only listener configured on the failover group for application connectivity

Answer

Configure an Azure SQL Database failover group and use the read-write and read-only listener endpoints for application connection strings.
The correct architecture uses an Azure SQL Database failover group and configurations for read-write and read-only listener endpoints. A failover group provides automatic failover capabilities across regions and exposes unique listener endpoints. These endpoints automatically route read-write traffic to the primary database and read-only traffic to the secondary partner database, ensuring that connection strings do not need to be updated after a failover.

Step-by-Step Solution

1
Evaluate the RTO/RPO and automatic failover requirements.
Identify that automatic failover to a secondary region is required with a short RTO (< 1 hour) and RPO (< 10 seconds).
This rules out backup-based recovery and indicates a replicated HA/DR architecture is needed.
2
Determine the configuration that supports automatic failover and read-write/read-only endpoints.
Select Azure SQL Database failover groups rather than standalone active geo-replication.
Failover groups support automatic failover and provide unified listener endpoints that route traffic to primary (read-write) and secondary (read-only) databases automatically.
3
Configure the application connection strings.
Connect applications using the read-write listener for write operations and the read-only listener for read operations.
This ensures the application does not require configuration or connection string changes when a failover occurs.

Key Concept

Azure SQL Database Failover Groups for HA/DR and read-scale routing
Question 462Question

You are designing the container compute infrastructure for a new retail analytics platform. The platform includes the following two workloads:
- A message-processing service that reads tasks from an Azure Service Bus queue and must scale dynamically based on the queue depth, including scaling down to zero instances.
- A daily reporting job that aggregates transactional data, runs for up to three hours per execution, and must execute to completion.

You need to recommend a containerized hosting solution for both workloads. The solution must minimize administrative effort.

Which two Azure container hosting options should you recommend?

Select all that apply

Show answer & explanation

Answer: Azure Container Apps to host the message-processing service; Azure Container Apps Jobs to host the daily reporting job

Answer

Azure Container Apps to host the message-processing service and Azure Container Apps Jobs to host the daily reporting job.
The correct recommendation is to use Azure Container Apps to host the message-processing service and Azure Container Apps Jobs to host the daily reporting job. Azure Container Apps manages event-driven scaling (KEDA) and supports scaling to zero, satisfying the requirements of the message-processing service. Azure Container Apps Jobs provides a serverless execution environment designed for run-to-completion tasks, supporting long-running executions of up to 24 hours, which accommodates the three-hour daily reporting job. Both services are fully managed, meeting the goal of minimizing administrative effort.

Step-by-Step Solution

1
Analyze the scaling and operational requirements of the message-processing workload.
The service needs dynamic scaling based on queue depth (KEDA), scale-to-zero capabilities, and minimized administrative overhead.
This workload maps to Azure Container Apps, which handles event-driven scaling automatically under a fully managed serverless model.
2
Analyze the execution duration and lifecycle of the reporting workload.
The job is a daily, run-to-completion batch process that takes up to three hours.
Azure Container Apps Jobs is ideal for this since it supports executions lasting up to 24 hours without cluster management overhead.
3
Evaluate the administrative overhead of Azure Kubernetes Service (AKS).
AKS is rejected because it requires cluster, virtual machine node pool, and control plane management, failing the requirement to minimize administrative effort.
AKS is suitable when custom Kubernetes API access or deep control plane customization is needed, which is not required here.
4
Evaluate the execution constraints of Azure Functions Consumption plan.
Azure Functions on a Consumption plan is rejected because of its 10-minute timeout limit.
The daily reporting job runs for three hours, which exceeds the platform's hard limits.

Key Concept

Selecting the optimal Azure container hosting option based on scaling needs, execution duration, and administrative overhead constraints.
Question 463Question

An organization is deploying a critical, steady-state production web application to Azure. The application requires continuous availability and a guaranteed service level agreement (SLA) with zero tolerance for unexpected virtual machine evictions or downtime. Which compute virtualization solution should you recommend?

Show answer & explanation

Answer: Standard Azure Virtual Machines

Answer

Standard Azure Virtual Machines
Standard Azure Virtual Machines provide the continuous availability, dedicated capacity, and Azure service level agreements (SLAs) required to support critical, steady-state production workloads without the risk of eviction.

Step-by-Step Solution

1
Analyze the workload requirements
The application is critical, steady-state, and requires continuous availability with a guaranteed SLA.
This rules out any options that allow virtual machine eviction or lack high availability guarantees.
2
Evaluate the hosting options against the requirements
Standard Azure Virtual Machines offer guaranteed capacity and SLA, meeting the production requirements, whereas Spot VMs are subject to eviction.
Choosing the compute type that guarantees continuous execution is necessary for production environments.

Key Concept

Selecting the appropriate Azure virtual machine hosting option based on workload stability, availability, and SLA requirements.
Question 464Question

An enterprise is designing the infrastructure for a critical distributed database platform on Azure. The platform consists of two distinct node types: three memory-optimized write nodes (E-series VMs) and three storage-optimized read-replicas (L-series VMs). The architecture must satisfy the following requirements:

* Achieve a compute uptime SLA of 99.99%99.99\% for both the write and read tiers.
* Maintain the lowest possible network latency and highest throughput for replication traffic between the write nodes and read-replicas.
* Allow administrators to perform rolling OS updates, stop, and start individual VMs manually without affecting other instances in the tier.
* Avoid the operational overhead of managing separate availability configurations for each tier.

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

Select all that apply

Show answer & explanation

Answer: Deploy the virtual machines using a Virtual Machine Scale Set configured with Flexible orchestration mode.; Associate all virtual machines in the scale set with a single Proximity Placement Group.

Answer

Deploy the virtual machines using a Virtual Machine Scale Set configured with Flexible orchestration mode, and associate all virtual machines in the scale set with a Proximity Placement Group.
Deploying the virtual machines using a Virtual Machine Scale Set in Flexible orchestration mode allows the system to achieve a 99.99%99.99\% SLA when spread across Availability Zones while supporting heterogeneous VM sizes (E-series and L-series) and individual VM control. Associating the VMs with a Proximity Placement Group ensures that within the zonal boundaries, the physical hosts are co-located as closely as possible to reduce latency and maximize throughput for replication traffic.

Step-by-Step Solution

1
Analyze the SLA requirement of 99.99%99.99\% for the compute tier.
Determine that achieving a 99.99%99.99\% uptime SLA requires deploying VMs across multiple Availability Zones in the same Azure region.
Azure guarantees a 99.99%99.99\% VM uptime SLA only when two or more instances are deployed across two or more Availability Zones.
2
Evaluate VM management requirements, specifically supporting heterogeneous VM sizes and individual VM control.
Identify that Virtual Machine Scale Sets in Flexible orchestration mode are required.
Flexible orchestration allows mixing different VM series (E-series and L-series) in the same scale set and permits individual VM lifecycle operations, unlike Uniform mode or Availability Sets.
3
Evaluate network latency requirements for replication traffic.
Determine that all VMs must be associated with a Proximity Placement Group.
A Proximity Placement Group groups VMs physically close together to achieve the lowest possible network latency.
4
Exclude solutions that fail to meet SLA or introduce eviction risk.
Discard the use of Availability Sets (limited to a 99.95%99.95\% SLA) and Spot VMs (subject to eviction).
Ensures the overall architecture satisfies all availability and reliability goals.

Key Concept

Designing compute high availability in Azure using Virtual Machine Scale Sets in Flexible orchestration mode across Availability Zones combined with Proximity Placement Groups to balance high uptime SLAs with low-latency network performance.
Question 465Question

A financial services company is designing a new event-driven transaction reconciliation system. The system consists of 15 microservices that run as Docker containers and scale dynamically based on the volume of messages in an Azure Service Bus queue.

The design must meet the following requirements:
- Support event-driven autoscaling using Kubernetes Event-driven Autoscaling (KEDA) specifications.
- Minimize administrative effort by avoiding the provisioning, patching, and management of container clusters, nodes, or control planes.
- Ensure strict network isolation between the development and production environments by routing all egress traffic through a centralized Azure Firewall.
- Isolate production logs from development logs in separate storage repositories to meet regulatory compliance, while preventing administrative overhead associated with managing log workspaces.

Which container hosting and logging solution should you recommend?

Show answer & explanation

Answer: Deploy the microservices to two separate Azure Container Apps Environments (one for development and one for production) integrated with dedicated virtual networks. Configure virtual network routing to direct egress traffic through the central Azure Firewall, and associate each environment with a separate Log Analytics workspace.

Answer

Deploy the microservices to two separate Azure Container Apps Environments (one for development and one for production) integrated with dedicated virtual networks. Configure virtual network routing to direct egress traffic through the central Azure Firewall, and associate each environment with a separate Log Analytics workspace.
The correct design utilizes Azure Container Apps (ACA) because it is a serverless container platform that natively supports Kubernetes Event-driven Autoscaling (KEDA) scaling rules without the operational overhead of managing clusters, nodes, or control planes. To achieve strict network isolation, each environment is deployed into its own virtual network with custom route tables directing egress through the Azure Firewall. To satisfy regulatory logging compliance, separate Log Analytics workspaces are used for each Container Apps Environment, ensuring production data isolation while keeping management overhead low compared to managing a cluster-based logging agent configuration.

Step-by-Step Solution

1
Analyze compute and infrastructure management requirements.
Determine that the serverless requirement and the aversion to cluster/node provisioning rule out standard AKS, leading to Azure Container Apps (ACA) as the primary compute candidate.
ACA provides a fully managed, serverless container platform that automatically abstracts node management while supporting native KEDA-based scaling.
2
Evaluate network isolation and egress routing constraints.
Determine that a dual-environment virtual network configuration is required to separate development and production, allowing custom route tables to direct egress traffic through Azure Firewall.
Strict environment-level network boundaries cannot be securely maintained within a single Container Apps Environment or a single shared VNet without complex, error-prone configurations.
3
Assess the logging compliance and administrative overhead constraints.
Conclude that two separate Log Analytics workspaces must be deployed (one per Container Apps Environment).
This satisfies the regulatory segregation of production logs from development logs, while avoiding the overhead of managing a massive multi-workspace mesh or a single workspace that violates the compliance boundary.

Key Concept

Selecting the optimal container platform and isolation boundary under strict administrative, networking, and compliance constraints in Microsoft Azure.
Question 466Question

You are designing a compute solution in Azure for a web application. The solution must meet the following requirements:
- The virtual machines (VMs) hosting the web application must have a guaranteed uptime SLA of 99.99%99.99\%.
- Incoming web traffic must be distributed across the VMs.

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

Select all that apply

Show answer & explanation

Answer: Deploy the virtual machines across two or more Availability Zones in the same Azure region.; Deploy a Standard Load Balancer to distribute incoming traffic to the virtual machines.

Answer

To achieve a 99.99%99.99\% uptime SLA and distribute traffic across the zones, you must deploy the virtual machines across two or more Availability Zones and use a Standard Load Balancer.
To meet the 99.99%99.99\% virtual machine uptime SLA, the virtual machines must be deployed across two or more Availability Zones. Distributing traffic across zonal virtual machines requires a Standard Load Balancer, which is zone-redundant and supports backend instances in different zones.

Step-by-Step Solution

1
Evaluate the SLA requirement for the virtual machines.
To meet the 99.99%99.99\% VM uptime SLA, the virtual machines must be deployed across two or more Availability Zones.
Microsoft offers a 99.99%99.99\% SLA for VMs only when two or more instances are deployed across different Availability Zones in the same region.
2
Select the appropriate load balancer SKU to distribute traffic across zones.
Choose a Standard Load Balancer.
The Standard SKU load balancer is required to route traffic to VMs in different Availability Zones, whereas the Basic SKU load balancer does not support this topology.

Key Concept

Designing compute high availability in Azure using Availability Zones and Standard Load Balancers to achieve a 99.99%99.99\% VM uptime SLA.
Estimated Time:1m 0s
Question 467Question

An enterprise is deploying a critical database workload on Azure Virtual Machines. The virtual machines are configured with Premium SSD v2 managed disks and are deployed across multiple Availability Zones in the East US region.

You are designing a business continuity and disaster recovery solution using Azure Backup. The solution must meet the following requirements:
- Data Residency: All backup data must remain within the East US region.
- Resiliency: The backup infrastructure must survive a single Availability Zone outage within the primary region.
- Performance: The solution must support restoring the virtual machines from snapshots stored on local disks for up to 77 days to meet a recovery time objective (RTO) of less than 1515 minutes.
- Retention: Backups must be retained daily for 6060 days.

Which two of the following configuration options should you select to meet these requirements? Select two.

Select all that apply

Show answer & explanation

Answer: Create a Recovery Services vault and configure its storage redundancy to Zone-Redundant Storage (ZRS).; Configure an Enhanced backup policy with a daily schedule, an instant restore retention of 77 days, and a vault-tier retention of 6060 days.

Answer

Configure a Recovery Services vault with Zone-Redundant Storage (ZRS) redundancy, and configure an Enhanced backup policy with a daily schedule, an instant restore retention of 77 days, and a vault-tier retention of 6060 days.
To satisfy both the resiliency and data residency requirements, the Recovery Services vault must be configured with Zone-Redundant Storage (ZRS). ZRS replicates the backup data across three availability zones within the primary region (East US), ensuring the backups survive a zone outage while keeping the data locally within the region. To support VMs configured with Premium SSD v2 managed disks and an instant restore retention of 77 days, an Enhanced backup policy must be used. Standard backup policies do not support Premium SSD v2 or Ultra disks, and their instant restore retention is limited to a maximum of 55 days.

Step-by-Step Solution

1
Determine the required vault storage redundancy type based on residency and availability needs.
Zone-Redundant Storage (ZRS) is selected for the Recovery Services vault.
The solution must survive a zone outage within East US and must not replicate data outside of East US. ZRS satisfies both constraints. Locally Redundant Storage (LRS) fails the zone outage requirement, and Geo-Redundant Storage (GRS) violates the data residency constraint by replicating to a paired region.
2
Select the appropriate backup policy type based on disk compatibility and instant restore requirements.
An Enhanced backup policy is selected.
The virtual machines use Premium SSD v2 managed disks, which are only supported by the Enhanced backup policy. In addition, the requirement for 77 days of instant restore capability exceeds the 55-day limit of the Standard backup policy.
3
Configure the backup policy parameters.
Configure instant restore retention to 77 days and vault-tier retention to 6060 days within the Enhanced policy.
This setup aligns with the required daily retention periods and enables fast local restores from disk snapshots for up to 77 days.

Key Concept

Azure Backup vault storage redundancy and Enhanced policy capabilities for advanced disk types
Question 468Question

You are designing a backup solution for an Azure Virtual Machine that hosts a critical enterprise resource planning (ERP) application. The virtual machine is configured with Premium SSD v2 managed disks.

Your design must meet the following requirements:
* The Recovery Time Objective (RTO) for restoring backups from the last 7 days must be minimized by using local snapshots.
* Backups must remain available even if an entire Azure region experiences an outage.
* Daily backups must be retained in the vault for 180 days.
* Administrative effort and cost must be minimized.

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

Select all that apply

Show answer & explanation

Answer: An Enhanced backup policy with the instant restore retention set to 7 days; A Recovery Services vault configured with Geo-redundant storage (GRS) and Cross Region Restore enabled

Answer

The correct configurations are using an Enhanced backup policy with the instant restore retention set to 7 days, and using a Recovery Services vault configured with Geo-redundant storage (GRS) and Cross Region Restore enabled.
To support local snapshot retention of 7 days (instant restore) and back up a VM using Premium SSD v2 managed disks, you must use an Enhanced backup policy. Standard backup policies only support up to 5 days of instant restore retention and do not support Premium SSD v2 disks. To ensure backup availability during a regional outage, the Recovery Services vault must be configured with Geo-redundant storage (GRS) and Cross Region Restore (CRR) enabled, allowing you to restore data in the secondary region.

Step-by-Step Solution

1
Evaluate the virtual machine disk configuration and the operational recovery requirements.
The virtual machine uses Premium SSD v2 managed disks and requires 7 days of instant recovery (local snapshot retention).
Standard backup policies only support up to 5 days of instant restore retention and do not support Premium SSD v2 managed disks. Therefore, an Enhanced backup policy must be used, with the instant restore retention set to 7 days.
2
Analyze the regional resiliency and disaster recovery requirements.
Backups must remain available if an entire Azure region fails, and they must be restorable in the secondary paired region.
A Recovery Services vault must be configured with Geo-redundant storage (GRS) and Cross Region Restore (CRR) enabled to allow restores in the paired region even while the primary region is offline.
3
Combine the selected configurations to form the complete backup design.
Choose the Enhanced backup policy with 7 days of instant restore and the Recovery Services vault configured with GRS and CRS.
This combination fulfills all constraints regarding disk compatibility, RTO, regional disaster recovery, and retention.

Key Concept

Designing Azure Virtual Machine backup solutions using Recovery Services vaults and backup policies, aligning snapshot and vault-level retention with recovery objectives and storage redundancy constraints.
Question 469Question

A healthcare provider plans to store patient telemetry logs in an Azure General Purpose v2 storage account. The storage configuration must meet the following requirements:

* Telemetry logs must remain writeable in the primary region even if an entire Azure availability zone (datacenter) within that region goes offline.
* The logs must be replicated to a secondary Azure region to ensure business continuity in the event of a regional disaster.
* The application running in the secondary region does not require read access to the logs unless a failover to the secondary region is initiated.
* The solution must minimize costs.

Which redundancy option should you recommend?

Show answer & explanation

Answer: Geo-zone-redundant storage (GZRS)

Answer

Geo-zone-redundant storage (GZRS) is the optimal configuration because it replicates data across three availability zones in the primary region (protecting against zone outages) and copies it asynchronously to a secondary region, without incurring the extra cost of read access to the secondary region.
Geo-zone-redundant storage (GZRS) provides high availability for write operations in the primary region by spreading data across three availability zones. It also replicates data asynchronously to a secondary region for disaster recovery. Since read access to the secondary region is not required before failover, GZRS meets all constraints at the lowest cost.

Step-by-Step Solution

1
Analyze primary region availability requirements.
The requirement states writes must continue if an availability zone fails. This rules out Locally Redundant Storage (LRS) options in the primary region, meaning the primary configuration must be Zone-Redundant (ZRS).
ZRS replicates data across three separate zones in the primary region, allowing write operations to continue if one zone goes offline.
2
Analyze secondary region replication requirements.
The data must replicate to a secondary region to protect against regional disasters. This requires geo-replication, pointing to either GZRS or RA-GZRS.
Standard ZRS only protects within a single region and lacks secondary region replication.
3
Evaluate read access requirements and cost constraints.
Read access to the secondary region is not needed unless a failover is initiated, which makes RA-GZRS unnecessary.
GZRS provides the required zone redundancy and geo-replication at a lower cost than RA-GZRS, which provides active read-only endpoints in the secondary region.

Key Concept

Azure storage redundancy tiers (LRS, ZRS, GRS, GZRS) and their recovery characteristics.
Question 470Question

A media streaming company is structuring its Azure environment to support multiple independent engineering teams. Each engineering team has a separate Azure subscription under a single Management Group. You need to design a governance structure that allows a central auditing team to inspect resource configurations across all subscriptions, without granting them permissions to modify any resources or view secrets and keys. The auditing team's membership changes frequently. Which of the following solutions should you recommend to meet these requirements while minimizing administrative overhead?

Show answer & explanation

Answer: Create a Microsoft Entra ID security group, add the auditing team members to the group, and assign the Reader role to the group at the Management Group scope.

Answer

Create a Microsoft Entra ID security group, add the auditing team members to the group, and assign the Reader role to the group at the Management Group scope.
The correct solution uses a Microsoft Entra ID security group to aggregate user accounts, which simplifies access management since membership updates in Entra ID automatically reflect in permissions. Assigning the Reader role at the Management Group scope utilizes Azure's inheritance model to apply the permission across all child subscriptions automatically, fulfilling the requirement for read-only access without access to secrets or modification rights.

Step-by-Step Solution

1
Determine the scope of the role assignment.
Using the Management Group scope ensures that permissions are inherited by all subscriptions nested under it, eliminating the need to assign roles at each subscription individually.
Reduces administrative overhead for multi-subscription environments.
2
Select the appropriate identity principal type.
Group-based assignment is chosen over individual user assignment.
Allows managing membership changes directly in Microsoft Entra ID without modifying Azure RBAC role assignments.
3
Identify the minimum required built-in role.
The Reader role is selected.
Grants read-only access to view resources but does not allow viewing secrets/keys (unlike Reader and Data Access) or modifying resources, adhering to the principle of least privilege.

Key Concept

Azure Management Group Scope and Group-Based RBAC Assignment
Question 471Question

A financial services company is designing a system to process payment transactions from an Azure Service Bus queue using containerized worker applications. The design must satisfy the following requirements:
- Scale the container instances dynamically from 00 to 100100 based on queue message depth.
- Support Kubernetes Event-driven Autoscaling (KEDA) natively without manual agent configuration.
- Minimize administrative effort and cluster management overhead.

Which Azure compute service should you recommend for the containerized worker applications?

Show answer & explanation

Answer: Azure Container Apps

Answer

Azure Container Apps should be recommended because it natively supports event-driven scaling using KEDA (including scaling to zero) while minimizing the operational and administrative effort of managing the underlying cluster infrastructure.
Azure Container Apps is the ideal solution because it is a serverless container hosting service that provides native support for Kubernetes Event-driven Autoscaling (KEDA). This allows the application to scale dynamically from zero to many instances based on queue depth, while completely removing the administrative overhead of managing Kubernetes control planes, node pools, or cluster maintenance.

Step-by-Step Solution

1
Analyze the requirements for container hosting, scaling behavior, and administrative effort constraints.
The workload requires dynamic scaling from 00 to 100100 instances based on queue depth using KEDA, and the team wants to minimize cluster management overhead.
This establishes the key criteria to evaluate against Azure container hosting options.
2
Evaluate the administrative overhead of the candidate services.
Azure Kubernetes Service (AKS) requires managing control planes and node pools, whereas Azure Container Apps (ACA) is a fully managed serverless platform that abstracts the underlying Kubernetes infrastructure.
To satisfy the requirement of minimizing administrative effort, a serverless or managed service is preferred over AKS.
3
Compare scaling capabilities of serverless container options.
Azure Container Apps natively supports KEDA for event-driven scaling and scaling down to zero. Azure Container Instances (ACI) and App Service do not natively support KEDA-based scaling.
This identifies the only service that fulfills both the KEDA auto-scaling requirement and the low administrative overhead goal.

Key Concept

Selecting Azure container hosting services based on scaling requirements (KEDA) and administrative overhead constraints.
Estimated Time:2m 0s
Question 472Question

An enterprise is designing a global disaster recovery and traffic routing solution for a hybrid workload deployed across the East US and West US regions. The workload consists of two primary services:

1. A web application API running on HTTPS that requires Web Application Firewall (WAF) protection, URL path-based routing (routing `/static/*` to storage and `/api/*` to compute), and SSL/TLS termination at the edge.
2. A latency-sensitive database replication daemon communicating over custom TCP port 14331433. The database clients have a legacy configuration that hardcodes or aggressively caches DNS query results, ignoring any DNS Time to Live (TTL) values.

Which two routing and load balancing strategies should you implement to satisfy the requirements for both services?

Select all that apply

Show answer & explanation

Answer: Deploy Azure Front Door for the HTTPS web API to handle SSL/TLS termination, path-based routing, and WAF protection at the global edge.; Deploy an Azure Cross-Region Load Balancer (Global Tier) to expose a single static Anycast IP address for routing the custom TCP port 14331433 traffic.

Answer

Deploy Azure Front Door for the HTTPS web API to handle SSL/TLS termination, path-based routing, and WAF protection at the global edge, and deploy an Azure Cross-Region Load Balancer (Global Tier) to expose a single static Anycast IP address for routing the custom TCP port 14331433 traffic.
The correct architecture combines Azure Front Door and Azure Cross-Region Load Balancer. Azure Front Door handles the HTTPS web API because it is a global Layer 77 service that natively supports TLS termination, path-based routing, and WAF integration. The Azure Cross-Region Load Balancer handles the custom TCP port 14331433 database replication traffic because it operates at Layer 44 and uses Anycast to expose a single static IP address. This static IP ensures that even if clients aggressively cache DNS records and ignore TTL, traffic is automatically rerouted at the network layer to the healthy region during a failover, bypassing the DNS propagation delay entirely.

Step-by-Step Solution

1
Analyze the global routing and feature requirements for the HTTPS web application API.
Identified the need for Layer 77 traffic management including SSL/TLS termination, URL path-based routing, and WAF protection at the edge.
These capabilities require an application-aware global routing service rather than a simple DNS-based or Layer 44 router.
2
Evaluate the network and client constraints for the database replication daemon on port 14331433.
Identified that the daemon runs over a custom TCP port and clients aggressively cache DNS records, ignoring TTL.
This rules out DNS-based load balancing (Azure Traffic Manager) due to failover failure risks, and rules out Azure Front Door because it does not support arbitrary non-HTTP TCP ports.
3
Map the evaluated requirements to optimal Azure global load balancing services.
Select Azure Front Door for the HTTPS Web API and Azure Cross-Region Load Balancer (Global Tier) for the TCP replication daemon.
Azure Front Door delivers Layer 77 global routing and WAF, while Cross-Region Load Balancer uses Anycast-based routing with a static IP to support Layer 44 TCP traffic without relying on DNS updates for failover.

Key Concept

Designing multi-region traffic routing strategies using Anycast IP (Cross-Region Load Balancer) versus Application-layer routing (Azure Front Door) based on protocol (TCP vs HTTPS) and client DNS behavior.
Estimated Time:3m 0s
Question 473Question

A healthcare provider is deploying a multi-tier clinical application across multiple Azure subscriptions under a single management group. The security operations center (SOC) team must be granted permissions to review and update network security rules on all subnets, but only when actively responding to a security incident. The solution must minimize administrative overhead, adhere to the principle of least privilege, and prevent permanent administrative access. Which configuration should you recommend to meet the requirements?

Show answer & explanation

Answer: Create a Microsoft Entra ID group for the SOC analysts. In Microsoft Entra Privileged Identity Management (PIM), configure an eligible assignment for the group to a custom Role-Based Access Control (RBAC) role with network security group rule write permissions, scoped at the management group level.

Answer

Create a Microsoft Entra ID group for the SOC analysts and configure an eligible assignment for the group to a custom Role-Based Access Control (RBAC) role with network security group rule write permissions scoped at the management group level using Microsoft Entra Privileged Identity Management (PIM).
Creating a Microsoft Entra ID security group for the security analysts minimizes overhead by allowing group-based role assignments. Assigning the custom role at the management group level ensures that permissions inherit down to all child subscriptions. Using Privileged Identity Management (PIM) to configure an eligible assignment provides just-in-time access, which satisfies the auditability and least privilege requirements while preventing permanent administrative rights.

Step-by-Step Solution

1
Consolidate the target users into a Microsoft Entra ID security group.
Simplifies administration and governance compared to managing individual user assignments.
Reduces operational overhead and ensures scalability.
2
Define a custom Azure RBAC role containing only the necessary permissions, such as Microsoft.Network/networkSecurityGroups/securityRules/*.
Enforces the principle of least privilege by not granting full network contributor rights.
Limits the security analysts' write permissions specifically to network security group rules.
3
Configure an eligible role assignment for the security group at the management group scope using Privileged Identity Management (PIM).
Grants just-in-time access across all subscriptions via inheritance, requiring active justification and preventing permanent access.
Meets the requirement for auditing and ensuring access is only active when responding to an incident.

Key Concept

Subscription governance and scalable RBAC using Microsoft Entra groups and PIM at the management group level to implement just-in-time administrative access.
Question 474Question

A digital publishing company is implementing a governance policy for external compliance reviewers who need temporary read-only access to all resources in a production subscription. The access must be time-limited, require multi-factor authentication (MFA) and business justification, and minimize administrative overhead by avoiding individual assignment configurations.

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

Select all that apply

Show answer & explanation

Answer: Create a Microsoft Entra security group, assign the Reader role to this group at the subscription scope, and configure the compliance reviewers as eligible members of this group in Privileged Identity Management (PIM).; In the PIM activation settings for the group, require multi-factor authentication (MFA), justification, and set the maximum activation duration to 8 hours.

Answer

Create a Microsoft Entra security group, assign the Reader role to this group at the subscription scope, and configure the compliance reviewers as eligible members of this group in Privileged Identity Management (PIM), and in the PIM activation settings for the group, require multi-factor authentication (MFA), justification, and set the maximum activation duration to 8 hours.
To design a secure, low-overhead solution, you should assign the subscription Reader role to a Microsoft Entra security group and configure the reviewers as eligible members of the group in PIM. This leverages group-based RBAC to keep administrative overhead low. Additionally, you should configure the PIM activation settings for the group to enforce the requirements of multi-factor authentication (MFA), justification, and a maximum activation duration of 8 hours, ensuring time-bound and justified just-in-time access.

Step-by-Step Solution

1
Evaluate the administrative overhead requirement.
Determine that assigning roles directly to individual user accounts scales poorly and increases administrative overhead. Group-based assignment must be used.
Best practice dictates using group-based assignments for RBAC rather than individual assignments to keep governance manageable and scalable.
2
Determine the PIM approach for group-based resources.
Create a Microsoft Entra ID group, assign the subscription Reader role to it, and use PIM for Groups to manage group membership eligibility.
This allows the external reviewers to be added as eligible members who can activate their membership in the group on-demand, which automatically grants them the Reader role at the subscription level.
3
Enforce just-in-time constraints, MFA, and justification.
Configure the PIM group activation settings to require MFA, business justification, and a maximum activation duration of 8 hours.
This ensures that users can only activate their access when needed, must justify it, must perform MFA, and the access automatically expires after 8 hours.

Key Concept

Using Privileged Identity Management (PIM) for Groups to manage membership eligibility with JIT activation settings, combined with group-based Azure RBAC assignment, to enforce least privilege and minimize administrative overhead.
Question 475Question

An organization plans to deploy a containerized order-processing application to Azure. The application must be deployed across two separate regions (East US and West US) to meet local data sovereignty requirements.

The solution must satisfy the following requirements:
- Support event-driven scaling of containers using KEDA.
- Minimize administrative and operational overhead.
- Ensure container logs do not cross regional boundaries.

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

Select all that apply

Show answer & explanation

Answer: Azure Container Apps to host the application containers; A separate Log Analytics workspace in each deployment region

Answer

To meet the requirements, the design should include Azure Container Apps to host the application containers, and a separate Log Analytics workspace in each deployment region.
The correct options are using Azure Container Apps for hosting the containers and setting up a separate Log Analytics workspace in each region. Azure Container Apps provides serverless container hosting that natively supports event-driven scaling using KEDA while minimizing infrastructure management. Using a separate Log Analytics workspace in each region ensures that telemetry and console logs are kept within the respective geographical regions, complying with local data sovereignty requirements.

Step-by-Step Solution

1
Evaluate compute hosting requirements to minimize administrative overhead and support event-driven scaling with KEDA.
Azure Container Apps is selected because it is a serverless platform that supports KEDA scaling natively with lower administrative overhead than Azure Kubernetes Service.
Azure Kubernetes Service requires cluster management and configuration, which increases operational effort.
2
Evaluate logging requirements to ensure compliance with regional data sovereignty limits.
Separate Log Analytics workspaces are selected in East US and West US.
A single centralized workspace would route logs across regional boundaries, violating the requirement to keep logs locally within the region.

Key Concept

Selecting container hosting and monitoring strategies in Azure based on scaling, administrative overhead, and regional compliance requirements.
Estimated Time:1m 0s
Question 476Question

Elysian Healthcare is designing a hybrid identity and access management solution for its Microsoft Entra ID tenant. The organization currently synchronizes user accounts from an on-premises Active Directory Domain Services (AD DS) domain.

The solution must meet the following requirements:
- Users must sign in to cloud services using their on-premises passwords.
- Users must be prompted for multi-factor authentication (MFA) when accessing any Azure management portal from an untrusted network.
- To prevent accidental tenant lockout during a service outage, a dedicated cloud-only emergency-access account must remain functional without MFA requirements.
- Administrative privileges for Azure resources must be granted dynamically on-demand for a limited time rather than being permanently assigned.
- On-premises infrastructure footprint and administrative overhead must be minimized.

Which of the following designs meets all of the requirements?

Show answer & explanation

Answer: Implement directory synchronization using Password Hash Synchronization (PHS). Create a Conditional Access policy requiring MFA for all users that excludes the emergency-access account. Configure Microsoft Entra Privileged Identity Management (PIM) with eligible role assignments.

Answer

Implement directory synchronization using Password Hash Synchronization (PHS). Create a Conditional Access policy requiring MFA for all users that excludes the emergency-access account. Configure Microsoft Entra Privileged Identity Management (PIM) with eligible role assignments.
The correct design utilizes Password Hash Synchronization (PHS) to synchronize on-premises credentials to Microsoft Entra ID with the lowest administrative overhead and server footprint. It implements a Conditional Access policy for MFA that excludes a cloud-only emergency-access account to prevent tenant lockout. Finally, it uses eligible role assignments in Microsoft Entra Privileged Identity Management (PIM) to ensure administrative privileges are requested and granted dynamically on-demand rather than remaining permanently assigned.

Step-by-Step Solution

1
Evaluate the hybrid identity synchronization requirement.
Password Hash Synchronization (PHS) is selected.
PHS allows users to sign in with their on-premises passwords while minimizing on-premises server footprint and administrative overhead compared to Active Directory Federation Services (AD FS).
2
Evaluate the emergency access and Conditional Access requirement.
Excluding the emergency-access account from the MFA Conditional Access policy.
This prevents administrative lockout in the event of an identity synchronization failure or a primary MFA service outage.
3
Evaluate the dynamic administrative access requirement.
Configure Microsoft Entra Privileged Identity Management (PIM) with eligible role assignments.
Eligible assignments require users to explicitly activate their roles on-demand for a limited duration, whereas active assignments make the access permanent.

Key Concept

Microsoft Entra ID Authentication, Conditional Access exclusions, and Privileged Identity Management (PIM) role assignments.
Question 477Question

A digital education company is designing an analytical data platform to process and analyze student interaction logs on Azure. The platform must meet the following requirements:

* Volume & Ingestion: Ingest 3 TB3 \text{ TB} of JSON logs daily at a peak velocity of 2,0002,000 events per second.
* Latency: Raw logs must be queryable via standard SQL within 1515 minutes of ingestion.
* Query Patterns: Daily dashboard queries targeting the last 2424 hours, and monthly exploratory reports analyzing historical data up to 22 years old. Historical reports must execute without manual intervention or data retrieval delays.
* Business Continuity: The analytical data store must remain available and resilient against a primary datacenter outage.
* Cost Optimization: Storage costs must be minimized by automatically moving older data to a lower-cost tier when it is no longer queried by the daily dashboards.

Which design should you recommend for the analytical storage, lifecycle policy, and query engine?

Show answer & explanation

Answer: Store the logs in an Azure Data Lake Storage Gen2 (ADLS Gen2) account configured with Read-Access Geo-Redundant Storage (RA-GRS). Implement a lifecycle policy to transition logs older than 30 days to the Cool tier, and use an Azure Synapse Analytics serverless SQL pool to execute the monthly historical reports.

Answer

The correct architecture uses Azure Data Lake Storage Gen2 configured with Read-Access Geo-Redundant Storage, transitions older data to the Cool tier using a lifecycle policy, and queries it with an Azure Synapse Analytics serverless SQL pool.
The correct design uses Azure Data Lake Storage Gen2 (ADLS Gen2) with Read-Access Geo-Redundant Storage (RA-GRS) to provide regional disaster resilience. To optimize costs without delaying reports, logs older than 30 days are automatically transitioned to the Cool tier (since Archive tier data requires a multi-hour rehydration process). Monthly exploratory reports are run using a serverless SQL pool, which is cost-effective for infrequent, ad-hoc queries because it does not require a provisioned, running cluster.

Step-by-Step Solution

1
Select the correct storage redundancy model.
Read-Access Geo-Redundant Storage (RA-GRS) is selected to ensure resilience against a primary datacenter outage.
Locally Redundant Storage (LRS) only replicates data within a single datacenter, failing the business continuity requirement.
2
Select the lifecycle storage tier for historical data.
The Cool tier is selected for archiving data older than 30 days.
The Archive tier introduces rehydration latency (several hours), which violates the requirement that monthly reports must run without manual intervention or data retrieval delays.
3
Select the query engine for ad-hoc monthly reporting.
Azure Synapse Analytics serverless SQL pool is selected.
Dedicated SQL pools require active compute provisioning and are inefficient for ad-hoc, monthly exploratory queries over raw files in ADLS Gen2, whereas serverless SQL pools execute queries on-demand and charge based on data processed.

Key Concept

Data Integration and Analytical Storage architecture design combining cost optimization, redundancy, lifecycle management, and query model selection.
Question 478Question

NovaPharm Logistics is designing a storage architecture for a new pharmaceutical inventory tracking system. The system writes transaction logs to an Azure Block Blob storage account located in East US. To satisfy regulatory compliance and ensure business continuity, the storage architecture must meet the following requirements:
- Designate West US as the secondary region for disaster recovery.
- Provide read access to the transaction logs in the secondary region with a Recovery Time Objective (RTO) of less than 15 minutes if the primary region experiences an outage.
- Permit write operations to the secondary region only after a failover is initiated, while minimizing overall storage costs.

Which replication and failover strategy should you recommend to meet these requirements?

Show answer & explanation

Answer: Configure the storage account to use Read-Access Geo-Redundant Storage (RA-GRS). Redirect read requests to the secondary endpoint during a primary region outage, and initiate a customer-managed failover to restore write capabilities in the secondary region.

Answer

Configure the storage account to use Read-Access Geo-Redundant Storage (RA-GRS). Redirect read requests to the secondary endpoint during a primary region outage, and initiate a customer-managed failover to restore write capabilities in the secondary region.
The correct option satisfies all the requirements. Read-Access Geo-Redundant Storage (RA-GRS) replicates data asynchronously to a secondary region and exposes a secondary read-only endpoint, allowing the application to meet the 15-minute RTO for reads during an East US outage. To write to the secondary region, a customer-managed failover must be initiated to promote the secondary region to primary.

Step-by-Step Solution

1
Analyze regional availability and read requirements.
Since read access is required in the secondary region (West US) during a primary region outage with a low RTO, a geo-redundant storage tier with read access to the secondary endpoint is necessary.
Standard GRS does not expose a readable secondary endpoint unless a failover is triggered. RA-GRS provides a readable secondary endpoint (accountnamesecondary.blob.core.windows.netaccountname-secondary.blob.core.windows.net) at all times.
2
Evaluate write capabilities in the secondary region.
Write operations to the secondary endpoint are blocked during normal operations.
Azure Storage does not support active-active multi-region writes. The secondary endpoint remains read-only unless a storage account failover is initiated, which promotes the secondary region to be the new primary.
3
Select the most cost-effective option that satisfies all constraints.
RA-GRS meets all recovery and access requirements at a lower cost than zone-redundant options (like RA-GZRS).
LRS does not provide native cross-region replication, and manual replication scripts introduce high RPO/RTO risks and operational costs.

Key Concept

Azure Storage Redundancy and Failover Capabilities
Estimated Time:2m 0s
Question 479Question

A company is planning to deploy two workloads on Azure Virtual Machines:
1. A batch processing job that runs nightly, can be interrupted at any time, and requires minimal costs.
2. A critical customer-facing API that must run continuously with a 99.9% uptime SLA.

Which two of the following virtual machine deployment strategies should you recommend to meet these requirements while minimizing costs? (Select two.)

Select all that apply

Show answer & explanation

Answer: Deploy the nightly batch processing job on Azure Spot Virtual Machines.; Deploy the customer-facing API on standard Azure Virtual Machines distributed across multiple Availability Zones.

Answer

Deploy the nightly batch processing job on Azure Spot Virtual Machines, and deploy the customer-facing API on standard Azure Virtual Machines distributed across multiple Availability Zones.
Deploying the batch processing job on Spot Virtual Machines leverages idle Azure capacity at deep discounts, which is ideal because the workload can tolerate interruptions. Deploying the customer-facing API on standard Virtual Machines across multiple Availability Zones ensures that the production workload meets its 99.9% uptime SLA and remains highly available.

Step-by-Step Solution

1
Analyze the requirements for the nightly batch processing workload.
The workload is non-critical, can tolerate interruptions, and must be highly cost-optimized. This makes it a perfect fit for Azure Spot VMs.
Spot VMs offer up to 90% cost savings compared to pay-as-you-go rates in exchange for the risk of eviction.
2
Analyze the requirements for the customer-facing API.
The API is critical, must run continuously, and requires a 99.9% SLA, which rules out Spot VMs.
Production workloads with strict SLAs require standard VMs with guaranteed runtimes.
3
Identify the high availability solution for the API VM deployment.
Deploying the standard VMs across multiple Availability Zones ensures protection against datacenter failures and meets the high availability SLA.
A single Availability Zone deployment does not protect against localized zone failures.

Key Concept

Selecting VM offerings and redundancy levels based on workload SLA and cost constraints.
Question 480Question

An online gaming company runs its matchmaking database on a single database in Azure SQL Database. You are designing a disaster recovery and high availability solution that replicates database updates to a secondary Azure region. The solution must support automatic failover to the secondary region if the primary region experiences a prolonged outage, without requiring connection string updates in the gaming clients. Additionally, the secondary replica must handle read-heavy analytics queries to offload the primary database. Which database configuration should you recommend?

Show answer & explanation

Answer: Configure a failover group containing the matchmaking database, and configure the analytics clients to connect using the read-only listener endpoint.

Answer

Configure a failover group containing the matchmaking database, and configure the analytics clients to connect using the read-only listener endpoint.
Configuring a failover group meets all requirements. Failover groups provide automatic failover capabilities with predefined grace periods and expose two DNS listener endpoints: a read-write listener and a read-only listener. The read-only listener automatically routes traffic (such as analytics queries) to the secondary database replica, and client connection strings do not need to be updated during or after a failover.

Step-by-Step Solution

1
Analyze the requirements for automatic cross-region failover and the need to preserve client connection strings.
Identify that a feature offering transparent endpoint redirection during failover is required.
This rules out basic active geo-replication, which requires manual failover and changes to client connection strings or custom DNS management.
2
Evaluate how to route the read-heavy analytics queries to the secondary region.
Identify that the solution must provide a read-only endpoint that points to the secondary replica.
Failover groups provide a read-only listener endpoint specifically designed to route read-only workloads to the secondary database replica.
3
Select the Azure SQL Database configuration that satisfies both automatic failover and read-only listener requirements.
Choose a failover group configured with an automatic failover policy.
Failover groups combine automatic failover capabilities with read-write and read-only listener endpoints to meet all constraints.

Key Concept

Azure SQL Database failover groups provide automatic cross-region failover and read-only listener endpoints that simplify client connection management.
Estimated Time:1m 30s
PreviousPage 24 / 60Next