The answer provided for challenge 1 was A: "use snowball to pre-load the SAN data into AWS S3 buckets, then setup Storage Gateway Volume Store to keep the SAN in sync." This is not correct.
Storage Gateway Volumes are stored as EBS Snapshots in S3, but the end-user does not have access to those S3 buckets – they are part of the service and not accessible in the user account, so you can’t preload these from the Snowball.
Only a file gateway permits you to access the backing store in S3 as it uses an S3 bucket you configure, in your account. If the answer was a file gateway, that could work, but not a volume gateway.
See the storagegateway FAQ ("Q. When I look in Amazon S3 why can’t I see my volume data?") or even the description in user guide for Volume gateways.
Answer A can’t work.
Hi RR Kras,
Good catch there, your eye for detail will serve you well on the exam. I think at one time, I had that answer as incorrect due to exactly the reason you mention, but guess I changed it over and failed to notice the error part. I needed to edit that video anyway as EFS now has lifecycle features. It’s been updated.
Just looked over the A answer and although you have changed this, File Gateway mode isn’t going to work with a SAN since traditionally they are block storage therefore what file shares are you referring to?
I immediately discounted this answer since Files don’t have anything to do with the SAN itself.