Examkin

Soru

Zorluk: Çok zorBlob, 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 has the following storage requirements:

1. Database transaction logs: Must support up to 60,00060,000 IOPS and less than 1 ms1\text{ ms} latency. The storage must remain available even if an entire Azure Availability Zone suffers an outage.
2. Long-term database backups: Must be stored in blob storage, retain high durability, be resilient against a regional disaster, and allow immediate read access to the secondary region at all times.
3. Temporary ETL files: Will be accessed via Shared Access Signatures (SAS) by external partners. The SAS tokens must be valid for 66 months, but the security team must have the ability to immediately revoke access if a token is compromised.

Which three storage configurations should you recommend to meet these requirements? (Select three.)

  1. Provision Azure Premium SSD v2 disks configured with Zone-Redundant Storage (ZRS) for the database transaction logs.Cevap
  2. Configure the backup blob storage account to use Read-Access Geo-Redundant Storage (RA-GRS).Cevap
  3. Generate Shared Access Signatures (SAS) by binding them to a Stored Access Policy on the blob container.Cevap
  4. D
    Provision Azure Ultra Disks for the database transaction logs.
  5. E
    Configure the backup blob storage account to use Locally Redundant Storage (LRS).
  6. F
    Generate ad-hoc Shared Access Signatures (SAS) with a 66-month expiration directly on the target blobs.

Cevap

To meet the storage requirements, you must provision Azure Premium SSD v2 disks with Zone-Redundant Storage (ZRS) for the transaction logs, configure the backup storage account to use Read-Access Geo-Redundant Storage (RA-GRS), and generate the Shared Access Signatures (SAS) by binding them to a Stored Access Policy.
The correct configurations are: using Azure Premium SSD v2 disks with Zone-Redundant Storage (ZRS) for the transaction logs, because Premium SSD v2 can deliver the required 60,00060,000 IOPS and sub-millisecond latency, while ZRS protects against zone-level failures; using Read-Access Geo-Redundant Storage (RA-GRS) for the backups, which replicates data to a secondary region for disaster recovery and permits read access to the secondary region at all times; using a Stored Access Policy to bind the SAS tokens, which enables immediate revocation of the SAS by simply deleting or changing the policy, without impacting other tokens or rotating storage keys.

Adım Adım Çözüm

1
Analyze the virtual machine disk performance and availability requirements.
The workload needs up to 60,00060,000 IOPS, sub-millisecond latency, and zone-level resilience. While Ultra Disk meets the performance limits, it only supports Locally Redundant Storage (LRS). Therefore, Azure Premium SSD v2 with Zone-Redundant Storage (ZRS) must be selected.
Premium SSD v2 supports up to 80,00080,000 IOPS and less than 1 ms1\text{ ms} latency, and supports ZRS configuration in supported regions.
2
Evaluate backup replication requirements.
Backups require durability, regional disaster resilience, and continuous read access in the secondary region. Read-Access Geo-Redundant Storage (RA-GRS) satisfies all these conditions.
RA-GRS provides geo-replication with read access to the secondary endpoint before failover occurs.
3
Establish a secure mechanism for temporary external access with revocation capability.
Shared Access Signatures (SAS) must be bound to a Stored Access Policy.
An ad-hoc SAS cannot be revoked without rotating account keys. A Stored Access Policy allows direct revocation by deleting or updating the policy.

Anahtar Kavram

Selecting Azure disk types, blob storage replication models, and SAS security patterns to meet performance, availability, and compliance requirements.
Bu soruyu puanla

Konular

Blob, File, and Disk Storage Solutions

Bu konudan daha fazla soru