AZ-204 Develop for Azure storage Practice Test 2 — 15 Questions

Question 1

You are developing a web application that stores user session data in Azure Redis Cache. The application experiences high traffic and you need to ensure that session data is not lost if the cache is restarted. Which feature should you enable?

Choose an answer to begin — your selection is scored in the full session.

Accepted Answer

Redis persistence (RDB or AOF). To prevent session data loss when the cache restarts, you must enable Redis persistence. This feature periodically saves the cache data to a storage account, allowing the data to be restored after a restart. Clustering, geo-replication, and private endpoints address scalability, disaster recovery, and security, respectively, but not data durability on restart.

Answer

Geo-replication

Answer

Clustering

Answer

Azure Private Endpoint

Question 2

You are developing an application that uses Azure Blob Storage. You need to implement a retry policy for transient failures when uploading blobs. The application uses the Azure.Storage.Blobs SDK. You want to configure the retry options to use exponential backoff with a maximum of 5 retries and a base delay of 2 seconds. Which code segment should you use?

Accepted Answer

var options = new BlobClientOptions(BlobClientOptions.ServiceVersion.V2021_12_02); options.Retry.MaxRetries = 5; options.Retry.Delay = TimeSpan.FromSeconds(2); options.Retry.Mode = RetryMode.Exponential;. To configure exponential backoff with a base delay of 2 seconds and 5 retries, you must set the Retry.Mode to RetryMode.Exponential, Retry.MaxRetries to 5, and Retry.Delay to 2 seconds. The BlobClientOptions class exposes these properties. The other options either use incorrect properties (NetworkTimeout) or set the wrong mode (Fixed), or omit the mode entirely, which may default to exponential but is not explicit. The correct code segment explicitly configures all required settings.

Answer

var options = new BlobClientOptions(); options.Retry.MaxRetries = 5; options.Retry.NetworkTimeout = TimeSpan.FromSeconds(2); options.Retry.Mode = RetryMode.Exponential;

Answer

var options = new BlobClientOptions(); options.Retry.MaxRetries = 5; options.Retry.Delay = TimeSpan.FromSeconds(2); options.Retry.Mode = RetryMode.Fixed;

Answer

var options = new BlobClientOptions(); options.Retry.MaxRetries = 5; options.Retry.Delay = TimeSpan.FromSeconds(2); options.Retry.MaxDelay = TimeSpan.FromSeconds(10);

Question 3

A company stores archival data in Azure Blob Storage. The data is accessed only a few times per year, and retrieval can take up to 15 hours. Which blob access tier minimizes storage costs while meeting these requirements?

Accepted Answer

Archive tier. The Archive tier is the correct choice because it is designed for data that is rarely accessed (a few times per year) and has a retrieval latency of up to 15 hours, which matches the requirement. It offers the lowest storage cost among Azure Blob Storage tiers, making it optimal for long-term archival data where infrequent access and delayed retrieval are acceptable.

Answer

Hot tier

Answer

Cool tier

Answer

Premium tier

Question 4

You are building a serverless application that needs to react to insertions and updates in an Azure Cosmos DB container. You want to process these changes using an Azure Function. Which trigger should you configure for the function?

Accepted Answer

Cosmos DB trigger. A Cosmos DB trigger is the correct choice because it is specifically designed to react to changes in a Cosmos DB container by leveraging the change feed. The Azure Function runtime polls the change feed for inserts and updates, invoking the function with batches of documents as they occur. This provides a native, serverless integration without needing additional services.

Answer

Blob trigger

Answer

Event Grid trigger

Answer

Service Bus trigger

Question 5

You are developing an application that writes logs to Azure Blob Storage. Each log entry is small (less than 1 KB) and you need to store millions of entries per day. You want to minimize storage costs and maximize write throughput. Which blob type should you use?

Accepted Answer

Append blobs.. Append blobs are optimized for append operations, making them ideal for logging scenarios where each log entry is appended to the blob. They provide high throughput for write-heavy, sequential append workloads and are cost-effective because they use the same block blob pricing but avoid the overhead of managing individual blocks for each small entry.

Answer

Block blobs with a high block size.

Answer

Page blobs.

Answer

Block blobs with a low block size.

Question 6

You need to upload large files (up to 100 GB) to Azure Blob Storage from a web application. The upload must be resilient to network failures and support pausing/resuming. Which approach should you use?

Accepted Answer

Use block blob with multiple blocks and parallel upload.. Block blobs support uploading large files (up to ~4.75 TB) by splitting the file into multiple blocks, uploading them in parallel for speed, and committing the block list atomically. This approach provides resilience to network failures (individual blocks can be retried) and supports pausing/resuming by tracking which blocks have been uploaded.

Answer

Upload the blob as a single PUT operation.

Answer

Use append blob.

Answer

Use AzCopy from the server.

Question 7

You need to store millions of small log entries (each <1 KB) per day from an IoT device. The logs are rarely read. Which storage solution is most cost-effective?

Accepted Answer

Azure Blob Storage Block Blob. Azure Blob Storage Block Blob is the most cost-effective solution for storing millions of small log entries (<1 KB) that are rarely read because it offers extremely low storage costs per GB, supports high-throughput ingestion, and is optimized for large-scale, append-oriented workloads. Block blobs can be stored in the 'Cool' or 'Archive' access tier to further reduce costs, and they can be efficiently batched into larger blocks (up to 100 MB per block) to minimize transaction costs.

Answer

Azure SQL Database

Answer

Azure Table Storage

Answer

Azure Files

Question 8

