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

Question 1

You are creating an Azure function that uses an output binding to write messages to an Azure Storage Queue. The function must ensure that messages are not lost if the function fails after writing to the queue. Which approach should you use?

Accepted Answer

Use the queue output binding with a queue trigger input binding in the same function.. Option D is correct because using a queue output binding with a queue trigger input binding in the same function ensures that the message is only written to the queue after the function execution completes successfully. If the function fails after the write, the output binding automatically rolls back the write, preventing message loss. This is achieved through the Azure Functions runtime's transactional behavior with storage bindings.

Answer

Use a separate queue client SDK to write messages and handle errors manually.

Answer

Write to the queue directly in the function code and rely on the function's retry policy.

Answer

Use a durable function to orchestrate the writing and processing.

Question 2

Which TWO of the following are valid methods for authenticating to Azure Blob Storage?

Accepted Answer

Shared Key (storage account key). Option C is correct because the Shared Key (storage account key) method uses the HMAC-SHA256 algorithm to sign a request string with the storage account key, providing full administrative access to the storage account. Option D is correct because Azure AD authentication with RBAC allows fine-grained access control to blob containers and blobs without exposing account keys, using OAuth 2.0 tokens.

Answer

Connection string with account key

Answer

Shared access signature (SAS) token

Answer

Client certificate authentication

Question 3

Which THREE of the following are true about Azure Blob Storage lifecycle management?

Accepted Answer

It can automatically move blobs to the Cool tier after a specified number of days.. Option B is correct because Azure Blob Storage lifecycle management policies can automatically transition blobs to the Cool tier after a specified number of days. This is achieved by defining a rule with a 'tierToCool' action and a 'daysAfterModificationGreaterThan' filter, allowing cost optimization based on data access patterns.

Answer

It can be defined at the container level.

Answer

It can change the replication type of the storage account.

Question 4

Which TWO of the following are correct about Azure Cosmos DB consistency levels?

Accepted Answer

Strong consistency is available in all Azure regions.. Option B is correct because Strong consistency is available in all Azure regions when the Cosmos DB account is configured to use it. However, it is important to note that Strong consistency cannot be combined with multi-region writes; it only supports a single write region. This ensures that all reads return the most recent write, but it comes at the cost of higher latency and reduced availability during regional outages.

Answer

Strong consistency provides the highest availability.

Answer

Session consistency is the default consistency level for all new Cosmos DB accounts.

Answer

Bounded staleness consistency is the default consistency level.

Question 5

You are developing a .NET application that needs to store and retrieve large binary objects (up to 4.7 TB) in Azure Blob Storage. The application requires the lowest possible latency for reads and must support object-level tiering. Which blob type should you use?

Accepted Answer

Block blob. Block blobs are designed for storing large binary objects up to approximately 4.74 TB and support object-level tiering (Hot, Cool, Cold, Archive). They offer the lowest read latency among Azure blob types because they can be accessed directly via HTTP/HTTPS and are optimized for streaming and random read access. Object-level tiering allows you to change the access tier of individual blobs without moving the storage account, which meets the requirement for granular cost optimization.

Answer

Archive storage account

Answer

Page blob

Answer

Append blob

Question 6

You have a web application that writes user-uploaded images to Azure Blob Storage. The application uses a shared access signature (SAS) token with read and write permissions. Users report that sometimes they receive 'AuthorizationFailure' errors when uploading images, but the issue is intermittent. What is the most likely cause?

Accepted Answer

The SAS token has expired and the application is not regenerating it before it expires. Option C is correct because SAS tokens have a defined expiration time. If the application does not regenerate the token before it expires, uploads will intermittently fail with 'AuthorizationFailure' errors. The intermittent nature is explained by the token being valid for some requests and expired for others, depending on when the token was last refreshed.

Answer

The blob container has a soft-delete policy that is preventing uploads

Answer

The storage account firewall is blocking requests from the web application's IP

Answer

The SAS token was generated with an incorrect IP range restriction

Question 7

You need to ensure that data stored in Azure Blob Storage is encrypted at rest using a customer-managed key stored in Azure Key Vault. Which feature should you configure?

Accepted Answer

Azure Storage encryption with customer-managed keys in Azure Key Vault. Azure Storage encryption with customer-managed keys in Azure Key Vault allows you to use your own encryption keys to protect data at rest in Blob Storage. This feature leverages Azure Storage Service Encryption (SSE) but wraps the data encryption key with a customer-managed key stored in Azure Key Vault, providing full control over key rotation and access policies.

Answer

Azure Disk Encryption (ADE) for the storage account

Answer

Azure Information Protection (AIP) for the blob container

Answer

Azure Storage Service Encryption (SSE) with Microsoft-managed keys

Question 8

You are developing a solution that uses Azure Table Storage to store time-series data. You need to query data for a specific device within a time range efficiently. Which two properties should you use as the PartitionKey and RowKey?

Accepted Answer

PartitionKey = deviceId, RowKey = timestamp. Option C is correct because using deviceId as the PartitionKey ensures all data for a specific device is stored in the same partition, enabling efficient point queries. Using timestamp as the RowKey allows range queries within a time range for that device, as RowKey is sorted lexicographically within a partition. This design optimizes query performance by minimizing partition scans and leveraging Azure Table Storage's natural ordering.

Answer

PartitionKey = timestamp, RowKey = reverse deviceId

Answer

PartitionKey = timestamp, RowKey = deviceId

