All practice questions

1198 questions

Question 361Question

A scientific research institute is designing the storage infrastructure for a high-performance computing (HPC) application. The application requires Azure Blob Storage with sub-millisecond latency and high throughput for write operations, which necessitates the Premium block blobs performance tier.

The architecture must satisfy the following resilience and accessibility requirements:
1. Protect against the outage of a single datacenter in the primary region by replicating data synchronously.
2. Protect against a regional disaster by maintaining an asynchronous copy of the data in a secondary paired region.
3. Allow a reporting tool located in the secondary region to read the data at any time without initiating a storage account failover.

Which storage solution should you recommend to meet these requirements?

Show answer & explanation

Answer: Deploy a Premium Block Blob storage account configured with Zone-Redundant Storage (ZRS) in the primary region, and implement a custom replication workflow using Azure Data Factory to copy blobs to a Premium Block Blob storage account configured with Zone-Redundant Storage (ZRS) in the secondary region.

Answer

Deploy a Premium Block Blob storage account configured with Zone-Redundant Storage (ZRS) in the primary region, and implement a custom replication workflow using Azure Data Factory to copy blobs to a Premium Block Blob storage account configured with Zone-Redundant Storage (ZRS) in the secondary region.
The correct solution uses a Premium Block Blob storage account with Zone-Redundant Storage (ZRS) in the primary region, which meets the low-latency requirement and protects against a single datacenter outage. Because Premium Block Blob storage accounts do not natively support geo-redundancy (GRS, GZRS, RA-GRS, or RA-GZRS), a secondary storage account must be deployed in the secondary region. Azure Data Factory can then be used to asynchronously replicate the blobs, providing read access to the secondary region without initiating a failover.

Step-by-Step Solution

1
Evaluate the workload performance requirements.
Determine that the sub-millisecond latency and high throughput requirements necessitate the Premium block blobs performance tier, which rules out Standard GPv2 storage accounts.
Standard storage accounts do not provide the performance characteristics needed for low-latency HPC write workloads.
2
Evaluate local high availability requirements.
Identify that to protect against a single datacenter outage in the primary region, Zone-Redundant Storage (ZRS) is required, eliminating Locally Redundant Storage (LRS) configurations.
ZRS replicates data synchronously across three availability zones, whereas LRS replicates data only within a single datacenter.
3
Assess geo-redundancy options for Premium Block Blobs.
Recognize that Premium Block Blob storage accounts only support LRS and ZRS. Native geo-redundancy (GRS, GZRS, RA-GZRS) is unavailable.
Azure architectural constraints limit native geo-redundancy options to Standard storage accounts.
4
Design the secondary region disaster recovery and read access mechanism.
Deploy a separate Premium Block Blob storage account in the secondary region and implement an asynchronous copy mechanism (such as Azure Data Factory) to replicate data.
This allows the reporting tool in the secondary region to read the data from the secondary storage account without initiating a failover, while maintaining the performance and primary availability requirements.

Key Concept

Premium Block Blob storage accounts only support Locally Redundant Storage (LRS) and Zone-Redundant Storage (ZRS). To achieve geo-redundancy and read access in a secondary region for Premium Block Blobs, you must deploy a separate storage account in the secondary region and implement a custom replication workflow.
Question 362Question

A financial services company is designing a disaster recovery solution for its transaction logs stored in Azure Blob Storage. The architect recommends configuring the storage account with Read-Access Geo-Redundant Storage (RA-GRS). The development team is updating the client application to handle failover scenarios and needs to understand the write capabilities of this storage design. Which two statements correctly describe the write operations behavior for this configuration? (Select two.)

Select all that apply

Show answer & explanation

Answer: Write operations can only be performed on the primary endpoint during normal operations.; Write operations can be performed on the secondary endpoint only after a failover has been initiated and completed.

Answer

Write operations are restricted to the primary endpoint during normal operations, and they can only be performed on the secondary endpoint after a failover has been initiated and completed.
The correct options are those stating that write operations are confined to the primary endpoint during normal operations and can only be performed on the secondary endpoint after a failover is initiated and completed. Under RA-GRS, the secondary endpoint provides read-only access prior to failover. Performing a failover promotes the secondary endpoint to the primary read-write role, enabling write capabilities.

Step-by-Step Solution

1
Analyze the configuration of Read-Access Geo-Redundant Storage (RA-GRS).
Identify that RA-GRS provides read-write access to the primary endpoint and read-only access to the secondary endpoint under normal operating conditions.
This establishes the baseline capability of the secondary endpoint before any disruption occurs.
2
Determine the state of write operations during normal operations and outages.
Confirm that write operations cannot be sent directly to the secondary endpoint, nor are they automatically redirected to the secondary endpoint for writing during an outage.
This rules out active-active write scenarios and automatic write failover.
3
Identify the mechanism required to enable write access in the secondary region.
Establish that a failover must be initiated to promote the secondary endpoint to a read-write role.
This determines how write capabilities are restored in a disaster recovery scenario.

Key Concept

Write capabilities of RA-GRS during normal operations and secondary failovers
Question 363Question

You are designing the storage architecture for a global pharmaceutical cold-chain monitoring system. Sensor devices on transport containers in North America, Europe, and Asia write telemetry data (temperature, humidity, and location) every 1010 seconds. The read/write ratio is 95%95\% writes and 5%5\% reads. The application requires a 99.999%99.999\% write availability SLA, sub-10 ms10\text{ ms} write latency, and must survive regional outages. You decide to use Azure Cosmos DB for NoSQL. Which of the following configurations should you recommend?

Show answer & explanation

Answer: Configure the Azure Cosmos DB account with multi-region writes across the target regions, use a synthetic partition key combining DeviceId and the date-hour (DeviceId_YYYYMMDDHH) for the container, and use Microsoft Entra ID role-based access control (RBAC) to secure database access.

Answer

