An organization is designing a shared storage architecture for a hybrid application. The application components are deployed in an Azure Kubernetes Service (AKS) cluster and on-premises virtual machines. The solution must meet the following requirements:
- Provide a shared file system that can be mounted concurrently by multiple AKS pods (ReadWriteMany) and the on-premises virtual machines using the SMB protocol.
- Ensure that the storage can survive a physical zone outage in the primary Azure region without data loss or service disruption.
- Provide access to on-premises users using their existing on-premises Active Directory Domain Services (AD DS) credentials.
- Secure the storage access; if Shared Access Signatures (SAS) are used for any ad-hoc diagnostic transfers, they must support easy revocation.
Which two actions should you include in the storage design?
- Create an Azure Files Premium file share configured with Zone-Redundant Storage (ZRS).Cevap
- Enable on-premises Active Directory Domain Services (AD DS) authentication for the Azure storage account.Cevap
- CCreate an Azure Files Standard file share configured with Locally Redundant Storage (LRS).
- DConfigure Read-Access Geo-Redundant Storage (RA-GRS) and use it as an active-active write target across two regions.
- EGenerate ad-hoc Shared Access Signatures (SAS) with a five-year validity window directly in the URI.