Amazon AWS Certified Data Engineer - Associate DEA-C01 Practice Test 12
Question 110
An upload event triggers a Lambda handler but the same object notification is delivered more than once. Which design principle is consistent with the stated data-processing contract?
- The governing design principle is that a pipeline schedule guarantees that every downstream source record was processed correctly.
- The governing design principle is that s3 event delivery is event driven and can be duplicate or out of order; consumers must tolerate repetition.
- The governing design principle is that a CloudWatch metric label is equivalent to a successful target table data-quality validation.
- The governing design principle is that every AWS managed service uses the same consistency, retry and query-processing semantics.
Explanation
Correct Answer
B:Implement by choosing to configure S3-to-EventBridge or supported S3 notifications with event filtering and an idempotent consumer. Verify with event rule match, bucket key, version identifier, invocation trace and duplicate-event test.
Incorrect Answers
A:A pipeline schedule guarantees that every downstream source record was processed correctly. That generalization conflicts with EventBridge S3 notification event routing. Instead s3 event delivery is event driven and can be duplicate or out of order; consumers must tolerate repetition. Check event rule match, bucket key, version identifier, invocation trace and duplicate-event test.
C:A CloudWatch metric label is equivalent to a successful target table data-quality validation. That generalization conflicts with EventBridge S3 notification event routing. Instead s3 event delivery is event driven and can be duplicate or out of order; consumers must tolerate repetition. Check event rule match, bucket key, version identifier, invocation trace and duplicate-event test.
D:Every AWS managed service uses the same consistency, retry and query-processing semantics. That generalization conflicts with EventBridge S3 notification event routing. Instead s3 event delivery is event driven and can be duplicate or out of order; consumers must tolerate repetition. Check event rule match, bucket key, version identifier, invocation trace and duplicate-event test.
Question 111
An upload event triggers a Lambda handler but the same object notification is delivered more than once. An incorrect proposal is: Configure a CloudWatch alarm as the sole S3 upload event source. What issue should reviewers anticipate if the shortcut is adopted?
- The concrete failure is that the presence of an accurate job timestamp automatically created unauthorized database credentials.
- The concrete failure is that inspecting an existing Athena query plan itself deleted every production table.
- The concrete failure is that a harmless resource display-name edit caused all prior ETL jobs to lose their source schemas.
- The concrete failure is that assuming every matching object event is unique can cause duplicate downstream partitions.
Explanation
Correct Answer
D:S3 event delivery is event driven and can be duplicate or out of order; consumers must tolerate repetition. The safer implementation is to configure S3-to-EventBridge or supported S3 notifications with event filtering and an idempotent consumer.
Incorrect Answers
A:That unrelated assertion does not explain the actual EventBridge S3 notification event routing risk.
B:That unrelated assertion does not explain the actual EventBridge S3 notification event routing risk. Inspecting an existing Athena query plan itself deleted every production table.
C:That unrelated assertion does not explain the actual EventBridge S3 notification event routing risk. A harmless resource display-name edit caused all prior ETL jobs to lose their source schemas.
Question 112
An upload event triggers a Lambda handler but the same object notification is delivered more than once. The observed failure is: Assuming every matching object event is unique can cause duplicate downstream partitions. Which response repairs the underlying problem without unnecessary privilege or data loss?
- The supported recovery step is to process every bucket event without checking prefix or suffix scope.
- The supported recovery step is to configure a CloudWatch alarm as the sole S3 upload event source.
- The supported recovery step is to assume EventBridge ordering is identical to S3 key sort order.
- The supported recovery step is to add an object-version processing ledger and validate filtered event delivery and replay safety.
Explanation
Correct Answer
D:This addresses the observed EventBridge S3 notification event routing failure while preserving the required contract. Recheck event rule match, bucket key, version identifier, invocation trace and duplicate-event test.
Incorrect Answers
A:Process every bucket event without checking prefix or suffix scope. Assuming every matching object event is unique can cause duplicate downstream partitions. Instead add an object-version processing ledger and validate filtered event delivery and replay safety.
B:Configure a CloudWatch alarm as the sole S3 upload event source. Assuming every matching object event is unique can cause duplicate downstream partitions. Instead add an object-version processing ledger and validate filtered event delivery and replay safety.
C:Assume EventBridge ordering is identical to S3 key sort order. Assuming every matching object event is unique can cause duplicate downstream partitions. Instead add an object-version processing ledger and validate filtered event delivery and replay safety.
Question 113
An upload event triggers a Lambda handler but the same object notification is delivered more than once. The proposed implementation needs explicit operational validation. How should the architecture review approve and test the scoped solution?
- The reviewed plan is to configure S3-to-EventBridge or supported S3 notifications with event filtering and an idempotent consumer; validate with event rule match, bucket key, version identifier, invocation trace and duplicate-event test.
- The reviewed plan is to configure a CloudWatch alarm as the sole S3 upload event source; treat a resource name as sufficient evidence.
- The reviewed plan is to assume EventBridge ordering is identical to S3 key sort order; omit the source-to-target verification.
- The reviewed plan is to process every bucket event without checking prefix or suffix scope; do not check the failure conditions.
Explanation
Correct Answer
A:S3 event delivery is event driven and can be duplicate or out of order; consumers must tolerate repetition. The change-review requirement is satisfied only when evidence is checked: Event rule match, bucket key, version identifier, invocation trace and duplicate-event test.
Incorrect Answers
B:A resource label is not proof of EventBridge S3 notification event routing.
C:S3 event delivery is event driven and can be duplicate or out of order; consumers must tolerate repetition. The accepted action is to configure S3-to-EventBridge or supported S3 notifications with event filtering and an idempotent consumer.
D:Assuming every matching object event is unique can cause duplicate downstream partitions. Verify with event rule match, bucket key, version identifier, invocation trace and duplicate-event test.
Question 114
A burst of partner uploads overwhelms a Lambda transformation that normally handles a few files per minute. What architecture action addresses the stated source-to-target behavior?
- Increase S3 retention instead of adding a work queue to absorb processing spikes.
- Make visibility timeout shorter than normal processing and assume no duplicates.
- Buffer work in SQS with suitable visibility timeout, Lambda batch handling and dead-letter policy.
- Delete every failed message without a dead-letter record.
Explanation
Correct Answer
C:Validate with visible and not-visible queue depth, age of oldest message, receive count, DLQ body and worker errors. SQS decouples producers from processing throughput; a DLQ isolates repeatedly failing messages for examination.
Incorrect Answers
A:This does not meet SQS buffering and dead-letter queue for burst ingestion. Treating repeated poison-message retries as success keeps the queue backlogged and hides bad input.
B:Make visibility timeout shorter than normal processing and assume no duplicates. This overlooks a required service or data boundary. SQS decouples producers from processing throughput; a DLQ isolates repeatedly failing messages for examination. Inspect visible and not-visible queue depth, age of oldest message, receive count, DLQ body and worker errors.
D:Delete every failed message without a dead-letter record. This leaves the relevant data-engineering requirement unresolved. Treating repeated poison-message retries as success keeps the queue backlogged and hides bad input. The appropriate action is to buffer work in SQS with suitable visibility timeout, Lambda batch handling and dead-letter policy.
Question 115
A burst of partner uploads overwhelms a Lambda transformation that normally handles a few files per minute. What validation evidence distinguishes a correct implementation from a dashboard-only change?
- A resource ARN alone without any current data-plane observation.
- A dashboard color with no source event or data row evidence.
- A browser screenshot from another AWS account and time period.
- Visible and not-visible queue depth, age of oldest message, receive count, DLQ body and worker errors.
Explanation
Correct Answer
D:SQS decouples producers from processing throughput; a DLQ isolates repeatedly failing messages for examination. These observations directly test SQS buffering and dead-letter queue for burst ingestion.
Incorrect Answers
A:A resource ARN alone without any current data-plane observation. This is not sufficient evidence for SQS buffering and dead-letter queue for burst ingestion. Check visible and not-visible queue depth, age of oldest message, receive count, DLQ body and worker errors. SQS decouples producers from processing throughput; a DLQ isolates repeatedly failing messages for examination.
B:A dashboard color with no source event or data row evidence. This is not sufficient evidence for SQS buffering and dead-letter queue for burst ingestion. Check visible and not-visible queue depth, age of oldest message, receive count, DLQ body and worker errors. SQS decouples producers from processing throughput; a DLQ isolates repeatedly failing messages for examination.
C:A browser screenshot from another AWS account and time period. This is not sufficient evidence for SQS buffering and dead-letter queue for burst ingestion. Check visible and not-visible queue depth, age of oldest message, receive count, DLQ body and worker errors. SQS decouples producers from processing throughput; a DLQ isolates repeatedly failing messages for examination.
Question 116
A burst of partner uploads overwhelms a Lambda transformation that normally handles a few files per minute. Which design principle is consistent with the stated data-processing contract?
- SQS decouples producers from processing throughput; a DLQ isolates repeatedly failing messages for examination.
- An S3 bucket prefix guarantees exactly-once multi-service transactions without an output commit.
- A CloudWatch metric label is equivalent to a successful target table data-quality validation.
- Every AWS managed service uses the same consistency, retry and query-processing semantics.
Explanation
Correct Answer
A:Verify with visible and not-visible queue depth, age of oldest message, receive count, DLQ body and worker errors. This is the relevant technical mechanism for SQS buffering and dead-letter queue for burst ingestion.
Incorrect Answers
B:An S3 bucket prefix guarantees exactly-once multi-service transactions without an output commit. That generalization conflicts with SQS buffering and dead-letter queue for burst ingestion. Instead sQS decouples producers from processing throughput; a DLQ isolates repeatedly failing messages for examination. Check visible and not-visible queue depth, age of oldest message, receive count, DLQ body and worker errors.
C:A CloudWatch metric label is equivalent to a successful target table data-quality validation. That generalization conflicts with SQS buffering and dead-letter queue for burst ingestion. Instead sQS decouples producers from processing throughput; a DLQ isolates repeatedly failing messages for examination. Check visible and not-visible queue depth, age of oldest message, receive count, DLQ body and worker errors.
D:Every AWS managed service uses the same consistency, retry and query-processing semantics. That generalization conflicts with SQS buffering and dead-letter queue for burst ingestion. Instead sQS decouples producers from processing throughput; a DLQ isolates repeatedly failing messages for examination. Check visible and not-visible queue depth, age of oldest message, receive count, DLQ body and worker errors.
Question 117
A burst of partner uploads overwhelms a Lambda transformation that normally handles a few files per minute. An incorrect proposal is: Increase S3 retention instead of adding a work queue to absorb processing spikes. What issue should reviewers anticipate if the shortcut is adopted?
- The presence of an accurate job timestamp automatically created unauthorized database credentials.
- Inspecting an existing Athena query plan itself deleted every production table.
- Treating repeated poison-message retries as success keeps the queue backlogged and hides bad input.
- The dashboard theme independently caused an unrelated source database failure.
Explanation
Correct Answer
C:This is why the incorrect shortcut does not meet SQS buffering and dead-letter queue for burst ingestion. SQS decouples producers from processing throughput; a DLQ isolates repeatedly failing messages for examination.
Incorrect Answers
A:The presence of an accurate job timestamp automatically created unauthorized database credentials. That unrelated assertion does not explain the actual SQS buffering and dead-letter queue for burst ingestion risk. The relevant failure is that treating repeated poison-message retries as success keeps the queue backlogged and hides bad input. Check visible and not-visible queue depth, age of oldest message, receive count, DLQ body and worker errors.
B:Inspecting an existing Athena query plan itself deleted every production table. That unrelated assertion does not explain the actual SQS buffering and dead-letter queue for burst ingestion risk. The relevant failure is that treating repeated poison-message retries as success keeps the queue backlogged and hides bad input. Check visible and not-visible queue depth, age of oldest message, receive count, DLQ body and worker errors.
D:The dashboard theme independently caused an unrelated source database failure. That unrelated assertion does not explain the actual SQS buffering and dead-letter queue for burst ingestion risk. The relevant failure is that treating repeated poison-message retries as success keeps the queue backlogged and hides bad input. Check visible and not-visible queue depth, age of oldest message, receive count, DLQ body and worker errors.
Question 118
A burst of partner uploads overwhelms a Lambda transformation that normally handles a few files per minute. The observed failure is: Treating repeated poison-message retries as success keeps the queue backlogged and hides bad input. Which response repairs the underlying problem without unnecessary privilege or data loss?
- Make visibility timeout shorter than normal processing and assume no duplicates.
- Delete every failed message without a dead-letter record.
- Increase S3 retention instead of adding a work queue to absorb processing spikes.
- Set batch retry and DLQ limits, inspect failed payload and prove healthy messages continue.
Explanation
Correct Answer
D:This addresses the observed SQS buffering and dead-letter queue for burst ingestion failure while preserving the required contract. SQS decouples producers from processing throughput; a DLQ isolates repeatedly failing messages for examination.
Incorrect Answers
A:Make visibility timeout shorter than normal processing and assume no duplicates. This does not restore the required state. Treating repeated poison-message retries as success keeps the queue backlogged and hides bad input. Instead set batch retry and DLQ limits, inspect failed payload and prove healthy messages continue. In this specific operating situation, a burst of partner uploads overwhelms a Lambda transformation that normally handles a few files per minute.
B:Delete every failed message without a dead-letter record. Treating repeated poison-message retries as success keeps the queue backlogged and hides bad input. Instead set batch retry and DLQ limits, inspect failed payload and prove healthy messages continue.
C:Increase S3 retention instead of adding a work queue to absorb processing spikes. This does not restore the required state. Treating repeated poison-message retries as success keeps the queue backlogged and hides bad input. Instead set batch retry and DLQ limits, inspect failed payload and prove healthy messages continue. In this specific operating situation, a burst of partner uploads overwhelms a Lambda transformation that normally handles a few files per minute.
Question 119
A malformed queue message is retried until the normal processing backlog starves. Which AWS design or configuration BEST satisfies the stated processing requirement?
- In this operational case, make visibility timeout shorter than normal processing and assume no duplicates.
- In this operational case, buffer work in SQS with suitable visibility timeout, Lambda batch handling and dead-letter policy.
- In this operational case, delete every failed message without a dead-letter record.
- In this operational case, increase S3 retention instead of adding a work queue to absorb processing spikes.
Explanation
Correct Answer
B:Validate with visible and not-visible queue depth, age of oldest message, receive count, DLQ body and worker errors. This directly addresses SQS buffering and dead-letter queue for burst ingestion.
Incorrect Answers
A:Make visibility timeout shorter than normal processing and assume no duplicates. This overlooks a required service or data boundary. SQS decouples producers from processing throughput; a DLQ isolates repeatedly failing messages for examination. Inspect visible and not-visible queue depth, age of oldest message, receive count, DLQ body and worker errors.
C:Delete every failed message without a dead-letter record. This leaves the relevant data-engineering requirement unresolved. Treating repeated poison-message retries as success keeps the queue backlogged and hides bad input. The appropriate action is to buffer work in SQS with suitable visibility timeout, Lambda batch handling and dead-letter policy.
D:This does not meet SQS buffering and dead-letter queue for burst ingestion. The supported design is to buffer work in SQS with suitable visibility timeout, Lambda batch handling and dead-letter policy.
Question 120
A malformed queue message is retried until the normal processing backlog starves. Which evidence would BEST verify that the intended pipeline outcome occurred?
- The relevant validation evidence is a successful ping to an unrelated service that did not process the data.
- The relevant validation evidence is visible and not-visible queue depth, age of oldest message, receive count, DLQ body and worker errors.
- The relevant validation evidence is a resource ARN alone without any current data-plane observation.
- The relevant validation evidence is a dashboard color with no source event or data row evidence.
Explanation
Correct Answer
B:SQS decouples producers from processing throughput; a DLQ isolates repeatedly failing messages for examination. Visible and not-visible queue depth, age of oldest message, receive count, DLQ body and worker errors.
Incorrect Answers
A:A successful ping to an unrelated service that did not process the data. This is not sufficient evidence for SQS buffering and dead-letter queue for burst ingestion. Check visible and not-visible queue depth, age of oldest message, receive count, DLQ body and worker errors. SQS decouples producers from processing throughput; a DLQ isolates repeatedly failing messages for examination.
C:A resource ARN alone without any current data-plane observation. This is not sufficient evidence for SQS buffering and dead-letter queue for burst ingestion. Check visible and not-visible queue depth, age of oldest message, receive count, DLQ body and worker errors. SQS decouples producers from processing throughput; a DLQ isolates repeatedly failing messages for examination.
D:A dashboard color with no source event or data row evidence. This is not sufficient evidence for SQS buffering and dead-letter queue for burst ingestion. Check visible and not-visible queue depth, age of oldest message, receive count, DLQ body and worker errors. SQS decouples producers from processing throughput; a DLQ isolates repeatedly failing messages for examination.