Configure the Azure Cosmos DB account with multi-region writes across the target regions, use a synthetic partition key combining DeviceId and the date-hour (DeviceId_YYYYMMDDHH) for the container, and use Microsoft Entra ID role-based access control (RBAC) to secure database access.
The configuration utilizing multi-region writes, a high-cardinality synthetic partition key (DeviceId_YYYYMMDDHH), and Microsoft Entra ID RBAC satisfies the 99.999%99.999\% write availability SLA, delivers low-latency writes globally, distributes ingestion traffic evenly across physical partitions, and employs secure modern identity authentication.

Step-by-Step Solution

1
Analyze write availability and resiliency requirements.
To achieve a 99.999%99.999\% write availability SLA and survive regional outages, multi-region writes must be enabled across the active regions.
Single-region write configurations only offer a 99.99%99.99\% SLA, whereas multi-region writes provide the highest level of availability and local write latency.
2
Determine the optimal partition key strategy.
Select a high-cardinality synthetic partition key combining DeviceId and date-hour (DeviceId_YYYYMMDDHH).
Since the workload is 95%95\% writes, a low-cardinality partition key would create hot partitions, exceeding storage and throughput limits on physical partitions.
3
Evaluate authentication and security best practices.
Use Microsoft Entra ID RBAC for database access and avoid using long-lived SAS tokens without stored access policies for associated storage accounts.
Identity-based authentication eliminates credential management overhead, and stored access policies are required to enable revocation of SAS tokens.

Key Concept

Designing globally distributed, high-performance, and resilient Azure Cosmos DB architectures using synthetic partition keys and multi-region writes.
Question 364Question

An enterprise uses Azure Files shares to store business-critical documents. You are designing a backup solution using Azure Backup that satisfies the following requirements:
- Shared file data must be backed up three times per day to achieve an 88-hour Recovery Point Objective (RPO).
- Backup data must be retained for 1010 years to comply with regulatory requirements.
- The vault storage must remain resilient to zone outages within the primary region while minimizing storage costs.

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

Select all that apply

Show answer & explanation

Answer: An Enhanced backup policy; A Recovery Services vault configured with Zone-Redundant Storage (ZRS)

Answer

The correct configuration requires choosing an Enhanced backup policy and a Recovery Services vault configured with Zone-Redundant Storage (ZRS).
The combination of an Enhanced backup policy and a Recovery Services vault configured with Zone-Redundant Storage (ZRS) meets all the requirements. The Enhanced policy is required for Azure Files to support sub-daily backups (meeting the 8-hour RPO) and long-term storage in the vault tier (meeting the 10-year retention rule). The ZRS configuration ensures the backup data is resilient to zone outages while being more cost-effective than geo-redundant storage.

Step-by-Step Solution

1
Analyze the RPO and retention requirements to determine the required backup policy tier.
An 8-hour RPO requires multiple backups per day, and a 10-year retention rule requires vault-level storage rather than just share snapshots. This necessitates an Enhanced backup policy, as Standard policies only support daily backups and a maximum of 200 days of snapshot retention.
Determines the backup policy tier required to meet the operational and compliance SLA.
2
Evaluate the resiliency and cost-minimization requirements for backup storage redundancy.
To survive a zone outage within the primary region, Zone-Redundant Storage (ZRS) must be used. Locally Redundant Storage (LRS) is not zone-resilient, and Geo-Redundant Storage (GRS) violates the cost-minimization requirement by replicating data across regions.
Identifies the correct storage replication tier for the Recovery Services vault.
3
Select the two correct configuration options based on the policy and vault redundancy requirements.
Select the Enhanced backup policy and the ZRS-configured Recovery Services vault.
Combines the policy and storage tier findings into the final configuration.

Key Concept

Azure Backup supports Standard and Enhanced backup policies, with the Enhanced policy enabling sub-daily backups and vault-tier storage for long-term retention. Storage redundancy options like ZRS protect vault data from zone failures cost-effectively.
Question 365Question

A financial services provider stores daily transaction receipts in an Azure Blob Storage container. The receipts are frequently accessed for auditing within the first 7 days and must support immediate, sub-second retrieval at any time. After 7 days, the receipts are rarely accessed but must be retained for 365 days to meet regulatory compliance requirements. The provider wants to configure an Azure Blob Storage lifecycle management policy to minimize storage costs.

Which lifecycle management policy rule should you recommend?

Show answer & explanation

Answer: Transition the blobs to the Cool tier 7 days after creation, and delete the blobs 365 days after creation.

Answer

Transition the blobs to the Cool tier 7 days after creation, and delete the blobs 365 days after creation.
The correct option transitions the blobs to the Cool tier 7 days after creation and deletes them after 365 days. The Cool tier is the most cost-effective tier that still provides immediate, sub-second retrieval, which satisfies the requirement that transaction receipts must be accessible immediately. Deleting the blobs after 365 days aligns with the compliance requirement to retain data for that period.

Step-by-Step Solution

1
Analyze retrieval latency requirements.
Since sub-second retrieval is required at any time, the Archive tier cannot be used because it has a rehydration latency of several hours.
Ensures that the selected storage tier meets the performance constraints specified in the scenario.
2
Identify the optimal cost-effective tier for infrequently accessed data.
The Cool tier is selected for receipts older than 7 days, as they are rarely accessed but still require immediate retrieval.
Minimizes storage costs while adhering to the latency requirement.
3
Apply the retention period rule.
Configure the lifecycle policy to delete blobs 365 days after creation.
Fulfills the compliance mandate to keep the records for exactly 365 days.

Key Concept

Azure Blob Storage lifecycle management tiering and latency requirements
Estimated Time:45s
Question 366Question

An enterprise is migrating a high-throughput transactional database workload to Azure Virtual Machines. The database storage architecture must satisfy the following requirements:
- The database transaction logs require consistent sub-millisecond write response times and high IOPS.
- The storage infrastructure must survive a localized datacenter (zone) failure within the primary region without data loss.
- Backup files containing database exports must be stored securely and made accessible to external auditors via a HTTPS URL for exactly seven days, with the capability to immediately revoke access if a security anomaly is detected.

