DEA-C01 · Question #143
A company is using Amazon Redshift to build a data warehouse solution. The company is loading hundreds of files into a fact table that is in a Redshift cluster. The company wants the data warehouse…
The correct answer is D. Use a single COPY command to load the data into the Redshift cluster. Amazon Redshift's COPY command is purpose-built for bulk data loading and is the most efficient method. A single COPY command automatically parallelizes the load across all cluster nodes and slices when loading multiple files from S3, fully exploiting Redshift's Massively…
Question
A company is using Amazon Redshift to build a data warehouse solution. The company is loading hundreds of files into a fact table that is in a Redshift cluster. The company wants the data warehouse solution to achieve the greatest possible throughput. The solution must use cluster resources optimally when the company loads data into the fact table. Which solution will meet these requirements?
Options
- AUse multiple COPY commands to load the data into the Redshift cluster.
- BUse S3DistCp to load multiple files into Hadoop Distributed File System (HDFS). Use an HDFS
- CUse a number of INSERT statements equal to the number of Redshift cluster nodes. Load the
- DUse a single COPY command to load the data into the Redshift cluster.
How the community answered
(28 responses)- A4% (1)
- B7% (2)
- C4% (1)
- D86% (24)
Explanation
Amazon Redshift's COPY command is purpose-built for bulk data loading and is the most efficient method. A single COPY command automatically parallelizes the load across all cluster nodes and slices when loading multiple files from S3, fully exploiting Redshift's Massively Parallel Processing (MPP) architecture. Using multiple COPY commands (Option A) actually hurts throughput because each COPY command commits a transaction and consumes cluster resources independently, creating overhead and contention. INSERT statements (Option C) are the least efficient method for bulk loads in Redshift. The single COPY command is the AWS-recommended approach precisely because it orchestrates the distributed load internally without extra coordination overhead.
Topics
Community Discussion
No community discussion yet for this question.