Knowledge + Practice

CCNA Data Storage Solutions Questions

75 of 233 questions · Page 2/4 · Data Storage Solutions topic · Answers revealed

Practice these questions Exam hub All questions

76

MCQeasy

A company wants to automatically tier data between hot, cool, and archive access tiers based on last access time to optimize costs. Which Azure feature should they implement?

A.Azure Blob Storage lifecycle management

B.Azure Data Box

C.Azure Backup

D.Azure File Sync

AnswerA

Lifecycle management automatically tiers data based on rules.

Why this answer

Azure Blob Storage lifecycle management allows you to define policies that automatically move blobs between hot, cool, and archive access tiers based on conditions such as last access time or age. This directly addresses the requirement to optimize costs by tiering data according to access patterns without manual intervention.

Exam trap

The trap here is that candidates may confuse Azure File Sync's 'cloud tiering' feature with blob lifecycle management, but File Sync only tiers between local server and Azure Files (not between hot/cool/archive tiers) and does not use last access time for tiering decisions.

How to eliminate wrong answers

Option B (Azure Data Box) is wrong because it is a physical data transfer service for offline migration of large datasets, not a tool for automated tiering based on access time. Option C (Azure Backup) is wrong because it provides backup and restore capabilities for Azure resources, not data lifecycle management between access tiers. Option D (Azure File Sync) is wrong because it synchronizes on-premises file servers with Azure file shares and can enable cloud tiering, but it does not support moving data between hot, cool, and archive tiers based on last access time; its tiering is limited to local vs. cloud caching.

Practice this question →

77

MCQmedium

A healthcare company is designing a data storage solution for its electronic health records (EHR) system. The system must store patient data in Azure SQL Database with high availability. The solution must meet the following requirements: - Data must be stored in the East US region with automatic failover to a secondary region in West US in case of a regional outage. - The Recovery Point Objective (RPO) must be less than 5 seconds. - The Recovery Time Objective (RTO) must be less than 1 hour. - The solution must minimize costs while meeting the RPO and RTO. Which Azure SQL Database configuration should the company recommend?

A.Deploy Azure SQL Database Managed Instance with failover group to a secondary instance in West US.

B.Deploy Azure SQL Database with active geo-replication to a secondary server in West US. Configure automatic failover using a failover group.

C.Deploy Azure SQL Database Business Critical tier with auto-failover group and a secondary replica in a different availability zone within East US.

D.Deploy Azure SQL Database General Purpose tier with zone-redundant configuration.

AnswerB

Active geo-replication provides low RPO and RTO across regions.

Why this answer

Option A is correct because Azure SQL Database active geo-replication with a secondary in West US meets the RPO of 5 seconds (typically 5-10 seconds) and RTO of 1 hour (failover time is usually < 30 minutes). Option B is wrong because auto-failover groups use the same replication but require a secondary in the same region for premium tiers. Option C is wrong because zone-redundant configuration provides high availability within a region, not across regions.

Option D is wrong because Azure SQL Database Managed Instance does not support active geo-replication with sub-5-second RPO.

Practice this question →

78

MCQmedium

A company ingests IoT sensor data into Azure Blob Storage. Data is written frequently and is accessed rarely after the first 24 hours. The company must retain the data for exactly 90 days for compliance. They want to minimize storage costs by automatically moving data to the cheapest possible storage tier as soon as possible. Which Azure Blob Storage lifecycle management policy should they implement?

A.Move to Cool tier after 1 day, delete after 90 days

B.Move to Archive tier after 1 day, delete after 90 days

C.Move to Cool tier after 30 days, delete after 90 days

D.Move to Archive tier after 30 days, delete after 90 days

AnswerA

Cool tier is the most cost-effective for data accessed rarely. Moving after 1 day minimizes storage cost early. Deleting after exactly 90 days meets compliance without early deletion penalties.

Why this answer

Option A is correct because the data is rarely accessed after 24 hours, so moving it to Cool tier after 1 day minimizes cost while still allowing low-latency access. The 90-day deletion aligns with the compliance retention requirement. Cool tier is the cheapest online tier, and moving data there as soon as possible (after 1 day) reduces costs without incurring the early deletion penalty or retrieval latency of Archive tier.

Exam trap

The trap here is that candidates often choose Archive tier thinking it is the cheapest, but they overlook the 180-day early deletion penalty and the fact that Cool tier is sufficient for 90-day retention with no penalty, making it the true cheapest option for this exact retention window.

How to eliminate wrong answers

Option B is wrong because moving data to Archive tier after 1 day would make it inaccessible for immediate use (Archive has a retrieval latency of up to 15 hours) and incurs a higher cost for early deletion if deleted before 180 days. Option C is wrong because waiting 30 days to move to Cool tier leaves data in the Hot tier for 29 extra days, incurring unnecessary storage costs when it could have been moved after 1 day. Option D is wrong because moving to Archive tier after 30 days still incurs the early deletion penalty (Archive requires a minimum 180-day retention) and the data is rarely accessed, but Cool tier after 1 day is cheaper and more appropriate.

Practice this question →

79

MCQmedium

Refer to the exhibit. You are reviewing the configuration of an Azure Blob Storage container used for storing financial audit records. The exhibit shows the container's immutability policy and legal hold settings. You need to ensure that the audit records cannot be deleted or modified for at least 7 years. What should you do?

A.Delete the container, create a new container, and set the immutability policy to 2555 days before locking.

B.Increase the immutability period to 2555 days by updating the policy.

C.Modify the immutability period to 2555 days.

D.Add additional legal hold tags for each year.

AnswerA

Only way to achieve 7-year retention with locked policy.

Why this answer

Option B is correct because the immutability policy is locked at 365 days (1 year) and cannot be increased after locking; you must delete the container, create a new one, and set the immutability period to 2555 days (7 years) before locking. Option A is wrong because you cannot modify a locked policy. Option C is wrong because legal hold does not enforce a time-based retention.

Option D is wrong because you cannot add more time to a locked policy.

Practice this question →

80

MCQeasy

A financial company must store customer transaction records in Azure Blob Storage. Regulatory requirements mandate that the records must not be modified or deleted for 7 years. Even administrators must be unable to alter or remove the blobs during this period. Which Azure Blob Storage feature should they enable?

A.Immutable storage with time-based retention policy

B.Legal hold

C.Soft delete

D.Versioning

AnswerA

Correct. A time-based retention policy enforces WORM for a fixed period, satisfying the 7-year regulatory requirement.

Why this answer

Immutable storage with a time-based retention policy (WORM – Write Once, Read Many) ensures that blobs cannot be modified or deleted for a specified duration, even by administrators. This directly satisfies the 7-year regulatory requirement by locking the data at the storage level, overriding any delete or write operations.

Exam trap

The trap here is that candidates often confuse soft delete or versioning with immutable storage, not realizing that only WORM policies (time-based retention or legal hold) provide true, administrator-proof immutability for a defined period.

How to eliminate wrong answers

Option B (Legal hold) is wrong because legal hold is an indefinite, policy-based lock that must be explicitly cleared; it does not enforce a fixed 7-year retention period and is typically used for litigation, not time-bound regulatory compliance. Option C (Soft delete) is wrong because soft delete only protects against accidental deletion by retaining deleted blobs for a configurable period, but it does not prevent modification or deletion by administrators during the retention window. Option D (Versioning) is wrong because versioning preserves previous blob versions but does not prevent deletion or overwrite of the current version; administrators can still delete or modify blobs, and versioning alone does not enforce a write-once, read-many constraint.

Practice this question →

81

MCQmedium

Refer to the exhibit. An Azure Policy is assigned to a subscription. A user tries to create a blob container via the Azure portal and receives a deny error. What is the most likely reason?

A.The policy denies creation of blob containers

B.The blob container requires immutable storage

C.The user is trying to enable public access on the container

D.The storage account does not have encryption enabled

AnswerA

The policy explicitly denies the write action for containers when the request is a PUT (create).

Why this answer

Option A is correct because the policy denies the 'Microsoft.Storage/storageAccounts/blobServices/containers/write' action when the request action is 'Microsoft.Storage/storageAccounts/blobServices/containers/put', which is the create container operation. Option B is wrong because the policy does not check encryption. Option C is wrong because the policy does not check public access.

Option D is wrong because the policy does not check blob immutability.

Practice this question →

82

MCQmedium

A global company stores customer profile data in JSON format. The application requires low-latency writes and reads from multiple regions. The solution must support multi-region writes with automatic conflict resolution and provide high availability. Which Azure Cosmos DB configuration should they choose?

A.SQL API with eventual consistency and multi-region writes enabled

B.MongoDB API with strong consistency and multi-region writes enabled

C.Table API with consistent prefix consistency and single-region writes

D.Gremlin API with session consistency and multi-region writes enabled

AnswerA

SQL API handles JSON, eventual consistency supports multi-region writes, and conflict resolution is automatic.

Why this answer

The scenario demands low-latency multi-region writes with automatic conflict resolution and high availability. Azure Cosmos DB's SQL API supports multi-region writes with eventual consistency, which is the only consistency level that allows multi-region writes. Eventual consistency provides the lowest latency and highest availability, and Cosmos DB's automatic conflict resolution handles concurrent writes across regions using last-writer-wins (LWW) or custom conflict resolution policies.

Exam trap

The trap here is that candidates often assume strong consistency is required for data integrity, but Azure Cosmos DB enforces that multi-region writes only work with eventual consistency, and automatic conflict resolution handles the trade-off between consistency and availability.

How to eliminate wrong answers

Option B is wrong because strong consistency cannot be used with multi-region writes; Cosmos DB restricts multi-region writes to eventual consistency only, as strong consistency would require synchronous replication across regions, defeating low-latency writes. Option C is wrong because single-region writes do not meet the requirement for multi-region writes, and consistent prefix consistency is not the recommended choice for multi-region write scenarios. Option D is wrong because Gremlin API (graph) is not optimized for JSON document storage and multi-region writes with session consistency do not provide automatic conflict resolution; session consistency is scoped to a single client session and does not handle cross-region conflicts.

Practice this question →

83

MCQhard

A company needs to store and analyze petabytes of semi-structured data from IoT devices. The data is append-only and written in time order. They need to support fast queries on time ranges and also aggregate data in real-time. Which Azure data service should they use?

A.Azure Data Explorer

B.Azure Cosmos DB

C.Azure SQL Database

D.Azure Table Storage

AnswerA

ADX (Kusto) is built for real-time analysis on large volumes of streaming data. It supports efficient time-series queries, ingestion from IoT sources, and real-time aggregations.

Why this answer

Azure Data Explorer (ADX) is purpose-built for high-performance analysis of large volumes of time-series and semi-structured data. It supports append-only ingestion, optimized time-range queries via its columnar storage and indexing, and real-time aggregation using Kusto Query Language (KQL) with built-in materialized views and update policies.

Exam trap

The trap here is that candidates often confuse Azure Data Explorer with Azure Cosmos DB because both handle semi-structured data, but Cosmos DB is optimized for transactional workloads with point reads and writes, not for petabyte-scale analytical time-series queries.

How to eliminate wrong answers

Option B (Azure Cosmos DB) is wrong because it is a globally distributed, multi-model NoSQL database optimized for low-latency transactional workloads, not for petabyte-scale analytical queries on append-only time-series data; its indexing and query patterns are not designed for high-throughput time-range scans. Option C (Azure SQL Database) is wrong because it is a relational OLTP database that struggles with petabyte-scale semi-structured data and append-only ingestion rates, and its indexing and query engine are not optimized for time-series analytics. Option D (Azure Table Storage) is wrong because it is a key-value store with limited query capabilities (only on partition and row keys), no native support for time-range aggregations, and poor performance for real-time analytics on large datasets.

Practice this question →

84

MCQeasy

Refer to the exhibit. You deploy this Bicep template. Which region is the primary write region?

A.West US

B.The resource group's location

C.East US

D.Both regions are primary

AnswerC

East US has failoverPriority 0, making it the primary write region.

Why this answer

Option A is correct because the location with failoverPriority 0 is the primary write region. Option B is wrong because failoverPriority 1 is secondary. Option C is wrong because the template does not specify a primary region explicitly; the priority determines it.

Option D is wrong because the location is set to the resource group's location, but the primary write region is defined by failoverPriority.

Practice this question →

85

MCQmedium

Your company runs a critical database on Azure SQL Managed Instance. You need to ensure zero data loss and automatic failover to a secondary region in the event of a regional outage. What should you configure?

A.Auto-failover groups for the Azure SQL Managed Instance

B.A single Azure SQL Managed Instance with zone-redundant configuration

C.Active geo-replication for the database

D.Failover groups with manual failover policy and automatic data synchronization

AnswerD

Failover groups provide automatic failover when configured correctly.

Why this answer

Option D is correct because it describes a failover group configured with manual failover policy and automatic data synchronization, which ensures zero data loss by synchronously replicating data to the secondary region and allows you to control when failover occurs, meeting the requirement for automatic failover in a regional outage scenario. For Azure SQL Managed Instance, failover groups with manual failover policy are the only way to achieve zero data loss (RPO=0) across regions, as automatic failover policy would allow asynchronous replication and potential data loss.

Exam trap

The trap here is that candidates confuse active geo-replication (available for Azure SQL Database) with failover groups for Azure SQL Managed Instance, or assume that auto-failover groups guarantee zero data loss when they actually use asynchronous replication by default.

