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 420
A Glue transform joins events to reference data refreshed weekly, but old events are silently reclassified on every rerun. Which engineering change best addresses the underlying issue?
- Right-size supported Lambda ephemeral storage or stream/process in bounded chunks.
- Align source transaction-log retention, DMS checkpoints, and CDC task health with the recovery objective.
- Join by intended as-of validity and persist versioned reference mappings.
- Tune consumption, heartbeat/poll behavior, batch sizes and idempotent processing to the workload.
Explanation
Correct Answer
C:Join by intended as-of validity and persist versioned reference mappings. It directly addresses the case cause (Reference data lacks effective-date or historical snapshot semantics.) and should be verified by: A replayed historical event receives its original applicable classification.
Incorrect Answers
A:That change addresses a Lambda ETL process writes temporary files larger than its configured /tmp capacity and receives storage errors; it would not repair this incident.
B:That change addresses a DMS CDC task finishes a full-load phase but stops capturing source table changes when the source transaction log expires; it would not repair this incident.
D:That change addresses an MSK consumer group repeatedly rebalances during long processing, causing duplicate deliveries; it would not repair this incident.
Question 421
An S3 table is tagged `classification=restricted`, but its Lake Formation LF-Tag grant allows a broad organizational unit with no business need. Which engineering change best addresses the underlying issue?
- Correlate CloudTrail and applicable KMS/service logs with job execution context.
- Inventory staging artifacts and enforce approved secure cleanup/retention and access.
- Narrow LF-Tag permissions to reviewed principals and classify data assets consistently.
- Scope shared views, roles and periodic reauthorization with a documented owner.
Explanation
Correct Answer
C:Narrow LF-Tag permissions to reviewed principals and classify data assets consistently. It directly addresses the case cause (Attribute-based permissions have a policy scope broader than the approved audience.) and should be verified by: An approved data steward queries the table while a nonmember receives denial.
Incorrect Answers
A:That change addresses an ETL role invokes KMS Decrypt repeatedly, but the pipeline's incident review examines only application logs without recording AWS API actor identity; it would not repair this incident.
B:That change addresses a lake-to-warehouse pipeline removes raw PII from visible tables but keeps an untracked temporary S3 staging prefix indefinitely; it would not repair this incident.
D: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.
Question 422
After resolving the following incident, which ongoing safeguard most directly prevents recurrence? A Glue job joins a tiny lookup table to billions of rows and performs a full distributed shuffle.
- Test Map concurrency under real vendor budgets before promotion.
- Audit ownership and naming of consumer checkpoints.
- Use transformation-contract tests before promoting Lambda versions.
- Record dimension-size thresholds and explain plans for joins.
Explanation
Correct Answer
D:Record dimension-size thresholds and explain plans for joins. This safeguards against a recurring cause: The join strategy ignores a safe broadcastable small dimension.
Incorrect Answers
A:That safeguard addresses another case: A pipeline launches thousands of concurrent Step Functions Map tasks and saturates a small partner API. It is not the control for this recurring failure.
B:That safeguard addresses another case: Two Kinesis consumers must independently recover after a deployment, but one team reuses the other's checkpoint store. It is not the control for this recurring failure.
C:That safeguard addresses another case: A Firehose transformation Lambda returns malformed record status envelopes and some messages enter an error prefix. It is not the control for this recurring failure.
Question 423
After resolving the following incident, which ongoing safeguard most directly prevents recurrence? A DynamoDB application requires strongly consistent reads immediately after a successful critical write but queries a global secondary index.
- Document consistency needs separately for each access pattern.
- Include KMS access in data-load integration tests.
- Document source-target deletion expectations and lag metrics.
- Review evolution compatibility and snapshot rollback requirements.
Explanation
Correct Answer
A:Document consistency needs separately for each access pattern. This safeguards against a recurring cause: The chosen read path cannot provide strong consistency on the GSI.
Incorrect Answers
B:That safeguard addresses another case: A Redshift COPY command reads encrypted S3 files but the IAM role lacks decryption permission for the customer KMS key. 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.
D:That safeguard addresses another case: A team adds a nonnullable required field to an Iceberg table but old rows have no value and downstream reads fail. It is not the control for this recurring failure.
Question 424
A Lake Formation-enabled S3 table is visible in Glue Data Catalog, but Athena SELECT is denied to the analyst role. Select THREE complementary measures that correctly repair and validate, and prevent recurrence of this failure.
- Grant scoped Lake Formation SELECT and required catalog permissions to the authorized principal.
- Disable Lake Formation governance so every employee can query all rows.
- Configure the appropriate service-principal trust and scoped invocation policy.
- An ordinary BI user sees only the approved masked representation.
- Test catalog visibility and data read permissions separately.
- The analyst queries permitted columns while sensitive excluded fields remain inaccessible.
Explanation
Correct Answers
A:Grant scoped Lake Formation SELECT and required catalog permissions to the authorized principal. The underlying cause is: Metadata discovery does not imply Lake Formation table data permission.
E:Test catalog visibility and data read permissions separately. This protects against the following risk: Metadata discovery does not imply Lake Formation table data permission.
F:The analyst queries permitted columns while sensitive excluded fields remain inaccessible. This is the observable result required before accepting the correction.
Incorrect Answers
B:Disable Lake Formation governance so every employee can query all rows. That shortcut conflicts with the stated requirement.
C: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.
D:This would validate a different case: A Redshift view exposes unmasked customer SSNs to a general BI role despite a requirement for partial disclosure. It does not verify the outcome required here.
Question 425
An API payload includes optional addresses but a transformation fails when a nullable nested object is absent. Which engineering change best addresses the underlying issue?
- Use nullable-aware extraction and document sensible default or reject handling per field.
- Create a supported Firehose dynamic-partitioning delivery stream with well-chosen keys and S3 prefixes.
- Configure validated subscriptions, policies and controlled test notifications.
- Check Glue connection subnet, ENIs, VPC routing, DNS, and the source's inbound rule.
Explanation
Correct Answer
A:Use nullable-aware extraction and document sensible default or reject handling per field. It directly addresses the case cause (The pipeline assumes every optional path exists for every row.) and should be verified by: Fixtures with present, null, and missing fields receive expected values or rejects.
Incorrect Answers
B:That change addresses a Firehose stream delivering transactions to S3 mixes every customer into the same prefix, making Athena queries scan all tenants; it would not repair this incident.
C:That change addresses a multi-account data pipeline sends operational alerts through an SNS topic that no engineer subscribes to; it would not repair this incident.
D:That change addresses a Glue connection to a source RDS database times out, although the JDBC credentials are valid; it would not repair this incident.
Question 426
A team applies a reviewed fix for this situation: A central CloudWatch Logs group for Glue jobs retains all raw customer payloads in debug messages across many teams. Which observed outcome would most convincingly validate the fix?
- A controlled state machine execution invokes only its intended function.
- The authorized destination role reads replicas and unapproved accounts remain denied.
- The job decrypts authorized data but receives denial on a neighboring client's key.
- A deliberate invalid record yields actionable error metadata without raw PII.
Explanation
Correct Answer
D:A deliberate invalid record yields actionable error metadata without raw PII. This verifies the result of redact values at source and restrict log retention and access by least privilege.
Incorrect Answers
A:This would verify another situation: A Step Functions state invokes a Lambda using a role that trusts EC2 instead of the Step Functions service. It does not validate the current case.
B:This would verify another situation: A data lake copies SSE-KMS objects across AWS accounts but the destination principal cannot decrypt the replica. It does not validate the current case.
C:This would verify another situation: A Glue data job decrypts source objects using a wildcard KMS permission spanning unrelated client keys. It does not validate the current case.
Question 427
A monthly data load uses Lambda to copy hundreds of gigabytes in a single invocation and repeatedly times out. Which engineering change best addresses the underlying issue?
- Inspect consumer access-denied logs and restore narrowly scoped Kinesis permissions.
- Move bulk transformation to a suitable managed batch/distributed service and orchestrate it.
- Run a null/uniqueness check in Glue or SQL and quarantine failing rows or batches.
- Normalize event time and use the required explicit UTC or business timezone boundaries.
Explanation
Correct Answer
B:Move bulk transformation to a suitable managed batch/distributed service and orchestrate it. It directly addresses the case cause (The data workload exceeds Lambda's practical bounded execution model.) and should be verified by: A maximum-size sample completes with a checkpointed durable output.
Incorrect Answers
A:That change addresses a Kinesis stream is receiving writes but downstream analytics remain empty after the consumer IAM role lost read permission; it would not repair this incident.
C: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 a daily sales pivot groups event timestamps by the viewer's local date and differs from the regulatory UTC day; it would not repair this incident.
Question 428
A team applies a reviewed fix for this situation: A table claims a `region` partition key but the written S3 paths use `geography=...`, so Athena pruning fails. Which observed outcome would most convincingly validate the fix?
- Network redistribution and join latency improve with unchanged outputs.
- Region-filtered queries prune to the expected physical prefixes.
- A multi-line order yields correct revenue and item counts in fixture reports.
- Replaying the same batch leaves one intended current version per key.
Explanation
Correct Answer
B:Region-filtered queries prune to the expected physical prefixes. This verifies the result of align approved partition key definitions and S3 path generation or repair registered metadata.
Incorrect Answers
A:This would verify another situation: A small dimension table joins huge Redshift facts, but an unnecessarily EVEN distribution causes repeated data transfer. It does not validate the current case.
C:This would verify another situation: A Redshift star schema mixes order-line and order-header facts in the same table and reports double-count revenue. It does not validate the current case.
D:This would verify another situation: A Redshift reporting pipeline accumulates duplicate business keys after retries because it appends without reconciling current versions. It does not validate the current case.
Question 429
An engineer adds a new processing step to an AWS Glue workflow but never connects its trigger to the existing dependency chain. Which engineering change best addresses the underlying issue?
- Inspect Spark stage metrics and split/salt hotspots or change skewed join strategy.
- Add and validate the correct conditional trigger path from the predecessor job.
- Examine iterator age, shard utilization, downstream latency and consumer parallelism.
- Check expected row counts against source manifest and tolerances before release.
Explanation
Correct Answer
B:Add and validate the correct conditional trigger path from the predecessor job. It directly addresses the case cause (The new job is present but unreachable from the workflow's actual trigger graph.) and should be verified by: A controlled workflow run invokes the added job exactly in the expected order.
Incorrect Answers
A:That change addresses an ETL task in Glue times out only when a small fraction of keys dominate the daily partition; it would not repair this incident.
C:That change addresses a Kinesis consumer reports healthy CPU yet its IteratorAge grows for hours during normal traffic; it would not repair this incident.
D:That change addresses a feed arrives with 30% fewer rows than normal, but a transformation succeeds and marks the data product complete; it would not repair this incident.
Question 430
A nightly lake job publishes versioned S3 snapshots but deletes all old snapshots before the replacement is fully validated. Select THREE complementary measures that correctly repair and validate, and prevent recurrence of this failure.
- An injected failed publish leaves the last approved snapshot accessible.
- Require verified replacement and retention checks before garbage collection.
- Expire all versions as soon as a new upload begins.
- A newly onboarded sensitive table receives the intended governed classification.
- Use staged validation and controlled retention/cleanup of replaced snapshots.
- Move the transactional system of record to a suitable relational operational database and replicate analysis data to Redshift.
Explanation
Correct Answers
A:An injected failed publish leaves the last approved snapshot accessible. This is the observable result required before accepting the correction.
B:Require verified replacement and retention checks before garbage collection. This protects against the following risk: The publish process removes its rollback point prematurely.
E:Use staged validation and controlled retention/cleanup of replaced snapshots. The underlying cause is: The publish process removes its rollback point prematurely.
Incorrect Answers
C:Expire all versions as soon as a new upload begins. That shortcut conflicts with the stated requirement.
D:This would validate a different case: A data catalog stores PII labels only as free-text comments, so new tables bypass a tagging-based access process. It does not verify the outcome required here.
F:That corrective action is for a different case: A Redshift analytics warehouse holds transactional checkout rows that require thousands of short atomic row updates per second. It does not resolve this incident.
AWS Certified Data Engineer - Associate DEA-C01 Practice Tests