Question 1,404 of 1,786
Data Store ManagementhardMultiple SelectObjective-mapped

Quick Answer

The best practice for optimizing query performance in Amazon Redshift is to use EVEN distribution for the large fact table 'sales' and interleaved sort keys for fact tables with multiple filter columns. EVEN distribution ensures data is evenly spread across all nodes, preventing data skew and maximizing parallel processing for complex analytical queries. Interleaved sort keys give equal weight to each column—such as date, region, and product—which optimizes zone maps and minimizes scanned data when queries filter on multiple predicates. On the AWS Certified Data Engineer Associate DEA-C01 exam, this tests your understanding of how distribution styles and sort keys directly impact workload performance; a common trap is choosing KEY distribution for a fact table without a natural join column, which can cause skew. Remember the memory tip: "EVEN for facts, interleaved for multi-column filters" to quickly recall the best practice for balancing storage and query speed.

DEA-C01 Data Store Management Practice Question

This DEA-C01 practice question tests your understanding of data store management. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.

A data engineer is setting up an Amazon Redshift cluster for a data warehouse. The cluster will store historical sales data and support complex analytical queries. To optimize query performance and manage storage, the engineer needs to choose appropriate distribution styles and sort keys for a large fact table 'sales' and several dimension tables. Which TWO of the following design decisions are BEST practices?

Clue words in this question

Noticing these words before you look at the options changes how you read each choice.

  • Clue: "best"

    Why it matters: Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.

Question 1hardmulti select
Full question →

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

Use interleaved sort keys on columns that are frequently used in filter predicates (e.g., date, region, product).

Option A is correct because interleaved sort keys in Amazon Redshift give equal weight to each column in the sort key, making them ideal for queries with filter predicates on multiple columns (e.g., date, region, product). This design optimizes zone maps and minimizes the amount of data scanned, significantly improving query performance for complex analytical workloads on large fact tables.

Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • Use interleaved sort keys on columns that are frequently used in filter predicates (e.g., date, region, product).

    Why this is correct

    Interleaved sort keys improve performance for queries filtering on multiple columns.

    Clue confirmation

    The clue word "best" in the question point toward this answer.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Use EVEN distribution for the fact table 'sales' to ensure an even data distribution across all nodes.

    Why this is correct

    EVEN distribution is good for large fact tables when no single key is used for all joins.

    Clue confirmation

    The clue word "best" in the question point toward this answer.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Use ALL distribution for the 'sales' fact table to replicate data to every node and avoid data movement.

    Why it's wrong here

    ALL distribution is for small dimension tables; replicating a large fact table wastes storage.

  • Use a compound sort key with the most frequently filtered column first.

    Why it's wrong here

    Compound sort keys are less effective when queries filter on columns other than the first.

  • Choose AUTO distribution style for all tables and let Amazon Redshift automatically assign distribution.

    Why it's wrong here

    AUTO may not always be optimal; manual selection can be better based on query patterns.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates often confuse EVEN distribution as a universal best practice for all fact tables, overlooking that KEY distribution on the join column is superior for star schema joins, and they may also incorrectly assume ALL distribution is suitable for large fact tables due to its join performance benefits, ignoring the prohibitive storage and write costs.

Detailed technical explanation

How to think about this question

Interleaved sort keys use a modified z-order curve to assign equal priority to each column, enabling efficient range-restricted scans on any subset of the sort key columns. Under the hood, Redshift stores metadata about the minimum and maximum values in each 1 MB block (zone maps); interleaved sorting maximizes the effectiveness of these zone maps when multiple columns are filtered, reducing the number of blocks scanned. In a real-world scenario, a sales fact table with frequent filters on date, region, and product_id would see dramatic I/O reduction with interleaved sort keys compared to a compound sort key, which only optimizes for the leading column.

KKey Concepts to Remember

  • Read the scenario before looking for a memorised answer.
  • Find the constraint that changes the correct option.
  • Eliminate answers that are true in general but not in this case.

TExam Day Tips

  • Watch for words such as best, first, most likely and least administrative effort.
  • Review why wrong options are wrong, not only why the correct option is correct.

Key takeaway

Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Real-world example

How this comes up in practice

A media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.

What to study next

Got this wrong? Here's your next step.

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

Related practice questions

Related DEA-C01 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free DEA-C01 practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this DEA-C01 question test?

Data Store Management — This question tests Data Store Management — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Use interleaved sort keys on columns that are frequently used in filter predicates (e.g., date, region, product). — Option A is correct because interleaved sort keys in Amazon Redshift give equal weight to each column in the sort key, making them ideal for queries with filter predicates on multiple columns (e.g., date, region, product). This design optimizes zone maps and minimizes the amount of data scanned, significantly improving query performance for complex analytical workloads on large fact tables.

What should I do if I get this DEA-C01 question wrong?

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

Are there clue words in this question I should notice?

Yes — watch for: "best". Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.

What is the key concept behind this question?

Read the scenario before looking for a memorised answer.

About these practice questions

Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Same concept, more angles

1 more ways this is tested on DEA-C01

These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.

Variation 1. A data engineering team is managing an Amazon Redshift cluster that is used for BI reporting. The cluster has a mix of large tables (some over 1 TB) and many smaller tables. The team notices that queries on a large fact table are slow. The fact table is distributed using KEY distribution on the customer_id column, which has high cardinality. The team wants to improve query performance. They have the option to change the distribution style and sort key. Which redesign should they implement?

hard
  • A.Keep the distribution style as AUTO and set the sort key to customer_id.
  • B.Change the distribution style to ALL and set the sort key to customer_id.
  • C.Change the distribution style to KEY on a different column with high cardinality.
  • D.Change the distribution style to EVEN and set the sort key to a date column used in WHERE clauses.

Why D: Option D is correct because using EVEN distribution ensures data is evenly distributed across all nodes, avoiding data skew that can occur with KEY distribution on a high-cardinality column like customer_id. Setting the sort key to a date column used in WHERE clauses enables range-restricted scans, significantly reducing the amount of data scanned for common BI queries that filter by date. This combination improves query performance by maximizing parallelism and minimizing I/O.

Keep practising

More DEA-C01 practice questions

Last reviewed: Jun 11, 2026

Question Discussion

Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.

Loading comments…

Sign in to join the discussion.

This DEA-C01 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the DEA-C01 exam.