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 870
A Redshift table has highly skewed account IDs as a distribution key and one compute slice processes most rows. Select THREE complementary measures that correctly repair and validate, and prevent recurrence of this failure.
- Add more slices while preserving a single skewed placement key.
- Per-slice row distribution and runtime meet expected thresholds.
- Representative spatial lookups return correctly without full-table scans.
- Track distribution skew after major tenant growth.
- Move the transactional system of record to a suitable relational operational database and replicate analysis data to Redshift.
- Review AUTO or more distributed keys and measure skew and join plans.
Explanation
Correct Answers
B:Per-slice row distribution and runtime meet expected thresholds. This is the observable result required before accepting the correction.
D:Track distribution skew after major tenant growth. This protects against the following risk: Join/distribution key cardinality is unsuitable for balanced data movement.
F:Review AUTO or more distributed keys and measure skew and join plans. The underlying cause is: Join/distribution key cardinality is unsuitable for balanced data movement.
Incorrect Answers
A:Add more slices while preserving a single skewed placement key. That shortcut conflicts with the stated requirement.
C:This would validate a different case: A geospatial data catalog is placed in DynamoDB with no defined access key and engineers scan the entire table for each location. It does not verify the outcome required here.
E: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.
Question 871
After resolving the following incident, which ongoing safeguard most directly prevents recurrence? A Glue data job decrypts source objects using a wildcard KMS permission spanning unrelated client keys.
- Add cross-account acceptance and resource-link tests to onboarding.
- Audit key grants and actual decrypt events after role changes.
- Maintain and test account/Region audit coverage inventories.
- Reconcile datashare permissions against the sharing agreement each release.
Explanation
Correct Answer
B:Audit key grants and actual decrypt events after role changes. This safeguards against a recurring cause: Cryptographic permissions exceed the data processing task's required keys.
Incorrect Answers
A:That safeguard addresses another case: A cross-account Lake Formation share is granted but the consumer account has not accepted its RAM invitation where required. It is not the control for this recurring failure.
C:That safeguard addresses another case: A CloudTrail Lake query lists IAM role changes but its event filter omits the Regions holding the relevant data pipelines. It is not the control for this recurring failure.
D:That safeguard addresses another case: A Redshift datashare exposes more tables than a partner is contractually allowed to query. It is not the control for this recurring failure.
Question 872
After resolving the following incident, which ongoing safeguard most directly prevents recurrence? A daily batch extraction reads only the first page of a vendor REST API and silently loses subsequent records.
- Profile algorithmic complexity for hot-path data structures.
- Schema-check workflow handoffs and reject incomplete manifests.
- Test large responses, page limits, and interrupted cursors in CI.
- Verify file magic bytes and compression metadata on source arrivals.
Explanation
Correct Answer
C:Test large responses, page limits, and interrupted cursors in CI. This safeguards against a recurring cause: The ingestion client ignores pagination tokens or cursor continuation.
Incorrect Answers
A:That safeguard addresses another case: A large ETL data structure uses a list for repeated membership checks and CPU use grows unexpectedly. It is not the control for this recurring failure.
B:That safeguard addresses another case: An ETL task finishes but its success event omits the S3 prefix and schema version needed downstream. It is not the control for this recurring failure.
D:That safeguard addresses another case: A processing job ingests gzipped files but its connector treats their contents as uncompressed text and creates corrupt rows. It is not the control for this recurring failure.
Question 873
A daily sensor batch is duplicated after retry, causing every aggregate event count to double. Which engineering change best addresses the underlying issue?
- Use supported wait-for-completion integration or a correctly bounded job-status polling loop.
- Configure supported persistent log delivery to a controlled durable location.
- Add and validate the correct conditional trigger path from the predecessor job.
- Deduplicate on a documented source event key and verify idempotent load state.
Explanation
Correct Answer
D:Deduplicate on a documented source event key and verify idempotent load state. It directly addresses the case cause (The pipeline lacks stable event-level uniqueness validation.) and should be verified by: A repeated batch does not change the accepted distinct event count.
Incorrect Answers
A:That change addresses a Step Functions data pipeline invokes Glue using a request/response integration and immediately launches Athena against unfinished output; it would not repair this incident.
B:That change addresses an EMR job intermittently fails due to capacity interruptions but its logs are stored only on the terminated instance; it would not repair this incident.
C:That change addresses an engineer adds a new processing step to an AWS Glue workflow but never connects its trigger to the existing dependency chain; it would not repair this incident.
Question 874
After resolving the following incident, which ongoing safeguard most directly prevents recurrence? A crawler changes a decimal sales column to string after encountering a nonnumeric banner row in one export.
- Include KMS access in data-load integration tests.
- Review hot/cold access patterns and storage-tier choices.
- Run type-conformance checks before crawlers refresh production metadata.
- Track model ID, vector dimension and index build provenance.
Explanation
Correct Answer
C:Run type-conformance checks before crawlers refresh production metadata. This safeguards against a recurring cause: Unvalidated mixed-format source rows contaminated schema inference.
Incorrect Answers
A: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.
B:That safeguard addresses another case: A customer expects fast key-value reads over frequently accessed session state yet stores every session in a multi-megabyte compressed S3 archive. It is not the control for this recurring failure.
D:That safeguard addresses another case: A vector retrieval index stores embeddings from two incompatible model versions in one dimension-dependent collection. It is not the control for this recurring failure.
Question 875
A team applies a reviewed fix for this situation: A Redshift data analyst has a role granting broad schema CREATE and DROP despite requiring only SELECT on a few views. Which observed outcome would most convincingly validate the fix?
- Controlled events from the missing day are queryable after catalog correction.
- The analyst queries authorized views but cannot modify their source tables.
- A controlled secret rotation works and logs contain no secret values.
- The intended job reads only its approved data prefix while unrelated access remains denied.
Explanation
Correct Answer
B:The analyst queries authorized views but cannot modify their source tables. This verifies the result of define and grant a read-only database role on approved schemas and views.
Incorrect Answers
A:This would verify another situation: An Athena query for CloudTrail logs shows a missing day because the log data lake partitions were never registered. It does not validate the current case.
C:This would verify another situation: A pipeline sends database credentials in plaintext environment variables and writes them to CloudWatch on failure. It does not validate the current case.
D:This would verify another situation: A Glue job in a private VPC cannot read a governed S3 source after the executor role loses permission, although its worker network is healthy. It does not validate the current case.
Question 876
An Aurora PostgreSQL vector workload uses a vector index tuned for approximate nearest neighbors without checking recall for a new embedding model. Which technical dependency most directly explains this behavior?
- The UNLOAD role and destination policy do not authorize the intended cross-account write.
- Table metadata maintenance does not match commit frequency and retention needs.
- Recovery snapshot and change-stream offsets do not represent a consistent recovery point.
- Index configuration and vector characteristics affect speed/recall tradeoffs.
Explanation
Correct Answer
D:Index configuration and vector characteristics affect speed/recall tradeoffs. The corresponding fix is to benchmark supported HNSW or other index choices against ground-truth neighbors and query latency.
Incorrect Answers
A:This diagnosis addresses another AWS case: A Redshift UNLOAD writes reporting data to an S3 bucket in another account but fails with access denied. The dependency here is different.
B:This diagnosis addresses another AWS case: An Iceberg table's snapshot history grows as frequent small commits accumulate and query planning becomes slow. The dependency here is different.
C:This diagnosis addresses another AWS case: A cross-region disaster recovery table is restored from an old snapshot, and CDC replication starts from an incompatible new checkpoint. The dependency here is different.
Question 877
A scheduled Glue workflow triggers two jobs concurrently though the second requires the first output's partition. Select THREE complementary measures that correctly repair and validate, and prevent recurrence of this failure.
- Add an explicit predecessor-success trigger or workflow state dependency.
- Visualize and test dependency DAGs on new schedule changes.
- The second job starts only after the first has committed the required partition.
- Use supported batching, buffering, compaction, or columnar write paths appropriate to latency.
- A failed release can restore the prior script and reproduce its output.
- Rely on alphabetical job names as a scheduler ordering mechanism.
Explanation
Correct Answers
A:Add an explicit predecessor-success trigger or workflow state dependency. The underlying cause is: Job ordering fails to express the producer-consumer dependency.
B:Visualize and test dependency DAGs on new schedule changes. This protects against the following risk: Job ordering fails to express the producer-consumer dependency.
C:The second job starts only after the first has committed the required partition. This is the observable result required before accepting the correction.
Incorrect Answers
D:That corrective action is for a different case: A Lambda process writes individual small S3 JSON files for millions of events and downstream scans slow dramatically. It does not resolve this incident.
E:This would validate a different case: A data engineering team manually changes Glue scripts on S3 without source control or a rollback identifier. It does not verify the outcome required here.
F:Rely on alphabetical job names as a scheduler ordering mechanism. That shortcut conflicts with the stated requirement.
Question 878
An Athena SQL query sums decimal prices stored as strings and uses lexicographic ordering on text. Select TWO complementary measures that correctly repair and validate this failure.
- Sort price strings alphabetically to derive a top-selling revenue list.
- The report matches known numeric test totals and identifies malformed values.
- Convert to validated decimal types upstream or with explicit safe casts before aggregation.
- A burst drains within the recovery SLA without widespread throttling.
- Reconcile accepted, filtered and quarantined records with explicit balance equations.
Explanation
Correct Answers
B:The report matches known numeric test totals and identifies malformed values. This is the observable result required before accepting the correction.
C:Convert to validated decimal types upstream or with explicit safe casts before aggregation. The underlying cause is: An ingestion schema preserves numeric measures with the wrong SQL type.
Incorrect Answers
A:Sort price strings alphabetically to derive a top-selling revenue list. That shortcut conflicts with the stated requirement.
D:This would validate a different case: An orchestrated data processing task receives tens of thousands of S3 events, causing Lambda reserved concurrency exhaustion. It does not verify the outcome required here.
E:That corrective action is for a different case: A data quality gate compares raw and target record totals without accounting for intentional filter exclusions, falsely failing clean batches. It does not resolve this incident.
Question 879
After resolving the following incident, which ongoing safeguard most directly prevents recurrence? A partner uploads a CSV over SFTP to Transfer Family but a load starts before the file finishes writing.
- Record source revision and artifact hash on every job run.
- Version the ingestion schema and alert on incompatible type drift.
- Require delivery manifests and replay-safe keys for partner batches.
- Associate build artifacts with immutable source hashes.
Explanation
Correct Answer
C:Require delivery manifests and replay-safe keys for partner batches. This safeguards against a recurring cause: The consuming workflow lacks a reliable transfer-completion boundary.
Incorrect Answers
A:That safeguard addresses another case: A data engineering team manually changes Glue scripts on S3 without source control or a rollback identifier. It is not the control for this recurring failure.
B:That safeguard addresses another case: A Glue PySpark job fails when an upstream field changes from integer to string in some JSON documents. It is not the control for this recurring failure.
D: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.
Question 880
A team applies a reviewed fix for this situation: A code deployment changes an ETL function's parameter name but unit tests exercise only the old pipeline entry point. Which observed outcome would most convincingly validate the fix?
- The load starts only when the reviewed export completion condition is met.
- The new deployment fails validation before production if a required parameter is missing.
- A fixture with two nested lines produces correct line and order totals.
- Mixed old/new fixtures produce expected typed output or documented rejects.
Explanation
Correct Answer
B:The new deployment fails validation before production if a required parameter is missing. This verifies the result of run contract and integration tests on the packaged pipeline artifact with versioned parameters.
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.
C:This would verify another situation: A Glue job reading nested JSON flattens arrays incorrectly and duplicates parent order totals. It does not validate the current case.
D:This would verify another situation: A Glue PySpark job fails when an upstream field changes from integer to string in some JSON documents. It does not validate the current case.
AWS Certified Data Engineer - Associate DEA-C01 Practice Tests