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 950
An S3-based table changes from hourly to daily partitions while old writers still publish hourly paths, giving inconsistent query results. Which engineering change best addresses the underlying issue?
- Migrate writers, metadata, and readers through a dual-read/reconciliation plan.
- Use a supported strongly consistent base-table or local-index read design where necessary.
- Align supported shared catalog integration or explicitly publish new partition metadata.
- Restrict crawler targets, table prefixes and schema-change behavior to approved locations.
Explanation
Correct Answer
A:Migrate writers, metadata, and readers through a dual-read/reconciliation plan. It directly addresses the case cause (Partition layout evolution was deployed without coordinating producers and catalog readers.) and should be verified by: A representative query returns both historical and new data exactly once.
Incorrect Answers
B:That change addresses a DynamoDB application requires strongly consistent reads immediately after a successful critical write but queries a global secondary index; it would not repair this incident.
C:That change addresses a Hive metastore-based EMR Spark job writes a new partition but Athena never sees it through Glue Data Catalog; it would not repair this incident.
D:That change addresses a Glue crawler crawls the entire lake for every hourly feed and adds unexpected tables from temporary staging prefixes; it would not repair this incident.
Question 951
A retail clickstream uses one Kinesis partition key equal to a constant and one shard is throttled while other shards idle. Which technical dependency most directly explains this behavior?
- The pipeline assumes every optional path exists for every row.
- Retries use non-idempotent output identity with uncertain prior completion.
- A fixed partition key concentrates writes on one hash range.
- Retry logic does not isolate staging and atomic commit boundaries.
Explanation
Correct Answer
C:A fixed partition key concentrates writes on one hash range. The corresponding fix is to distribute records across suitable high-cardinality partition keys while preserving required per-entity ordering.
Incorrect Answers
A:This diagnosis addresses another AWS case: An API payload includes optional addresses but a transformation fails when a nullable nested object is absent. The dependency here is different.
B:This diagnosis addresses another AWS case: An orchestrator invokes a Lambda that writes to S3 then times out; the retry writes a second output under a new random key. The dependency here is different.
D:This diagnosis addresses another AWS case: A Glue workflow reruns yesterday's partition after a partially failed daily job but overwrites already-approved historical results. The dependency here is different.
Question 952
A Lake Formation-enabled S3 table is visible in Glue Data Catalog, but Athena SELECT is denied to the analyst role. Which engineering change best addresses the underlying issue?
- Use approved Macie sensitive-data discovery and validated data classifications with access review.
- Grant scoped Lake Formation SELECT and required catalog permissions to the authorized principal.
- Store and rotate credentials in Secrets Manager with scoped runtime retrieval and redacted logs.
- Enable reviewed CloudTrail data events for the required S3 buckets or prefixes.
Explanation
Correct Answer
B:Grant scoped Lake Formation SELECT and required catalog permissions to the authorized principal. It directly addresses the case cause (Metadata discovery does not imply Lake Formation table data permission.) and should be verified by: The analyst queries permitted columns while sensitive excluded fields remain inaccessible.
Incorrect Answers
A:That change addresses a data privacy analyst needs to identify PII in unknown S3 datasets but assumes object names reveal sensitive content; it would not repair this incident.
C:That change addresses a pipeline sends database credentials in plaintext environment variables and writes them to CloudWatch on failure; it would not repair this incident.
D:That change addresses an S3 data-access investigation searches CloudTrail for object reads but only management events were enabled; it would not repair this incident.
Question 953
A Glue job begins consuming twice its normal DPU budget after a transformation adds a repeated cross join. Which engineering change best addresses the underlying issue?
- Express ordered execution or an appropriate DAG with artifact-ready checks.
- Add explicit row-count, schema, and quality validation before the publish step.
- Profile physical plans and remove unintended cross joins or use reviewed predicates.
- Run a null/uniqueness check in Glue or SQL and quarantine failing rows or batches.
Explanation
Correct Answer
C:Profile physical plans and remove unintended cross joins or use reviewed predicates. It directly addresses the case cause (Changed query logic multiplies intermediate data and compute cost.) and should be verified by: Correct row counts and bounded DPU-hours return in a repeatable fixture.
Incorrect Answers
A:That change addresses an EMR workflow submits five jobs simultaneously but two require the first job's generated HDFS staging output; it would not repair this incident.
B:That change addresses a Glue ETL job completes with warnings but the orchestrator assumes success despite a downstream quality check failing; it would not repair this incident.
D: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.
Question 954
A Redshift reporting pipeline accumulates duplicate business keys after retries because it appends without reconciling current versions. Select THREE complementary measures that correctly repair and validate, and prevent recurrence of this failure.
- Replaying the same batch leaves one intended current version per key.
- Yesterday's test row becomes queryable without a broad table recreation.
- Test duplicate and late-arriving records in warehouse loads.
- Assume COPY automatically enforces a uniqueness constraint on every key.
- Review supported replication/delete-marker configuration and establish reconciliation monitoring.
- Use staging with a reviewed MERGE or idempotent replace pattern keyed by business identity.
Explanation
Correct Answers
A:Replaying the same batch leaves one intended current version per key. This is the observable result required before accepting the correction.
C:Test duplicate and late-arriving records in warehouse loads. This protects against the following risk: The warehouse load lacks deterministic upsert/merge semantics.
F:Use staging with a reviewed MERGE or idempotent replace pattern keyed by business identity. The underlying cause is: The warehouse load lacks deterministic upsert/merge semantics.
Incorrect Answers
B:This would validate a different case: An Athena query of yesterday's S3 partition returns zero rows because its table metadata lacks that partition. It does not verify the outcome required here.
D:Assume COPY automatically enforces a uniqueness constraint on every key. That shortcut conflicts with the stated requirement.
E:That corrective action is for a different case: An S3 replication configuration excludes delete markers, but a team assumes target data will reflect source deletes instantly. It does not resolve this incident.
Question 955
A Glue job uses a fixed worker count at peak and wastes compute on tiny nightly delta batches. Which engineering change best addresses the underlying issue?
- Configure validated subscriptions, policies and controlled test notifications.
- Use an appropriate hashed lookup structure while preserving deterministic output behavior.
- Measure runtime and costs by job size and configure eligible autoscaling or differentiated job profiles.
- Follow documented API pagination and persist progress in resumable checkpoints.
Explanation
Correct Answer
C:Measure runtime and costs by job size and configure eligible autoscaling or differentiated job profiles. It directly addresses the case cause (Compute sizing is not matched to variable input size and workload characteristics.) and should be verified by: Small batches finish at lower cost without violating latency objectives.
Incorrect Answers
A: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.
B:That change addresses a large ETL data structure uses a list for repeated membership checks and CPU use grows unexpectedly; 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 956
An Athena table uses daily partitions on a timestamp with millions of near-empty partition folders. Select TWO complementary measures that correctly repair and validate this failure.
- Average scanned bytes and query planning time improve without data loss.
- Expired sessions are denied immediately even if the physical item persists briefly.
- Qualify or configure the intended catalog/database and verify metadata references.
- Create a separate partition for every individual event timestamp.
- Reassess partition keys/granularity and apply efficient columnar file layout.
Explanation
Correct Answers
A:Average scanned bytes and query planning time improve without data loss. This is the observable result required before accepting the correction.
E:Reassess partition keys/granularity and apply efficient columnar file layout. The underlying cause is: Partition granularity is too fine for data volume and query predicates.
Incorrect Answers
B:This would validate a different case: A DynamoDB table contains session records with expired timestamps but items remain visible immediately after expiry. It does not verify the outcome required here.
C:That corrective action is for a different case: Two Athena workgroups query identically named tables but one references a different data catalog and gets old records. It does not resolve this incident.
D:Create a separate partition for every individual event timestamp. That shortcut conflicts with the stated requirement.
Question 957
After resolving the following incident, which ongoing safeguard most directly prevents recurrence? An application seeks low-latency semantic recommendations but indexes product names as plain text without generated embeddings.
- Track distribution skew after major tenant growth.
- Document source-target deletion expectations and lag metrics.
- Monitor embedding version alignment and evaluation quality.
- Audit catalog lifecycle on organizational changes.
Explanation
Correct Answer
C:Monitor embedding version alignment and evaluation quality. This safeguards against a recurring cause: Lexical text indexing does not implement the intended vector similarity retrieval.
Incorrect Answers
A:That safeguard addresses another case: A Redshift table has highly skewed account IDs as a distribution key and one compute slice processes most rows. It is not the control for this recurring failure.
B: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 SageMaker Catalog project references a dataset whose owner changed but permissions and business definitions still point to the former team. It is not the control for this recurring failure.
Question 958
After resolving the following incident, which ongoing safeguard most directly prevents recurrence? A Redshift reporting pipeline accumulates duplicate business keys after retries because it appends without reconciling current versions.
- Test duplicate and late-arriving records in warehouse loads.
- Test version rollback and expiration dates before enabling cleanup.
- Enforce required tag vocabulary in dataset onboarding.
- Track catalog and snapshot IDs across pipeline steps.
Explanation
Correct Answer
A:Test duplicate and late-arriving records in warehouse loads. This safeguards against a recurring cause: The warehouse load lacks deterministic upsert/merge semantics.
Incorrect Answers
B:That safeguard addresses another case: An S3 lifecycle rule expires noncurrent object versions immediately, preventing recovery from accidental overwrites. It is not the control for this recurring failure.
C:That safeguard addresses another case: A data catalog stores PII labels only as free-text comments, so new tables bypass a tagging-based access process. It is not the control for this recurring failure.
D:That safeguard addresses another case: A dataset uses Iceberg but Spark and Athena query different catalogs and show conflicting table snapshots. It is not the control for this recurring failure.
Question 959
After resolving the following incident, which ongoing safeguard most directly prevents recurrence? A Redshift UNLOAD writes reporting data to an S3 bucket in another account but fails with access denied.
- Track metadata version and compatible migration steps per release.
- Revalidate role, bucket and key permissions after account boundary changes.
- Test duplicate and late-arriving records in warehouse loads.
- Define backward/forward compatibility rules before source rollout.
Explanation
Correct Answer
B:Revalidate role, bucket and key permissions after account boundary changes. This safeguards against a recurring cause: The UNLOAD role and destination policy do not authorize the intended cross-account write.
Incorrect Answers
A:That safeguard addresses another case: Two developers independently edit Glue Data Catalog schema types during release, and a job fails after the last writer wins. It is not the control for this recurring failure.
C:That safeguard addresses another case: A Redshift reporting pipeline accumulates duplicate business keys after retries because it appends without reconciling current versions. It is not the control for this recurring failure.
D:That safeguard addresses another case: A lake dataset adds an optional JSON field and an older consumer fails because it expects an exact fixed set of keys. It is not the control for this recurring failure.
Question 960
A team applies a reviewed fix for this situation: A processing job ingests gzipped files but its connector treats their contents as uncompressed text and creates corrupt rows. Which observed outcome would most convincingly validate the fix?
- A simulated transient failure recovers and persistent failures produce timely alerts.
- A controlled JDBC connection from the Glue execution context succeeds.
- A real on-call endpoint receives a test failure with actionable context.
- Decompressed samples match checksums and expected record counts.
Explanation
Correct Answer
D:Decompressed samples match checksums and expected record counts. This verifies the result of configure supported decompression and validate input format before parsing.
Incorrect Answers
A:This would verify another situation: An AWS MWAA DAG has no task-level retries or SLA alerts, and a brief Glue API throttle causes a missed daily close. It does not validate the current case.
B:This would verify another situation: A Glue connection to a source RDS database times out, although the JDBC credentials are valid. It does not validate the current case.
C:This would verify another situation: A multi-account data pipeline sends operational alerts through an SNS topic that no engineer subscribes to. It does not validate the current case.
AWS Certified Data Engineer - Associate DEA-C01 Practice Tests