Question

For volume gateways, when would you use Cached volumes?

a) When you need to minimize data transfer costs
b) When you need low-latency access to the entire dataset
c) When you want to store all data locally
d) When you want to archive data to a virtual tape library

Answer 1

Cached volumes are used within AWS Storage Gateway to minimize data transfer costs by retaining frequently accessed data on-site and storing the bulk of the data in the cloud. They are not intended for local storage of an entire dataset or for archiving to a virtual tape library.

Step-by-step explanation:

For volume gateways, Cached volumes are typically used when you need to minimize data transfer costs by storing data on the cloud and retaining a subset of it locally for low-latency access. This option is suitable when you have a large dataset but do not require all of it to be stored locally, as only the most frequently accessed data is kept on-site. Conversely, if you need low-latency access to the entire dataset, then the Stored volumes configuration might be more appropriate. Cached volumes are not suitable for scenarios where you want to store all data locally (option c) or when the primary purpose is archiving data to a virtual tape library (option d), which is a different type of AWS Storage Gateway configuration.