Question

Difficulty: Very hardBlob, File, and Disk Storage Solutions

An enterprise is migrating an on-premises transactional database to an Azure Virtual Machine. You are designing the storage architecture to meet the following requirements:

- Transaction Logs: The drive hosting the database transaction logs must support at least 25,00025,000 IOPS and deliver sub-millisecond write latency.
- Database Backups: Backups must be stored in Azure Blob Storage and remain available even in the event of a complete regional outage of the primary Azure region.
- Auditor Access: An external auditing firm requires access to download specific backup files for a period of 1414 days. You must be able to immediately revoke this access at any point during the 1414 days without affecting other clients or rotating the storage account access keys.

Which storage design should you recommend?

  1. A
    Provision a Premium SSD disk for the transaction logs. Store the backups in a Locally Redundant Storage (LRS) Blob storage account. Configure a Shared Access Signature (SAS) associated with a stored access policy for the auditor.
  2. B
    Provision a Standard HDD disk for the transaction logs. Store the backups in a Geo-Redundant Storage (GRS) Blob storage account. Configure a Shared Access Signature (SAS) associated with a stored access policy for the auditor.
  3. Provision a Premium SSD disk for the transaction logs. Store the backups in a Geo-Redundant Storage (GRS) Blob storage account. Configure a Shared Access Signature (SAS) associated with a stored access policy for the auditor.Answer
  4. D
    Provision a Premium SSD disk for the transaction logs. Store the backups in a Geo-Redundant Storage (GRS) Blob storage account. Configure an ad-hoc Shared Access Signature (SAS) with a 14-day validity period defined directly in the token query string for the auditor.

Answer

Provision a Premium SSD disk for the transaction logs, store backups in a Geo-Redundant Storage (GRS) Blob storage account, and configure a Shared Access Signature (SAS) associated with a stored access policy for the auditor.
The solution that combines Premium SSD, Geo-Redundant Storage (GRS), and a SAS token associated with a stored access policy is correct. Premium SSD provides the necessary IOPS and sub-millisecond write latency for database transaction logs. GRS replicates backup data to a secondary Azure region to survive a primary regional disaster. Linking the auditor's SAS token to a stored access policy enables administrators to instantly revoke access by deleting or altering the policy, without modifying the storage account keys or disrupting other applications.

Step-by-Step Solution

1
Evaluate the database transaction logs' performance and latency needs.
Determine that magnetic storage (Standard HDD) is unsuitable, and Premium SSD, Premium SSD v2, or Ultra Disk is required to guarantee at least 25,00025,000 IOPS and sub-millisecond write latency.
Standard HDD/SSD tiers cannot provide high IOPS alongside consistent sub-millisecond write performance.
2
Determine the redundancy level required to survive a complete regional outage.
Select Geo-Redundant Storage (GRS) or Geo-Zone-Redundant Storage (GZRS) for the backups.
Locally Redundant Storage (LRS) and Zone-Redundant Storage (ZRS) only replicate data within the primary region and would be lost if the entire region failed.
3
Analyze the access control and revocation requirements for the external auditor.
Choose a Shared Access Signature (SAS) linked to a Stored Access Policy.
An ad-hoc SAS cannot be revoked without rotating storage account keys. Associating the SAS with a stored access policy allows revocation by simply deleting or updating the policy on the container.

Key Concept

Selecting appropriate Azure disk tiers for performance, configuring storage replication for regional disaster recovery, and securing blob access using delegable and revocable stored access policies.

Alternative Method

Instead of Premium SSD, you could also use Ultra Disk for the transaction logs to achieve sub-millisecond latency, but Premium SSD remains a valid and cost-effective choice for meeting the specified 25,00025,000 IOPS requirement.
Estimated Time:3m 0s
Rate this question