Answer: Deploy an AWS Storage Gateway file gateway to replace NFS storage., Deploy an AWS Storage Gateway volume gateway to replace the block storage.

## Explanation **Correct Answers: B and D** **B. Deploy an AWS Storage Gateway file gateway to replace NFS storage.** - AWS Storage Gateway File Gateway provides a file interface to Amazon S3, allowing you to store and retrieve objects as files. - It supports NFS (Network File System) and SMB (Server Message Block) protocols, making it compatible with existing NFS-based applications. - It includes local caching capabilities for frequently accessed data, which improves performance. **D. Deploy an AWS Storage Gateway volume gateway to replace the block storage.** - AWS Storage Gateway Volume Gateway provides iSCSI block storage volumes that can be mounted as local storage by on-premises applications. - It supports both cached volumes (where frequently accessed data is cached locally) and stored volumes (where all data is stored locally and asynchronously backed up to AWS). - This allows existing block storage applications to work without re-architecting. **Why other options are incorrect:** **A. Mount Amazon S3 as a file system to the on-premises servers.** - While tools like S3FS exist to mount S3 as a file system, they don't provide the same level of performance, local caching, or protocol compatibility as Storage Gateway. - S3 is object storage, not designed for direct file system mounting with high performance requirements. **C. Deploy AWS Snowball Edge to provision NFS mounts to on-premises servers.** - AWS Snowball Edge is designed for data transfer and edge computing, not for ongoing storage expansion with local caching. - It's a temporary solution for data migration, not a permanent storage expansion solution. **E. Deploy Amazon Elastic File System (Amazon EFS) volumes and mount them to on-premises servers.** - Amazon EFS is designed for AWS cloud environments and requires AWS Direct Connect or VPN connectivity. - While EFS can be accessed from on-premises via AWS Direct Connect, it doesn't provide local caching capabilities at the on-premises location. - The performance would be limited by network latency between on-premises and AWS. **Key Requirements Met:** 1. **Supports both block and NFS storage** - Volume Gateway for block storage, File Gateway for NFS storage 2. **Local caching** - Both Storage Gateway solutions support local caching 3. **No re-architecting** - Uses standard protocols (iSCSI for block, NFS for file) 4. **High-performing** - Local caching improves performance for frequently accessed data 5. **Expands storage capacity** - Backed by virtually unlimited AWS cloud storage