AWS Certified Solutions Architect Professional SAP-C02 Practice Question
A healthcare provider is redesigning its on-premises picture-archiving and communication system (PACS). The legacy application runs on VMware hosts and accesses a single 12-TiB iSCSI LUN. About 2 TiB of the images are accessed frequently; the rest is rarely used but must still be available with millisecond-level latency. The data-center SAN capacity must be reduced. The new solution must:
continue to present block storage over iSCSI with no application changes
store incremental, point-in-time backups in AWS
let engineers quickly create development copies of the dataset on Amazon EC2 by restoring snapshots to Amazon EBS volumes
require the least additional on-premises storage capacity
Which approach will meet these requirements?
Deploy AWS Storage Gateway as a Volume Gateway in cached-volume mode. Create a 12-TiB cached volume, allocate about 2 TiB of local SSD cache, and schedule snapshots to AWS. Restore snapshots to new Amazon EBS volumes for development workloads.
Deploy AWS Storage Gateway as a Volume Gateway in stored-volume mode. Create a 12-TiB stored volume on local disks and schedule snapshots to AWS. Use the snapshots to provision development volumes in Amazon EC2.
Deploy AWS Storage Gateway as a File Gateway. Expose an NFS share backed by an S3 Standard-IA bucket and mount it on the application servers.
Install an AWS DataSync agent to copy the iSCSI LUN to an Amazon S3 bucket on a nightly schedule and mount the dataset in AWS by using an S3 file system such as s3fs.
Deploying a Volume Gateway in cached-volume mode satisfies every requirement. Cached volumes keep the primary dataset in Amazon S3 and retain only recently accessed blocks plus an upload buffer on local VM disks, allowing the on-premises SAN footprint to shrink to roughly the cache size (for example 2 TiB). The gateway exposes the volume as an iSCSI target, so the application does not need to change. Incremental backups are taken as Amazon EBS snapshots; because the volume is smaller than 16 TiB, those snapshots can be restored either back to the gateway or to new EBS volumes in an EC2 development environment.
Stored-volume mode would still require the full 12 TiB to remain on-premises. File Gateway provides NFS/SMB, not iSCSI block, and AWS DataSync alone offers only file transfer, not block storage or snapshot-based restores. Therefore, the cached-volume configuration is the only option that meets all stated constraints while minimizing local storage.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is AWS Storage Gateway and how does it work?
Open an interactive chat with Bash
What is the difference between cached-volume and stored-volume modes in Storage Gateway?
Open an interactive chat with Bash
How are snapshots used in AWS Storage Gateway for backups and development?
Open an interactive chat with Bash
AWS Certified Solutions Architect Professional SAP-C02
Accelerate Workload Migration and Modernization
Your Score:
Report Issue
Bash, the Crucial Exams Chat Bot
AI Bot
Loading...
Loading...
Loading...
IT & Cybersecurity Package Join Premium for Full Access