CCNA Design data storage solutions Questions — Page 3 of 3

151

MCQmedium

A company stores log data in Azure Blob Storage. The logs are accessed frequently for the first 30 days, then only occasionally for up to 1 year, and after that must be retained for 7 years for compliance purposes. The company wants to minimize storage costs by automatically moving data to cheaper tiers. Which Azure Blob Storage lifecycle management policy should they implement?

A.Move to Cool tier after 30 days, move to Archive tier after 365 days, delete after 2555 days

B.Move to Cool tier after 30 days, move to Archive tier after 365 days, delete after 7 years

C.Move to Cool tier after 30 days, move to Archive tier after 30 days, delete after 2555 days

D.Move to Archive tier after 30 days, keep in Archive until deletion after 2555 days

AnswerA

This policy correctly matches the log usage lifecycle: for the first 30 days data remains Hot for frequent queries; from day 30 to day 365 it is moved to Cool because access becomes occasional but still needed; after 365 days it is moved to Archive for long-term compliance while deletion occurs after 2555 days (exactly 7 years). That transition sequence minimizes cost: Hot for active use, Cool for sporadic retrieval with no rehydration fee, and Archive for rarely accessed records, with deletion eliminating any further storage charges. The rule uses numeric day values as Azure requires.

Why this answer

It aligns with the access patterns: move to Cool tier after 30 days (frequent access period), move to Archive tier after 365 days (occasional access period ends), and delete after 2555 days (7 years retention). This minimizes costs by transitioning data to progressively cheaper storage tiers and automatically deleting it when compliance retention expires.

Exam trap

The trap here is that candidates may choose Option B thinking '7 years' is acceptable in the policy, but Azure requires the 'delete after' action to be specified in days (2555), not years, and they may overlook the early deletion penalty of the Archive tier when moving data too soon.

How to eliminate wrong answers

Option B is wrong because it specifies 'delete after 7 years' without converting to days; Azure lifecycle management policies require the 'delete after' action to be defined in days, not years, and 7 years equals 2555 days, not a literal '7 years' string. Option C is wrong because it moves data to Archive tier after only 30 days, which would incur early deletion fees and retrieval costs since logs are still accessed occasionally for up to a year; Archive tier is for rarely accessed data and has a 180-day minimum storage charge. Option D is wrong because it moves data directly to Archive tier after 30 days, ignoring the Cool tier entirely, which increases costs due to early deletion penalties and higher retrieval costs for the occasional access period up to 365 days.

Practice this question →

152

MCQeasy

A company needs a fully managed NoSQL database for a new application with a key-value and document data model. They require single-digit millisecond latency at any scale, multi-region writes with automatic conflict resolution, and a serverless capacity option to handle unpredictable traffic. Which Azure data service should they use?

A.Azure Table Storage

B.Azure Cosmos DB

C.Azure Cache for Redis

D.Azure SQL Database

AnswerB

Azure Cosmos DB is the correct choice because it is a fully managed, multi-model NoSQL database that guarantees single-digit millisecond latency for reads and writes at the 99th percentile. Its multi-region writes capability lets you write to any region with automatic conflict resolution policies and a health-based failover, while the serverless mode adds throughput and storage per request, making it ideal for spiky or unpredictable workloads.

Why this answer

Azure Cosmos DB is the correct choice because it is a fully managed NoSQL database that supports both key-value and document data models natively. It guarantees single-digit millisecond latency at any scale, offers multi-region writes with automatic conflict resolution via its multi-master replication, and provides a serverless capacity mode that automatically scales based on demand, making it ideal for unpredictable traffic.

Exam trap

The trap here is that candidates often confuse Azure Table Storage as a NoSQL database that supports multi-region writes, but it lacks document support and automatic conflict resolution, making Cosmos DB the only option that meets all requirements.

How to eliminate wrong answers

Option A is wrong because Azure Table Storage is a key-value store but does not support a document data model, lacks multi-region writes with automatic conflict resolution, and does not offer a serverless capacity option (it uses provisioned throughput). Option C is wrong because Azure Cache for Redis is an in-memory caching service, not a fully managed NoSQL database; it does not natively support document data models or multi-region writes with conflict resolution. Option D is wrong because Azure SQL Database is a relational database (SQL-based), not a NoSQL database, and does not support key-value or document data models natively, nor does it offer multi-region writes with automatic conflict resolution.

Practice this question →

153

MCQhard

You are designing a data storage solution for an IoT application that ingests millions of events per second. Each event is a small JSON message (under 1 KB). The solution must support real-time analytics and allow queries on recent data (last 24 hours) with low latency. Historical data (older than 24 hours) should be stored in a cost-optimized manner for occasional compliance queries. Which combination of Azure services should you recommend?

A.Azure Cosmos DB for both real-time and historical data

B.Azure Event Hubs for ingestion and Azure Functions for querying

C.Azure SQL Database with elastic pool

D.Azure Data Explorer for real-time analytics and Azure Blob Storage for historical data

AnswerD

Azure Data Explorer is a fast, fully managed analytics database specifically designed for querying large volumes of time-series and log data, with built-in high-throughput ingestion from sources like Event Hubs and low-latency queries for real-time dashboards. For historical data, Azure Blob Storage provides economical, tiered object storage that retains massive data volumes at a fraction of the cost, enabling that data to be rehydrated or queried on demand via technologies like Synapse or ADX’s external table feature. This architecture cleanly separates the hot path for interactive real-time analysis from the cold path for long-term retention, satisfying both performance and cost constraints.

Why this answer

Azure Data Explorer (ADX) is purpose-built for real-time analytics on high-velocity data streams, ingesting millions of events per second with sub-second query latency on recent data. Azure Blob Storage provides a cost-optimized tier (e.g., Cool or Archive) for historical data older than 24 hours, which can be queried occasionally via ADX’s continuous export or external table feature. This combination meets both the low-latency real-time analytics requirement and the cost-effective long-term storage need.

Exam trap

The trap here is that candidates often confuse high-throughput ingestion with query capability, assuming that any service that can ingest data (like Event Hubs) can also serve real-time queries, or that a general-purpose database (like Cosmos DB or SQL Database) can handle the extreme volume and analytics pattern of IoT telemetry.

How to eliminate wrong answers

Option A is wrong because Azure Cosmos DB, while fast for transactional workloads, is not optimized for high-throughput ingestion of millions of events per second for real-time analytics; its per-request cost and indexing overhead would be prohibitive for this volume, and it lacks native time-series analytics capabilities. Option B is wrong because Azure Event Hubs is an ingestion service, not a query engine; Azure Functions are stateless and unsuitable for low-latency ad-hoc queries over terabytes of recent data, and they cannot efficiently handle the querying requirement. Option C is wrong because Azure SQL Database with elastic pool cannot ingest millions of events per second due to connection and transaction limits, and its cost for storing and querying high-volume time-series data would be excessive compared to purpose-built solutions.

Practice this question →

154

MCQmedium

Your company is migrating a critical on-premises database to Azure SQL Managed Instance. The database is 500 GB and requires minimal downtime during migration. You need to choose the best migration approach. What should you recommend?

A.Use the export/import bacpac method.

B.Use Azure Data Factory to copy data.

C.Use transactional replication.

D.Use Azure Database Migration Service with online migration.

AnswerD

