Question

Difficulty: HardBlob, File, and Disk Storage Solutions

An organization is designing the storage infrastructure for a mission-critical financial application hosted on Azure Virtual Machines. The application requires a database data drive that must support at least 15,00015,000 IOPS and sub-millisecond write latency. The database files must survive a storage zone failure. Additionally, you must provide secure, temporary, write-only access to specific database backup blobs for external auditors, and this access must be easily revocable at any time. Which two configurations should you include in the storage design? (Select two.)

  1. Configure the database data drive using Premium SSD v2 managed disks with zone-redundant storage (ZRS).Answer
  2. Generate a Shared Access Signature (SAS) token that is associated with a Stored Access Policy.Answer
  3. C
    Configure the database data drive using Ultra Disks.
  4. D
    Configure the database data drive using Standard SSD managed disks with zone-redundant storage (ZRS).
  5. E
    Generate a Shared Access Signature (SAS) token with the expiration time defined directly in the token URI and set to 3030 days.

Answer

Configure the database data drive using Premium SSD v2 managed disks with zone-redundant storage (ZRS), and generate a Shared Access Signature (SAS) token associated with a Stored Access Policy.
Premium SSD v2 managed disks support zone-redundant storage (ZRS) while delivering the required 15,00015,000 IOPS and sub-millisecond latency. Additionally, associating the SAS token with a Stored Access Policy provides the ability to revoke access immediately by deleting or modifying the policy.

Step-by-Step Solution

1
Analyze database performance and redundancy needs.
The application requires at least 15,00015,000 IOPS, sub-millisecond latency, and protection against zone outages. This rules out Standard SSDs (insufficient performance) and Ultra Disks (lack ZRS support). Premium SSD v2 supports ZRS and can meet the performance requirements.
Choosing the correct disk type ensures both high-performance SLAs and zone-level resilience are met simultaneously.
2
Analyze security and revocation requirements for external access.
Temporary access must be write-only and easily revocable. An ad-hoc SAS token defined in the URI cannot be revoked without rotating delegation keys. A SAS token linked to a Stored Access Policy can be revoked instantly by removing or altering the policy.
Associating SAS tokens with Stored Access Policies is the standard Azure best practice for managing and revoking external access without disrupting other operations.

Key Concept

Selecting high-performance Azure disk types that support zone-redundant storage (ZRS), and implementing revocable blob access using Shared Access Signatures (SAS) associated with Stored Access Policies.
Rate this question