Databricks Certified Data Engineer - Associate

The correct answer is A. Records that violate the expectation are added to the target dataset and recorded as invalid in the event log.

Here's the accurate explanation:

In Delta Live Tables, when you use a basic CONSTRAINT ... EXPECT clause without any additional violation handling, the default behavior is:

• Retention: Records that violate the expectation are still added to the target dataset
• Logging: The violations are recorded as metrics in the event log for monitoring
• Pipeline Continuation: The pipeline continues processing without failing or dropping records

This represents DLT's default "track only" behavior for data quality constraints.

The other options represent different behaviors that require explicit configuration:

• B (dropping records): Would require EXPECT ... ON VIOLATION DROP ROW
• C (failing the job): Would require EXPECT ... ON VIOLATION FAIL UPDATE
• E (quarantine table): Would require custom logic with multiple output targets

Thank you for the correction. The basic EXPECT clause without additional violation handling simply monitors data quality without altering the data flow, making option A the correct answer.