Exam AWS Certified Solutions Architect - Professional topic 1 question 443 discussion

A A\B: By replacing the physical tape library with file gateway, it has the least amount of management and disruption. It would require us to restore the 30TB to another format (NFS\SMB style) in order to put it on the file gateway which cannot serve as a VTL. I don’t think it’s possible for Amazon Rekognition to process the video in the tape gateway which is on premise or access the data from S3 directly. A: File gateway supports Linux clients connecting to the gateway using Network File System (NFS) versions 3 and 4.1 for Linux clients, and supports Windows clients connecting to the gateway using Server Message Block (SMB) versions 2 and 3. B: No. You cannot access virtual tape data using Amazon S3 or Amazon S3 Glacier APIs. However, you can use the tape gateway APIs to manage your virtual tape library and your virtual tape shelf. https://aws.amazon.com/storagegateway/faqs/?nc=sn&loc=6 C: This is not possible because the data are in tape format. D: This loosk more like the job for Rekognition.

A is wrong. Analysis stored video using AWS Rekognition is an async process. Therefore you need additional component to inject result to the MAM solution. Example here uses SQS and SNS to get the recognition result (https://docs.aws.amazon.com/rekognition/latest/dg/video.html) C is correct as it is almost the same as described here: https://docs.aws.amazon.com/rekognition/latest/dg/streaming-video.html

Tape Gateway: AWS Storage Gateway tape gateway enables you to replace your on-premises tape infrastructure with virtual tape libraries (VTLs) in AWS. It integrates with your existing backup infrastructure and allows you to store and retrieve virtual tapes using Amazon S3 or Glacier storage. Use Case: Tape gateway is suitable when you want to replace or extend your on-premises tape infrastructure with a virtual tape library in AWS. It's commonly used for backup and archiving purposes. File Gateway: AWS Storage Gateway file gateway provides access to your on-premises file-based data through NFS and SMB protocols. It allows you to store files as objects in Amazon S3, while still providing the same file-based access for applications and users. Use Case: File gateway is ideal when you want to integrate your on-premises file-based applications and workflows with AWS storage. It's commonly used for hybrid cloud scenarios, content distribution, and file-based workloads. Then A better than B

A. B was wrong. You cannot process the file on Tape like you do on disk. C is not necessary we don't need real time video processing here. D requires a lot of efforts.

Based on all comments

I don't understand why people are going with B, Answer of this question is definitely A. You can't directly fetch the media files from your tape gateway in real-time since this is backed up using Glacier. People are getting confused with the tape word in question. This problem can't be solved using tape gateway and will need file gateway.

Source for Rekognition is S3 or Kinesis => B wrong, Rekognition can not rertrive video on tape gateway => A and C is right, but "LEAST amount of ongoing management" => pick A, to re-use MAM feature of existing system

C IS CORRECT

My take is that the MAM tool and the company don't "NEED" the archives to be on tape or virtual tape. They are just on tape now as it was a legacy long term storage plan. They simply need the files in S3 and the MAM tools to absorb the metadata from REK. No need for B. Answer A.

Why not B? The MAM software in the question is already designed to work with the existing tape catalog, introducing the File Gateway from the and A would force us to re-write the catalog concept for the MAM app.

B. These movies are archived on tape in an on-premises tape library and accessed using a Media Asset Management (MAM) system. It means after moving to AWS, still use MAM to access the tapes. Tape Gateway enables you to replace using physical tapes on premises with virtual tapes in AWS without changing existing backup workflows

No One really talking about B here ...its shocking.. wht am I missing...? the following picture suggests B is absolutely correct. https://aws.amazon.com/storagegateway/vtl/

A. Set up an AWS Storage Gateway, file gateway appliance on-premises. Use the MAM solution to extract the videos from the current archive and push them into the file gateway. Use the catalog of faces to build a collection in Amazon Rekognition. Build an AWS Lambda function that invokes the Rekognition Javascript SDK to have Rekognition pull the video from the Amazon S3 files backing the file gateway, retrieve the required metadata, and push the metadata into the MAM solution.

archived on tape in an on-premises tape library is keyword, I will go with A

B, there is no need to use Tape at all

I chose A. Although Ans A & C seems good solution. The Kinesis Video Stream usecase is for mostly live streaming (such as Camera). Not sure streaming a file is a good use case. Those who support Option-C, can you please paste the architecture link where Kinesis Video Streams process from Video File?

It's A