All practice questions

1198 questions

Question 901Question

A biotechnology company is designing an identity governance and privileged access strategy for its Azure environment.

The company has the following requirements:
- A team of five external data scientists must be granted the Virtual Machine Contributor role on a resource group named RG-Research for a duration of six months.
- The external data scientists must only have access when actively performing work, and all access requests must be logged.
- To prevent tenant lockout, the company must maintain two emergency access accounts that are bypassed by standard security controls.
- All administrative role assignments must adhere to the principle of least privilege and scale efficiently without direct user-to-role mappings.

Which two of the following configuration choices should you recommend to meet the requirements? Select TWO.

Select all that apply

Show answer & explanation

Answer: Create a Microsoft Entra ID security group, add the external data scientists to the group, and assign the group as eligible for the Virtual Machine Contributor role in Microsoft Entra Privileged Identity Management (PIM) at the resource group scope.; Configure two emergency access accounts, and exclude these accounts from all Microsoft Entra Conditional Access policies that enforce Multi-Factor Authentication (MFA).

Answer

Create a Microsoft Entra ID security group, add the external data scientists to the group, and assign the group as eligible for the Virtual Machine Contributor role in PIM at the resource group scope. Additionally, configure two emergency access accounts and exclude them from all Conditional Access MFA policies.
The correct architecture requires: (1) using a security group for the external data scientists and configuring it as an eligible assignment in PIM to satisfy scalability and just-in-time (JIT) requirements, and (2) configuring emergency access accounts that are explicitly excluded from MFA policies to prevent lockout during a service disruption.

Step-by-Step Solution

1
Address scalability and JIT access requirements by grouping the external data scientists and using PIM.
By using a Microsoft Entra security group and assigning it to PIM as an eligible assignment, you ensure that access is only activated when needed (JIT) and is managed at the group level rather than directly on individual accounts.
Direct role assignments to users do not scale and are harder to audit, and active assignments bypass PIM's JIT authorization model.
2
Address tenant lockout protection requirements by configuring emergency access accounts.
By excluding the two emergency access accounts from Conditional Access policies enforcing MFA, you ensure administrative access remains possible during MFA service outages.
Failing to exclude emergency accounts from MFA requirements runs the risk of total tenant lockout if the authentication mechanism fails.

Key Concept

Microsoft Entra ID Privileged Identity Management (PIM) and emergency access account administration.
Question 902Question

A healthcare provider is designing a new analytical data solution on Azure to integrate and process telemetry from medical sensors and daily diagnostic reports. The design must satisfy the following technical requirements:

* Diagnostic reports: 800 GB800\text{ GB} of compressed JSON files are uploaded as a batch once every 24 hours24\text{ hours}.
* Exploratory analysis: Data analysts must be able to run ad-hoc, exploratory queries directly against the raw JSON batch files without incurring costs for idle compute resources.
* Disaster recovery: The raw analytical data must be resilient against a regional datacenter failure.
* Access control: External research partners must be granted temporary, read-only access to the raw data files. The access must be immediately revocable at any time without rotating the primary storage account keys.

Which combination of storage redundancy, analytical querying engine, and authorization mechanism should you recommend to meet these requirements?

Show answer & explanation

Answer: Azure Data Lake Storage Gen2 (ADLS Gen2) configured with Geo-Redundant Storage (GRS); Azure Synapse Serverless SQL pool; Shared Access Signature (SAS) tokens associated with a stored access policy.

Answer

Azure Data Lake Storage Gen2 (ADLS Gen2) configured with Geo-Redundant Storage (GRS); Azure Synapse Serverless SQL pool; Shared Access Signature (SAS) tokens associated with a stored access policy.
The correct answer configuration combines Geo-Redundant Storage (GRS) to survive a regional disaster, Azure Synapse Serverless SQL pool to query raw JSON files cost-effectively on an ad-hoc basis, and SAS tokens linked to a stored access policy to ensure access can be immediately revoked without affecting other clients.

Step-by-Step Solution

1
Determine the storage redundancy model based on resiliency requirements.
Locally Redundant Storage (LRS) is ruled out because it does not provide protection against regional datacenter failure. Geo-Redundant Storage (GRS) is selected to ensure data is replicated to a secondary region.
The system must survive a regional datacenter failure, which requires replicating data beyond a single physical region.
2
Evaluate the compute engine trade-offs for exploratory queries on JSON data.
Azure Synapse Serverless SQL pool is selected over Dedicated SQL pool.
Since the queries are ad-hoc and exploratory, serverless SQL pools avoid provisioning persistent resources, billing only for the data processed by the queries, which aligns with minimizing idle compute costs.
3
Select the correct security and revocation mechanism for external partners.
Shared Access Signature (SAS) tokens associated with a stored access policy are chosen over ad-hoc SAS tokens.
A stored access policy allows instantaneous revocation of the SAS tokens by modifying or deleting the policy directly on the container, without disrupting other users or requiring storage account key rotation.

Key Concept

Designing cost-effective, resilient, and secure Azure analytical storage solutions by matching data query patterns with the appropriate compute tier (Serverless SQL vs Dedicated SQL), redundancy options (GRS vs LRS), and secure delegation mechanisms (Stored Access Policies).
Estimated Time:2m 30s
Question 903Question

A global media streaming platform is designing an analytical pipeline to process and analyze content viewing sessions. The platform requires a solution to store and query historical logs with the following characteristics:

* Daily batch uploads of session log files in Parquet format, totaling 5 TB5\text{ TB} of new data per day.
* A total of 800 TB800\text{ TB} of historical logs stored in a central repository.
* Data scientists must run sporadic, ad-hoc exploratory queries to analyze viewing trends, which can tolerate a query latency of up to 30 seconds30\text{ seconds}.
* The architecture must minimize administrative overhead and reduce costs by avoiding continuously running compute resources.
* The storage solution must remain resilient and survive a datacenter outage in the primary region.

Which two components should you include in the storage and query design?

