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 minutes when requested by compliance auditors.
Which two storage configurations should you recommend to meet these requirements?
- An Azure Files Premium share using Zone-Redundant Storage (ZRS) for the active media assets.Answer
- An Azure Blob Storage account configured with the Cool tier for the historical project logs.Answer
- CAn Azure Files Premium share using Locally Redundant Storage (LRS) for the active media assets.
- DAn Azure Blob Storage account configured with the Archive tier for the historical project logs.
- EA 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
Key Concept
Selecting Azure storage services, tiers, and redundancy levels based on latency, protocol, availability, and recovery time objectives.