Examkin

Question

Difficulty: HardBlob, File, and Disk Storage Solutions

An enterprise is designing the storage infrastructure for a financial analytics application that is migrating to Azure. The application has the following requirements:
- A database running on an Azure Virtual Machine requires a dedicated managed disk for write-heavy transaction logs with a performance target of 10,00010,000 IOPS and sub-millisecond write latency.
- A shared volume must be mounted concurrently by ten Linux servers to process incoming CSV files via the NFS v4.1 protocol with sub-millisecond latency.
- Telemetry logs must be stored cost-effectively for five years. The logs are rarely accessed but must be available for immediate, sub-second query execution when requested.

Which two storage configurations should you include in the design?

  1. Premium SSD v2 managed disks for the database transaction logsAnswer
  2. An Azure Files Premium tier file share for the shared volumeAnswer
  3. C
    Azure Blob Storage Archive tier for the telemetry logs
  4. D
    Standard HDD managed disks for the database transaction logs
  5. E
    An Azure Blob Storage account configured with Locally Redundant Storage (LRS) for critical telemetry logs to ensure survival during a primary datacenter outage

Answer

Premium SSD v2 managed disks for the database transaction logs and an Azure Files Premium tier file share for the shared volume
Premium SSD v2 managed disks provide the sub-millisecond write latency and high IOPS capabilities needed for transaction logs. Azure Files Premium tier is required because NFS v4.1 shares are only supported on the Premium tier.

Step-by-Step Solution

1
Evaluate the database transaction log requirement.
Identify that the database requires 10,00010,000 IOPS and sub-millisecond write latency.
Premium SSD v2 or Ultra Disk is required to achieve sub-millisecond latency. Premium SSD v2 is the most cost-effective option that satisfies these requirements, whereas Standard HDD cannot support such IOPS or latency targets.
2
Evaluate the shared volume requirement.
Determine that the file share must support NFS v4.1 and concurrent access from ten Linux servers.
Azure Files supports NFS v4.1 only in the Premium tier. Standard tier Azure Files supports only SMB and REST protocols.
3
Evaluate the telemetry logs retrieval latency requirement.
Determine that while the data is rarely accessed, it must be queryable with sub-second retrieval times.
Moving data to the Archive tier introduces a rehydration latency of hours, which does not allow for immediate, sub-second query execution.

Key Concept

Selecting Azure storage services and tiers based on latency, performance, protocol, and redundancy requirements.
Rate this question

Topics

Blob, File, and Disk Storage Solutions

More questions from this topic