Which storage and access configuration should you recommend to meet these requirements?

Show answer & explanation

Answer: Configure the transaction logs on Ultra Disk or Premium SSD v2 managed disks using Zone-Redundant Storage (ZRS). Store the backup files in an Azure Blob storage container with Zone-Redundant Storage (ZRS), and grant the auditors access using a Shared Access Signature (SAS) associated with a stored access policy.

Answer

Configure the transaction logs on Ultra Disk or Premium SSD v2 managed disks using Zone-Redundant Storage (ZRS). Store the backup files in an Azure Blob storage container with Zone-Redundant Storage (ZRS), and grant the auditors access using a Shared Access Signature (SAS) associated with a stored access policy.
The correct configuration uses Ultra Disk or Premium SSD v2 managed disks with Zone-Redundant Storage (ZRS) for the transaction logs, meeting the sub-millisecond latency and zone-redundancy requirements. For the backup files, Azure Blob storage with Zone-Redundant Storage (ZRS) provides the necessary resilience, and utilizing a Shared Access Signature (SAS) linked to a stored access policy allows the access to be immediately revoked by modifying or deleting the policy.

Step-by-Step Solution

1
Analyze the performance requirements for the database transaction logs.
Identify that consistent sub-millisecond write response times and high IOPS require high-performance disk types such as Premium SSD v2 or Ultra Disk.
Standard SSD and Standard HDD tiers do not guarantee the low latency and high IOPS necessary for database logs.
2
Determine the redundancy requirements for both transaction logs and backup files.
Determine that Zone-Redundant Storage (ZRS) is required for both systems to survive a localized datacenter (zone) failure.
Locally Redundant Storage (LRS) replicates data only within a single datacenter, making it vulnerable to zone outages.
3
Evaluate the security and revocation requirements for the temporary backup access.
Select a Shared Access Signature (SAS) associated with a stored access policy.
An ad-hoc SAS cannot be revoked without rotating the storage account keys. Associating the SAS with a stored access policy allows immediate revocation by deleting or updating the policy.

Key Concept

Designing high-performance, zone-resilient disk storage and securing Azure Blob storage using revocable access methods (Stored Access Policies).
Question 367Question

An e-sports tournament platform is designing a disaster recovery and high availability strategy for its matchmaking and player state tracking database layer. The platform has the following requirements:
- The database must support SQL Server Agent jobs and native cross-database queries.
- The primary database must be deployed in the Business Critical tier in East US.
- A secondary replica must be configured in West US to meet a Recovery Time Objective (RTO) of less than 1515 seconds and a Recovery Point Objective (RPO) of less than 55 seconds.
- Client applications must automatically reconnect to the active primary replica without manual connection string modifications during a failover.
- Read-only analytics queries must be offloaded to the secondary replica.
- All database replication traffic must travel privately over Microsoft's backbone network without traversing the public internet.

To implement this, the database administration team peers the virtual networks (VNets) in East US and West US, opens ports 50225022 and 110001199911000-11999 in the Network Security Groups (NSGs), deploys the primary Azure SQL Managed Instance, and deploys the secondary Azure SQL Managed Instance. However, when they attempt to establish an auto-failover group, the configuration fails.

Which of the following options identifies the cause of this failure and the correct configuration step to resolve it?

Show answer & explanation

Answer: The secondary managed instance was deployed with a default, distinct DNS zone prefix. You must delete the secondary instance and recreate it while specifying the primary instance as the DNS zone partner to ensure they share the same DNS zone.

Answer

The secondary managed instance must be recreated while specifying the primary instance as the DNS zone partner to ensure they share the same DNS zone prefix.
The correct option is correct because Azure SQL Managed Instance failover groups require that both the primary and secondary instances belong to the same DNS zone. When an instance is created, it is assigned a random DNS zone prefix. To establish a failover group, the secondary instance must be created with the primary instance configured as its DNS zone partner. If the secondary instance is created without this relationship, it cannot be added to the failover group, and it must be recreated with the partner parameter specified.

Step-by-Step Solution

1
Analyze the database requirements and features needed.
Identify that Azure SQL Managed Instance is required due to SQL Server Agent and cross-database query needs, and that an Auto-Failover Group is required to support the automatic failover listener and the RTO/RPO requirements.
Determining the correct Azure SQL service offering and DR mechanism is the foundation of the architecture design.
2
Evaluate the networking and DNS constraints for SQL Managed Instance failover groups.
Recognize that the primary and secondary instances must have non-overlapping IP spaces, secure network connectivity (e.g., peered VNets), and must share the same DNS zone.
Failover groups for Managed Instances cannot be established if the instances do not reside in the same DNS zone, which must be configured during the creation of the secondary instance.
3
Determine the resolution for the failover group configuration failure.
Identify that the secondary instance must be recreated with the primary instance specified as the DNS zone partner to ensure DNS zone matching.
DNS zone partnership cannot be modified after the SQL Managed Instance is deployed.

Key Concept

Designing High Availability and Disaster Recovery using Auto-Failover Groups in Azure SQL Managed Instance, including networking and DNS zone partner prerequisites.
Question 368Question

You are designing a disaster recovery solution to Azure for an on-premises VMware virtual machine named VM1. The virtual machine hosts a web application and has the following disk configuration and write churn metrics:

- Disk 1 (OS): Standard SSD, 4 MB/s4\text{ MB/s} write churn
- Disk 2 (Temp Data): Premium SSD, 85 MB/s85\text{ MB/s} write churn (contains temporary cache files that do not need to be preserved)
- Disk 3 (App Logs): Premium SSD, 12 MB/s12\text{ MB/s} write churn

