Design Data Storage Solutions

315 questions

Question 1Question

A retail corporation plans to migrate an on-premises inventory management system to Microsoft Azure. The database tier has the following requirements:
- The system must run a specialized database monitoring agent directly on the database server's operating system, which requires local administrator privileges.
- The environment must support SQL Server Agent to run scheduled maintenance and data synchronization jobs.
- The administration team must minimize the operational overhead of manually managing operating system updates and SQL Server patches.
- The database storage must support high-performance transactions, with the ability to dynamically scale disk performance up to 80,00080,000 IOPS.

Which Azure SQL deployment option should you recommend?

Show answer & explanation

Answer: SQL Server on Azure Virtual Machines

Answer

SQL Server on Azure Virtual Machines
SQL Server on Azure Virtual Machines is correct because it provides full access to the underlying operating system, allowing the installation of custom monitoring agents with local administrator privileges. Automated patching overhead is minimized through the SQL Server IaaS Agent Extension.

Step-by-Step Solution

1
Identify the core operating system and application requirements.
The requirement for a local OS-level monitoring agent with administrative access rules out fully managed platform services.
Managed services like Azure SQL Database and Azure SQL Managed Instance abstract the underlying operating system and do not allow administrative logins or local agent installations.
2
Verify how the administrative patching overhead requirement can be met.
SQL Server on Azure Virtual Machines supports Automated Patching when registered with the SQL Server IaaS Agent Extension.
This minimizes the operational overhead of manual patching while still providing full OS-level control.
3
Evaluate storage performance capabilities for the chosen solution.
SQL Server on Azure VMs can be configured with Premium SSD v2 or Ultra Disk to support scaling up to 80,00080,000 IOPS.
This satisfies the high-performance transaction scaling requirements.

Key Concept

Selecting SQL Server on Azure VMs when local OS access or third-party agent installation is required, combined with IaaS extension for automated management.
Question 2Question

You are designing an Azure migration strategy for several legacy databases. Match each workload scenario on the left with the correct Azure Cosmos DB API on the right to ensure the migration requires minimal application refactoring while meeting performance and architectural requirements.

Click a left item, then click its matching right item

Items

A telemetry ingestion application that processes high-frequency time-series data from IoT devices. The legacy database uses a wide-column storage model, and developers query it using CQL-based scripts that must be preserved.
A fraud-detection application that analyzes relationships between financial transactions, user accounts, and device fingerprints to find suspicious circular paths. The application requires complex multi-hop query traversals using vertices and edges.
An e-commerce product catalog that is being migrated from an on-premises database. It stores documents in BSON format, relies on nested arrays, and utilizes existing application drivers that communicate over port 27017.
A globally distributed user session state store that currently utilizes Azure Table Storage. The business requires migrating to a database that guarantees sub-10ms read and write latencies with a 99.999% availability SLA and dedicated throughput.

Matches

Show answer & explanation

Answer

Match the wide-column CQL telemetry application to Azure Cosmos DB for Apache Cassandra; match the graph-based fraud-detection application to Azure Cosmos DB for Apache Gremlin; match the BSON-based product catalog to Azure Cosmos DB for MongoDB; and match the low-latency Table Storage workload to Azure Cosmos DB for Table.
Matching each legacy system to its corresponding wire-compatible Azure Cosmos DB API allows developers to preserve client-side code, drivers, and query structures while gaining the benefits of a fully managed cloud database.

Step-by-Step Solution

1
Analyze the technical requirements of the first scenario (CQL and wide-column).
Identify that the Cassandra Query Language (CQL) and wide-column store map directly to the Cassandra API.
This minimizes development effort by allowing the reuse of existing Cassandra drivers and queries.
2
Analyze the technical requirements of the second scenario (vertices, edges, multi-hop traversals).
Identify that a property graph model utilizing TinkerPop/Gremlin maps directly to the Gremlin API.
Graph databases are optimized for traversing relationships between entities.
3
Analyze the technical requirements of the third scenario (BSON, port 27017, nested arrays).
Identify that these details describe MongoDB database communications, which map to the MongoDB API.
Cosmos DB for MongoDB supports the MongoDB wire protocol, allowing applications to connect using standard MongoDB client drivers.
4
Analyze the technical requirements of the fourth scenario (Azure Table Storage migration with sub-10ms latency and 99.999% SLA).
Identify that the Table API provides a drop-in replacement for Table Storage with premium performance guarantees.
Azure Cosmos DB for Table offers turnkey global distribution, dedicated throughput, and single-digit millisecond latency SLAs compared to standard Azure Table Storage.

Key Concept

Selecting the appropriate Azure Cosmos DB API based on legacy database systems, query APIs, protocols, and performance requirements.
Question 3Question

