CDC & lake sinks — Debezium changelog to Iceberg, commit on checkpoint, schema evolution

6 h
requires FLK-04
requires FLK-06

From your world. loading your lakehouse: a CDC feed from an operational database landing as an upserted Iceberg table your dbt models read

Practice quiz with instant feedback. For a scored run that counts toward your local progress, use uv run de quiz FLK-10.

6What is the correct way to feed a deterministic CDC changelog into Flink for testing, without Docker? AA live Postgres with Debezium running in Docker BA file (or Kafka topic on a native broker) of Debezium-JSON envelopes that the built-in debezium-json format reads CA random data generator DThere is no way without Docker

7A Flink Iceberg CDC job crashes and recovers from its last checkpoint. Why does the job not commit rows twice to the table? AThe sink de-duplicates by scanning the whole table BThe sink commits idempotently for each checkpoint id. On recovery, it does not apply again a snapshot for a checkpoint that it already committed CIceberg forbids duplicate rows DFlink disables checkpointing after a crash

8Which are good reasons to prefer a continuous Flink CDC → Iceberg job to a nightly batch MERGE? Select all that apply. (select all that apply) AThe target stays continuously current. It is not up to a day old BExactly-once commit-on-checkpoint gives a clean snapshot history CIt is always cheaper to operate than batch for tiny, rarely-changing tables DIt handles updates and deletes by primary key, and not only appends