Certified Data Engineer Associate Practice Test 24
Question 230
At a logistics carrier, a large fact DataFrame is joined to a very small reference dimension but shuffle volume dominates runtime. The dataset `viewer_sessions` is in scope, and raw records must remain available for replay. What verification provides evidence of correct behavior under the original adverse condition?
- Run only a normal, unchanged `viewer_sessions` sample and review reference table size.
- Review a platform-level availability report for `viewer_sessions` without testing whether shuffling both sides is unnecessary when the small reference fits within safe broadcast memory.
- Check that the intended configuration exists for `viewer_sessions` and that a healthy run succeeded, without inducing the earlier failure.
- Compare join plans and row counts with and without broadcasting the small dimension
Explanation
Correct Answer
D:Compare join plans and row counts with and without broadcasting the small dimension. This reproduces the scenario-dependent condition, verifies reference table size, Spark physical plan, shuffle bytes, and joined row cardinality, and directly tests whether shuffling both sides is unnecessary when the small reference fits within safe broadcast memory is resolved. Observed results, not intent, determine approval.
Incorrect Answers
A:Run only a normal, unchanged `viewer_sessions` sample and review reference table size. A normal sample does not challenge shuffling both sides is unnecessary when the small reference fits within safe broadcast memory.
B:Review a platform-level availability report for `viewer_sessions` without testing whether shuffling both sides is unnecessary when the small reference fits within safe broadcast memory. Aggregate availability does not establish the behavior of affected `viewer_sessions` records. It cannot replace the direct exercise: compare join plans and row counts with and without broadcasting the small dimension.
C:Check that the intended configuration exists for `viewer_sessions` and that a healthy run succeeded, without inducing the earlier failure. Installed configuration and a healthy run are insufficient to prove the failure mode is gone. The original issue was shuffling both sides is unnecessary when the small reference fits within safe broadcast memory.
Question 231
At a food delivery company, a customer event enrichment drops customers without matching segmentation rows even though the report requires all customers. The dataset `prescription_claims` is in scope, and downstream dashboards cannot accept fabricated values. Which investigation best tests the stated constraint with direct data?
- Inspect normal-period success metrics for the stated dataset without reproducing the source error
- Correlate left-side customer count, unmatched key sample across affected and unaffected `R034-CASE-047` runs.
- Compare the current configuration and the signed change approval, without source-row evidence
- Review completed run status and aggregate cluster health without record-level correlation
Explanation
Correct Answer
B:Correlate left-side customer count, unmatched key sample across affected and unaffected `R034-CASE-047` runs.. By joining left-side customer count, unmatched key sample, join type, and missing segment rate across the affected and unaffected conditions, the investigation directly tests the recorded mechanism: an inner join discards left-side rows without a corresponding dimension match. It also sets a measurable baseline for include a customer with no segment and confirm that customer remains with a null or default segment.
Incorrect Answers
A:Inspect normal-period success metrics for the stated dataset without reproducing the source error. A healthy-run trend can be useful, but it does not expose an inner join discards left-side rows without a corresponding dimension match. The failing-path left-side customer count, unmatched key sample, join type, and missing segment rate has to be correlated before attributing cause.
C:Compare the current configuration and the signed change approval, without source-row evidence. A desired configuration and approval ticket are not runtime proof. In this case they omit left-side customer count, unmatched key sample, join type, and missing segment rate, the direct means of distinguishing an inner join discards left-side rows without a corresponding dimension match.
D:Review completed run status and aggregate cluster health without record-level correlation. A successful aggregate platform state can coexist with an inner join discards left-side rows without a corresponding dimension match. This check never observes the affected `prescription_claims` records or their causal path.
Question 232
At a food delivery company, a customer event enrichment drops customers without matching segmentation rows even though the report requires all customers. The dataset `prescription_claims` is in scope, and downstream dashboards cannot accept fabricated values. Which option targets the actual technical dependency rather than an incidental symptom?
- Append both datasets with unionByName instead of joining them; use that approach for `prescription_claims`.
- Use a left join from the customer DataFrame to segmentation and handle unmatched dimension fields explicitly
- Keep the inner join and fill null segmentation fields afterward; use that approach for `prescription_claims`.
- Use a cross join to preserve all customers without join keys; use that approach for `prescription_claims`.
Explanation
Correct Answer
B:Use a left join from the customer DataFrame to segmentation and handle unmatched dimension fields explicitly. This directly addresses an inner join discards left-side rows without a corresponding dimension match. The design should be accepted only after include a customer with no segment and confirm that customer remains with a null or default segment; the related operational boundary is to retain all required primary records while documenting the dimension-match quality gap.
Incorrect Answers
A:Append both datasets with unionByName instead of joining them; use that approach for `prescription_claims`. Union stacks rows; it does not enrich each customer with its dimension attributes. For `prescription_claims`, this cannot remove the causal limitation: an inner join discards left-side rows without a corresponding dimension match.
C:Keep the inner join and fill null segmentation fields afterward; use that approach for `prescription_claims`. Rows removed by the inner join cannot be recovered by a later fillna. For `prescription_claims`, this cannot remove the causal limitation: an inner join discards left-side rows without a corresponding dimension match.
D:Use a cross join to preserve all customers without join keys; use that approach for `prescription_claims`. A Cartesian product creates spurious combinations instead of valid matches. For `prescription_claims`, this cannot remove the causal limitation: an inner join discards left-side rows without a corresponding dimension match.
Question 233
At a food delivery company, a customer event enrichment drops customers without matching segmentation rows even though the report requires all customers. The dataset `prescription_claims` is in scope, and downstream dashboards cannot accept fabricated values. A teammate proposes: "Append both datasets with unionByName instead of joining them." Which technical limitation is the decisive reason not to approve that specific proposal?
- The dashboard cached the prior result; no DataFrame operation or underlying data requires correction.
- Union stacks rows; it does not enrich each customer with its dimension attributes. The proposal does not repair `prescription_claims`.
- Rows removed by the inner join cannot be recovered by a later fillna. This would apply to an alternative change for `prescription_claims`.
- A Cartesian product creates spurious combinations instead of valid matches. This would apply to another option for `prescription_claims`.
Explanation
Correct Answer
B:Union stacks rows; it does not enrich each customer with its dimension attributes. The proposal does not repair `prescription_claims`. This identifies the known limitation of the exact proposed action. Union stacks rows; it does not enrich each customer with its dimension attributes. The underlying problem remains an inner join discards left-side rows without a corresponding dimension match; Use a left join from the customer DataFrame to segmentation and handle unmatched dimension fields explicitly instead targets that failure.
Incorrect Answers
A:The dashboard cached the prior result; no DataFrame operation or underlying data requires correction. The case provides a concrete failing data or control path; a mere alternate theory does not address an inner join discards left-side rows without a corresponding dimension match.
C:Rows removed by the inner join cannot be recovered by a later fillna. This would apply to an alternative change for `prescription_claims`. This failure applies to the separate proposal "Keep the inner join and fill null segmentation fields afterward".
D:A Cartesian product creates spurious combinations instead of valid matches. This would apply to another option for `prescription_claims`. This limitation belongs to the different alternative "Use a cross join to preserve all customers without join keys". The stem calls for the specific failure of "Append both datasets with unionByName instead of joining them".
Question 234
At a food delivery company, a customer event enrichment drops customers without matching segmentation rows even though the report requires all customers. The dataset `prescription_claims` is in scope, and downstream dashboards cannot accept fabricated values. What operational boundary should be documented for approval?
- Append both datasets with unionByName instead of joining them
- Retain all required primary records while documenting the dimension-match quality gap
- Use a cross join to preserve all customers without join keys
- Keep the inner join and fill null segmentation fields afterward
Explanation
Correct Answer
B:Retain all required primary records while documenting the dimension-match quality gap. This explicitly bounds the compromise while still addressing an inner join discards left-side rows without a corresponding dimension match. Acceptance relies on include a customer with no segment and confirm that customer remains with a null or default segment rather than simply declaring the change complete.
Incorrect Answers
A:Append both datasets with unionByName instead of joining them. Union stacks rows; it does not enrich each customer with its dimension attributes. Monitoring after deployment does not make this approach a safe bounded tradeoff for `prescription_claims`.
C:Use a cross join to preserve all customers without join keys. A Cartesian product creates spurious combinations instead of valid matches. Monitoring after deployment does not make this approach a safe bounded tradeoff for `prescription_claims`.
D:Keep the inner join and fill null segmentation fields afterward. Rows removed by the inner join cannot be recovered by a later fillna. Monitoring after deployment does not make this approach a safe bounded tradeoff for `prescription_claims`.
Question 235
At a food delivery company, a customer event enrichment drops customers without matching segmentation rows even though the report requires all customers. The dataset `prescription_claims` is in scope, and downstream dashboards cannot accept fabricated values. Which validation should be required in the release record?
- Review a platform-level availability report for `prescription_claims` without testing whether an inner join discards left-side rows without a corresponding dimension match.
- Run only a normal, unchanged `prescription_claims` sample and review left-side customer count.
- Include a customer with no segment and confirm that customer remains with a null or default segment
- Check that the intended configuration exists for `prescription_claims` and that a healthy run succeeded, without inducing the earlier failure.
Explanation
Correct Answer
C:Include a customer with no segment and confirm that customer remains with a null or default segment. This reproduces the scenario-dependent condition, verifies left-side customer count, unmatched key sample, join type, and missing segment rate, and directly tests whether an inner join discards left-side rows without a corresponding dimension match is resolved. Observed results, not intent, determine approval.
Incorrect Answers
A:Review a platform-level availability report for `prescription_claims` without testing whether an inner join discards left-side rows without a corresponding dimension match. Aggregate availability does not establish the behavior of affected `prescription_claims` records. It cannot replace the direct exercise: include a customer with no segment and confirm that customer remains with a null or default segment.
B:Run only a normal, unchanged `prescription_claims` sample and review left-side customer count. A normal sample does not challenge an inner join discards left-side rows without a corresponding dimension match.
D:Check that the intended configuration exists for `prescription_claims` and that a healthy run succeeded, without inducing the earlier failure. Installed configuration and a healthy run are insufficient to prove the failure mode is gone. The original issue was an inner join discards left-side rows without a corresponding dimension match.
Question 236
At an education technology firm, a large fact DataFrame is joined to a very small reference dimension but shuffle volume dominates runtime. The dataset `daily_receipts` is in scope, and raw records must remain available for replay. Before choosing a remedy, which investigation actually distinguishes the failure mechanism from a green dashboard?
- Compare the saved configuration with the signed change ticket for `daily_receipts` while omitting source and output records.
- Correlate reference table size, Spark physical plan across affected and unaffected `R034-CASE-048` runs.
- Examine only a normal successful run of `daily_receipts` and trend reference table size without recreating the fault.
- Review aggregate cluster availability and job completion for `daily_receipts` without correlating the observed error path.
Explanation
Correct Answer
B:Correlate reference table size, Spark physical plan across affected and unaffected `R034-CASE-048` runs.. By joining reference table size, Spark physical plan, shuffle bytes, and joined row cardinality across the affected and unaffected conditions, the investigation directly tests the recorded mechanism: shuffling both sides is unnecessary when the small reference fits within safe broadcast memory. It also sets a measurable baseline for compare join plans and row counts with and without broadcasting the small dimension.
Incorrect Answers
A:Compare the saved configuration with the signed change ticket for `daily_receipts` while omitting source and output records. A desired configuration and approval ticket are not runtime proof. In this case they omit reference table size, Spark physical plan, shuffle bytes, and joined row cardinality, the direct means of distinguishing shuffling both sides is unnecessary when the small reference fits within safe broadcast memory.
C:Examine only a normal successful run of `daily_receipts` and trend reference table size without recreating the fault. A healthy-run trend can be useful, but it does not expose shuffling both sides is unnecessary when the small reference fits within safe broadcast memory. The failing-path reference table size, Spark physical plan, shuffle bytes, and joined row cardinality has to be correlated before attributing cause.
D:Review aggregate cluster availability and job completion for `daily_receipts` without correlating the observed error path. A successful aggregate platform state can coexist with shuffling both sides is unnecessary when the small reference fits within safe broadcast memory. This check never observes the affected `daily_receipts` records or their causal path.
Question 237
At an education technology firm, a large fact DataFrame is joined to a very small reference dimension but shuffle volume dominates runtime. The dataset `daily_receipts` is in scope, and raw records must remain available for replay. Which implementation best resolves the stated defect without breaking the business constraint?
- Broadcast the multi-terabyte fact table instead; use that approach for `daily_receipts`.
- Use a cross join and filter the matches after multiplication; use that approach for `daily_receipts`.
- Increase shuffle partitions without considering join distribution; use that approach for `daily_receipts`.
- Broadcast the genuinely small dimension and join on the validated business key, checking output cardinality
Explanation
Correct Answer
D:Broadcast the genuinely small dimension and join on the validated business key, checking output cardinality. This directly addresses shuffling both sides is unnecessary when the small reference fits within safe broadcast memory. The design should be accepted only after compare join plans and row counts with and without broadcasting the small dimension; the related operational boundary is to use a targeted broadcast when the reference is safely small, not an unconditional broadcast policy.
Incorrect Answers
A:Broadcast the multi-terabyte fact table instead; use that approach for `daily_receipts`. Replicating the large side exceeds executor memory and can cause instability. For `daily_receipts`, this cannot remove the causal limitation: shuffling both sides is unnecessary when the small reference fits within safe broadcast memory.
B:Use a cross join and filter the matches after multiplication; use that approach for `daily_receipts`. A Cartesian product creates excessive intermediate rows and work. For `daily_receipts`, this cannot remove the causal limitation: shuffling both sides is unnecessary when the small reference fits within safe broadcast memory.
C:Increase shuffle partitions without considering join distribution; use that approach for `daily_receipts`. More partitions do not eliminate an avoidable shuffle of the small dimension. For `daily_receipts`, this cannot remove the causal limitation: shuffling both sides is unnecessary when the small reference fits within safe broadcast memory.
Question 238
At an education technology firm, a large fact DataFrame is joined to a very small reference dimension but shuffle volume dominates runtime. The dataset `daily_receipts` is in scope, and raw records must remain available for replay. A teammate proposes: "Use a cross join and filter the matches after multiplication." Which technical limitation is the decisive reason not to approve that specific proposal?
- More partitions do not eliminate an avoidable shuffle of the small dimension. This would apply to an alternative change for `daily_receipts`.
- The dashboard cached the prior result; no DataFrame operation or underlying data requires correction.
- A Cartesian product creates excessive intermediate rows and work. The proposal does not repair `daily_receipts`.
- Replicating the large side exceeds executor memory and can cause instability. This would apply to another option for `daily_receipts`.
Explanation
Correct Answer
C:A Cartesian product creates excessive intermediate rows and work. The proposal does not repair `daily_receipts`. This identifies the known limitation of the exact proposed action. A Cartesian product creates excessive intermediate rows and work. The underlying problem remains shuffling both sides is unnecessary when the small reference fits within safe broadcast memory; Broadcast the genuinely small dimension and join on the validated business key, checking output cardinality instead targets that failure.
Incorrect Answers
A:More partitions do not eliminate an avoidable shuffle of the small dimension. This would apply to an alternative change for `daily_receipts`. This failure applies to the separate proposal "Increase shuffle partitions without considering join distribution".
B:The dashboard cached the prior result; no DataFrame operation or underlying data requires correction. The case provides a concrete failing data or control path; a mere alternate theory does not address shuffling both sides is unnecessary when the small reference fits within safe broadcast memory.
D:Replicating the large side exceeds executor memory and can cause instability. This would apply to another option for `daily_receipts`. This limitation belongs to the different alternative "Broadcast the multi-terabyte fact table instead". The stem calls for the specific failure of "Use a cross join and filter the matches after multiplication".
Question 239
At an education technology firm, a large fact DataFrame is joined to a very small reference dimension but shuffle volume dominates runtime. The dataset `daily_receipts` is in scope, and raw records must remain available for replay. Which bounded tradeoff would preserve the core outcome and control operational risk?
- Use a targeted broadcast when the reference is safely small, not an unconditional broadcast policy
- Use a cross join and filter the matches after multiplication; monitor results only after launch of `daily_receipts`.
- Broadcast the multi-terabyte fact table instead; monitor results only after launch of `daily_receipts`.
- Increase shuffle partitions without considering join distribution; monitor results only after launch of `daily_receipts`.
Explanation
Correct Answer
A:Use a targeted broadcast when the reference is safely small, not an unconditional broadcast policy. This explicitly bounds the compromise while still addressing shuffling both sides is unnecessary when the small reference fits within safe broadcast memory. Acceptance relies on compare join plans and row counts with and without broadcasting the small dimension rather than simply declaring the change complete.
Incorrect Answers
B:Use a cross join and filter the matches after multiplication; monitor results only after launch of `daily_receipts`. A Cartesian product creates excessive intermediate rows and work. Monitoring after deployment does not make this approach a safe bounded tradeoff for `daily_receipts`.
C:Broadcast the multi-terabyte fact table instead; monitor results only after launch of `daily_receipts`. Replicating the large side exceeds executor memory and can cause instability. Monitoring after deployment does not make this approach a safe bounded tradeoff for `daily_receipts`.
D:Increase shuffle partitions without considering join distribution; monitor results only after launch of `daily_receipts`. More partitions do not eliminate an avoidable shuffle of the small dimension. Monitoring after deployment does not make this approach a safe bounded tradeoff for `daily_receipts`.
Question 240
At an education technology firm, a large fact DataFrame is joined to a very small reference dimension but shuffle volume dominates runtime. The dataset `daily_receipts` is in scope, and raw records must remain available for replay. Before release, which acceptance test would actually demonstrate that the root problem is controlled?
- Compare join plans and row counts with and without broadcasting the small dimension
- Run only a normal, unchanged `daily_receipts` sample and review reference table size.
- Review a platform-level availability report for `daily_receipts` without testing whether shuffling both sides is unnecessary when the small reference fits within safe broadcast memory.
- Check that the intended configuration exists for `daily_receipts` and that a healthy run succeeded, without inducing the earlier failure.
Explanation
Correct Answer
A:Compare join plans and row counts with and without broadcasting the small dimension. This reproduces the scenario-dependent condition, verifies reference table size, Spark physical plan, shuffle bytes, and joined row cardinality, and directly tests whether shuffling both sides is unnecessary when the small reference fits within safe broadcast memory is resolved. Observed results, not intent, determine approval.
Incorrect Answers
B:Run only a normal, unchanged `daily_receipts` sample and review reference table size. A normal sample does not challenge shuffling both sides is unnecessary when the small reference fits within safe broadcast memory.
C:Review a platform-level availability report for `daily_receipts` without testing whether shuffling both sides is unnecessary when the small reference fits within safe broadcast memory. Aggregate availability does not establish the behavior of affected `daily_receipts` records. It cannot replace the direct exercise: compare join plans and row counts with and without broadcasting the small dimension.
D:Check that the intended configuration exists for `daily_receipts` and that a healthy run succeeded, without inducing the earlier failure. Installed configuration and a healthy run are insufficient to prove the failure mode is gone. The original issue was shuffling both sides is unnecessary when the small reference fits within safe broadcast memory.