SAA-C03 · Question #529
A company wants to migrate an Oracle database to AWS. The database consists of a single table that contains millions of geographic information systems (GIS) images that are high resolution and are…
The correct answer is B. Store the images in Amazon S3 buckets. Use Amazon DynamoDB with the geographic code as. The most resilient and scalable architecture for handling millions of high-resolution images with frequent updates is to store the binary images in Amazon S3 and store their metadata or "Store large objects like images in Amazon S3 and use Amazon DynamoDB to store metadata and…
Question
A company wants to migrate an Oracle database to AWS. The database consists of a single table that contains millions of geographic information systems (GIS) images that are high resolution and are identified by a geographic code. When a natural disaster occurs, tens of thousands of images get updated every few minutes. Each geographic code has a single image or row that is associated with it. The company wants a solution that is highly available and scalable during such events. Which solution will meet this requirement?
Options
- AStore the images and geographic codes in a database table. Use Oracle running on an Amazon
- BStore the images in Amazon S3 buckets. Use Amazon DynamoDB with the geographic code as
- CStore the images and geographic codes in an Amazon DynamoDB table. Configure DynamoDB
- DStore the images in Amazon S3 buckets. Store geographic codes and image S3 URLs in a
How the community answered
(42 responses)- A7% (3)
- B69% (29)
- C19% (8)
- D5% (2)
Explanation
The most resilient and scalable architecture for handling millions of high-resolution images with frequent updates is to store the binary images in Amazon S3 and store their metadata or "Store large objects like images in Amazon S3 and use Amazon DynamoDB to store metadata and references. This design pattern is scalable, highly available, and cost-effective." Why B is correct: Amazon S3 is designed for storing large volumes of binary data (images). DynamoDB provides low-latency reads/writes using the geographic code as the partition key. Highly available, serverless, and auto-scaling, suitable for disaster scenarios with bursts of Reduces pressure on the database layer by separating metadata from image storage. Why the others are incorrect: Option A and D: Storing images directly in RDS is expensive, unscalable, and not optimal for Option C: DynamoDB is suitable, but storing actual binary image data in DynamoDB is not best practice due to item size limits (400 KB) and performance concerns.
Community Discussion
No community discussion yet for this question.