Examkin

Question

Difficulty: HardBlob, File, and Disk Storage Solutions

An animation studio is migrating its core rendering pipeline to Azure. The pipeline consists of 150150 Linux-based virtual machines running rendering software.

The design requirements for the shared storage solution are as follows:
- Protocol & Compatibility: The rendering nodes require shared storage that supports NFS, POSIX-compliant file permissions, and hard links.
- Performance: The storage must support high-throughput parallel reads and writes, achieving sub-1010 millisecond metadata operation latency.
- Availability: The storage solution must remain available even if a single physical datacenter (availability zone) in the primary Azure region experiences an outage.
- Administration: The storage solution must minimize the administrative overhead of managing OS-level clustering, virtual machines, or file system updates.

Which storage solution should you recommend in the design?

  1. A
    An Azure Files NFS v 4.14.1 share in a Premium FileStorage account configured with Locally Redundant Storage (LRS).
  2. B
    An Azure Blob Storage container configured with NFS v 33 in a Standard General Purpose v 22 storage account configured with Zone-Redundant Storage (ZRS).
  3. An Azure Files NFS v 4.14.1 share in a Premium FileStorage account configured with Zone-Redundant Storage (ZRS).Answer
  4. D
    An Azure Files SMB 3.03.0 share in a Premium FileStorage account configured with Zone-Redundant Storage (ZRS), using a Shared Access Signature (SAS) token with a 55-year lifetime for authentication.

Answer

An Azure Files NFS v 4.14.1 share in a Premium FileStorage account configured with Zone-Redundant Storage (ZRS).
The correct solution is the option recommending an Azure Files NFS v 4.14.1 share in a Premium FileStorage account configured with Zone-Redundant Storage (ZRS). This fully managed service natively supports POSIX permissions and hard links required by Linux workloads, delivers sub-1010 millisecond metadata latency via the Premium tier, and survives availability zone outages through ZRS.

Step-by-Step Solution

1
Analyze compatibility and protocol requirements.
The rendering nodes are Linux-based and require NFS with support for POSIX-compliant permissions and hard links. This excludes SMB-based storage configurations.
Linux rendering pipelines typically rely on hard links and POSIX permissions, which are fully supported under NFS but not natively preserved over SMB without complex AD mappings.
2
Evaluate performance and account tier constraints.
The solution must support sub-1010 millisecond latency and high-throughput operations, requiring a Premium storage tier. NFS v 33 on Blob Storage requires a Premium BlockBlobStorage account, and NFS v 4.14.1 on Azure Files requires a Premium FileStorage account.
Standard tiers do not support NFS protocols and cannot guarantee the sub-1010 millisecond metadata latencies required for rendering workloads.
3
Evaluate availability and redundancy requirements.
To survive a physical datacenter (availability zone) outage, the storage account must be configured with Zone-Redundant Storage (ZRS). Locally Redundant Storage (LRS) is eliminated.
ZRS replicates data synchronously across three availability zones within the primary region, providing resiliency against zone failures that LRS cannot offer.
4
Select the fully managed solution that satisfies all conditions.
An Azure Files NFS v 4.14.1 share in a Premium FileStorage account with ZRS meets all compatibility, performance, and availability constraints while minimizing management overhead.
It offers a fully managed (PaaS) file share, eliminating the administrative effort of managing custom VM clusters.

Key Concept

Selecting the correct Azure Files tier, protocol (NFS vs SMB), and redundancy options for high-performance Linux workloads requiring POSIX compliance and zone-level resilience.
Rate this question

Topics

Blob, File, and Disk Storage Solutions

More questions from this topic