You are designing the storage infrastructure for a reporting application migrating to Azure. The application components have the following storage requirements:
- The database transaction logs require single-digit millisecond write latency.
- The storage hosting the transaction logs must remain available if a single datacenter in the primary region fails.
- External partners need temporary access to raw log files stored in Azure Blob Storage. You must be able to revoke this access immediately if a security compromise occurs.
Which two storage configurations should you include in the design?
- Configure the database transaction logs to use Premium SSD managed disks with Zone-Redundant Storage (ZRS).Answer
- Generate Shared Access Signatures (SAS) associated with a stored access policy for the raw log files.Answer
- CConfigure the database transaction logs to use Standard SSD managed disks with Zone-Redundant Storage (ZRS).
- DConfigure the database transaction logs to use Premium SSD managed disks with Locally Redundant Storage (LRS).
- EGenerate ad-hoc Shared Access Signatures (SAS) with a long expiration time directly in the URI for the raw log files.
Answer
Configure the database transaction logs to use Premium SSD managed disks with Zone-Redundant Storage (ZRS), and generate Shared Access Signatures (SAS) associated with a stored access policy for the raw log files.
The design satisfies all requirements by choosing Premium SSD disks to meet the performance criteria, configuring Zone-Redundant Storage (ZRS) to withstand a single datacenter outage, and using stored access policies to govern the SAS tokens so that access can be revoked immediately if necessary.
Step-by-Step Solution
Key Concept
Selecting appropriate disk tiers, redundancy options, and access security methods in Azure Storage.