Examkin

Soru

Zorluk: ZorBlob, File, and Disk Storage Solutions

An enterprise is designing the storage infrastructure for a new mission-critical transaction processing application deployed on Azure Virtual Machines. The architecture must satisfy the following requirements:

- The transaction log drive requires block storage that supports at least 50005{}000 IOPS and 200200 MB/s of throughput with sub-millisecond write latency.
- The transaction log storage must remain highly available and survive a physical datacenter (availability zone) outage within the primary Azure region without data loss.
- Application audit logs stored in Azure Blob Storage must be securely shared with external auditors via time-bound links that can be revoked immediately at any time without rotating the primary storage account keys or affecting other active signatures.

Which storage configuration should you recommend?

  1. A
    Standard HDD Managed Disks configured with Zone-Redundant Storage (ZRS) for the transaction logs, and Azure Blob Storage with Shared Access Signatures (SAS) tied to a Stored Access Policy for the audit logs.
  2. B
    Premium SSD v2 Managed Disks configured with Locally Redundant Storage (LRS) for the transaction logs, and Azure Blob Storage with Shared Access Signatures (SAS) tied to a Stored Access Policy for the audit logs.
  3. Premium SSD v2 Managed Disks configured with Zone-Redundant Storage (ZRS) for the transaction logs, and Azure Blob Storage with Shared Access Signatures (SAS) tied to a Stored Access Policy for the audit logs.Cevap
  4. D
    Premium SSD v2 Managed Disks configured with Zone-Redundant Storage (ZRS) for the transaction logs, and Azure Blob Storage with ad-hoc Shared Access Signatures (SAS) containing a direct expiration timestamp for the audit logs.

Cevap

The correct option recommends Premium SSD v2 Managed Disks with Zone-Redundant Storage (ZRS) for the transaction logs, and Azure Blob Storage with Shared Access Signatures (SAS) tied to a Stored Access Policy for the audit logs.
The correct configuration uses Premium SSD v2 with Zone-Redundant Storage (ZRS) for the VM disks to guarantee sub-millisecond latencies, support the throughput/IOPS specifications, and withstand an availability zone failure. By using a Shared Access Signature tied to a Stored Access Policy, the audit logs can be shared securely with external partners, and the access can be instantly revoked by modifying or deleting the policy in Azure without rotating the master storage account keys.

Adım Adım Çözüm

1
Evaluate disk options for the transaction log performance requirements.
Standard HDD is eliminated as it cannot deliver sub-millisecond latencies or support 50005{}000 IOPS. Premium SSD v2 is selected because it meets both performance metrics and supports sub-millisecond write latency.
Database transaction logs are latency-sensitive and require high-performance block storage.
2
Determine the redundancy level required to survive a physical datacenter outage.
Locally Redundant Storage (LRS) is eliminated because it is confined to a single datacenter. Zone-Redundant Storage (ZRS) is selected because it replicates data across three availability zones in the region.
The system must survive a zone outage without data loss.
3
Identify the mechanism for sharing blob storage that allows instant revocation without rotating primary account keys.
Ad-hoc SAS is eliminated because it cannot be revoked without key rotation. A SAS associated with a Stored Access Policy is selected because modifying or deleting the policy immediately invalidates the SAS.
The security requirements demand granular, immediate revocation of external auditor access.

Anahtar Kavram

Selecting appropriate Azure disk storage and configuring secure data access mechanisms
Bu soruyu puanla

Konular

Blob, File, and Disk Storage Solutions

Bu konudan daha fazla soru