100% Latest & Updated Databricks Certified Data Engineer Associate Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 290
A payments silver table must never have negative approved transaction amounts. Which setup step most directly realizes the proposed design?
- Cast the measurement to numeric and use filter on the validated threshold predicate.
- Read the bronze Delta table with PySpark, use explicit casts and normalization, quarantine invalid keys, and write a separate governed silver table.
- Select compatible columns and apply unionByName with an explicit schema contract.
- Implement an amount >= 0 validation and define an explicit fail or quarantine action.
Explanation
Correct Answer
D:Implement an amount >= 0 validation and define an explicit fail or quarantine action. A crafted negative amount is rejected or quarantined and never reaches gold.
Incorrect Answers
A:If a bronze telemetry table must expose only current readings above a threshold for a dashboard, “Cast the measurement to numeric and use filter on the validated threshold predicate” may be the appropriate response. Implement an amount >= 0 validation and define an explicit fail or quarantine action.
B:A retail bronze orders table contains string totals, inconsistent country codes and missing order identifiers before a silver SLA can begin. In those circumstances, “Read the bronze Delta table with PySpark, use explicit casts and normalization, quarantine invalid keys, and write a separate governed silver table” fits. Implement an amount >= 0 validation and define an explicit fail or quarantine action.
C:When two quarterly datasets have identical columns but their records must be vertically appended and duplicates preserved, “Select compatible columns and apply unionByName with an explicit schema contract” could be relevant. Implement an amount >= 0 validation and define an explicit fail or quarantine action.
Question 291
A payments silver table must never have negative approved transaction amounts. What is the most relevant verification evidence for this case?
- Comparable runs use useful parallel tasks with lower total overhead.
- The revoked identifiers are absent, and nonrevoked source customers remain.
- A crafted negative amount is rejected or quarantined and never reaches gold.
- The executed plan shows a broadcast join and no large dimension repartition overhead.
Explanation
Correct Answer
C:A crafted negative amount is rejected or quarantined and never reaches gold.
Incorrect Answers
A:A Spark job has many tiny input partitions and inefficient parallel task utilization. In those circumstances, “Comparable runs use useful parallel tasks with lower total overhead” fits. A crafted negative amount is rejected or quarantined and never reaches gold.
B:When a GDPR deletion feed requires excluding rows whose identifiers appear on a revoked-consent list, “The revoked identifiers are absent, and nonrevoked source customers remain” could be relevant. A crafted negative amount is rejected or quarantined and never reaches gold.
D:A small static country table enriches a huge events DataFrame and a large shuffle must be avoided when eligible. In those circumstances, “The executed plan shows a broadcast join and no large dimension repartition overhead” fits. A crafted negative amount is rejected or quarantined and never reaches gold.
Question 292
A payments silver table must never have negative approved transaction amounts. The team observes: An invalid negative amount appears in a reporting aggregate. What is the most likely mechanism behind the observed defect?
- The split expression or output indexing was incorrect.
- The validation checked data type but not the amount domain rule.
- The transform used a left outer join or failed to filter unmatched records.
- The transform interpreted local clock text without its source offset.
Explanation
Correct Answer
B:The validation checked data type but not the amount domain rule. Implement an amount >= 0 validation and define an explicit fail or quarantine action.
Incorrect Answers
A:When a source field packs a city and postal code with a single pipe delimiter, “The split expression or output indexing was incorrect” could be relevant. The validation checked data type but not the amount domain rule.
C:A product-order dataset needs one enriched row only when a matching dimension key exists. In those circumstances, “The transform used a left outer join or failed to filter unmatched records” fits. The validation checked data type but not the amount domain rule.
D:When a payroll bronze table has event timestamps saved as arbitrary text from two time zones, “The transform interpreted local clock text without its source offset” could be relevant. The validation checked data type but not the amount domain rule.
Question 293
An insurance gold fact table combines multiple silver sources with different dates and must remain reconcilable. Which approach most directly satisfies the requirement?
- Validate source-to-target row and amount reconciliation at the business grain.
- Apply a row filter with a typed comparison before serving the data.
- Validate currencies and join the approved conversion reference before writing standardized silver amounts.
- Split the field into separate city and postal-code columns with a validated schema.
Explanation
Correct Answer
A:Validate source-to-target row and amount reconciliation at the business grain. Sample control totals match by period and partition without unexplained duplicate keys.
Incorrect Answers
B:A bronze telemetry table must expose only current readings above a threshold for a dashboard. In those circumstances, “Apply a row filter with a typed comparison before serving the data” fits. Validate source-to-target row and amount reconciliation at the business grain.
C:When a marketing bronze feed arrives with mixed currency columns, but conversion rates are supplied in a governed reference table, “Validate currencies and join the approved conversion reference before writing standardized silver amounts” could be relevant. Validate source-to-target row and amount reconciliation at the business grain.
D:If a source field packs a city and postal code with a single pipe delimiter, “Split the field into separate city and postal-code columns with a validated schema” may be the appropriate response. Validate source-to-target row and amount reconciliation at the business grain.
Question 294
An insurance gold fact table combines multiple silver sources with different dates and must remain reconcilable. Which configuration or engineering action would most directly implement the requirement?
- Join by currency and effective date, reject unmatched rates, and create typed base-currency amount columns.
- Measure dimension size and tune the broadcast threshold or apply an eligible hint only if memory fits.
- Compare approved source totals and unique keys to the aggregated gold results under the same time window.
- Use select on an allowlist or drop the disallowed columns before writing the table.
Explanation
Correct Answer
C:Compare approved source totals and unique keys to the aggregated gold results under the same time window. Sample control totals match by period and partition without unexplained duplicate keys.
Incorrect Answers
A:A marketing bronze feed arrives with mixed currency columns, but conversion rates are supplied in a governed reference table. In those circumstances, “Join by currency and effective date, reject unmatched rates, and create typed base-currency amount columns” fits. Compare approved source totals and unique keys to the aggregated gold results under the same time window.
B:When a large fact-to-small-dimension join repeatedly performs an avoidable shuffle, “Measure dimension size and tune the broadcast threshold or apply an eligible hint only if memory fits” could be relevant. Compare approved source totals and unique keys to the aggregated gold results under the same time window.
D:An account table has three irrelevant vendor-internal columns that must not reach the published silver table. In those circumstances, “Use select on an allowlist or drop the disallowed columns before writing the table” fits. Compare approved source totals and unique keys to the aggregated gold results under the same time window.
Question 295
An insurance gold fact table combines multiple silver sources with different dates and must remain reconcilable. Which test would establish that the change worked as intended?
- The approximate count is within the accepted tolerance of an exact sample benchmark.
- Sample control totals match by period and partition without unexplained duplicate keys.
- Only new eligible event rows advance the target after a restart.
- An audit sample reproduces each converted value using the effective-date exchange rate.
Explanation
Correct Answer
B:Sample control totals match by period and partition without unexplained duplicate keys.
Incorrect Answers
A:When a reporting table must count unique devices across billions of events with an acceptable approximation, “The approximate count is within the accepted tolerance of an exact sample benchmark” could be relevant. Sample control totals match by period and partition without unexplained duplicate keys.
C:A downstream pipeline needs incremental consumption of a continuous events feed into a governed table. In those circumstances, “Only new eligible event rows advance the target after a restart” fits. Sample control totals match by period and partition without unexplained duplicate keys.
D:When a marketing bronze feed arrives with mixed currency columns, but conversion rates are supplied in a governed reference table, “An audit sample reproduces each converted value using the effective-date exchange rate” could be relevant. Sample control totals match by period and partition without unexplained duplicate keys.
Question 296
An insurance gold fact table combines multiple silver sources with different dates and must remain reconcilable. The team observes: The gold report doubles some claims despite valid individual source rows. Which configuration or design gap best explains the symptom?
- Silver was written before applying the reference normalization mapping.
- The default shuffle partition count was unsuitable for this workload.
- The completed count was computed as COUNT(*) without checking status.
- The joining and aggregation grain created many-to-many duplication without reconciliation checks.
Explanation
Correct Answer
D:The joining and aggregation grain created many-to-many duplication without reconciliation checks. Compare approved source totals and unique keys to the aggregated gold results under the same time window.
Incorrect Answers
A:If a CRM ingestion contains two representations of the same state name and optional phone fields that are sometimes null, “Silver was written before applying the reference normalization mapping” may be the appropriate response. The joining and aggregation grain created many-to-many duplication without reconciliation checks.
B:A heavily shuffled ETL join creates thousands of tiny shuffle partitions while tasks spend time scheduling. In those circumstances, “The default shuffle partition count was unsuitable for this workload” fits. The joining and aggregation grain created many-to-many duplication without reconciliation checks.
C:When a service operations report must count completed deliveries separately from all attempted deliveries, “The completed count was computed as COUNT(*) without checking status” could be relevant. The joining and aggregation grain created many-to-many duplication without reconciliation checks.
Question 297
An upstream extraction occasionally fails with a transient network error and finance needs an automatic bounded retry before downstream reports run. Which architecture or engineering decision best fits this scenario?
- Prefer a data-driven table trigger to guessing the completion time with cron.
- Use Lakeflow Jobs task retry policies instead of manually restarting the whole workflow.
- Use a scheduled Lakeflow Jobs trigger in the intended time zone.
- Use a pipeline task with a dependency on the validation notebook task.
Explanation
Correct Answer
B:Use Lakeflow Jobs task retry policies instead of manually restarting the whole workflow. A simulated transient error retries within policy and downstream tasks begin only after success.
Incorrect Answers
A:A pipeline should start only when a nightly upstream table update is complete, but the update time varies. In those circumstances, “Prefer a data-driven table trigger to guessing the completion time with cron” fits. Use Lakeflow Jobs task retry policies instead of manually restarting the whole workflow.
C:If a regulated daily ledger load must run at 02:00 in the business time zone even with no new files, “Use a scheduled Lakeflow Jobs trigger in the intended time zone” may be the appropriate response. Use Lakeflow Jobs task retry policies instead of manually restarting the whole workflow.
D:A Lakeflow Spark Declarative Pipeline must be refreshed only after a file validation notebook succeeds. In those circumstances, “Use a pipeline task with a dependency on the validation notebook task” fits. Use Lakeflow Jobs task retry policies instead of manually restarting the whole workflow.
Question 298
An upstream extraction occasionally fails with a transient network error and finance needs an automatic bounded retry before downstream reports run. Which implementation step is most appropriate before production use?
- Set an appropriate scheduled trigger and verify required upstream availability before the cutoff.
- Configure the monitored volume or external location and validate file-arrival trigger access.
- Set the extraction task max retries and suitable backoff while keeping its writes idempotent.
- Set the dependency and valid run-if behavior on the dashboard task.
Explanation
Correct Answer
C:Set the extraction task max retries and suitable backoff while keeping its writes idempotent. A simulated transient error retries within policy and downstream tasks begin only after success.
Incorrect Answers
A:When an accounts pipeline runs once on the first business day and data is available before a fixed cutoff, “Set an appropriate scheduled trigger and verify required upstream availability before the cutoff” could be relevant. Set the extraction task max retries and suitable backoff while keeping its writes idempotent.
B:If a landing volume receives source files at unpredictable hours and processing should start on arrival, “Configure the monitored volume or external location and validate file-arrival trigger access” may be the appropriate response. Set the extraction task max retries and suitable backoff while keeping its writes idempotent.
D:When a dashboard refresh task should not run if an upstream pipeline task failed its quality check, “Set the dependency and valid run-if behavior on the dashboard task” could be relevant. Set the extraction task max retries and suitable backoff while keeping its writes idempotent.
Question 299
An upstream extraction occasionally fails with a transient network error and finance needs an automatic bounded retry before downstream reports run. Which acceptance test provides the strongest evidence that the intended outcome has been achieved?
- The query task executes under the configured identity and writes the expected results.
- Two nearby trigger events do not execute conflicting copies over the same output partition simultaneously.
- The run graph shows the selected task types in the intended execution order.
- A simulated transient error retries within policy and downstream tasks begin only after success.
Explanation
Correct Answer
D:A simulated transient error retries within policy and downstream tasks begin only after success.
Incorrect Answers
A:If a SQL-only analytics team needs to run a saved query as part of a governed batch job, “The query task executes under the configured identity and writes the expected results” may be the appropriate response. A simulated transient error retries within policy and downstream tasks begin only after success.
B:An expensive batch that runs for hours must avoid overlapping with its next schedule occurrence. In those circumstances, “Two nearby trigger events do not execute conflicting copies over the same output partition simultaneously” fits. A simulated transient error retries within policy and downstream tasks begin only after success.
C:When a weekly pipeline needs a Python notebook for extraction, SQL for transformation and a dashboard refresh after both, “The run graph shows the selected task types in the intended execution order” could be relevant. A simulated transient error retries within policy and downstream tasks begin only after success.
Question 300
An upstream extraction occasionally fails with a transient network error and finance needs an automatic bounded retry before downstream reports run. The team observes: A temporary source timeout leaves the report chain permanently failed after one attempt. Which root cause should be addressed first given this evidence?
- The schedule was configured without the business time zone.
- The notebook never published the named task value required by the downstream condition.
- The extraction task had no appropriate retry configuration.
- A table-update trigger was used despite an unconditional time-bound reporting obligation.
Explanation
Correct Answer
C:The extraction task had no appropriate retry configuration. Set the extraction task max retries and suitable backoff while keeping its writes idempotent.
Incorrect Answers
A:A regulated daily ledger load must run at 02:00 in the business time zone even with no new files. In those circumstances, “The schedule was configured without the business time zone” fits. The extraction task had no appropriate retry configuration.
B:When a source notebook should output a small validated row-count value used by a later condition task, “The notebook never published the named task value required by the downstream condition” could be relevant. The extraction task had no appropriate retry configuration.
D:An analytics report must be published every morning regardless of whether source tables changed overnight. In those circumstances, “A table-update trigger was used despite an unconditional time-bound reporting obligation” fits. The extraction task had no appropriate retry configuration.
Certified Data Engineer Associate Practice Tests