100% Latest & Updated Databricks Certified Data Engineer Associate Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 220
A source field packs a city and postal code with a single pipe delimiter. The team observes: The postal code retains the city prefix after transformation. Which root cause should be addressed first given this evidence?
- The quality transform filtered rows without recording rejected records.
- An inner join unintentionally dropped unmatched left rows.
- The split expression or output indexing was incorrect.
- The pipeline used duplicate-eliminating UNION rather than UNION ALL semantics.
Explanation
Correct Answer
C:The split expression or output indexing was incorrect. Use split with the literal delimiter, trim both elements, and handle malformed input explicitly.
Incorrect Answers
A:When a silver quality gate must reject records missing a transaction identifier, but analysts still need an error count, “The quality transform filtered rows without recording rejected records” could be relevant. The split expression or output indexing was incorrect.
B:If a subscriptions dataset must preserve every account even when no payment has arrived, “An inner join unintentionally dropped unmatched left rows” may be the appropriate response. The split expression or output indexing was incorrect.
D:When two quarterly datasets have identical columns but their records must be vertically appended and duplicates preserved, “The pipeline used duplicate-eliminating UNION rather than UNION ALL semantics” could be relevant. The split expression or output indexing was incorrect.
Question 221
A customer schema is changing from old_customer_id to customer_id while dashboards expect the new name. Which technical design is most appropriate for the stated constraint?
- Use UNION ALL or DataFrame unionByName rather than a relational join.
- Rename the column while preserving values and documenting dependent consumers.
- Keep all landing events in bronze while writing validated and keyed latest records into silver.
- Apply a deliberate cross join to form a bounded Cartesian product.
Explanation
Correct Answer
B:Rename the column while preserving values and documenting dependent consumers. The schema exposes customer_id and its values match the old identifier set.
Incorrect Answers
A:If two quarterly datasets have identical columns but their records must be vertically appended and duplicates preserved, “Use UNION ALL or DataFrame unionByName rather than a relational join” may be the appropriate response. Rename the column while preserving values and documenting dependent consumers.
C:When a health feed has duplicate late-arrival patient observations but raw arrivals must remain reviewable, “Keep all landing events in bronze while writing validated and keyed latest records into silver” could be relevant. Rename the column while preserving values and documenting dependent consumers.
D:If a risk team needs all combinations of five scenario assumptions and six stress categories, “Apply a deliberate cross join to form a bounded Cartesian product” may be the appropriate response. Rename the column while preserving values and documenting dependent consumers.
Question 222
A customer schema is changing from old_customer_id to customer_id while dashboards expect the new name. Which action should the engineer perform to establish the intended control?
- Join on the product key with an inner join and select the disambiguated columns.
- Use withColumnRenamed or an equivalent SELECT alias and update the governed silver target.
- Join accounts LEFT OUTER JOIN payments on account_id and preserve missing payment fields.
- Supply both key equality predicates to the Spark join condition.
Explanation
Correct Answer
B:Use withColumnRenamed or an equivalent SELECT alias and update the governed silver target. The schema exposes customer_id and its values match the old identifier set.
Incorrect Answers
A:A product-order dataset needs one enriched row only when a matching dimension key exists. In those circumstances, “Join on the product key with an inner join and select the disambiguated columns” fits. Use withColumnRenamed or an equivalent SELECT alias and update the governed silver target.
C:If a subscriptions dataset must preserve every account even when no payment has arrived, “Join accounts LEFT OUTER JOIN payments on account_id and preserve missing payment fields” may be the appropriate response. Use withColumnRenamed or an equivalent SELECT alias and update the governed silver target.
D:A customer match requires both organization identifier and customer identifier, since a customer number is reused by different businesses. In those circumstances, “Supply both key equality predicates to the Spark join condition” fits. Use withColumnRenamed or an equivalent SELECT alias and update the governed silver target.
Question 223
A customer schema is changing from old_customer_id to customer_id while dashboards expect the new name. Which observation best proves the workload meets its requirement?
- Queries reflect permitted underlying table changes at query time.
- The accepted plus rejected counts reconcile to the original source batch.
- Equivalent instants from different offsets compare equal and raw source text remains available.
- The schema exposes customer_id and its values match the old identifier set.
Explanation
Correct Answer
D:The schema exposes customer_id and its values match the old identifier set.
Incorrect Answers
A:When a finance dashboard reads a curated metric that should always reflect the latest base table without storing a separately maintained aggregate, “Queries reflect permitted underlying table changes at query time” could be relevant. The schema exposes customer_id and its values match the old identifier set.
B:If a silver quality gate must reject records missing a transaction identifier, but analysts still need an error count, “The accepted plus rejected counts reconcile to the original source batch” may be the appropriate response. The schema exposes customer_id and its values match the old identifier set.
C:A payroll bronze table has event timestamps saved as arbitrary text from two time zones. In those circumstances, “Equivalent instants from different offsets compare equal and raw source text remains available” fits. The schema exposes customer_id and its values match the old identifier set.
Question 224
A customer schema is changing from old_customer_id to customer_id while dashboards expect the new name. The team observes: The dashboard cannot resolve the required customer_id column after deployment. Which underlying cause most directly explains this failure?
- The join predicate used customer_id alone, omitting organization_id.
- The denominator included rows without a valid numeric price.
- An equijoin or filtering condition unintentionally removed Cartesian pairs.
- The pipeline left the legacy column name or dropped it without a replacement.
Explanation
Correct Answer
D:The pipeline left the legacy column name or dropped it without a replacement. Use withColumnRenamed or an equivalent SELECT alias and update the governed silver target.
Incorrect Answers
A:If a customer match requires both organization identifier and customer identifier, since a customer number is reused by different businesses, “The join predicate used customer_id alone, omitting organization_id” may be the appropriate response. The pipeline left the legacy column name or dropped it without a replacement.
B:A sales dashboard needs mean transaction value per region while excluding null prices. In those circumstances, “The denominator included rows without a valid numeric price” fits. The pipeline left the legacy column name or dropped it without a replacement.
C:When a risk team needs all combinations of five scenario assumptions and six stress categories, “An equijoin or filtering condition unintentionally removed Cartesian pairs” could be relevant. The pipeline left the legacy column name or dropped it without a replacement.
Question 225
A GDPR deletion feed requires excluding rows whose identifiers appear on a revoked-consent list. Which design choice best addresses the stated business and technical requirement?
- Enforce numeric conversion and an allowed sensor range during the bronze-to-silver transform.
- Create a silver projection that casts monetary values, normalizes country codes and rejects missing required keys without overwriting bronze.
- Apply a left anti join or equivalent NOT EXISTS with the consent-revocation keys.
- Apply a deliberate cross join to form a bounded Cartesian product.
Explanation
Correct Answer
C:Apply a left anti join or equivalent NOT EXISTS with the consent-revocation keys. The revoked identifiers are absent, and nonrevoked source customers remain.
Incorrect Answers
A:An IoT bronze dataset contains temperatures as strings and an impossible reading that must not contaminate hourly gold summaries. In those circumstances, “Enforce numeric conversion and an allowed sensor range during the bronze-to-silver transform” fits. Apply a left anti join or equivalent NOT EXISTS with the consent-revocation keys.
B:When a retail bronze orders table contains string totals, inconsistent country codes and missing order identifiers before a silver SLA can begin, “Create a silver projection that casts monetary values, normalizes country codes and rejects missing required keys without overwriting bronze” could be relevant. Apply a left anti join or equivalent NOT EXISTS with the consent-revocation keys.
D:A risk team needs all combinations of five scenario assumptions and six stress categories. In those circumstances, “Apply a deliberate cross join to form a bounded Cartesian product” fits. Apply a left anti join or equivalent NOT EXISTS with the consent-revocation keys.
Question 226
A GDPR deletion feed requires excluding rows whose identifiers appear on a revoked-consent list. Which setup step most directly realizes the proposed design?
- Review spill metrics and join strategy, then test supported executor memory or partition adjustments.
- Create the appropriate Unity Catalog view with an explicit stable SELECT.
- Compare runs while adjusting spark.sql.shuffle.partitions within tested bounds.
- Join source customers against revoked ids using left_anti on the right key.
Explanation
Correct Answer
D:Join source customers against revoked ids using left_anti on the right key. The revoked identifiers are absent, and nonrevoked source customers remain.
Incorrect Answers
A:When a large join spills to disk repeatedly although executor memory pressure is high, “Review spill metrics and join strategy, then test supported executor memory or partition adjustments” could be relevant. Join source customers against revoked ids using left_anti on the right key.
B:If a finance dashboard reads a curated metric that should always reflect the latest base table without storing a separately maintained aggregate, “Create the appropriate Unity Catalog view with an explicit stable SELECT” may be the appropriate response. Join source customers against revoked ids using left_anti on the right key.
C:A heavily shuffled ETL join creates thousands of tiny shuffle partitions while tasks spend time scheduling. In those circumstances, “Compare runs while adjusting spark.sql.shuffle.partitions within tested bounds” fits. Join source customers against revoked ids using left_anti on the right key.
Question 227
A GDPR deletion feed requires excluding rows whose identifiers appear on a revoked-consent list. What is the most relevant verification evidence for this case?
- The execution plan reflects a broadcast strategy and the run improves without OOM.
- Comparable runs use useful parallel tasks with lower total overhead.
- The accepted plus rejected counts reconcile to the original source batch.
- The revoked identifiers are absent, and nonrevoked source customers remain.
Explanation
Correct Answer
D:The revoked identifiers are absent, and nonrevoked source customers remain.
Incorrect Answers
A:If a large fact-to-small-dimension join repeatedly performs an avoidable shuffle, “The execution plan reflects a broadcast strategy and the run improves without OOM” may be the appropriate response. The revoked identifiers are absent, and nonrevoked source customers remain.
B: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. The revoked identifiers are absent, and nonrevoked source customers remain.
C:When a silver quality gate must reject records missing a transaction identifier, but analysts still need an error count, “The accepted plus rejected counts reconcile to the original source batch” could be relevant. The revoked identifiers are absent, and nonrevoked source customers remain.
Question 228
A GDPR deletion feed requires excluding rows whose identifiers appear on a revoked-consent list. The team observes: A revoked customer is still present in the exported serving table. What is the most likely mechanism behind the observed defect?
- The job insisted on a full exact DISTINCT despite permitted approximate accuracy.
- An equijoin or filtering condition unintentionally removed Cartesian pairs.
- A batch overwrite replaced the persistent incremental streaming target.
- The operation used left outer or omitted the anti-match predicate.
Explanation
Correct Answer
D:The operation used left outer or omitted the anti-match predicate. Join source customers against revoked ids using left_anti on the right key.
Incorrect Answers
A:A reporting table must count unique devices across billions of events with an acceptable approximation. In those circumstances, “The job insisted on a full exact DISTINCT despite permitted approximate accuracy” fits. The operation used left outer or omitted the anti-match predicate.
B:When a risk team needs all combinations of five scenario assumptions and six stress categories, “An equijoin or filtering condition unintentionally removed Cartesian pairs” could be relevant. The operation used left outer or omitted the anti-match predicate.
C:If a downstream pipeline needs incremental consumption of a continuous events feed into a governed table, “A batch overwrite replaced the persistent incremental streaming target” may be the appropriate response. The operation used left outer or omitted the anti-match predicate.
Question 229
An account table has three irrelevant vendor-internal columns that must not reach the published silver table. Which approach most directly satisfies the requirement?
- Apply a business-rule assertion before promoting data to silver or gold.
- Create a silver projection that casts monetary values, normalizes country codes and rejects missing required keys without overwriting bronze.
- Project only the explicitly approved fields rather than carrying the full source schema.
- Size and optimize the join and memory allocation after inspecting Spark UI evidence.
Explanation
Correct Answer
C:Project only the explicitly approved fields rather than carrying the full source schema. The published schema contains only the approved fields despite extra bronze columns.
Incorrect Answers
A:When a payments silver table must never have negative approved transaction amounts, “Apply a business-rule assertion before promoting data to silver or gold” could be relevant. Project only the explicitly approved fields rather than carrying the full source schema.
B:If a retail bronze orders table contains string totals, inconsistent country codes and missing order identifiers before a silver SLA can begin, “Create a silver projection that casts monetary values, normalizes country codes and rejects missing required keys without overwriting bronze” may be the appropriate response. Project only the explicitly approved fields rather than carrying the full source schema.
D:When a large join spills to disk repeatedly although executor memory pressure is high, “Size and optimize the join and memory allocation after inspecting Spark UI evidence” could be relevant. Project only the explicitly approved fields rather than carrying the full source schema.
Question 230
An account table has three irrelevant vendor-internal columns that must not reach the published silver table. Which configuration or engineering action would most directly implement the requirement?
- Join accounts LEFT OUTER JOIN payments on account_id and preserve missing payment fields.
- Use dropDuplicates on event_id after defining the desired event window or batch boundary.
- Group by service area and aggregate conditional SUM for completed rows and COUNT for attempts.
- Use select on an allowlist or drop the disallowed columns before writing the table.
Explanation
Correct Answer
D:Use select on an allowlist or drop the disallowed columns before writing the table. The published schema contains only the approved fields despite extra bronze columns.
Incorrect Answers
A:If a subscriptions dataset must preserve every account even when no payment has arrived, “Join accounts LEFT OUTER JOIN payments on account_id and preserve missing payment fields” may be the appropriate response. Use select on an allowlist or drop the disallowed columns before writing the table.
B:A click event feed contains retries with identical event_id and should count each business event once. In those circumstances, “Use dropDuplicates on event_id after defining the desired event window or batch boundary” fits. Use select on an allowlist or drop the disallowed columns before writing the table.
C:When a service operations report must count completed deliveries separately from all attempted deliveries, “Group by service area and aggregate conditional SUM for completed rows and COUNT for attempts” could be relevant. Use select on an allowlist or drop the disallowed columns before writing the table.
Certified Data Engineer Associate Practice Tests