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 70
An MWAA DAG was deployed but its Python import fails, so no scheduled run appears. Which engineering change best addresses the underlying issue?
- Repartition data with appropriate cardinality and avoid bottlenecking single-stage operations.
- Inspect DAG import errors and validate packaging dependencies before deployment.
- Update reviewed DMS table mapping and validate permissions and schema-change handling.
- Use reproducible clean builds and validate the packaged Lambda handler in CI.
Explanation
Correct Answer
B:Inspect DAG import errors and validate packaging dependencies before deployment. It directly addresses the case cause (The scheduler cannot parse the DAG file and therefore cannot schedule its tasks.) and should be verified by: The DAG parses and a controlled run completes its expected task graph.
Incorrect Answers
A:That change addresses a data transformation uses one Spark partition for a terabyte input and only one executor stays busy; it would not repair this incident.
C:That change addresses an on-premises Oracle source feeds DMS, but newly added tables never appear in a configured migration; it would not repair this incident.
D:That change addresses a SAM deployment packages an outdated Lambda handler because build artifacts from a previous branch were reused; it would not repair this incident.
Question 71
A large ETL data structure uses a list for repeated membership checks and CPU use grows unexpectedly. Select THREE complementary measures that correctly repair and validate, and prevent recurrence of this failure.
- Increase the number of retries for a CPU-bound lookup loop.
- A load fixture has equivalent membership decisions at reduced compute time.
- Profile algorithmic complexity for hot-path data structures.
- Validate timestamp offsets and write a canonical UTC event-time field while retaining the source timestamp.
- Use an appropriate hashed lookup structure while preserving deterministic output behavior.
- Fixtures with present, null, and missing fields receive expected values or rejects.
Explanation
Correct Answers
B:A load fixture has equivalent membership decisions at reduced compute time. This is the observable result required before accepting the correction.
C:Profile algorithmic complexity for hot-path data structures. This protects against the following risk: Linear repeated lookups are inefficient for a high-cardinality membership workload.
E:Use an appropriate hashed lookup structure while preserving deterministic output behavior. The underlying cause is: Linear repeated lookups are inefficient for a high-cardinality membership workload.
Incorrect Answers
A:Increase the number of retries for a CPU-bound lookup loop. That shortcut conflicts with the stated requirement.
D:That corrective action is for a different case: A data ingestion service accepts API JSON but passes inconsistent event time zones to downstream partitions. It does not resolve this incident.
F:This would validate a different case: An API payload includes optional addresses but a transformation fails when a nullable nested object is absent. It does not verify the outcome required here.
Question 72
After resolving the following incident, which ongoing safeguard most directly prevents recurrence? A Redshift reporting job suddenly spends time redistributing a large fact table after a schema change.
- Compare query plans on major DDL/schema changes.
- Document sampling design and population coverage in analysis artifacts.
- Report sample sizes and require full validation for critical keys.
- Review dependency edges and intermediate outputs on each workflow change.
Explanation
Correct Answer
A:Compare query plans on major DDL/schema changes. This safeguards against a recurring cause: The changed table layout or join pattern increases data movement.
Incorrect Answers
B:That safeguard addresses another case: An Athena Spark notebook reads only a handful of development files yet a manager interprets its average as an entire production trend. It is not the control for this recurring failure.
C:That safeguard addresses another case: A streaming pipeline evaluates quality from a random sample of 10 messages and assumes it proves a million-row batch is correct. It is not the control for this recurring failure.
D:That safeguard addresses another case: An EMR workflow submits five jobs simultaneously but two require the first job's generated HDFS staging output. It is not the control for this recurring failure.
Question 73
An Athena query uses SELECT * on a wide Parquet table, although the report needs two measures and a date. Which technical dependency most directly explains this behavior?
- The query unnecessarily reads columns beyond its actual projection.
- Single-metric quality scoring hides unintended data loss.
- Pipeline retry handling and final quality checks do not preserve all expected groups.
- The pipeline lacks stable event-level uniqueness validation.
Explanation
Correct Answer
A:The query unnecessarily reads columns beyond its actual projection. The corresponding fix is to select only needed fields and apply effective partition predicates where applicable.
Incorrect Answers
B: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.
C:This diagnosis addresses another AWS case: A Spark aggregation produces incorrect category totals because one hot key is dropped after a task retry and the target doesn't reconcile. The dependency here is different.
D:This diagnosis addresses another AWS case: A daily sensor batch is duplicated after retry, causing every aggregate event count to double. The dependency here is different.
Question 74
A Step Functions run is marked succeeded although a downstream notification publish fails and no incident ticket is opened. Select THREE complementary measures that correctly repair and validate, and prevent recurrence of this failure.
- Model the notification as a checked task with failure handling or durable outbox.
- Use defensible stratified sampling with confidence limits or full checks for critical constraints.
- Test alert-delivery failure modes separately from ETL completion.
- Ignore notification API errors because the data job succeeded.
- A simulated notification outage produces recoverable failure evidence and eventual delivery.
- A maximum-size sample completes with a checkpointed durable output.
Explanation
Correct Answers
A:Model the notification as a checked task with failure handling or durable outbox. The underlying cause is: The workflow's success criteria omit an operationally required delivery dependency.
C:Test alert-delivery failure modes separately from ETL completion. This protects against the following risk: The workflow's success criteria omit an operationally required delivery dependency.
E:A simulated notification outage produces recoverable failure evidence and eventual delivery. This is the observable result required before accepting the correction.
Incorrect Answers
B:That corrective action is for a different case: A streaming pipeline evaluates quality from a random sample of 10 messages and assumes it proves a million-row batch is correct. It does not resolve this incident.
D:Ignore notification API errors because the data job succeeded. That shortcut conflicts with the stated requirement.
F:This would validate a different case: A monthly data load uses Lambda to copy hundreds of gigabytes in a single invocation and repeatedly times out. It does not verify the outcome required here.
Question 75
A streaming pipeline evaluates quality from a random sample of 10 messages and assumes it proves a million-row batch is correct. Which technical dependency most directly explains this behavior?
- Job terminal status is not equivalent to acceptance of the produced data product.
- The window aggregation does not specify a deterministic temporal frame.
- Workflow execution order lacks explicit job dependencies.
- The sample is too small or unrepresentative for a claimed whole-population guarantee.
Explanation
Correct Answer
D:The sample is too small or unrepresentative for a claimed whole-population guarantee. The corresponding fix is to use defensible stratified sampling with confidence limits or full checks for critical constraints.
Incorrect Answers
A: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.
B:This diagnosis addresses another AWS case: A data science notebook uses a rolling 7-day average without ordering by event date, so results change with input row order. The dependency here is different.
C:This diagnosis addresses another AWS case: An EMR workflow submits five jobs simultaneously but two require the first job's generated HDFS staging output. The dependency here is different.
Question 76
After resolving the following incident, which ongoing safeguard most directly prevents recurrence? An operational RDS database has a complex read-only report consuming most CPU at peak checkout time.
- Document fact grain and validate cardinality in data model reviews.
- Validate file format and compression before metadata publication.
- Document source-target deletion expectations and lag metrics.
- Set resource-isolation objectives for OLTP and BI loads.
Explanation
Correct Answer
D:Set resource-isolation objectives for OLTP and BI loads. This safeguards against a recurring cause: Analytical query workload competes with the transaction service.
Incorrect Answers
A:That safeguard addresses another case: A Redshift star schema mixes order-line and order-header facts in the same table and reports double-count revenue. It is not the control for this recurring failure.
B:That safeguard addresses another case: An S3 prefix contains `.json.gz` objects but the Glue crawler labels them as raw JSON and downstream parsers fail. It is not the control for this recurring failure.
C:That safeguard addresses another case: An S3 replication configuration excludes delete markers, but a team assumes target data will reflect source deletes instantly. It is not the control for this recurring failure.
Question 77
After resolving the following incident, which ongoing safeguard most directly prevents recurrence? A Step Functions run is marked succeeded although a downstream notification publish fails and no incident ticket is opened.
- Require multidimensional quality gates before final publish.
- Report sample sizes and require full validation for critical keys.
- Test alert-delivery failure modes separately from ETL completion.
- Monitor bytes scanned per report and require column selection in review.
Explanation
Correct Answer
C:Test alert-delivery failure modes separately from ETL completion. This safeguards against a recurring cause: The workflow's success criteria omit an operationally required delivery dependency.
Incorrect Answers
A:That safeguard addresses another case: A data team declares a successful cleanup because duplicate percentage fell, but the job also dropped valid unique rows. It is not the control for this recurring failure.
B:That safeguard addresses another case: A streaming pipeline evaluates quality from a random sample of 10 messages and assumes it proves a million-row batch is correct. It is not the control for this recurring failure.
D:That safeguard addresses another case: An Athena query uses SELECT * on a wide Parquet table, although the report needs two measures and a date. It is not the control for this recurring failure.
Question 78
A Spark pipeline includes a wide shuffle stage because it joins on a function applied to both tables, preventing efficient key reuse. Which engineering change best addresses the underlying issue?
- Document and validate the record envelope and implement the matching decode path.
- Precompute consistent normalized join keys and select suitable partitioning and join strategies.
- Use reproducible clean builds and validate the packaged Lambda handler in CI.
- Consume a supported completion event or atomic finalized object naming before ingestion.
Explanation
Correct Answer
B:Precompute consistent normalized join keys and select suitable partitioning and join strategies. It directly addresses the case cause (On-the-fly key normalization causes expensive join planning and movement.) and should be verified by: Join output stays correct while shuffle cost and job duration decline.
Incorrect Answers
A:That change addresses a streaming producer writes compressed messages into a format the Lambda consumer assumes is plain UTF-8; it would not repair this incident.
C:That change addresses a SAM deployment packages an outdated Lambda handler because build artifacts from a previous branch were reused; it would not repair this incident.
D:That change addresses a partner uploads a CSV over SFTP to Transfer Family but a load starts before the file finishes writing; it would not repair this incident.
Question 79
A nightly lake job publishes versioned S3 snapshots but deletes all old snapshots before the replacement is fully validated. Which technical dependency most directly explains this behavior?
- The publish process removes its rollback point prematurely.
- Object storage access patterns do not match the required high-frequency key-value access.
- Crawler scope is broader than the governed dataset and includes nonauthoritative paths.
- A lake table lacks effective columnar layout and pruning for its query pattern.
Explanation
Correct Answer
A:The publish process removes its rollback point prematurely. The corresponding fix is to use staged validation and controlled retention/cleanup of replaced snapshots.
Incorrect Answers
B:This diagnosis addresses another AWS case: An online session store uses S3 object listing as a low-latency millisecond key lookup service and response times are erratic. The dependency here is different.
C:This diagnosis addresses another AWS case: A Glue crawler crawls the entire lake for every hourly feed and adds unexpected tables from temporary staging prefixes. The dependency here is different.
D:This diagnosis addresses another AWS case: An Athena query reads huge raw JSON partitions for a narrow timestamp filter and scans far more bytes than expected. The dependency here is different.
Question 80
An ETL task in Glue times out only when a small fraction of keys dominate the daily partition. Which engineering change best addresses the underlying issue?
- Reconcile accepted, filtered and quarantined records with explicit balance equations.
- Inspect Spark stage metrics and split/salt hotspots or change skewed join strategy.
- Aggregate by validated stable user identity and the intended time-window rules.
- Join on documented unique customer identifiers and enforce suitable grain.
Explanation
Correct Answer
B:Inspect Spark stage metrics and split/salt hotspots or change skewed join strategy. It directly addresses the case cause (Skew creates straggler executors and prevents completion within the SLA.) and should be verified by: Long-running tasks improve without changing aggregate results.
Incorrect Answers
A:That change addresses a data quality gate compares raw and target record totals without accounting for intentional filter exclusions, falsely failing clean batches; it would not repair this incident.
C:That change addresses a marketing report uses COUNT(*) of event records as its active user metric and overstates adoption when users retry; it would not repair this incident.
D:That change addresses a Redshift SQL view joins two tables on customer name, and a same-name collision merges unrelated accounts; it would not repair this incident.
AWS Certified Data Engineer - Associate DEA-C01 Practice Tests