Azure Database Migration Service with online migration is the correct choice because it performs an initial full copy of the schema and data, then uses a continuous replication stream to keep the target synchronized with the source as transactions occur. It supports a controlled cutover where you can validate the target, stop writes on the source, and switch applications with near-zero downtime. DMS automates the heavy lifting, handles large databases like 500 GB, and is designed specifically for minimal-downtime migrations to Azure SQL, eliminating the need for manual log shipping or custom replication code.

Why this answer

Azure Database Migration Service (DMS) with online migration is the correct choice because it supports minimal downtime by continuously replicating changes from the source SQL Server to Azure SQL Managed Instance using a log-based change capture mechanism. This allows you to cut over to the target with only a brief pause, meeting the critical requirement for a 500 GB database.

Exam trap

The trap here is that candidates often confuse transactional replication (Option C) with a managed migration service, but DMS is the purpose-built Azure tool for online migrations with minimal downtime, whereas replication requires more manual configuration and is not optimized for one-time migrations.

How to eliminate wrong answers

Option A is wrong because the export/import bacpac method is an offline process that exports the database schema and data to a .bacpac file, which requires the database to be quiesced or taken offline, causing significant downtime for a 500 GB database. Option B is wrong because Azure Data Factory is designed for bulk data movement and orchestration, not for live transactional replication with minimal downtime; it would require a full copy and cannot handle ongoing changes without complex custom logic. Option C is wrong because transactional replication requires manual setup of publishers, distributors, and subscribers, and while it can provide near-real-time synchronization, it is not a managed migration service and does not handle the full schema and data migration as seamlessly as DMS, often requiring additional steps to ensure consistency.

Practice this question →

155

MCQeasy

You need to store billions of small JSON files (average 50 KB) that are accessed infrequently but must be available within seconds when requested. Which Azure storage solution is most cost-effective?

A.Azure SQL Database with a table storing JSON

B.Azure Files with SMB shares

C.Azure Blob Storage Cool tier

D.Azure Cosmos DB with a container for each file

AnswerC

Azure Blob Storage Cool tier is purpose-built for massive, flat namespace object storage where a single account can hold trillions of blobs. Its storage cost per GB is significantly lower than hot tier, SQL Database, or Cosmos DB, and the access latency remains low enough to serve 50 KB JSON objects on demand. While Cool tier carries a minimum retention period and early-delete fee, for infrequently accessed small files it is the most cost-effective and scalable choice among the options.

Why this answer

Azure Blob Storage Cool tier is the most cost-effective solution for storing billions of small JSON files (average 50 KB) that are infrequently accessed but require low-latency retrieval within seconds. The Cool tier offers low storage costs for data accessed less than once per month, while still providing sub-second access latency for individual blobs via HTTPS REST API, matching the 'available within seconds' requirement without the higher costs of Hot or premium tiers.

Exam trap

The trap here is that candidates often choose Azure Cosmos DB (Option D) because of its low-latency guarantees, but they overlook the massive cost difference for storing billions of small files, where Blob Storage's object storage model is far more economical for infrequently accessed data.

How to eliminate wrong answers

Option A is wrong because Azure SQL Database is a relational database optimized for transactional queries and structured data, not for storing billions of individual small files; storing each JSON file as a row would incur high storage costs (minimum 1 MB per row for LOB data) and poor performance for file-level retrieval. Option B is wrong because Azure Files with SMB shares is designed for shared file systems with SMB protocol overhead and is not optimized for billions of small files; it incurs higher costs per GB than Blob Storage and lacks native support for efficient bulk operations on individual small objects. Option D is wrong because Azure Cosmos DB is a NoSQL database optimized for low-latency queries and real-time access with high throughput, but its cost per GB of storage is significantly higher than Blob Storage (often 10x or more), making it prohibitively expensive for storing billions of small files that are accessed infrequently.

Practice this question →

156

MCQmedium

A company runs a SQL Server database on an Azure virtual machine in a single region. They need to increase storage capacity and improve I/O performance for their transaction-intensive workload. They also want to ensure high availability within the same datacenter (99.99% SLA). What should they do?

A.Use Azure Premium SSD v2 managed disks in a storage pool with mirroring across multiple disks.

B.Use Azure Ultra Disk storage attached to the VM.

C.Deploy the SQL Server on an availability set and use Storage Spaces Direct with multiple disks.

D.Enable Azure SQL Managed Instance with auto-failover groups.

AnswerC

Correct. Deploying SQL Server on an availability set ensures multiple VMs are in separate fault domains and update domains, achieving 99.99% SLA. Storage Spaces Direct pools multiple disks across VMs, providing both increased capacity and I/O performance through mirroring, while also offering data redundancy.

Why this answer

To achieve 99.99% availability within a single datacenter, you need multiple VMs in an availability set. Option C combines an availability set with Storage Spaces Direct (S2D), which uses multiple disks across VMs to provide both performance (through disk pooling) and high availability (via mirroring). This meets all requirements: increased storage capacity, improved I/O performance, and 99.99% SLA.

Option A only addresses disk performance and redundancy but fails to provide VM-level redundancy, which is necessary for the SLA.

Exam trap

Candidates often think that simply using high-performance disks (like Premium SSD v2 or Ultra Disk) is sufficient for the SLA. However, the 99.99% SLA requires multiple VMs in an availability set. Storage Spaces Direct with availability set provides both performance and HA within a datacenter.

How to eliminate wrong answers

Option B is wrong because Azure Ultra Disk storage, while offering extremely low latency and high IOPS, does not natively support mirroring or striping across multiple disks in a storage pool to increase capacity and I/O simultaneously; it is typically used as a single disk and does not provide the same aggregated performance and redundancy as a mirrored pool. Option C is wrong because Storage Spaces Direct is designed for on-premises or Azure Stack HCI scenarios, not for Azure VMs; it cannot be used with Azure managed disks and would not be supported in a standard Azure VM deployment. Option D is wrong because Azure SQL Managed Instance with auto-failover groups is a PaaS solution that moves the workload off the VM, which does not address the requirement to increase storage capacity and I/O performance for the existing SQL Server on an Azure VM, and it introduces a different architecture and SLA model.

Practice this question →

157

MCQmedium

A global e-commerce company stores product catalog data in a JSON document format. The application requires low-latency reads and writes from multiple geographic regions. The solution must support multi-region writes with automatic conflict resolution and provide a guaranteed 99th percentile latency. Which Azure Cosmos DB API and consistency level should they choose?

A.SQL API with Session consistency

B.Table API with Eventual consistency

C.SQL API with Strong consistency

D.MongoDB API with Bounded staleness consistency

AnswerA

The SQL API is Cosmos DB's native JSON document data plane, making it the natural fit for product catalog records which are typically nested JSON objects with varying attributes. Session consistency is the default and most widely used consistency level because it gives each client a read-your-writes guarantee with low, predictable latency; this is exactly what an e-commerce session needs when a user updates their cart or profile. It avoids the overhead of strong consistency while preventing users from seeing inconsistent views of their own actions.

Why this answer

The SQL API with Session consistency is correct because it supports multi-region writes with automatic conflict resolution using last-writer-wins (LWW) and provides a guaranteed 99th percentile latency. Session consistency is the most widely used level for globally distributed applications, offering read-your-writes guarantees while maintaining low latency across regions.

Exam trap

The trap here is that candidates often assume Strong consistency is required for low-latency multi-region writes, but Strong consistency is incompatible with multi-region writes and would actually increase latency, while Session consistency provides the right balance of performance and guarantees.

How to eliminate wrong answers

