nerdexam
Amazon

DAS-C01 · Question #179

A company uses Amazon Redshift to store its data. The reporting team runs ad-hoc queries to generate reports from the Amazon Redshift database. The reporting team recently started to experience…

The correct answer is B. Configure automatic workload management (WLM) from the Amazon Redshift console. Configuring automatic WLM (Workload Management) in Amazon Redshift resolves query queue contention. Automatic WLM uses machine learning to dynamically allocate memory and concurrency slots to queries based on their complexity and cluster resources, preventing long-running…

Processing

Question

A company uses Amazon Redshift to store its data. The reporting team runs ad-hoc queries to generate reports from the Amazon Redshift database. The reporting team recently started to experience inconsistencies in report generation. Ad-hoc queries used to generate reports that would typically take minutes to run can take hours to run. A data analytics specialist debugging the issue finds that ad-hoc queries are stuck in the queue behind long-running queries. How should the data analytics specialist resolve the issue?

Options

  • ACreate partitions in the tables queried in ad-hoc queries.
  • BConfigure automatic workload management (WLM) from the Amazon Redshift console.
  • CCreate Amazon Simple Queue Service (Amazon SQS) queues with different priorities. Assign queries to
  • DRun the VACUUM command for all tables in the database.

How the community answered

(15 responses)
  • A
    13% (2)
  • B
    80% (12)
  • C
    7% (1)

Explanation

Configuring automatic WLM (Workload Management) in Amazon Redshift resolves query queue contention. Automatic WLM uses machine learning to dynamically allocate memory and concurrency slots to queries based on their complexity and cluster resources, preventing long-running queries from monopolizing the queue and blocking ad-hoc queries. Manual WLM requires fixed queue configuration, while automatic WLM adapts in real time. Creating table partitions (A) optimizes storage and scan performance but does not address query queue ordering. Amazon SQS (C) is a messaging service unrelated to Redshift query management. The VACUUM command (D) reclaims space and re-sorts rows but has no impact on WLM queue behavior.

Topics

#Amazon Redshift#Workload Management (WLM)#Query Performance#Concurrency Management

Community Discussion

No community discussion yet for this question.

Full DAS-C01 Practice