Examkin

Question

Difficulty: MediumBlob, File, and Disk Storage Solutions

An organization is designing a storage solution for a medical imaging application that generates high-resolution files. The solution must meet the following requirements:
- Files must be immediately accessible via HTTP/HTTPS protocols.
- Files are frequently accessed during the first 30 days, after which they are rarely accessed but must remain available for retrieval within seconds.
- External medical partners must be granted temporary access to specific files. The organization must be able to immediately revoke all active external access links to a container if a security breach is suspected, without modifying the primary storage account keys.
- Data must be replicated to a secondary region to protect against regional disasters, but read access to the secondary region is not required under normal operations.

Which storage configuration should you recommend?

  1. A
    Azure Blob storage configured with Locally Redundant Storage (LRS), using Shared Access Signatures (SAS) governed by a Stored Access Policy, and a lifecycle policy that moves files to the Cool tier after 30 days.
  2. B
    Azure Blob storage configured with Geo-Redundant Storage (GRS), using ad-hoc Shared Access Signatures (SAS) with an expiration time, and a lifecycle policy that moves files to the Cool tier after 30 days.
  3. Azure Blob storage configured with Geo-Redundant Storage (GRS), using Shared Access Signatures (SAS) governed by a Stored Access Policy, and a lifecycle policy that moves files to the Cool tier after 30 days.Answer
  4. D
    Azure Blob storage configured with Geo-Redundant Storage (GRS), using Shared Access Signatures (SAS) governed by a Stored Access Policy, and a lifecycle policy that moves files to the Archive tier after 30 days.

Answer

Azure Blob storage configured with Geo-Redundant Storage (GRS), using Shared Access Signatures (SAS) governed by a Stored Access Policy, and a lifecycle policy that moves files to the Cool tier after 30 days.
The correct configuration uses Azure Blob storage with GRS for regional redundancy (without active read access to the secondary), a Stored Access Policy to govern SAS tokens so that access can be revoked immediately by modifying or deleting the policy, and a lifecycle management rule to transition data to the Cool tier after 30 days to meet the retrieval time constraint (seconds vs. hours for the Archive tier).

Step-by-Step Solution

1
Determine the appropriate redundancy option to satisfy the regional disaster recovery requirement without read-access overhead.
Select Geo-Redundant Storage (GRS) instead of Locally Redundant Storage (LRS) or Read-Access Geo-Redundant Storage (RA-GRS).
GRS replicates data to a secondary region, providing protection against regional outages, but keeps the secondary endpoint offline/unavailable for reads under normal conditions.
2
Identify the mechanism that allows temporary sharing of container contents with the ability to instantly revoke all active links.
Use Shared Access Signatures (SAS) associated with a Stored Access Policy (SAP).
An ad-hoc SAS can only be revoked by rotating storage account keys, whereas a SAS linked to a Stored Access Policy can be revoked immediately by deleting or modifying the policy.
3
Determine the best cost-optimized tier that still allows low-latency retrieval within seconds after 30 days.
Use a lifecycle management policy to transition blobs to the Cool tier.
The Cool tier is optimized for infrequently accessed data and supports sub-second retrieval times, whereas the Archive tier takes hours to rehydrate.

Key Concept

Selecting the optimal Azure Blob storage configuration by balancing replication requirements, access tier retrieval latency constraints, and instant security token revocation features.
Estimated Time:1m 30s
Rate this question

Topics

Blob, File, and Disk Storage Solutions

More questions from this topic