Option B (Table API with Eventual consistency) is wrong because the Table API does not support multi-region writes; it only supports single-region writes with multi-region reads. Option C (SQL API with Strong consistency) is wrong because Strong consistency cannot be used with multi-region writes; it is only supported in single-region write configurations and would introduce high latency across regions. Option D (MongoDB API with Bounded staleness consistency) is wrong because Bounded staleness consistency, while supporting multi-region writes, does not guarantee a specific 99th percentile latency due to the configurable staleness window (k or t), which can introduce unpredictable delays.

Practice this question →

158

Multi-Selecthard

Which THREE of the following are best practices for designing an Azure SQL Database solution for performance and scalability?

Select 3 answers

A.Use appropriate indexes to optimize query performance

B.Use elastic pools to manage multiple databases with variable workloads

C.Implement read replicas for read-heavy workloads

D.Avoid using stored procedures to reduce complexity

E.Disable automatic tuning to maintain consistent performance

AnswersA, B, C

Indexes are data structures that enable the query engine to locate rows using seek operations instead of full table scans. Appropriate indexes tailored to the workload's predicates, joins, and ordering can reduce I/O and CPU while improving response times. However, they must be balanced against write overhead and storage costs, so they should be designed rather than added indiscriminately.

Why this answer

Appropriate indexes, such as clustered and nonclustered indexes, reduce the number of data pages scanned during query execution, directly improving query performance. In Azure SQL Database, index tuning is critical for minimizing I/O and CPU overhead, especially for large tables or complex joins.

Exam trap

The trap here is that candidates may mistakenly think stored procedures add complexity or that disabling automatic tuning ensures consistency, when in fact both practices hinder scalability and performance in Azure SQL Database's managed environment.

Practice this question →

159

MCQmedium

A company wants to cache frequently accessed session state and product data for their e-commerce website. They need the cache to be highly available with a 99.9% SLA and provide fast read and write access. The solution must be fully managed. Which Azure Cache tier should they choose?

A.Azure Redis Cache Basic tier

B.Azure Redis Cache Standard tier

C.Azure Redis Cache Premium tier

D.Azure Content Delivery Network

AnswerB

Azure Redis Cache Standard tier is a fully managed in-memory cache that runs on two replicas in the same datacenter, with automatic failover and a 99.9% SLA. For session state and frequently accessed product data, this replication provides the required high availability while keeping the architecture simple and cost-effective. It also supports standard Redis features such as expiration policies and cache-aside patterns, making it a natural fit for stateless web front ends that need a resilient shared state store.

Why this answer

The Standard tier of Azure Redis Cache provides a 99.9% SLA through built-in replication with two nodes (primary and replica) in the same region, ensuring high availability. It is fully managed, supports fast read/write access for session state and product data, and meets the requirement without the additional cost or complexity of the Premium tier.

Exam trap

The trap here is that candidates often choose the Premium tier for high availability, not realizing that the Standard tier already provides a 99.9% SLA with replication, and Premium adds features like data persistence and clustering that are not required by the question.

How to eliminate wrong answers

Option A is wrong because the Basic tier has no SLA (0% SLA) and no replication, making it unsuitable for high availability requirements. Option C is wrong because the Premium tier, while offering higher performance and features like persistence and clustering, is overkill for the stated requirements and incurs unnecessary cost; the Standard tier already meets the 99.9% SLA and fast access needs. Option D is wrong because Azure Content Delivery Network is a caching solution for static content delivery at edge locations, not a low-latency, fully managed cache for dynamic session state and product data; it does not provide the read/write semantics required for session state.

Practice this question →

160

MCQmedium

You are designing a hybrid storage solution where on-premises applications need low-latency access to file shares hosted in Azure. The solution must cache frequently accessed files locally and sync changes bidirectionally. Which Azure feature should you use?

A.Azure File Sync

B.Azure Data Box

C.Azure NetApp Files with ExpressRoute

D.Azure Blob Storage with Azure Files migration

AnswerA

Azure File Sync is the correct choice for a hybrid storage solution that requires ongoing, bidirectional synchronization. It installs an agent on your on-premises Windows Server, creates a local cache, and continuously syncs changes both to and from an Azure file share. This gives you local performance for active files while maintaining a cloud copy for disaster recovery, multi-site replication, and backup. Its cloud tiering policy also optimizes local storage capacity by automatically moving cold files to Azure and leaving placeholders.

Why this answer

Azure File Sync is the correct choice because it enables bidirectional syncing of Azure file shares with on-premises Windows Servers, caching frequently accessed files locally for low-latency access while automatically syncing changes back to Azure. This meets the hybrid requirement of local caching and bidirectional sync without requiring full migration or dedicated network circuits.

Exam trap

The trap here is that candidates confuse Azure NetApp Files with ExpressRoute as a caching solution, but ExpressRoute only improves network latency and reliability—it does not provide local caching or bidirectional sync, which are core requirements of the scenario.

How to eliminate wrong answers

Option B is wrong because Azure Data Box is a physical data transfer device for bulk offline migration, not a continuous caching or bidirectional sync solution. Option C is wrong because Azure NetApp Files with ExpressRoute provides high-performance NFS/SMB volumes but does not include built-in bidirectional caching or sync with on-premises file servers; it requires separate replication tools. Option D is wrong because Azure Blob Storage with Azure Files migration is a one-time migration path, not a hybrid caching and sync service; Blob Storage itself does not support SMB file shares or bidirectional sync natively.

Practice this question →

161

MCQeasy

Your company has a large number of unstructured files (images, videos) that need to be stored cost-effectively in Azure. The data is accessed infrequently but must be available within minutes when needed. Which storage tier should you recommend?

A.Premium tier.

B.Archive tier.

C.Cool tier.

D.Hot tier.

AnswerC

The Cool tier is an online access tier intended for data that is infrequently accessed (a few times a month) but must be available immediately on demand. It offers lower storage costs and lower write/read transaction costs than Hot, allowing you to store many images economically while still supporting low-latency reads that can complete within milliseconds. Because there is no rehydration step, images are directly readable, and the 30-day minimum retention period aligns with typical lifecycle policies for images that are rarely accessed but need to be available.

Why this answer

The Cool tier is designed for data that is infrequently accessed but requires immediate availability when needed. It offers lower storage costs than the Hot tier while maintaining low-latency access (within minutes), making it ideal for unstructured files like images and videos that are accessed rarely but must be retrievable on demand.

Exam trap

The trap here is that candidates often confuse the Archive tier's low storage cost with immediate availability, overlooking the mandatory rehydration latency that violates the 'within minutes' requirement.

How to eliminate wrong answers

Option A is wrong because the Premium tier is optimized for high-performance, low-latency access (sub-millisecond) and is intended for active workloads, not cost-effective storage of infrequently accessed data. Option B is wrong because the Archive tier has the lowest storage cost but requires a rehydration process that can take up to 15 hours (Standard tier) or 1-5 hours (High Priority tier), failing the 'available within minutes' requirement. Option D is wrong because the Hot tier is designed for frequently accessed data with higher storage costs, making it unsuitable for infrequently accessed files where cost optimization is a priority.

Practice this question →

162

MCQmedium

A media company stores large video files that are accessed once a month for audits. When needed, they must be available for download immediately (within seconds). The company wants to minimize storage costs. Which Azure Blob Storage access tier should they use?

A.Hot tier

B.Cool tier

C.Cold tier

D.Archive tier

AnswerB

