A company’s on-premises applications use both block storage and NFS and are running out of storage capacity. The company needs a high-performance solution that supports local caching without re-architecting the applications. Which combination of actions should a solutions architect take? (Choose two.)

The correct options are to deploy an AWS Storage Gateway file gateway and an AWS Storage Gateway volume gateway. A File Gateway provides a file interface to Amazon S3, supporting NFS and SMB protocols. This allows on-premises applications to use NFS shares that are backed by scalable cloud storage, with local caching for performance, without re-architecting. A Volume Gateway provides block storage to on-premises applications using iSCSI. It can be configured in cached mode, storing primary data in S3 while retaining frequently accessed data locally, or stored mode, keeping primary data on-premises and asynchronously backing it up to S3. Both options integrate with existing protocols and offer local caching, meeting the requirements. Mounting Amazon S3 as a file system directly is not a native or high-performance solution for on-premises applications. AWS Snowball Edge is primarily for large-scale data transfer or edge computing, not for continuous, high-performance NFS mounts from on-premises to the cloud. Amazon EFS is a cloud-native NFS file system and cannot be directly mounted by on-premises servers without additional networking solutions like AWS Direct Connect or VPN, and it doesn't inherently provide local caching for on-premises access in the same way Storage Gateway does.