How should you store S3 objects to support high request rates?
Short answer
C Store the objects by using object key names distributed across multiple prefixes.
Question
Key Takeaways
The exam tests your understanding that S3 request performance scales with the number of prefixes; the common trap is to confuse storage classes or tagging with performance optimization.
To optimize an S3 bucket for high request rates, distribute object keys across multiple prefixes so request load is spread across partitions. The AWS community strongly supports this approach, citing official performance guidance.
Common mistake: Selecting option A (S3 Intelligent-Tiering) or option B (root of the bucket) is common because they sound like broad optimizations, but S3 Intelligent-Tiering only automates cost savings on storage classes and using a single root prefix actually concentrates requests on one partition, increasing the risk of throttling.
Expert Analysis
Why the Answer Is Correct
Option C is correct because Amazon S3 automatically partitions data based on object key names, and spreading keys across multiple prefixes allows the load to be balanced over a wider range of partitions. This is exactly what the AWS documentation recommends for achieving high request rates. One community comment (likes=3) points to the official docs and highlights that distributing object key names across prefixes spreads load across many partitions.
Why the Other Options Are Wrong
Option A, S3 Intelligent-Tiering, is a storage class that optimizes costs by moving objects between access tiers; it does not affect request partitioning or throughput limits. Option B, storing objects at the root, means all objects share a single prefix, which concentrates traffic on a small number of partitions and can degrade performance under high request rates. Option D, using object tags named 'prefix' with unique values, is not recognized by S3 for partitioning; tagging is for metadata, management, and access control, not for distributing request load.
Community Comment Notes
Comments overwhelmingly support C, with 100% votes for C. One user (likes=3) explicitly mentions that distributing object key names across multiple prefixes ensures load is spread across many partitions. Another commenter (likes=3) shared the official AWS documentation link about optimizing S3 performance, reinforcing that this is the approved approach. No comments support the other options, indicating a clear consensus.
Official Reference
https://docs.aws.amazon.com/AmazonS3/latest/userguide/optimizing-performance.html
This link opens the official vendor documentation in a new tab.
Exam Strategy
When you see a question about high request rates or S3 performance, think about how S3 partitions data by key prefix. Avoid choosing answers that involve storage classes, tags, or simple root storage; the correct solution usually involves distributing object keys across prefixes to utilize parallel partitions.
Community Votes
100% of anonymous learners picked answer C. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 3 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 3
-
cachac 👍 3 Answered CBy distributing object key names across multiple prefixes, you can ensure that the load is spread across many partitions.
-
KarBiswa 👍 3 Answered Chttps://docs.aws.amazon.com/AmazonS3/latest/userguide/optimizing-performance.html
-
65703c1 👍 1 Answered CC is the correct answer.
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All DVA-C02 Questions
Access 100 questions with complete answers and detailed explanations.
View Full DVA-C02 Practice Test →