Compliance requires that every payment amount be non-negative. An engineer runs the statement below on a Delta table that already holds millions of historical rows, including negative refunds imported from a legacy migration: ```sql ALTER TABLE catalog.finance.payments ADD CONSTRAINT chk_amount CHECK (amount >= 0); ``` What is the outcome of this statement, and why?

1. A. It succeeds — the CHECK applies only to rows written after it is added, and existing rows are never re-validated against it 💬 A
2. B. It fails with a parse error — CHECK constraints are not supported on Delta tables, where only NOT NULL can be enforced 💬 B
3. C. It succeeds — the constraint is created in a disabled, logging-only state and only starts validating once it is enabled 💬 C
4. D. It fails — ADD CONSTRAINT verifies every existing row against the CHECK, and the negative rows block it until they are corrected or removed ✓ D

Revelar gabarito

Resposta correta: It fails — ADD CONSTRAINT verifies every existing row against the CHECK, and the negative rows block it until they are corrected or removed

Referência: https://docs.databricks.com/aws/en/tables/constraints