A company is designing a storage solution for a document management application. The documents must be stored in Azure Blob Storage.

The solution must meet the following requirements:
- If an entire Azure region suffers a major outage, the storage solution must remain resilient and prevent data loss.
- Access to the files must be granted to external vendors using Shared Access Signatures (SAS) that can be invalidated immediately if a security compromise is suspected.

Which two storage configurations should you recommend to meet the requirements?

Select all that apply

Show answer & explanation

Answer: Configure the storage account to use Geo-redundant storage (GRS).; Create a stored access policy on the container and associate it with the Shared Access Signatures (SAS).

Answer

Configure the storage account to use Geo-redundant storage (GRS) and create a stored access policy on the container to associate with the Shared Access Signatures (SAS).
To ensure protection against regional outages, the storage account must be configured with Geo-redundant storage (GRS), which replicates data to a secondary region. To allow immediate invalidation of Shared Access Signatures (SAS), you must use a stored access policy, which allows you to revoke or change the permissions of associated SAS tokens without modifying the storage account keys.

Step-by-Step Solution

1
Analyze the resiliency requirement for regional outages.
Locally redundant storage (LRS) is insufficient because it only replicates data within a single datacenter. Geo-redundant storage (GRS) must be selected to ensure data is copied to a secondary region, providing protection against a regional failure.
Choosing the correct storage redundancy tier ensures business continuity during regional disasters.
2
Analyze the security requirement for immediate SAS revocation.
Ad-hoc SAS URIs cannot be individually revoked without rotating the storage account keys (which affects all SAS tokens). Associating the SAS with a stored access policy allows the policy to be modified or deleted, instantly revoking all SAS tokens tied to that policy.
Stored access policies decouple the SAS token validation from account keys, allowing fine-grained and immediate access control revocation.

Key Concept

Azure storage redundancy options and secure access delegation via stored access policies.
Question 4Question

You are designing an Azure Blob Storage solution for storing virtual machine backups. The solution must meet the following requirements:
- Ensure the backups remain available if a single datacenter in the primary region fails.
- Ensure backups can be retrieved within seconds if a restore is initiated.
- Minimize storage costs.

Which storage configuration should you recommend?

Show answer & explanation

Answer: Zone-redundant storage (ZRS) in the Cool access tier

Answer

Zone-redundant storage (ZRS) in the Cool access tier
Zone-redundant storage (ZRS) replicates data synchronously across three Azure availability zones in the primary region, meeting the requirement to survive a single datacenter (zone) failure. The Cool access tier is cost-effective for storage that is not accessed frequently but requires immediate retrieval times, which matches the backup restoration requirements.

Step-by-Step Solution

1
Identify the resiliency requirement.
The solution must survive a single datacenter failure in the primary region.
Locally-redundant storage (LRS) is insufficient because it only replicates within a single datacenter. Zone-redundant storage (ZRS) or geo-redundant options are required.
2
Analyze retrieval time requirements.
The backups must be retrieved within seconds (sub-second retrieval).
This rules out the Archive access tier, which requires hours for data rehydration. The Hot or Cool tiers are appropriate.
3
Compare cost and redundancy options.
Zone-redundant storage (ZRS) in the Cool tier is selected.
ZRS meets the datacenter resilience requirement at a lower cost than geo-redundant options like RA-GRS, and the Cool tier provides immediate retrieval at a lower storage cost than the Hot tier.

Key Concept

Azure Storage Redundancy and Access Tiers
Question 5Question

A company is developing a fleet management application. The application will store real-time telemetry from 50,000 delivery vehicles. The workload has a read/write ratio of 80% writes and 20% reads. The data must be distributed across three Azure regions to support global users, and the solution must avoid partition throttling while maintaining high availability. Which configuration should you recommend for the Azure Cosmos DB container?

Show answer & explanation

Answer: Use vehicleId as the partition key and enable multi-region replication.

Answer

Use vehicleId as the partition key and enable multi-region replication.
The correct option is to use vehicleId as the partition key and enable multi-region replication. vehicleId is a high-cardinality key that distributes writes evenly across logical partitions, while multi-region replication ensures low latency and high availability across the three target regions.

Step-by-Step Solution

1
Evaluate the partition key requirements based on the high write volume (80% writes).
Identify that a high-cardinality key is required to distribute writes evenly and avoid hot partitions.
Choosing a low-cardinality key like status or date would concentrate writes into a few partitions, leading to throttling.
2
Evaluate the replication and redundancy requirements for a global application in three regions.
Identify that multi-region replication is required to serve users globally.
Locally redundant storage (LRS) keeps data within a single datacenter facility and cannot support multi-region distribution.

Key Concept

Selecting high-cardinality partition keys and configuring appropriate global distribution in Azure Cosmos DB to prevent throttling and ensure high availability.
Question 6Question