How to eliminate wrong answers

Option A is wrong because auto-failover groups for Azure SQL Managed Instance use asynchronous replication by default, which cannot guarantee zero data loss (RPO > 0) during a regional outage. Option B is wrong because zone-redundant configuration protects against failures within a single region (availability zone failures), not against a complete regional outage, and it does not provide cross-region disaster recovery. Option C is wrong because active geo-replication is not supported for Azure SQL Managed Instance; it is a feature for Azure SQL Database (single database or elastic pool), not for managed instances.

Practice this question →

86

MCQmedium

A software company hosts multiple small databases for different clients on Azure SQL Database. Each database has low average usage but experiences unpredictable spikes. The company wants to minimize cost by pooling resources across databases while allowing each database to consume resources up to a set limit during spikes. They also need the ability to easily add new databases without manual sizing. Which Azure SQL Database deployment option should they choose?

A.Azure SQL Database elastic pool

B.Azure SQL Database single database with reserved capacity

C.Azure SQL Managed Instance

D.SQL Server on Azure Virtual Machines

AnswerA

Elastic pools allow databases to share resources from a common pool, reducing cost for databases with low average usage and high, unpredictable spikes. They also simplify adding new databases.

Why this answer

Azure SQL Database elastic pool is the correct choice because it allows multiple databases to share a fixed pool of resources (eDTUs or vCores), which minimizes cost by pooling resources across databases with low average usage and unpredictable spikes. Each database can automatically burst up to a configurable per-database resource limit (e.g., max eDTU per database) during spikes, and new databases can be added to the pool without manual sizing, as they simply consume from the shared pool.

Exam trap

The trap here is that candidates may choose single database with reserved capacity (Option B) thinking it offers cost savings, but they overlook that reserved capacity applies to a single database and does not provide resource pooling or automatic bursting across multiple databases, making it more expensive for the described workload.

How to eliminate wrong answers

Option B is wrong because Azure SQL Database single database with reserved capacity reserves compute resources for a single database, which does not pool resources across multiple databases and would be cost-inefficient for low-average-usage databases with spikes. Option C is wrong because Azure SQL Managed Instance is a fully managed instance of SQL Server with fixed resource limits per instance, not designed for pooling resources across many small databases with unpredictable spikes, and it requires manual sizing for each new database. Option D is wrong because SQL Server on Azure Virtual Machines requires manual management of VM resources, does not provide built-in resource pooling or automatic bursting across databases, and incurs higher operational overhead and cost for many small databases.

Practice this question →

87

MCQmedium

A company runs a data analytics workload that processes large amounts of unstructured data (images and videos). The data is accessed frequently for the first month, then rarely. They need to store the data cost-effectively for 7 years to meet compliance. The solution must support fast retrieval of data within the first month. Which Azure storage solution should they recommend?

A.Azure Blob Storage with hot tier for 30 days, then lifecycle management to cool tier for 6 months, then archive tier

B.Azure Blob Storage with premium tier for 30 days, then lifecycle to archive tier

C.Azure Files with lifecycle management

D.Azure Disk Storage with snapshots

AnswerA

Hot tier offers fast access for the first month; lifecycle management moves data to cool/archive to reduce cost.

Why this answer

Azure Blob Storage with hot tier for the first 30 days meets the fast retrieval requirement for frequently accessed data, while lifecycle management automatically moves data to cool tier for 6 months and then to archive tier for the remaining 7-year compliance period, minimizing cost. The archive tier offers the lowest storage cost for rarely accessed data, and lifecycle policies ensure seamless transitions without manual intervention.

Exam trap

The trap here is that candidates often confuse 'premium' with 'fast retrieval' and overlook that the hot tier already provides low-latency access for frequently used data, while premium is overkill and cost-prohibitive for this workload.

How to eliminate wrong answers

Option B is wrong because the premium tier is designed for low-latency, high-transaction workloads (e.g., IoT, interactive apps) and is unnecessarily expensive for this scenario; it also lacks a cool tier transition, leading to higher costs before archiving. Option C is wrong because Azure Files is a fully managed file share for SMB/NFS protocols, not optimized for large-scale unstructured data like images and videos, and its lifecycle management is limited compared to Blob Storage tiers. Option D is wrong because Azure Disk Storage provides block-level storage for VMs, not cost-effective long-term archival for unstructured data, and snapshots are incremental backups, not a tiered storage solution for compliance.

Practice this question →

88

MCQmedium

A company is building a global real-time collaboration platform. The application data is stored as JSON documents and needs to be available for low-latency reads and writes from multiple geographic regions. The application must support multi-region writes so that users can update data from any region with automatic conflict resolution. The company wants a fully managed database service with a guaranteed SLA for availability and throughput. Which Azure data service should they choose?

A.Azure Cosmos DB with SQL API and multiple write regions

B.Azure SQL Database with active geo-replication

C.Azure Table Storage

D.Azure Cache for Redis

AnswerA

Cosmos DB supports multi-region writes, automatic conflict resolution, global distribution, low latency, and 99.999% availability. It is ideal for globally distributed real-time applications.

Why this answer

Azure Cosmos DB with SQL API and multiple write regions is the correct choice because it is a fully managed, globally distributed NoSQL database that natively supports multi-region writes with automatic conflict resolution. It provides low-latency reads and writes from any region, a guaranteed SLA for availability (99.999% for multi-region writes) and throughput, and is optimized for JSON document storage, making it ideal for a real-time collaboration platform.

Exam trap

The trap here is that candidates often confuse active geo-replication in Azure SQL Database (which supports only single-region writes) with true multi-region write support, leading them to choose Option B despite its read-only secondary regions.

How to eliminate wrong answers

Option B is wrong because Azure SQL Database with active geo-replication supports only a single writable primary region; secondary regions are read-only, which does not meet the requirement for multi-region writes. Option C is wrong because Azure Table Storage is a key-value store that does not support multi-region writes with automatic conflict resolution and lacks a guaranteed throughput SLA. Option D is wrong because Azure Cache for Redis is an in-memory cache, not a fully managed database service; it does not provide durable storage or native multi-region write capabilities with conflict resolution.

Practice this question →

89

MCQmedium

Your company is migrating on-premises Oracle databases to Azure. The new solution must support a minimum of 99.99% availability SLA and allow for schema changes with minimal downtime. What should you recommend?

A.Azure SQL Managed Instance Business Critical tier

B.Azure Cosmos DB for PostgreSQL

C.Azure SQL Database Business Critical tier with zone redundancy

D.Azure Virtual Machines running Oracle Database with Availability Zones

AnswerC

Business Critical tier offers high availability and zone redundancy, meeting 99.99% SLA.

Why this answer

Azure SQL Database Business Critical tier with zone redundancy provides a 99.995% SLA, exceeding the 99.99% requirement, and supports online schema changes with minimal downtime via features like online index operations and schema modification with minimal blocking. Zone redundancy replicates data across three Azure Availability Zones within a region, ensuring high availability and automatic failover without data loss.

Exam trap

The trap here is that candidates often assume Azure SQL Managed Instance is equivalent to Azure SQL Database for high availability, but Managed Instance lacks zone redundancy, making it unable to meet the 99.99% SLA in a multi-zone failure scenario.

How to eliminate wrong answers

Option A is wrong because Azure SQL Managed Instance Business Critical tier offers a 99.99% SLA but does not support zone redundancy, limiting its availability to a single zone and potentially causing downtime during a zonal failure. Option B is wrong because Azure Cosmos DB for PostgreSQL is a distributed database optimized for horizontally scalable workloads and does not natively support schema changes with minimal downtime; schema changes often require table locks or downtime. Option D is wrong because Azure Virtual Machines running Oracle Database with Availability Zones can achieve high availability but requires manual configuration for patching, failover, and schema changes, leading to more downtime compared to a managed service like Azure SQL Database.

Practice this question →

90

MCQmedium

A company ingests millions of IoT sensor data points per second. They need a fully managed analytics service optimized for time-series data that can ingest high-velocity data, perform real-time analytics, and store data for historical analysis. The solution must integrate with Azure Stream Analytics for stream processing. Which Azure data service should they choose?

A.Azure Cosmos DB

B.Azure SQL Database

C.Azure Data Explorer (ADX)

D.Azure Blob Storage

AnswerC

ADX is purpose-built for large-scale time-series data, providing rapid data ingestion, real-time analytics, and seamless integration with Azure Stream Analytics.

Why this answer

Azure Data Explorer (ADX) is the correct choice because it is a fully managed, high-performance analytics service optimized for time-series and log data. It can ingest millions of IoT sensor data points per second, perform real-time analytics with sub-second query latency, and store data for historical analysis. ADX natively integrates with Azure Stream Analytics for stream processing, making it ideal for this scenario.

Exam trap

The trap here is that candidates often confuse Azure Data Explorer with Azure Cosmos DB or Azure SQL Database because they all support time-series data, but only ADX is purpose-built for high-velocity ingestion and real-time analytics with native Stream Analytics integration.

How to eliminate wrong answers

Option A is wrong because Azure Cosmos DB is a NoSQL database designed for transactional workloads with multi-model support, not optimized for high-velocity time-series analytics or native integration with Azure Stream Analytics. Option B is wrong because Azure SQL Database is a relational database for OLTP workloads, lacking the columnar storage, ingestion pipeline, and query engine optimized for time-series data at millions of events per second. Option D is wrong because Azure Blob Storage is an object storage service for unstructured data, not an analytics engine; it cannot perform real-time analytics or directly integrate with Azure Stream Analytics for stream processing.

Practice this question →

91

Multi-Selectmedium

Which TWO of the following are benefits of using Azure Cosmos DB for a globally distributed application?

Select 2 answers

A.Support for foreign key constraints across containers

B.Multiple consistency models to choose from

C.Built-in support for transactional replication

D.Native support for SQL Server stored procedures

E.Automatic indexing of all data

AnswersB, E

Cosmos DB offers five consistency levels.

Why this answer

Azure Cosmos DB offers multiple well-defined consistency models (strong, bounded staleness, session, consistent prefix, and eventual) that allow developers to balance consistency, availability, and latency according to application needs. This is a key benefit for globally distributed applications because it enables tuning data guarantees across regions without sacrificing performance.

Exam trap

The trap here is that candidates confuse Cosmos DB's JavaScript-based stored procedures with SQL Server stored procedures, or assume that a globally distributed NoSQL database would support foreign keys or transactional replication like a traditional relational database.

Practice this question →

92

Multi-Selectmedium

Which TWO of the following are benefits of using Azure Cosmos DB for a globally distributed application?

Select 2 answers

A.Multiple well-defined consistency levels

B.Full support for SQL Server features like stored procedures

C.Turnkey global distribution across multiple Azure regions

D.Automatic failover to a secondary region without manual intervention

E.Support for only the SQL API

AnswersA, C

Cosmos DB offers five consistency levels.

Why this answer

Azure Cosmos DB offers multiple well-defined consistency levels (Strong, Bounded Staleness, Session, Consistent Prefix, Eventual) that allow developers to balance data consistency, availability, and latency according to application requirements. This flexibility is a key benefit for globally distributed applications because different operations may tolerate different levels of staleness while still meeting SLAs.

Exam trap

The trap here is that candidates often confuse 'automatic failover' with 'no manual intervention required'—Azure Cosmos DB requires explicit configuration (enabling automatic failover and setting region priorities) for it to occur automatically, and even then, failover is not instantaneous and may involve a brief period of unavailability.

Practice this question →

93

Multi-Selecteasy

Which TWO of the following are features of Azure SQL Database that help ensure high availability? (Select two.)

Select 2 answers

A.Active geo-replication

B.Long-term retention (LTR) backups

C.Automatic tuning

D.Zone-redundant availability

E.Transparent Data Encryption (TDE)

AnswersA, D

Replicates data to a secondary region for disaster recovery.

Why this answer

Active geo-replication (Option A) creates readable secondary replicas of an Azure SQL Database in a paired Azure region, enabling manual or automatic failover to maintain availability during a regional outage. This feature ensures high availability by providing disaster recovery capabilities with a Recovery Point Objective (RPO) of up to 5 seconds and a Recovery Time Objective (RTO) of less than 1 hour, depending on the failover group configuration.

Exam trap

The trap here is that candidates often confuse backup features (like LTR) or security features (like TDE) with high availability mechanisms, but only replication-based solutions (geo-replication and zone-redundancy) directly address availability during failures.

Practice this question →

94

MCQhard

A company stores terabytes of archival data that must be retained for 10 years per regulatory requirements. The data is accessed infrequently (once or twice per year) and retrieval latency of up to 5 hours is acceptable. The company wants the lowest storage cost. They also need to ensure data is encrypted at rest and immutability to prevent deletion or modification during the retention period. Which Azure storage solution should they choose?

A.Azure Blob Storage with Hot tier and lifecycle management to Archive tier with WORM policy

B.Azure Blob Storage with Cool tier and lifecycle management to Archive tier with legal hold

C.Azure Blob Storage with Archive tier and immutability policy (time-based retention)

D.Azure Files with premium tier and soft delete

AnswerC

Archive tier offers the lowest cost, and immutability policy ensures data cannot be deleted or modified during the 10-year retention.

Why this answer

