Examkin

Question

Difficulty: MediumBlob, File, and Disk Storage Solutions

A logistics company is designing the Azure storage infrastructure for a legacy fleet management application. The application will run on Azure Virtual Machines and has the following storage requirements:
- The virtual machine operating system and application binaries require persistent disk storage that supports sub-millisecond write latency.
- A shared file system is required to store application configuration files. The share must support the SMB 3.0 protocol, be accessible simultaneously by multiple virtual machines, and must survive a local datacenter zone outage.
- External partners need read-only access to specific PDF reports stored in Azure Blob Storage. This access must be granted via a Shared Access Signature (SAS) that can be easily revoked if compromised, without regenerating storage account keys.

Which two configurations should you include in the storage design? (Select TWO.)

  1. Premium SSD v2 managed disks for the operating system and application binariesAnswer
  2. A Shared Access Signature (SAS) token for the Blob storage container that is associated with a stored access policyAnswer
  3. C
    Standard HDD managed disks for the operating system and application binaries
  4. D
    An ad-hoc Shared Access Signature (SAS) token with a lifetime of one year generated directly using the storage account key
  5. E
    An Azure Files share configured with Locally Redundant Storage (LRS) for the shared configuration files

Answer

Premium SSD v2 managed disks for the operating system and application binaries, and a Shared Access Signature (SAS) token for the Blob storage container that is associated with a stored access policy.
Premium SSD v2 managed disks satisfy the requirement for sub-millisecond write latency. Additionally, associating a Shared Access Signature (SAS) token with a stored access policy enables revocation without rotating the primary storage account keys.

Step-by-Step Solution

1
Analyze the VM disk latency requirement.
Identify that sub-millisecond latency demands high-performance SSD tiers (such as Premium SSD v2 or Ultra Disk) rather than magnetic-based standard options.
This rules out Standard HDD options which are designed for backup/archival and do not guarantee low latency.
2
Evaluate the file share zone outage requirement.
Determine that the storage account containing the Azure Files share must be configured with Zone-Redundant Storage (ZRS) or Geo-Zone-Redundant Storage (GZRS).
Locally Redundant Storage (LRS) stores three copies of data inside a single datacenter zone, making it a single point of failure during a zone outage.
3
Assess the secure data sharing and revocation requirement.
Determine that the SAS token must be associated with a stored access policy.
If an ad-hoc SAS is compromised, revoking it requires rotating the storage account keys, which breaks other services. A stored access policy can be deleted or updated to immediately invalidate the associated SAS token.

Key Concept

Azure Managed Disk selection, Azure Files availability zones, and secure Blob storage sharing with revocable SAS tokens using stored access policies.
Rate this question

Topics

Blob, File, and Disk Storage Solutions

More questions from this topic