A long ETL load competes with interactive user queries on one Redshift cluster.
Protect short interactive queries without serializing every workload.
Which approach is most appropriate?
Classify workloads with WLM queues, priorities, concurrency limits, and monitoring; compare scaling cost with response targets.
Detailed explanation
Changing storage does not resolve Redshift query-resource contention.
Changing storage does not resolve Redshift query-resource contention.
Workload-specific allocation can protect interactive response time while retaining ETL throughput.
Workload-specific allocation can protect interactive response time while retaining ETL throughput.
ETL can occupy resources and make interactive latency unpredictable.
ETL can occupy resources and make interactive latency unpredictable.
Audit retention does not allocate Redshift query resources.
Audit retention does not allocate Redshift query resources.
Check official documentation
Compare the following points with the official documentation.
Amazon Redshift workload management、query priorities、concurrency scalingの公式説明を確認する。
What to confirm
保存場所の変更とクエリリソース管理の違いを説明できる。
Key points
- WLM
- Priority
- Concurrency Scaling
- Query monitoring
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
SLA separation
Interactive response targets and batch throughput can require different queues.
Cost trade-off
Compare scaling or resize cost with the response-time benefit.