A company is designing the storage architecture for a health informatics application hosted on Azure Linux virtual machines. The design must meet the following requirements:
- The application requires a shared filesystem that is POSIX-compliant, supports concurrent read/write access from multiple VMs with sub-millisecond metadata latency, and can survive a datacenter zone outage.
- Database transaction logs must be stored on VM disk storage that guarantees sub-millisecond write latency and supports scaling IOPS and throughput dynamically without virtual machine deallocation.
- System audit logs must be stored in a WORM (Write Once, Read Many) state for seven years. External auditors must be granted access to these logs for exactly 30 days using a token that can be revoked immediately if a security compromise is suspected.
Which three storage configurations should you include in the design? (Select three.)
- Configure Azure Files Premium tier using the Network File System (NFS) protocol and Zone-Redundant Storage (ZRS).Cevap
- Deploy Premium SSD v2 disks for the database transaction logs and adjust performance settings dynamically as workload demands change.Cevap
- Configure Azure Blob Storage with a time-based retention policy, and generate a Service SAS linked to a Stored Access Policy for audit log access.Cevap
- DDeploy Standard SSD disks for the database transaction logs to minimize costs while maintaining transaction write performance.
- EConfigure Azure Blob Storage with a time-based retention policy, and generate an ad-hoc SAS token signed with the storage account key for audit log access.
- FConfigure Azure Files Standard tier using Locally-Redundant Storage (LRS) and mount the shares using SMB 3.0.