You are developing an application that writes log entries to Azure Blob Storage. Each log entry is approximately 500 bytes, and you expect to generate millions of entries per day. The logs are rarely read, and when they are read, you need to retrieve ranges of logs sequentially. Which blob type should you use to minimize storage costs and maximize write throughput?

Accepted Answer

Append blobs. Append blobs are optimized for append operations, making them ideal for write-heavy, sequential logging scenarios. Each append operation adds data to the end of the blob, achieving high write throughput without the overhead of managing block lists. Since logs are rarely read and accessed sequentially, append blobs minimize storage costs compared to block blobs (which require block management overhead) and page blobs (which are designed for random access and are more expensive).

Answer

Block blobs

Answer

Page blobs

Answer

Azure Files shares

Question 9

An application stores large media files (up to 5 GB) that are frequently appended to but rarely read sequentially. Which Azure Blob Storage type should be used to optimize writes and cost?

Accepted Answer

Append blob. Append blobs are optimized for append operations, making them ideal for scenarios like logging or storing media files that are frequently appended to. They support high-throughput writes without the overhead of managing block lists, and they are cost-effective for sequential append workloads compared to block blobs, which require explicit block management and are better suited for random read/write patterns.

Answer

Block blob

Answer

Page blob

Answer

Archive blob

Question 10

You are developing a .NET Core application that stores session state data. The data is infrequently updated but must be read quickly for every user request. You need a serverless, globally distributed storage solution with low latency reads. Which Azure storage solution should you use?

Accepted Answer

Azure Cosmos DB with SQL API. Azure Cosmos DB with SQL API is the correct choice because it provides a globally distributed, serverless database service with single-digit millisecond read latency at any scale, making it ideal for infrequently updated session state that must be read quickly for every user request. Its multi-region replication ensures low-latency reads from any location, and the SQL API offers a familiar query interface for .NET Core applications.

Answer

Azure Table Storage

Answer

Azure Redis Cache

Answer

Azure Blob Storage

Question 11

You need to store large binary files (up to 2 GB) that are frequently overwritten in place (entire file replaced). You want to minimize storage cost and write latency. Which Azure Blob Storage type should you use?

Accepted Answer

Block Blob. Block blobs are optimized for storing large binary files (up to ~4.75 TB) and support high-throughput uploads via PutBlock and PutBlockList operations. They allow overwriting an entire blob by uploading a new set of blocks, which minimizes write latency compared to page blobs that require sector-aligned writes. Block blobs also offer lower storage cost than page blobs, making them the best choice for frequently overwritten large files.

Answer

Page Blob

Answer

Append Blob

Answer

Archive Blob

Question 12

An application writes millions of small log entries (500 bytes each) daily. The logs are rarely read, and when read, they are accessed sequentially. You need to minimize storage costs and maximize write throughput. Which Azure Blob Storage type should you use?

Accepted Answer

Append Blob. Append Blob is optimized for append operations, making it ideal for logging scenarios where new data is continuously added to the end of the blob. It provides high write throughput for small, sequential writes (like 500-byte log entries) and lower storage costs compared to Block Blob for this pattern, as it avoids the overhead of managing multiple blocks per append. Additionally, Append Blob supports sequential read access efficiently, matching the rare, sequential read requirement.

Answer

Block Blob

Answer

Page Blob

Answer

Archive Blob

Question 13

You are building an IoT solution that generates millions of small log entries (each less than 1 KB) per day. The logs are rarely read, and when they are read, they are always accessed in chronological order. You need to minimize storage costs and maximize write throughput. Which Azure Blob Storage type should you use?

Accepted Answer

Append Blob. Append Blob is optimized for append operations, making it ideal for scenarios like logging where data is continuously added and rarely modified. It supports high-throughput writes because each append operation is atomic and does not require reading or updating existing blocks, which minimizes overhead. Since the logs are accessed in chronological order, Append Blob's sequential block structure allows efficient streaming reads without random access overhead.

Answer

Block Blob

Answer

Page Blob

Answer

Archive Blob

Question 14

You need to store a large (terabytes) append-only dataset for compliance purposes. The data must be immutable to prevent tampering after writes. You also want to minimize storage cost and achieve high write throughput. Which Azure Storage solution should you use?

Accepted Answer

Azure Blob Storage with Append Blobs and an immutable blob policy. Azure Blob Storage with Append Blobs and an immutable blob policy is correct because Append Blobs are optimized for append-only operations (e.g., logging, audit trails) and support high write throughput. Immutable blob policies (WORM – Write Once, Read Many) enforce data immutability at the blob level, preventing modification or deletion during the retention period, which meets compliance requirements. This combination minimizes storage cost by using the cool or archive tier for Append Blobs, while still achieving the required write performance.

Answer

Azure Data Lake Storage Gen2 with Append Blobs and immutability

Answer

Azure Files with immutable shares

Answer

Azure NetApp Files with immutability

Question 15

You are building a compliance solution that stores terabytes of data in Azure Blob Storage. Data is appended frequently and never modified. Regulatory requirements mandate that no data can be overwritten or deleted for 7 years. Which storage configuration should you enable?

Accepted Answer

Enable immutability policy (time-based retention). A is correct because a time-based retention policy under Azure Blob Storage immutability policy ensures that blobs cannot be overwritten or deleted for a specified duration (here, 7 years). This meets the regulatory requirement of write-once-read-many (WORM) compliance, and the policy is enforced at the storage container level, preventing any modifications or deletions even by the storage account owner.

Answer

Enable blob soft delete

Answer

Enable blob versioning

Answer

Enable change feed