An organization is designing the storage infrastructure for a new containerized application workflow on Azure. The architecture must satisfy the following technical requirements:

- Provide a shared, POSIX-compliant file system for a cluster of Linux nodes that supports the NFS v4.1 protocol and can withstand the outage of a single Availability Zone within the primary Azure region.
- Provide block storage for a transaction-intensive database workload that requires consistent sub-millisecond disk write latencies.

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

Select all that apply

Show answer & explanation

Answer: Configure Azure Files Premium tier with Zone-Redundant Storage (ZRS) and the NFS protocol for the shared file system; Configure Premium SSD v2 managed disks for the database workload

Answer

Configure Azure Files Premium tier with Zone-Redundant Storage (ZRS) using NFS, and configure Premium SSD v2 managed disks for the database workload.
Configuring Azure Files Premium tier with Zone-Redundant Storage (ZRS) using NFS provides a POSIX-compliant, zone-resilient shared file system that meets the Linux cluster requirements. Configuring Premium SSD v2 managed disks delivers the necessary low latency and high IOPS for transaction-intensive database workloads.

Step-by-Step Solution

1
Evaluate the shared file system requirements.
The file system must be POSIX-compliant, support NFS v4.1, and tolerate a zone outage. Azure Files Premium tier supports NFS v4.1 and can use Zone-Redundant Storage (ZRS) to meet these needs.
Standard tier Azure Files does not support NFS, and LRS does not survive zone outages.
2
Evaluate database storage requirements.
The database needs consistent sub-millisecond disk write latencies. Premium SSD v2 managed disks provide the required IOPS and low-latency metrics.
Standard HDD and Standard SSD disks cannot guarantee sub-millisecond latencies.
3
Verify security and protocol compatibility.
Reject SAS token authentication since NFS file shares in Azure Files rely on network-level security and POSIX permissions rather than SAS tokens, and long-lived SAS tokens introduce risk.
Ensures the recommended solution is technically feasible and secure.

Key Concept

Azure storage design matching performance, protocol (NFS/SMB), and resiliency (LRS/ZRS) requirements to appropriate disk and file service configurations.
Question 7Question

An international logistics company is designing the data tier for a new transport management platform. The platform consists of two distinct subsystems:

* The tracking subsystem requires a database that supports cross-database queries, SQL Server Agent for scheduling route calculation jobs, and Common Language Runtime (CLR) integration. The solution must minimize operational overhead.
* The invoicing subsystem requires a single database that experiences highly variable traffic patterns, including long periods of zero activity. The solution must minimize compute costs during idle periods.

Which two Azure SQL services should you recommend to support the subsystems? (Select TWO).

Select all that apply

Show answer & explanation

Answer: Azure SQL Managed Instance for the tracking subsystem; Azure SQL Database serverless for the invoicing subsystem

Answer

Azure SQL Managed Instance for the tracking subsystem, and Azure SQL Database serverless for the invoicing subsystem
The correct recommendations are Azure SQL Managed Instance for the tracking subsystem and Azure SQL Database serverless for the invoicing subsystem. Azure SQL Managed Instance supports instances requiring SQL Server Agent, CLR integration, and cross-database queries without the administrative overhead of managing virtual machines. Azure SQL Database serverless is ideal for a single database with unpredictable traffic and idle periods because it automatically scales compute resources and pauses during inactivity to reduce compute costs to zero.

Step-by-Step Solution

1
Analyze the requirements for the tracking subsystem.
The subsystem requires legacy compatibility features including SQL Server Agent, CLR integration, and cross-database queries, but specifies that operational overhead must be minimized.
This rules out Azure SQL Database single database (which lacks SQL Agent/CLR/cross-db query support) and makes SQL Server on Azure VMs less optimal than a PaaS solution due to higher operational overhead.
2
Select the optimal database service for the tracking subsystem.
Azure SQL Managed Instance is chosen.
Managed Instance provides near 100% compatibility with the SQL Server database engine, including SQL Agent, CLR, and cross-database queries, while running as a fully managed PaaS service.
3
Analyze the requirements for the invoicing subsystem.
The subsystem consists of a single database with highly variable traffic and periods of inactivity, requiring compute costs to be minimized during idle times.
This points to a serverless model where resources auto-scale and can be paused when not in use.
4
Select the optimal database service for the invoicing subsystem.
Azure SQL Database serverless is chosen.
Azure SQL Database serverless automatically scales compute and supports auto-pausing, billing only for storage when paused, which perfectly satisfies the cost optimization requirement for a single database.

Key Concept

Azure SQL service tier selection based on feature compatibility (SQL Agent, CLR, cross-database queries) and workload auto-scaling requirements.
Question 8Question

