Modernize to DynamoDB and store large videos as S3 objects referenced by key
A company needs to modernize an application and migrate the application to AWS. The application stores user profile data as text in a single table in an on-premises MySQL database. After the modernization, users will use the application to upload video files that are up to 4 GB in size. Other users must be able to download the video files from the application. The company needs a video storage solution that provides rapid scaling. The solution must not affect application performance. Which solution will meet these requirements?
Community Votes
100% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
Binary video content belongs in object storage, not in a database item, and DynamoDB items are limited to 400 KB, so the videos go to S3 and the database stores only the S3 key alongside the profile attributes.
An application stores user profile data as text in a single table in an on-premises MySQL database, and after modernization users will upload video files up to 4 GB that other users must be able to download. The storage solution must scale rapidly and must not affect application performance.
Base64-encoding the videos into a database column. A 4 GB file cannot fit a DynamoDB item at all because items are capped at 400 KB, and even where it could fit, base64 inflates the payload by a third and makes every read of a profile fetch the media, which is precisely the application performance impact the question prohibits.
Community Discussion (4 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
The requirement to scale rapidly without affecting application performance points at separating the media from the record. DynamoDB is a NoSQL database that handles the key-value profile data and the modernized access patterns with on-demand capacity, and the AWS Schema Conversion Tool assists the DMS migration from the MySQL schema. The videos go into Amazon S3, which stores objects of any size up to 5 TB and scales without provisioning, and the DynamoDB item holds only the S3 key. Downloads are then served directly from S3, so the database never carries the media traffic and application performance is unaffected by video volume.Why the Other Options Are Wrong
A: Migrating to Aurora PostgreSQL and base64-encoding videos into a TEXT column is a non-starters for 4 GB objects, since a single item of that size is not supported and the base64 overhead alone would be roughly a third larger than the original file, plus every profile read would drag the media through the database. D: The same base64 problem applies to DynamoDB, and it is more severe because a DynamoDB item is limited to 400 KB, so a 4 GB video cannot be stored as an attribute at all. C: Amazon Keyspaces is a wide-column store for Apache Cassandra workloads, which is not a match for this application's data model, and the choice adds a migration target with no benefit over DynamoDB for this access pattern.Community Comment Notes
The community voted 100 to 0 for B, with commenters pointing out that a 4 GB file size rules out storing the video in the database and that Amazon Keyspaces is not relevant to this scenario, and another noting that S3 handles the storage while DynamoDB holds the metadata and the S3 key.Official Reference
Related Analysis
Practice All SAP-C02 Questions
Access 85 questions with complete answers and detailed explanations.
View Full SAP-C02 Practice Test →