Select all that apply

Show answer & explanation

Answer: An Azure Synapse Analytics serverless SQL pool to query the Parquet files directly; An Azure Data Lake Storage Gen2 account configured with Geo-Redundant Storage (GRS)

Answer

The optimal design includes an Azure Synapse Analytics serverless SQL pool and an Azure Data Lake Storage Gen2 account configured with Geo-Redundant Storage (GRS).
The combination of an Azure Synapse Analytics serverless SQL pool and a Geo-Redundant Storage (GRS) account meets all criteria. The serverless SQL pool allows querying Parquet files in place without maintaining active compute clusters, eliminating idle costs and reducing management overhead. GRS replicates the logs to a secondary region to satisfy the requirement to survive a primary datacenter outage.

Step-by-Step Solution

1
Analyze the query and compute requirements.
The requirements specify sporadic, ad-hoc queries with up to 30 seconds30\text{ seconds} of latency and a constraint to avoid continuously running compute while minimizing administrative overhead.
This points to a serverless query engine rather than a dedicated persistent cluster.
2
Select the query engine.
Azure Synapse Analytics serverless SQL pool is selected because it queries files directly in the data lake, scales dynamically, and bills only for data processed, eliminating idle compute costs.
Dedicated SQL pools require persistent running compute or active management of pause/resume states, which increases overhead and costs.
3
Analyze the storage and resiliency requirements.
The solution must survive a datacenter outage in the primary region.
This rules out Locally Redundant Storage (LRS) and requires a geo-redundant storage option.
4
Select the storage redundancy option.
Azure Data Lake Storage Gen2 with Geo-Redundant Storage (GRS) is selected.
GRS replicates data asynchronously to a secondary region, providing protection against a regional datacenter failure.

Key Concept

Selecting cost-effective analytical query engines and appropriate storage redundancy levels in Azure data architectures.
Question 904Question

You are designing a serverless container solution on Azure. The solution must host microservices with zero cluster management overhead and scale containers automatically based on the number of messages in an Azure Service Bus queue. Which two configurations or services should you recommend?

Select all that apply

Show answer & explanation

Answer: Azure Container Apps to host the microservices; Kubernetes Event-driven Autoscaling (KEDA) scale rules configured on the container app

Answer

Azure Container Apps to host the microservices and Kubernetes Event-driven Autoscaling (KEDA) scale rules configured on the container app
The correct options are to use the serverless hosting platform designed for microservices and its built-in event-driven scaling configuration. Azure Container Apps hosts the microservices without cluster management, and native KEDA integration enables scaling to zero and up based on Service Bus queue depth.

Step-by-Step Solution

1
Analyze the requirements for host architecture.
Identify that serverless container hosting is required to achieve zero cluster management overhead.
Azure Container Apps is Microsoft's recommended serverless platform for microservices when cluster-level administration is not needed.
2
Evaluate the autoscaling requirement.
Identify that event-driven scaling based on queue messages is supported natively through KEDA scale rules.
Azure Container Apps utilizes integrated KEDA for scaling rules based on HTTP traffic, CPU/Memory, or event sources like Azure Service Bus.

Key Concept

Selecting serverless container services and event-driven scaling mechanisms in Azure to minimize operational overhead
Estimated Time:1m 0s
Question 905Question

A financial services firm is designing the storage infrastructure for a new document archiving system. The system will store critical customer statements as Block Blobs in a general-purpose v2 storage account. The design must satisfy the following technical requirements:

- The storage solution must withstand the complete failure of an Azure availability zone in the primary region without any data loss or read/write service disruption.
- To protect against a regional disaster, the data must be replicated to a secondary paired region.
- In the event of a primary region outage, the application must be able to immediately read the archived documents from the secondary region without initiating a storage account failover and without waiting for Microsoft to declare a disaster.

Which redundancy option should you select for the storage account?

Show answer & explanation

Answer: Read-Access Geo-Zone-Redundant Storage (RA-GZRS)

Answer

Read-Access Geo-Zone-Redundant Storage (RA-GZRS)
Read-Access Geo-Zone-Redundant Storage (RA-GZRS) is correct because it uses Zone-Redundant Storage (ZRS) in the primary region to survive a zone outage, replicates the data asynchronously to a secondary region for disaster recovery, and provides a read-only endpoint in the secondary region that is available immediately without initiating a failover.

Step-by-Step Solution

1
Analyze primary region availability requirements.
The requirement to survive a complete availability zone outage in the primary region without service disruption rules out Locally Redundant Storage (LRS) and replication options built on LRS, such as Read-Access Geo-Redundant Storage (RA-GRS). It leaves Zone-Redundant Storage (ZRS), Geo-Zone-Redundant Storage (GZRS), and Read-Access Geo-Zone-Redundant Storage (RA-GZRS) as candidates.
Zonal redundancy is necessary to ensure that data remains online and accessible even if one of the physical datacenters housing the availability zone fails.
2
Analyze regional disaster recovery requirements.
The requirement to replicate data to a secondary region rules out Zone-Redundant Storage (ZRS), which is confined to the primary region. This leaves Geo-Zone-Redundant Storage (GZRS) and Read-Access Geo-Zone-Redundant Storage (RA-GZRS).
Cross-region replication is required to achieve recovery and durability in a secondary region in the event of a disaster affecting the primary region.
3
Analyze secondary region read requirements and failover constraints.
The requirement to read data immediately from the secondary region without initiating a failover or waiting for Microsoft to declare a disaster rules out Geo-Zone-Redundant Storage (GZRS), leaving Read-Access Geo-Zone-Redundant Storage (RA-GZRS) as the only viable option.
Standard geo-redundant options require a failover to switch primary endpoints before the secondary region is readable. Only read-access options (RA-GRS/RA-GZRS) expose a permanent secondary read-only endpoint (-secondary) that applications can query at any time.

Key Concept

Selecting Azure Storage redundancy tiers to meet combined availability, regional disaster recovery, and read-access requirements.
Estimated Time:2m 0s
Question 906Question

