All practice questions

1198 questions

Question 481Question

An enterprise is onboarding an external vendor to perform temporary maintenance on Azure Virtual Machines located in a production resource group. The maintenance window is 30 days. The design must enforce the principle of least privilege, require multi-factor authentication (MFA) and manager approval before accessing the resources, and automatically clean up access after the maintenance period. Which two configurations should you include in the identity governance and privileged access design?

Select all that apply

Show answer & explanation

Answer: Create a Microsoft Entra ID security group for the vendor accounts, and configure the group as eligible for the Virtual Machine Contributor role at the resource group level in Privileged Identity Management (PIM).; Configure PIM role settings for the Virtual Machine Contributor role to require MFA and approval upon activation, and set the assignment duration to expire after 30 days.

Answer

Configure group eligibility for the Virtual Machine Contributor role using PIM, and configure PIM settings to require MFA, manager approval, and an eligibility duration of 30 days.
The correct architecture uses group-based role assignments in Entra ID to simplify management. By configuring the group as eligible in Privileged Identity Management (PIM), the vendor accounts do not hold permanent administrative privileges. Activating the role requires MFA and approval as configured in the role settings, and setting an eligibility lifetime of 30 days ensures access is automatically revoked.

Step-by-Step Solution

1
Consolidate the vendor users into a dedicated Entra ID security group.
Simplifies governance by avoiding direct user role assignments.
Aligns with Microsoft's recommended practice of group-based identity administration.
2
Assign the security group as eligible for the Virtual Machine Contributor role at the resource group scope in PIM.
Ensures the role is not constantly active and can be requested on-demand.
Implements Just-In-Time (JIT) access to enforce the principle of least privilege.
3
Modify the Virtual Machine Contributor role activation settings in PIM to require MFA and approval, and limit the eligibility duration to 30 days.
Enforces strong authentication, administrative oversight, and automatic decommissioning of access.
Meets the specific business requirements of MFA enforcement, approval, and auto-revocation.

Key Concept

Applying Entra ID Privileged Identity Management (PIM) with group-based RBAC to enforce temporary, approved, and authenticated just-in-time administrative access.
Question 482Question

Zenith Financial Services is designing an identity security strategy using Microsoft Entra ID. The design must meet specific access control requirements for various user roles and device states.

Match each business security requirement to the correct Microsoft Entra ID Conditional Access or authentication control.

Click a left item, then click its matching right item

Items

Require user sign-in sessions to Microsoft 365 applications to prompt for re-authentication every 12 hours.
Limit web-based email access to read-only mode and block attachment downloads on unmanaged personal devices.
Allow access to cloud applications only from devices that are registered in Microsoft Entra ID and meet corporate security baselines.
Enforce the use of FIDO2 security keys or Windows Hello for Business when administrators access the Azure portal.

Matches

Show answer & explanation

Answer

The correct matches are: 1) Prompting for re-authentication every 12 hours matches 'Conditional Access session control: Sign-in frequency'. 2) Blocking attachment downloads on personal devices matches 'Conditional Access session control: App enforced restrictions'. 3) Restricting access to compliant devices matches 'Conditional Access grant control: Require device to be marked as compliant'. 4) Requiring FIDO2 or Windows Hello for Business matches 'Conditional Access grant control: Require authentication strength'.
The correct matches map the specific technical capabilities of Microsoft Entra ID to the corresponding business scenarios. Requiring re-authentication after a set timeframe is handled by the Sign-in frequency session control. Restricting specific app actions like downloading email attachments is managed via App enforced restrictions. Allowing access only to healthy devices is enforced through the 'Require device to be marked as compliant' grant control. Restricting the login methods to phishing-resistant mechanisms such as FIDO2 is handled by the 'Require authentication strength' grant control.

Step-by-Step Solution

1
Analyze the requirement for prompting user sessions to re-authenticate every 12 hours.
This relates to session lifetime and re-authentication intervals, which is controlled by the Sign-in frequency session control.
Sign-in frequency determines how long a user's session token is valid before they must authenticate again.
2
Analyze the requirement to restrict email attachment downloads on unmanaged personal devices.
This requires collaborating with the underlying application (Exchange Online) to restrict in-app features based on device compliance, which is managed via App enforced restrictions.
App enforced restrictions allow application-level session controls to be applied dynamically based on the device's status.
3
Analyze the requirement to restrict access only to registered and compliant devices.
This represents a binary grant decision (allow or deny) based on device compliance, which maps to the 'Require device to be marked as compliant' grant control.
Device compliance verification requires MDM enrollment (like Microsoft Intune) to evaluate and report on compliance status.
4
Analyze the requirement to mandate FIDO2 or Windows Hello for Business.
This restricts the permitted authentication methods to phishing-resistant options, which is configured via the 'Require authentication strength' grant control.
Authentication strength allows defining specific authentication method requirements, including custom or pre-defined phishing-resistant policies.

Key Concept

Microsoft Entra ID Authentication and Conditional Access controls (Grant controls vs Session controls)
Estimated Time:1m 30s
Question 483Question

An organization is designing the storage architecture for two Azure General Purpose v2 storage accounts with different business requirements:

* StorageAccount1: Stores machine learning models. The storage must survive a zone failure within the primary region and replicate to a secondary paired region to protect against a regional outage. Read access to the secondary region is not required.
* StorageAccount2: Stores static media assets. The storage must survive a zone failure within the primary region, replicate to a secondary region, and allow the application to read the media assets from the secondary region at any time without triggering a storage failover.

Which two redundancy options should you recommend to meet these requirements?

Select all that apply

Show answer & explanation

Answer: Geo-zone-redundant storage (GZRS) for StorageAccount1; Read-access geo-zone-redundant storage (RA-GZRS) for StorageAccount2

Answer