An organization is migrating a high-performance Linux-based application to Azure Virtual Machines. The application requires a shared file system that supports POSIX-compliant file locks and the NFS protocol. The design requires that the storage solution must survive a single zone outage within an Azure region while maintaining high performance. Which storage solution should you recommend?

Show answer & explanation

Answer: Premium Azure Files configured with Zone-Redundant Storage (ZRS) using the NFS protocol.

Answer

Premium Azure Files configured with Zone-Redundant Storage (ZRS) using the NFS protocol.
Premium Azure Files configured with Zone-Redundant Storage (ZRS) using the NFS protocol is correct. Premium Azure Files natively supports NFS 4.1, which provides full POSIX-compliant locking. ZRS replicates data across three availability zones in the region, ensuring the storage survives a zone outage.

Step-by-Step Solution

1
Identify the protocol and locking requirements.
The application requires NFS and POSIX-compliant file locks. Premium Azure Files supports NFS 4.1, which meets this requirement.
Standard Azure Files does not support NFS, which eliminates options using that tier.
2
Determine the redundancy and performance requirements.
The solution must survive a zone outage (requiring Zone-Redundant Storage - ZRS) and maintain high performance (Premium tier).
This rules out options utilizing Locally Redundant Storage (LRS).
3
Evaluate the viability of lifecycle tiering.
Workloads with active file system access cannot use the Archive tier because the retrieval latency is too high.
This eliminates designs proposing Blob Storage with Archive tier lifecycle policies.

Key Concept

Selecting Azure Files Premium tier with ZRS for NFS and zone redundancy.
Question 9Question

A healthcare provider plans to allow external clinical researchers to upload trial datasets to a specific Azure Blob Storage container. You need to design an access solution that meets the following requirements:
- The researchers must have write access for a maximum of 48 hours.
- You must be able to revoke access immediately if a security compromise is detected.
- The solution must minimize administrative effort.

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

Select all that apply

Show answer & explanation

Answer: Create a stored access policy on the blob container.; Generate a Shared Access Signature (SAS) token that references the stored access policy.

Answer

To meet the security and revocation requirements with minimal administrative overhead, you must create a stored access policy on the blob container and generate a Shared Access Signature (SAS) token that references this policy.
To meet the requirement of immediate revocation, you must define a stored access policy on the blob container and then generate a Shared Access Signature (SAS) token that references this policy. If a compromise is detected, you can delete or modify the stored access policy, which immediately invalidates the SAS token without needing to rotate the storage account keys.

Step-by-Step Solution

1
Identify the revocation requirement.
Determine that ad-hoc SAS tokens cannot be revoked individually without rotating the master storage account keys.
Stored access policies enable granular control and immediate revocation of SAS tokens by modifying or deleting the policy.
2
Bind the access method to the policy.
Generate a service SAS token that inherits its parameters and validity from the stored access policy.
This guarantees that if the policy is removed or updated, the token is invalidated instantly.
3
Evaluate administrative overhead constraints.
Avoid direct RBAC role assignments to individual user accounts.
Direct assignments increase management complexity, violating Azure governance and least-privilege scaling best practices.

Key Concept

Delegating access to Azure Storage containers securely using Stored Access Policies to support revocation.
Estimated Time:1m 0s
Question 10Question

An enterprise stores large volumes of raw sensor data in Parquet format within an Azure Data Lake Storage Gen2 container. Members of the data engineering team need to run occasional, exploratory SQL queries to analyze the schema and contents of new files. They do not want to load the data into a database or keep compute clusters running when no queries are active.

Which Azure Synapse Analytics component is the most appropriate option to satisfy these requirements?

Show answer & explanation

Answer: A serverless SQL pool

Answer

A serverless SQL pool
The correct option is a serverless SQL pool because it allows data engineers to query data in the data lake directly without loading it or provisioning a cluster. It charges per query based on data processed, aligning with the requirement to avoid idle compute costs.

Step-by-Step Solution

1
Analyze the requirements
Occasional, exploratory SQL queries directly on Parquet files in Azure Data Lake Storage Gen2 without provisioning persistent compute clusters.
This establishes that we need an on-demand query engine that charges based on usage rather than continuous provisioning.
2
Evaluate the capabilities of serverless SQL pools vs dedicated SQL pools in Azure Synapse Analytics
Serverless SQL pools run queries on-demand and scale compute automatically, charging only for data processed. Dedicated SQL pools require running clusters and data ingestion.
This helps identify the Synapse component that satisfies the requirement to minimize idle compute cost and query files directly.

Key Concept

Azure Synapse SQL Serverless vs Dedicated Pools
Question 11Question