Cool tier offers a low per-GB storage price with a modest per-GB retrieval fee and a 30-day minimum retention period, which aligns perfectly with monthly access. Retrieval is immediate because objects remain in the online tier, so the media company can read or stream the video without waiting for rehydration. For large files read once per month, Cool delivers the lowest total cost among tiers that still provide on-demand access, making it the correct choice.

Why this answer

The Cool tier is optimal for this scenario because it balances low storage cost with high availability and low latency access. Video files accessed once a month for audits require immediate download (within seconds), which Cool tier supports with the same millisecond latency as Hot tier, but at a lower storage price. Archive tier would introduce a multi-hour rehydration delay, making it unsuitable for on-demand access within seconds.

Exam trap

The trap here is that candidates often choose Archive tier for infrequent access without realizing that the multi-hour rehydration latency makes it impossible to meet the 'within seconds' availability requirement, or they choose Hot tier out of habit for any access speed requirement, ignoring the cost-minimization goal.

How to eliminate wrong answers

Option A (Hot tier) is wrong because it has the highest storage cost, which contradicts the goal of minimizing storage costs for infrequently accessed data. Option C (Cold tier) is wrong because although it offers lower storage cost than Cool, it has a higher minimum storage duration (90 days vs 30 days) and a higher early deletion fee, making it more expensive for data accessed only once a month. Option D (Archive tier) is wrong because it requires a rehydration process that takes up to 15 hours, making it impossible to provide download within seconds on demand.

Practice this question →

163

MCQeasy

Your company uses Azure SQL Database and needs to retain backups for 7 years for compliance. Which backup retention policy should you configure?

A.Increase automated backup retention to 7 years.

B.Configure point-in-time restore backup retention for 7 years.

C.Enable geo-redundant backups.

D.Configure long-term retention (LTR) backup policy.

AnswerD

Configuring a long-term retention (LTR) backup policy is the correct approach for retaining backups beyond 35 days. LTR allows you to define separate retention periods for weekly, monthly, and yearly full backups, with a maximum retention of 10 years. These backups are stored in Azure Blob storage (geo-redundant by default) and are independent of automated backup and PITR retention limits. For a 7-year retention requirement, you can specify a yearly LTR policy with a 7-year retention period.

Why this answer

Azure SQL Database's automated backup retention is limited to a maximum of 35 days, which is insufficient for a 7-year compliance requirement. Long-term retention (LTR) allows you to retain full database backups for up to 10 years by storing them in separate Azure Blob Storage containers. Therefore, configuring an LTR backup policy is the correct solution for meeting a 7-year retention mandate.

Exam trap

The trap here is that candidates often confuse the maximum retention for automated backups (35 days) with the ability to extend it arbitrarily, or they mistakenly think point-in-time restore retention can be configured for years, when in reality only long-term retention (LTR) supports multi-year archival.

How to eliminate wrong answers

Option A is wrong because Azure SQL Database automated backup retention has a maximum of 35 days, not 7 years; you cannot increase it beyond that limit. Option B is wrong because point-in-time restore (PITR) backup retention is also capped at 35 days and is designed for short-term recovery, not long-term archival compliance. Option C is wrong because enabling geo-redundant backups (e.g., geo-redundant storage) provides disaster recovery protection by replicating backups to a paired region, but it does not extend the retention period beyond the default 35 days.

Practice this question →

164

MCQeasy

A company needs to store millions of small JSON files (average 10 KB each) for a serverless application. The data must be accessed via HTTPS and support high read throughput. Which Azure storage solution is most cost-effective?

A.Azure Blob Storage (general-purpose v2, hot tier)

B.Azure Files (standard)

C.Azure Cosmos DB

D.Azure Table Storage

AnswerA

Azure Blob Storage (general-purpose v2) is purpose-built for storing massive numbers of small, unstructured objects like JSON files. It exposes a REST API over HTTPS, allows per-blob metadata and tags, and supports hot/cool/archive lifecycle management. The hot tier optimizes for frequent reads, making it both cost-effective and highly scalable for millions of entries.

Why this answer

Azure Blob Storage (general-purpose v2, hot tier) is the most cost-effective solution because it provides native HTTPS access, high throughput for read-heavy workloads, and low-cost storage for small objects like JSON files. The hot tier optimizes for frequent access, and GPv2 accounts support the high request rates needed for millions of small files without premium pricing.

Exam trap

The trap here is that candidates often choose Azure Cosmos DB for JSON files due to its native JSON support, but they overlook the cost inefficiency of using a transactional database for static file storage, where blob storage provides the same HTTPS access at a fraction of the cost.

How to eliminate wrong answers

Option B (Azure Files) is wrong because it is designed for SMB/NFS file shares with mounted drives, not for direct HTTPS access to individual small objects, and its cost per GB is higher than blob storage for this use case. Option C (Azure Cosmos DB) is wrong because it is a NoSQL database optimized for transactional workloads with low-latency queries, not for bulk storage of static JSON files, and its RU-based pricing would be prohibitively expensive for millions of small files with high read throughput. Option D (Azure Table Storage) is wrong because it is a NoSQL key-value store for structured data with partition key limitations, not designed for storing raw JSON files as blobs, and its throughput is constrained by partition scalability.

Practice this question →

165

MCQhard

You are designing a data storage solution for a global e-commerce platform that handles millions of transactions per day. The platform uses Azure Cosmos DB for its transactional data. The company wants to implement a real-time analytics pipeline to monitor sales trends and detect anomalies. The analytics must be performed on the transactional data with minimal latency (under 5 seconds). The solution must not impact the transactional workload's performance. The analytics queries involve aggregations over time windows and joins with reference data stored in Azure SQL Database. You need to recommend a solution. Which option should you choose?

A.Enable Azure Synapse Link for Cosmos DB and use Synapse serverless SQL to query the transactional data directly.

B.Use Azure Data Factory to copy data from Cosmos DB to Azure Synapse Analytics every minute, and run analytics queries in Synapse.

C.Use Azure Cosmos DB change feed to stream data to Azure Stream Analytics, which performs the aggregations and joins with reference data from Azure SQL Database.

D.Use Azure Databricks with Auto Loader to incrementally load data from Cosmos DB into Delta Lake, and then query with Spark SQL.

AnswerC

The Cosmos DB change feed emits each insert, update, and delete in real time, allowing Azure Stream Analytics to ingest the stream directly via the Cosmos DB connector. Stream Analytics can perform tumbling or hopping window aggregations and join the streaming events with reference data loaded from Azure SQL Database (using a reference input) at sub-second latency, making it the only option that satisfies both the 5-second SLA and the need for real-time joins against look-up data.

Why this answer

Azure Cosmos DB change feed enables real-time streaming of transactional data to Azure Stream Analytics, which can perform low-latency aggregations and joins with reference data from Azure SQL Database without impacting the transactional workload. This architecture meets the sub-5-second latency requirement and avoids any direct query load on Cosmos DB.

Exam trap

The trap here is that candidates often choose Azure Synapse Link (Option A) thinking it provides real-time analytics, but they overlook that Synapse Link's analytical store is refreshed asynchronously (typically every 1-5 minutes) and serverless SQL queries add additional latency, making it unsuitable for sub-5-second requirements.

How to eliminate wrong answers

Option A is wrong because Azure Synapse Link for Cosmos DB uses analytical store and serverless SQL, which is designed for near-real-time analytics but typically incurs higher latency (often >5 seconds) due to the time required to populate the analytical store and the overhead of querying large transactional datasets directly. Option B is wrong because Azure Data Factory copying data every minute introduces at least 60 seconds of latency, far exceeding the 5-second requirement, and the copy process can impact the transactional workload's performance. Option D is wrong because Azure Databricks with Auto Loader is optimized for batch or micro-batch processing, not true real-time streaming, and the incremental load from Cosmos DB would add latency beyond 5 seconds while also requiring complex orchestration to avoid impacting the source.

