Examkin

Question

Difficulty: HardBlob, File, and Disk Storage Solutions

A medical research facility is deploying a genomic data analysis application on Azure. The application utilizes a combination of virtual machine-based analytics engines and a shared storage platform. The storage infrastructure must satisfy the following constraints:

* The analytics database requires high-performance write operations for transient scratch space, needing sub-millisecond latencies.
* A shared file storage system must support POSIX-compliant file access over NFS for multiple Linux-based compute nodes, with high throughput and resiliency against local datacenter zone outages.
* Temporary datasets must be shared with external research teams via pre-signed URLs. The facility must be able to invalidate these URLs immediately if a security anomaly is detected, without affecting other shared datasets.

Which TWO of the following configurations should you recommend in the storage architecture design? (Select TWO.)

  1. Provision Ultra Disk storage for the database transient scratch space.Answer
  2. Deploy a Premium tier Azure Files share configured with NFS and Zone-Redundant Storage (ZRS).Answer
  3. C
    Provision Standard SSD managed disks for the database transient scratch space.
  4. D
    Configure Locally Redundant Storage (LRS) for the NFS file shares to minimize replication latency.
  5. E
    Generate ad-hoc Shared Access Signatures (SAS) signed directly by the storage account access key.

Answer

Provision Ultra Disk storage for the database transient scratch space and deploy a Premium tier Azure Files share configured with NFS and Zone-Redundant Storage (ZRS).
The correct configurations are to provision Ultra Disk storage for the database scratch space and to deploy a Premium tier Azure Files share with NFS and ZRS. Ultra Disk is the only selected storage option that guarantees the required sub-millisecond write latencies. Premium tier Azure Files supports NFS v4.1 and can be deployed with ZRS, satisfying the requirements for POSIX compliance, NFS access, and zone outage resiliency. Stored access policies must be utilized to manage SAS tokens to support instant revocation.

Step-by-Step Solution

1
Analyze the database scratch space requirements.
Identify that sub-millisecond latency is required, which narrows the disk storage selection to Ultra Disk or Premium SSD v2.
Standard SSD and Standard HDD disks cannot meet the strict sub-millisecond latency demands of high-performance database workloads.
2
Analyze the shared file storage requirements.
Identify that POSIX-compliant NFS file access with zone resiliency is required, directing the selection to Premium tier Azure Files with Zone-Redundant Storage (ZRS).
Standard tier Azure Files does not support NFS. Premium tier Azure Files supports NFS and can be provisioned with ZRS to sustain a zone failure.
3
Analyze the blob sharing and revocation requirements.
Determine that SAS tokens must be managed using stored access policies to allow immediate, individual revocation without key rotation.
Ad-hoc SAS tokens generated directly from the storage account key cannot be revoked individually without rotating the entire storage account key.

Key Concept

Selecting appropriate Azure storage service tiers, disk types, redundancy configurations, and security access policies to meet strict latency, protocol, availability, and revocation requirements.
Rate this question

Topics

Blob, File, and Disk Storage Solutions

More questions from this topic