Option C is correct because Azure Blob Storage's Archive tier offers the lowest storage cost for infrequently accessed data, and the immutability policy with time-based retention provides WORM (Write Once, Read Many) compliance to prevent deletion or modification for the required 10-year period. The 5-hour retrieval latency is acceptable for archival data accessed once or twice per year, and encryption at rest is automatically enabled for all Azure Blob Storage tiers.

Exam trap

The trap here is that candidates often confuse legal hold (which is indefinite and does not prevent modification) with time-based retention immutability policy, or they incorrectly choose a higher-cost tier like Hot or Cool thinking lifecycle management will reduce costs, ignoring that the Archive tier itself is the cheapest and directly meets the latency requirement.

How to eliminate wrong answers

Option A is wrong because the Hot tier is the most expensive storage tier and is unnecessary for archival data accessed once or twice per year; lifecycle management to Archive tier adds complexity but the Hot tier cost is wasted. Option B is wrong because legal hold is an indefinite retention mechanism that cannot enforce a specific 10-year retention period, and it does not prevent modification of blobs (only deletion); the Cool tier is also more expensive than Archive. Option D is wrong because Azure Files with premium tier is designed for low-latency file shares and is extremely costly for terabytes of archival data, and soft delete does not provide immutability or prevent modification.

Practice this question →

95

MCQeasy

A startup needs a cost-effective data storage solution for its application logs. The logs are accessed infrequently but must be available for audit purposes for up to 3 years. The solution should minimize storage costs while allowing data retrieval within 24 hours when needed. Which Azure storage tier should the company recommend?

A.Azure Blob Storage Cool tier

B.Azure Blob Storage Hot tier

C.Azure Blob Storage Archive tier

D.Azure Blob Storage Premium tier

AnswerC

Lowest cost for rarely accessed data with retrieval time in hours.

Why this answer

The Archive tier is the most cost-effective option for data that is infrequently accessed and requires retrieval times of up to 15 hours (standard) or 24 hours (high-priority). Since the logs must be available within 24 hours and stored for up to 3 years, Archive meets both the cost and retrieval requirements, as it offers the lowest storage cost among Azure Blob Storage tiers.

Exam trap

The trap here is that candidates often confuse the Archive tier's retrieval time with the Hot or Cool tiers, assuming Archive is too slow for any audit requirement, but the 24-hour SLA for high-priority rehydration makes it suitable for this scenario.

How to eliminate wrong answers

Option A is wrong because the Cool tier is designed for data accessed less than once per month, but its storage cost is higher than Archive, and it offers near-instant retrieval, which is unnecessary given the 24-hour retrieval window. Option B is wrong because the Hot tier is optimized for frequent access (multiple times per month) and has the highest storage cost, making it unsuitable for infrequently accessed audit logs. Option D is wrong because the Premium tier is intended for low-latency, high-transaction workloads (e.g., IoT, real-time analytics) and incurs the highest cost, which is not justified for archival audit logs.

Practice this question →

96

MCQmedium

A healthcare organization stores patient records in Azure SQL Database. They need to ensure that all read queries against the database are directed to a read-only replica to offload the primary. Which feature should you configure?

A.Elastic database queries

B.Failover groups

C.Read scale-out

D.Active geo-replication

AnswerC

Read scale-out enables routing read-only queries to a readable secondary replica.

Why this answer

Read scale-out in Azure SQL Database allows you to direct read-only queries to a read-only replica, offloading the primary database. By setting the `ApplicationIntent=ReadOnly` connection string parameter, queries are automatically routed to the secondary replica, which is ideal for read-heavy workloads like patient record queries.

Exam trap

The trap here is that candidates confuse Active geo-replication (which also provides readable secondaries) with Read scale-out, but Active geo-replication requires explicit connection string changes per replica, whereas Read scale-out automatically routes read-only queries via the same logical server endpoint.

How to eliminate wrong answers

Option A is wrong because Elastic database queries are used to run distributed queries across multiple databases, not to offload reads to a read-only replica. Option B is wrong because Failover groups provide high availability and geo-replication management, but they do not automatically route read queries to a read-only replica without additional configuration. Option D is wrong because Active geo-replication creates readable secondary replicas in different regions for disaster recovery, but it does not natively support automatic read-only query routing from the primary connection string; it requires manual connection string changes.

Practice this question →

97

Multi-Selecthard

Which THREE of the following are valid methods to securely transfer data to Azure Blob Storage? (Select three.)

Select 3 answers

A.Azure Data Box

B.Azure File Sync

C.AzCopy

D.Azure Migrate

E.Azure Import/Export service

AnswersA, C, E

Physical appliance for large data transfers to blob storage.

Why this answer

Azure Data Box is a physical data transfer solution that allows you to securely transfer large volumes of data to Azure Blob Storage when network transfer is impractical. It uses AES-256 encryption for data at rest and TLS for data in transit, and after the device is shipped back, data is automatically uploaded to your designated storage account.

Exam trap

The trap here is that candidates often confuse Azure File Sync with a general-purpose data transfer tool, but it is strictly for file shares (SMB) and cannot target Blob Storage, while Azure Migrate is mistaken for a data transfer service when it is actually a migration orchestration tool for servers and applications.

Practice this question →

98

MCQhard

You are designing a storage solution for a global e-commerce platform that must serve users from multiple regions with low latency. The data includes product catalog (read-heavy, rarely updated) and user session state (write-heavy, short-lived). Which combination of Azure services meets the requirements?

A.Azure Cosmos DB for session state and Azure Front Door with Azure CDN for catalog.

B.Azure Cache for Redis for session state and Azure Front Door for catalog.

C.Azure Table Storage for session state and Azure Front Door for catalog.

D.Azure SQL Database with geo-replication for both.

AnswerA

Cosmos DB multi-region writes for session state; Front Door + CDN for read-heavy catalog.

Why this answer

Option A is correct because Azure Cosmos DB provides multi-region writes for low-latency session state, and Azure Front Door with Azure CDN can cache static catalog data globally. Option B is wrong because Azure SQL Database with geo-replication is not ideal for session state due to cost and performance. Option C is wrong because Azure Table Storage does not support multi-region writes natively.

Option D is wrong because Azure Cache for Redis is not suitable as the primary persistent store for session state.

Practice this question →

99

MCQhard

A company uses Azure NetApp Files for high-performance file shares accessed by Linux VMs. They need to reduce latency for read-heavy workloads. Which configuration should you implement?

A.Migrate to Azure Files with Azure File Sync

B.Enable read-only cache on the volume

C.Disable the export policy to allow all clients

D.Mount the volume using SMB protocol

AnswerB

Read-only cache reduces latency for read-heavy workloads.

Why this answer

Azure NetApp Files supports a read-only cache option on volumes, which stores frequently accessed data in a high-speed cache (SSD-based) local to the compute resources. This reduces read latency for read-heavy workloads by serving data from the cache instead of the underlying storage tier. The cache is transparent to the Linux VMs and requires no application changes.

Exam trap

The trap here is that candidates may confuse Azure NetApp Files with Azure Files, assuming that Azure File Sync or SMB mounting can provide similar performance benefits, when in fact Azure NetApp Files uses NFS and its read-only cache is the specific feature designed for reducing read latency.

How to eliminate wrong answers

Option A is wrong because migrating to Azure Files with Azure File Sync does not provide the same low-latency, high-performance characteristics as Azure NetApp Files, and Azure File Sync is designed for hybrid caching, not for reducing latency within Azure. Option C is wrong because disabling the export policy to allow all clients removes all access controls and security, which is a security risk and does not reduce latency. Option D is wrong because mounting the volume using SMB protocol is not supported for Azure NetApp Files with Linux VMs (it uses NFS), and SMB would introduce additional protocol overhead and compatibility issues, increasing latency rather than reducing it.

Practice this question →

100

Drag & Dropmedium

Drag and drop the steps to implement Azure Traffic Manager for geographic routing into the correct order.

Drag steps to the numbered slots on the right, or tap a step then tap a slot.

Steps

Order

Why this order

Create profile, add endpoints, configure mapping, update DNS, test.

Practice this question →

101

MCQmedium

A media company needs to store large volumes of video files that are processed by an application. The files are accessed via REST APIs and are rarely accessed after the first few days. The company wants to minimize storage costs by automatically moving older files to a cheaper storage tier without any manual intervention. Which Azure storage solution should they use, and which feature should they configure?

A.Azure Blob Storage with lifecycle management policies

B.Azure Files with tiering

C.Azure NetApp Files with capacity pools

D.Azure Disk Storage with managed disks

AnswerA

Blob Storage provides REST API access and supports lifecycle management rules to automatically transition blobs from hot to cool to archive tiers, reducing costs as data ages.

Why this answer

Azure Blob Storage with lifecycle management policies is the correct solution because it allows you to define rules that automatically move blobs to cooler tiers (e.g., from Hot to Cool to Archive) based on age or last modification time, minimizing storage costs without manual intervention. The REST API access requirement is natively supported by Blob Storage via HTTPS, and the large video file workload fits well within its object storage capabilities.

Exam trap

The trap here is that candidates may confuse Azure Files tiering (which is for hybrid caching with Azure File Sync) with Blob Storage lifecycle management, or assume that any storage service with 'tiering' in its name provides automated cost-optimized tiering for REST-accessible data.

How to eliminate wrong answers

Option B is wrong because Azure Files uses the SMB protocol and does not support REST API access for video file processing; its tiering feature (Azure File Sync cloud tiering) is designed for on-premises caching, not automated cost-optimized tiering of rarely accessed files. Option C is wrong because Azure NetApp Files provides NFS/SMB volumes with capacity pools for high-performance workloads, but it lacks built-in automated lifecycle tiering to cheaper storage and is overkill for rarely accessed video files. Option D is wrong because Azure Disk Storage provides block-level managed disks for VMs, not REST API-accessible object storage, and has no lifecycle management feature to automatically move data to cheaper tiers.

Practice this question →

102

MCQhard

A company is building a petabyte-scale data lake for analytics. They need a storage solution that supports a hierarchical namespace, POSIX-like permissions (ACLs), and is optimized for big data analytics workloads using Apache Spark and Hive. The data must be accessible over the Azure Blob Storage API. Which Azure data service should they use?

A.Azure Blob Storage (with flat namespace)

B.Azure Data Lake Storage Gen2

C.Azure NetApp Files

D.Azure HPC Cache

AnswerB

ADLS Gen2 combines Blob Storage with a hierarchical namespace and ACLs, enabling Hadoop-compatible access and high-performance analytics with Spark, Hive, and other tools.

Why this answer

Azure Data Lake Storage Gen2 (ADLS Gen2) is the correct choice because it combines a hierarchical namespace with POSIX-like ACLs and is natively optimized for big data analytics workloads like Apache Spark and Hive. It exposes data through the Azure Blob Storage API, meeting all stated requirements for petabyte-scale analytics.

Exam trap

The trap here is that candidates often confuse Azure Blob Storage (which is object storage with a flat namespace) with ADLS Gen2, not realizing that the hierarchical namespace and POSIX ACLs are exclusive to ADLS Gen2 and critical for big data analytics engines like Spark and Hive.

How to eliminate wrong answers

Option A is wrong because Azure Blob Storage with a flat namespace lacks a hierarchical namespace and POSIX-like ACLs, making it unsuitable for Hive and Spark workloads that rely on directory structures and fine-grained permissions. Option C is wrong because Azure NetApp Files provides NFS/SMB access with POSIX permissions but does not support the Azure Blob Storage API, which is a stated requirement. Option D is wrong because Azure HPC Cache is a caching layer for high-performance computing, not a persistent data lake storage service, and it does not provide a hierarchical namespace or native Blob API access.

Practice this question →

103

MCQeasy

A small business is migrating its on-premises file server to Azure. The file server contains 2 TB of data that is accessed infrequently. The business wants to minimize costs and only pay for storage used. The solution must support SMB protocol and allow for on-premises caching to reduce latency. Which Azure storage solution should the business recommend?

A.Azure Files Standard tier with Azure File Sync

B.Azure Disk Storage Standard HDD with shared disks

C.Azure NetApp Files Standard tier with cross-region replication

D.Azure Blob Storage Cool tier with Azure Storage Explorer

AnswerA

SMB access and caching on-premises.

Why this answer

Option B is correct because Azure Files with Azure File Sync provides cloud storage with SMB access and on-premises caching via sync. Option A is wrong because Azure Blob Storage does not support SMB. Option C is wrong because Azure NetApp Files is more expensive.

Option D is wrong because Azure Disk Storage is not a file sharing solution.

Practice this question →

104

MCQmedium

A gaming company stores player session data in Azure Cosmos DB. They need to handle sudden spikes in write traffic without throttling and ensure low-latency reads globally. Which configuration should they use?

A.Autoscale provisioned throughput

B.Serverless capacity mode

C.Multi-region writes

D.Manual provisioned throughput

AnswerA

Autoscale automatically scales RU/s to handle spikes without throttling.

Why this answer

Autoscale provisioned throughput (A) is correct because it allows Cosmos DB to automatically scale up to the maximum throughput (up to 10x the base RU/s) during sudden write spikes, preventing throttling (HTTP 429 errors). Combined with multi-region writes (which is a separate configuration), it ensures low-latency global reads by enabling writes to be accepted in any region and replicated asynchronously. This meets both the spike-handling and global read latency requirements.

Exam trap