Practice this question →

166

MCQhard

A company stores petabytes of sensor data in Azure Data Lake Storage Gen2. They need to run complex analytics queries that involve joining multiple datasets and aggregating time-series data. The queries must complete within seconds. Which Azure service should they use for querying?

A.Azure Stream Analytics

B.Azure Data Explorer

C.Azure Synapse Analytics

D.Azure Databricks

AnswerC

Azure Synapse Analytics is the correct choice because it combines a massively parallel processing (MPP) SQL engine with direct query access to data stored in Azure Data Lake Storage through both dedicated SQL pools and serverless SQL, enabling fast interactive T-SQL queries over petabyte volumes. Its dedicated pool distributes rows across 60 compute nodes with columnstore indexes, while serverless provides per-query billing without provisioning. This architecture supports complex joins, aggregations, and BI reporting at the scale and concurrency expected from a data warehouse, making it the best fit for the sensor data lake.

Why this answer

Azure Synapse Analytics (Option C) is correct because it provides a unified analytics platform that can directly query petabyte-scale data in Azure Data Lake Storage Gen2 using T-SQL or Spark, and its distributed query engine (PolyBase or Synapse SQL) can perform complex joins and time-series aggregations with sub-second response times when combined with appropriate indexing and materialized views.

Exam trap

The trap here is that candidates often confuse Azure Data Explorer (Option B) as the best choice for time-series data, but the question specifies complex joins across multiple datasets and direct querying of Data Lake Storage Gen2, which Synapse handles natively while Data Explorer requires data ingestion and is not designed for multi-table joins at petabyte scale.

How to eliminate wrong answers

Option A is wrong because Azure Stream Analytics is a real-time stream processing service designed for low-latency queries on streaming data, not for complex ad-hoc analytics on petabytes of stored historical data in Data Lake Storage Gen2. Option B is wrong because Azure Data Explorer is optimized for interactive analytics on large volumes of time-series and log data, but it requires data to be ingested into its own storage engine, not directly querying Data Lake Storage Gen2, and it lacks the full T-SQL and Spark capabilities needed for complex joins across multiple datasets. Option D is wrong because Azure Databricks is a big data analytics platform using Apache Spark, which can handle complex queries but typically requires data to be loaded into Spark DataFrames or tables, and it may not achieve consistent sub-second query completion without significant optimization and caching, unlike Synapse's dedicated SQL pool or serverless SQL.

Practice this question →

167

Multi-Selecthard

Which THREE factors should you consider when selecting a partition key for an Azure Cosmos DB container? (Select three.)

Select 3 answers

A.Even distribution of request unit (RU) consumption

B.Low cardinality to reduce overhead

C.High cardinality (many distinct values)

D.Property with large binary data

E.Property frequently used as a filter in queries

AnswersA, C, E

An effective partition key must result in a relatively even distribution of request unit (RU) consumption across all logical partitions, not just a high number of distinct values. If a particular key value receives a disproportionate share of reads or writes, the physical partition hosting it becomes hot and triggers throttling (HTTP 429) for that traffic. Therefore, when evaluating candidate keys, you should model the expected workload and confirm that no single key value accounts for an excessive fraction of the total RU spend.

Why this answer

An even distribution of request unit (RU) consumption across physical partitions prevents hot partitions, which can throttle throughput and degrade performance. In Azure Cosmos DB, the partition key determines how data and throughput are distributed; if RU consumption is skewed, some partitions become overloaded while others remain underutilized, violating the design goal of uniform load.

Exam trap

The trap here is that candidates confuse low cardinality with efficiency, but Cosmos DB requires high cardinality to avoid storage limits and hot partitions, and they may also mistakenly think large binary properties are acceptable partition keys despite the 2 KB limit and indexing overhead.

Practice this question →

168

Multi-Selectmedium

You are designing a data storage solution for a multi-tenant SaaS application. Each tenant's data must be isolated and encrypted with a tenant-specific key. The solution must support automatic key rotation and the ability to revoke a tenant's access immediately by disabling their key. The data will be stored in Azure Blob Storage. Which two actions should you include in your design? (Choose two.)

Select 2 answers

A.Create a separate Azure Key Vault for each tenant and store the tenant's customer-managed key in that vault.

B.Use Azure Disk Encryption with BitLocker for each tenant's virtual machine disks.

C.Configure Azure Blob Storage encryption scopes, each using a tenant-specific customer-managed key from the tenant's Key Vault.

D.Store all tenant data in a single container and use a single customer-managed key stored in Azure Key Vault Managed HSM.

E.Enable Azure Storage Service Encryption with Microsoft-managed keys and use Azure Policy to enforce per-tenant encryption.

AnswersA, C

Using a separate Azure Key Vault per tenant provides strong isolation of keys. Each tenant's key is stored in its own vault, and you can disable the key in that vault to immediately revoke access to that tenant's data. This also simplifies key management and auditing per tenant. Azure Blob Storage supports customer-managed keys from a Key Vault, and you can configure each storage account or encryption scope to use a specific key.

Why this answer

The requirements are per-tenant encryption with tenant-specific keys, automatic key rotation, and immediate revocation by disabling a key. Creating a separate Key Vault per tenant and using encryption scopes in Blob Storage that reference those keys achieves this. Encryption scopes allow different containers or blobs to be encrypted with different keys, and disabling a key in Key Vault immediately blocks access to data encrypted with that key.

This design provides strong isolation and meets all requirements.

Exam trap

The trap here is assuming that a single key with access policies can provide per-tenant isolation; revoking one tenant's access would affect all tenants if they share a key.

Practice this question →

169

MCQeasy

A company stores sensitive customer data in Azure Blob Storage. They need to ensure that data at rest is encrypted using a customer-managed key stored in Azure Key Vault. Which of the following should they use?

A.Azure Storage Service Encryption with customer-managed keys in Azure Key Vault

B.Azure Disk Encryption

C.Azure Storage Service Encryption with Microsoft-managed keys

D.Azure Information Protection

AnswerA

Azure Storage Service Encryption (SSE) is enabled by default for all Azure Storage accounts, including Blob Storage, encrypting data at rest before it is persisted to disk. By specifying customer-managed keys (CMK) in Azure Key Vault, you take ownership of the encryption key lifecycle — including rotation, versioning, and revocation — rather than relying on Microsoft-held keys. This also enables auditability of key usage via Key Vault logs, and can be integrated with Azure Policy to enforce CMK across subscriptions. For a scenario requiring customer-managed encryption for sensitive customer data in Blob Storage, SSE with CMK is the appropriate mechanism.

Why this answer

Azure Storage Service Encryption (SSE) encrypts data at rest in Azure Blob Storage. When configured with customer-managed keys (CMK) stored in Azure Key Vault, the customer controls the encryption key lifecycle, including rotation and revocation, meeting the requirement for customer-managed key control. This is the only option that directly applies to Blob Storage data at rest with CMK support.

Exam trap

The trap here is that candidates confuse Azure Disk Encryption (which encrypts VM disks) with Azure Storage Service Encryption (which encrypts Blob Storage data), leading them to select the wrong service for the given scenario.

How to eliminate wrong answers

