Examkin

Question

Difficulty: MediumBlob, File, and Disk Storage Solutions

You are designing the storage infrastructure for a business-critical SQL Server database running on an Azure Virtual Machine. The database transaction logs require a dedicated disk that supports up to 5,0005,000 IOPS and sub-millisecond latency. The architecture must survive a zone failure in the primary region. Additionally, database backup exports must be securely stored in an Azure Blob Storage container and accessed by a third-party auditing application using a Shared Access Signature (SAS) token that can be revoked immediately if compromised.

Which storage configuration should you recommend?

  1. A
    Configure the transaction log drive on Premium SSD managed disks using Locally Redundant Storage (LRS). Store the backup exports in a Blob Storage container and authorize the auditing application using a SAS token associated with a stored access policy.
  2. Configure the transaction log drive on Premium SSD managed disks using Zone-Redundant Storage (ZRS). Store the backup exports in a Blob Storage container and authorize the auditing application using a SAS token associated with a stored access policy.Answer
  3. C
    Configure the transaction log drive on Standard SSD managed disks using Zone-Redundant Storage (ZRS). Store the backup exports in a Blob Storage container and authorize the auditing application using a SAS token associated with a stored access policy.
  4. D
    Configure the transaction log drive on Premium SSD managed disks using Zone-Redundant Storage (ZRS). Store the backup exports in a Blob Storage container and authorize the auditing application using an ad-hoc SAS token with a 2-year expiration time.

Answer

Configure the transaction log drive on Premium SSD managed disks using Zone-Redundant Storage (ZRS). Store the backup exports in a Blob Storage container and authorize the auditing application using a SAS token associated with a stored access policy.
The correct configuration uses Premium SSD to meet the IOPS and latency requirements of database transaction logs, employs Zone-Redundant Storage (ZRS) to ensure zone resiliency, and utilizes a stored access policy for the SAS token to allow immediate revocation.

Step-by-Step Solution

1
Analyze the performance requirements for the transaction log drive.
The workload requires 5,0005,000 IOPS and sub-millisecond latency. This points to Premium SSD or Ultra Disk, eliminating Standard SSD.
Database transaction logs are write-intensive and sensitive to write latency.
2
Evaluate the resiliency requirement for the disk.
The architecture must survive a zone failure, meaning the disks must use Zone-Redundant Storage (ZRS). Locally Redundant Storage (LRS) is insufficient.
ZRS replicates data across three availability zones in the primary region.
3
Determine the secure access method for Blob Storage with instant revocation capabilities.
To revoke a SAS token immediately without regenerating the storage account keys, the SAS must be associated with a stored access policy.
An ad-hoc SAS token cannot be revoked unless the storage account keys are rotated, which breaks all other SAS tokens signed with the same key.

Key Concept

Azure managed disk performance tiers, zone redundancy, and stored access policies for secure SAS token revocation.
Estimated Time:1m 30s
Rate this question

Topics

Blob, File, and Disk Storage Solutions

More questions from this topic