DATABRICKS-DEP Question 72

Community Discussion

Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.

• Chose A0

  ,B,D - Correct answer s : A, B, D — Set `sequence_by` to the `_commit_version` column, or a business timestamp, so out-of-order change events apply in true logical order rather than arrival order.; Set `stored_as_scd_type` to `2` so the target table retains a full, queryable history of prior values for each key instead of overwriting the row in place on every update.; Set `apply_as_deletes` to the condition that identifies delete events from the feed, so that deleted source rows are tombstoned and excluded from the current view of the dimension. A . `sequence_by` tells AUTO CDC how to determine the true logical order of events, which is essential when events can arrive out of order. Using the commit version or a business timestamp ensures a late-arriving older change does not incorrectly overwrite a newer one. B . SCD Type 2 is the configuration that tells AUTO CDC to retain historical versions of each row rather than updating in place, which is exactly the historical tracking the dimension table requires. This is the correct setting for the stated requirement. C . AUTO CDC does not infer deletes automatically from any `_change_type` value, including `update_preimage`, which simply represents the pre-change state of an ordinary update. Deletes must be identified explicitly through the `apply_as_deletes` parameter or they will not be applied. D . Explicitly configuring `apply_as_deletes` with the condition that identifies delete events is the documented way to make AUTO CDC tombstone those rows in the target table. Without this configuration, delete events from the source would not be reflected downstream at all. E . SCD Type 1 is the in-place update mode that overwrites the existing row with no retained history, which is the opposite of what preserving full history requires. The dimension table in this scenario needs Type 2, not Type 1, to meet its stated history requirement. F . `keys` identifies the column or columns that uniquely match an incoming change event to an existing target row, not a partitioning hint. Using a non-unique column like `region` would cause unrelated customer records to be incorrectly matched and overwritten.