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 680
A Lambda processor logs errors but its CloudWatch Logs retention is shorter than the postmortem evidence requirement. Which engineering change best addresses the underlying issue?
- Reconcile accepted, filtered and quarantined records with explicit balance equations.
- Run a null/uniqueness check in Glue or SQL and quarantine failing rows or batches.
- Set an appropriate retention and controlled access policy for log groups.
- Buffer events with a supported queue or stream and cap downstream concurrent workers.
Explanation
Correct Answer
C:Set an appropriate retention and controlled access policy for log groups. It directly addresses the case cause (Operational log retention is not aligned with audit or incident policy.) and should be verified by: A test log remains available through the required investigation period.
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.
B:That change addresses a batch containing a required `customer_id` null value is committed to Redshift and breaks joins the next day; it would not repair this incident.
D:That change addresses an orchestrated data processing task receives tens of thousands of S3 events, causing Lambda reserved concurrency exhaustion; it would not repair this incident.
Question 681
A scheduled Glue workflow triggers two jobs concurrently though the second requires the first output's partition. Which engineering change best addresses the underlying issue?
- Use a stable ingestion event ID with conditional writes or a deduplicating transaction design.
- Add an explicit predecessor-success trigger or workflow state dependency.
- Use supported partial batch failure handling and idempotent sink writes with a failure destination.
- Inspect key distribution and apply skew-aware partitioning, salting, or alternate aggregation strategy.
Explanation
Correct Answer
B:Add an explicit predecessor-success trigger or workflow state dependency. It directly addresses the case cause (Job ordering fails to express the producer-consumer dependency.) and should be verified by: The second job starts only after the first has committed the required partition.
Incorrect Answers
A:That change addresses an ingestion app writes identical DynamoDB item updates after a network retry and an audit counter increments twice; it would not repair this incident.
C:That change addresses a Lambda Kinesis event-source mapping repeatedly delivers the same batch after one malformed record fails; it would not repair this incident.
D:That change addresses an EMR Spark job sends all rows for a popular customer to one reducer and fails despite plenty of idle cores; it would not repair this incident.
Question 682
An online session store uses S3 object listing as a low-latency millisecond key lookup service and response times are erratic. Which technical dependency most directly explains this behavior?
- Crawler scope is broader than the governed dataset and includes nonauthoritative paths.
- Archival extraction ignores DynamoDB continuation keys.
- Unvalidated mixed-format source rows contaminated schema inference.
- Object storage access patterns do not match the required high-frequency key-value access.
Explanation
Correct Answer
D:Object storage access patterns do not match the required high-frequency key-value access. The corresponding fix is to choose an appropriately modeled DynamoDB or other eligible low-latency store with measured capacity.
Incorrect Answers
A: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.
B:This diagnosis addresses another AWS case: A DynamoDB archival pipeline uses Scan without pagination and misses records beyond the first page. The dependency here is different.
C:This diagnosis addresses another AWS case: A crawler changes a decimal sales column to string after encountering a nonnumeric banner row in one export. The dependency here is different.
Question 683
A monitoring rule sees one Athena query failure and pages the full team despite a known transient backend retry. Which technical dependency most directly explains this behavior?
- The workflow's sensor condition does not match the actual upstream terminal status.
- Alarm logic lacks an agreed signal threshold and actionable severity.
- Pipeline retry handling and final quality checks do not preserve all expected groups.
- The data workload exceeds Lambda's practical bounded execution model.
Explanation
Correct Answer
B:Alarm logic lacks an agreed signal threshold and actionable severity. The corresponding fix is to correlate bounded retry recovery with sustained failure-rate or SLA breach conditions.
Incorrect Answers
A:This diagnosis addresses another AWS case: An MWAA scheduled data DAG waits forever for an upstream batch because the external task reports completion through a different status name. 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 monthly data load uses Lambda to copy hundreds of gigabytes in a single invocation and repeatedly times out. The dependency here is different.
Question 684
A team applies a reviewed fix for this situation: An AWS MWAA DAG has no task-level retries or SLA alerts, and a brief Glue API throttle causes a missed daily close. Which observed outcome would most convincingly validate the fix?
- The load starts only when the reviewed export completion condition is met.
- The published job serializes work to executors and produces correct output.
- A simulated transient failure recovers and persistent failures produce timely alerts.
- One consumer restarts without altering the other consumer's offset.
Explanation
Correct Answer
C:A simulated transient failure recovers and persistent failures produce timely alerts. This verifies the result of configure bounded task retries, failure callbacks and deadline-aware notifications.
Incorrect Answers
A:This would verify another situation: An EventBridge schedule starts a warehouse load during an upstream S3 export rather than after all files are ready. It does not validate the current case.
B:This would verify another situation: A team changes an analytics library but releases a job without checking distributed task serialization compatibility. It does not validate the current case.
D:This would verify another situation: Two Kinesis consumers must independently recover after a deployment, but one team reuses the other's checkpoint store. It does not validate the current case.
Question 685
A clickstream pipeline converts all nested attributes to strings before storage, making numeric analytics unreliable. Which technical dependency most directly explains this behavior?
- Invocation concurrency is not budgeted against account capacity and downstream rate limits.
- Workflow handoff lacks a complete machine-readable output contract.
- Producer bootstrap configuration does not follow the advertised Kafka broker endpoint set.
- Transformation discards intended field types and semantic metadata.
Explanation
Correct Answer
D:Transformation discards intended field types and semantic metadata. The corresponding fix is to apply a defined typed schema, normalize units, and retain raw payloads for replay.
Incorrect Answers
A: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.
B:This diagnosis addresses another AWS case: An ETL task finishes but its success event omits the S3 prefix and schema version needed downstream. The dependency here is different.
C:This diagnosis addresses another AWS case: An MSK producer succeeds only intermittently after brokers change because its connection string contains one retired broker address. The dependency here is different.
Question 686
An Athena query for CloudTrail logs shows a missing day because the log data lake partitions were never registered. Which engineering change best addresses the underlying issue?
- Scope shared views, roles and periodic reauthorization with a documented owner.
- Review CloudTrail denied access and compare effective role, bucket and KMS permissions.
- Configure supported KMS key policy, IAM and replication encryption settings for the intended accounts.
- Confirm CloudTrail delivery, then repair Athena catalog partitions or approved projection.
Explanation
Correct Answer
D:Confirm CloudTrail delivery, then repair Athena catalog partitions or approved projection. It directly addresses the case cause (Audit log delivery and analytics catalog partition visibility are separate requirements.) and should be verified by: Controlled events from the missing day are queryable after catalog correction.
Incorrect Answers
A:That change addresses a Redshift datashare grants partner analysts access to a customer data mart without a purpose or term limit; it would not repair this incident.
B:That change addresses an S3 lake read works with an administrator role but fails with the production ETL role, and the team assumes the dataset is corrupt; it would not repair this incident.
C:That change addresses a data lake copies SSE-KMS objects across AWS accounts but the destination principal cannot decrypt the replica; it would not repair this incident.
Question 687
After resolving the following incident, which ongoing safeguard most directly prevents recurrence? An AWS MWAA DAG has no task-level retries or SLA alerts, and a brief Glue API throttle causes a missed daily close.
- Monitor Lambda concurrent executions and event-source lag together.
- Define deployment acceptance criteria for contracts and IAM access.
- Review DAG deadlines and failure paths for each critical dependency.
- Add grain and cardinality assertions after each flattening step.
Explanation
Correct Answer
C:Review DAG deadlines and failure paths for each critical dependency. This safeguards against a recurring cause: Airflow task failure handling does not match known transient dependency behavior.
Incorrect Answers
A:That safeguard addresses another case: A Lambda ETL function exhausts concurrency during a flash sale, causing fresh events to be throttled. It is not the control for this recurring failure.
B:That safeguard addresses another case: A CI pipeline promotes an ETL artifact after syntax checks but without a representative integration job against staged data. It is not the control for this recurring failure.
D:That safeguard addresses another case: A Glue job reading nested JSON flattens arrays incorrectly and duplicates parent order totals. It is not the control for this recurring failure.
Question 688
An Athena query for CloudTrail logs shows a missing day because the log data lake partitions were never registered. Select TWO complementary measures that correctly repair and validate this failure.
- A sample output meets organizational reidentification risk requirements.
- Configure the appropriate service-principal trust and scoped invocation policy.
- Confirm CloudTrail delivery, then repair Athena catalog partitions or approved projection.
- Controlled events from the missing day are queryable after catalog correction.
- Conclude the account had no API activity because Athena returned zero rows.
Explanation
Correct Answers
C:Confirm CloudTrail delivery, then repair Athena catalog partitions or approved projection. The underlying cause is: Audit log delivery and analytics catalog partition visibility are separate requirements.
D:Controlled events from the missing day are queryable after catalog correction. This is the observable result required before accepting the correction.
Incorrect Answers
A:This would validate a different case: A tokenization pipeline uses a deterministic unkeyed hash on low-entropy postal identifiers and calls them irreversibly anonymous. It does not verify the outcome required here.
B:That corrective action is for a different case: A Step Functions state invokes a Lambda using a role that trusts EC2 instead of the Step Functions service. It does not resolve this incident.
E:Conclude the account had no API activity because Athena returned zero rows. That shortcut conflicts with the stated requirement.
Question 689
A retail clickstream uses one Kinesis partition key equal to a constant and one shard is throttled while other shards idle. Which engineering change best addresses the underlying issue?
- Minimize input fields, mask prohibited values, and apply approved data-handling and output-validation controls.
- Unpersist intermediate datasets and profile appropriate storage levels and partitions.
- Publish versioned manifest metadata containing output location, partition, checksum, and schema identity.
- Distribute records across suitable high-cardinality partition keys while preserving required per-entity ordering.
Explanation
Correct Answer
D:Distribute records across suitable high-cardinality partition keys while preserving required per-entity ordering. It directly addresses the case cause (A fixed partition key concentrates writes on one hash range.) and should be verified by: Shard write throttling falls and event order within each chosen entity remains stable.
Incorrect Answers
A:That change addresses an ETL pipeline calls a Bedrock model on full records containing account secrets merely to extract public product categories; it would not repair this incident.
B:That change addresses an EMR Spark pipeline runs near memory limits because it caches multiple large datasets and never releases them; it would not repair this incident.
C:That change addresses an ETL task finishes but its success event omits the S3 prefix and schema version needed downstream; it would not repair this incident.
Question 690
After resolving the following incident, which ongoing safeguard most directly prevents recurrence? A Firehose pipeline is expected to deliver individual records instantly, yet it buffers batches before S3 delivery.
- Track average object size alongside throughput and query planning time.
- Record end-to-end latency separately from producer acknowledgement.
- Associate build artifacts with immutable source hashes.
- Include duplicate-event and retry fixtures in integration tests.
Explanation
Correct Answer
B:Record end-to-end latency separately from producer acknowledgement. This safeguards against a recurring cause: Delivery buffering settings and destination behavior conflict with the required freshness.
Incorrect Answers
A:That safeguard addresses another case: A Lambda process writes individual small S3 JSON files for millions of events and downstream scans slow dramatically. It is not the control for this recurring failure.
C:That safeguard addresses another case: A SAM deployment packages an outdated Lambda handler because build artifacts from a previous branch were reused. It is not the control for this recurring failure.
D:That safeguard addresses another case: An EventBridge rule matches both replayed and new events and starts two identical pipelines for the same batch. It is not the control for this recurring failure.
AWS Certified Data Engineer - Associate DEA-C01 Practice Tests