The solution must meet a Recovery Point Objective (RPO) of 2 hours2\text{ hours} and a Recovery Time Objective (RTO) of 4 hours4\text{ hours}.

Which of the following actions should you recommend? (Select TWO).

Select all that apply

Show answer & explanation

Answer: Replicate Disk 1 and Disk 3, and exclude Disk 2 from the replication configuration.; Configure Azure Site Recovery to replicate the supported disks of the virtual machine to Azure.

Answer

Recommending the replication of Disk 1 and Disk 3 while excluding Disk 2, and configuring Azure Site Recovery for the virtual machine.
Azure Site Recovery supports a maximum write churn of 25 MB/s25\text{ MB/s} per Premium SSD and 10 MB/s10\text{ MB/s} per Standard SSD/HDD for VMware virtual machines. Disk 2's churn of 85 MB/s85\text{ MB/s} is well above this threshold. Because Disk 2 contains temporary cache data that does not need to be restored during a failover, it can be excluded from replication. This keeps the active replication churn within supported limits. Azure Site Recovery is the designated service to orchestrate the replication and failover of virtual machines to meet low RPO/RTO parameters.

Step-by-Step Solution

1
Analyze the write churn of each virtual machine disk against the supported limits of Azure Site Recovery.
Disk 1 (4 MB/s4\text{ MB/s}) and Disk 3 (12 MB/s12\text{ MB/s}) are within standard limits, but Disk 2 (85 MB/s85\text{ MB/s}) exceeds the 25 MB/s25\text{ MB/s} limit for Premium SSDs.
Ensuring the workloads are within replication boundaries prevents deployment and operational failures.
2
Identify if any high-churn disks can be excluded based on their data type.
Disk 2 contains only temporary cache files and can be safely excluded from the replication setup.
Excluding temporary or scratch disks is a supported method to bypass churn limits and reduce replication overhead.
3
Recommend Azure Site Recovery to coordinate the replication of the remaining compatible disks to meet the disaster recovery goals.
The final design uses Azure Site Recovery with Disk 1 and Disk 3 replicated, and Disk 2 excluded.
This configuration successfully meets the RPO and RTO targets while remaining fully within Azure Site Recovery's support limitations.

Key Concept

Excluding high-churn temporary disks from Azure Site Recovery replication to stay within supported boundaries.
Question 369Question

A software-as-a-service (SaaS) provider has a customer billing application that runs on a single database in Azure SQL Database. The database is deployed in the East US region. You need to design a disaster recovery solution that meets the following requirements:
- In the event of a regional outage, the database must support automatic failover to the West US region with a recovery time objective (RTO) of less than 1 hour.
- The application must use a constant read-write endpoint that does not require updating connection strings when a failover occurs.
- Read-only billing reports must be offloaded to the secondary region database replica.
- Administrative intervention during failover must be minimized.

Which database configuration should you select?

Show answer & explanation

Answer: Create an auto-failover group that includes the database, and configure the application to connect to the read-write and read-only listener endpoints.

Answer

Create an auto-failover group that includes the database, and configure the application to connect to the read-write and read-only listener endpoints.
Creating an auto-failover group is correct because it manages replication and failover of Azure SQL databases to a secondary region automatically. It provides read-write and read-only DNS listener endpoints that remain constant, allowing the application to use a single connection string without modification during a failover event, while offloading reporting workloads to the secondary replica.

Step-by-Step Solution

1
Analyze the business requirements for database recovery, noting the need for automatic failover to a secondary region, a constant connection string, read-scale routing, and minimal administrative effort.
The requirements point to a managed Azure SQL Database disaster recovery solution rather than an IaaS migration, which would increase management overhead.
This rules out IaaS configurations (SQL Server on Azure VMs) as they do not align with the minimal administrative intervention goal.
2
Evaluate Azure SQL Database high availability and disaster recovery options, comparing active geo-replication and auto-failover groups.
Active geo-replication requires manual intervention to fail over and does not provide unified connection string listeners, whereas auto-failover groups automate failover and expose read-write and read-only listener endpoints.
This satisfies the automatic failover, unchanging connection string, and read-scale requirements.
3
Identify the correct configuration that combines auto-failover groups with the single database setup.
An auto-failover group is configured with the primary database server and a secondary server in the target region, containing the customer billing database.
This achieves the desired HA/DR architecture with zero application-side connection string changes during a failover.

Key Concept

Azure SQL Database Auto-Failover Groups provide automatic regional failover and listener endpoints for transparent connection redirection and read-scale routing.
Question 370Question

Solarize Logistics is designing an identity and access management solution for its Microsoft Entra ID tenant. The security and infrastructure teams specify the following requirements:
- Require multi-factor authentication (MFA) for all administrative access.
- Prevent administrative tenant lockout in the event of an Azure MFA service outage.
- Provide just-in-time (JIT) access for administrative roles.
- Minimize on-premises infrastructure overhead for hybrid identity synchronization.

Which set of design decisions should you recommend?

Show answer & explanation

Answer: Implement Password Hash Synchronization (PHS) for hybrid identity, configure administrative roles in Privileged Identity Management (PIM) as eligible, and exclude a dedicated cloud-only emergency access account from the Conditional Access policy requiring MFA.

Answer

Implement Password Hash Synchronization (PHS) for hybrid identity, configure administrative roles in Privileged Identity Management (PIM) as eligible, and exclude a dedicated cloud-only emergency access account from the Conditional Access policy requiring MFA.
The correct design decision combines Password Hash Synchronization (PHS) to minimize on-premises infrastructure, Privileged Identity Management (PIM) with eligible assignments for just-in-time access, and the exclusion of an emergency access account from Conditional Access policies to prevent lockout.

Step-by-Step Solution