A healthcare organization is designing a cloud-based clinical trial platform. Patient health records are stored in an Azure Blob Storage container named `trials`. A third-party auditing firm requires read-only access to this container for a period of 120120 days. The security architecture must ensure that the access can be immediately revoked at any time without rotating the storage account access keys or impacting other applications. Additionally, all access requests must originate from the auditing firm's public IP range of 198.51.100.0/24198.51.100.0/24.

Which access control strategy should you recommend to meet these requirements?

Show answer & explanation

Answer: Create a stored access policy on the container, and then generate a service Shared Access Signature (SAS) token that references the policy and specifies the allowed IP address range.

Answer

Create a stored access policy on the container, and then generate a service Shared Access Signature (SAS) token that references the policy and specifies the allowed IP address range.
The correct option recommends creating a stored access policy on the container and generating a service SAS token referencing it. A stored access policy provides a way to manage SAS tokens on the server side, allowing revocation by simply deleting or modifying the policy without rotating the storage account keys. It also supports specifying IP address constraints directly in the SAS token parameters.

Step-by-Step Solution

1
Analyze the access scope and revocation requirements.
Identify that the access is limited to a single container for a specific duration, and must be immediately revokable without rotating the storage account keys.
This determines that an ad-hoc SAS token is unsuitable, and a mechanism linked to a stored access policy is required.
2
Compare SAS implementation options.
Confirm that a service SAS referencing a stored access policy allows revocation on the server side by deleting or updating the policy.
This meets the key requirement of revocation without rotating the primary or secondary storage account keys.
3
Apply additional network security controls to the SAS parameter definition.
Verify that the service SAS token can restrict access to the specific external IP address range.
This satisfies the requirement that all requests must originate from the auditing firm's public IP range.

Key Concept

Stored Access Policies and Shared Access Signatures
Question 12Question

A healthcare organization is migrating an on-premises Electronic Health Record (EHR) system to Azure. The design requires configuring secure access to an Azure Storage account named ehrdata that contains sensitive patient medical images in a blob container.

The solution must meet the following security requirements:
- External partner radiologists must be granted temporary read-only access to the blob container for 7 days. This access must be immediately revocable at any time before the 7 days expire.
- Internal compliance auditors require access to review the data, and the configuration must enforce scalable access control using identity best practices.
- Security administrators must be able to rotate storage keys, but only during scheduled audit windows, requiring manager approval before they can perform this action.

Which three actions should you include in the storage security and access control design? (Select three.)

Select all that apply

Show answer & explanation

Answer: Create a Stored Access Policy on the destination container, and generate a Shared Access Signature (SAS) token associated with that policy for the external radiologists.; Assign the Storage Blob Data Reader role to a Microsoft Entra ID security group containing the internal auditors.; Configure Microsoft Entra Privileged Identity Management (PIM) to make the security administrators eligible for the Storage Account Key Operator Service Role, requiring approval to activate.

Answer

To secure the storage account, you should create a Stored Access Policy on the destination container and generate a associated SAS token; assign the Storage Blob Data Reader role to a Microsoft Entra ID security group rather than individual users; and configure Microsoft Entra PIM to make security administrators eligible for the Storage Account Key Operator Service Role with activation approval required.
The correct architecture leverages a Stored Access Policy to bind the SAS token lifetime and permissions, facilitating revocation at any time. It uses Microsoft Entra ID security groups for scalable role assignments to enforce governance. Finally, it implements Privileged Identity Management (PIM) with eligible role assignments to enforce just-in-time (JIT) administrative access requiring workflow approval.

Step-by-Step Solution

1
Address external partner access security
Create a Stored Access Policy on the container and generate an associated SAS token.
This configuration allows the organization to revoke the SAS token early by changing the stored policy constraints or deleting the policy, without impacting other integrations.
2
Address auditor access scalability
Create a security group in Microsoft Entra ID, add the auditors to the group, and assign the Storage Blob Data Reader role to the group.
Direct role assignments to individual users do not scale and make access governance auditing difficult.
3
Address administrator privilege escalation
Configure Privileged Identity Management (PIM) with eligible assignments for the Storage Account Key Operator Service Role, requiring approval.
Active assignments leave administrative privileges permanently active, which violates the principle of least privilege and just-in-time access.

Key Concept

Applying least privilege, scalability, and revocability to Azure Storage security.
Estimated Time:3m 0s
Question 13Question

An organization is designing a relational data storage solution for a new patient scheduling portal. The database tier must support the following requirements:

* Run on a single database using a serverless compute model that automatically scales compute resources based on workload demand.
* Automatically pause the database during periods of inactivity to minimize costs.
* Ensure that database backups are resilient against a primary datacenter outage.

Which deployment option should you recommend?

Show answer & explanation

Answer: Azure SQL Database serverless with Zone-Redundant Storage (ZRS) backup redundancy

