DEA-C01 Question 170
Single answerYou are working as a data engineer for a company that processes large-scale IoT sensor data. The raw data is ingested into an S3 bucket and then processed daily into a data warehouse. However, the processing jobs are taking longer than expected due to high retrieval latency for the raw data stored in S3. Which S3 storage class and configuration should you use to optimize for faster retrieval performance?
- A
S3 Standard with bucket versioning enabled
- B
S3 Intelligent-Tiering with frequent access tiering
- C
S3 Standard with Transfer Acceleration enabled
- D
S3 Standard-IA (Infrequent Access)
Show answer and explanation
Correct answer: C
Explanation
S3 Standard with Transfer Acceleration enabled is the most appropriate configuration for optimizing retrieval performance in this scenario. Transfer Acceleration leverages CloudFront edge locations to reduce data retrieval latency, making it ideal for workloads where fast access to large-scale data is critical, such as daily processing of IoT sensor data. The other options either focus on cost optimization or provide storage solutions not tailored to high-performance frequent access demands.
- A. Incorrect.
S3 Standard with bucket versioning enabled does not optimize retrieval performance. Versioning is primarily used for data recovery and maintaining multiple versions of an object, not for performance improvement.
- B. Incorrect.
S3 Intelligent-Tiering optimizes cost by automatically moving objects between access tiers based on access patterns. While suitable for cost-efficiency, it does not specifically reduce retrieval latency for frequently accessed data.
- C. Correct.
S3 Standard with Transfer Acceleration enabled is the correct choice as Transfer Acceleration uses Amazon CloudFront's globally distributed edge locations to improve upload and download speeds, reducing retrieval latency for large datasets.
- D. Incorrect.
S3 Standard-IA (Infrequent Access) is designed for data that is accessed less frequently but requires rapid retrieval when needed. However, it is not optimized for high-performance frequent access scenarios.