1
Select the hybrid identity synchronization method with the lowest on-premises complexity.
Password Hash Synchronization (PHS) is selected.
PHS requires only the Azure AD Connect agent and has no additional server dependencies, unlike Active Directory Federation Services (AD FS) which requires federation servers, web application proxies, and certificate management.
2
Configure the administrative roles to support just-in-time (JIT) access governance.
Configure role assignments in Privileged Identity Management (PIM) as eligible.
Eligible assignments require administrators to explicitly activate their roles when executing tasks, ensuring they only hold privileges when necessary rather than permanently.
3
Design the Conditional Access policy to enforce MFA while safeguarding administrative access.
Exclude a cloud-only emergency access (glass-breaker) account from the MFA policy.
Excluding a dedicated emergency access account prevents administrators from being locked out of the tenant if the Azure MFA service is down or misconfigured.

Key Concept

Designing secure identity, authentication, and access policies in Microsoft Entra ID by combining PHS, PIM, and Conditional Access exclusions.
Estimated Time:1m 30s
Question 371Question

A software company is designing a relational database solution in Azure for a critical multi-tenant inventory application. The database architecture must meet the following requirements:
- Provide high availability within the primary region that can survive a datacenter zone outage.
- Replicate database data to a secondary Azure region to support disaster recovery with an RTO of less than 11 hour and an RPO of less than 55 minutes.
- Ensure that client applications can automatically reconnect to the secondary region database during a failover without requiring configuration updates or DNS changes.
- Support routing read-only inventory reports to the secondary region to reduce the load on the primary database.

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

Select all that apply

Show answer & explanation

Answer: Configure an Auto-Failover Group containing the primary database in the primary region and a secondary replica in the paired region.; Deploy the database using the Azure SQL Database Business Critical service tier with zone redundancy enabled.

Answer

Deploy the database on the Azure SQL Database Business Critical tier with zone redundancy enabled, and configure an Auto-Failover Group with read-write and read-only listeners.
To support regional disaster recovery with automatic failover and read-scale routing under a single endpoint, you should configure an Auto-Failover Group. This exposes read-write and read-only listener endpoints that persist through failovers, preventing the need to update client connection strings. Deploying the database on the Business Critical service tier of Azure SQL Database with zone redundancy enabled guarantees high availability that is resilient to availability zone failures within the primary region.

Step-by-Step Solution

1
Evaluate the requirement for local high availability resilient to datacenter zone outages.
By selecting Azure SQL Database on the Business Critical tier and enabling zone redundancy, the primary database replica is spread across different physical zones in the primary region.
This guarantees that the database will remain online even if one of the physical datacenters in the primary region undergoes an outage.
2
Address the disaster recovery, automatic failover, and client reconnection criteria.
Implement an Auto-Failover Group between the primary and secondary regions, which exposes unified read-write and read-only listener endpoints.
Auto-Failover Groups satisfy the RTO and RPO limits through asynchronous replication and handle client redirection automatically, ensuring that client applications do not require connection string updates during a failover.
3
Satisfy the requirement to offload read-only inventory reports to the secondary region.
Utilize the read-only listener of the Auto-Failover Group to route analytical and reporting queries directly to the secondary replica database.
This offloads read operations from the primary transactional database, maximizing performance and efficiency.

Key Concept

Designing relational database high availability and disaster recovery using Azure SQL Database features like zone redundancy and Auto-Failover Groups.
Estimated Time:2m 0s
Question 372Question

A smart-home IoT company is designing a data storage architecture for device telemetry logs stored in Azure Blob Storage. The system must meet the following requirements:
- Survive a complete regional outage of the primary Azure region.
- Support active-active write operations in both the primary and secondary regions simultaneously.
- Minimize storage costs.
An architect recommends using Read-Access Geo-Redundant Storage (RA-GRS) to allow telemetry ingestion services in both regions to write directly to the storage account.
Why does the recommended solution fail to meet the requirements?

Show answer & explanation

Answer: Read-Access Geo-Redundant Storage (RA-GRS) does not support write operations to the secondary region; the secondary endpoint is read-only unless a failover is initiated.

Answer

Read-Access Geo-Redundant Storage (RA-GRS) does not support write operations to the secondary region; the secondary endpoint is read-only unless a failover is initiated.
The correct option is correct because Read-Access Geo-Redundant Storage (RA-GRS) replicates data to a secondary region but only allows read access to the secondary endpoint. It does not support write operations in the secondary region, failing the active-active write requirement.

Step-by-Step Solution

1
Identify the replication and access characteristics of Read-Access Geo-Redundant Storage (RA-GRS).
RA-GRS replicates data to a secondary region asynchronously and provides read-only access to the secondary endpoint.
To determine whether the secondary endpoint can accept write operations.
2
Compare the capabilities of RA-GRS against the business requirement for active-active write operations in both regions.
Since RA-GRS does not support writes to the secondary region, it cannot be used for an active-active write configuration.
To identify why the architect's recommendation fails the requirement.

Key Concept

Azure Storage replication redundancy options and write limitations of read-access secondary endpoints.
Estimated Time:45s
Question 373Question

A manufacturing company is designing a storage solution for archiving smart factory telemetry files in an Azure Blob Storage container. The solution must meet the following security and administrative requirements:

- Internal data analysts must have read access to the container. Access permissions must scale automatically when analysts join or leave the organization without modifying individual resource permissions.
- External manufacturing partners require read access to specific telemetry files for a maximum duration of 8 hours. The company must be able to immediately revoke this access at any time without rotating the primary or secondary storage account keys.
- Storage administrators must only obtain permission to manage the storage account settings on-demand after an approval process, and the permission must automatically expire after 2 hours.

Which combination of security controls should you recommend to meet these requirements?

Show answer & explanation

Answer: Assign the Storage Blob Data Reader role to a Microsoft Entra ID security group containing the data analysts. Use a Stored Access Policy on the container to generate Shared Access Signatures (SAS) for the external partners. Configure eligible role assignments in Microsoft Entra Privileged Identity Management (PIM) for the administrators.

Answer