Answer

Azure SQL Database serverless with Zone-Redundant Storage (ZRS) backup redundancy
The correct option is the one specifying Azure SQL Database serverless with Zone-Redundant Storage (ZRS) backup redundancy. Azure SQL Database serverless automatically scales compute for single databases and includes an auto-pause feature to optimize costs during inactive periods. Selecting ZRS replication for database backups ensures that the data is replicated across different availability zones, meeting the requirement to remain resilient against a primary datacenter outage.

Step-by-Step Solution

1
Analyze the database operational model requirements.
The solution requires a single database that supports auto-scaling and auto-pausing during periods of inactivity. This points directly to the serverless compute tier of Azure SQL Database, as Azure SQL Managed Instance and SQL Server on Azure VMs do not support auto-pausing.
To eliminate relational database deployment models that do not meet the primary cost and scalability requirements.
2
Evaluate backup redundancy options for disaster resilience.
The backups must survive a primary datacenter outage. Locally Redundant Storage (LRS) is insufficient because it replicates data within a single datacenter. Zone-Redundant Storage (ZRS) replicates data across three Azure availability zones within the region, providing resilience against datacenter failures.
To select the storage redundancy type that matches the organization's disaster recovery guidelines.
3
Cross-reference disk requirements and administrative limits.
SQL Server on Azure VMs is ruled out due to high management overhead, and using Standard HDD for transaction logs would cause severe performance bottlenecks.
To ensure no other options satisfy the constraints.

Key Concept

Selecting appropriate Azure SQL service tiers and storage redundancy configurations based on workload patterns and disaster recovery requirements.
Question 14Question

A company is planning the storage architecture for a new application. The business requirements state that the data must be replicated synchronously across three separate availability zones within the primary region to ensure high availability. Which two Azure Storage replication options should you recommend to meet this requirement? (Select two.)

Select all that apply

Show answer & explanation

Answer: Zone-redundant storage (ZRS); Geo-zone-redundant storage (GZRS)

Answer

Zone-redundant storage (ZRS) and Geo-zone-redundant storage (GZRS)
The correct options are Zone-redundant storage (ZRS) and Geo-zone-redundant storage (GZRS). ZRS replicates data synchronously across three availability zones in the primary region. GZRS combines the high availability of ZRS in the primary region with asynchronous replication to a secondary region, meaning both options meet the requirement of synchronous zonal replication in the primary region.

Step-by-Step Solution

1
Analyze the primary region replication requirement.
The requirement specifies synchronous replication across three availability zones within the primary region.
This determines that the storage account replication tier must support zone-redundancy in the primary region.
2
Evaluate the replication behavior of each storage tier in the primary region.
Zone-redundant storage (ZRS) and Geo-zone-redundant storage (GZRS) both replicate data synchronously across three zones in the primary region. Locally redundant storage (LRS) and Geo-redundant storage (GRS) only replicate within a single zone/datacenter in the primary region.
Comparing the options isolates the two that satisfy the zone-redundancy requirement.

Key Concept

Azure Storage Zone Redundancy
Estimated Time:45s
Question 15Question

You are an Azure Solutions Architect designing a data storage solution for a global media streaming platform. The platform must store real-time user playback progress and watch history. The workload has a read-to-write ratio of approximately 40:6040:60. The solution must be distributed across three regions (East US, West Europe, and East Asia) to achieve sub-10ms write latency at the 99th percentile and support an active-active setup. The platform requires a 99.999% availability SLA for both reads and writes. High availability and regional disaster resilience must be guaranteed for all data, including database backups.

Which two configuration options should you include in the architectural design to meet these requirements? (Select TWO)

Select all that apply

Show answer & explanation

Answer: Enable multi-region writes for the Azure Cosmos DB account to support the active-active global configuration and satisfy the low latency and high availability SLA.; Select a high-cardinality partition key, such as a combination of user ID and session ID, to distribute read and write operations evenly across logical partitions.

Answer

Enable multi-region writes for the Azure Cosmos DB account and select a high-cardinality partition key, such as a combination of user ID and session ID.
The correct solution involves enabling multi-region writes for the Azure Cosmos DB account and selecting a high-cardinality partition key (user ID + session ID). Multi-region writes ensure write operations are committed locally in all designated regions, satisfying both the sub-10ms write latency and the 99.999% write availability SLA. A high-cardinality partition key guarantees that the write-heavy workload is evenly distributed across logical and physical partitions, avoiding resource hot spots.

Step-by-Step Solution

