DBS-C01 Stored Procedures in Redshift Practice Question
A company is migrating a legacy Oracle data warehouse to Amazon Redshift. The source uses complex stored procedures with cursors, temporary tables, and PL/SQL. Which THREE design considerations should the company evaluate?
⚠ Common exam trap
Many exam-takers assume Redshift supports all Oracle database features (like PL/SQL, cursors, and auto-scaling) because both are relational databases, but Redshift is a columnar, MPP data warehouse with significant differences in procedural logic and resource management.
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
✓
Redshift does not support procedural languages like PL/SQL; stored procedures must be rewritten in SQL or Python.
Amazon Redshift does not support Oracle's PL/SQL procedural language; stored procedures must be rewritten using Redshift's PL/pgSQL or Python UDFs (option A). Redshift supports temporary tables, but they are session-scoped and must be explicitly dropped or they persist until session ends (option B). Redshift does not support cursors as in Oracle; result sets must be handled using alternative methods such as fetching into arrays or using LIMIT/OFFSET (option D). These are key migration considerations.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Redshift does not support procedural languages like PL/SQL; stored procedures must be rewritten in SQL or Python.
Why this is correct
Redshift supports PL/pgSQL and Python, but not Oracle's PL/SQL.
- ✓
Redshift supports temporary tables, but they are session-scoped and not automatically dropped in all cases.
Why this is correct
Temporary tables exist for the duration of a session and must be managed carefully.
- ✗
Redshift Concurrency Scaling can handle thousands of concurrent queries.
Why it's wrong here
Concurrency Scaling is a feature for handling spikes, but not a primary migration consideration.
- ✓
Redshift does not support cursors; result sets must be handled differently.
Why this is correct
Cursors are not supported in Redshift; alternative patterns must be used.
- ✗
Redshift automatically scales compute capacity based on workload.
Why it's wrong here
Auto-scaling is not automatic; it requires elastic resize or concurrency scaling configuration.
Go deeper
Related to this question
About these practice questions
Courseiva writes every DBS-C01 question from scratch — 1,663 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This DBS-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 DBS-C01 exam.