Answer

PartitionKey = deviceId, RowKey = reverse timestamp

Question 9

A company stores sensitive customer data in Azure Blob Storage. They require that all access to the storage account be logged and that any access from outside the corporate network be denied. They also need to allow read access from a specific Azure web app without exposing the storage account publicly. Which three actions should be taken? (Choose three.)

Accepted Answer

Enable diagnostic settings for the storage account and send logs to a Log Analytics workspace. Option B is correct because enabling diagnostic settings for the storage account and sending logs to a Log Analytics workspace captures all access logs (including read, write, and delete operations) as required by the scenario. This satisfies the logging requirement without exposing the storage account publicly, as logs are sent over the Azure backbone network.

Answer

Enable Azure Defender for Storage

Answer

Generate a SAS token and store it in the web app's configuration

Question 10

A company stores customer images in Azure Blob Storage. They need to reduce costs by automatically moving blobs that have not been accessed for 30 days to Cool tier, and after 90 days to Archive tier. They also need to delete blobs after one year. Which two Azure features should they implement? (Choose two.)

Accepted Answer

Azure Blob Storage lifecycle management policy. Azure Blob Storage lifecycle management policy is the correct feature because it allows you to define rules to automatically transition blobs to cooler tiers (Cool, Archive) based on the 'last accessed' or 'last modified' time, and to delete blobs after a specified period. This directly meets the requirement to move blobs after 30 days to Cool, after 90 days to Archive, and delete after one year, without manual intervention.

Answer

Azure Blob Storage object replication

Answer

Azure Blob Storage soft delete

Answer

Azure Blob Storage immutability policy

Answer

Azure Blob Storage versioning with a retention policy

Question 11

You need to grant a user access to read and write blobs in a specific container for exactly 24 hours. The user is external to your organization. Which two methods can you use? (Choose two.)

Accepted Answer

Create a shared access signature (SAS) token with an expiry time of 24 hours. Option A is correct because a shared access signature (SAS) token can be scoped to a specific container and granted read and write permissions, with an expiry time set to exactly 24 hours. This allows the external user to access only that container for the specified duration without exposing the storage account key or requiring Azure AD authentication.

Answer

Share the storage account access key with the user

Answer

Create an account SAS token with read and write permissions

Answer

Assign the 'Storage Blob Data Contributor' role to the user's Microsoft account

Question 12

You are designing a solution to store large amounts of log data that will be queried infrequently but must be retained for regulatory purposes for 7 years. The logs are append-only and do not need to be modified. You need to choose a cost-effective storage option. Which three Azure capabilities should you consider? (Choose three.)

Accepted Answer

Azure Blob Storage lifecycle management policy. Azure Blob Storage with Cool or Archive access tier is cost-effective for infrequent access. Lifecycle management can automate tier transitions. Immutability policies ensure logs cannot be modified, meeting regulatory requirements. Soft delete is for accidental deletion, not immutability.

Answer

Azure Blob Storage soft delete

Answer

Azure Table Storage

Question 13

You need to upload a large file (500 MB) to Azure Blob Storage from a .NET application with high throughput and resilience to network interruptions. Which approach should you use?

Accepted Answer

Use the Azure Storage SDK for .NET with the UploadAsync method that automatically splits the file into blocks. Option A is correct because the Azure Storage SDK's UploadAsync method automatically uses block blob staging, splitting the 500 MB file into multiple blocks that are uploaded in parallel. This provides high throughput and resilience: if a network interruption occurs, only the failed blocks need to be retried, not the entire file. The SDK handles block management and final commit, making it ideal for large file uploads.

Answer

Use HTTP PUT with the entire file in a single request

Answer

Use the Azure Portal to upload the file

Answer

Use AzCopy with a single command

Question 14

You are using Azure File Storage to share configuration files across multiple virtual machines running a legacy application. The application requires SMB 3.0 protocol with encryption. You need to ensure the file share is accessible from all VMs without exposing it to the internet. Which configuration should you use?

Accepted Answer

Create a storage account with a private endpoint and mount the file share using the private IP. Option D is correct because a private endpoint assigns the storage account a private IP address from your virtual network, allowing VMs to access the file share over SMB 3.0 with encryption without exposing the storage account to the public internet. This meets the requirement for secure, private connectivity while supporting the legacy application's SMB 3.0 protocol needs.

Answer

Create a storage account with a shared access signature (SAS) token and mount using the SAS URL

Answer

Create a storage account with a public endpoint and use a VPN gateway to connect the VMs

Answer

Create a storage account with a public endpoint and configure the firewall to allow only the VNet

Question 15

You are designing a solution that requires storing millions of small (1-5 KB) messages from IoT devices. Each message has a unique device ID and timestamp. You need to support efficient point queries by device ID and time range, and also support aggregation queries (e.g., count of messages per device per hour). Which Azure storage solution should you use?

Accepted Answer

Azure Table Storage. Azure Table Storage is the correct choice because it is a NoSQL key-value store optimized for storing large volumes of structured, non-relational data. It supports efficient point queries using the PartitionKey (device ID) and RowKey (timestamp), enabling fast retrieval by device ID and time range. Additionally, it allows aggregation queries like counting messages per device per hour via partition-scanned queries or client-side aggregation, and it is cost-effective for storing millions of small (1-5 KB) messages.

Answer

Azure Cosmos DB for NoSQL

Answer

Azure Queue Storage

Answer

Azure Blob Storage with JSON files