A logistics company, Zenith-Fleet, uses an Azure Storage v2 account to store critical telemetry logs. The system has the following requirements:
- Maximum read availability: Reads must be highly available even during a primary region outage.
- Recovery Point Objective (RPO) for writes: Less than 1515 minutes.
- Recovery Time Objective (RTO) for writes: Less than 11 hour.
- Cost: Must minimize cross-region data transfer costs and redundancy costs.

To meet these requirements, the architect configured the account with Read-Access Geo-Redundant Storage (RA-GRS). The primary region (East US) experiences a catastrophic outage. The operations team observes that the storage account's `Last Sync Time` is 88 minutes behind the current time. To restore write access within the RTO, the team plans to initiate a customer-managed failover to the secondary region (West US).

Which of the following correctly describes the write availability, DNS resolution, and redundancy behavior during and after the failover process?

Show answer & explanation

Answer: Write operations to the storage account are unavailable until the failover completes; once completed, the primary endpoint DNS record updates to resolve to the secondary region, write access is restored, and the storage account replication changes to Locally Redundant Storage (LRS).

Answer

Write operations to the storage account are unavailable until the failover completes; once completed, the primary endpoint DNS record updates to resolve to the secondary region, write access is restored, and the storage account replication changes to Locally Redundant Storage (LRS).
During a customer-managed failover of an Azure Storage account, the failover process updates the primary DNS endpoint of the storage account to point to the secondary region. During the failover, write operations are temporarily unavailable. Once completed, the primary endpoint resolves to the new region, write capabilities are restored, and the storage account's replication status is set to Locally Redundant Storage (LRS) in the new primary region.

Step-by-Step Solution

1
Evaluate the RPO and Last Sync Time.
The RPO is 1515 minutes, and the Last Sync Time is 88 minutes behind. Failover is safe to proceed because the expected data loss (88 minutes) is within the RPO limit.
Customer-managed failover is an asynchronous process where any data not yet replicated (indicated by Last Sync Time) will be lost.
2
Determine write availability during the transition.
Write operations are rejected while the failover is actively processing.
The storage account is transitioning DNS and master keys, during which time writes to either region are blocked.
3
Analyze endpoint behavior and DNS propagation post-failover.
The DNS record of the primary endpoint (e.g., `mystorage.blob.core.windows.net`) is updated to resolve to the secondary region's scale units.
Updating the primary endpoint DNS ensures that the application does not need connection string changes to resume reads and writes.
4
Identify the post-failover redundancy state.
The storage account becomes Locally Redundant Storage (LRS) in the new primary region (West US).
Because there is no longer a secondary replica in another region, the redundancy degrades to LRS. Re-enabling geo-redundancy (reprotecting) must be done manually after failover completes.

Key Concept

Azure Storage customer-managed failover mechanics, DNS resolution updates, and post-failover redundancy conversion to LRS.
Estimated Time:3m 0s
Question 907Question

A financial services company is designing a high availability (HA) and disaster recovery (DR) solution for a database workload currently on-premises. The workload requires cross-database queries and SQL Server Agent jobs. The solution must support:

* An RTO of 3030 minutes
* An RPO of 55 seconds
* Automatic failover to a secondary Azure region
* A single connection string that does not change after failover
* Minimal administrative overhead

Which two actions should you recommend to meet the requirements?

Select all that apply

Show answer & explanation

Answer: Deploy Azure SQL Managed Instance as the relational database tier.; Configure an auto-failover group that includes a read-write listener.

Answer

Deploy Azure SQL Managed Instance and configure an auto-failover group with a read-write listener.
To support instance-level features such as SQL Server Agent jobs and cross-database queries with minimal administrative overhead, Azure SQL Managed Instance is required. To meet the DR requirements, which include automatic failover to a secondary region, a 3030-minute RTO, a 55-second RPO, and a single connection string, you must configure an auto-failover group with a read-write listener.

Step-by-Step Solution

1
Evaluate legacy SQL Server feature requirements.
Identify that cross-database queries and SQL Server Agent jobs require Azure SQL Managed Instance rather than Azure SQL Database.
Azure SQL Database single databases and elastic pools do not support cross-database queries and SQL Server Agent jobs natively.
2
Evaluate HA/DR requirements (RTO, RPO, automatic failover, and single connection string).
Determine that an auto-failover group must be configured.
Auto-failover groups provide automatic failover capabilities across regions and offer a single connection endpoint (listener) that redirects traffic without client modification.

Key Concept

Designing high availability and disaster recovery for SQL Server workloads in Azure requiring SQL Agent and cross-database queries using SQL Managed Instance and Auto-Failover Groups.
Question 908Question

You are designing the infrastructure for a database synchronization tool that runs as an Azure Function. The tool is triggered by a webhook and runs for up to 15 minutes per invocation. Which two Azure hosting options should you recommend to support this execution duration while minimizing operational overhead? (Select two.)

Select all that apply

Show answer & explanation

Answer: Azure Functions Premium plan; Azure Functions Dedicated (App Service) plan

Answer

The Azure Functions Premium plan and the Azure Functions Dedicated (App Service) plan are the correct choices because they support execution times longer than 10 minutes while avoiding the high administrative overhead of Azure Kubernetes Service.
The Azure Functions Premium plan and the Azure Functions Dedicated (App Service) plan both support execution durations longer than 10 minutes, making them suitable for the 15-minute runtime of the synchronization tool. They also maintain a low operational overhead, aligning with the requirement to minimize management effort.

Step-by-Step Solution

1
Analyze the execution duration requirement of the workload.
The workload runs for up to 15 minutes per invocation.
This duration exceeds the 10-minute maximum execution limit of the Azure Functions Consumption plan.
2
Evaluate the remaining Azure Functions hosting plans for duration limits.
Both the Premium plan and Dedicated (App Service) plan support execution durations of 15 minutes or longer (Premium is default 30 minutes / unbounded; Dedicated is unbounded).
These plans prevent timeout errors for workloads exceeding 10 minutes.
3
Evaluate alternative hosting options like Azure Kubernetes Service (AKS) against operational requirements.
AKS supports long execution times but introduces high operational overhead for setup, maintenance, and scaling of a cluster.
For a simple database synchronization tool, Azure Functions provides a much simpler management model than AKS.

