A startup runs analytics that sit idle for most of the day, then spike without warning when analysts explore new datasets, sometimes at night or on weekends. The team does not want to size or operate a cluster, and it wants to pay only for the compute its queries actually consume. Which Amazon Redshift configuration meets these requirements?
Choose one.
Redshift Serverless bills for compute only while queries run and scales automatically; provisioned clusters, even with pause/resume or concurrency scaling, are sized and operated by you.
Two constraints decide: unpredictable, intermittent load and pay-per-use with no cluster to operate. Serverless on-demand billing meets both. A pause/resume schedule is the tempting near-twin because it also avoids paying for idle compute, but it only works when idle periods are predictable, and the cluster is still yours to size. A Serverless reservation keeps the no-cluster model but bills its committed RPUs every hour, idle or not. Concurrency scaling optimizes an always-on provisioned cluster.
- Note the load profile: mostly idle, unpredictable spikes.
- Note the operations constraint: no cluster to size or manage.
- Reject provisioned options, including scheduled pause, which needs predictable idle windows.
- Reject commitments such as reservations that bill whether or not queries run.
- Choose Redshift Serverless on-demand, billed per RPU-second while queries run.
Exam tip: Intermittent, unpredictable analytics with no cluster to manage means Redshift Serverless.
Choosing an AWS Data Store: Redshift, DynamoDB, Aurora, S3, and MemoryDB — the lesson that teaches this.