Databricks Certified Data Engineer - Associate
Get started today
Ultimate access to all questions.
Deep dive into the quiz with AI chat providers.
We prepare a focused prompt with your quiz and certificate details so each AI can offer a more tailored, in-depth explanation.
Question 35 \
A dataset has been defined using Delta Live Tables and includes an expectations clause:
CONSTRAINT valid_timestamp EXPECT (timestamp > '2020-01-01') \
What is the expected behavior when a batch of data containing data that violates these constraints is processed?
Real Exam
Community
LLeetQuiz
A
Records that violate the expectation are added to the target dataset and recorded as invalid in the event log.
B
Records that violate the expectation are dropped from the target dataset and recorded as invalid in the event log.
C
Records that violate the expectation cause the job to fail.
D
Records that violate the expectation are added to the target dataset and flagged as invalid in a field added to the target dataset.
E
Records that violate the expectation are dropped from the target dataset and loaded into a quarantine table.
Explanation:
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.
Comments
Loading comments...