Certified Data Engineer Associate Practice Test 26
Question 250
At a gaming analytics company, a DataFrame cleanup drops records when a numeric threshold is missing, but policy requires retaining those rows for review. The dataset `content_clicks` is in scope, and the release must preserve the original source evidence. What verification provides evidence of correct behavior under the original adverse condition?
- Review a platform-level availability report for `content_clicks` without testing whether ordinary numeric comparisons against null produce unknown predicates that filters do not retain.
- Inject null, zero and positive amounts and assert each enters the intended output or review route
- Run only a normal, unchanged `content_clicks` sample and review null input count.
- Check that the intended configuration exists for `content_clicks` and that a healthy run succeeded, without inducing the earlier failure.
Explanation
Correct Answer
B:Inject null, zero and positive amounts and assert each enters the intended output or review route. This reproduces the scenario-dependent condition, verifies null input count, filter predicate, kept and rejected row counts, and downstream reporting totals, and directly tests whether ordinary numeric comparisons against null produce unknown predicates that filters do not retain is resolved. Observed results, not intent, determine approval.
Incorrect Answers
A:Review a platform-level availability report for `content_clicks` without testing whether ordinary numeric comparisons against null produce unknown predicates that filters do not retain. Aggregate availability does not establish the behavior of affected `content_clicks` records. It cannot replace the direct exercise: inject null, zero and positive amounts and assert each enters the intended output or review route.
C:Run only a normal, unchanged `content_clicks` sample and review null input count. A normal sample does not challenge ordinary numeric comparisons against null produce unknown predicates that filters do not retain.
D:Check that the intended configuration exists for `content_clicks` 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 ordinary numeric comparisons against null produce unknown predicates that filters do not retain.
Question 251
At an online travel marketplace, a nested commerce DataFrame contains arrays of product line items that need one row per product for inventory analysis. The dataset `session_facts` is in scope, and a finance audit requires reproducible aggregated figures. Which investigation best tests the stated constraint with direct data?
- Compare the saved configuration with the signed change ticket for `session_facts` while omitting source and output records.
- Examine only a normal successful run of `session_facts` and trend array item counts without recreating the fault.
- Correlate array item counts, order IDs across affected and unaffected `R034-CASE-051` runs.
- Review aggregate cluster availability and job completion for `session_facts` without correlating the observed error path.
Explanation
Correct Answer
C:Correlate array item counts, order IDs across affected and unaffected `R034-CASE-051` runs.. By joining array item counts, order IDs, output row counts, and nested-field types across the affected and unaffected conditions, the investigation directly tests the recorded mechanism: selecting the array as one column leaves all child products inside the same row. It also sets a measurable baseline for test orders with one, zero and three items and validate item-level row counts and parent associations.
Incorrect Answers
A:Compare the saved configuration with the signed change ticket for `session_facts` while omitting source and output records. A desired configuration and approval ticket are not runtime proof. In this case they omit array item counts, order IDs, output row counts, and nested-field types, the direct means of distinguishing selecting the array as one column leaves all child products inside the same row.
B:Examine only a normal successful run of `session_facts` and trend array item counts without recreating the fault. A healthy-run trend can be useful, but it does not expose selecting the array as one column leaves all child products inside the same row. The failing-path array item counts, order IDs, output row counts, and nested-field types has to be correlated before attributing cause.
D:Review aggregate cluster availability and job completion for `session_facts` without correlating the observed error path. A successful aggregate platform state can coexist with selecting the array as one column leaves all child products inside the same row. This check never observes the affected `session_facts` records or their causal path.
Question 252
At an online travel marketplace, a nested commerce DataFrame contains arrays of product line items that need one row per product for inventory analysis. The dataset `session_facts` is in scope, and a finance audit requires reproducible aggregated figures. Which option targets the actual technical dependency rather than an incidental symptom?
- Split raw JSON on commas to form separate products; use that approach for `session_facts`.
- Use explode on the product array, retaining the order identifier alongside each child product record
- Rename the array field to product_id without changing the values; use that approach for `session_facts`.
- Apply distinct to the array column and expect one item per row; use that approach for `session_facts`.
Explanation
Correct Answer
B:Use explode on the product array, retaining the order identifier alongside each child product record. This directly addresses selecting the array as one column leaves all child products inside the same row. The design should be accepted only after test orders with one, zero and three items and validate item-level row counts and parent associations; the related operational boundary is to expand nested entities only in the curated model and preserve original bronze event context.
Incorrect Answers
A:Split raw JSON on commas to form separate products; use that approach for `session_facts`. Delimiter parsing ignores nested objects and escaped text. For `session_facts`, this cannot remove the causal limitation: selecting the array as one column leaves all child products inside the same row.
C:Rename the array field to product_id without changing the values; use that approach for `session_facts`. Renaming changes only the label, not the nested cardinality. For `session_facts`, this cannot remove the causal limitation: selecting the array as one column leaves all child products inside the same row.
D:Apply distinct to the array column and expect one item per row; use that approach for `session_facts`. Distinct deduplicates rows but does not flatten an array. For `session_facts`, this cannot remove the causal limitation: selecting the array as one column leaves all child products inside the same row.
Question 253
At an online travel marketplace, a nested commerce DataFrame contains arrays of product line items that need one row per product for inventory analysis. The dataset `session_facts` is in scope, and a finance audit requires reproducible aggregated figures. A teammate proposes: "Split raw JSON on commas to form separate products." Which technical limitation is the decisive reason not to approve that specific proposal?
- Distinct deduplicates rows but does not flatten an array. This would apply to an alternative change for `session_facts`.
- Renaming changes only the label, not the nested cardinality. This would apply to another option for `session_facts`.
- The dashboard cached the prior result; no DataFrame operation or underlying data requires correction.
- Delimiter parsing ignores nested objects and escaped text. The proposal does not repair `session_facts`.
Explanation
Correct Answer
D:Delimiter parsing ignores nested objects and escaped text. The proposal does not repair `session_facts`. This identifies the known limitation of the exact proposed action. Delimiter parsing ignores nested objects and escaped text. The underlying problem remains selecting the array as one column leaves all child products inside the same row; Use explode on the product array, retaining the order identifier alongside each child product record instead targets that failure.
Incorrect Answers
A:Distinct deduplicates rows but does not flatten an array. This would apply to an alternative change for `session_facts`. This failure applies to the separate proposal "Apply distinct to the array column and expect one item per row".
B:Renaming changes only the label, not the nested cardinality. This would apply to another option for `session_facts`. This limitation belongs to the different alternative "Rename the array field to product_id without changing the values". The stem calls for the specific failure of "Split raw JSON on commas to form separate products".
C: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 selecting the array as one column leaves all child products inside the same row.
Question 254
At an online travel marketplace, a nested commerce DataFrame contains arrays of product line items that need one row per product for inventory analysis. The dataset `session_facts` is in scope, and a finance audit requires reproducible aggregated figures. What operational boundary should be documented for approval?
- Rename the array field to product_id without changing the values; monitor results only after launch of `session_facts`.
- Apply distinct to the array column and expect one item per row; monitor results only after launch of `session_facts`.
- Split raw JSON on commas to form separate products; monitor results only after launch of `session_facts`.
- Expand nested entities only in the curated model and preserve original bronze event context
Explanation
Correct Answer
D:Expand nested entities only in the curated model and preserve original bronze event context. This explicitly bounds the compromise while still addressing selecting the array as one column leaves all child products inside the same row. Acceptance relies on test orders with one, zero and three items and validate item-level row counts and parent associations rather than simply declaring the change complete.
Incorrect Answers
A:Rename the array field to product_id without changing the values; monitor results only after launch of `session_facts`. Renaming changes only the label, not the nested cardinality. Monitoring after deployment does not make this approach a safe bounded tradeoff for `session_facts`.
B:Apply distinct to the array column and expect one item per row; monitor results only after launch of `session_facts`. Distinct deduplicates rows but does not flatten an array. Monitoring after deployment does not make this approach a safe bounded tradeoff for `session_facts`.
C:Split raw JSON on commas to form separate products; monitor results only after launch of `session_facts`. Delimiter parsing ignores nested objects and escaped text. Monitoring after deployment does not make this approach a safe bounded tradeoff for `session_facts`.
Question 255
At an online travel marketplace, a nested commerce DataFrame contains arrays of product line items that need one row per product for inventory analysis. The dataset `session_facts` is in scope, and a finance audit requires reproducible aggregated figures. Which validation should be required in the release record?
- Check that the intended configuration exists for `session_facts` and that a healthy run succeeded, without inducing the earlier failure.
- Test orders with one, zero and three items and validate item-level row counts and parent associations
- Review a platform-level availability report for `session_facts` without testing whether selecting the array as one column leaves all child products inside the same row.
- Run only a normal, unchanged `session_facts` sample and review array item counts.
Explanation
Correct Answer
B:Test orders with one, zero and three items and validate item-level row counts and parent associations. This reproduces the scenario-dependent condition, verifies array item counts, order IDs, output row counts, and nested-field types, and directly tests whether selecting the array as one column leaves all child products inside the same row is resolved. Observed results, not intent, determine approval.
Incorrect Answers
A:Check that the intended configuration exists for `session_facts` 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 selecting the array as one column leaves all child products inside the same row.
C:Review a platform-level availability report for `session_facts` without testing whether selecting the array as one column leaves all child products inside the same row. Aggregate availability does not establish the behavior of affected `session_facts` records. It cannot replace the direct exercise: test orders with one, zero and three items and validate item-level row counts and parent associations.
D:Run only a normal, unchanged `session_facts` sample and review array item counts. A normal sample does not challenge selecting the array as one column leaves all child products inside the same row.
Question 256
At a global apparel distributor, a DataFrame cleanup drops records when a numeric threshold is missing, but policy requires retaining those rows for review. The dataset `tower_incidents` is in scope, and the release must preserve the original source evidence. Before choosing a remedy, which investigation actually distinguishes the failure mechanism from a green dashboard?
- Correlate null input count, filter predicate across affected and unaffected `R034-CASE-052` runs.
- Compare the current configuration and the signed change approval, without source-row evidence
- Inspect normal-period success metrics for the stated dataset without reproducing the source error
- Review aggregate cluster availability and job completion for `tower_incidents` without correlating the observed error path.
Explanation
Correct Answer
A:Correlate null input count, filter predicate across affected and unaffected `R034-CASE-052` runs.. By joining null input count, filter predicate, kept and rejected row counts, and downstream reporting totals across the affected and unaffected conditions, the investigation directly tests the recorded mechanism: ordinary numeric comparisons against null produce unknown predicates that filters do not retain. It also sets a measurable baseline for inject null, zero and positive amounts and assert each enters the intended output or review route.
Incorrect Answers
B: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 null input count, filter predicate, kept and rejected row counts, and downstream reporting totals, the direct means of distinguishing ordinary numeric comparisons against null produce unknown predicates that filters do not retain.
C: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 ordinary numeric comparisons against null produce unknown predicates that filters do not retain. The failing-path null input count, filter predicate, kept and rejected row counts, and downstream reporting totals has to be correlated before attributing cause.
D:Review aggregate cluster availability and job completion for `tower_incidents` without correlating the observed error path. A successful aggregate platform state can coexist with ordinary numeric comparisons against null produce unknown predicates that filters do not retain. This check never observes the affected `tower_incidents` records or their causal path.
Question 257
At a global apparel distributor, a DataFrame cleanup drops records when a numeric threshold is missing, but policy requires retaining those rows for review. The dataset `tower_incidents` is in scope, and the release must preserve the original source evidence. Which implementation best resolves the stated defect without breaking the business constraint?
- Use dropna on every DataFrame column before saving; use that approach for `tower_incidents`.
- Replace every null amount with an invented high value; use that approach for `tower_incidents`.
- Write filter("amount > 0") and assume nulls remain; use that approach for `tower_incidents`.
- Use a null-aware filter or explicit error category and keep the unmatched rows in a separate exception dataset
Explanation
Correct Answer
D:Use a null-aware filter or explicit error category and keep the unmatched rows in a separate exception dataset. This directly addresses ordinary numeric comparisons against null produce unknown predicates that filters do not retain. The design should be accepted only after inject null, zero and positive amounts and assert each enters the intended output or review route; the related operational boundary is to retain uncertain records for remediation without treating them as valid positive transactions.
Incorrect Answers
A:Use dropna on every DataFrame column before saving; use that approach for `tower_incidents`. Dropping all null-bearing rows increases data loss and ignores field semantics. For `tower_incidents`, this cannot remove the causal limitation: ordinary numeric comparisons against null produce unknown predicates that filters do not retain.
B:Replace every null amount with an invented high value; use that approach for `tower_incidents`. Fabricated positive amounts can incorrectly satisfy business rules. For `tower_incidents`, this cannot remove the causal limitation: ordinary numeric comparisons against null produce unknown predicates that filters do not retain.
C:Write filter("amount > 0") and assume nulls remain; use that approach for `tower_incidents`. A null comparison is not true and rows are removed by the filter. For `tower_incidents`, this cannot remove the causal limitation: ordinary numeric comparisons against null produce unknown predicates that filters do not retain.
Question 258
At a global apparel distributor, a DataFrame cleanup drops records when a numeric threshold is missing, but policy requires retaining those rows for review. The dataset `tower_incidents` is in scope, and the release must preserve the original source evidence. A teammate proposes: "Replace every null amount with an invented high value." Which technical limitation is the decisive reason not to approve that specific proposal?
- Dropping all null-bearing rows increases data loss and ignores field semantics. This would apply to an alternative change for `tower_incidents`.
- Fabricated positive amounts can incorrectly satisfy business rules. The proposal does not repair `tower_incidents`.
- The dashboard cached the prior result; no DataFrame operation or underlying data requires correction.
- A null comparison is not true and rows are removed by the filter. This would apply to another option for `tower_incidents`.
Explanation
Correct Answer
B:Fabricated positive amounts can incorrectly satisfy business rules. The proposal does not repair `tower_incidents`. This identifies the known limitation of the exact proposed action. Fabricated positive amounts can incorrectly satisfy business rules. The underlying problem remains ordinary numeric comparisons against null produce unknown predicates that filters do not retain; Use a null-aware filter or explicit error category and keep the unmatched rows in a separate exception dataset instead targets that failure.
Incorrect Answers
A:Dropping all null-bearing rows increases data loss and ignores field semantics. This would apply to an alternative change for `tower_incidents`. This failure applies to the separate proposal "Use dropna on every DataFrame column before saving".
C: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 ordinary numeric comparisons against null produce unknown predicates that filters do not retain.
D:A null comparison is not true and rows are removed by the filter. This would apply to another option for `tower_incidents`. This limitation belongs to the different alternative "Write filter("amount > 0") and assume nulls remain". The stem calls for the specific failure of "Replace every null amount with an invented high value".
Question 259
At a global apparel distributor, a DataFrame cleanup drops records when a numeric threshold is missing, but policy requires retaining those rows for review. The dataset `tower_incidents` is in scope, and the release must preserve the original source evidence. Which bounded tradeoff would preserve the core outcome and control operational risk?
- Replace every null amount with an invented high value
- Write filter("amount > 0") and assume nulls remain
- Retain uncertain records for remediation without treating them as valid positive transactions
- Use dropna on every DataFrame column before saving; monitor results only after launch of `tower_incidents`.
Explanation
Correct Answer
C:Retain uncertain records for remediation without treating them as valid positive transactions. This explicitly bounds the compromise while still addressing ordinary numeric comparisons against null produce unknown predicates that filters do not retain. Acceptance relies on inject null, zero and positive amounts and assert each enters the intended output or review route rather than simply declaring the change complete.
Incorrect Answers
A:Replace every null amount with an invented high value. Fabricated positive amounts can incorrectly satisfy business rules. Monitoring after deployment does not make this approach a safe bounded tradeoff for `tower_incidents`.
B:Write filter("amount > 0") and assume nulls remain. A null comparison is not true and rows are removed by the filter. Monitoring after deployment does not make this approach a safe bounded tradeoff for `tower_incidents`.
D:Use dropna on every DataFrame column before saving; monitor results only after launch of `tower_incidents`. Dropping all null-bearing rows increases data loss and ignores field semantics. Monitoring after deployment does not make this approach a safe bounded tradeoff for `tower_incidents`.
Question 260
At a global apparel distributor, a DataFrame cleanup drops records when a numeric threshold is missing, but policy requires retaining those rows for review. The dataset `tower_incidents` is in scope, and the release must preserve the original source evidence. Before release, which acceptance test would actually demonstrate that the root problem is controlled?
- Check that the intended configuration exists for `tower_incidents` and that a healthy run succeeded, without inducing the earlier failure.
- Review a platform-level availability report for `tower_incidents` without testing whether ordinary numeric comparisons against null produce unknown predicates that filters do not retain.
- Run only a normal, unchanged `tower_incidents` sample and review null input count.
- Inject null, zero and positive amounts and assert each enters the intended output or review route
Explanation
Correct Answer
D:Inject null, zero and positive amounts and assert each enters the intended output or review route. This reproduces the scenario-dependent condition, verifies null input count, filter predicate, kept and rejected row counts, and downstream reporting totals, and directly tests whether ordinary numeric comparisons against null produce unknown predicates that filters do not retain is resolved. Observed results, not intent, determine approval.
Incorrect Answers
A:Check that the intended configuration exists for `tower_incidents` 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 ordinary numeric comparisons against null produce unknown predicates that filters do not retain.
B:Review a platform-level availability report for `tower_incidents` without testing whether ordinary numeric comparisons against null produce unknown predicates that filters do not retain. Aggregate availability does not establish the behavior of affected `tower_incidents` records. It cannot replace the direct exercise: inject null, zero and positive amounts and assert each enters the intended output or review route.
C:Run only a normal, unchanged `tower_incidents` sample and review null input count. A normal sample does not challenge ordinary numeric comparisons against null produce unknown predicates that filters do not retain.