100% Latest & Updated Amazon AWS Certified Data Engineer - Associate DEA-C01 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 40
A data team declares a successful cleanup because duplicate percentage fell, but the job also dropped valid unique rows. Select THREE complementary measures that correctly repair and validate, and prevent recurrence of this failure.
- Keep identifiers typed as strings and apply field-specific whitespace rules only.
- A shuffled fixture returns the same expected seven-day windows.
- Prefer fewer rows as sufficient proof of higher data quality.
- Accepted distinct keys remain complete while true duplicates are controlled.
- Compare uniqueness, completeness, reconciliation, and distribution against known fixtures.
- Require multidimensional quality gates before final publish.
Explanation
Correct Answers
D:Accepted distinct keys remain complete while true duplicates are controlled. This is the observable result required before accepting the correction.
E:Compare uniqueness, completeness, reconciliation, and distribution against known fixtures. The underlying cause is: Single-metric quality scoring hides unintended data loss.
F:Require multidimensional quality gates before final publish. This protects against the following risk: Single-metric quality scoring hides unintended data loss.
Incorrect Answers
A:That corrective action is for a different case: An analyst creates a Glue DataBrew visual cleaning step that trims all leading zeros from product IDs, breaking lookups. It does not resolve this incident.
B:This would validate a different case: A data science notebook uses a rolling 7-day average without ordering by event date, so results change with input row order. It does not verify the outcome required here.
C:Prefer fewer rows as sufficient proof of higher data quality. That shortcut conflicts with the stated requirement.
Question 41
A SageMaker Catalog project shares a data product broadly across teams without recording owner and allowed purpose. Which engineering change best addresses the underlying issue?
- Enable reviewed CloudTrail data events for the required S3 buckets or prefixes.
- Configure the appropriate service-principal trust and scoped invocation policy.
- Publish ownership, purpose, classification and scoped project access before sharing.
- Narrow LF-Tag permissions to reviewed principals and classify data assets consistently.
Explanation
Correct Answer
C:Publish ownership, purpose, classification and scoped project access before sharing. It directly addresses the case cause (Business catalog sharing lacks stewardship and usage-governance metadata.) and should be verified by: Approved consumers see the product while unauthorized project members cannot query it.
Incorrect Answers
A:That change addresses an S3 data-access investigation searches CloudTrail for object reads but only management events were enabled; it would not repair this incident.
B:That change addresses a Step Functions state invokes a Lambda using a role that trusts EC2 instead of the Step Functions service; it would not repair this incident.
D:That change addresses an S3 table is tagged `classification=restricted`, but its Lake Formation LF-Tag grant allows a broad organizational unit with no business need; it would not repair this incident.
Question 42
An on-premises Oracle source feeds DMS, but newly added tables never appear in a configured migration. Which technical dependency most directly explains this behavior?
- Map concurrency is uncapped relative to external rate limits.
- Table selection rules cover only the original schema or table set.
- Packaging does not cleanly bind compiled artifacts to the current source revision.
- The callback correlation contract is missing or insecure.
Explanation
Correct Answer
B:Table selection rules cover only the original schema or table set. The corresponding fix is to update reviewed DMS table mapping and validate permissions and schema-change handling.
Incorrect Answers
A:This diagnosis addresses another AWS case: A pipeline launches thousands of concurrent Step Functions Map tasks and saturates a small partner API. The dependency here is different.
C:This diagnosis addresses another AWS case: A SAM deployment packages an outdated Lambda handler because build artifacts from a previous branch were reused. The dependency here is different.
D:This diagnosis addresses another AWS case: A Step Functions Standard workflow waits for an external vendor callback but the task token is lost in logs. The dependency here is different.
Question 43
A team applies a reviewed fix for this situation: A tokenization pipeline uses a deterministic unkeyed hash on low-entropy postal identifiers and calls them irreversibly anonymous. Which observed outcome would most convincingly validate the fix?
- The user obtains aggregate headcount without querying raw compensation fields.
- An aged controlled audit fixture remains retrievable for the required period.
- A controlled object read produces a traceable data event with expected context.
- A sample output meets organizational reidentification risk requirements.
Explanation
Correct Answer
D:A sample output meets organizational reidentification risk requirements. This verifies the result of apply an approved privacy design with keyed tokenization or stronger controls and threat modeling.
Incorrect Answers
A:This would verify another situation: A Lake Formation table exposes a private salary column through a broad Athena SELECT grant when an analyst needs only aggregated headcount. It does not validate the current case.
B:This would verify another situation: An organization exports audit logs to S3 without lifecycle retention review and required records expire before annual audit. It does not validate the current case.
C:This would verify another situation: An S3 data-access investigation searches CloudTrail for object reads but only management events were enabled. It does not validate the current case.
Question 44
A team applies a reviewed fix for this situation: An AWS Glue job writes to a governed S3 target but lacks the Lake Formation data-location access permission required for its workflow. Which observed outcome would most convincingly validate the fix?
- The job writes only its registered approved table location.
- A sample output meets organizational reidentification risk requirements.
- The approved role reads the encrypted object but cannot decrypt unrelated keys.
- Approved consumers see the product while unauthorized project members cannot query it.
Explanation
Correct Answer
A:The job writes only its registered approved table location. This verifies the result of grant scoped data-location and catalog permissions alongside required IAM policies.
Incorrect Answers
B:This would verify another situation: A tokenization pipeline uses a deterministic unkeyed hash on low-entropy postal identifiers and calls them irreversibly anonymous. It does not validate the current case.
C:This would verify another situation: A Glue job reads an S3 object encrypted with a customer-managed KMS key and fails even though it has `s3:GetObject`. It does not validate the current case.
D:This would verify another situation: A SageMaker Catalog project shares a data product broadly across teams without recording owner and allowed purpose. It does not validate the current case.
Question 45
A DynamoDB application requires strongly consistent reads immediately after a successful critical write but queries a global secondary index. Which technical dependency most directly explains this behavior?
- The chosen read path cannot provide strong consistency on the GSI.
- The warehouse load lacks deterministic upsert/merge semantics.
- The catalog partition listing is not synchronized with newly written S3 prefixes.
- Storage lifecycle no longer reflects retention and access patterns.
Explanation
Correct Answer
A:The chosen read path cannot provide strong consistency on the GSI. The corresponding fix is to use a supported strongly consistent base-table or local-index read design where necessary.
Incorrect Answers
B:This diagnosis addresses another AWS case: A Redshift reporting pipeline accumulates duplicate business keys after retries because it appends without reconciling current versions. The dependency here is different.
C:This diagnosis addresses another AWS case: An Athena query of yesterday's S3 partition returns zero rows because its table metadata lacks that partition. The dependency here is different.
D:This diagnosis addresses another AWS case: A data lake keeps years of detailed application logs in S3 Standard despite infrequent historical access and an approved 90-day hot tier. The dependency here is different.
Question 46
A Glue crawler discovers an S3 path containing two incompatible CSV header layouts and produces a wide schema with ambiguous columns. Which technical dependency most directly explains this behavior?
- Schema representation prevents typed spatial validation and query optimization.
- Object lifecycle configuration conflicts with required retention and legal policy.
- Join/distribution key cardinality is unsuitable for balanced data movement.
- Schema discovery crosses incompatible source populations in one catalog grouping.
Explanation
Correct Answer
D:Schema discovery crosses incompatible source populations in one catalog grouping. The corresponding fix is to separate source prefixes/classifiers and create versioned tables with validated schema mappings.
Incorrect Answers
A:This diagnosis addresses another AWS case: A lake stores customer location coordinates as one unparsed text field while downstream joins require numeric latitude and longitude. The dependency here is different.
B:This diagnosis addresses another AWS case: An S3 data product has an approved seven-year retention requirement, but an engineer adds a 30-day expiration lifecycle rule. The dependency here is different.
C:This diagnosis addresses another AWS case: A Redshift table has highly skewed account IDs as a distribution key and one compute slice processes most rows. The dependency here is different.
Question 47
A Glue crawler crawls the entire lake for every hourly feed and adds unexpected tables from temporary staging prefixes. Which engineering change best addresses the underlying issue?
- Restrict crawler targets, table prefixes and schema-change behavior to approved locations.
- Review AUTO or more distributed keys and measure skew and join plans.
- Separate or explicitly model fact grain and join to dimensions at compatible levels.
- Tune supported export parallelism and downstream compaction based on file size and latency.
Explanation
Correct Answer
A:Restrict crawler targets, table prefixes and schema-change behavior to approved locations. It directly addresses the case cause (Crawler scope is broader than the governed dataset and includes nonauthoritative paths.) and should be verified by: The catalog contains only expected production datasets after a staging-file arrival.
Incorrect Answers
B:That change addresses a Redshift table has highly skewed account IDs as a distribution key and one compute slice processes most rows; it would not repair this incident.
C:That change addresses a Redshift star schema mixes order-line and order-header facts in the same table and reports double-count revenue; it would not repair this incident.
D:That change addresses a warehouse unload creates thousands of tiny output files, raising downstream S3 request and processing overhead; it would not repair this incident.
Question 48
A team applies a reviewed fix for this situation: A nightly data product uses a moving seven-day window but incoming source events arrive late and are excluded without a watermark policy. Which observed outcome would most convincingly validate the fix?
- A completed upstream fixture unblocks the DAG while failures follow the error path.
- A known delayed event updates the intended window according to policy.
- Correct row counts and bounded DPU-hours return in a repeatable fixture.
- A controlled event is consumed and appears in the authorized downstream sink.
Explanation
Correct Answer
B:A known delayed event updates the intended window according to policy. This verifies the result of implement event-time windows with a supported lateness allowance and correction/backfill strategy.
Incorrect Answers
A:This would verify another situation: An MWAA scheduled data DAG waits forever for an upstream batch because the external task reports completion through a different status name. It does not validate the current case.
C:This would verify another situation: A Glue job begins consuming twice its normal DPU budget after a transformation adds a repeated cross join. It does not validate the current case.
D:This would verify another situation: A Kinesis stream is receiving writes but downstream analytics remain empty after the consumer IAM role lost read permission. It does not validate the current case.
Question 49
A nightly aggregation counts an order once per status-change event rather than once per order ID. Which engineering change best addresses the underlying issue?
- Choose a stable order identity and the correct aggregation or distinct-current-state logic.
- Inspect DAG import errors and validate packaging dependencies before deployment.
- Separate ingestion capacity budgets and backpressure with appropriate queues or schedules.
- Use deterministic batch output keys or conditional commits and reconcile existing results on retry.
Explanation
Correct Answer
A:Choose a stable order identity and the correct aggregation or distinct-current-state logic. It directly addresses the case cause (The event grain is different from the intended business entity grain.) and should be verified by: A multi-status order contributes exactly one order to the verified report.
Incorrect Answers
B:That change addresses an MWAA DAG was deployed but its Python import fails, so no scheduled run appears; it would not repair this incident.
C:That change addresses a large historical data export shares the same small API rate limit as near-real-time orders and delays critical events; it would not repair this incident.
D:That change addresses an orchestrator invokes a Lambda that writes to S3 then times out; the retry writes a second output under a new random key; it would not repair this incident.
Question 50
A team applies a reviewed fix for this situation: A DynamoDB archival pipeline uses Scan without pagination and misses records beyond the first page. Which observed outcome would most convincingly validate the fix?
- Representative referential integrity tests pass after a controlled cutover.
- Archive row counts and key sets reconcile with the source snapshot.
- Test similar products rank appropriately for documented benchmark queries.
- A controlled report field traces back to the expected source attribute and job revision.
Explanation
Correct Answer
B:Archive row counts and key sets reconcile with the source snapshot. This verifies the result of iterate with the supported LastEvaluatedKey mechanism and checkpoint progress.
Incorrect Answers
A:This would verify another situation: An AWS DMS migration creates a new database table but foreign-key dependencies fail during cutover because schema compatibility was never rehearsed. It does not validate the current case.
C:This would verify another situation: An application seeks low-latency semantic recommendations but indexes product names as plain text without generated embeddings. It does not validate the current case.
D:This would verify another situation: A data team cannot determine whether a report column came from the original CRM source or an intermediate cleansing step. It does not validate the current case.
AWS Certified Data Engineer - Associate DEA-C01 Practice Tests