A news portal is looking for a data store to store 120 GB of metadata about its posts and comments. The posts and comments are not frequently looked up or updated. However, occasional lookups are…

Question

Options

• AUse Amazon DynamoDB with on-demand capacity mode. Purchase reserved capacity.
• BUse Amazon ElastiCache for Redis for data storage. Turn off cluster mode.
• CUse Amazon S3 Standard-Infrequent Access (S3 Standard-IA) for data storage and use Amazon
• DUse Amazon DynamoDB with on-demand capacity mode. Switch the table class to DynamoDB

• A
  9% (4)
• B
  7% (3)
• C
  28% (12)
• D
  56% (24)

Explanation

Option D is correct because DynamoDB Standard-Infrequent Access (Standard-IA) is purpose-built for data that is stored long-term but accessed rarely - it cuts storage costs by roughly 60% compared to the Standard table class while preserving DynamoDB's signature single-digit millisecond read/write latency, satisfying both the cost and performance requirements.

Option A is wrong because reserved capacity applies to provisioned mode, not on-demand mode - combining the two is contradictory, and it also uses the Standard table class, which is more expensive for infrequently accessed data.

Option B is wrong because ElastiCache for Redis is an in-memory cache designed for hot, frequently accessed data; it is far too expensive for 120 GB of rarely touched metadata and is not meant to serve as a primary data store.

Option C is wrong because S3 Standard-IA is object storage optimized for bulk retrieval - it cannot deliver single-digit millisecond latency on individual record lookups, which is a hard requirement here.

Memory tip: Match the "IA" suffix to the use case - whenever a question says data is infrequently accessed but still needs millisecond response times, DynamoDB Standard-IA is the signal word; if milliseconds aren't required, S3-IA becomes the cheaper answer.

No community discussion yet for this question.