The trap here is confusing 'multi-region writes' (which handles global write availability) with 'autoscale' (which handles traffic spikes), leading candidates to pick C because they think global writes are needed for low-latency reads, when in fact reads can be served from any region without multi-region writes.

How to eliminate wrong answers

Option B (Serverless capacity mode) is wrong because it is designed for intermittent or low-traffic workloads and cannot handle sudden spikes in write traffic; it has a maximum throughput cap of 5,000 RU/s per container and no autoscale capability, leading to throttling under heavy load. Option C (Multi-region writes) is wrong because it addresses global write availability and conflict resolution, not the ability to handle sudden traffic spikes; it does not prevent throttling if the provisioned throughput is insufficient. Option D (Manual provisioned throughput) is wrong because it requires manual adjustment to handle spikes, which is not feasible for sudden, unpredictable traffic; it will throttle requests if the fixed RU/s limit is exceeded.

Practice this question →

105

MCQmedium

A company wants to migrate its on-premises file server to Azure. The application accesses files using the Server Message Block (SMB) protocol and requires identity-based access integrated with on-premises Active Directory Domain Services (AD DS). The solution must be fully managed and provide low latency for users within the same region. Which Azure solution should they choose?

A.Azure Files with Active Directory authentication and Azure File Sync.

B.Azure NetApp Files with SMB volumes.

C.Azure Blob Storage with NFS 3.0 support.

D.Azure Managed Disk with a file server VM.

AnswerA

Azure Files supports SMB protocol, can be domain-joined to on-premises AD DS for identity-based access, and is fully managed. Azure File Sync can optionally cache files on-premises but is not required for the migration.

Why this answer

Azure Files with Active Directory authentication and Azure File Sync is the correct choice because it provides a fully managed SMB file share that supports identity-based access using on-premises AD DS. Azure File Sync enables caching of frequently accessed files on-premises or in Azure, reducing latency for users in the same region while maintaining a single namespace. This solution meets all requirements: SMB protocol, identity-based access, fully managed service, and low latency.

Exam trap

The trap here is that candidates often choose Azure NetApp Files (Option B) because it supports SMB and AD DS, but they overlook that it is not fully managed and is more complex to deploy, whereas Azure Files with File Sync is the fully managed, lower-cost alternative that meets all stated requirements.

How to eliminate wrong answers

Option B is wrong because Azure NetApp Files is not fully managed; it requires provisioning and managing capacity pools and is more expensive, and while it supports SMB with AD DS, it is not the simplest fully managed solution for this scenario. Option C is wrong because Azure Blob Storage with NFS 3.0 does not support SMB protocol or identity-based access with AD DS; it uses NFS and requires Azure Active Directory Domain Services or other identity providers, not on-premises AD DS. Option D is wrong because Azure Managed Disk with a file server VM is not fully managed; it requires you to manage the VM, OS, and file server software, increasing operational overhead, and does not provide native SMB identity-based integration without additional configuration.

Practice this question →

106

MCQeasy

A company wants to store log data from multiple applications for up to 30 days for analysis. The data is append-only, and queries are infrequent but need to be fast when run. Which Azure data storage solution should you recommend?

A.Azure Log Analytics Workspace

B.Azure Table Storage

C.Azure Data Lake Storage Gen2

D.Azure Blob Storage (archive tier)

AnswerA

Log Analytics is built for log data, fast queries, and configurable retention.

Why this answer

Azure Log Analytics Workspace is the correct choice because it is purpose-built for ingesting, storing, and querying log data from multiple sources. It supports append-only log ingestion, retains data for up to 30 days in its interactive retention tier (configurable), and provides fast Kusto Query Language (KQL) queries for infrequent analysis. The workspace integrates natively with Azure Monitor and other services, making it ideal for centralized log analysis.

Exam trap

The trap here is that candidates often choose Azure Blob Storage (archive tier) for cost savings, overlooking the explicit requirement for fast query performance, which the archive tier cannot provide due to its multi-hour rehydration latency.

How to eliminate wrong answers

Option B is wrong because Azure Table Storage is a NoSQL key-value store designed for structured, transactional data, not for log analytics; it lacks native query capabilities for time-series log data and does not support fast, ad-hoc queries across multiple log sources. Option C is wrong because Azure Data Lake Storage Gen2 is optimized for big data analytics on large volumes of unstructured or semi-structured data, not for low-latency, infrequent queries on append-only logs; it is better suited for batch processing and data lakes. Option D is wrong because Azure Blob Storage (archive tier) is designed for long-term, cold storage with high retrieval latency (hours), not for fast queries on recent log data; it is cost-effective for archival but violates the requirement for fast query performance.

Practice this question →

107

Drag & Dropmedium

Drag and drop the steps to deploy a web app using Azure App Service with a custom domain and SSL certificate into the correct order.

Drag steps to the numbered slots on the right, or tap a step then tap a slot.

Steps

Order

Why this order

Create the app, map domain, upload cert, bind, then enforce HTTPS.

Practice this question →

108

MCQmedium

Refer to the exhibit. You attempt to create a new storage account with the property 'supportsHttpsTrafficOnly' set to false. What is the result?

A.The storage account is created and an audit log is generated.

B.The storage account creation is denied.

C.The storage account is created with HTTPS enforced automatically.

D.The storage account is created but encryption is disabled.

AnswerB

The policy denies creation when HTTPS is not enforced.

Why this answer

When you attempt to create a storage account with 'supportsHttpsTrafficOnly' set to false, Azure denies the creation because this property is deprecated and no longer accepted. As of late 2023, Azure Storage enforces HTTPS for all new storage accounts by default, and the property has been removed from the creation API. Setting it to false triggers a validation error, resulting in a denial of the creation request.

Exam trap

The trap here is that candidates assume the property still exists and can be set to false to disable HTTPS, but Azure has deprecated and removed it, causing the creation to be denied rather than silently ignoring the setting or allowing insecure traffic.

How to eliminate wrong answers

Option A is wrong because the creation is denied before any audit log is generated; the request fails validation at the Azure Resource Manager layer. Option C is wrong because the creation is denied entirely, so no storage account is created with any enforced setting. Option D is wrong because the creation is denied, and encryption settings are not evaluated or applied when the request is rejected.

Practice this question →

109

MCQeasy

A company needs to store immutable audit logs for regulatory compliance. The logs must be stored in a write-once, read-many (WORM) state for 7 years. Which Azure storage feature should be used?

A.Azure Blob Storage immutable storage with time-based retention

B.Azure SQL Database temporal tables

C.Azure Blob Storage change feed

D.Azure Blob Storage soft delete

AnswerA

Enforces WORM for a specified retention period.

Why this answer

Azure Blob Storage immutable storage with time-based retention enforces a WORM (Write Once, Read Many) state, preventing logs from being modified or deleted for a specified retention period. This directly meets the regulatory requirement to store audit logs immutably for 7 years, as the policy locks the data at the container or blob level and cannot be removed until the retention interval expires.

Exam trap

The trap here is that candidates confuse soft delete or change feed with immutable storage, not realizing that only immutable storage enforces a true WORM state that prevents both deletion and overwriting, which is required for regulatory compliance.

How to eliminate wrong answers

Option B is wrong because Azure SQL Database temporal tables track historical changes to data but do not enforce WORM immutability; data can still be physically deleted or altered by privileged users. Option C is wrong because Azure Blob Storage change feed provides a transaction log of blob changes for processing, not a mechanism to prevent modifications or deletions. Option D is wrong because Azure Blob Storage soft delete only offers recovery from accidental deletion within a retention window, but does not prevent overwrites or enforce a write-once state.

Practice this question →

110

MCQhard

A company is designing a data storage solution for an IoT pipeline that ingests time-series data from millions of devices. The data is append-only and queried by time range. The solution must support low-latency queries and automated retention policies. Which Azure data store should they choose?

A.Azure SQL Database

B.Azure Cosmos DB

C.Azure Data Explorer (ADX)

D.Azure Blob Storage with Azure Data Lake Storage Gen2

AnswerC

ADX is purpose-built for time-series and IoT data, with fast ingestion and querying.

Why this answer

Azure Data Explorer (ADX) is purpose-built for interactive analytics on large volumes of streaming, time-series data. It supports append-only ingestion, low-latency queries over time ranges via its Kusto Query Language (KQL), and native automated retention policies (e.g., soft-delete and hard-delete periods) without manual management.

Exam trap

The trap here is that candidates often confuse Cosmos DB's low-latency individual item access with the need for time-series range queries, overlooking that Cosmos DB lacks native time-series indexing and automated retention policies, while ADX is the only Azure service explicitly designed for high-throughput append-only time-series analytics with built-in lifecycle management.

How to eliminate wrong answers

Option A is wrong because Azure SQL Database is a relational OLTP store optimized for transactional workloads with frequent updates, not for high-throughput append-only time-series ingestion or time-range queries at scale. Option B is wrong because Azure Cosmos DB is a multi-model NoSQL database designed for globally distributed, low-latency reads/writes on individual items, but it lacks native time-series optimization, efficient range scans over massive append-only streams, and built-in automated retention policies for time-series data. Option D is wrong because Azure Blob Storage with Azure Data Lake Storage Gen2 provides cheap, scalable object storage for raw data but does not offer low-latency interactive querying or native time-series analytics; it requires additional compute engines (e.g., Azure Synapse) to query, adding latency and complexity.

Practice this question →

111

MCQhard

A company is designing a data lake for analytics. The data includes personally identifiable information (PII) that must be anonymized before analysts access it. Which Azure service should they use to automate the anonymization process?

A.Azure Policy

B.Azure SQL Database dynamic data masking

C.Azure Key Vault

D.Microsoft Purview data policies

AnswerD

Automates classification and masking for data lakes.

Why this answer

Microsoft Purview data policies allow you to define and enforce data access policies that can automatically anonymize or mask sensitive data, such as PII, when accessed by analysts. This service integrates with Azure data lake storage and provides a centralized way to manage data governance and compliance, making it the correct choice for automating anonymization in a data lake scenario.

Exam trap

The trap here is that candidates often confuse Azure SQL Database dynamic data masking (Option B) with a general-purpose anonymization solution, but it only works for relational databases, not for data lakes, and does not automate the process across heterogeneous file formats.

How to eliminate wrong answers

Option A is wrong because Azure Policy is used to enforce organizational standards and assess compliance across Azure resources, not to automate data-level anonymization or masking within a data lake. Option B is wrong because Azure SQL Database dynamic data masking applies masking at the database query level for SQL databases, but it is not designed for data lake storage (e.g., Azure Data Lake Storage Gen2) and does not automate anonymization for file-based analytics. Option C is wrong because Azure Key Vault is a service for securely storing and managing secrets, keys, and certificates, not for applying data anonymization or masking transformations.

Practice this question →

112

MCQeasy

A company plans to store operational logs from Azure App Services in a scalable and cost-effective way. The logs must be retained for 90 days and then automatically deleted. Which Azure data storage solution should you recommend?

A.Azure Blob Storage with lifecycle management

B.Azure SQL Database with retention policy

C.Azure Log Analytics Workspace

D.Azure Cosmos DB with TTL

AnswerC

Log Analytics Workspace is optimized for log data with retention policies and query capabilities.

Why this answer

Option B is correct because Azure Log Analytics Workspace is designed for storing and analyzing logs with built-in retention policies. Option A is wrong because Blob Storage is for unstructured data but lacks native log querying. Option C is wrong because Azure SQL Database is for relational data and less cost-effective for logs.

Option D is wrong because Cosmos DB is for NoSQL workloads and overpriced for logs.

Practice this question →

113

Multi-Selectmedium

Which TWO Azure services can be used to host a MongoDB-compatible database with global distribution? (Select two.)

Select 2 answers

A.Azure SQL Database

B.Azure Cosmos DB API for MongoDB

C.Azure Database for PostgreSQL

D.Azure Database for MongoDB (MongoDB Atlas on Azure)

E.Azure Cache for Redis

AnswersB, D

Cosmos DB API for MongoDB provides MongoDB compatibility with global distribution.

Why this answer

Azure Cosmos DB API for MongoDB is correct because it provides a MongoDB-compatible API layer over Cosmos DB's globally distributed, multi-model database engine. This allows you to use standard MongoDB drivers and tools while benefiting from Cosmos DB's turnkey global distribution, multi-region writes, and 99.999% availability SLA.

Exam trap

The trap here is that candidates may assume only one service can host a MongoDB-compatible database, overlooking that both a native MongoDB service (Atlas) and a protocol-compatible alternative (Cosmos DB API for MongoDB) are valid, and that Azure SQL Database or PostgreSQL are relational databases that cannot serve MongoDB workloads.

Practice this question →

114

MCQeasy

A company wants to store raw data from IoT devices, social media feeds, and transactional databases for analytics. They need a storage solution that supports a hierarchical namespace for organizing data into directories and allows fine-grained access control at the directory and file level. They also need to query the data using Azure Synapse Analytics in-place. Which Azure storage solution should they use?

A.A

B.B

C.C

D.D

AnswerB

Azure Data Lake Storage Gen2 provides a hierarchical namespace, ACL-based permissions, and seamless integration with Azure Synapse Analytics for in-place querying.

Why this answer

Azure Data Lake Storage Gen2 (ADLS Gen2) is the correct choice because it provides a hierarchical namespace that organizes data into directories and subdirectories, supports POSIX-like fine-grained access control at the directory and file level via ACLs, and can be queried in-place by Azure Synapse Analytics using its built-in serverless SQL pool or dedicated SQL pool. This combination of hierarchical namespace, granular security, and direct analytics integration makes it ideal for the described raw data storage and analytics scenario.

