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 270
After resolving the following incident, which ongoing safeguard most directly prevents recurrence? An MWAA DAG was deployed but its Python import fails, so no scheduled run appears.
- Require DAG import and syntax checks in CI.
- Review retention and recovery objectives whenever downstream processing latency changes.
- Record expected grain for every output fact table.
- Measure freshness and refresh overhead before materialization.
Explanation
Correct Answer
A:Require DAG import and syntax checks in CI. This safeguards against a recurring cause: The scheduler cannot parse the DAG file and therefore cannot schedule its tasks.
Incorrect Answers
B:That safeguard addresses another case: A fraud detector needs to reread yesterday's Kinesis records but the stream uses its short default retention window. It is not the control for this recurring failure.
C:That safeguard addresses another case: A nightly aggregation counts an order once per status-change event rather than once per order ID. It is not the control for this recurring failure.
D:That safeguard addresses another case: A Redshift transformation materializes a complex subquery repeatedly in one reporting workflow and exceeds its compute budget. It is not the control for this recurring failure.
Question 271
A team applies a reviewed fix for this situation: A dataset uses Iceberg but Spark and Athena query different catalogs and show conflicting table snapshots. Which observed outcome would most convincingly validate the fix?
- A controlled report field traces back to the expected source attribute and job revision.
- Archive row counts and key sets reconcile with the source snapshot.
- Both engines read the same committed table snapshot within planned freshness bounds.
- The catalog contains only expected production datasets after a staging-file arrival.
Explanation
Correct Answer
C:Both engines read the same committed table snapshot within planned freshness bounds. This verifies the result of unify the supported catalog/table identity and validate snapshot visibility across engines.
Incorrect Answers
A: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.
B:This would verify another situation: A DynamoDB archival pipeline uses Scan without pagination and misses records beyond the first page. It does not validate the current case.
D:This would verify another situation: A Glue crawler crawls the entire lake for every hourly feed and adds unexpected tables from temporary staging prefixes. It does not validate the current case.
Question 272
A CloudWatch dashboard mixes Glue processed-record counts with Kinesis PutRecords count and calls them identical pipeline throughput. Which technical dependency most directly explains this behavior?
- Service metrics represent different stages and may count retries or batches differently.
- Presence checking does not enforce the field's required format contract.
- The workflow has no buffering or explicit throughput regulation at the ingress boundary.
- Recipe selection and deployment version are not aligned.
Explanation
Correct Answer
A:Service metrics represent different stages and may count retries or batches differently. The corresponding fix is to define consistent stage-level event counts and correlate stable IDs at checkpoints.
Incorrect Answers
B:This diagnosis addresses another AWS case: A Glue data quality rule checks only that an email column is nonnull but accepts invalid malformed addresses. The dependency here is different.
C:This diagnosis addresses another AWS case: An orchestrated data processing task receives tens of thousands of S3 events, causing Lambda reserved concurrency exhaustion. The dependency here is different.
D:This diagnosis addresses another AWS case: A Glue DataBrew recipe was changed interactively but the production pipeline still applies a previous published recipe version. The dependency here is different.
Question 273
A team applies a reviewed fix for this situation: A batch import uses a Lambda in a private subnet that cannot reach S3 because no NAT or S3 endpoint path is configured. Which observed outcome would most convincingly validate the fix?
- The second job starts only after the first has committed the required partition.
- Object counts decrease while all events remain available and fresh enough.
- Decompressed samples match checksums and expected record counts.
- The Lambda retrieves the intended object without an unrestricted internet route.
Explanation
Correct Answer
D:The Lambda retrieves the intended object without an unrestricted internet route. This verifies the result of configure a supported S3 VPC endpoint or justified outbound path with required IAM and endpoint policies.
Incorrect Answers
A:This would verify another situation: A scheduled Glue workflow triggers two jobs concurrently though the second requires the first output's partition. It does not validate the current case.
B:This would verify another situation: A Lambda process writes individual small S3 JSON files for millions of events and downstream scans slow dramatically. It does not validate the current case.
C:This would verify another situation: A processing job ingests gzipped files but its connector treats their contents as uncompressed text and creates corrupt rows. It does not validate the current case.
Question 274
A team applies a reviewed fix for this situation: A daily Python ingestion script calls S3 ListObjectsV2 only once and misses most keys after data growth. Which observed outcome would most convincingly validate the fix?
- A representative connector read works in the target runtime without fallback hacks.
- An inventory fixture beyond one page reconciles with all expected object keys.
- A high-precision fixture survives transformation without unexpected rounding loss.
- A transient injected failure remains logged, while persistent failures trigger on-call alerts.
Explanation
Correct Answer
B:An inventory fixture beyond one page reconciles with all expected object keys. This verifies the result of use the supported paginator/continuation token and durable inventory checkpoints.
Incorrect Answers
A:This would verify another situation: A data pipeline updates its Glue version but custom connector dependencies fail at initialization. It does not validate the current case.
C:This would verify another situation: An upstream system changes a decimal field from two to four digits of precision and rounding introduces revenue drift. It does not validate the current case.
D:This would verify another situation: A monitoring rule sees one Athena query failure and pages the full team despite a known transient backend retry. It does not validate the current case.
Question 275
An EventBridge schedule starts a warehouse load during an upstream S3 export rather than after all files are ready. Select THREE complementary measures that correctly repair and validate, and prevent recurrence of this failure.
- Add a fixed two-minute sleep without a producer completion signal.
- Enforce producer-consumer handoff contracts and late-arrival tests.
- The published job serializes work to executors and produces correct output.
- Use deterministic batch output keys or conditional commits and reconcile existing results on retry.
- The load starts only when the reviewed export completion condition is met.
- Use an explicit completed-manifest event or a sensor/check against expected export state.
Explanation
Correct Answers
B:Enforce producer-consumer handoff contracts and late-arrival tests. This protects against the following risk: A wall-clock trigger is not a reliable data-completion dependency.
E:The load starts only when the reviewed export completion condition is met. This is the observable result required before accepting the correction.
F:Use an explicit completed-manifest event or a sensor/check against expected export state. The underlying cause is: A wall-clock trigger is not a reliable data-completion dependency.
Incorrect Answers
A:Add a fixed two-minute sleep without a producer completion signal. That shortcut conflicts with the stated requirement.
C:This would validate a different case: A team changes an analytics library but releases a job without checking distributed task serialization compatibility. It does not verify the outcome required here.
D:That corrective action is for a different case: An orchestrator invokes a Lambda that writes to S3 then times out; the retry writes a second output under a new random key. It does not resolve this incident.
Question 276
A lake stores customer location coordinates as one unparsed text field while downstream joins require numeric latitude and longitude. Which technical dependency most directly explains this behavior?
- Columnar analytical storage is misaligned with the application's OLTP write workload.
- The object layout introduces avoidable fetch/decompression overhead for granular hot data.
- External-table query capability is confused with supported table mutation semantics.
- Schema representation prevents typed spatial validation and query optimization.
Explanation
Correct Answer
D:Schema representation prevents typed spatial validation and query optimization. The corresponding fix is to model validated numeric coordinate fields with units and location quality checks.
Incorrect Answers
A:This diagnosis addresses another AWS case: A Redshift analytics warehouse holds transactional checkout rows that require thousands of short atomic row updates per second. The dependency here is different.
B:This diagnosis addresses another AWS case: A customer expects fast key-value reads over frequently accessed session state yet stores every session in a multi-megabyte compressed S3 archive. The dependency here is different.
C:This diagnosis addresses another AWS case: A Redshift query joins external and local datasets but expects Spectrum to automatically overwrite remote S3 data during UPDATE. The dependency here is different.
Question 277
A team applies a reviewed fix for this situation: A Redshift Spectrum external table points to S3 partitions whose IAM role cannot read the new prefix after an account move. Which observed outcome would most convincingly validate the fix?
- Region-filtered queries prune to the expected physical prefixes.
- A controlled external-table query reads the intended new partition only.
- A test order maps to exactly the customer attributes valid at transaction time.
- A representative query returns both historical and new data exactly once.
Explanation
Correct Answer
B:A controlled external-table query reads the intended new partition only. This verifies the result of grant scoped S3 and catalog/Lake Formation access to the Redshift authorized role.
Incorrect Answers
A:This check verifies a different issue: A table claims a `region` partition key but the written S3 paths use `geography=...`, so Athena pruning fails. It is not sufficient evidence for this case.
C:This would verify another situation: A warehouse fact table is joined to customer history using only customer ID, multiplying matches across changing customer versions. It does not validate the current case.
D:This would verify another situation: An S3-based table changes from hourly to daily partitions while old writers still publish hourly paths, giving inconsistent query results. It does not validate the current case.
Question 278
A Glue PySpark job fails when an upstream field changes from integer to string in some JSON documents. Which engineering change best addresses the underlying issue?
- Store an execution identity and use conditional state transitions before starting work.
- Use a stable manifest identifier with transactional state before launching or committing loads.
- Apply an explicit compatible schema or deliberate conversion and quarantine unparseable values.
- Follow documented API pagination and persist progress in resumable checkpoints.
Explanation
Correct Answer
C:Apply an explicit compatible schema or deliberate conversion and quarantine unparseable values. It directly addresses the case cause (Schema inference is unstable across source data evolution.) and should be verified by: Mixed old/new fixtures produce expected typed output or documented rejects.
Incorrect Answers
A:That change addresses an EventBridge rule matches both replayed and new events and starts two identical pipelines for the same batch; it would not repair this incident.
B:That change addresses a production Glue workflow receives the same completed-file notification twice and creates two warehouse loads; it would not repair this incident.
D:That change addresses a daily batch extraction reads only the first page of a vendor REST API and silently loses subsequent records; it would not repair this incident.
Question 279
A Firehose pipeline is expected to deliver individual records instantly, yet it buffers batches before S3 delivery. Which technical dependency most directly explains this behavior?
- Queue-consumer concurrency exceeds the sink's sustainable write capacity.
- Delivery buffering settings and destination behavior conflict with the required freshness.
- The callback correlation contract is missing or insecure.
- Invocation concurrency is not budgeted against account capacity and downstream rate limits.
Explanation
Correct Answer
B:Delivery buffering settings and destination behavior conflict with the required freshness. The corresponding fix is to choose suitable supported buffering and verify whether the freshness SLA fits Firehose delivery.
Incorrect Answers
A:This diagnosis addresses another AWS case: An SQS-backed processor overwhelms a downstream database after scaling consumers without any concurrency cap. The dependency here is different.
C: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.
D:This diagnosis addresses another AWS case: A Lambda ETL function exhausts concurrency during a flash sale, causing fresh events to be throttled. The dependency here is different.
Question 280
A team applies a reviewed fix for this situation: A Glue data quality rule checks only that an email column is nonnull but accepts invalid malformed addresses. Which observed outcome would most convincingly validate the fix?
- Execution plan and runtime return within accepted bounds with identical answers.
- A completed upstream fixture unblocks the DAG while failures follow the error path.
- Malformed fixture values fail quality checks without discarding unrelated valid records.
- Long-running tasks improve without changing aggregate results.
Explanation
Correct Answer
C:Malformed fixture values fail quality checks without discarding unrelated valid records. This verifies the result of combine nullable, format, and authorized-value validation with appropriate error routing.
Incorrect Answers
A:This would verify another situation: A Redshift reporting job suddenly spends time redistributing a large fact table after a schema change. It does not validate the current case.
B: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.
D:This would verify another situation: An ETL task in Glue times out only when a small fraction of keys dominate the daily partition. It does not validate the current case.
AWS Certified Data Engineer - Associate DEA-C01 Practice Tests