Use a Storage Gateway volume gateway in cache mode with AWS Backup for iSCSI block storage
A global ecommerce company has many data centers around the world. With the growth of its stored data, the company needs to set up a solution to provide scalable storage for legacy on-premises file applications. The company must be able to take point-in-time copies of volumes by using AWS Backup and must retain low-latency access to frequently accessed data. The company also needs to have storage volumes that can be mounted as Internet Small Computer System Interface (iSCSI) devices from the company’s on-premises application servers. Which solution will meet these requirements?
Community Votes
100% of anonymous learners picked answer C. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
A volume gateway in cache mode presents an iSCSI block volume backed by S3 while caching frequently accessed data locally, so it delivers low-latency reads to the on-premises servers, and its volumes are first-class resources that AWS Backup can protect with point-in-time recovery.
A global ecommerce company needs scalable storage for legacy on-premises file applications, must be able to take point-in-time copies of the volumes with AWS Backup, must retain low-latency access to frequently accessed data, and needs volumes mountable as iSCSI devices from its on-premises application servers.
Choosing a file gateway or a tape gateway. A file gateway exposes an NFS or SMB share rather than an iSCSI block device, so legacy applications expecting iSCSI mounts cannot use it, and a tape gateway is for archival workloads with tape cartridges rather than for active low-latency volumes.
Community Discussion (8 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
The requirement for volumes that mount as iSCSI devices immediately identifies a Storage Gateway volume gateway, since that gateway type presents block storage over iSCSI to on-premises servers. Configuring it in cache mode means the most frequently accessed data is stored in the local cache for low-latency access while the full volume is durently backed in S3, so storage scales without provisioning on-premises capacity. AWS Backup supports Storage Gateway volumes, so point-in-time copies can be taken on a schedule, which satisfies the point-in-time copy requirement. Together the iSCSI interface, the local cache for latency, and Backup integration cover all three stated needs in one gateway type.Why the Other Options Are Wrong
A: A tape gateway writes to tape cartridges and its purpose is archival, so it does not present iSCSI volumes to on-premises application servers and it cannot provide the low-latency active access the requirement describes. B: An FSx File Gateway and an S3 File Gateway both expose file shares over NFS or SMB rather than iSCSI block devices, and AWS Backup does not provide the point-in-time volume copies described for that combination, so the mounting requirement is not met. D: A file gateway in cache mode still exposes a file share rather than an iSCSI block volume, so the legacy applications that need iSCSI devices cannot mount it, which is the defining requirement of the question.Community Comment Notes
The community voted 100 to 0 for C, and the top-voted comment stated that C is the comprehensive answer covering scalable storage, low-latency access, point-in-time backups, and iSCSI device support. Another commenter explained why the FSx File Gateway option is unnecessary, since the volumes themselves can be backed up and restored through AWS Backup with a volume gateway, and a commenter linked the Storage Gateway volume documentation.Official Reference
Related Analysis
Practice All SAP-C02 Questions
Access 85 questions with complete answers and detailed explanations.
View Full SAP-C02 Practice Test →