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?
Redshift supports PL/pgSQL and Python, but not Oracle's PL/SQL.
Why this answer
Amazon Redshift does not support Oracle's PL/SQL procedural language. Stored procedures must be rewritten using Redshift's SQL-based procedural language (PL/pgSQL) or Python (via UDFs). This is a critical migration consideration because complex logic involving loops, conditionals, and error handling must be translated to supported constructs.
Exam trap
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.