Exam AWS Certified Solutions Architect - Associate SAA-C02 topic 1 question 162 discussion

it should be A. For SG volume gateway, you cannot directly access the backups using Amazon S3 API. Q: When I look in Amazon S3 why can’t I see my volume data? A: Your volumes are stored in an Amazon S3 bucket maintained by the AWS Storage Gateway service. Your volumes are accessible for I/O operations through AWS Storage Gateway. You cannot directly access them using Amazon S3 API actions. You can take point-in-time snapshots of gateway volumes that are made available in the form of Amazon EBS snapshots, which can be turned into either Storage Gateway Volumes or EBS Volumes. Use the File Gateway to work with your data natively in S3.

Read FAQs for storage gateway It definitely says File gateway A as the choice for databases What can I do with File Gateway? A: Use cases for File Gateway include: (a) migrating on-premises file data to Amazon S3, while maintaining fast local access to recently accessed data, (b) Backing up on-premises file data as objects in Amazon S3 (including Microsoft SQL Server and Oracle databases and logs), with the ability to use S3 capabilities such as lifecycle management and cross region replication, and, (c) Hybrid cloud workflows using data generated by on-premises applications for processing by AWS services such as machine learning, big data analytics or serverless functions.

AAAAAAAAA

AWS Storage Gateway volume gateway is layer4 not application layer.

using voting comment to enable community answer :) enjoy the explanation from expert here

If there was an option for SG tape gateway, that would be ideal.. but given backup can be on NFS share, A can also be an answer. Option B provides iscsi volume access to onprem resources and backup server is unable to use it as it is (unless we format it as a filesystem)

A. Deploy an AWS Storage Gateway file gateway on-premises and associate it with an Amazon S3 bucket.

The only thing I could see B is wrong is that you don't need an API call. You just access the files as if it is mounted on your local machine.

Answer is A https://aws.amazon.com/storagegateway/file/: "Move database and file backups into the cloud and free up on-premises storage capacity" "access to these backups for quick recovery" -> S3 is to be used

I was doubting snowball since cost is not an issue . But Snowball transfers the data into amazon S3 first and then if you want to transfer that data to glacier, you need to set up an S3 lifecycle policy to get it into glacier. Hence the option which is correct is A.

Your volumes are stored in an Amazon S3 bucket maintained by the AWS Storage Gateway service. Your volumes are accessible for I/O operations through AWS Storage Gateway. You cannot directly access them using Amazon S3 API actions. You can take point-in-time snapshots of gateway volumes that are made available in the form of Amazon EBS snapshots, which can be turned into either Storage Gateway Volumes or EBS Volumes. Use the File Gateway to work with your data natively in S3. So the answer is A

After reading below, A deemed the best answer https://aws.amazon.com/blogs/storage/back-up-your-on-premises-applications-to-the-cloud-using-aws-storage-gateway/

Answer B

A Because "You cannot directly access them using Amazon S3 API actions" Your volumes are stored in an Amazon S3 bucket maintained by the AWS Storage Gateway service. Your volumes are accessible for I/O operations through AWS Storage Gateway. You cannot directly access them using Amazon S3 API actions.

.......

See File Gateway from https://docs.aws.amazon.com/storagegateway/latest/userguide/WhatIsStorageGateway.html so answer is A

A sounds good to me