Which combination of actions should a solutions architect take to meet these requirements?
(Choose two.)
Mount Amazon S3 as a file system to the on-premises servers.
Deploy an AWS Storage Gateway file gateway to replace NFS storage.
Deploy AWS Snowball Edge to provision NFS mounts to on-premises servers.
Deploy an AWS Storage Gateway volume gateway to replace the block storage.
Deploy Amazon Elastic Fife System (Amazon EFS) volumes and mount them to on-premises servers.
Explanations:
Mounting Amazon S3 as a file system requires an additional layer (like S3FS), and it does not provide NFS support directly. This option does not address the need for local caching or directly integrate with existing NFS applications.
Deploying an AWS Storage Gateway file gateway can replace NFS storage by providing a local cache for frequently accessed data, allowing existing applications to interact with S3 using NFS, which fits the requirement for performance and local caching without re-architecting applications.
AWS Snowball Edge is primarily designed for data transfer and edge computing, not for providing NFS mounts to on-premises servers. This option does not align with the need for ongoing storage capacity and local caching.
Deploying an AWS Storage Gateway volume gateway can replace block storage by providing block storage in the cloud with local caching capabilities. This solution helps meet the performance requirements and integrates well with existing applications without needing a full re-architecture.
Amazon Elastic File System (EFS) is a managed NFS service, but it cannot be mounted directly to on-premises servers without a VPN or Direct Connect. This option does not fulfill the requirement for local caching without re-architecting existing applications.
I assess that the answer is:
Deploy an AWS Storage Gateway file gateway to replace NFS storage.