Assign the Storage Blob Data Reader role to a Microsoft Entra ID security group containing the data analysts, use a Stored Access Policy on the container to generate Shared Access Signatures (SAS) for the external partners, and configure eligible role assignments in Microsoft Entra Privileged Identity Management (PIM) for the administrators.
The correct recommendation incorporates three primary security principles: administrative scalability via Entra ID group assignments, granular time-bound external delegation via Stored Access Policies, and just-in-time access via PIM eligible assignments. Group-based RBAC ensures that permissions update dynamically without manual database or resource-level configuration changes. A Stored Access Policy binds the SAS token's lifecycle, enabling instant revocation. Eligible roles in PIM require administrators to request activation and justify access when performing tasks, fulfilling the 2-hour window requirement with approval.

Step-by-Step Solution

1
Select the appropriate access control method for data analysts.
Use a Microsoft Entra ID security group and assign the Storage Blob Data Reader role to the group rather than individual users.
This allows user permissions to scale automatically as analysts join or leave the group, reducing administrative overhead.
2
Select the appropriate mechanism for external partner access.
Create a Stored Access Policy on the Blob container and generate the Shared Access Signature (SAS) token from this policy.
A Stored Access Policy provides a way to immediately revoke the generated SAS tokens by deleting or modifying the policy, avoiding the need to rotate storage account keys.
3
Select the administrative access governance control.
Configure Microsoft Entra Privileged Identity Management (PIM) with eligible role assignments.
This enforces the principle of least privilege, requiring administrators to request activation (just-in-time) rather than having standing active access.

Key Concept

Data Storage Security and Access Control
Question 374Question

An enterprise is designing an identity governance and privileged access strategy for its Azure subscription. The subscription contains critical production workloads. The solution must meet the following requirements:
- A group of external compliance auditors needs read-only access to all subscription resources for a temporary period of three weeks.
- A group of internal security administrators needs to manage Azure role assignments, but only when actively conducting access reviews.
- Administrative overhead must be minimized, and the principle of least privilege must be strictly followed.

Which of the following actions should you include in the design? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Create a Microsoft Entra security group for the external auditors, and configure an eligible Reader role assignment for the group using Privileged Identity Management (PIM).; Create a Microsoft Entra security group for the internal security administrators, and configure an eligible User Access Administrator role assignment for the group using Privileged Identity Management (PIM).

Answer

To meet the requirements, you should create Microsoft Entra security groups for both the auditors and administrators, and configure eligible role assignments (Reader and User Access Administrator respectively) in Privileged Identity Management (PIM) for those groups.
The design must leverage Microsoft Entra Privileged Identity Management (PIM) to enforce just-in-time (JIT) access. Creating security groups and configuring them with eligible role assignments (Reader for auditors and User Access Administrator for internal admins) ensures permissions are only activated when required and are managed collectively rather than individually, reducing overhead and maintaining the least privilege principle.

Step-by-Step Solution

1
Identify the governance requirement for the external auditors.
The external auditors require temporary read-only access, which corresponds to the Reader role assigned as eligible using PIM, rather than a permanent active role.
Using PIM eligibility ensures access is only active when needed, meeting the least privilege and temporary access requirement.
2
Identify the governance requirement for the internal security administrators.
The internal administrators require role management capabilities during access reviews, which corresponds to the User Access Administrator role assigned as eligible in PIM.
Making the assignment eligible ensures administrative permissions are activated only on-demand during active reviews.
3
Determine the correct method for assigning roles to minimize administrative overhead.
Roles must be assigned to Microsoft Entra security groups rather than individual user accounts.
Group-based role assignments scale easily and reduce the administrative burden of individual permissions management.

Key Concept

Just-in-time (JIT) access governance using Microsoft Entra Privileged Identity Management (PIM) group-based eligible assignments.
Question 375Question

An organization is deploying a media rendering application on Azure Virtual Machines. The application has the following storage requirements:
- A shared file system that must be concurrently mounted by multiple Linux rendering nodes using the NFS protocol, requiring low-latency file access and resilience against availability zone outages.
- High-performance block storage for active rendering jobs that requires sub-millisecond write response times and high IOPS.

Which two storage solutions should you include in the design?

Select all that apply

Show answer & explanation

Answer: A Premium Azure Files share configured with Zone-Redundant Storage (ZRS); An Azure Ultra Disk managed disk

Answer

To meet the requirements, you should include a Premium Azure Files share configured with Zone-Redundant Storage (ZRS) to serve as the shared file system for the Linux nodes, and an Azure Ultra Disk managed disk to support the high performance needed for active rendering jobs.
A Premium Azure Files share with Zone-Redundant Storage (ZRS) meets both the NFS protocol requirement for Linux rendering nodes and provides high availability across zones. An Azure Ultra Disk managed disk is the correct choice for the active rendering jobs as it guarantees the required sub-millisecond write latency and high IOPS.

Step-by-Step Solution

1
Evaluate the shared file system protocol and redundancy requirements.
The file system requires NFS protocol support and must survive availability zone outages. Premium Azure Files supports NFS v4.1 and can be deployed with Zone-Redundant Storage (ZRS). Standard Azure Files does not support NFS and Locally Redundant Storage (LRS) does not offer zone resilience.
This step ensures that the selected file storage meets the protocol and high availability constraints of the Linux nodes.
2
Evaluate the block storage performance requirements.
The block storage must support active rendering jobs requiring sub-millisecond write latency and high IOPS. Ultra Disk managed disks meet this sub-millisecond latency threshold, whereas Standard SSDs do not.
This step matches the workload performance profile to the appropriate managed disk SKU.

Key Concept

Designing Azure storage by mapping workload requirements to the correct storage types, tiers, protocol support (NFS/SMB), and redundancy configurations.
Estimated Time:2m 0s
Question 376Question

You are designing a disaster recovery (DR) solution from the North Europe region to the West Europe region for an e-commerce application hosted on Azure Virtual Machines. The application architecture and workload metrics are as follows:

* Web Tier: Two virtual machines, each with a single 128 GB128\text{ GB} Standard SSD OS disk. The average write churn is 0.2 MB/s0.2\text{ MB/s} per VM.
* Application Tier: Two virtual machines, each with a single 256 GB256\text{ GB} Premium SSD disk. The average write churn is 3 MB/s3\text{ MB/s} per VM.
* Database Tier: One SQL Server virtual machine with three Premium SSD disks: an OS disk (1.5 MB/s1.5\text{ MB/s} write churn), a data disk (12 MB/s12\text{ MB/s} write churn), and a transaction log disk (26 MB/s26\text{ MB/s} write churn).

The business continuity requirements specify:

* Web and Application Tiers: Recovery Point Objective (RPO) of 2 hours2\text{ hours} and Recovery Time Objective (RTO) of 2 hours2\text{ hours}.
* Database Tier: RPO of 15 seconds15\text{ seconds} and RTO of 30 minutes30\text{ minutes}.

Which two replication methods should you include in the disaster recovery design? (Select two.)

Select all that apply

Show answer & explanation

Answer: Replicate the Web and Application tier virtual machines to the target region using Azure Site Recovery.; Replicate the database tier workload to the target region using SQL Server Always On Availability Groups.

Answer

Replicate the Web and Application tier virtual machines to the target region using Azure Site Recovery, and replicate the database tier workload to the target region using SQL Server Always On Availability Groups.
The correct design uses Azure Site Recovery for the Web and Application tiers because their write churn rates (0.2 MB/s0.2\text{ MB/s} and 3 MB/s3\text{ MB/s}) are well within standard ASR limits (10 MB/s10\text{ MB/s} per disk) and their 2 hours2\text{ hours} RPO requirement is easily satisfied. The database tier workload must be replicated using SQL Server Always On Availability Groups because the 15 seconds15\text{ seconds} RPO cannot be met by ASR's replication frequency, and SQL Server's native replication effectively handles the high 26 MB/s26\text{ MB/s} log disk write churn.

Step-by-Step Solution

1
Analyze the RPO requirements for each application tier.
The Web and Application tiers require an RPO of 2 hours2\text{ hours}, which is compatible with the replication frequencies of Azure Site Recovery. The Database tier requires a near-real-time RPO of 15 seconds15\text{ seconds}.
Azure Site Recovery (ASR) provides replication with recovery points typically generated every few minutes, which cannot satisfy a sub-minute (e.g., 15 seconds15\text{ seconds}) RPO. Therefore, a database-native synchronous or low-latency asynchronous replication method is required for the database tier.
2
Evaluate the write churn limits for the database VM's disks against Azure Site Recovery limits.
The database transaction log disk write churn is 26 MB/s26\text{ MB/s}. Under standard Azure Site Recovery policies, the write churn limit is 10 MB/s10\text{ MB/s} per Premium SSD. ASR High Churn support can handle up to 20 MB/s20\text{ MB/s} (standard high churn) or 30 MB/s30\text{ MB/s} (highest churn) depending on VM sizing, but ASR still cannot meet the RPO requirement.
Validating write churn prevents replication lag, disk throttling, and failure to meet recovery objectives. The log disk's high churn of 26 MB/s26\text{ MB/s} makes it a poor candidate for standard ASR replication.
3
Evaluate the write churn limits for the Web and Application VM disks.
The Web tier has 0.2 MB/s0.2\text{ MB/s} churn, and the Application tier has 3 MB/s3\text{ MB/s} churn. Both are well below the 10 MB/s10\text{ MB/s} standard ASR limit.
This confirms that ASR is fully supported and cost-effective for replication of the Web and Application tiers.
4
Synthesize the final architecture.
Web and App tiers are replicated via Azure Site Recovery. The Database tier is replicated using SQL Server Always On Availability Groups to West Europe.
Combining Azure Site Recovery for stateless/low-churn application tiers with database-native replication for stateful/high-churn database tiers is the recommended Azure architecture to meet heterogeneous RPO/RTO and churn requirements.

Key Concept

Azure Site Recovery replication limits and using database-native replication for workloads with sub-minute RPO or high write churn.
Estimated Time:3m 0s
Question 377Question

An organization plans to deploy a microservices-based application consisting of several containerized background services. The services need to scale dynamically in response to incoming messages in an Azure Service Bus queue using Kubernetes Event-driven Autoscaling (KEDA). The organization wants to avoid managing Kubernetes nodes, clusters, or control planes, and does not require direct access to the Kubernetes API. Which Azure service should you recommend to host these containerized services?

Show answer & explanation

Answer: Azure Container Apps

Answer

Azure Container Apps
Azure Container Apps is a serverless container platform designed for microservices and background workloads. It natively supports Kubernetes Event-driven Autoscaling (KEDA), enabling scale-to-zero configurations based on metrics such as Azure Service Bus message counts, all while eliminating the administrative overhead of managing Kubernetes clusters, nodes, or control planes.

Step-by-Step Solution

1
Identify the core workload requirement.
The application requires hosting background processing microservices that scale dynamically based on Azure Service Bus queue messages using KEDA.
This establishes the scale trigger and deployment pattern required by the design.
2
Evaluate the administrative overhead constraints.
The organization wants to avoid managing nodes, clusters, or control planes, and does not require direct access to the Kubernetes API.
This rules out full-featured Kubernetes orchestrators that require active infrastructure management.
3
Select the Azure container service that meets both scaling and management requirements.
Azure Container Apps provides a serverless platform that supports KEDA out of the box without requiring cluster administration.
It matches all requirements while minimizing administrative effort, aligning with Microsoft best practices.

Key Concept

Azure container hosting service selection based on operational overhead and scaling requirements
Question 378Question