Geo-zone-redundant storage (GZRS) for StorageAccount1 and Read-access geo-zone-redundant storage (RA-GZRS) for StorageAccount2
The correct options are Geo-zone-redundant storage (GZRS) for StorageAccount1 and Read-access geo-zone-redundant storage (RA-GZRS) for StorageAccount2. GZRS replicates data across three availability zones in the primary region and copies it to a secondary region, which satisfies the zone survival and regional replication requirements for StorageAccount1. RA-GZRS provides the same zonal and regional protection while also enabling read access to the secondary region without failover, satisfying all requirements for StorageAccount2.

Step-by-Step Solution

1
Analyze the requirements for StorageAccount1
StorageAccount1 requires survival of zone outages in the primary region (zonal redundancy) and replication to a secondary region (geo-redundancy), with no secondary read access needed. This points to Geo-zone-redundant storage (GZRS).
GZRS combines the high availability of zone-redundant storage (ZRS) with the disaster recovery of geo-redundant storage (GRS).
2
Analyze the requirements for StorageAccount2
StorageAccount2 requires survival of zone outages in the primary region (zonal redundancy), replication to a secondary region (geo-redundancy), and read access to the secondary region without failover (read-access). This points to Read-access geo-zone-redundant storage (RA-GZRS).
RA-GZRS adds read-only endpoints in the secondary region to GZRS, allowing applications to read data from the secondary region without initiating a failover.

Key Concept

Selecting Azure Storage redundancy tiers to meet availability (zone-redundancy) and disaster recovery (geo-redundancy and read access) requirements.
Question 484Question

A healthcare provider plans to migrate a legacy patient records system to Azure. The system must run on dedicated physical servers that host only this provider's workloads to comply with strict regulatory isolation requirements. The workload is critical and cannot tolerate eviction or interruption. Which Azure compute virtualization solution should you recommend?

Show answer & explanation

Answer: Azure Dedicated Hosts

Answer

Azure Dedicated Hosts
Azure Dedicated Hosts provides physical servers that are dedicated to a single Azure subscription. This ensures that no other tenant's virtual machines run on the same physical hardware, satisfying regulatory compliance requirements, while ensuring the host does not have eviction risks.

Step-by-Step Solution

1
Analyze the isolation requirement
The requirement states that the physical servers must only host the workloads of a single customer.
This rules out multi-tenant Azure virtual machine hosting options.
2
Evaluate the workload reliability requirements
The legacy system is critical and cannot tolerate eviction or interruption.
This rules out options that introduce eviction risk, such as Spot VMs.
3
Select the correct compute hosting solution
Azure Dedicated Hosts provides physical servers dedicated to one Azure subscription, ensuring physical isolation and steady-state reliability.
It satisfies both the regulatory isolation and the continuous availability requirements.

Key Concept

Azure Dedicated Hosts provides hardware-level physical isolation for virtualized workloads.
Question 485Question

You are designing a routing solution for an Azure environment to meet corporate security compliance. The environment contains a virtual network named `vnet-prod-spoke` with an address space of 10.10.0.0/1610.10.0.0/16.

To ensure security inspection, all outbound traffic destined for the internet must be redirected to an on-premises VPN gateway, while virtual machines within `vnet-prod-spoke` must be able to communicate directly with one another.

You create a custom route table and associate it with the subnets in `vnet-prod-spoke`.

Which route configuration should you add to the route table to meet these requirements?

Show answer & explanation

Answer: A route for 0.0.0.0/00.0.0.0/0 with a next hop type of Virtual Network Gateway.

Answer

A route for 0.0.0.0/00.0.0.0/0 with a next hop type of Virtual Network Gateway.
The correct configuration is a route for 0.0.0.0/00.0.0.0/0 with a next hop type of Virtual Network Gateway. Under Azure's routing rules, the longest prefix match determines which route is selected. Since the virtual network's default system route of 10.10.0.0/1610.10.0.0/16 is more specific than the default route 0.0.0.0/00.0.0.0/0, traffic destined for resources inside the virtual network will be routed locally, while all other traffic (internet-bound) will be forwarded to the Virtual Network Gateway.

Step-by-Step Solution

1
Identify the target prefix for all internet-bound traffic.
The target prefix representing all destinations outside the virtual network (the default route) is 0.0.0.0/00.0.0.0/0.
Redirection of all internet traffic requires a default route that matches any destination not covered by more specific routes.
2
Determine the next hop type to direct traffic to the on-premises network.
The next hop type must be set to Virtual Network Gateway.
A VPN gateway or ExpressRoute gateway is represented in Azure routing tables by the Virtual Network Gateway next hop type.
3
Analyze the impact on local traffic routing.
Local traffic within `vnet-prod-spoke` matches the system-defined local route (10.10.0.0/1610.10.0.0/16 -> Local). Since 10.10.0.0/1610.10.0.0/16 is a longer (more specific) prefix than 0.0.0.0/00.0.0.0/0, Azure will prioritize the local route for internal communication.
Azure routing logic always uses the longest prefix match (LPM) to select the route, so no additional route is needed for local traffic.

Key Concept

Azure uses the longest prefix match (LPM) algorithm to select routes. A user-defined route (UDR) for a broad prefix like 0.0.0.0/00.0.0.0/0 does not override more specific system routes, such as the local virtual network route.
Question 486Question

A financial services company is designing the storage infrastructure for a transaction auditing application in Azure. The application writes transaction logs to a standard General Purpose v2 (GPv2) storage account. The design must satisfy the following resilience requirements:

- Data must remain highly available even if an entire datacenter within the primary Azure region suffers a catastrophic power or cooling failure.
- In the event of a complete regional outage affecting the primary Azure region, the data must be recoverable from a secondary paired region.

Which two redundancy options should you recommend to meet these requirements?

Select all that apply

Show answer & explanation

Answer: Geo-zone-redundant storage (GZRS); Read-access geo-zone-redundant storage (RA-GZRS)