Key Concept

Selecting appropriate Azure serverless hosting plans based on execution duration limits and operational complexity.
Question 909Question

A healthcare software provider is designing a storage lifecycle strategy for medical imaging files stored in a general-purpose v2 (GPv2) Azure Blob storage account. The access patterns and requirements for the imaging files are as follows:

* For the first 30 days after creation, files are frequently accessed by clinicians and require immediate, sub-second retrieval.
* From day 31 to day 120, files are accessed occasionally for audits. Immediate, sub-second retrieval is still required during this period.
* After 120 days, files must be preserved for historical research. A retrieval latency of up to 15 hours is acceptable for these historical files.
* The solution must minimize storage and transaction costs.

Which lifecycle management policy configuration should you recommend?

Show answer & explanation

Answer: Transition blobs to the Cool tier 30 days after creation, and transition blobs to the Archive tier 120 days after creation.

Answer

Transition blobs to the Cool tier 30 days after creation, and transition blobs to the Archive tier 120 days after creation.
The policy that transitions blobs to the Cool tier after 30 days and to the Archive tier after 120 days is optimal. The Cool tier provides the necessary sub-second access for audit purposes from day 31 to day 120. Moving the data to the Archive tier at day 120 satisfies the 15-hour retrieval tolerance at the lowest storage cost. Because the data resides in the Cool tier for 90 days, it exceeds the Cool tier's 30-day minimum retention threshold, avoiding early deletion fees.

Step-by-Step Solution

1
Analyze access latency requirements across all phases.
Immediate, sub-second retrieval is required from day 0 to day 120. A latency of up to 15 hours is acceptable after day 120.
This rules out placing any data in the Archive tier before day 120, as the Archive tier has retrieval latencies ranging from hours to days.
2
Evaluate storage tier choices for the day 31 to day 120 window.
The Cool tier is chosen over the Hot tier to optimize storage costs, and satisfies the sub-second access requirement.
Both Hot and Cool tiers provide sub-second access, but Cool is cheaper for storage and suitable for data accessed occasionally.
3
Check minimum retention constraints and early deletion charges.
Transitioning from Cool to Archive after 90 days (from day 30 to day 120) avoids early deletion fees.
The Cool tier has a 30-day minimum retention policy. Since the data remains in Cool for 90 days, it avoids charges. Using the Cold tier (90-day minimum retention) and transitioning early would incur penalty fees.

Key Concept

Designing lifecycle management policies that optimize costs by aligning data access tiers with retrieval latency limits and avoiding early deletion penalties.
Estimated Time:2m 0s
Question 910Question

A financial services company is designing a privileged access governance solution for its Azure environment. The solution must meet the following requirements:

* Members of the IT security department must be able to assume the Security Administrator role on a temporary basis, not exceeding 4 hours per session, requiring Multi-Factor Authentication (MFA) and Chief Information Security Officer (CISO) approval.
* An emergency 'break-glass' administrative account must be maintained to prevent tenant lockout, ensuring it is exempt from the standard MFA requirements in the event of an identity provider outage.
* Administrative overhead for managing individual user role assignments must be minimized.

Which combination of configuration actions should you recommend?

Show answer & explanation

Answer: Configure the Security Administrator role in Microsoft Entra Privileged Identity Management (PIM) to require MFA, approval, and a maximum activation duration of 4 hours. Assign the IT security department's Microsoft Entra ID group as eligible for the role. Configure a Conditional Access policy requiring MFA for administrator roles, but exclude the emergency break-glass account from the policy.

Answer

Configure the Security Administrator role in Microsoft Entra Privileged Identity Management (PIM) to require MFA, approval, and a maximum activation duration of 4 hours; assign the group as eligible; and configure a Conditional Access policy requiring MFA while excluding the emergency account.
The correct option addresses all three design goals: it uses Microsoft Entra Privileged Identity Management (PIM) with group-based eligibility (minimizing administrative overhead) and enforces the 4-hour activation limit with CISO approval and MFA. Furthermore, it creates a Conditional Access policy requiring MFA for administrative actions while keeping the emergency break-glass account excluded to prevent tenant lockout.

Step-by-Step Solution

1
Evaluate the requirement for temporary access and approval for the Security Administrator role.
Microsoft Entra Privileged Identity Management (PIM) is identified as the tool to enforce just-in-time (JIT) access, allowing a maximum activation duration of 4 hours, CISO approval, and MFA verification during activation.
PIM role settings allow granular control over role activation parameters including duration and approval workflows.
2
Address the requirement to minimize administrative overhead for role assignments.
The IT security department's group should be assigned as eligible for the role in PIM, rather than assigning individual users.
Group-based role assignment ensures that additions or removals of staff members do not require manual role reconfiguration, simplifying access governance.
3
Review the requirement to protect the emergency account from lockout.
The Conditional Access policy enforcing MFA for administrative roles must explicitly exclude the emergency break-glass account.
Emergency accounts must be accessible even when the primary MFA provider is unavailable; failing to exclude them violates resilience best practices.

Key Concept

Privileged Identity Management (PIM) settings, group-based assignments, and Conditional Access policies with emergency exclusions.
Estimated Time:2m 0s
Question 911Question

A startup is deploying a web application that stores user profile documents in an Azure General Purpose v2 (GPv2) storage account. The design requirements are as follows:

* The documents must remain highly available and survive the loss of an entire availability zone in the primary region without administrative intervention or failover.
* The documents must also be replicated to a secondary region to protect against a regional disaster.
* To control costs, the startup wants the most cost-effective option that meets these requirements and does not require read access to the secondary region under normal operations.

