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 780
A team applies a reviewed fix for this situation: An AWS Config rule flags altered S3 encryption settings but the team uses CloudTrail alone as its continuous current-state configuration inventory. Which observed outcome would most convincingly validate the fix?
- A test export contains permitted pseudonyms and omits restricted raw fields.
- A controlled bucket configuration change is detected with historical and current evidence.
- A controlled state machine execution invokes only its intended function.
- The user obtains aggregate headcount without querying raw compensation fields.
Explanation
Correct Answer
B:A controlled bucket configuration change is detected with historical and current evidence. This verifies the result of use AWS Config resource history/rules alongside CloudTrail API events as appropriate.
Incorrect Answers
A:This would verify another situation: A DynamoDB-backed application needs to redact sensitive values before exporting analytics but relies only on table encryption. It does not validate the current case.
C: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.
D:This would verify another situation: A Lake Formation table exposes a private salary column through a broad Athena SELECT grant when an analyst needs only aggregated headcount. It does not validate the current case.
Question 781
After resolving the following incident, which ongoing safeguard most directly prevents recurrence? A data ingestion service accepts API JSON but passes inconsistent event time zones to downstream partitions.
- Add lifecycle checks for persistence and executor memory use.
- Include sink recovery and duplicate tests in streaming deployment gates.
- Record expected grain for every output fact table.
- Apply schema and timestamp quality tests at ingress.
Explanation
Correct Answer
D:Apply schema and timestamp quality tests at ingress. This safeguards against a recurring cause: Upstream event timestamps lack a normalized timezone and parsing contract.
Incorrect Answers
A:That safeguard addresses another case: An EMR Spark pipeline runs near memory limits because it caches multiple large datasets and never releases them. It is not the control for this recurring failure.
B:That safeguard addresses another case: A Glue streaming job writes duplicate target rows when a microbatch is retried after a worker restart. It is not the control for this recurring failure.
C:That safeguard addresses another case: A nightly aggregation counts an order once per status-change event rather than once per order ID. It is not the control for this recurring failure.
Question 782
After resolving the following incident, which ongoing safeguard most directly prevents recurrence? A small dimension table joins huge Redshift facts, but an unnecessarily EVEN distribution causes repeated data transfer.
- Practice restore and replay consistency during recovery drills.
- Define backward/forward compatibility rules before source rollout.
- Document fact grain and validate cardinality in data model reviews.
- Review table size and plan evidence before overriding AUTO placement.
Explanation
Correct Answer
D:Review table size and plan evidence before overriding AUTO placement. This safeguards against a recurring cause: Data placement increases redistribution for a frequently used join.
Incorrect Answers
A:That safeguard addresses another case: A cross-region disaster recovery table is restored from an old snapshot, and CDC replication starts from an incompatible new checkpoint. It is not the control for this recurring failure.
B: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.
C:That safeguard addresses another case: A Redshift star schema mixes order-line and order-header facts in the same table and reports double-count revenue. It is not the control for this recurring failure.
Question 783
A Lambda processor logs errors but its CloudWatch Logs retention is shorter than the postmortem evidence requirement. Select THREE complementary measures that correctly repair and validate, and prevent recurrence of this failure.
- Review service log-retention settings when compliance requirements change.
- A maximum-size sample completes with a checkpointed durable output.
- A test log remains available through the required investigation period.
- Set an appropriate retention and controlled access policy for log groups.
- Disable log creation to avoid unexpected log-retention cost.
- Use defensible stratified sampling with confidence limits or full checks for critical constraints.
Explanation
Correct Answers
A:Review service log-retention settings when compliance requirements change. This protects against the following risk: Operational log retention is not aligned with audit or incident policy.
C:A test log remains available through the required investigation period. This is the observable result required before accepting the correction.
D:Set an appropriate retention and controlled access policy for log groups. The underlying cause is: Operational log retention is not aligned with audit or incident policy.
Incorrect Answers
B:This would validate a different case: A monthly data load uses Lambda to copy hundreds of gigabytes in a single invocation and repeatedly times out. It does not verify the outcome required here.
E:Disable log creation to avoid unexpected log-retention cost. That shortcut conflicts with the stated requirement.
F:That corrective action is for a different case: A streaming pipeline evaluates quality from a random sample of 10 messages and assumes it proves a million-row batch is correct. It does not resolve this incident.
Question 784
A team applies a reviewed fix for this situation: A data access policy permits all S3 prefixes under `reports/*`, unintentionally including payroll records stored beneath that path. Which observed outcome would most convincingly validate the fix?
- A controlled state machine execution invokes only its intended function.
- The partner accesses only intended assets and access ends when approval expires.
- Development cannot write production data while ETL still runs correctly.
- The report job reads its approved prefix but payroll reads fail.
Explanation
Correct Answer
D:The report job reads its approved prefix but payroll reads fail. This verifies the result of narrow bucket and access-point resource ARNs and test effective explicit deny boundaries.
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 Redshift datashare grants partner analysts access to a customer data mart without a purpose or term limit. It does not validate the current case.
C:This would verify another situation: A data engineering service uses one unrestricted role for production ETL, development notebooks and reporting. It does not validate the current case.
Question 785
An Athena automated report tries to read query results immediately after StartQueryExecution returns a query ID. Select TWO complementary measures that correctly repair and validate this failure.
- Rebuild and test connector libraries against the supported new Glue runtime.
- Poll GetQueryExecution with bounded backoff and handle FAILED/CANCELLED before reading results.
- Report generation uses only a successful query's actual result location.
- Read the output S3 prefix immediately after query submission.
- A deliberately truncated file triggers a quality alert and prevents false success.
Explanation
Correct Answers
B:Poll GetQueryExecution with bounded backoff and handle FAILED/CANCELLED before reading results. The underlying cause is: The report does not wait for the asynchronous query to reach SUCCEEDED.
C:Report generation uses only a successful query's actual result location. This is the observable result required before accepting the correction.
Incorrect Answers
A:That corrective action is for a different case: A data pipeline updates its Glue version but custom connector dependencies fail at initialization. It does not resolve this incident.
D:Read the output S3 prefix immediately after query submission. That shortcut conflicts with the stated requirement.
E:This would validate a different case: A feed arrives with 30% fewer rows than normal, but a transformation succeeds and marks the data product complete. It does not verify the outcome required here.
Question 786
After resolving the following incident, which ongoing safeguard most directly prevents recurrence? An analytics partition must be removed under a deletion request, yet its historical copies persist in untracked S3 archive paths.
- Maintain deletion inventories and downstream lineage obligations.
- Benchmark partition count and size distributions.
- Revalidate vector dimensions and retrieval metrics after model revisions.
- Track metadata version and compatible migration steps per release.
Explanation
Correct Answer
A:Maintain deletion inventories and downstream lineage obligations. This safeguards against a recurring cause: Data deletion workflow lacks a complete inventory of copies and derived datasets.
Incorrect Answers
B:That safeguard addresses another case: An Athena table uses daily partitions on a timestamp with millions of near-empty partition folders. It is not the control for this recurring failure.
C:That safeguard addresses another case: An Aurora PostgreSQL vector workload uses a vector index tuned for approximate nearest neighbors without checking recall for a new embedding model. It is not the control for this recurring failure.
D: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.
Question 787
A Glue ETL job completes with warnings but the orchestrator assumes success despite a downstream quality check failing. Which technical dependency most directly explains this behavior?
- Job terminal status is not equivalent to acceptance of the produced data product.
- A reporting timestamp interpretation differs from the approved aggregation calendar.
- SQL window scope does not match the required per-tenant aggregation.
- The sample does not represent the target population and interval.
Explanation
Correct Answer
A:Job terminal status is not equivalent to acceptance of the produced data product. The corresponding fix is to add explicit row-count, schema, and quality validation before the publish step.
Incorrect Answers
B:This diagnosis addresses another AWS case: A daily sales pivot groups event timestamps by the viewer's local date and differs from the regulatory UTC day. The dependency here is different.
C:This diagnosis addresses another AWS case: A Redshift window query uses SUM without the intended PARTITION BY and produces one cumulative total over all tenants. The dependency here is different.
D:This diagnosis addresses another AWS case: An Athena Spark notebook reads only a handful of development files yet a manager interprets its average as an entire production trend. The dependency here is different.
Question 788
A lake dataset adds an optional JSON field and an older consumer fails because it expects an exact fixed set of keys. Select THREE complementary measures that correctly repair and validate, and prevent recurrence of this failure.
- Use supported S3 Object Lock legal hold/retention and review lifecycle interactions.
- Protected test objects remain undeletable under expected retention conditions.
- Use versioned compatible schemas and tolerant reads with explicit unknown-field handling.
- Delete all legacy records whenever a new optional column appears.
- Old records remain readable and new optional fields are preserved for updated consumers.
- Define backward/forward compatibility rules before source rollout.
Explanation
Correct Answers
C:Use versioned compatible schemas and tolerant reads with explicit unknown-field handling. The underlying cause is: Schema evolution is treated as a breaking change despite an optional additive field.
E:Old records remain readable and new optional fields are preserved for updated consumers. This is the observable result required before accepting the correction.
F:Define backward/forward compatibility rules before source rollout. This protects against the following risk: Schema evolution is treated as a breaking change despite an optional additive field.
Incorrect Answers
A:That corrective action is for a different case: A legal-hold dataset is subject to an S3 Lifecycle expiration rule that would remove evidence at the usual age. It does not resolve this incident.
B:This would validate a different case: A legal-hold dataset is subject to an S3 Lifecycle expiration rule that would remove evidence at the usual age. It does not verify the outcome required here.
D:Delete all legacy records whenever a new optional column appears. That shortcut conflicts with the stated requirement.
Question 789
A team applies a reviewed fix for this situation: A Glue transform joins events to reference data refreshed weekly, but old events are silently reclassified on every rerun. Which observed outcome would most convincingly validate the fix?
- Only the matching authorized callback advances the waiting workflow.
- Replaying the same event leaves one intended item state and audit increment.
- The published job serializes work to executors and produces correct output.
- A replayed historical event receives its original applicable classification.
Explanation
Correct Answer
D:A replayed historical event receives its original applicable classification. This verifies the result of join by intended as-of validity and persist versioned reference mappings.
Incorrect Answers
A:This would verify another situation: A Step Functions Standard workflow waits for an external vendor callback but the task token is lost in logs. It does not validate the current case.
B:This would verify another situation: An ingestion app writes identical DynamoDB item updates after a network retry and an audit counter increments twice. It does not validate the current case.
C: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.
Question 790
A daily sensor batch is duplicated after retry, causing every aggregate event count to double. Which technical dependency most directly explains this behavior?
- The query unnecessarily reads columns beyond its actual projection.
- The orchestration integration returns before the asynchronous ETL work finishes.
- Skew creates straggler executors and prevents completion within the SLA.
- The pipeline lacks stable event-level uniqueness validation.
Explanation
Correct Answer
D:The pipeline lacks stable event-level uniqueness validation. The corresponding fix is to deduplicate on a documented source event key and verify idempotent load state.
Incorrect Answers
A:This diagnosis addresses another AWS case: An Athena query uses SELECT * on a wide Parquet table, although the report needs two measures and a date. The dependency here is different.
B:This diagnosis addresses another AWS case: A Step Functions data pipeline invokes Glue using a request/response integration and immediately launches Athena against unfinished output. The dependency here is different.
C:This diagnosis addresses another AWS case: An ETL task in Glue times out only when a small fraction of keys dominate the daily partition. The dependency here is different.
AWS Certified Data Engineer - Associate DEA-C01 Practice Tests