Question

Difficulty: MediumBlob, File, and Disk Storage Solutions

An organization is migrating a media processing application to Azure and has identified two key storage requirements:

1. A shared file system to store active media assets. This file system must support the NFS protocol, deliver sub-millisecond latency, and survive a zone-wide datacenter outage.
2. A long-term repository for historical project logs. These logs must be stored at the lowest possible storage cost, but they must be accessible within 1010 minutes when requested by compliance auditors.

Which two storage configurations should you recommend to meet these requirements?

  1. An Azure Files Premium share using Zone-Redundant Storage (ZRS) for the active media assets.Answer
  2. An Azure Blob Storage account configured with the Cool tier for the historical project logs.Answer
  3. C
    An Azure Files Premium share using Locally Redundant Storage (LRS) for the active media assets.
  4. D
    An Azure Blob Storage account configured with the Archive tier for the historical project logs.
  5. E
    A series of Standard HDD managed disks attached to the virtual machines to host the shared NFS file system.

Answer

An Azure Files Premium share using Zone-Redundant Storage (ZRS) for the active media assets, and an Azure Blob Storage account configured with the Cool tier for the historical project logs.
The correct configurations are an Azure Files Premium share using Zone-Redundant Storage (ZRS) and an Azure Blob Storage account using the Cool tier. NFS file shares are restricted to the Premium tier of Azure Files, which is designed to provide sub-millisecond latency. Opting for Zone-Redundant Storage (ZRS) satisfies the business continuity requirement by replicating data across three availability zones. For the historical logs, the requirement to access files within ten minutes eliminates the Archive tier because of its multi-hour rehydration latency. The Cool tier serves as the most cost-effective online tier that allows instant data access.

Step-by-Step Solution

1
Determine the storage tier and redundancy for the shared NFS system.
Azure Files Premium tier is selected because NFS file shares are only supported on Premium. Zone-Redundant Storage (ZRS) is chosen to survive zone-wide outages.
NFS protocol support and sub-millisecond latency require Azure Files Premium, while zone outage resilience requires ZRS.
2
Evaluate the tier requirements for the historical project logs.
Azure Blob Storage Cool tier is selected.
Although the Archive tier is cheaper, its high rehydration latency prevents access within the required ten-minute window. The Cool tier offers low-cost storage with sub-second retrieval times.

Key Concept

Selecting Azure storage services, tiers, and redundancy levels based on latency, protocol, availability, and recovery time objectives.
Rate this question