Home › Forums › AWS › AWS Certified Solutions Architect Professional › Another wrong answer.. › Reply To: Another wrong answer..
-
Hi AWSPro21,
Thanks for your feedback.
In the given scenario, the company has a large amount of video data stored on tape drives in their on-premises data center. They want to move this data to AWS and also analyze the data to build a metadata library. The scenario also does not specify that the on-premises tape library needs to be replaced. It’s important to understand the difference between the AWS Storage Gateway’s File Gateway and Tape Gateway options and how they align with the company’s requirements.
The AWS Storage Gateway service provides a way to securely move on-premises data to AWS. It offers different types of gateways, including File Gateway and Tape Gateway, each suited for different use cases.
The Tape Gateway is designed to help you move away from physical tapes towards a virtual tape library in the cloud. It’s a great solution if you’re looking to archive data in AWS for long-term retention, typically using Amazon S3 Glacier or Glacier Deep Archive. However, it’s not designed for frequent data access or analysis.
On the other hand, the File Gateway provides a seamless way to connect to the cloud to store application data files and backup images as durable objects on Amazon S3. It provides low-latency access to data through transparent local caching. This means that frequently accessed data is cached on-premises, providing your applications with low-latency access, while securely and durably storing your data in Amazon S3.
In the context of the given question, the company not only wants to move the data to AWS, but they also want to frequently access and analyze the data using Amazon Rekognition. Therefore, the File Gateway would be a more suitable solution because it provides the low-latency access needed for frequent data analysis.
I hope this helps! If you have any more questions, feel free to ask
Best Regards,
JR @ Tutorials Dojo