1
Analyze global availability and latency requirements.
Identified that active-active multi-region writes are required to meet sub-10ms write latency and the 99.999% availability SLA.
Single-region write models incur cross-region network latency for writes originating in other regions, which exceeds the sub-10ms limit, and only offer 99.99% availability for writes.
2
Evaluate partitioning strategy for write-heavy workload.
Determined that a high-cardinality partition key like user ID and session ID is necessary to avoid physical partition throughput limits.
Cosmos DB distributes data based on partition keys. Low-cardinality keys like region create hot partitions that bottleneck writes and waste RU/s.
3
Evaluate backup redundancy and security configuration.
Ruled out Locally Redundant Storage (LRS) for backups and long-lived Shared Access Signatures without stored access policies.
LRS does not survive datacenter outages, and long-lived SAS tokens cannot be easily revoked if leaked, failing resiliency and security best practices.

Key Concept

Azure Cosmos DB Multi-Region Replication and Partitioning Design
Question 16Question

A company plans to migrate an on-premises SQL Server database to Azure. The database requires the use of SQL Server Agent to run scheduled maintenance jobs, and cross-database queries are heavily utilized. The database administration team wants to minimize administrative overhead for managing the underlying operating system. Which Azure SQL deployment option should you recommend?

Show answer & explanation

Answer: Azure SQL Managed Instance

Answer

Azure SQL Managed Instance
Azure SQL Managed Instance is a fully managed Platform-as-a-Service (PaaS) relational database engine that provides near 100% compatibility with on-premises SQL Server. It supports instance-level capabilities such as SQL Server Agent, cross-database queries, and Common Language Runtime (CLR), while eliminating the administrative overhead of managing the underlying operating system and hardware.

Step-by-Step Solution

1
Identify the legacy SQL Server features required by the workload.
The workload requires SQL Server Agent and cross-database queries.
These features are standard SQL Server features but are not supported by all Azure SQL deployment tiers.
2
Identify the administrative overhead requirements.
The customer wants to minimize administrative overhead for the operating system.
This rules out Infrastructure-as-a-Service (IaaS) options like SQL Server on Azure VMs, which require OS patching and management.
3
Evaluate Platform-as-a-Service (PaaS) options against the feature requirements.
Azure SQL Managed Instance supports both SQL Server Agent and cross-database queries, while Azure SQL Database (single database and elastic pools) does not support them natively.
This leaves Azure SQL Managed Instance as the only deployment option that satisfies both the legacy features and the managed OS requirements.

Key Concept

Selecting the appropriate Azure SQL deployment option based on SQL Server feature compatibility and management requirements.
Question 17Question

A company is deploying a new retail application in Azure that requires a relational database backend. The database design must satisfy the following requirements:
- Cost-effectively manage resource allocation for 20 databases that experience short, unpredictable spikes in usage.
- Ensure that database backups remain available even if a single datacenter within the primary region suffers a complete outage.

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

Select all that apply

Show answer & explanation

Answer: Azure SQL Database Elastic Pools; Zone-redundant storage (ZRS) for backup storage redundancy

Answer

Azure SQL Database Elastic Pools and Zone-redundant storage (ZRS) for backup storage redundancy.
Azure SQL Database Elastic Pools are the optimal choice to manage resource allocation and cost for multiple databases with unpredictable workloads. Zone-redundant storage (ZRS) provides the required resiliency against a single datacenter outage by replicating backup data across different availability zones within the region.

Step-by-Step Solution

1
Analyze the database resource sharing requirement.
Since there are 20 databases with unpredictable usage spikes, Azure SQL Database Elastic Pools is the most cost-effective choice to share compute resources.
Elastic Pools allow databases to share a pool of resources, preventing the need to over-provision each individual database.
2
Analyze the backup redundancy requirement.
To protect backups against a single datacenter failure within the region, Zone-redundant storage (ZRS) must be chosen.
Locally redundant storage (LRS) stores all copies within a single datacenter, which fails the requirement to survive a datacenter outage.

Key Concept

Azure SQL Database Elastic Pools and Backup Redundancy Options
Question 18Question

A company is designing a new relational database solution in Azure. The database has the following requirements:

* Must support SQL Server Agent for scheduling internal database maintenance tasks.
* Must be deployed with a private IP address within an Azure Virtual Network (VNet).

Which two Azure SQL deployment options meet these requirements?

Select all that apply

Show answer & explanation

Answer: SQL Server on Azure Virtual Machines; Azure SQL Managed Instance

Answer

SQL Server on Azure Virtual Machines and Azure SQL Managed Instance
SQL Server on Azure Virtual Machines and Azure SQL Managed Instance both natively support SQL Server Agent. Additionally, both options are deployed directly within an Azure Virtual Network, giving them private IP addresses by default.

Step-by-Step Solution