Option B is wrong because Azure Disk Encryption encrypts OS and data disks of virtual machines, not Azure Blob Storage data. Option C is wrong because it uses Microsoft-managed keys, not customer-managed keys as required. Option D is wrong because Azure Information Protection is a classification and labeling solution for documents and emails, not an encryption mechanism for data at rest in Blob Storage.

Practice this question →

170

MCQmedium

A global e-commerce company runs a product catalog application that requires low-latency reads and writes from multiple geographic regions. The data is key-value structured and must be replicated with multi-region write capability. The company needs a fully managed NoSQL database service with guaranteed 99th percentile latency and automatic conflict resolution. Which Azure data service should they choose?

A.Azure Cosmos DB

B.Azure Table Storage

C.Azure Redis Cache

D.Azure SQL Database

AnswerA

Azure Cosmos DB is a globally distributed NoSQL database engineered for product-catalog workloads that require active-active writes across multiple Azure regions. It supports a choice of APIs (SQL, MongoDB, Cassandra, etc.), and with multi-region writes it provides automatic conflict resolution, turnkey global distribution, and deterministic 99th-percentile latency SLAs. For an ecommerce catalog, Cosmos DB's partition-key design and tunable consistency levels allow low-latency reads and writes at scale while meeting a strict SLO.

Why this answer

Azure Cosmos DB is the correct choice because it is a fully managed NoSQL database that supports multi-region writes with automatic conflict resolution, guarantees 99th percentile latency, and provides low-latency reads and writes globally. Its multi-master replication and tunable consistency models meet the key-value structured data requirements and the need for high availability across geographic regions.

Exam trap

The trap here is that candidates may confuse Azure Table Storage's NoSQL nature with Cosmos DB's multi-region write and latency guarantees, overlooking the critical requirements for automatic conflict resolution and 99th percentile latency SLAs.

How to eliminate wrong answers

Option B is wrong because Azure Table Storage is a NoSQL key-value store but does not support multi-region write capability or automatic conflict resolution, and it lacks guaranteed 99th percentile latency SLAs. Option C is wrong because Azure Redis Cache is an in-memory data store, not a fully managed NoSQL database, and it does not provide multi-region write replication or automatic conflict resolution for persistent data. Option D is wrong because Azure SQL Database is a relational database, not a NoSQL key-value store, and it does not natively support multi-region writes with automatic conflict resolution.

Practice this question →

171

MCQmedium

You are the Azure architect for a healthcare organization that needs to store patient medical records (unstructured data) and provide secure access to doctors and nurses via a web application. The data must be encrypted at rest and in transit. Access must be authorized based on the requester's role (doctor, nurse, admin). The solution must be cost-effective and support high concurrency. You decide to use Azure Blob Storage. You need to design the access control mechanism. What should you recommend?

A.Enable storage service encryption and use HTTPS.

B.Use shared access signatures (SAS) with stored access policies.

C.Use Azure RBAC with Microsoft Entra ID authentication.

D.Use storage account access keys and distribute them to users.

AnswerC

Azure RBAC with Microsoft Entra ID authentication assigns built-in or custom roles scoped to the storage account or container, so doctors, nurses and admins receive permissions matching their role. This satisfies the stem's role-based authorisation requirement while remaining cost-effective and supporting high concurrency.

Why this answer

Use Azure RBAC with Microsoft Entra ID authentication. Azure RBAC (Role-Based Access Control) integrated with Microsoft Entra ID (formerly Azure AD) allows you to assign permissions to users based on their roles (e.g., doctor, nurse, admin) for fine-grained access to Blob Storage. This meets the requirement for role-based authorization without managing separate keys or tokens.

Option A is incorrect because encryption at rest and HTTPS only address data protection, not access control. Option B is incorrect because shared access signatures (SAS) grant time-limited access to specific resources but are not tied to user roles. Option D is incorrect because storage account access keys provide full administrative access to the entire storage account, not role-based permissions.

Practice this question →

172

MCQeasy

A startup is building a new mobile app backend. They need a fully managed relational database service with built-in high availability, automatic backups, and built-in intelligence to optimize performance. They want to minimize administrative overhead for tasks like patching and scaling. Which Azure service should they use?

A.Azure SQL Database

B.SQL Server on Azure Virtual Machines

C.Azure Database for MySQL

D.Azure Cosmos DB

AnswerA

Azure SQL Database is the correct choice because it is a fully managed Platform-as-a-Service relational database that eliminates patching, backups, and high-availability configuration. Its built-in intelligent query optimization, automatic tuning, and geo-replication capabilities align directly with the requirement for a fully managed backend. You simply provision the logical server and database, and Azure handles infrastructure redundancy, automated backups with point-in-time restore, and a 99.99% SLA, freeing your team to focus on application development.

Why this answer

Azure SQL Database is a fully managed Platform-as-a-Service (PaaS) relational database that includes built-in high availability (99.99% SLA), automatic backups with point-in-time restore, and built-in intelligence features like automatic tuning, adaptive query processing, and intelligent insights. This minimizes administrative overhead for patching, scaling, and performance optimization, making it ideal for a startup that wants to focus on app development rather than database management.

Exam trap

The trap here is that candidates often confuse 'fully managed' with 'IaaS' or pick Azure Database for MySQL because it is also fully managed, but they overlook the specific requirement for 'built-in intelligence to optimize performance,' which is a hallmark of Azure SQL Database's automatic tuning features, not available in Azure Database for MySQL.

How to eliminate wrong answers

Option B is wrong because SQL Server on Azure Virtual Machines is an Infrastructure-as-a-Service (IaaS) offering that requires you to manage patching, backups, high availability setup (e.g., Always On Availability Groups), and scaling manually, increasing administrative overhead. Option C is wrong because Azure Database for MySQL is a fully managed relational database, but it lacks the built-in intelligence features (e.g., automatic tuning, intelligent insights) that Azure SQL Database provides, and the question specifically asks for 'built-in intelligence to optimize performance.' Option D is wrong because Azure Cosmos DB is a NoSQL database (supporting document, key-value, graph, and column-family models), not a relational database, and it does not use SQL as its primary query language (though it has a SQL API, it is not a relational database engine).

Practice this question →

173

MCQeasy

A company wants to store application configuration settings and secrets (e.g., database connection strings, API keys) securely with automatic rotation. Access must be controlled and audited. Which Azure service should they use?

A.Azure Key Vault

B.Azure App Configuration

C.Azure Storage Queues

D.Azure Service Bus

AnswerA

Azure Key Vault is a specialized cloud service for securely storing and controlling access to secrets, encryption keys, and certificates. It uses Azure Active Directory authentication and fine-grained access policies to govern who can read or modify secret versions, and it natively integrates with Azure services (e.g., App Service) via Key Vault references for automatic secret rotation with zero downtime. It also provides audit logging, soft-delete, and purge protection, making it the only option here designed specifically for secrets management.

Why this answer

Azure Key Vault is the correct choice because it is designed specifically for securely storing and managing secrets, keys, and certificates. It supports automatic rotation of secrets via integration with Azure managed identities and event grid notifications, and provides fine-grained access control through Azure RBAC and access policies, with full auditing via Azure Monitor and diagnostic logs.

Exam trap

The trap here is that candidates often confuse Azure App Configuration with Key Vault because both deal with configuration, but App Configuration is for non-sensitive settings and feature flags, while Key Vault is the only service that provides secure secret storage with rotation and auditing.

How to eliminate wrong answers