Exam trap

The trap here is that candidates often confuse Azure Blob Storage (flat namespace, no directory ACLs) with ADLS Gen2 (hierarchical namespace, full ACL support) because both are built on the same underlying storage platform, but only ADLS Gen2 enables the directory-level organization and fine-grained access control required for enterprise analytics workloads.

How to eliminate wrong answers

Option A is wrong because Azure Blob Storage does not natively support a hierarchical namespace or fine-grained directory/file-level ACLs; it uses a flat namespace and container-level access policies, which cannot meet the directory organization and granular access control requirements. Option C is wrong because Azure Files provides SMB file shares with directory structure and ACLs, but it is not designed for in-place querying by Azure Synapse Analytics and lacks the scale-out performance and analytics integration needed for big data workloads. Option D is wrong because Azure Cosmos DB is a NoSQL database optimized for transactional and real-time workloads with its own query API (SQL, MongoDB, etc.), not a storage solution for raw data with a hierarchical namespace, and it cannot be queried in-place by Azure Synapse Analytics as a storage layer.

Practice this question →

115

Multi-Selectmedium

Which TWO Azure services provide native support for Azure Active Directory (now Entra ID) authentication for accessing data? (Choose two.)

Select 2 answers

A.Azure Blob Storage.

B.Azure Files (SMB).

C.Azure SQL Database.

D.Azure Cache for Redis.

E.Azure Cosmos DB.

AnswersA, C

Supports Microsoft Entra ID authentication for blobs.

Why this answer

Options A and C are correct. Azure SQL Database supports Microsoft Entra ID authentication. Azure Storage supports Microsoft Entra ID authentication for blobs and queues.

Option B is wrong because Azure Cosmos DB uses keys or tokens, not native Entra ID. Option D is wrong because Azure Cache for Redis uses access keys. Option E is wrong because Azure Files supports Entra ID for SMB but not for REST; however, the question likely expects storage and SQL.

Azure Files does support Entra ID for SMB, so it could be considered, but it's less common. The best answers are SQL and Storage.

Practice this question →

116

MCQmedium

A healthcare analytics platform stores semi-structured JSON documents and requires globally distributed low-latency reads with tunable consistency. Which Azure data platform should be recommended?

A.Azure Cosmos DB

B.Azure Files premium shares

C.Azure Data Factory

D.Azure SQL Managed Instance

AnswerA

Cosmos DB provides globally distributed NoSQL APIs, tunable consistency, and low-latency reads.

Why this answer

Azure Cosmos DB is the correct choice because it natively supports semi-structured JSON documents, offers globally distributed multi-region writes and reads with low-latency (typically <10 ms at the 99th percentile), and provides tunable consistency levels (from strong to eventual) via its multi-master replication protocol. This directly matches the requirements for a healthcare analytics platform needing global distribution and flexible consistency.

Exam trap

The trap here is that candidates often confuse Azure SQL Managed Instance's JSON support (which can store JSON as text but lacks native document indexing and global distribution) with a true document database, or they mistakenly think Azure Files can serve as a document store because it supports file-based access, ignoring the need for queryable semi-structured data and tunable consistency.

How to eliminate wrong answers

Option B is wrong because Azure Files premium shares provide SMB/NFS file shares with low latency but are not designed for semi-structured JSON document storage or globally distributed low-latency reads with tunable consistency; they are a file-level service, not a document database. Option C is wrong because Azure Data Factory is a cloud-based ETL and data integration service, not a data store; it cannot serve low-latency reads or provide tunable consistency for stored documents. Option D is wrong because Azure SQL Managed Instance is a relational database engine (SQL Server) that stores data in a structured, tabular format, not semi-structured JSON documents natively, and its global distribution capabilities are limited to failover groups with eventual consistency, lacking the tunable consistency levels of Cosmos DB.

Practice this question →

117

MCQeasy

You need to design a data storage solution for a mobile app that requires low-latency reads and writes globally. The data is JSON documents with varying schemas. Which Azure service should you choose?

A.Azure Cache for Redis

B.Azure Cosmos DB

C.Azure SQL Database

D.Azure Table Storage

AnswerB

Cosmos DB is a globally distributed NoSQL database with native JSON support and low-latency.

Why this answer

Azure Cosmos DB is the correct choice because it provides native global distribution with multi-region writes and single-digit-millisecond latency at the 99th percentile, making it ideal for a mobile app requiring low-latency reads and writes worldwide. It natively supports JSON documents with varying schemas through its document model and offers multiple consistency levels to balance performance and data integrity.

Exam trap

The trap here is that candidates often choose Azure Cache for Redis because they associate 'low-latency' with caching, but they overlook that the requirement is for a durable, globally distributed primary data store with varying JSON schemas, which Redis as a cache cannot fulfill as a persistent, globally writable database.

How to eliminate wrong answers

Option A is wrong because Azure Cache for Redis is an in-memory cache, not a primary data store, and it does not natively support global distribution with write replication or schema-variant JSON documents as a durable persistence layer. Option C is wrong because Azure SQL Database requires a fixed relational schema and does not natively handle varying JSON schemas without complex workarounds, nor does it offer the same low-latency global write distribution as Cosmos DB. Option D is wrong because Azure Table Storage is a key-value store that stores data as entities with a fixed schema (partition key and row key), not as flexible JSON documents, and it lacks native global distribution with multi-region writes.

Practice this question →

118

Multi-Selecteasy

Which TWO Azure storage replication options provide durability for data in the event of a regional disaster? (Select two.)

Select 2 answers

A.Geo-zone-redundant storage (GZRS)

B.Geo-redundant storage (GRS)

C.Read-access geo-redundant storage (RA-GRS)

D.Zone-redundant storage (ZRS)

E.Locally redundant storage (LRS)

AnswersA, B

GZRS combines ZRS and GRS for maximum durability.

Why this answer

Options B and D are correct. Geo-redundant storage (GRS) replicates data to a secondary region. Geo-zone-redundant storage (GZRS) combines zone-redundancy with geo-redundancy.

Option A is wrong because LRS only protects within a single datacenter. Option C is wrong because ZRS protects within a region only. Option E is wrong because RA-GRS provides read access but same durability as GRS.

Practice this question →

119

MCQhard

Your company stores sensitive customer data in Azure Blob Storage. You must ensure that data is encrypted at rest using customer-managed keys (CMK) and that key rotation is automated. You also need to prevent data from being accessed by any Microsoft administrator. Which solution should you implement?

A.Use Azure Key Vault (Standard) to store customer-managed keys and enable automatic key rotation.

B.Use Azure Disk Encryption with customer-managed keys stored in Azure Key Vault.

C.Use Azure Key Vault Managed HSM with customer-managed keys and enable double encryption with infrastructure encryption.

D.Enable Azure Storage Service Encryption with platform-managed keys.

AnswerC

Managed HSM provides tenant-controlled keys and isolation; double encryption adds an additional layer.

Why this answer

Option C is correct because Azure Key Vault Managed HSM provides FIPS 140-2 Level 3 validated hardware security modules (HSMs) for storing customer-managed keys (CMK), supports automated key rotation, and enables double encryption via infrastructure encryption. This ensures that data is encrypted at rest with a customer-controlled key, and the use of Managed HSM prevents Microsoft administrators from accessing the key material, as the HSM is isolated and Microsoft has no export or visibility permissions.

Exam trap

The trap here is that candidates often confuse Azure Key Vault (Standard) with Managed HSM, assuming both provide the same level of isolation and security, but only Managed HSM offers FIPS 140-2 Level 3 HSM-backed keys and prevents Microsoft administrator access, which is critical for sensitive customer data scenarios.

How to eliminate wrong answers

Option A is wrong because Azure Key Vault (Standard) uses software-backed keys (not HSM-backed) and does not provide the same level of isolation to prevent Microsoft administrators from accessing key material; it also does not support double encryption with infrastructure encryption. Option B is wrong because Azure Disk Encryption is designed for encrypting virtual machine disks, not Azure Blob Storage data, and it does not address the requirement to prevent Microsoft administrator access to the keys. Option D is wrong because Azure Storage Service Encryption with platform-managed keys uses Microsoft-managed keys, not customer-managed keys, and thus does not meet the CMK requirement or provide isolation from Microsoft administrators.

Practice this question →

120

MCQeasy

A company wants to migrate its on-premises file server to Azure with minimal application changes. The application accesses files over the SMB protocol and requires identity-based access using the existing on-premises Active Directory Domain Services (AD DS). They need the solution to be fully managed with low latency. Which Azure storage solution should they choose?

A.Azure Files

B.Azure NetApp Files

C.Azure Blob Storage with NFS 3.0

D.Azure Disk Storage

AnswerA

Azure Files provides fully managed SMB file shares with on-premises AD DS authentication, ideal for lift-and-shift migration.

Why this answer

Azure Files is the correct choice because it provides fully managed SMB file shares that can be accessed over the SMB protocol with identity-based authentication using on-premises AD DS via Azure Files AD DS integration. This allows the application to connect with minimal changes, as it continues to use SMB and existing domain credentials, while Azure Files offers low-latency access when deployed in the same region as the application.

Exam trap

The trap here is that candidates often confuse Azure NetApp Files with Azure Files, assuming that because NetApp Files supports SMB and AD DS, it is the best choice, but they overlook the 'fully managed' requirement and the fact that Azure Files is the simpler, more cost-effective PaaS solution for standard file server migrations.

How to eliminate wrong answers

Option B is wrong because Azure NetApp Files is a high-performance, enterprise-grade file service that supports SMB and AD DS, but it is not fully managed in the same sense as Azure Files (it requires provisioning of capacity pools and has a different pricing model); it also introduces unnecessary complexity for a standard file server migration. Option C is wrong because Azure Blob Storage with NFS 3.0 does not support the SMB protocol, and it lacks native identity-based access with on-premises AD DS, requiring different authentication mechanisms. Option D is wrong because Azure Disk Storage provides block-level storage attached to a VM, not a shared file service; it would require the application to be rewritten or run on a VM with a file server role, increasing management overhead and not meeting the fully managed requirement.

Practice this question →

121

Drag & Dropmedium

Drag and drop the steps to migrate an on-premises SQL Server database to Azure SQL Database using the Data Migration Assistant (DMA) into the correct order.

Drag steps to the numbered slots on the right, or tap a step then tap a slot.

Steps

Order

Why this order

Install DMA, assess, fix issues, then migrate and monitor.

Practice this question →

122

MCQmedium

Your organization needs to share large files (up to 100 GB) with external partners securely. The solution must allow partners to access files for a limited time and track who accessed which file. Which Azure solution should you use?

A.Azure Data Box.

B.Azure Blob Storage with shared access signatures (SAS).

C.Azure Files with SMB protocol.

D.Azure Blob Storage with public access.

AnswerB

SAS provides time-limited access; logs track access.

Why this answer

Option B is correct because Azure Storage shared access signatures (SAS) with expiration and access logging provide time-limited access and tracking. Option A is wrong because Azure Files with SMB requires domain join. Option C is wrong because Azure Data Box is for physical data transfer.

Option D is wrong because Azure Blob Storage with public access does not provide time-limited control.

Practice this question →

123

Matchingmedium

Match each Azure disaster recovery feature to its description.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts

Matches

Orchestrates replication and failover of VMs

Cloud-based backup for Azure and on-premises workloads

Physically separate datacenter within a region

Logical grouping for fault and update domains

Another Azure region for cross-region replication

Why these pairings

These are key concepts for business continuity and disaster recovery.

Practice this question →

124

MCQmedium

You need to design a disaster recovery strategy for Azure SQL Database. The primary region is East US. The database must be available within 1 hour of a regional outage with no data loss. Which solution meets the requirements?

A.Configure a failover group with automatic failover to a secondary in West US

B.Perform regular backups to Azure Blob Storage in a secondary region

C.Configure active geo-replication and manually initiate failover

D.Use geo-restore from geo-redundant backups

AnswerA

Failover groups provide zero data loss and automatic failover within 1 hour.

Why this answer

A failover group with automatic failover to a secondary in West US meets the 1-hour RTO and zero data loss (RPO=0) requirement because Azure SQL Database failover groups use synchronous replication within the same region or asynchronous replication across regions. For a regional outage, the secondary must be in a paired region (West US) and configured with automatic failover policy; the database will be available within minutes, well under 1 hour, and with no data loss because all committed transactions are replicated synchronously before acknowledgment.

Exam trap

The trap here is that candidates confuse active geo-replication (which requires manual failover) with failover groups (which support automatic failover), and they overlook the strict RPO=0 requirement that eliminates any backup-based solution (B and D) because backups always have a non-zero RPO.

How to eliminate wrong answers

Option B is wrong because performing regular backups to Azure Blob Storage in a secondary region does not guarantee zero data loss (RPO can be up to the backup frequency, e.g., 1 hour for differential backups) and restoring from backups typically takes longer than 1 hour (RTO can be hours). Option C is wrong because active geo-replication requires manual failover initiation, which cannot guarantee a 1-hour RTO if the administrator is unavailable or delayed, and the requirement specifies automatic failover. Option D is wrong because geo-restore from geo-redundant backups (RA-GRS) has an RPO of at least 1 hour (backup frequency) and an RTO that can exceed 1 hour due to the time needed to restore a large database from a backup copy.