Which redundancy option should you recommend?

Show answer & explanation

Answer: Geo-zone-redundant storage (GZRS)

Answer

Geo-zone-redundant storage (GZRS)
Geo-zone-redundant storage (GZRS) meets all constraints by synchronously replicating data across three availability zones in the primary region (surviving a zonal outage without administrative intervention) and asynchronously replicating it to a secondary region (surviving a regional disaster). Since it does not provide active read access to the secondary region, it is the most cost-effective option that satisfies the requirements.

Step-by-Step Solution

1
Evaluate the primary region resilience requirement.
The primary region must survive an availability zone outage without administrative failover. This requires Zone-redundant storage (ZRS) or Geo-zone-redundant storage (GZRS) as the primary replication mechanism, ruling out Locally redundant storage (LRS) and Geo-redundant storage (GRS).
LRS and GRS replicate data within a single facility in the primary region and cannot tolerate a zonal failure without data unavailability or failover.
2
Evaluate the regional disaster recovery requirement.
The solution must replicate data to a secondary region. This rules out Zone-redundant storage (ZRS) and points to Geo-zone-redundant storage (GZRS) or Read-access geo-zone-redundant storage (RA-GZRS).
ZRS only replicates data within the primary region.
3
Compare the remaining options based on cost and read access requirements.
The startup does not require read access to the secondary region and wants to minimize costs. Geo-zone-redundant storage (GZRS) is selected over Read-access geo-zone-redundant storage (RA-GZRS).
RA-GZRS provides read-only access to the secondary region but is more expensive than GZRS.

Key Concept

Choosing the appropriate Azure Storage redundancy tier based on zonal resilience, regional disaster recovery, and cost considerations.
Question 912Question

An enterprise is designing a data storage solution for a system that generates transactional log blobs in a General-purpose v2 Azure Storage account.

The storage design must meet the following requirements:
* Logs must be accessed frequently and immediately during the first 30 days.
* Between day 31 and day 180, access is infrequent, but any query must return results with sub-second retrieval latency.
* After 180 days, the logs must be retained for a compliance period of 5 years. During this period, retrieval latency of up to 15 hours is acceptable, and storage costs must be minimized.
* The logs must be protected against deletion and modification by all users, including administrators, during the 5-year compliance period.

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

Select all that apply

Show answer & explanation

Answer: Create a lifecycle management rule that transitions blobs to the Cool tier 30 days after creation, and to the Archive tier 180 days after creation.; Configure a locked time-based retention policy on the blob container.

Answer

Configure a lifecycle management rule to transition blobs to the Cool tier after 30 days and the Archive tier after 180 days, and configure a locked time-based retention policy on the container.
The correct strategy combines a lifecycle policy that moves data to the Cool tier after 30 days (supporting sub-second access for infrequent queries) and to the Archive tier after 180 days (minimizing cost when high latency is acceptable). Additionally, to prevent modification or deletion by administrators, a locked time-based retention policy must be configured on the container.

Step-by-Step Solution

1
Analyze retrieval latency requirements for each phase of the data lifecycle.
Identify that the first 30 days require immediate/frequent access (Hot tier), days 31 to 180 require sub-second retrieval (Cool tier), and after 180 days, hours-long latency is acceptable (Archive tier).
This establishes the correct lifecycle transition intervals and prevents placing data in a high-latency tier prematurely.
2
Determine the immutability policy needed to meet the compliance and admin-protection requirements.
Select a locked time-based retention policy rather than a legal hold or unlocked policy.
Locked time-based retention policies strictly prevent modification and deletion of blobs by any user, including administrators, for a defined duration, which satisfies the regulatory requirement.
3
Select the correct combination of lifecycle management rules and immutability settings.
Combine the rule transitioning to Cool at 30 days and Archive at 180 days with the container-level locked time-based retention policy.
This dual-action approach meets both cost-optimization/retrieval speed and strict data compliance requirements.

Key Concept

Azure Blob Storage Lifecycle Management and Immutable Storage Policies
Question 913Question

A logistics company is modernizing a web-based vehicle tracking API hosted on a pool of Azure Virtual Machines in a single region. The API requires SSL/TLS termination and URL path-based routing to direct traffic to different backend pools. The virtual machines are currently configured with Basic SKU Public IP addresses for management. You need to recommend a regional load balancing solution that meets these requirements. Which Azure service should you select?

Show answer & explanation

Answer: Azure Application Gateway (Standard v2)

Answer

Azure Application Gateway (Standard v2) is the correct service because it provides Layer 7 load balancing features, including SSL/TLS termination and URL path-based routing, within a single region. Because it routes traffic to the backend using private IP addresses, it does not conflict with the existing Basic SKU Public IP configurations on the backend virtual machines.
Azure Application Gateway (Standard v2) is designed for regional Layer 7 load balancing. It natively supports SSL/TLS termination and URL path-based routing. Since it forwards traffic to backend VMs via private IP addresses, the SKU of the virtual machines' public IPs does not impact its deployment.

Step-by-Step Solution

1
Analyze protocol and routing requirements.
The application is web-based, requiring Layer 7 features (SSL/TLS termination and URL path-based routing).
This rules out Layer 4 solutions like Azure Load Balancer.
2
Determine the geographic scope of the load balancer.
The workload is located in a single region.
This makes regional load balancers like Azure Application Gateway preferred over global services like Azure Front Door or Azure Traffic Manager.
3
Verify SKU compatibility with existing virtual machine configurations.
Backend virtual machines have Basic SKU Public IPs, which cannot be mixed with a Standard Load Balancer backend pool. However, Azure Application Gateway operates via private IPs and does not trigger this SKU mismatch.
Ensures the selected architecture is valid and will not fail deployment.

Key Concept

Azure Application Gateway is a regional Layer 7 load balancer that supports SSL/TLS termination and URL path-based routing, and it avoids the Basic/Standard SKU mismatch constraint because it routes traffic over private IPs.
Question 914Question