Option B (Azure App Configuration) is wrong because it is optimized for managing application configuration settings and feature flags, not for storing secrets; it lacks native automatic rotation and secret-specific access policies. Option C (Azure Storage Queues) is wrong because it is a message queue service for asynchronous communication, not a secure store for secrets or configuration. Option D (Azure Service Bus) is wrong because it is an enterprise message broker for reliable messaging and pub/sub patterns, not a secrets management service.

Practice this question →

174

MCQhard

A media company uploads large video files to Azure Blob Storage. Users frequently access recent videos, while older videos are rarely accessed after 30 days. The company wants to minimize storage costs while ensuring that recently accessed videos are immediately available. Which storage tier strategy should you recommend?

A.Use Premium tier for all files

B.Use Cool tier for all files with lifecycle management to Archive

C.Use Hot tier for the first 30 days, then automatically move to Cool tier

D.Use Archive tier for all files and rehydrate on access

AnswerC

Hot tier for the first 30 days gives immediate low-latency access during the peak viewing and editing window, and the lifecycle rule fires automatically to transition blobs to Cool after the access pattern cools down. Cool tier then cuts storage cost by roughly 40-50% while still offering sub-second latency for occasional replays. Because lifecycle evaluation runs once per day, the rule must be set to '30 days after last modification' to avoid a 31-day gap; this simple policy balances cost and availability without manual intervention.

Why this answer

It balances cost and performance by using the Hot tier for the first 30 days (when videos are frequently accessed) and then automatically transitioning to the Cool tier via Azure Blob Storage lifecycle management. This ensures immediate availability for recent uploads while minimizing storage costs for older, rarely accessed content. The Cool tier offers lower storage costs than Hot but still provides low-latency access, meeting the requirement that recently accessed videos are immediately available.

Exam trap

The trap here is that candidates may assume Cool tier is always the cheapest option for infrequent access, but they overlook that Archive tier, while cheaper, introduces unacceptable rehydration delays for the 'immediately available' requirement, and that Hot tier is necessary for the initial high-access period to avoid access costs and latency.

How to eliminate wrong answers

Option A is wrong because using Premium tier for all files incurs significantly higher costs (designed for high transaction rates and low latency) without any cost optimization for rarely accessed older videos. Option B is wrong because using Cool tier from the start means recently uploaded videos (accessed frequently) are stored in a tier optimized for infrequent access, which has higher access costs and may introduce latency on first access compared to Hot tier. Option D is wrong because Archive tier has the lowest storage cost but requires rehydration (which can take up to 15 hours) before videos can be accessed, violating the requirement that recently accessed videos are immediately available.

Practice this question →

175

MCQhard

A global e-commerce company uses Azure Cosmos DB to store its product catalog. The catalog is read-heavy, with users worldwide expecting consistent reads with a 99th percentile latency under 10 ms. Writes to the catalog are performed by a central admin team in one region. The company needs to minimize write latency and cost while ensuring that users always see the same data within a single session. Which Cosmos DB configuration should the company choose?

A.Single-master write region with Strong consistency and multiple read regions

B.Multi-master write with Eventual consistency and all regions enabled for writes

C.Single-master write region with Session consistency and multiple read regions

D.Multi-master write with Strong consistency and two regions

AnswerC

Session consistency deployed with a single-master write region and multiple read regions is the optimal balance: all writes are sent to one regional endpoint, minimizing write latency and avoiding cross-region conflict resolution. The Cosmos DB SDK manages session tokens to ensure that within the same user session, reads are served from any read region yet still reflect the most recent writes performed in that session, satisfying the requirement for session consistency. This design provides low-latency reads globally for the e-commerce workload, where users access the application from various geographic regions, without the cost or complexity of multi-master writes.

Why this answer