Answer

The correct redundancy options are Geo-zone-redundant storage (GZRS) and Read-access geo-zone-redundant storage (RA-GZRS).
To survive a datacenter-level outage in the primary region, the storage account must use zone redundancy (ZRS) in the primary region. To protect against a regional disaster, it must replicate to a secondary region. The configurations that provide both primary zone-redundancy and secondary regional replication are Geo-zone-redundant storage (GZRS) and Read-access geo-zone-redundant storage (RA-GZRS).

Step-by-Step Solution

1
Analyze the primary region resilience requirement.
The requirement states that data must survive the failure of an entire datacenter within the primary region, which necessitates zone redundancy.
Zone-redundancy replicates data across multiple availability zones within a region, protecting against single-datacenter outages.
2
Analyze the regional resilience requirement.
The requirement states that data must be recoverable from a secondary paired region during a complete regional outage, which necessitates geo-redundancy.
Geo-redundancy asynchronously replicates data to a secondary paired region to protect against region-wide outages.
3
Determine which storage redundancy options satisfy both the zone redundancy and geo-redundancy requirements.
Geo-zone-redundant storage (GZRS) and Read-access geo-zone-redundant storage (RA-GZRS) are identified as the correct options.
Both configurations replicate data across three availability zones in the primary region and replicate it to a secondary paired region. Read-access geo-redundant storage (RA-GRS) fails the zone-redundancy requirement in the primary region, and Zone-redundant storage (ZRS) fails the geo-redundancy requirement.

Key Concept

Selecting Azure Storage redundancy options that combine availability zone protection in the primary region with asynchronous replication to a secondary region.
Question 487Question

A logistics company is designing a hosting solution for a new containerized web API. The API is packaged as a single Docker container. The workload must support scaling down to zero instances when idle to minimize costs, and the solution must require the lowest administrative overhead. Which service should you recommend?

Show answer & explanation

Answer: Azure Container Apps

Answer

Azure Container Apps
Azure Container Apps is the ideal solution because it provides a serverless platform designed for containerized microservices and APIs. It allows scaling down to zero instances during idle periods to eliminate compute costs, while removing the administrative burden of provisioning and managing clusters or virtual machines.

Step-by-Step Solution

1
Analyze the workload requirements
The application is a single containerized web API that requires request-driven scaling (including scaling to zero) and must be managed with minimal administrative effort.
Understanding the scaling pattern and management constraints helps narrow down the appropriate Azure container hosting options.
2
Evaluate Azure container hosting services against requirements
Azure Container Apps provides serverless container hosting, request-based scaling to zero, and low administrative overhead. Azure Kubernetes Service (AKS) requires cluster management and has high overhead. Azure Virtual Machines with Spot VMs cannot guarantee availability and do not scale to zero natively. Azure Functions introduces execution timeout limitations and code modification overhead.
Comparing the capabilities of each candidate service ensures the selected solution satisfies all design constraints.

Key Concept

Selecting the appropriate Azure container hosting service based on scaling requirements and administrative overhead
Question 488Question

An enterprise is designing a container-based ingestion and processing solution for healthcare telemetry data. The telemetry is ingested in two distinct geographical regions: East US and West US. The design must accommodate the following requirements:

- Workload 1: A lightweight microservice that processes telemetry messages from an Azure Service Bus queue. The workload must support event-driven scaling using KEDA, including scaling to zero instances when no messages are present, while minimizing infrastructure management overhead.
- Workload 2: A batch processing job that runs model training algorithms. The job requires custom access to the underlying Kubernetes API to orchestrate child pods across dedicated, physically isolated compute nodes.
- Logging: Container logs from the East US and West US regions must be kept strictly segregated within their respective geographical boundaries to comply with local healthcare privacy and data residency laws.

Which three design decisions should you recommend?

Select all that apply

Show answer & explanation

Answer: Deploy Workload 1 to Azure Container Apps.; Deploy Workload 2 to Azure Kubernetes Service (AKS).; Provision two separate regional Log Analytics workspaces to store container logs.

Answer

Deploy Workload 1 to Azure Container Apps, deploy Workload 2 to Azure Kubernetes Service (AKS), and provision two separate regional Log Analytics workspaces.
The correct design decisions are to deploy Workload 1 to Azure Container Apps, deploy Workload 2 to Azure Kubernetes Service (AKS), and provision two separate regional Log Analytics workspaces. Azure Container Apps is optimized for microservices requiring event-driven scaling (KEDA) and scaling to zero without the administrative overhead of managing clusters. Azure Kubernetes Service (AKS) is required for Workload 2 because it exposes direct access to the Kubernetes API for pod orchestration and supports dedicated physical hosts for compute isolation. Separate regional Log Analytics workspaces are necessary to satisfy strict regional data residency and isolation compliance requirements, preventing cross-region log replication.

Step-by-Step Solution

1
Analyze requirements for Workload 1.
Workload 1 needs event-driven scaling (KEDA), scale-to-zero capability, and minimal administrative overhead.
Azure Container Apps natively supports KEDA and scaling to zero without the overhead of cluster management, making it the best fit.
2
Analyze requirements for Workload 2.
Workload 2 requires direct access to the Kubernetes API and physical isolation on dedicated hosts.
Azure Kubernetes Service (AKS) supports dedicated hosts and exposes the Kubernetes API, whereas Azure Container Apps abstracts the control plane and does not allow Kubernetes API access.
3
Analyze regional compliance and data residency requirements.
Logs from East US and West US must be kept strictly segregated within their geographical boundaries.
Two separate regional Log Analytics workspaces must be provisioned to ensure data residency compliance, avoiding a single centralized workspace.

Key Concept