A pharmaceutical company is planning to migrate a proprietary drug-discovery modeling application to Azure. The application has the following requirements:
- The virtual machines must run on hardware dedicated to a single customer at the physical host level to meet compliance standards.
- The workload requires a memory-to-vCPU ratio of at least 88 GiB of RAM per vCPU.
- The workload is steady-state, runs continuously, and cannot tolerate unexpected eviction or downtime.
- The storage layer requires a single disk that provides 10,00010,000 IOPS and 200200 MB/s throughput, with the capability to dynamically scale IOPS without resizing the disk.
- The architecture must guarantee a 99.99%99.99\% VM availability SLA.

Which of the following compute virtualization and storage solutions should you recommend to meet these requirements?

Show answer & explanation

Answer: Azure Dedicated Hosts deploying Esv5-series virtual machines distributed across multiple Availability Zones, using Premium SSD v2 storage.

Answer

Azure Dedicated Hosts deploying Esv5-series virtual machines distributed across multiple Availability Zones, using Premium SSD v2 storage.
The correct option satisfies all constraints: Azure Dedicated Hosts provide the required physical hardware isolation; the Esv5-series VM size provides the minimum 88 GiB of RAM per vCPU; Premium SSD v2 supports 10,00010,000 IOPS and allows independent performance scaling without disk resizing; and distributing VMs across multiple Availability Zones meets the 99.99%99.99\% availability SLA requirement.

Step-by-Step Solution

1
Analyze the tenant isolation and workload characteristics.
Single-tenant physical host isolation requires Azure Dedicated Hosts, which rules out public multi-tenant virtual machines and Spot VMs.
Regulatory compliance demands dedicated hardware, and the steady-state nature rules out Spot VMs due to eviction risk.
2
Determine the memory and virtual machine series requirements.
A memory-to-vCPU ratio of 88 GiB requires a memory-optimized VM family like the Esv5-series, which is supported on Azure Dedicated Hosts.
General-purpose (D-series) or compute-optimized (F-series) families do not meet the minimum 88 GiB per vCPU requirement.
3
Evaluate storage performance and scaling capabilities.
Premium SSD v2 is selected because it supports provisioning up to 80,00080,000 IOPS and allows independent tuning of IOPS and throughput without resizing the disk.
Standard SSDs do not scale to 10,00010,000 IOPS, and Standard/Premium SSD v1 requires expanding disk size to increase performance limits.
4
Validate the SLA and high availability design.
Distribute the Azure Dedicated Hosts and corresponding virtual machines across at least two Availability Zones.
A 99.99%99.99\% SLA for Azure VMs requires instances to be deployed across two or more Availability Zones in the same region.

Key Concept

Designing compute virtualization using Azure Dedicated Hosts, memory-optimized VM sizes, Premium SSD v2, and multi-zone high availability to meet SLA, compliance, and performance requirements.
Estimated Time:2m 30s
Question 915Question

Apex Aerospace is designing a Microsoft Entra ID identity strategy. The organization plans to implement a strict Conditional Access policy that requires Multi-Factor Authentication (MFA) for all administrative roles. The security team wants to ensure that administrators can still access the tenant to resolve configuration issues or during a cloud-based MFA service outage. Which design option should you recommend?

Show answer & explanation

Answer: Create two dedicated emergency access accounts, assign them the Global Administrator role, and exclude them from the Conditional Access policies requiring MFA.

Answer

Create two dedicated emergency access accounts, assign them the Global Administrator role, and exclude them from the Conditional Access policies requiring MFA.
Creating dedicated emergency access accounts (break-glass accounts) and excluding them from the Conditional Access policies that enforce MFA ensures that administrators have a fallback mechanism to sign in and resolve configuration issues or outages without requiring MFA.

Step-by-Step Solution

1
Analyze the lockout risk associated with enforcing MFA on all administrative accounts.
Identify that a service outage or misconfiguration affecting Microsoft Entra MFA would prevent all administrators from signing in.
This establishes the need for a bypass or recovery mechanism that does not depend on MFA.
2
Evaluate Microsoft's best practices for tenant emergency management.
Determine that Microsoft recommends creating at least two dedicated emergency access accounts (break-glass accounts) that are highly monitored, rarely used, and excluded from MFA requirements.
Excluding these accounts from Conditional Access MFA policies ensures they can authenticate even if the MFA service is entirely unavailable.
3
Select the option that aligns with the emergency access account configuration.
Select the option advocating for the creation and exclusion of emergency access accounts.
This meets the security and availability requirements without introducing unnecessary hybrid infrastructure like AD FS or violating least privilege via PIM active assignments.

Key Concept

Microsoft Entra ID emergency access accounts
Estimated Time:2m 0s
Question 916Question

You are designing a global database solution using Azure Cosmos DB. You need to match the specific application requirements on the left to the appropriate Azure Cosmos DB consistency level on the right that meets those requirements with the lowest latency and highest availability.

Click a left item, then click its matching right item

Items

A financial reporting application requiring that reads never see out-of-order updates, and replication lag must not exceed 55 minutes or 100,000100,000 operations.
A stock trading platform where all reads across all regions must return the absolute latest, committed write, accepting higher latency and lower availability.
A collaborative document editing application where users must always read their own writes immediately, but other users can see updates with a slight delay.
A blog comments section where comments must appear in the order they were posted, but there is no requirement for real-time synchronization.

Matches

Show answer & explanation

Answer

The collaborative document editor matches Session consistency. The financial reporting application matches Bounded Staleness consistency. The stock trading platform matches Strong consistency. The blog comments section matches Consistent Prefix consistency.
Each application requirement matches the most cost-effective and performant consistency level that satisfies its specific ordering and latency constraints. Strong consistency is used for absolute real-time correctness; Bounded Staleness for predictable regional lag limits; Session for read-your-own-writes session isolation; and Consistent Prefix for basic sequence preservation without real-time synchronization.

Step-by-Step Solution

