- A
Redshift does not support procedural languages like PL/SQL; stored procedures must be rewritten in SQL or Python.
Redshift supports PL/pgSQL and Python, but not Oracle's PL/SQL.
- B
Redshift supports temporary tables, but they are session-scoped and not automatically dropped in all cases.
Temporary tables exist for the duration of a session and must be managed carefully.
- C
Redshift Concurrency Scaling can handle thousands of concurrent queries.
Why wrong: Concurrency Scaling is a feature for handling spikes, but not a primary migration consideration.
- D
Redshift does not support cursors; result sets must be handled differently.
Cursors are not supported in Redshift; alternative patterns must be used.
- E
Redshift automatically scales compute capacity based on workload.
Why wrong: Auto-scaling is not automatic; it requires elastic resize or concurrency scaling configuration.
DBS-C01 Stored Procedures in Redshift Practice Question
This DBS-C01 practice question tests your understanding of workload-specific database design. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. A key principle to apply: stored Procedures in Redshift. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
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?
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.
Key principle: Stored Procedures in Redshift
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.
Related concept
Stored Procedures in Redshift
- ✓
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.
Related concept
Stored Procedures in Redshift
- ✗
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.
Related concept
Stored Procedures in Redshift
- ✗
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.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates 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.
Detailed technical explanation
How to think about this question
Redshift's procedural language for stored procedures is based on PL/pgSQL, which supports variables, cursors (via FOR loops), and exception handling, but it lacks Oracle-specific features like autonomous transactions or bulk collect. Temporary tables in Redshift are session-scoped and are automatically dropped when the session ends, but if a session is reused (e.g., via connection pooling), they persist until explicitly dropped, which can cause naming conflicts or stale data. Cursors in Redshift are supported only within stored procedures using DECLARE CURSOR, but they are read-only and cannot be used for positioned updates; result sets from queries must be consumed via FETCH or by returning a REFCURSOR.
KKey Concepts to Remember
- Stored Procedures in Redshift
- Temporary Tables in Redshift
- Cursor Support in Redshift
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Stored Procedures in Redshift
Real-world example
How this comes up in practice
An e-commerce site experiences heavy traffic on Black Friday and near-zero traffic during off-peak weeks. Rather than provisioning permanent large VMs, the team uses auto-scaling groups that add capacity automatically under load and reduce it overnight. Questions like this test whether you understand elasticity, availability zones, and cloud compute scaling patterns.
What to study next
Got this wrong? Here's your next step.
Review stored Procedures in Redshift, then practise related DBS-C01 questions on the same topic to reinforce the concept.
- →
Workload-Specific Database Design — study guide chapter
Learn the concepts, then practise the questions
- →
Workload-Specific Database Design practice questions
Targeted practice on this topic area only
- →
All DBS-C01 questions
1,730 questions across all exam domains
- →
AWS Certified Database Specialty DBS-C01 study guide
Full concept coverage aligned to exam objectives
- →
DBS-C01 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related DBS-C01 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Workload-Specific Database Design practice questions
Practise DBS-C01 questions linked to Workload-Specific Database Design.
Deployment and Migration practice questions
Practise DBS-C01 questions linked to Deployment and Migration.
Management and Operations practice questions
Practise DBS-C01 questions linked to Management and Operations.
Monitoring and Troubleshooting practice questions
Practise DBS-C01 questions linked to Monitoring and Troubleshooting.
Database Security practice questions
Practise DBS-C01 questions linked to Database Security.
DBS-C01 fundamentals practice questions
Practise DBS-C01 questions linked to DBS-C01 fundamentals.
DBS-C01 scenario practice questions
Practise DBS-C01 questions linked to DBS-C01 scenario.
DBS-C01 troubleshooting practice questions
Practise DBS-C01 questions linked to DBS-C01 troubleshooting.
Practice this exam
Start a free DBS-C01 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this DBS-C01 question test?
Workload-Specific Database Design — This question tests Workload-Specific Database Design — Stored Procedures in Redshift.
What is the correct answer to this question?
The correct answer is: 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.
What should I do if I get this DBS-C01 question wrong?
Review stored Procedures in Redshift, then practise related DBS-C01 questions on the same topic to reinforce the concept.
What is the key concept behind this question?
Stored Procedures in Redshift
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Keep practising
More DBS-C01 practice questions
- A company is deploying a new application on Amazon RDS for PostgreSQL. The security policy requires that all data be enc…
- Match each AWS service to its primary purpose.
- A financial services company runs a production Amazon Aurora MySQL database cluster (1 writer, 2 readers) in us-east-1.…
- A company is designing a database for a global e-commerce platform that requires low-latency reads and writes from multi…
- A security auditor reviews the output of a DynamoDB table description command as shown in the exhibit. Which statement a…
- A company is migrating an on-premises Oracle database to Amazon RDS for Oracle. The database contains sensitive data tha…
Last reviewed: Jun 24, 2026
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.