Selecting container hosting solutions (Azure Container Apps vs. Azure Kubernetes Service) based on scaling, API access, and infrastructure overhead constraints, combined with regional log segregation for compliance.
Estimated Time:3m 0s
Question 489Question

You are designing a backup solution for an Azure Virtual Machine hosting a critical line-of-business (LOB) application. The virtual machine is configured with Premium SSD v2 managed disks.

The backup solution must satisfy the following requirements:
- Recoveries from any backup created within the last 4545 days must achieve a recovery time objective (RTO) of under 55 minutes by restoring directly from local snapshots.
- Backup data must be replicated to a secondary region to protect against regional outages.
- Daily backups must be retained for 9090 days, and monthly backups must be retained for 11 year.
- The solution must minimize cost while meeting the technical capabilities of the storage and backup services.

Which backup configuration should you recommend to meet these requirements?

Show answer & explanation

Answer: An Enhanced backup policy in a Recovery Services vault configured with Geo-Redundant Storage (GRS), with the instant restore snapshot retention set to 3030 days, and the remaining daily and monthly recovery points retained in the Vault-standard tier.

Answer

An Enhanced backup policy in a Recovery Services vault configured with Geo-Redundant Storage (GRS), with the instant restore snapshot retention set to 3030 days, and the remaining daily and monthly recovery points retained in the Vault-standard tier.
The correct configuration uses an Enhanced backup policy in a Recovery Services vault with geo-redundant storage (GRS) and sets the instant restore snapshot retention to the maximum supported limit of 3030 days. Standard backup policies do not support Premium SSD v2 managed disks. While the requirement specifies instant recovery for up to 4545 days, the platform limit for instant restore snapshot retention in an Enhanced policy is 3030 days. Setting the retention to 3030 days satisfies the requirement to the maximum extent possible, with older recovery points stored in the Vault-standard tier.

Step-by-Step Solution

1
Identify the disk types and select the appropriate backup policy type.
Since the VM uses Premium SSD v2 managed disks, an Enhanced backup policy must be used. Standard backup policies do not support Premium SSD v2, Ultra Disk, or Shared Disks.
Azure Backup requires the Enhanced policy to protect VMs using advanced disk types.
2
Evaluate the instant restore (snapshot-tier) retention limitations.
The requirement asks for 4545 days of instant recovery from local snapshots. However, the maximum supported instant restore retention for an Enhanced policy is 3030 days. Therefore, the policy must be configured with a 3030-day instant restore retention, which is the maximum possible.
Configuring a value higher than 3030 days in the policy will result in a configuration error.
3
Select the correct vault type and redundancy settings.
The backups must be stored in a Recovery Services vault configured with Geo-Redundant Storage (GRS).
Recovery Services vaults are used for Azure VM backups, and GRS satisfies the requirement for regional resilience.

Key Concept

Azure VM Enhanced backup policy disk support and instant restore limits
Estimated Time:2m 30s
Question 490Question

An online gaming company is architecting a storage backend for a global multiplayer game. The system must store real-time player matchmaking states in Azure Cosmos DB for NoSQL and deliver daily activity reports to customers via Azure Blob Storage.

The architecture must meet the following requirements:
- The Cosmos DB container must support a workload of 80% writes and 20% reads, achieving a 99.999% write availability SLA.
- The partition key for the matchmaking container must prevent hot partitions during peak tournament times when specific matchmaking pools experience massive spikes in active updates.
- Database backups must survive a regional disaster.
- Access to the daily activity reports in Blob Storage must be granted to client applications using Shared Access Signature (SAS) tokens that can be easily revoked in case of compromise without disrupting other services.

Which configuration should you recommend?

Show answer & explanation

Answer: Configure the Cosmos DB account with multi-region writes, partition the container using the matchmaking session identifier, use geo-redundant backup storage, and manage Blob Storage SAS access with a stored access policy.

Answer

Configure the Cosmos DB account with multi-region writes, partition the container using the matchmaking session identifier, use geo-redundant backup storage, and manage Blob Storage SAS access with a stored access policy.
The correct design uses multi-region writes to satisfy the 99.999% write availability SLA, partitions the container using the high-cardinality matchmaking session identifier to distribute write throughput evenly across physical partitions, uses geo-redundant backup storage to survive regional disasters, and leverages a stored access policy for Shared Access Signatures (SAS) to allow clean revocation of client access.

Step-by-Step Solution

1
Select the write replication configuration for the database.
Enable multi-region writes on the Azure Cosmos DB account.
Azure Cosmos DB single-region write configurations only provide a 99.99% write availability SLA. To achieve a 99.999% SLA for write operations, multi-region writes are required.
2
Determine the partition key strategy for the NoSQL container.
Choose the high-cardinality matchmaking session identifier.
Choosing a low-cardinality key like a geographic region will concentrate write operations onto a limited number of physical partitions, causing hot partitions and Request Rate Too Large exceptions.
3
Select backup redundancy and access token policies.
Choose geo-redundant backup storage and use a stored access policy for SAS tokens.
Geo-redundancy ensures backups survive regional datacenter loss. A stored access policy allows instant revocation of SAS tokens by changing the policy configuration, avoiding the need to rotate account master keys.

Key Concept

Azure Cosmos DB and NoSQL Solutions
Question 491Question

A retail corporation is designing an analytical data platform on Azure to analyze sales transactions. The solution must meet the following requirements:
- Ingest 100 GB100\text{ GB} of CSV and Parquet files daily into Azure Data Lake Storage Gen2 (ADLS Gen2), with a total historical volume of 50 TB50\text{ TB}.
- Enable data analysts to perform ad-hoc exploratory queries directly on the data lake files without provisioning or managing pre-allocated compute resources.
- Protect the data against both localized zone failures and regional disasters.
- Provide external auditors with read-only access to a specific folder in the data lake for 3030 days, with the ability to immediately revoke access if necessary.

Which two options should you include in the recommendation to meet these requirements?

