Q48 — AWS SAA-C03 Ch.15
Question 48 of 100 | ← Chapter 15
Q1148. A company is using an Amazon Redshift cluster to run analytics queries for multiple sales teams. In addition to the typical workload, on the last Monday morning of each month, thousands of users run reports. Users have reported slow response times during the monthly surge.The company must improve query performance without impacting the availability of the Redshift cluster.Which solution will meet these requirements?
- A. Resize the Redshift cluster by using the classic resize capability of Amazon Redshift before every monthly surge. Reduce the cluster to its original size after each surge.
- B. Resize the Redshift cluster by using the elastic resize capability of Amazon Redshift before every monthly surge. Reduce the cluster to its original size after each surge.
- C. Enable the concurrency scaling feature for the Redshift cluster for specific workload management (WLM) queues. ✓
- D. Enable Amazon Redshift Spectrum for the Redshift cluster before every monthly surge.
Correct Answer: C. Enable the concurrency scaling feature for the Redshift cluster for specific workload management (WLM) queues.
Explanation
To address the performance issues during the monthly surge in report usage while maintaining cluster availability, let's evaluate the options:Key Requirements:Improve query performance during the monthly surge.Not impact the availability of the Redshift cluster.Cost-effective (resizing manually every month is cumbersome and may not be ideal).Option Analysis:A. Resize the Redshift cluster using classic resize before every monthly surge, then reduce it afterward. Classic resize requires the cluster to be unavailable during the resize operation (it creates a new cluster and copies data). This violates the "no impact on availability" requirement.This is not a good solution.B. Resize the Redshift cluster using elastic resize before every monthly surge, then reduce it afterward. Elastic resize is faster than classic resize and does not require the cluster to be unavailable (though there may be a brief pause). However, it still involves manual intervention, is not instantaneous, and may incur costs for the larger cluster size when not needed.This is better than classic resize but still not ideal for recurring, predictable workloads. C. Enable the concurrency scaling feature for the Redshift cluster for specific workload management (WLM) queues.Concurrency scaling automatically adds transient clusters to handle spikes in query workload without affecting the main cluster's availability. It is ideal for predictable spikes (like monthly reporting) and does not require manual resizing.This is the best solution for the given requirements.D. Enable Amazon Redshift Spectrum before every monthly surge. Redshift Spectrum allows querying data directly from S3, reducing the load on the Redshift cluster. However, it is not a direct solution for improving query performance on the Redshift cluster itself (it offloads queries to S3, which may or may not help depending on the workload). It also requires manual setup and is not a drop-in solution for improving concurrency.This is not the best fit for the described problem.Correct Answer:C. Enable the concurrency scaling feature for the Redshift cluster for specific workload management (WLM) queues.This solution automatically handles the surge in queries without manual intervention, maintains cluster availability, and is cost-effective for predictable spikes.The solution that best meets the requirements for improving query performance during the monthly surge without impacting the availability of the Redshift cluster is:C. Enable the concurrency scaling feature for the Redshift cluster for specific workload management (WLM) queues.Concurrency Scaling: This feature automatically adds transient capacity to handle increased workloads, allowing more queries to run simultaneously without impacting the performance of the main cluster. Workload Management (WLM): By configuring WLM queues appropriately, you can prioritize critical queries and ensure that the system can handle the surge in report generation effectively.This approach allows the company to manage peak loads efficiently while maintaining availability and performance.