AWS Certified Data Engineer Associate DEA-C01 Practice Question

In Amazon Redshift, a stored procedure automatically runs inside a single implicit transaction. As long as the procedure itself does not issue an explicit COMMIT or ROLLBACK, every statement inside the body is committed (or rolled back) together when the CALL returns. Wrapping the business logic in a PL/pgSQL block that begins with CREATE OR REPLACE PROCEDURE … LANGUAGE plpgsql AS $$ BEGIN and ends with END; $$ keeps the job atomic. Using COMMIT statements inside the procedure, issuing individual UPDATE/DELETE statements from the scheduler, or running multiple CALL commands would each introduce separate transactions and defeat the single-commit requirement.