Select all that apply

Show answer & explanation

Answer: Configure the ADLS Gen2 storage account to use Read-Access Geo-Zone-Redundant Storage (RA-GZRS), and use Azure Synapse Analytics serverless SQL pools for the ad-hoc exploratory queries.; Create a stored access policy on the target folder container, and generate a Shared Access Signature (SAS) token linked to this policy to provide access to the external auditors.

Answer

Configure the Azure Data Lake Storage Gen2 account to use Read-Access Geo-Zone-Redundant Storage (RA-GZRS), use Azure Synapse Analytics serverless SQL pools for ad-hoc exploratory queries, and use a stored access policy linked to a Shared Access Signature (SAS) to grant the external auditors access.
The requirement for high availability and disaster recovery across zone and regional outages is satisfied by using Read-Access Geo-Zone-Redundant Storage (RA-GZRS), which replicates data across multiple zones in the primary region and to a secondary region. The requirement for ad-hoc queries without pre-allocated compute is met by Azure Synapse Analytics serverless SQL pools, which query data directly in the data lake without provisioning compute resources. The requirement for revokable access is met by generating a Shared Access Signature (SAS) linked to a stored access policy, allowing direct revocation of access by modifying or deleting the policy.

Step-by-Step Solution

1
Analyze the storage redundancy and disaster recovery requirement.
Identify that Locally Redundant Storage (LRS) is insufficient for regional disaster resilience and zone failures. Read-Access Geo-Zone-Redundant Storage (RA-GZRS) is required.
RA-GZRS replicates data across availability zones in the primary region and geo-replicates it to a secondary region.
2
Analyze the compute model for ad-hoc queries.
Select Azure Synapse Analytics serverless SQL pools instead of dedicated SQL pools.
Serverless SQL pools allow querying files directly in Azure Data Lake Storage Gen2 without provisioning persistent compute resources, whereas dedicated SQL pools require provisioned compute clusters.
3
Determine the secure temporary access mechanism.
Recommend using a Shared Access Signature (SAS) linked to a stored access policy.
A stored access policy allows the immediate revocation of the SAS by altering or deleting the policy, which is not possible with an ad-hoc SAS unless the storage account keys are rotated.

Key Concept

Designing highly available, cost-effective analytical storage solutions on Azure utilizing Synapse serverless SQL pools and securing access using stored access policies.
Question 492Question

A global manufacturing company is designing an identity governance and access solution for its IT operations team. The team needs to occasionally perform security administrator tasks in Microsoft Entra ID. The solution must ensure that administrative permissions are not active by default, require multi-factor authentication (MFA) and a business justification to activate, and follow administrative best practices for scalability. Additionally, the company wants to ensure that their disaster recovery planning includes preventing tenant lockout for their break-glass accounts. Which of the following designs should you recommend to meet these requirements?

Show answer & explanation

Answer: Create a Microsoft Entra ID security group, assign the IT operations team members to the group, configure the group as eligible for the Security Administrator role in Privileged Identity Management (PIM), and exclude emergency access accounts from the administrative Conditional Access MFA policies.

Answer

Create a Microsoft Entra ID security group, assign the IT operations team members to the group, configure the group as eligible for the Security Administrator role in Privileged Identity Management (PIM), and exclude emergency access accounts from the administrative Conditional Access MFA policies.
The correct design creates a Microsoft Entra ID security group for group-based PIM assignment, configures eligibility to ensure just-in-time access, and excludes emergency access accounts from Conditional Access MFA policies to prevent lockout.

Step-by-Step Solution

1
Evaluate group-based management for scalable administration of administrative roles in Microsoft Entra ID.
Determine that IT operations team members must be placed in a security group rather than assigned roles directly to minimize administrative overhead.
Assigning roles directly to individual users violates scalability best practices.
2
Determine the appropriate Privileged Identity Management (PIM) assignment type to satisfy the requirement that permissions are not active by default.
Configure the security group's assignment as eligible rather than permanently active.
Eligible assignments require users to perform just-in-time activation, including justification and MFA, adhering to the principle of least privilege.
3
Identify the configuration needed to prevent tenant lockout during MFA enforcement.
Exclude emergency access (break-glass) accounts from strict Conditional Access MFA policies.
Ensures administrative access to the tenant remains possible even if there is an MFA service disruption or credential loss.

Key Concept

Privileged Identity Management group-based eligibility and emergency access exclusions
Estimated Time:1m 30s
Question 493Question

A digital health platform is designing a containerized microservice-based architecture to process patient data in two regions: North Europe (Ireland) and West Europe (Netherlands). The platform has the following requirements:
- The microservices must scale dynamically from zero based on HTTP traffic and message queue depth.
- You must minimize the administrative effort required to manage container orchestration, patching, and OS maintenance.
- For compliance and data sovereignty reasons, application log data from the Irish region must be strictly segregated at the data-plane level and stored within Ireland, while Netherlands log data must remain within the Netherlands.

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

Select all that apply

Show answer & explanation

Answer: Host the microservices on Azure Container Apps; Provision separate Azure Log Analytics workspaces in the North Europe and West Europe regions

Answer

Host the microservices on Azure Container Apps, and provision separate Azure Log Analytics workspaces in the North Europe and West Europe regions.
Hosting the microservices on Azure Container Apps meets the requirements of running containerized workloads, scaling from zero, and supporting KEDA out-of-the-box while minimizing administrative overhead by using a fully managed serverless platform. Provisioning separate Log Analytics workspaces in the North Europe and West Europe regions ensures compliance with strict data sovereignty and log isolation requirements between the two regions.

Step-by-Step Solution

