An enterprise is migrating an on-premises transactional database to an Azure Virtual Machine. You are designing the storage architecture to meet the following requirements:
- Transaction Logs: The drive hosting the database transaction logs must support at least IOPS and deliver sub-millisecond write latency.
- Database Backups: Backups must be stored in Azure Blob Storage and remain available even in the event of a complete regional outage of the primary Azure region.
- Auditor Access: An external auditing firm requires access to download specific backup files for a period of days. You must be able to immediately revoke this access at any point during the days without affecting other clients or rotating the storage account access keys.
Which storage design should you recommend?
- AProvision a Premium SSD disk for the transaction logs. Store the backups in a Locally Redundant Storage (LRS) Blob storage account. Configure a Shared Access Signature (SAS) associated with a stored access policy for the auditor.
- BProvision a Standard HDD disk for the transaction logs. Store the backups in a Geo-Redundant Storage (GRS) Blob storage account. Configure a Shared Access Signature (SAS) associated with a stored access policy for the auditor.
- Provision a Premium SSD disk for the transaction logs. Store the backups in a Geo-Redundant Storage (GRS) Blob storage account. Configure a Shared Access Signature (SAS) associated with a stored access policy for the auditor.Answer
- DProvision a Premium SSD disk for the transaction logs. Store the backups in a Geo-Redundant Storage (GRS) Blob storage account. Configure an ad-hoc Shared Access Signature (SAS) with a 14-day validity period defined directly in the token query string for the auditor.