Session consistency provides the required 'read your own writes' guarantee within a single session, which ensures users always see the same data during their session without the latency and cost penalties of Strong consistency. Single-master writes minimize write latency by directing all writes to one region (the central admin team's region), while multiple read regions allow global users to read from the nearest region with sub-10 ms latency. This configuration balances cost, performance, and consistency needs for a read-heavy catalog with centralized writes.

Exam trap

The trap here is that candidates often confuse 'strong consistency' with 'always correct' and overlook that Session consistency is sufficient for per-session guarantees, while Strong consistency adds unnecessary latency and cost for a read-heavy catalog with centralized writes.

How to eliminate wrong answers

Option A is wrong because Strong consistency with multiple read regions requires all replicas to acknowledge reads, which increases read latency and cost, and does not minimize write latency as writes must still propagate synchronously to all read regions. Option B is wrong because Multi-master writes with Eventual consistency would allow writes from any region, but the central admin team writes from one region, and eventual consistency does not guarantee that users see their own writes within a session, violating the 'same data within a single session' requirement. Option D is wrong because Multi-master writes with Strong consistency across two regions would introduce high write latency (due to synchronous replication) and increased cost, while the scenario only needs single-master writes from one admin region.

Practice this question →

176

MCQhard

A company stores petabytes of image files for a content delivery network. The images are accessed frequently for the first week, then rarely afterward. They must be retained for 5 years for compliance. The company wants to minimize storage costs while maintaining performance for frequently accessed data. Which storage solution and tier strategy should they recommend?

A.Azure Blob Storage with a lifecycle policy: Hot for 7 days, Cool for the remainder of 5 years

B.Azure Files with premium tier

C.Azure Data Lake Storage Gen2 with hot tier only

D.Azure Blob Storage with archive tier from day 1

AnswerA

This is correct because Azure Blob Storage is optimized for serving large volumes of static objects over HTTP/S to Azure CDN or Front Door, and its lifecycle management feature automates movement between access tiers based on blob age. Setting a rule for Hot for 7 days matches the period of heavy read traffic, after which transitioning to Cool for the remaining 5 years dramatically reduces storage cost while still providing sub-second latency for occasional access. The lifecycle policy evaluates each blob's last modification date and enforces the tier change without manual intervention, exactly fitting a cost-sensitive archive-with-fast-recent-access pattern.

Why this answer

Azure Blob Storage with a lifecycle policy is the correct solution because it automatically transitions blobs from the Hot tier (for frequent access during the first week) to the Cool tier (for rare access over the remaining 5 years), minimizing storage costs while maintaining low-latency performance for the initial high-access period. The Hot tier provides high throughput and low access costs for frequently read data, while the Cool tier offers lower storage costs for infrequently accessed data, meeting both performance and compliance retention requirements.

Exam trap

The trap here is that candidates often choose the Archive tier for long-term retention without considering the performance impact of frequent access during the first week, overlooking that Archive requires hours to rehydrate and incurs high read costs, making it unsuitable for the initial high-access period.

How to eliminate wrong answers

Option B is wrong because Azure Files with premium tier uses SSD-backed file shares designed for low-latency enterprise workloads (e.g., SQL Server, home directories), not for petabyte-scale image content delivery; it is cost-prohibitive for long-term retention and lacks native lifecycle tiering to reduce costs. Option C is wrong because Azure Data Lake Storage Gen2 with hot tier only provides no cost optimization for rarely accessed data after the first week, leading to unnecessarily high storage costs for 5 years of compliance retention. Option D is wrong because Azure Blob Storage with archive tier from day 1 would impose high retrieval costs and multi-hour rehydration latency for images that are frequently accessed during the first week, violating the performance requirement for the initial access period.

Practice this question →

177

MCQeasy

A company stores log data in Azure Blob Storage. Logs are accessed frequently for the first 30 days, then rarely accessed but must be retained for 7 years for compliance. They want to minimize storage costs. Which storage tier and lifecycle management rule should they use?

A.Use the Cool tier for initial storage, and a lifecycle rule to move to Archive after 30 days.

B.Use the Hot tier for initial storage, and a lifecycle rule to move to the Cool tier after 30 days, then to Archive after 7 years.

C.Use the Hot tier for initial storage, and a lifecycle rule to move to Archive after 30 days.

D.Use the Archive tier for initial storage, and a lifecycle rule to move to Hot for the first 30 days.

AnswerC

Hot tier optimizes for frequent access during the first 30 days. Moving directly to Archive after 30 days minimizes storage cost during the long retention period, as Archive has the lowest storage cost for rarely accessed data.

Why this answer

The Hot tier is optimal for frequent access during the first 30 days, and a lifecycle rule moving directly to Archive after 30 days minimizes costs by immediately transitioning to the lowest-cost storage tier for long-term retention. The Archive tier is the most cost-effective for data that is rarely accessed and must be retained for 7 years, as it offers the lowest storage cost but higher retrieval latency and cost.

Exam trap

The trap here is that candidates may overcomplicate by adding an intermediate Cool tier (Option B) or incorrectly assume Archive can be used for initial storage (Option D), failing to recognize that direct transition to Archive after the hot period is the most cost-effective for long-term retention with minimal access.

How to eliminate wrong answers

Option A is wrong because using the Cool tier for initial storage is not cost-effective for frequently accessed logs; the Hot tier has lower access costs for frequent reads/writes, making it more economical for the first 30 days. Option B is wrong because moving to Cool after 30 days and then to Archive after 7 years incurs unnecessary transition costs and storage costs in Cool for 7 years, whereas direct transition to Archive after 30 days is cheaper for long-term retention. Option D is wrong because storing data initially in the Archive tier is impractical for frequent access; Archive has high retrieval latency (up to 15 hours) and high access costs, making it unsuitable for data accessed frequently in the first 30 days.

Practice this question →

178

Multi-Selectmedium

Which THREE considerations are important when designing a data archiving solution for Azure Storage to optimize costs?

Select 3 answers

A.Use the hot tier for all data to ensure high performance.

B.Consider early deletion penalties for data moved to archive tier.

C.Account for data retrieval (rehydration) costs when accessing archived data.

D.Choose the appropriate access tier (hot, cool, or archive) based on access frequency.

E.Use geo-redundant storage (GRS) for all archive data.

AnswersB, C, D

The archive access tier in Azure Blob Storage carries a 180-day minimum billing period; if you delete a blob or move it to a hotter tier before 180 days, you are charged an early deletion fee equal to the remaining days of storage. This penalty exists because Microsoft prices archive storage on the assumption of long-term commitment, and the fee can easily erase any savings from tiering data down. Therefore, any lifecycle policy that archives data must include a retention analysis to avoid unexpected charges when data is retired prematurely.

Why this answer

Azure Archive tier has a minimum storage duration of 180 days; deleting or moving data before that incurs an early deletion penalty equal to the cost of the remaining days. This is critical for cost optimization as it prevents unexpected charges from short-lived data.

Exam trap

The trap here is that candidates often overlook early deletion penalties and rehydration costs, focusing only on the low storage price of archive tier, leading to unexpected charges when data is deleted or accessed prematurely.

Practice this question →

179

MCQhard

Your company uses Azure SQL Database and needs to archive data older than 7 years for compliance. The archived data must be stored in the most cost-effective manner, must be immutable, and must be deleted exactly after 10 years. What should you use?

A.Azure Archive Storage with lifecycle management to delete after 10 years

B.Azure Blob Storage with immutable storage and time-based retention policy

C.Azure SQL Database restore to a point in time with a retention period of 10 years

D.Azure SQL Database long-term retention (LTR) backups

AnswerB

Azure Blob Storage with immutable storage enforces a write-once-read-many (WORM) policy that blocks any writes or deletes until the retention period expires. A time-based retention policy can be set to exactly 10 years, ensuring data cannot be altered or removed during that period and is automatically eligible for deletion only after the policy lapses, satisfying both archival and compliance needs.

Why this answer

Azure Blob Storage with immutable storage and a time-based retention policy ensures that archived data cannot be modified or deleted until the specified retention period expires. This meets the compliance requirements for immutability and a 10-year deletion timeline, while blob storage tiers (e.g., cool or archive) can be used for cost-effective long-term storage.

Exam trap

The trap here is that candidates often confuse Azure Archive Storage's low cost with immutability, failing to realize that immutability requires a separate WORM policy, which Archive Storage does not inherently provide.

How to eliminate wrong answers

Option A is wrong because Azure Archive Storage alone does not provide immutability; it only offers low-cost storage with lifecycle management for deletion, but without a write-once-read-many (WORM) policy, data could be altered or deleted prematurely. Option C is wrong because Azure SQL Database point-in-time restore has a maximum retention period of 35 days, not 10 years, and does not provide immutability. Option D is wrong because Azure SQL Database long-term retention (LTR) backups are not immutable; they can be manually deleted before the retention period ends, and they are stored as backups, not as an immutable archive.

Practice this question →

180

MCQmedium

You are designing a disaster recovery solution for a SQL Server database hosted on an Azure VM. The recovery point objective (RPO) is 5 minutes, and the recovery time objective (RTO) is 1 hour. Which strategy should you recommend?

A.Use Azure SQL Managed Instance with failover groups.

B.Configure log shipping to a secondary VM in another region.

C.Use Azure Backup to back up the database every 5 minutes.

D.Replicate the VM using Azure Site Recovery with 5-minute replication.

AnswerA

Failover groups in Azure SQL Managed Instance provide automated, regional replication of databases with a configurable replication policy, ensuring an RPO of zero seconds (or near-zero) and RTO of under a minute for unplanned failovers. The service handles primary/secondary role transitions and redirects connections to the new primary, meeting the stated RPO and RTO requirements without needing to manage a secondary VM. As a PaaS offering, it also includes built-in high availability and eliminates the operational overhead of manual log shipping or backup/restore processes.

Why this answer

Azure SQL Managed Instance with failover groups provides automated, synchronous or asynchronous replication of the database to a secondary region, enabling a Recovery Point Objective (RPO) of 5 minutes and a Recovery Time Objective (RTO) of 1 hour. The failover group handles automatic or manual failover at the instance level, ensuring minimal data loss and rapid recovery without complex manual log shipping or backup restoration.

Exam trap

The trap here is that candidates often confuse Azure Site Recovery's 5-minute replication frequency with meeting database-level RPO, but Site Recovery replicates disk blocks, not SQL Server transaction log consistency, so it cannot guarantee a 5-minute RPO for database transactions without additional configuration like log shipping or Always On availability groups.

How to eliminate wrong answers

Option B is wrong because log shipping to a secondary VM in another region typically has an RPO of 15 minutes or more (depending on log backup frequency) and requires manual failover steps, making it unable to consistently meet a 5-minute RPO and 1-hour RTO. Option C is wrong because Azure Backup for SQL Server on Azure VM has a minimum backup frequency of 15 minutes for transaction log backups, not 5 minutes, and restoring from backups takes longer than 1 hour due to restore time and point-in-time recovery overhead. Option D is wrong because Azure Site Recovery replicates the entire VM at the disk level, not the database transaction logs, and its 5-minute replication frequency applies to disk changes, not SQL Server transaction log consistency, leading to potential data corruption or longer recovery times for database-consistent failover.

Practice this question →