1
Evaluate the compute options based on administrative effort and autoscaling requirements.
Azure Container Apps is selected because it is a serverless platform that supports event-driven scaling natively and minimizes administrative overhead compared to AKS, which requires manual node and cluster management.
The scenario requires minimizing administrative effort while supporting container scaling based on HTTP traffic and queue depth.
2
Evaluate the monitoring and compliance requirements for log data residency.
Separate Log Analytics workspaces must be deployed in each region (North Europe and West Europe).
Compliance and data sovereignty demand that log data from Ireland and the Netherlands be physically segregated and stored in their respective regions.

Key Concept

Selecting container hosting platforms and designing regional monitoring architectures based on operational overhead and compliance requirements.
Estimated Time:3m 0s
Question 494Question

A company is designing a high availability (HA) and disaster recovery (DR) solution for an on-premises relational database that is being migrated to Azure. The database workload has the following characteristics:
- It requires SQL Server Agent jobs for nightly data maintenance.
- It relies on cross-database queries between three distinct databases.

The DR design must satisfy the following requirements:
- In the event of a regional outage, failover to the secondary region must occur automatically with minimal data loss.
- The application connection strings must remain unchanged after a failover.
- Read-heavy analytics queries must be offloaded to the secondary region to avoid impacting transaction processing.

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

Select all that apply

Show answer & explanation

Answer: Azure SQL Managed Instance configured within an auto-failover group across two regions, using the read-write listener for transactions and the read-only listener for analytics; Global virtual network peering between the delegated subnets of the SQL Managed Instances in both regions to facilitate database replication traffic

Answer

Azure SQL Managed Instance configured within an auto-failover group across two regions, using the read-write listener for transactions and the read-only listener for analytics, along with global virtual network peering between the delegated subnets of the SQL Managed Instances in both regions.
To support SQL Server Agent and cross-database queries, Azure SQL Managed Instance must be selected. To support automatic failover and avoid connection string changes, an auto-failover group must be configured. The auto-failover group provides a read-write listener for transactional workloads and a read-only listener to offload read-heavy analytics to the secondary instance. For the Managed Instances to replicate data, global virtual network peering must be established between the delegated subnets in both regions.

Step-by-Step Solution

1
Analyze the application compatibility requirements.
Since the workload requires SQL Server Agent and cross-database queries, Azure SQL Database (Single/Elastic Pool) is ruled out. Azure SQL Managed Instance is selected as the target database service.
Azure SQL Managed Instance provides near 100% compatibility with on-premises SQL Server features like SQL Agent and cross-database queries.
2
Determine the disaster recovery mechanism.
Auto-failover groups must be configured. They support automatic failover, database-level replication, and provide read-write and read-only listener endpoints.
This configuration meets the requirement for automatic failover without changing application connection strings, and allows routing read-heavy workloads to the secondary instance.
3
Determine the network connectivity requirements.
Configure virtual network peering between the virtual networks containing the delegated subnets of the primary and secondary SQL Managed Instances.
SQL Managed Instance failover groups require direct IP connectivity between the instances, which is established using global virtual network peering or VPN gateways.

Key Concept

Designing high availability and disaster recovery for relational databases on Azure using SQL Managed Instance auto-failover groups and networking prerequisites.
Question 495Question

An enterprise is designing a container-based application on Azure. The application consists of two workloads:

* Workload 1: An API gateway that requires custom Kubernetes Custom Resource Definitions (CRDs) and direct access to the Kubernetes control plane API.
* Workload 2: A queue processing service that scales dynamically based on the count of active messages in an Azure Service Bus queue.

The solution must minimize administrative overhead for Workload 2.

Which two services should you recommend? (Select two.)

Select all that apply

Show answer & explanation

Answer: Azure Kubernetes Service (AKS) for Workload 1; Azure Container Apps for Workload 2

Answer

The correct answers are the options recommending Azure Kubernetes Service (AKS) for Workload 1 and Azure Container Apps for Workload 2.
Azure Kubernetes Service (AKS) is the correct choice for Workload 1 because it provides full access to the Kubernetes control plane API and supports custom Custom Resource Definitions (CRDs). Azure Container Apps is the correct choice for Workload 2 because it natively integrates with KEDA (Kubernetes Event-driven Autoscaling) to scale dynamically based on Azure Service Bus queue length, while minimizing administrative overhead by operating as a serverless container platform.

Step-by-Step Solution

1
Analyze the technical requirements of Workload 1.
Workload 1 requires custom Kubernetes CRDs and direct control plane API access.
These requirements dictate a hosting service that exposes full Kubernetes management capabilities.
2
Compare Azure Kubernetes Service (AKS) and Azure Container Apps (ACA) against the requirements of Workload 1.
Only AKS supports custom CRDs and direct API access, whereas ACA abstracts the control plane and does not support these features.
This identifies the correct compute solution for the first workload.
3
Analyze the requirements and administrative constraints of Workload 2.
Workload 2 requires queue-based autoscaling (KEDA) and must minimize administrative effort.
This helps choose between a serverless container service (ACA) and a fully managed Kubernetes cluster (AKS).
4
Evaluate hosting options for Workload 2.
Azure Container Apps provides built-in KEDA scaling and serverless management, whereas AKS introduces high administrative overhead and ACI lacks native queue-based scaling.
This determines the best hosting service that satisfies both the technical and operational constraints.

Key Concept

Selecting container hosting services based on Kubernetes API access requirements and administrative overhead constraints.
Question 496Question

A healthcare provider is designing an analytical data platform to analyze telemetry from patient monitoring devices. The platform must meet the following requirements:
- Ingest telemetry data at a rate of 1500015{}000 events per second.
- Store raw events in Azure Data Lake Storage (ADLS) Gen2 in JSON format, with an expected annual volume of 100 TB100\text{ TB}.
- Enable analysts to perform ad-hoc, exploratory queries on the raw JSON data with a latency of less than 10 seconds10\text{ seconds}.
- Provide regional disaster resilience for the stored data.
- Minimize administrative overhead and run-time costs.
Which two configurations should you include in the design? (Select two.)