Practice this question →

125

MCQmedium

A company is building a new application that requires a fully managed relational database. The application has varying workloads across different databases. The company wants to pool resources to optimize cost and allow each database to scale as needed. They also need automated backups with point-in-time restore and geo-replication for disaster recovery. Which Azure data service should they use?

A.Azure SQL Database

B.Azure SQL Managed Instance

C.Azure Database for MySQL

D.Azure Database for PostgreSQL

AnswerA

Azure SQL Database supports elastic pools for resource sharing among databases, automated backups, point-in-time restore, and active geo-replication for disaster recovery.

Why this answer

Azure SQL Database is a fully managed relational database service that supports elastic pools, which allow you to pool resources across multiple databases to optimize cost and enable each database to scale independently based on demand. It also provides automated backups with point-in-time restore (PITR) and active geo-replication for disaster recovery, meeting all the stated requirements.

Exam trap

The trap here is that candidates often confuse Azure SQL Database with Azure SQL Managed Instance, assuming Managed Instance also supports elastic pools, but it does not—elastic pools are exclusive to Azure SQL Database.

How to eliminate wrong answers

Option B (Azure SQL Managed Instance) is wrong because it is designed for lift-and-shift migrations requiring near 100% SQL Server compatibility and does not support elastic pools for resource pooling across databases; it uses a fixed resource model per instance. Option C (Azure Database for MySQL) is wrong because it is a fully managed MySQL service but does not support elastic pools or the same geo-replication capabilities as Azure SQL Database; its geo-replication is limited to read replicas in paired regions without active failover. Option D (Azure Database for PostgreSQL) is wrong because it is a fully managed PostgreSQL service but lacks elastic pool functionality and its geo-replication is based on read replicas, not active geo-replication with automatic failover.

Practice this question →

126

MCQmedium

You need to design a disaster recovery strategy for an Azure SQL Database that supports a critical financial application. The recovery point objective (RPO) is 5 seconds and recovery time objective (RTO) is 30 seconds. Which option should you choose?

A.Use failover groups with manual failover.

B.Use long-term retention (LTR) backups.

C.Configure active geo-replication with auto-failover groups.

D.Enable geo-restore (geo-redundant backup).

AnswerC

Provides RPO of 5 seconds and RTO of 30 seconds.

Why this answer

Option C is correct because Azure SQL Database active geo-replication provides continuous data synchronization with an RPO of 5 seconds and automatic failover with an RTO of 30 seconds when configured with failover groups. Option A is wrong because geo-restore has an RPO of 1 hour. Option B is wrong because long-term retention does not provide near-real-time RPO.

Option D is wrong because auto-failover groups with manual failover have higher RTO.

Practice this question →

127

Multi-Selecthard

Which THREE of the following are best practices for designing a data storage solution using Azure Cosmos DB?

Select 3 answers

A.Store large binary data (e.g., images) directly as documents

B.Use the appropriate consistency level based on application requirements

C.Choose a partition key that evenly distributes request units (RU) across partitions

D.Enable autoscale on containers with unpredictable traffic patterns

E.Use manual provisioned throughput for all containers to control costs

AnswersB, C, D

Choosing consistency optimizes performance and cost.

Why this answer

Option B is correct because Azure Cosmos DB offers five well-defined consistency levels (strong, bounded staleness, session, consistent prefix, and eventual). Choosing the appropriate level based on application requirements is a best practice, as it balances data consistency guarantees against latency and throughput. For example, session consistency is ideal for multi-user applications where each user reads their own writes, while strong consistency ensures linearizability but reduces availability and increases latency.

Exam trap

The trap here is that candidates often assume manual throughput is always more cost-effective, but Azure Cosmos DB's autoscale is designed to handle unpredictable workloads without the risk of throttling or over-provisioning, making it a best practice for such scenarios.

Practice this question →

128

MCQeasy

You are designing a storage solution for a globally distributed application that requires low-latency read access from multiple regions. Which Azure storage solution should you recommend?

A.Azure Blob Storage with read-access geo-redundant storage (RA-GRS)

B.Azure SQL Database with active geo-replication

C.Azure Files with Azure File Sync

D.Azure Cosmos DB with multi-region writes and multiple read regions

AnswerD

Cosmos DB is designed for global distribution with low-latency reads and writes.

Why this answer

Azure Cosmos DB with multi-region writes and multiple read regions is the correct choice because it provides turnkey global distribution with single-digit-millisecond latency for reads and writes from any Azure region. This solution directly addresses the requirement for low-latency read access from multiple regions, as Cosmos DB automatically replicates data to all configured regions and offers multiple consistency models to balance performance and data freshness.

Exam trap

The trap here is that candidates often confuse RA-GRS (which provides read-only secondary access only during failover) with true active-active multi-region reads, leading them to choose Azure Blob Storage instead of Cosmos DB.

How to eliminate wrong answers

Option A is wrong because Azure Blob Storage with RA-GRS provides read access from a secondary region only during failover or if the primary region is unavailable, and it does not offer active-active multi-region reads with low-latency guarantees; the secondary region is read-only and not designed for simultaneous low-latency access from multiple regions. Option B is wrong because Azure SQL Database with active geo-replication is designed for disaster recovery and read-scale workloads, but it does not support multi-region writes and typically incurs higher latency for cross-region reads compared to a globally distributed NoSQL solution like Cosmos DB. Option C is wrong because Azure Files with Azure File Sync is optimized for file sharing and caching on-premises or in a single region, not for globally distributed low-latency read access from multiple Azure regions; it relies on sync intervals and does not provide native multi-region read endpoints.

Practice this question →

129

MCQmedium

Your company uses Azure Cosmos DB for a globally distributed application. You need to ensure that writes in one region are not lost if that region fails. Which consistency level should you use to guarantee that writes are durable?

A.Eventual consistency

B.Bounded staleness consistency

C.Strong consistency

D.Consistent prefix consistency

AnswerB

Bounded staleness provides a guarantee that writes are not lost beyond a configurable staleness.

Why this answer

Bounded staleness consistency guarantees that writes are durable across regions by ensuring that replicas lag behind the primary by at most K versions or a time interval T. This means that even if a region fails, all acknowledged writes are preserved and will be replicated to other regions within the configured staleness window, preventing data loss.

Exam trap

The trap here is that candidates often assume strong consistency is required for write durability, but bounded staleness actually provides the same durability guarantee with better performance and availability in globally distributed setups.

How to eliminate wrong answers

Option A is wrong because eventual consistency does not guarantee durability of writes in the event of a region failure; it only ensures that replicas will eventually converge, but writes may be lost if the region fails before propagation. Option C is wrong because strong consistency, while providing the highest durability, is not required to prevent write loss and can introduce higher latency and reduced availability in globally distributed scenarios. Option D is wrong because consistent prefix consistency ensures reads see writes in order but does not guarantee that all writes are durably stored across regions before a failure.

Practice this question →

130

MCQhard

You are designing a data lake for advanced analytics in Azure. The data includes structured, semi-structured, and unstructured data. The solution must support schema-on-read and have the ability to query using SQL. Which Azure service should you choose?

A.Azure Blob Storage.

B.Azure SQL Database.

C.Azure Data Lake Storage Gen2.

D.Azure Cosmos DB.

AnswerC

Supports all data types, schema-on-read, and SQL querying.

Why this answer

Option D is correct because Azure Data Lake Storage Gen2 provides a hierarchical namespace for storing all data types and integrates with query engines like Azure Synapse SQL for schema-on-read. Option A is wrong because Azure SQL Database is for structured data only. Option B is wrong because Azure Cosmos DB is for transactional workloads, not data lake.

Option C is wrong because Azure Blob Storage lacks the hierarchical namespace needed for a data lake.

Practice this question →

131

Multi-Selecthard

Which THREE considerations are important when designing a storage solution for Azure Virtual Desktop (AVD) user profiles using FSLogix? (Choose three.)

Select 3 answers

A.Use Azure Files as the storage solution.

B.Use a public endpoint for profile storage.

C.Provision sufficient IOPS for user profiles.

D.Enable geo-redundant storage (GRS) for disaster recovery.

E.Ensure low latency between session hosts and storage.

AnswersA, C, E

Supports SMB, needed for FSLogix.

Why this answer

Options B, C, and D are correct. FSLogix profiles require a share that supports SMB (Azure Files). Low latency is critical for user experience.

High IOPS are needed for profile reads/writes. Option A is wrong because public endpoint is not required; private endpoint is recommended. Option E is wrong because geo-redundancy is not typically required for FSLogix; locally redundant or zone-redundant is sufficient.

Practice this question →

132

MCQmedium

You need to design a storage solution for a global e-commerce application that requires low-latency access to product catalog data across multiple Azure regions. The data is read-heavy and updates are rare. Which service should you use for the primary data store?

A.Azure SQL Database with active geo-replication

B.Azure Table Storage

C.Azure Redis Cache

D.Azure Cosmos DB

AnswerD

Cosmos DB offers turnkey global distribution with multiple consistency levels and low latency.

Why this answer

Azure Cosmos DB is the correct choice because it provides globally distributed, multi-region writes and reads with turnkey data replication and guaranteed single-digit-millisecond latency at the 99th percentile. Its multi-homing API and automatic failover capabilities make it ideal for a read-heavy, rarely updated global e-commerce catalog that requires low-latency access across multiple Azure regions.

Exam trap

The trap here is that candidates often confuse a caching layer (Redis) with a globally distributed primary store, or assume that a relational database with geo-replication (Azure SQL) is suitable for any multi-region scenario, ignoring the specific read-heavy, rare-update pattern that Cosmos DB is optimized for.

How to eliminate wrong answers

Option A is wrong because Azure SQL Database with active geo-replication is designed for transactional workloads with frequent writes and strong consistency, not for a read-heavy, rarely updated catalog; its geo-replication adds latency and cost overhead for read-only scenarios. Option B is wrong because Azure Table Storage is a NoSQL key-value store that lacks native global distribution and multi-region replication, resulting in higher latency for cross-region reads and no built-in low-latency guarantees. Option C is wrong because Azure Redis Cache is an in-memory cache, not a durable primary data store; it is used to accelerate reads from a backing database, not to serve as the authoritative source of truth for product catalog data.

Practice this question →

133

MCQmedium

A company is migrating a large on-premises SQL Server database to Azure SQL Managed Instance. They need to minimize downtime during migration. The database is 500 GB and the network link is 1 Gbps. Which migration approach should they recommend?

A.Use Azure Database Migration Service with online migration

B.Perform offline backup and restore

C.Use transactional replication

D.Export BACPAC and import

AnswerA

Online migration via DMS allows continuous replication with minimal downtime, suitable for a 500 GB database.

Why this answer

Option A is correct because Azure Database Migration Service (DMS) with online migration mode uses continuous change data capture (CDC) to synchronize ongoing changes from the on-premises SQL Server to Azure SQL Managed Instance, minimizing downtime to a brief cutover window. This approach is ideal for a 500 GB database over a 1 Gbps link, as it avoids the lengthy full data transfer required by offline methods.

Exam trap

The trap here is that candidates often assume offline backup and restore is the simplest and fastest method, but they overlook the 'minimize downtime' requirement, which makes online migration via DMS the only correct choice despite its added complexity.

How to eliminate wrong answers

Option B is wrong because offline backup and restore requires taking the source database offline for the entire duration of the backup transfer and restore, which for a 500 GB database over 1 Gbps would cause significant downtime (hours), failing the minimize-downtime requirement. Option C is wrong because transactional replication requires manual setup of publishers, distributors, and subscribers, and while it can reduce downtime, it is more complex to configure and manage for a full database migration compared to DMS, and it does not natively handle schema changes or large-scale migrations as efficiently. Option D is wrong because exporting a BACPAC file involves a full database export and import, which locks tables during export and requires the database to be mostly offline, resulting in substantial downtime for a 500 GB database over 1 Gbps.

Practice this question →

134

MCQeasy

You need to design a storage solution for a large-scale media streaming application. The application serves video files to users worldwide. The solution must minimize latency for end-users and optimize content delivery costs. Which Azure service combination should you use?

A.Azure Cosmos DB with multi-region writes

B.Azure NetApp Files with Azure Front Door

C.Azure Blob Storage with Azure Content Delivery Network (CDN)

D.Azure Files with Azure File Sync

AnswerC

Blob Storage stores videos; CDN caches at edge locations for low latency and cost efficiency.

Why this answer

Azure Blob Storage is optimized for storing large, unstructured data like video files, and when paired with Azure Content Delivery Network (CDN), it caches content at edge nodes worldwide. This combination minimizes latency for global users by serving videos from the nearest point of presence (PoP) and reduces egress costs by offloading traffic from the origin storage to the CDN's distributed network.

Exam trap