1
Analyze the collaborative document editor requirement for reading own writes.
Identify Session consistency as it provides the read-your-own-writes guarantee within a client session at low latency.
Session consistency is the default and optimized level for user-specific write-to-read flows.
2
Analyze the financial reporting application requirement for bound operations and time limits.
Identify Bounded Staleness consistency as it explicitly bounds lag by operations (KK) or time (TT).
This consistency level is designed specifically for applications that can tolerate some staleness but need a strict SLA on how far behind reads can be.
3
Analyze the stock trading platform requirement for absolute latest reads.
Identify Strong consistency as it ensures linearizability across all regions.
Strong consistency guarantees that a read always returns the most recent write, which is critical for financial transactions where stale reads are unacceptable.
4
Analyze the blog comments requirement for ordered but delayed updates.
Identify Consistent Prefix consistency as it guarantees that updates are returned in order without out-of-sequence anomalies.
Consistent Prefix is the lowest latency consistency model that still guarantees sequence preservation, preventing comments from appearing out of order.

Key Concept

Azure Cosmos DB Consistency Levels
Question 917Question

An Azure Solutions Architect is designing the storage architecture for a global telehealth application. The application must ingest real-time patient health telemetry from 5 million wearable devices distributed globally, with a read/write ratio of 10%10\% reads to 90%90\% writes. The data storage solution must meet a 99.99%99.99\% availability SLA. Real-time metrics must be stored in Azure Cosmos DB (NoSQL API), while weekly diagnostic report files must be uploaded by the devices directly to Azure Blob Storage. The architecture must satisfy the following requirements:
- Prevent database hot partitions during high-frequency write operations.
- Ensure the weekly diagnostic reports survive a primary datacenter outage.
- Secure device access to the Blob Storage account while minimizing administrative overhead and enabling token revocation.

Which design configuration should you recommend?

Show answer & explanation

Answer: Partition the Cosmos DB container using the device ID, configure Geo-Redundant Storage (GRS) for the Blob Storage account, and issue short-lived Shared Access Signatures (SAS) generated dynamically via a user delegation key.

Answer

Partition the Cosmos DB container using the device ID, configure Geo-Redundant Storage (GRS) for the Blob Storage account, and issue short-lived Shared Access Signatures (SAS) generated dynamically via a user delegation key.
The correct configuration uses the device ID as the partition key because it has high cardinality, which distributes the high write load evenly. Geo-Redundant Storage (GRS) is used to replicate weekly reports to a secondary region, providing protection against datacenter failures. Generating short-lived SAS tokens dynamically via user delegation keys ensures client access is temporary, secure, and easily managed via Entra ID.

Step-by-Step Solution

1
Select the partition key for Azure Cosmos DB.
Choose the device ID.
Since there are 5 million devices, device ID provides a high-cardinality key that distributes writes evenly across logical partitions, avoiding hot partitions.
2
Select the redundancy tier for Azure Blob Storage.
Choose Geo-Redundant Storage (GRS).
To survive a primary datacenter outage, GRS replicates data synchronously to a primary region and asynchronously to a secondary region.
3
Define the authentication and access method for Azure Blob Storage.
Generate short-lived SAS tokens dynamically using a user delegation key.
Using a user delegation key secured by Microsoft Entra ID credentials provides a secure, short-lived SAS token that avoids hardcoding storage account master keys and simplifies access revocation.

Key Concept

Selecting high-cardinality partition keys in Azure Cosmos DB to prevent hot partitions, combined with appropriate storage redundancy and secure, delegatable access policies.
Question 918Question

NexaHealth is designing an identity and security strategy using Microsoft Entra ID. You need to match each technical requirement to the most appropriate Microsoft Entra ID or Conditional Access feature. Drag the appropriate feature from the column on the right to the matching requirement on the left.

Click a left item, then click its matching right item

Items

Enforce multi-factor authentication (MFA) for administrative roles only when their sign-in attempt is classified as a medium or high risk level.
Enforce a maximum inactive session lifetime of one hour for web-based access to sensitive clinical portals.
Block the use of organization-specific and healthcare-specific terms within user passwords during password creation or reset.
Enable external guest users to authenticate using their existing Google or Facebook accounts without provisioning new credentials.

Matches

Show answer & explanation

Answer

The correct pairings are: Requirement 1 matches 'Conditional Access sign-in risk condition', Requirement 2 matches 'Conditional Access session controls', Requirement 3 matches 'Microsoft Entra Password Protection custom list', and Requirement 4 matches 'Microsoft Entra External ID identity providers'.
Each security and authentication requirement maps to a dedicated feature in Microsoft Entra: sign-in risk policies evaluate session context, session controls manage idle session lifetimes, custom password protection lists prevent insecure industry terms, and external identity provider configuration allows direct federation with third-party accounts.

Step-by-Step Solution

1
Analyze the requirement to enforce MFA dynamically based on anomalous access patterns.
Identify that the sign-in risk condition assesses the probability of a compromised request in real-time.
This allows targeting MFA prompts specifically to risky authentication attempts rather than every administrative login.
2
Analyze the requirement to limit the duration of inactive web portal sessions.
Determine that session controls within Conditional Access policies manage browser session persistence and sign-in frequency.
These controls enforce a re-authentication prompt once the specified threshold is crossed.
3
Analyze the requirement to restrict the use of industry-specific terms in user passwords.
Determine that Microsoft Entra Password Protection allows uploading a custom list of banned terms.
This list is evaluated alongside the global banned password list to secure password validation.
4
Analyze the requirement to authenticate guest users via existing consumer identity accounts.
Identify that Microsoft Entra External ID identity providers support external federation with identity providers like Google and Facebook.
This avoids provisioning internal credentials for external partners, simplifying governance.

Key Concept

Selecting the correct Microsoft Entra identity, authentication, and Conditional Access features to satisfy specific security and business compliance requirements.
Estimated Time:2m 0s
Question 919Question

You are designing the compute infrastructure for a mission-critical web application on Azure.

