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 1080
A large ETL data structure uses a list for repeated membership checks and CPU use grows unexpectedly. Which engineering change best addresses the underlying issue?
- Apply an explicit compatible schema or deliberate conversion and quarantine unparseable values.
- Use an appropriate hashed lookup structure while preserving deterministic output behavior.
- Evaluate a compatible materialized view or staged aggregate with an explicit refresh policy.
- Precompute consistent normalized join keys and select suitable partitioning and join strategies.
Explanation
Correct Answer
B:Use an appropriate hashed lookup structure while preserving deterministic output behavior. It directly addresses the case cause (Linear repeated lookups are inefficient for a high-cardinality membership workload.) and should be verified by: A load fixture has equivalent membership decisions at reduced compute time.
Incorrect Answers
A:That change addresses a Glue PySpark job fails when an upstream field changes from integer to string in some JSON documents; it would not repair this incident.
C:That change addresses a Redshift transformation materializes a complex subquery repeatedly in one reporting workflow and exceeds its compute budget; it would not repair this incident.
D:That change addresses a Spark pipeline includes a wide shuffle stage because it joins on a function applied to both tables, preventing efficient key reuse; it would not repair this incident.
Question 1081
A fraud detector needs to reread yesterday's Kinesis records but the stream uses its short default retention window. Select TWO complementary measures that correctly repair and validate this failure.
- Evaluate a broadcast join or other optimized join strategy within Glue/Spark memory limits.
- A replay starting at the intended timestamp retrieves the retained events.
- A representative time-window report has correct results with lower CPU/runtime.
- Assume that creating a new consumer restores expired stream records.
- Configure sufficient Kinesis retention and checkpoint offsets before the outage window expires.
Explanation
Correct Answers
B:A replay starting at the intended timestamp retrieves the retained events. This is the observable result required before accepting the correction.
E:Configure sufficient Kinesis retention and checkpoint offsets before the outage window expires. The underlying cause is: The consumer's recovery period exceeds the stream's retained data duration.
Incorrect Answers
A:That corrective action is for a different case: A Glue job joins a tiny lookup table to billions of rows and performs a full distributed shuffle. It does not resolve this incident.
C:This would validate a different case: A Redshift query repeatedly casts a large timestamp string field during aggregation and consumes excess CPU. It does not verify the outcome required here.
D:Assume that creating a new consumer restores expired stream records. That shortcut conflicts with the stated requirement.
Question 1082
A team applies a reviewed fix for this situation: An Iceberg table's snapshot history grows as frequent small commits accumulate and query planning becomes slow. Which observed outcome would most convincingly validate the fix?
- An overwritten fixture can be restored within the intended recovery interval.
- A newly onboarded sensitive table receives the intended governed classification.
- Planning overhead falls while required rollback snapshots remain available.
- Aged test objects transition as expected while required retrieval remains possible.
Explanation
Correct Answer
C:Planning overhead falls while required rollback snapshots remain available. This verifies the result of run supported snapshot expiration and metadata cleanup with retention safeguards.
Incorrect Answers
A:This would verify another situation: An S3 lifecycle rule expires noncurrent object versions immediately, preventing recovery from accidental overwrites. It does not validate the current case.
B:This would verify another situation: A data catalog stores PII labels only as free-text comments, so new tables bypass a tagging-based access process. It does not validate the current case.
D:This would verify another situation: A data lake keeps years of detailed application logs in S3 Standard despite infrequent historical access and an approved 90-day hot tier. It does not validate the current case.
Question 1083
A team applies a reviewed fix for this situation: A geospatial data catalog is placed in DynamoDB with no defined access key and engineers scan the entire table for each location. Which observed outcome would most convincingly validate the fix?
- Queries return comparable relevant neighbors from a consistent model representation.
- A controlled subject deletion is absent from permitted current and derived query paths.
- An injected failed publish leaves the last approved snapshot accessible.
- Representative spatial lookups return correctly without full-table scans.
Explanation
Correct Answer
D:Representative spatial lookups return correctly without full-table scans. This verifies the result of select an appropriate supported index or purpose-built query store using measured predicates.
Incorrect Answers
A:This would verify another situation: A vector retrieval index stores embeddings from two incompatible model versions in one dimension-dependent collection. It does not validate the current case.
B:This would verify another situation: An analytics partition must be removed under a deletion request, yet its historical copies persist in untracked S3 archive paths. It does not validate the current case.
C:This would verify another situation: A nightly lake job publishes versioned S3 snapshots but deletes all old snapshots before the replacement is fully validated. It does not validate the current case.
Question 1084
A data ingestion service accepts API JSON but passes inconsistent event time zones to downstream partitions. Which technical dependency most directly explains this behavior?
- The workflow treats the service invocation acknowledgement as a completed workload.
- Incoming data representation no longer matches the table's expected date parsing.
- Upstream event timestamps lack a normalized timezone and parsing contract.
- Running job artifacts are not tied to reviewed version history.
Explanation
Correct Answer
C:Upstream event timestamps lack a normalized timezone and parsing contract. The corresponding fix is to validate timestamp offsets and write a canonical UTC event-time field while retaining the source timestamp.
Incorrect Answers
A:This diagnosis addresses another AWS case: A Step Functions pipeline sends a notification before the ETL task's asynchronous execution actually completes. The dependency here is different.
B:This diagnosis addresses another AWS case: A Redshift COPY import fails on a changed date format in one batch even though prior files loaded. The dependency here is different.
D:This diagnosis addresses another AWS case: A data engineering team manually changes Glue scripts on S3 without source control or a rollback identifier. The dependency here is different.
Question 1085
A small dimension table joins huge Redshift facts, but an unnecessarily EVEN distribution causes repeated data transfer. Select TWO complementary measures that correctly repair and validate this failure.
- Evaluate Redshift AUTO distribution or a justified ALL/KEY strategy from query plans.
- Invalid coordinates are rejected and valid ones support intended filters.
- Create governed business catalog descriptions and owner/lineage metadata in the supported catalog product.
- Apply DISTSTYLE ALL to every multi-terabyte fact table.
- Network redistribution and join latency improve with unchanged outputs.
Explanation
Correct Answers
A:Evaluate Redshift AUTO distribution or a justified ALL/KEY strategy from query plans. The underlying cause is: Data placement increases redistribution for a frequently used join.
E:Network redistribution and join latency improve with unchanged outputs. This is the observable result required before accepting the correction.
Incorrect Answers
B:This would validate a different case: A lake stores customer location coordinates as one unparsed text field while downstream joins require numeric latitude and longitude. It does not verify the outcome required here.
C:That corrective action is for a different case: An analytics team relies on Glue technical table names to determine which datasets are permitted for finance reporting. It does not resolve this incident.
D:Apply DISTSTYLE ALL to every multi-terabyte fact table. That shortcut conflicts with the stated requirement.
Question 1086
After resolving the following incident, which ongoing safeguard most directly prevents recurrence? A nightly data product uses a moving seven-day window but incoming source events arrive late and are excluded without a watermark policy.
- Separate compute success from business-data acceptance gates.
- Document allowed lateness and watermark monitoring by source.
- Test pagination and retries against large synthetic bucket prefixes.
- Monitor end-to-end flow, not producer success alone.
Explanation
Correct Answer
B:Document allowed lateness and watermark monitoring by source. This safeguards against a recurring cause: Data freshness and event-time completeness assumptions are not explicit.
Incorrect Answers
A:That safeguard addresses another case: A Glue ETL job completes with warnings but the orchestrator assumes success despite a downstream quality check failing. It is not the control for this recurring failure.
C:That safeguard addresses another case: A daily Python ingestion script calls S3 ListObjectsV2 only once and misses most keys after data growth. It is not the control for this recurring failure.
D:That safeguard addresses another case: A Kinesis stream is receiving writes but downstream analytics remain empty after the consumer IAM role lost read permission. It is not the control for this recurring failure.
Question 1087
A fact table in Redshift filters mostly on event date but load order does not correlate with the filter, driving wide block scans. Which engineering change best addresses the underlying issue?
- Apply a stable catalog schema and quarantine malformed headers or records upstream.
- Record source, transformations and versioned lineage in supported catalog/project metadata.
- Measure query plans and evaluate AUTO or an appropriate event-time sort design.
- Review AUTO or more distributed keys and measure skew and join plans.
Explanation
Correct Answer
C:Measure query plans and evaluate AUTO or an appropriate event-time sort design. It directly addresses the case cause (The current sort/physical layout is unhelpful for common predicates.) and should be verified by: A selective date query scans fewer blocks without losing late records.
Incorrect Answers
A:That change addresses a crawler changes a decimal sales column to string after encountering a nonnumeric banner row in one export; it would not repair this incident.
B:That change addresses a data team cannot determine whether a report column came from the original CRM source or an intermediate cleansing step; it would not repair this incident.
D: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.
Question 1088
A cross-region disaster recovery table is restored from an old snapshot, and CDC replication starts from an incompatible new checkpoint. Which technical dependency most directly explains this behavior?
- Recovery snapshot and change-stream offsets do not represent a consistent recovery point.
- The catalog partition listing is not synchronized with newly written S3 prefixes.
- Partition metadata and physical prefix naming do not agree.
- The two metastore environments are not synchronized.
Explanation
Correct Answer
A:Recovery snapshot and change-stream offsets do not represent a consistent recovery point. The corresponding fix is to restore a compatible snapshot/checkpoint pair and reconcile changes before resuming writes.
Incorrect Answers
B: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.
C:This diagnoses a different AWS data-engineering case: A table claims a `region` partition key but the written S3 paths use `geography=...`, so Athena pruning fails. It does not account for the stated dependency.
D:This diagnosis addresses another AWS case: A Hive metastore-based EMR Spark job writes a new partition but Athena never sees it through Glue Data Catalog. The dependency here is different.
Question 1089
A Kinesis stream is receiving writes but downstream analytics remain empty after the consumer IAM role lost read permission. Which technical dependency most directly explains this behavior?
- The orchestration integration returns before the asynchronous ETL work finishes.
- Stream producer health is separate from the consumer's authorization and processing.
- Job terminal status is not equivalent to acceptance of the produced data product.
- Single-metric quality scoring hides unintended data loss.
Explanation
Correct Answer
B:Stream producer health is separate from the consumer's authorization and processing. The corresponding fix is to inspect consumer access-denied logs and restore narrowly scoped Kinesis permissions.
Incorrect Answers
A:This diagnosis addresses another AWS case: A Step Functions data pipeline invokes Glue using a request/response integration and immediately launches Athena against unfinished output. The dependency here is different.
C:This diagnosis addresses another AWS case: A Glue ETL job completes with warnings but the orchestrator assumes success despite a downstream quality check failing. The dependency here is different.
D:This diagnosis addresses another AWS case: A data team declares a successful cleanup because duplicate percentage fell, but the job also dropped valid unique rows. The dependency here is different.
Question 1090
A data catalog stores PII labels only as free-text comments, so new tables bypass a tagging-based access process. Which engineering change best addresses the underlying issue?
- Grant scoped bucket permissions and necessary KMS access to the Redshift execution role.
- Apply approved standardized catalog classification tags or LF-Tags and validate inherited rules.
- Apply application-level expiry checks where strict visibility is required and keep TTL for eventual cleanup.
- Plan a suitable alternate index or redesign around known query requirements.
Explanation
Correct Answer
B:Apply approved standardized catalog classification tags or LF-Tags and validate inherited rules. It directly addresses the case cause (Inconsistent metadata taxonomies prevent reliable automated governance.) and should be verified by: A newly onboarded sensitive table receives the intended governed classification.
Incorrect Answers
A:That change addresses a Redshift UNLOAD writes reporting data to an S3 bucket in another account but fails with access denied; it would not repair this incident.
C:That change addresses a DynamoDB table contains session records with expired timestamps but items remain visible immediately after expiry; it would not repair this incident.
D:That change addresses a DynamoDB table uses composite key `tenant#date` but most reads are by `transaction_id` only and become scans; it would not repair this incident.
AWS Certified Data Engineer - Associate DEA-C01 Practice Tests