Noos
PT EN
RAN-DBDEA-00251
Ranvier · DBDEA

Exam DBDEA Topics: jobs Difficulty: medium

A downstream Lakeflow Job must refresh whenever two specific upstream tables change — sales.orders and sales.returns — but a third table in the same schema, sales.staging, changes constantly and must never trigger the job. How should the table update trigger be configured?

Options (Reading Mode) Click to filter discussion →
  1. A. Monitor the whole sales schema, and cancel any run that was triggered by sales.staging
  2. B. Select sales.orders and sales.returns as the trigger's monitored tables, so only they fire the job
  3. C. Add a filter in the job's first task that checks which table changed before continuing
  4. D. Rely on the default behavior, because table update triggers always watch every table in the source schema
Reveal answer

Correct answer: Select sales.orders and sales.returns as the trigger's monitored tables, so only they fire the job

Reference: https://docs.databricks.com/aws/en/jobs/trigger-table-update

Train this exam on Ranvier →

02 — The Myelin Layer · Canonical Discussion

Where the exam tries to trick you — and how those who passed solved it.

0 Passed

contributed to this question

Answer Distractor Matrix Click an option to filter or open its dissection.
✦ Consolidated Synthesis (Wiki) rev. #1 (baseline) · CC BY-SA 4.0
Start synthesis for this question →

No community synthesis consolidated for this question yet. Below is the verifiable official starting point — if you passed the exam, open the option dissection.

Official Answer (B): Select sales.orders and sales.returns as the trigger's monitored tables, so only they fire the job

Ranvier · DBDEA

Contribute to this Question

Your contribution builds your Orbital Sheath

Peer contributions

No public contribution yet. Be the first who passed to explain why the distractors trick candidates — your contribution builds your Orbital Sheath.