Examkin

Question

Difficulty: HardBlob, File, and Disk Storage Solutions

You are designing the storage architecture for a new high-performance financial ledger system hosted on Azure Linux Virtual Machines.

The system must satisfy the following requirements:
* Database transaction logs: Support up to 2000020{}000 IOPS and 500 MB/s500\text{ MB/s} throughput with sub-millisecond latency. The storage solution must sustain a single availability zone outage without data loss.
* Shared configuration files: Multiple Linux VMs must concurrently access a POSIX-compliant shared file system over the NFS v4.1 protocol. This storage must also remain available during an availability zone outage.
* Historical audit logs: Store logs cost-effectively for 77 years. They are rarely accessed, but when requested, they must be fully available for read operations within 1010 minutes.

Which TWO of the following configurations should you include in the storage design? (Select TWO)

  1. Provision Premium SSD v2 Managed Disks configured with Zone-Redundant Storage (ZRS) for the database transaction logs.Answer
  2. Create an Azure Files Premium share using the NFS v4.1 protocol and configured with Zone-Redundant Storage (ZRS) for the shared configuration files.Answer
  3. C
    Provision Ultra Disks configured with Zone-Redundant Storage (ZRS) for the database transaction logs.
  4. D
    Configure Azure Blob Storage Archive tier with a lifecycle policy to store the historical audit logs.
  5. E
    Create an Azure Files Standard share using the SMB protocol and configured with Locally-Redundant Storage (LRS) for the shared configuration files.

Answer

Provision Premium SSD v2 Managed Disks configured with Zone-Redundant Storage (ZRS) for the database transaction logs, and create an Azure Files Premium share using the NFS v4.1 protocol and configured with Zone-Redundant Storage (ZRS) for the shared configuration files.
Premium SSD v2 Managed Disks support ZRS and allow independent provisioning of up to 8000080{}000 IOPS and 1200 MB/s1{}200\text{ MB/s} throughput with sub-millisecond latencies, making them ideal for the transaction logs. Azure Files Premium (FileStorage) supports NFS v4.1 and ZRS, meeting the multi-VM concurrent POSIX-compliant access and zone-resiliency requirements for the configuration files.

Step-by-Step Solution

1
Analyze the requirements for the database transaction logs.
The workload requires up to 2000020{}000 IOPS, 500 MB/s500\text{ MB/s} throughput, sub-millisecond latency, and zone redundancy. Premium SSD v2 satisfies these performance metrics and supports Zone-Redundant Storage (ZRS). Ultra Disks do not support ZRS and are limited to Locally-Redundant Storage (LRS).
To ensure both performance targets and high availability constraints are met for critical database transaction logs.
2
Analyze the requirements for the shared configuration files.
The workload requires a POSIX-compliant shared file system accessible by multiple Linux VMs concurrently via NFS v4.1, along with zone redundancy. Azure Files Premium (FileStorage) is required to support the NFS v4.1 protocol with the necessary low latency and supports ZRS. Azure Files Standard with SMB fails both the protocol and performance requirements.
To select a compatible file storage service and protocol that supports multi-writer access on Linux with zone-level resilience.
3
Analyze the requirements for the historical audit logs.
The logs must be accessible within 1010 minutes. While the Archive tier is cost-effective, it requires a rehydration process that takes hours, which is too slow. Therefore, Hot, Cool, or Cold Blob Storage tiers must be used instead of the Archive tier.
To ensure that retrieval times do not exceed the 1010-minute threshold defined by business requirements.

Key Concept

Selecting Azure disk tiers and file storage services based on performance, protocol (NFS vs SMB), availability (ZRS vs LRS), and retrieval latency requirements.
Rate this question

Topics

Blob, File, and Disk Storage Solutions

More questions from this topic