D is the correct answer Volume Gateway CACHED Vs STORED Cached = stores a subset of frequently accessed data locally Stored = Retains the ENTIRE ("all file types") in on prem data centre

ChatGPT is wrong. "Immediate access to all file types from the on-premises systems without experiencing latency" needs "stored volume" type. With "cached volume" not all data will be available locally.

"users retain immediate access to all file types" immediate cannot be cached -> D

all file types. Cached only save the most frecuently or lastest accesed. If you didn´t access any type for a long time, you will not cache it -> No immediate access

"Immediate access to all file types from the on-premises systems without experiencing latency" requirement is not met by C. Also the solution is meant for DR purposes, the primary storage for the data should remain on premises.

In the cached mode, your primary data is written to S3, while retaining your frequently accessed data locally in a cache for low-latency access. In the stored mode, your primary data is stored locally and your entire dataset is available for low-latency access while asynchronously backed up to AWS. Reference: https://aws.amazon.com/storagegateway/faqs/ Good luck.

"The company wants to ensure that end users retain immediate access to all file types from the on-premises systems " D is the correct answer.

Correct answer is Volume Gateway Stored which keeps all data on premises. To have immediate access to the data. Cached is for frequently accessed data only.

all file types, NOT all files. Volume mode can not cache 100TBs.

dddddddd

End users retain immediate access to all file types = Volume Gateway stored volume

Also the solution is meant for DR purposes, it's not like they need more storage or so.

D is the correct answer Volume Gateway CACHED Vs STORED Cached = stores a data recentlly at local Stored = Retains the ENTIRE ("all file types") in on prem data centre

Bad question. No RTO/RPO, so impossible to properly answer. They probably want to hear option D. Depending on RPO, option B is also an adequate solution (data remains immediately accessible without experiencing latency via existing infrastructure, backup to cloud for DR). Also, this option requires LESS changes to existing infra than A. Only argument against B is that VTLs are usually used for legacy DR solutions, not for new ones, where object storage such as S3 is usually supported natively.

https://docs.aws.amazon.com/storagegateway/latest/vgw/StorageGatewayConcepts.html Stored volumes can range from 1 GiB to 16 TiB in size and must be rounded to the nearest GiB. Each gateway configured for stored volumes can support up to 32 volumes and a total volume storage of 512 TiB (0.5 PiB).

pentium75 is right.

It is stated the company wants to keep the data locally and have DR plan in cloud. It points directly to the volume gateway

"The company wants to ensure that end users retain immediate access to all file types from the on-premises systems " This points to stored volumes..

A,B are wrong types of gateways for hundreds of TB of data that needs immediate access on-prem. C limits to 10TB. D provides access to all the files.

The stored volume configuration stores the entire data set on-premises and asynchronously backs up the data to AWS. The cached volume configuration stores recently accessed data on-premises, and the remaining data is stored in Amazon S3 -that is why D is right

Answer is C go argue somewhere.

From chatGPT4 Considering the requirements of minimal infrastructure change, immediate file access, and low-latency, Option C: Provisioning an AWS Storage Gateway Volume Gateway (cached volume) with a 10 TB local cache, seems to be the most fitting solution. This setup aligns with the existing iSCSI setup and provides a local cache for low-latency access, while also configuring scheduled snapshots for disaster recovery. In the event of a disaster, restoring a snapshot to an Amazon EBS volume and attaching it to an Amazon EC2 instance as described in this option would align with the recovery objective.

CCCCCCCCCCCCCCCC