Select all that apply

Show answer & explanation

Answer: Configure the ADLS Gen2 storage account to use Geo-redundant storage (GRS).; Use Azure Synapse Analytics serverless SQL pools to query the raw JSON files in the data lake.

Answer

To satisfy the requirements, the storage account must be configured to use Geo-redundant storage (GRS) for regional disaster resilience, and Azure Synapse Analytics serverless SQL pools must be used to perform ad-hoc queries on the raw JSON files stored in ADLS Gen2.
Geo-redundant storage (GRS) provides the required regional disaster resilience by asynchronously replicating data to a secondary region. Azure Synapse Analytics serverless SQL pools provide an on-demand, serverless query engine to run ad-hoc queries directly on the JSON files stored in ADLS Gen2, minimizing administrative overhead and costs since you only pay for queries executed.

Step-by-Step Solution

1
Determine the data redundancy level required for regional disaster resilience.
Identify that Locally redundant storage (LRS) is insufficient as it does not survive a regional outage, whereas Geo-redundant storage (GRS) provides regional replication.
The solution must withstand a regional disaster, requiring data replication to a secondary region.
2
Determine the query model that minimizes administrative overhead and costs for ad-hoc exploratory queries on raw JSON files.
Select serverless SQL pools instead of dedicated SQL pools.
Serverless SQL pools charge on a per-query basis and do not require provisioning or managing compute clusters, which aligns with the cost-optimization and minimal-overhead goals.

Key Concept

Designing an analytical architecture using Azure Synapse serverless SQL pools for ad-hoc data lake queries and ADLS Gen2 with Geo-redundant storage (GRS) for disaster recovery.
Question 497Question

A company plans to deploy a new public-facing web application on Azure Virtual Machines. The application will run steady-state, predictable workloads 24/7 and requires a guaranteed availability SLA of 99.99%. Which two virtual machine configurations or options should you select to meet these requirements while optimizing costs? (Select two.)

Select all that apply

Show answer & explanation

Answer: Azure Reserved Virtual Machine Instances to reduce compute costs for the predictable workload.; Azure Virtual Machines deployed across multiple Availability Zones to meet the 99.99% availability SLA.

Answer

Select Azure Reserved Virtual Machine Instances to reduce compute costs for the predictable workload, and deploy Azure Virtual Machines across multiple Availability Zones to meet the 99.99% availability SLA.
Azure Reserved Virtual Machine Instances are ideal for steady-state workloads running continuously, as they offer significant discounts for a committed term. To achieve the 99.99% availability SLA, Azure requires virtual machines to be deployed across multiple Availability Zones in a region.

Step-by-Step Solution

1
Analyze the availability requirement.
The application requires a 99.99% availability SLA.
Azure guarantees a 99.99% uptime SLA for virtual machines only when two or more instances are deployed across two or more Availability Zones in the same region.
2
Analyze the cost optimization requirement for a 24/7 steady-state workload.
Azure Reserved Virtual Machine Instances (RIs) should be used.
Reserved Instances allow you to commit to a one-year or three-year plan, providing deep discounts for predictable, continuous compute workloads.
3
Evaluate and rule out incorrect options based on constraints.
Spot VMs and single zone deployments are ruled out.
Spot VMs can be evicted at any time and offer no SLA, making them unsuitable for production workloads. A single zone deployment cannot provide the 99.99% availability SLA.

Key Concept

Designing high-availability and cost-optimized virtual machine solutions using Availability Zones and Reserved Instances.
Question 498Question

A LegalTech company is designing a document indexing and analysis solution on Azure. The architecture must satisfy the following requirements:
- Process uploaded PDF agreements using a custom containerized parser that dynamically scales from zero based on the number of messages in an Azure Storage queue.
- Provide a containerized HTTP API front-end to receive document upload metadata.
- Run all containers on a platform that minimizes operational and infrastructure management overhead.
- Support event-driven autoscaling using KEDA natively without managing virtual machine nodes or Kubernetes control planes.
- Ensure all components are deployed securely with private IP addresses within an Azure Virtual Network.

Which compute solution should you recommend for hosting the containerized parser?

Show answer & explanation

Answer: Azure Container Apps

Answer

Azure Container Apps is the recommended solution because it provides a serverless environment that natively integrates with KEDA for event-driven autoscaling (including scaling to zero), supports deployment into an internal Virtual Network, and eliminates the administrative overhead associated with managing Kubernetes clusters.
The correct answer is Azure Container Apps because it provides a serverless container hosting environment that completely abstracts cluster management. It natively supports event-driven scaling using KEDA, allowing containers to scale to zero when the Azure Storage queue is empty. Furthermore, it supports deployment into an internal Azure Virtual Network, meeting all security and connectivity criteria with minimal operational overhead.

Step-by-Step Solution

1
Analyze the operational constraints
The solution must minimize administrative effort, ruling out solutions that require managing cluster control planes or virtual machine nodes.
This requirement differentiates managed Kubernetes environments from serverless container services.
2
Evaluate autoscaling requirements
The platform must support event-driven scaling using KEDA natively, specifically scaling from and to zero instances based on Azure Storage Queue length.
This rules out standard container instances or web apps that lack native KEDA scaling hooks.
3
Evaluate network isolation requirements
The platform must support deployment within an Azure Virtual Network with private IP addresses.
Both Azure Kubernetes Service and Azure Container Apps support internal virtual network environments, but Azure Container Apps achieves this with much lower operational overhead.

Key Concept

Selecting container compute solutions based on operational overhead and native scaling mechanisms
Question 499Question

NovaHealth Solutions is designing a disaster recovery strategy for its clinical intake application. The application writes transactional check-in records to an Azure Storage account. You need to recommend a storage replication and recovery strategy that meets the following requirements:

* During a primary region outage, existing records must be readable within 15 minutes.
* During a primary region outage, write capabilities for new records must be restored within 1 hour.
* Data loss (RPO) for both reads and writes must be less than 15 minutes.
* Costs must be minimized.

Which storage configuration and disaster recovery strategy should you recommend?

Show answer & explanation

Answer: Configure the storage account to use Read-Access Geo-Redundant Storage (RA-GRS). During a primary region outage, point the application to the secondary read-only endpoint, and initiate a customer-managed failover to make the secondary region the new primary for write operations.

Answer

Configure the storage account to use Read-Access Geo-Redundant Storage (RA-GRS). During a primary region outage, point the application to the secondary read-only endpoint, and initiate a customer-managed failover to make the secondary region the new primary for write operations.
The correct strategy is to use Read-Access Geo-Redundant Storage (RA-GRS) and point the application to the secondary read-only endpoint during an outage to meet the 15-minute read RTO, while initiating a customer-managed failover to restore write capabilities within 1 hour. This ensures zero read downtime and restores write capabilities within the RTO while minimizing storage costs.

Step-by-Step Solution

1
Analyze read availability requirements during a primary outage.
Since existing records must be readable within 15 minutes, Geo-Redundant Storage (GRS) is insufficient because its secondary endpoint is not readable until a failover is completed (which can take up to 1 hour). Read-Access Geo-Redundant Storage (RA-GRS) must be used to provide immediate read access to the secondary region.
RA-GRS provides a secondary read-only endpoint that allows read access even when the primary region is unavailable, satisfying the 15-minute read RTO.
2
Analyze write recovery requirements during a primary outage.
Write capabilities must be restored within 1 hour. A customer-managed failover can be initiated on the RA-GRS storage account, which converts the secondary region into the new primary (with LRS) and restores write capabilities within the 1-hour window.
Before failover, the secondary endpoint of an RA-GRS account is strictly read-only. Initiating the failover changes the storage account type to LRS in the secondary region and opens it for writes.
3
Evaluate cost efficiency constraints.
RA-GRS meets all requirements. Read-Access Geo-Zone-Redundant Storage (RA-GZRS) would also meet the availability requirements but at a higher cost, and there are no requirements for zone-redundancy in the primary region.
To minimize costs, RA-GRS is preferred over RA-GZRS because it does not require zone-redundant storage in the primary region.

Key Concept

Read-Access Geo-Redundant Storage (RA-GRS) replication and customer-managed failover behavior.
Question 500Question

An enterprise designs a hub-and-spoke virtual network topology in Azure to connect cloud workloads with their on-premises datacenter. The hub virtual network, `vnet-hub-core` (10.100.0.0/1610.100.0.0/16), contains an Azure Firewall deployed at 10.100.4.410.100.4.4 and an ExpressRoute virtual network gateway. The spoke virtual network, `vnet-spoke-prod` (10.110.0.0/1610.110.0.0/16), contains a subnet named `snet-app` (10.110.1.0/2410.110.1.0/24). Virtual network peering is established between `vnet-hub-core` and `vnet-spoke-prod` with gateway transit enabled. The ExpressRoute gateway dynamically learns the on-premises database subnet prefix 172.20.100.0/24172.20.100.0/24 and the summary prefix 172.16.0.0/12172.16.0.0/12 via BGP. A custom Route Table is associated with `snet-app` and has gateway route propagation enabled. To ensure all traffic to the on-premises environment is inspected by the firewall, a User-Defined Route (UDR) is added with a destination prefix of 172.16.0.0/12172.16.0.0/12 and next hop address of 10.100.4.410.100.4.4. During auditing, network administrators discover that traffic destined for the database servers at 172.20.100.50172.20.100.50 bypasses the Azure Firewall and is sent directly to the ExpressRoute gateway. Which of the following explains this behavior?

Show answer & explanation

Answer: The dynamically learned BGP route for 172.20.100.0/24172.20.100.0/24 has a longer prefix match than the User-Defined Route for 172.16.0.0/12172.16.0.0/12, causing Azure to prioritize the BGP route.

Answer

The dynamically learned BGP route for 172.20.100.0/24172.20.100.0/24 has a longer prefix match than the User-Defined Route for 172.16.0.0/12172.16.0.0/12, causing Azure to prioritize the BGP route.
In Azure routing, Longest Prefix Match (LPM) is the primary algorithm used to select a route. The destination IP 172.20.100.50172.20.100.50 matches both the User-Defined Route (172.16.0.0/12172.16.0.0/12) and the BGP-learned route (172.20.100.0/24172.20.100.0/24). Because the BGP route has a longer prefix length (/24 vs. /12), Azure selects it. The rule where UDRs take precedence over BGP is only applied as a tie-breaker when the prefix lengths are identical.

Step-by-Step Solution

1
Analyze the destination IP address of the database traffic.
The destination is 172.20.100.50172.20.100.50, which matches both the UDR prefix 172.16.0.0/12172.16.0.0/12 and the BGP prefix 172.20.100.0/24172.20.100.0/24.
Identifying all matching routes in the subnet's routing table is the first step in determining path selection.
2
Evaluate the routes based on Azure's Longest Prefix Match (LPM) rule.
The prefix 172.20.100.0/24172.20.100.0/24 has a length of 24, which is longer (more specific) than the UDR prefix 172.16.0.0/12172.16.0.0/12 with a length of 12.
Azure always evaluates prefix length first; a longer prefix match takes precedence over any other route selection criteria, including route source type.
3
Determine the routing outcome.
Azure selects the /24 BGP route, directing traffic directly to the ExpressRoute gateway and bypassing the firewall next hop specified in the /12 UDR.
This explains the bypass behavior observed by the network administrators.

Key Concept

Azure route selection order and Longest Prefix Match (LPM)
PreviousPage 25 / 60Next