The application consists of two tiers:
- A web frontend tier that must host stateless virtual machines, support automatic horizontal scaling, and guarantee a virtual machine uptime SLA of 99.99%99.99\%.
- A backend transaction processing tier that consists of stateful virtual machines, requires a virtual machine uptime SLA of 99.95%99.95\%, and requires sub-millisecond network latency between the virtual machine instances.

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

Select all that apply

Show answer & explanation

Answer: Deploy the web frontend tier using a Virtual Machine Scale Set in Flexible orchestration mode distributed across three Availability Zones.; Deploy the backend transaction processing tier in an Availability Set within a single Availability Zone, and associate the virtual machines with a Proximity Placement Group.

Answer

Deploy the web frontend tier using a Virtual Machine Scale Set in Flexible orchestration mode distributed across three Availability Zones, and deploy the backend transaction processing tier in an Availability Set within a single Availability Zone associated with a Proximity Placement Group.
To satisfy the frontend tier's requirements of a 99.99%99.99\% SLA and auto-scaling, you must deploy a Virtual Machine Scale Set in Flexible orchestration mode across multiple Availability Zones. To satisfy the backend tier's requirements of a 99.95%99.95\% SLA and sub-millisecond network latency, you must place the virtual machines in an Availability Set within a single Availability Zone and associate them with a Proximity Placement Group. This guarantees the 99.95%99.95\% SLA while keeping the instances physically close enough to minimize network latency.

Step-by-Step Solution

1
Analyze the high availability requirements for the web frontend tier.
The frontend requires a 99.99%99.99\% uptime SLA and auto-scaling. In Azure, a 99.99%99.99\% SLA for virtual machines requires distributing them across multiple Availability Zones. Virtual Machine Scale Sets in Flexible orchestration mode support zonal distribution and scale-out capabilities.
Choosing a configuration that spans zones is necessary to meet the 99.99%99.99\% SLA, and scale sets are needed to handle automatic horizontal scaling.
2
Analyze the high availability and latency requirements for the backend tier.
The backend requires a 99.95%99.95\% SLA and sub-millisecond latency. An Availability Set provides a 99.95%99.95\% SLA. To guarantee sub-millisecond latency, the instances must be placed in a single Availability Zone and associated with a Proximity Placement Group to ensure they are physically colocated in the same data center.
Spreading backend virtual machines across different Availability Zones would increase latency beyond the sub-millisecond requirement, so keeping them in a single zone with a Proximity Placement Group is necessary.
3
Verify load balancing and SKU compatibility rules.
Standard Load Balancers are required for zonal deployments but they only support Standard SKU resources. Assigning Basic SKU public IPs to virtual machines behind a Standard Load Balancer is invalid.
This confirms that options attempting to mix Standard and Basic SKUs are invalid.

Key Concept

Designing compute high availability in Azure by balancing Availability Zones (for 99.99%99.99\% SLA), Availability Sets (for 99.95%99.95\% SLA), and Proximity Placement Groups (for low latency), while respecting resource SKU compatibility rules.
Question 920Question

Veloce Logistics is designing a hybrid identity and security strategy to integrate its on-premises Active Directory Domain Services (AD DS) environment with Microsoft Entra ID. The IT security team has the following requirements:

- Users must be able to sign in to cloud resources using their on-premises credentials.
- If a security incident occurs in the on-premises environment or network connectivity to on-premises is lost, users must still be able to sign in to cloud services without relying on on-premises infrastructure.
- To prevent tenant lockout during a cloud-based multi-factor authentication (MFA) service outage, the security administrator must ensure at least one highly privileged emergency access account can bypass MFA.
- Administrative roles must be managed using Privileged Identity Management (PIM) to prevent persistent administrative privileges.

Which of the following represents the most appropriate combination of hybrid authentication and policy design for Veloce Logistics?

Show answer & explanation

Answer: Configure Microsoft Entra Connect with Password Hash Synchronization (PHS). Create a Conditional Access policy requiring MFA for all users, but exclude a dedicated emergency access account from this policy. Configure Privileged Identity Management (PIM) role assignments as eligible rather than active.

Answer

Configure Microsoft Entra Connect with Password Hash Synchronization (PHS), exclude a dedicated emergency access account from the MFA Conditional Access policy, and assign Privileged Identity Management (PIM) roles as eligible.
The correct option correctly identifies Password Hash Synchronization (PHS) as the hybrid identity solution that satisfies the dependency requirement, since authentication occurs directly in Microsoft Entra ID without calling back to on-premises. It also ensures that the emergency access account is excluded from the MFA requirement to prevent tenant lockout during a service outage, and specifies that PIM roles must be eligible rather than active to prevent persistent administrative privileges.

Step-by-Step Solution

1
Evaluate the hybrid authentication options against the resiliency requirement.
Password Hash Synchronization (PHS) is selected because it replicates credential hashes to Microsoft Entra ID. This allows users to authenticate in the cloud even if on-premises domain controllers or connection links are offline. Active Directory Federation Services (AD FS) and Pass-through Authentication (PTA) require active on-premises communication.
To ensure authentication capability is not dependent on on-premises infrastructure or connectivity.
2
Address the risk of lockout during a cloud MFA service outage.
Exclude a dedicated emergency access (break-glass) account from the Conditional Access policy requiring MFA.
This guarantees that administrators can still access the tenant if the cloud MFA service is experiencing an outage.
3
Configure the administrative access governance model.
Configure Privileged Identity Management (PIM) role assignments as 'Eligible' rather than 'Active'.
This ensures administrators must explicitly activate their roles on-demand (just-in-time) rather than maintaining permanent, persistent privileges.

Key Concept

Designing a resilient hybrid identity, authentication, and access control strategy using Microsoft Entra ID, including Password Hash Synchronization, Conditional Access policy exclusions, and Privileged Identity Management (PIM) eligibility.
Estimated Time:1m 30s
PreviousPage 46 / 60Next