The trap here is that candidates confuse Azure Front Door (a global load balancer with HTTP caching) with a full CDN, but for static video content, Azure CDN (or Azure Front Door's CDN profile) is the correct service because it provides dedicated edge caching and egress cost optimization, whereas Front Door's primary role is application acceleration and routing.

How to eliminate wrong answers

Option A is wrong because Azure Cosmos DB is a NoSQL database designed for transactional workloads with multi-region writes, not for storing and serving large binary video files; it lacks the cost-effective blob storage and CDN integration needed for media streaming. Option B is wrong because Azure NetApp Files provides high-performance NFS/SMB file shares for enterprise applications, not a globally distributed content delivery mechanism; Azure Front Door is a global load balancer and application accelerator, not a caching CDN optimized for static content like video files. Option D is wrong because Azure Files with Azure File Sync is designed for hybrid file sharing and synchronization across on-premises and cloud, not for low-latency global video streaming; it lacks edge caching and does not optimize egress costs for large-scale media delivery.

Practice this question →

135

MCQhard

A financial services company is migrating its on-premises SAP HANA database to Azure. The database requires high IOPS and low latency with a capacity of 4 TB. They need to choose a storage solution that supports SAP HANA certified configurations. Which Azure storage solution should they use?

A.Azure Premium SSD v2

B.Azure Ultra Disk Storage

C.Azure Standard HDD

D.Azure NetApp Files

AnswerB

Azure Ultra Disk Storage provides high IOPS, low latency, and is certified for SAP HANA.

Why this answer

Azure Ultra Disk Storage is the correct choice because it is the only Azure managed disk that is SAP HANA certified for high IOPS and sub-millisecond latency, which is critical for SAP HANA workloads. It supports up to 300,000 IOPS and 2,000 MB/s throughput per disk, and can be provisioned with up to 64 TB capacity, easily covering the 4 TB requirement. Premium SSD v2 is not SAP HANA certified for production databases, and Azure NetApp Files, while offering high performance, is not a managed disk and requires specific NFS configurations that may not meet SAP HANA's strict certification requirements for block storage.

Exam trap

The trap here is that candidates often assume Premium SSD v2 is the best choice for all high-performance workloads, but SAP HANA has specific certification requirements that exclude Premium SSD v2 for production databases, making Ultra Disk the only correct option among the managed disks listed.

How to eliminate wrong answers

Option A is wrong because Azure Premium SSD v2, despite offering high IOPS and low latency, is not certified by SAP for SAP HANA production workloads; SAP HANA requires specific disk types like Ultra Disk or Premium SSD (v1) for certified configurations. Option C is wrong because Azure Standard HDD provides low IOPS and high latency, which cannot meet the performance demands of SAP HANA databases requiring high IOPS and low latency. Option D is wrong because Azure NetApp Files is a file-based NFS storage solution, not a block storage managed disk, and while it can be used with SAP HANA, it requires additional configuration and is not the direct Azure managed disk solution that is SAP HANA certified for high IOPS and low latency block storage.

Practice this question →

136

MCQhard

Contoso Ltd. is a global retail company with headquarters in New York and operations in Europe and Asia. They are migrating their on-premises SQL Server databases to Azure. The databases include a customer database (500 GB), an orders database (2 TB), and a product catalog database (100 GB). The customer database requires high read throughput with sub-10 ms latency for global users. The orders database must support complex queries and reporting with point-in-time restore capability up to 35 days. The product catalog is updated infrequently but must be available for read-heavy workloads with strong consistency. Contoso wants to minimize costs while meeting performance and compliance requirements. They also need to support hybrid deployments for databases that must remain on-premises due to data sovereignty laws. You need to design a data storage solution. Which combination of Azure services and configurations should you recommend?

A.Azure SQL Managed Instance for all databases with geo-replication for customer DB; use failover groups for global distribution; Azure Data Sync for hybrid

B.Azure SQL Database Hyperscale for all databases; use geo-replication for customer DB; Azure SQL Server on Azure VMs for hybrid

C.Azure Cosmos DB with multiple write regions for customer DB; Azure SQL Database Business Critical for orders; Azure SQL Database serverless for product catalog; Azure SQL Managed Instance with managed instance link for hybrid

D.Azure SQL Database Business Critical for customer DB with geo-replication; Azure SQL Database Hyperscale for orders; Azure SQL Database serverless for product catalog; Azure SQL Managed Instance for hybrid

AnswerC

Cosmos DB provides global low-latency; SQL DB Business Critical supports complex queries; serverless reduces cost; managed instance link enables hybrid.

Why this answer

Option C is correct because Azure Cosmos DB with multiple write regions provides global low-latency for customer data; Azure SQL Database with Business Critical tier for orders provides complex query support and point-in-time restore; Azure SQL Database serverless for product catalog reduces costs for infrequent updates; and Azure SQL Managed Instance supports hybrid deployments with link. Option A is wrong because Azure SQL Database Hyperscale is for large databases but does not provide global low-latency. Option B is wrong because Azure SQL Database for customer data would not meet sub-10 ms latency globally.

Option D is wrong because Azure SQL Managed Instance for all databases increases costs unnecessarily.

Practice this question →

137

MCQhard

A company runs a high-throughput time-series workload that stores sensor data from IoT devices. Data is ingested at a rate of millions of events per second. The application requires low-latency queries (under 100 ms) on recent data (less than 30 days old) and the ability to run occasional analytical queries on historical data older than 30 days. The solution must automatically move cold data to a cost-optimized tier and provide built-in analytics. Which Azure service should they use?

A.Azure Time Series Insights (TSI)

B.Azure Cosmos DB with analytical store

C.Azure Event Hubs with Azure Data Lake Storage

D.Azure SQL Database with elastic query

AnswerA

Azure TSI is purpose-built for time-series data, supports high ingestion, low-latency warm queries, automatic cold tiering, and built-in time-series analytics.

Why this answer

Azure Time Series Insights (TSI) is purpose-built for high-throughput IoT time-series data, supporting millions of events per second with sub-100 ms query latency on warm data (less than 30 days old). It automatically moves cold data to a cost-optimized warm/cold store and provides built-in analytics and visualization for time-series patterns, making it the ideal choice for this scenario.

Exam trap

The trap here is that candidates often choose Azure Cosmos DB or Event Hubs because they are familiar with high-throughput ingestion, but they overlook the specific requirement for built-in time-series analytics and automatic cold data tiering, which TSI uniquely provides out of the box.

How to eliminate wrong answers

Option B is wrong because Azure Cosmos DB with analytical store is a NoSQL database optimized for multi-model data and transactional workloads, not specifically for high-throughput time-series ingestion with automatic cold tiering and built-in time-series analytics. Option C is wrong because Azure Event Hubs with Azure Data Lake Storage provides event ingestion and long-term storage but lacks built-in low-latency querying (under 100 ms) and native time-series analytics; it requires additional services like Azure Stream Analytics or Synapse for querying. Option D is wrong because Azure SQL Database with elastic query is a relational database designed for structured transactional data, not for ingesting millions of events per second with automatic cold data movement and time-series-specific analytics.

Practice this question →

138

Multi-Selecteasy

Which TWO Azure services provide native support for change data capture (CDC) to stream database changes to other systems?

Select 2 answers

A.Azure Table Storage

B.Azure Cosmos DB

C.Azure Cache for Redis

D.Azure SQL Database

E.Azure Synapse Link for Azure Cosmos DB

AnswersB, D

Cosmos DB change feed provides CDC.

Why this answer

Azure Cosmos DB provides native change feed support, which is a persistent, ordered log of changes (inserts, updates, deletes) that can be streamed to downstream systems via the Change Feed processor or Azure Functions. This makes it a correct answer for change data capture (CDC) scenarios.

Exam trap

The trap here is that candidates may confuse Azure Synapse Link for Azure Cosmos DB (an analytical store) with a native CDC service, when in fact it relies on the underlying change feed but is not itself a CDC streaming solution.

Practice this question →

139

MCQmedium

A company is migrating a MongoDB-compatible application to Azure. The application requires low-latency reads and writes globally. It needs to support multi-region writes so that updates can be made from any region with automatic conflict resolution. The data is JSON documents that can vary in schema. The company wants a fully managed database service with native support for MongoDB APIs. Which Azure data service should they choose?

A.Azure SQL Database

B.Azure Cosmos DB with the API for MongoDB

C.Azure Database for MongoDB

D.Azure Cache for Redis

AnswerB

Cosmos DB's API for MongoDB provides full MongoDB wire protocol compatibility, global distribution with multi-region writes, configurable consistency levels, and automatic conflict resolution. It is designed for low-latency, globally distributed applications.

Why this answer

Azure Cosmos DB with the API for MongoDB is the correct choice because it provides a fully managed, globally distributed database service that natively supports the MongoDB wire protocol. It offers multi-region writes with automatic conflict resolution using last-writer-wins (LWW) or custom conflict resolution policies, ensuring low-latency reads and writes globally. Its schema-agnostic nature handles JSON documents with varying schemas, meeting all stated requirements.

Exam trap

The trap here is that candidates may confuse 'Azure Database for MongoDB' (which does not exist) with Azure Cosmos DB's API for MongoDB, or incorrectly assume that a relational database like Azure SQL Database can handle schema-flexible JSON documents with global multi-region writes.

How to eliminate wrong answers

Option A is wrong because Azure SQL Database is a relational database that does not support MongoDB APIs, JSON document storage with varying schemas, or multi-region writes with automatic conflict resolution. Option C is wrong because Azure Database for MongoDB does not exist as a native Azure service; the correct service is Azure Cosmos DB with the API for MongoDB, and this option represents a common misconception of a separate service. Option D is wrong because Azure Cache for Redis is an in-memory caching service, not a fully managed database for persistent JSON document storage, and it does not support MongoDB APIs or multi-region writes.

Practice this question →

140

MCQeasy

A company is deploying a containerized microservices application on Azure Kubernetes Service (AKS). The application requires persistent storage that can be attached to pods and supports dynamic provisioning. Which Azure storage solution should they use?

A.Azure Blob Storage

B.Azure Files

C.Azure NetApp Files

D.Azure Disks

AnswerD

Azure Disks support dynamic provisioning via StorageClass and are commonly used with AKS.

Why this answer

Azure Disks is the correct choice because it provides block-level storage volumes that can be dynamically provisioned via the AKS built-in StorageClass, supporting ReadWriteOnce access mode required for a single pod in a containerized microservices application. Azure Disks integrate directly with Kubernetes PersistentVolumeClaims (PVCs) for dynamic provisioning, offering low-latency, high-performance storage suitable for stateful workloads.

Exam trap

The trap here is that candidates often confuse Azure Files (shared file storage) with Azure Disks (block storage), assuming that 'persistent storage' always means file shares, but for single-pod dynamic provisioning in AKS, Azure Disks are the native and optimal choice.

How to eliminate wrong answers

Option A is wrong because Azure Blob Storage is object storage accessed via HTTP/HTTPS, not block storage, and does not support direct attachment to pods via Kubernetes PV/PVC without a CSI driver or sidecar, making it unsuitable for dynamic provisioning in AKS. Option B is wrong because Azure Files provides SMB/NFS file shares that support ReadWriteMany access, but for a single-pod persistent storage scenario, Azure Disks offer lower latency and are more cost-effective; Azure Files is typically used for shared access across multiple pods, not single-pod dynamic provisioning. Option C is wrong because Azure NetApp Files is a premium enterprise-grade file service with high cost and complexity, overkill for standard AKS persistent storage, and requires additional configuration for dynamic provisioning compared to the native Azure Disks integration.

Practice this question →

141

MCQmedium

A company runs a legacy application on Azure Virtual Machines. The application uses a SQL Server database that requires 50,000 IOPS consistently. It also uses a shared file system for storing documents. They plan to migrate from on-premises where they used a SAN for block storage and NAS for file shares. Which combination of Azure storage should they use to meet performance requirements?

A.Premium SSD v2 disks for the database and Azure Files premium tier for the file share.

B.Premium SSD (non-v2) for the database and Azure NetApp Files for the file share.

C.Ultra Disk for the database and Azure Files standard tier for the file share.

D.Standard SSD for the database and Azure Blob Storage for the file share.

AnswerA

Premium SSD v2 can achieve 50,000 IOPS with a 320 GiB disk (which gives 4,000 IOPS per GiB, 320*4000=1,280,000? No, let's check: Premium SSD v2 IOPS scales linearly to 80,000 at 1 TiB, but smaller disks can still achieve high IOPS. It is designed for high-performance databases. Azure Files Premium offers low latency and high throughput for file sharing, suitable for a shared file system.

Why this answer

Premium SSD v2 disks can deliver up to 80,000 IOPS per disk, easily meeting the 50,000 IOPS requirement for the SQL Server database. Azure Files premium tier uses SSD-backed storage and provides consistent low-latency performance suitable for a shared file system, replacing the on-premises NAS. This combination directly maps the SAN (block) and NAS (file) workloads to Azure's highest-performance managed disks and file shares.

Exam trap

The trap here is that candidates often assume Premium SSD (non-v2) or Ultra Disk are the only high-IOPS options, overlooking that Premium SSD v2 is the only managed disk tier that can deliver 50,000 IOPS on a single disk without requiring disk striping or large disk sizes.

How to eliminate wrong answers

Option B is wrong because Premium SSD (non-v2) has a maximum IOPS of 20,000 per disk (for P50 size), which cannot meet the 50,000 IOPS requirement; Azure NetApp Files is a valid file share solution but is overkill and not the most cost-effective choice when Azure Files premium tier suffices. Option C is wrong because Ultra Disk can meet the IOPS requirement, but Azure Files standard tier uses HDD-based storage with much lower IOPS and higher latency, failing the consistent performance needed for the file share. Option D is wrong because Standard SSD maxes out at 6,000 IOPS per disk, far below 50,000 IOPS, and Azure Blob Storage is object storage, not a shared file system (it lacks SMB protocol support for file shares).

Practice this question →

142

MCQeasy

A company runs a global e-commerce application that needs to store product catalog data. The data is JSON documents with variable schemas. The application requires single-digit millisecond read and write latencies at any scale and must support automatic synchronous replication across multiple Azure regions for high availability and low latency reads from any region. Which Azure data service should they choose?

A.Azure SQL Database with active geo-replication

B.Azure Cosmos DB with multi-region writes

C.Azure Table Storage

D.Azure Database for PostgreSQL with read replicas

AnswerB

Cosmos DB natively supports globally distributed data with multi-region writes, automatic and synchronous replication, and guaranteed single-digit millisecond latency at the 99th percentile for reads and writes. It also handles JSON documents with variable schemas.

Why this answer

Azure Cosmos DB with multi-region writes is the correct choice because it natively supports JSON documents with variable schemas, guarantees single-digit millisecond read and write latencies at any scale via its multi-homing API, and provides automatic synchronous replication across multiple Azure regions with active-active configurations. This ensures high availability and low-latency reads from any region without manual failover or data loss.

Exam trap

The trap here is that candidates often confuse 'automatic synchronous replication' with 'active geo-replication' or 'read replicas,' assuming that any multi-region database service provides synchronous writes, whereas only Cosmos DB with multi-region writes offers true synchronous replication across regions for both reads and writes.

How to eliminate wrong answers

Option A is wrong because Azure SQL Database with active geo-replication uses asynchronous replication, which cannot guarantee synchronous multi-region writes and may introduce latency or data loss during failover, and it requires a fixed relational schema, not variable JSON documents. Option C is wrong because Azure Table Storage is a NoSQL key-value store that does not support JSON documents natively, lacks automatic synchronous multi-region replication, and typically offers higher latencies (tens of milliseconds) compared to Cosmos DB's single-digit millisecond guarantees. Option D is wrong because Azure Database for PostgreSQL with read replicas uses asynchronous replication for read scaling, not synchronous multi-region writes, and its relational schema cannot handle variable JSON documents as efficiently as a native document database.

Practice this question →

143

MCQhard

A company is designing a disaster recovery solution for its on-premises SQL Server databases that are critical for business operations. The databases are approximately 500 GB each. The solution must meet the following requirements: - Replicate data to Azure with minimal data loss (RPO of 15 minutes). - Automatically failover to Azure in case of an on-premises outage. - Use existing SQL Server licenses to minimize costs. Which Azure service should the company use?

A.Azure Site Recovery with SQL Server replication

B.Azure Database Migration Service (DMS)

C.Azure SQL Managed Instance with managed instance link

D.Azure SQL Database Managed Instance with transaction replication

AnswerC

Provides near-real-time replication and automatic failover using existing licenses.

Why this answer

Option D is correct because Azure SQL Managed Instance supports managed instance link for near-real-time replication with RPO of 15 minutes and automatic failover using distributed availability groups. Option A is wrong because Azure Database Migration Service is for one-time migration, not ongoing replication. Option B is wrong because Azure Site Recovery replicates at the VM level, not database-level with SQL-specific consistency.

Option C is wrong because Azure SQL Database Managed Instance does not support Azure Hybrid Benefit for SQL Server licenses in the same way as Azure SQL Managed Instance.

Practice this question →

144

MCQeasy

Your company needs to store configuration data (key-value pairs) for applications in a highly scalable and low-latency manner. The data is accessed frequently. Which Azure service should you choose?

A.Azure Cosmos DB.

B.Azure Cache for Redis.

C.Azure SQL Database.

D.Azure Table Storage.

AnswerB

In-memory, low-latency, scalable.

Why this answer

Option C is correct because Azure Cache for Redis provides in-memory key-value storage with low latency and high scalability. Option A is wrong because Azure Table Storage is slower. Option B is wrong because Azure Cosmos DB is overkill for simple key-value.

Option D is wrong because Azure SQL Database is relational and has higher latency.

Practice this question →

145

MCQhard

Your company plans to store sensitive customer data in Azure Blob Storage. The data must be encrypted at rest and in transit. Additionally, access must be audited and restricted based on user identity. Which configuration meets these requirements?

A.Use shared access signatures (SAS) for access control.

B.Use Azure RBAC for access and Azure Monitor logs for auditing.

C.Configure network firewalls and use private endpoints.

D.Enable customer-managed keys (CMK) and use SAS.

AnswerB

RBAC provides identity-based access; logs provide auditing.

Why this answer

Option C is correct because Azure Storage provides encryption at rest (SSE) by default, HTTPS ensures encryption in transit, and Azure RBAC with Azure Monitor logs provides identity-based access and auditing. Option A is wrong because SAS tokens do not use user identity. Option B is wrong because customer-managed keys are optional and not required for encryption at rest.

Option D is wrong because firewall rules do not provide identity-based access control.

Practice this question →

146

MCQmedium

A company deploys a web application on Azure VMs. The application stores session state and frequently accessed product data. They need a low-latency, in-memory cache to reduce database load and improve response times. The cache must be managed and support data persistence with replication across availability zones within the region. Which Azure service and tier should they choose?

A.Azure Cache for Redis (Premium tier)

B.Azure Cache for Redis (Basic tier)

C.Azure Cache for Redis (Standard tier)

D.Azure Cache for Redis (Enterprise tier)

AnswerA

The Premium tier of Azure Cache for Redis provides features like data persistence (RDB/AOF), clustering, and zone redundancy with replication across availability zones for high availability. It is fully managed.

Why this answer

Azure Cache for Redis Premium tier is the correct choice because it supports data persistence (RDB/AOF), replication across availability zones via zone redundancy, and provides low-latency, in-memory caching for session state and product data. The Basic tier lacks replication and persistence, Standard tier offers replication but not zone redundancy or persistence, and Enterprise tier is overkill for this scenario, adding unnecessary cost and complexity.

Exam trap

The trap here is that candidates often confuse the Standard tier's replication (which is within a single datacenter) with zone redundancy, or assume Enterprise tier is always better for persistence, when Premium tier specifically offers both persistence and zone redundancy at a lower cost.

How to eliminate wrong answers

Option B (Basic tier) is wrong because it provides no replication, no data persistence, and no SLA, making it unsuitable for high-availability or durable caching needs. Option C (Standard tier) is wrong because while it offers replication within a single datacenter, it does not support zone redundancy across availability zones or built-in data persistence (RDB/AOF). Option D (Enterprise tier) is wrong because it is designed for advanced scenarios like active geo-replication and Redis modules (RediSearch, RedisBloom), which are not required here, and it incurs higher cost without providing additional benefit for basic session state and product caching.

Practice this question →

147

MCQmedium

You are deploying an Azure SQL Database using the ARM template snippet above. Which of the following describes the resulting database configuration?

A.Standard tier with 100 DTUs

B.Zone-redundant deployment

C.Maximum size of 10 GB

D.Premium tier with 100 DTUs

AnswerA

S3 corresponds to Standard tier with 100 DTUs.

Why this answer

The ARM template snippet specifies `requestedServiceObjectiveName: "S0"`, which maps to the Standard service tier with 100 DTUs. The S0 performance level in Azure SQL Database provides 100 DTUs and a maximum database size of 250 GB, making option A correct.

Exam trap

The trap here is that candidates often confuse the maximum size limits between tiers (e.g., assuming S0 has a 10 GB limit like Basic) or mistakenly associate the DTU count (100) with the Premium tier, overlooking that the `requestedServiceObjectiveName` value explicitly defines the tier and performance level.

How to eliminate wrong answers

Option B is wrong because zone-redundant deployment is only available for the Premium and Business Critical service tiers, not the Standard tier, and the template does not include any zone-redundant configuration property. Option C is wrong because the Standard S0 tier has a maximum size of 250 GB, not 10 GB; the 10 GB limit applies to the Basic tier (B). Option D is wrong because the template specifies `requestedServiceObjectiveName: "S0"`, which is a Standard tier objective, not a Premium tier; Premium tiers use objectives like P1, P2, etc., and offer higher DTUs and features like zone redundancy.

Practice this question →

148

MCQeasy

A company needs to store and analyze petabytes of IoT telemetry data. The data is append-only and rarely updated. They require SQL-based querying and columnar storage for fast analytics. Which Azure storage solution should you choose?

A.Azure Cosmos DB with analytical store

B.Azure SQL Database with columnstore indexes

C.Azure Blob Storage with Azure Cognitive Search

D.Azure Data Lake Storage Gen2 with Azure Synapse SQL pool

AnswerD

Data Lake Storage Gen2 provides scalable storage and Synapse SQL pool enables SQL over Parquet.

Why this answer

Azure Data Lake Storage Gen2 (ADLS Gen2) provides hierarchical namespace and petabyte-scale storage optimized for big data analytics. When combined with Azure Synapse SQL pool (formerly SQL DW), it enables SQL-based querying over columnar storage (using PolyBase or CETAS) for fast analytics on append-only IoT telemetry data. This combination supports massive data volumes, append-only workloads, and columnar storage for high-performance analytical queries.

Exam trap

The trap here is that candidates often choose Azure SQL Database with columnstore indexes (Option B) because they focus on the 'SQL-based querying and columnar storage' requirement without considering the petabyte-scale constraint, which exceeds Azure SQL Database's maximum storage capacity.

How to eliminate wrong answers

Option A is wrong because Azure Cosmos DB with analytical store is designed for globally distributed, multi-model NoSQL data with automatic indexing, not for petabyte-scale append-only IoT telemetry requiring SQL-based columnar analytics; its analytical store uses Azure Synapse Link but is optimized for operational data, not bulk append-only streams. Option B is wrong because Azure SQL Database with columnstore indexes is a relational OLTP database with a maximum size of 4 TB (or 128 TB with Hyperscale), which cannot handle petabytes of data, and columnstore indexes are best for read-mostly workloads but the service lacks the distributed scale-out architecture needed for petabyte-scale analytics. Option C is wrong because Azure Blob Storage with Azure Cognitive Search provides object storage and full-text search capabilities, not SQL-based querying or columnar storage; Cognitive Search is for indexing and searching unstructured text, not for analytical queries on structured IoT data.

Practice this question →

149

MCQhard

A company runs a large-scale write-intensive application that requires a horizontally scalable relational database. They need to distribute data across multiple nodes to handle high write throughput while supporting SQL queries, including joins and transactions. The solution must be fully managed and provide elastic scaling. Which Azure database service should they choose?

A.Azure SQL Database Hyperscale

B.Azure Cosmos DB

C.Azure Database for PostgreSQL Hyperscale (Citus)

D.Azure SQL Managed Instance

AnswerC

Citus distributes data across multiple nodes, allowing horizontal scaling for write-heavy workloads. It supports full SQL, joins, and transactions, meeting the relational database requirements.

Why this answer

Azure Database for PostgreSQL Hyperscale (Citus) is the correct choice because it provides horizontal scaling (sharding) across multiple worker nodes using the Citus extension, which distributes data and parallelizes SQL queries. It supports full SQL, including joins and transactions, while offering elastic scaling for write-intensive workloads. This makes it ideal for large-scale relational databases that need high write throughput and horizontal scalability.

Exam trap

The trap here is that candidates often confuse 'horizontal scaling' with 'hyperscale' or 'managed instance' options, assuming any 'scalable' database service supports distributed writes, but only Citus provides true horizontal sharding for relational workloads with full SQL and transaction support.

How to eliminate wrong answers

Option A is wrong because Azure SQL Database Hyperscale is designed for read-intensive workloads with fast scaling of compute and storage, but it does not distribute data across multiple nodes for horizontal write scaling; it uses a single primary node with page servers for storage. Option B is wrong because Azure Cosmos DB is a NoSQL database that does not support full relational SQL features like joins and transactions across multiple documents in the same way a relational database does; it is schema-agnostic and not a relational database. Option D is wrong because Azure SQL Managed Instance is a fully managed instance of SQL Server that provides vertical scaling but not horizontal scaling across multiple nodes; it is limited to a single instance and does not distribute data across nodes for high write throughput.

Practice this question →

150

Multi-Selecthard

Which THREE considerations are important when designing a data storage solution for a high-throughput IoT ingestion pipeline in Azure?

Select 3 answers

A.Network latency between devices and Azure

B.Ingestion throughput limits of the storage service

C.Data retention and archival policies

D.Partitioning strategy to distribute load

E.Data consistency levels required by downstream consumers

AnswersB, C, D

Must ensure the service can handle the peak ingestion rate.

Why this answer

Option B is correct because Azure Storage services like Blob Storage and Event Hubs have defined ingestion throughput limits (e.g., up to 20 MB/s per partition or 1 MB/s per ingress for standard-tier Event Hubs). Exceeding these limits causes throttling (HTTP 429 errors) and data loss, making throughput capacity a critical design consideration for high-throughput IoT pipelines.

Exam trap

The trap here is confusing network-level considerations (latency, bandwidth) with storage-level design constraints (throughput limits, partitioning), leading candidates to select Option A instead of focusing on the storage service's inherent ingestion capacity.

Practice this question →

← PreviousPage 2 of 4 · 233 questions totalNext →

Ready to test yourself?

Try a timed practice session using only Data Storage Solutions questions.

Start 20-question session