Examkin

Soru

Zorluk: ZorBlob, File, and Disk Storage Solutions

An enterprise is designing the storage architecture for a transaction database hosted on Azure Virtual Machines and its associated backups. The architecture must meet the following requirements:

* Database Data Volume: Requires 65,000 IOPS and 900 MB/s throughput. The storage must survive a zone outage within the primary region without data loss.
* Database Log Volume: Requires guaranteed sub-millisecond write latency and 10,000 IOPS. Application-level replication provides cross-zone disaster recovery.
* Backups: Must be stored in Azure Blob Storage. An external auditor requires read access to these backups for 48 hours. This access must be immediately revocable at any time without rotating the primary storage account keys.

Which configuration should you recommend?

  1. Configure Premium SSD v2 with Zone-Redundant Storage (ZRS) for the data volume, Ultra Disk with Locally Redundant Storage (LRS) for the log volume, and generate a Shared Access Signature (SAS) token associated with a stored access policy for the backup blobs.Cevap
  2. B
    Configure Ultra Disk with Locally Redundant Storage (LRS) for both the data and log volumes, and generate a Shared Access Signature (SAS) token associated with a stored access policy for the backup blobs.
  3. C
    Configure Standard SSD with Zone-Redundant Storage (ZRS) for the data volume, Premium SSD (v1) with Locally Redundant Storage (LRS) for the log volume, and generate a Shared Access Signature (SAS) token associated with a stored access policy for the backup blobs.
  4. D
    Configure Premium SSD v2 with Zone-Redundant Storage (ZRS) for the data volume, Ultra Disk with Locally Redundant Storage (LRS) for the log volume, and generate an ad-hoc Shared Access Signature (SAS) token with a two-year expiration period for the backup blobs.

Cevap

Configure Premium SSD v2 with Zone-Redundant Storage (ZRS) for the data volume, Ultra Disk with Locally Redundant Storage (LRS) for the log volume, and generate a Shared Access Signature (SAS) token associated with a stored access policy for the backup blobs.
The correct configuration uses Premium SSD v2 with Zone-Redundant Storage (ZRS) for the data volume to satisfy both the high performance requirements (65,000 IOPS and 900 MB/s) and the zone-failure resiliency requirement. It uses Ultra Disk with Locally Redundant Storage (LRS) for the database log volume to guarantee the sub-millisecond write latency required. Finally, it uses a Shared Access Signature (SAS) token linked to a stored access policy to grant the auditor temporary access to the backups, allowing immediate revocation if necessary without rotating the primary storage account keys.

Adım Adım Çözüm

1
Select storage for the database data volume.
Premium SSD v2 with Zone-Redundant Storage (ZRS) is selected.
The data volume requires 65,000 IOPS and 900 MB/s, which exceeds the single-disk limits of Premium SSD v1. Premium SSD v2 supports up to 80,000 IOPS and 1,200 MB/s on a single disk and supports ZRS for zone resiliency. Ultra Disk does not support ZRS.
2
Select storage for the database log volume.
Ultra Disk with Locally Redundant Storage (LRS) is selected.
The database log volume requires guaranteed sub-millisecond write latency, which is a key capability of Ultra Disk. Since replication is handled at the application layer, LRS at the storage layer is acceptable.
3
Select access mechanism for backups.
Shared Access Signature (SAS) associated with a stored access policy.
A stored access policy allows the SAS token to be revoked at any time by modifying or deleting the policy. An ad-hoc SAS token can only be revoked by rotating the storage account keys, which would disrupt other operations.

Anahtar Kavram

Azure Managed Disks performance levels (Premium SSD v2 vs. Ultra Disk), disk redundancy (ZRS vs. LRS), and secure Blob access using Shared Access Signatures with stored access policies.
Bu soruyu puanla

Konular

Blob, File, and Disk Storage Solutions

Bu konudan daha fazla soru