1
Identify the requirement for SQL Server Agent support.
Only SQL Server on Azure Virtual Machines and Azure SQL Managed Instance support this feature natively.
Azure SQL Database single database and elastic pools do not support SQL Server Agent natively.
2
Identify the requirement for private IP address deployment within a VNet.
Both SQL Server on Azure Virtual Machines and Azure SQL Managed Instance are deployed inside an Azure Virtual Network.
Azure SQL Database single database and elastic pools are logical services hosted on public endpoints by default.

Key Concept

Selecting the appropriate Azure SQL relational database service based on feature compatibility and network isolation requirements.
Question 19Question

A company is planning to migrate a legacy on-premises electronic health record (EHR) application to Azure. The relational database for the application has the following requirements:
- Must support SQL Server Agent to run nightly maintenance jobs.
- Must support Database Mail to send automated notifications to administrators.
- Must be deployed into a private, delegated subnet within an Azure Virtual Network.
- In the event of a regional disaster, all database backups must remain available.
- The administrative overhead for managing operating system patching and hardware updates must be minimized.

Which Azure SQL deployment option should you recommend?

Show answer & explanation

Answer: Azure SQL Managed Instance configured with geo-redundant storage (GRS) backups.

Answer

Azure SQL Managed Instance configured with geo-redundant storage (GRS) backups
The option recommending Azure SQL Managed Instance with geo-redundant storage (GRS) backups is correct because it meets all requirements. Azure SQL Managed Instance is a fully managed PaaS service that supports instance-level features such as SQL Server Agent and Database Mail. It runs inside a delegated subnet within a virtual network. Using GRS backups ensures that backups survive a regional disaster while avoiding the administrative overhead of OS patching associated with virtual machines.

Step-by-Step Solution

1
Analyze instance-level requirements
SQL Server Agent and Database Mail are instance-level features, meaning that standard Azure SQL Database (single database or elastic pools) cannot meet these requirements natively.
Azure SQL Database does not support instance-level features like SQL Server Agent or Database Mail.
2
Evaluate administrative overhead constraint
SQL Server on Azure VMs is ruled out because it requires manual OS and database engine patching, failing the constraint to minimize administration.
Choosing a PaaS service is necessary to offload OS and engine maintenance to Microsoft.
3
Determine the service tier
Azure SQL Managed Instance is selected because it is a PaaS service that supports SQL Server Agent, Database Mail, and virtual network integration.
Managed Instance provides near 100% compatibility with the SQL Server database engine along with PaaS benefits.
4
Select backup storage redundancy
Geo-redundant storage (GRS) must be chosen for backups rather than locally redundant storage (LRS).
Only GRS replicates backups to a secondary paired region to survive a primary regional disaster.

Key Concept

Azure SQL service comparison based on legacy feature support, network requirements, and management overhead
Question 20Question

An organization is planning to migrate an on-premises payroll application to Azure. The application database relies on SQL Server Agent for scheduled data reconciliation and executes cross-database queries. The database must be deployed in a secure environment with native Azure Virtual Network (VNet) integration. To meet disaster recovery requirements, all backups must survive a regional outage, and the database administration team must minimize administrative effort for operating system and database engine patching. Which Azure SQL deployment option should you recommend?

Show answer & explanation

Answer: Azure SQL Managed Instance

Answer

Azure SQL Managed Instance
Azure SQL Managed Instance is the correct recommendation because it provides near-100% compatibility with the on-premises SQL Server database engine, including native support for SQL Server Agent and cross-database queries. As a fully managed Platform as a Service (PaaS), it handles operating system and database engine patching automatically, integrates natively with an Azure Virtual Network, and supports geo-redundant backup storage to ensure backups survive a regional outage.

Step-by-Step Solution

1
Analyze the technical and administrative requirements of the database migration scenario.
Requirements identified: SQL Server Agent support, cross-database query support, native VNet integration, regional backup resiliency (survive regional outage), and minimal administrative overhead (PaaS model).
Understanding constraints is necessary to filter out non-compliant Azure database services.
2
Evaluate the management overhead (IaaS vs. PaaS) requirement.
SQL Server on Azure Virtual Machines is eliminated because it is an IaaS solution requiring the administration team to manage operating system and database patching.
The organization specified a need to minimize administrative patching efforts.
3
Compare PaaS options against legacy database feature and backup requirements.
Azure SQL Database (both single database and elastic pool configurations) is eliminated because it lacks native support for SQL Server Agent and cross-database queries. Additionally, choosing locally redundant storage (LRS) fails the requirement for regional resilience.
Selecting a service tier that lacks native support for required legacy features would lead to deployment failure or complex, unmanageable workarounds.

Key Concept

Selecting the appropriate Azure SQL deployment option based on legacy feature support, network requirements, and administrative overhead.
Page 1 / 16Next
Design Data Storage Solutions Practice Questions — Microsoft Azure Solutions Architect (AZ-305) | Examkin