A company is migrating a business-critical application to Azure Virtual Machines. The database VMs require a robust backup strategy to meet strict operational recovery objectives. The backup design must satisfy the following technical requirements:
- Backups must be replicated to a secondary Azure region to allow restore operations even if the primary region is completely unavailable.
- To support rapid recovery of database files, local snapshots must be kept in the hardware source tier for 7 days.
- Daily recovery points must be retained in the vault for 45 days.

Which backup configuration should you select to meet these requirements?

Show answer & explanation

Answer: A Recovery Services vault configured with Geo-Redundant Storage (GRS) using a backup policy of the Enhanced tier with the snapshot retention period set to 7 days.

Answer

A Recovery Services vault configured with Geo-Redundant Storage (GRS) using a backup policy of the Enhanced tier with the snapshot retention period set to 7 days.
The configuration using a Recovery Services vault with Geo-Redundant Storage (GRS) and an Enhanced tier policy is correct. A Recovery Services vault is required to back up Azure VMs. GRS replicates the backup data to a secondary paired region to survive a primary region failure. The Enhanced policy tier is necessary because it supports custom snapshot (instant restore) retention up to 30 days, allowing the specified 7-day local snapshot requirement to be met.

Step-by-Step Solution

1
Determine the required vault type for Azure Virtual Machine backups.
Azure Virtual Machine backups require a Recovery Services vault, as Backup vaults do not support this workload type.
Ensures the backup target is compatible with the source workload.
2
Evaluate the storage redundancy requirement for regional disaster recovery.
The vault must be configured with Geo-Redundant Storage (GRS) to replicate backups to a secondary region and survive a primary region failure.
Meets the requirement for replication to a secondary Azure region.
3
Determine the required backup policy tier for a 7-day snapshot retention.
An Enhanced policy tier must be used because the Standard policy tier restricts instant recovery snapshot retention to a maximum of 5 days.
Ensures local snapshots are kept for 7 days to meet the low RTO objective.

Key Concept

Azure Backup vault types, storage redundancy, and policy tier capabilities
Question 379Question

A company plans a new deployment of a customer portal application that requires 30 separate relational databases, one for each regional office. The databases have highly variable and unpredictable usage patterns throughout the day, with peaks occurring at different times. The solution must ensure high availability, minimize administrative overhead, and optimize hosting costs by sharing database resources. No database requires instance-level features such as SQL Server Agent or CLR. Which Azure SQL deployment option should you recommend?

Show answer & explanation

Answer: Azure SQL Database elastic pools

Answer

Azure SQL Database elastic pools
Azure SQL Database elastic pools allow multiple databases to share a single pool of resources (eDTUs or vCores). This matches the requirements of having 30 databases with unpredictable, non-overlapping usage spikes, optimizing cost and minimizing administrative effort while providing built-in high availability.

Step-by-Step Solution

1
Analyze the application requirements.
Requirements include: 30 separate databases, unpredictable/variable usage peaks at different times, shared resources to optimize costs, high availability, minimized administrative overhead, and no requirement for instance-level features.
This establishes the constraints and drivers for selecting the appropriate database service tier.
2
Evaluate the options against administrative overhead and resource sharing.
Platform-as-a-Service (PaaS) options (Azure SQL Database) are preferred over Infrastructure-as-a-Service (IaaS) (SQL Server on Azure VMs) to minimize management overhead. Elastic pools allow resources to be shared across multiple databases.
Eliminating VMs reduces patching and maintenance overhead, while choosing shared resources addresses the cost optimization goal.
3
Evaluate the database tier requirements.
Since there are no instance-level compatibility requirements (like SQL Server Agent, CLR, or cross-database queries), Azure SQL Database is preferred over Managed Instance. Specifically, elastic pools fit the multi-database, variable workload scenario perfectly.
This confirms that elastic pools are the most cost-effective and appropriate option that meets all specified constraints.

Key Concept

Selecting the appropriate Azure SQL deployment option based on resource sharing, cost optimization, and compatibility requirements.
Question 380Question

A gaming company is designing a secure storage solution to share log files stored in an Azure Blob Storage container named `gamelogs` with an external game analytics agency. The agency requires access to the container for 30 days from a specific public IP range. You must ensure that access can be revoked immediately if a security breach occurs. Additionally, a group of internal security administrators must be able to temporarily elevate their permissions to manage the storage account settings when an incident is reported, but they must not hold these privileges permanently. Which two actions should you include in the storage security design? (Select two.)

Select all that apply

Show answer & explanation

Answer: Create a stored access policy on the container, and then generate a Shared Access Signature (SAS) token linked to this policy.; Configure Microsoft Entra Privileged Identity Management (PIM) to make the security administrators eligible for the Storage Account Contributor role.

Answer

The correct actions are: creating a stored access policy on the container to generate a SAS token, and configuring Microsoft Entra Privileged Identity Management (PIM) to make security administrators eligible for the Storage Account Contributor role.
The correct approach uses a stored access policy on the blob container to generate the SAS token, allowing for instant revocation if needed by modifying or deleting the policy. It also uses Microsoft Entra Privileged Identity Management (PIM) to configure eligible role assignments for the security administrators, which ensures they only receive elevated permissions (just-in-time) after requesting activation.

Step-by-Step Solution

1
Analyze the requirement for sharing blob container access with external partners with the ability to revoke immediately.
Identify that a Shared Access Signature (SAS) is required, but it must be linked to a stored access policy to support immediate revocation without rotating the account keys.
Ad-hoc SAS tokens cannot be revoked individually; deleting or modifying a stored access policy is the only way to revoke a token without key rotation.
2
Analyze the requirement for temporary, non-permanent elevated permissions for security administrators.
Identify that Microsoft Entra Privileged Identity Management (PIM) must be used to configure the administrators as eligible for the required role, rather than active.
Configuring the role as eligible enforces just-in-time (JIT) access, aligning with the principle of least privilege.

Key Concept

Designing data storage security and access control using stored access policies and just-in-time identity management.
PreviousPage 19 / 60Next