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 160
After resolving the following incident, which ongoing safeguard most directly prevents recurrence? A legal-hold dataset is subject to an S3 Lifecycle expiration rule that would remove evidence at the usual age.
- Run type-conformance checks before crawlers refresh production metadata.
- Classify transactional versus analytical requirements in storage design reviews.
- Contract-test the partition naming convention at writer and catalog boundaries.
- Verify legal-hold operations in compliance test scenarios.
Explanation
Correct Answer
D:Verify legal-hold operations in compliance test scenarios. This safeguards against a recurring cause: Retention policy must not override active preservation requirements.
Incorrect Answers
A:That safeguard addresses another case: A crawler changes a decimal sales column to string after encountering a nonnumeric banner row in one export. It is not the control for this recurring failure.
B:That safeguard addresses another case: A Redshift analytics warehouse holds transactional checkout rows that require thousands of short atomic row updates per second. It is not the control for this recurring failure.
C:This safeguard addresses another failure: A table claims a `region` partition key but the written S3 paths use `geography=...`, so Athena pruning fails. It is not the direct control for this recurring problem.
Question 161
A DMS CDC task finishes a full-load phase but stops capturing source table changes when the source transaction log expires. Select TWO complementary measures that correctly repair and validate this failure.
- A source insert or update reaches the target after an interruption and restart.
- Align source transaction-log retention, DMS checkpoints, and CDC task health with the recovery objective.
- Shuffle volume declines and matching output rows remain identical.
- Restart full load repeatedly without protecting CDC checkpoints.
- Apply a defined typed schema, normalize units, and retain raw payloads for replay.
Explanation
Correct Answers
A:A source insert or update reaches the target after an interruption and restart. This is the observable result required before accepting the correction.
B:Align source transaction-log retention, DMS checkpoints, and CDC task health with the recovery objective. The underlying cause is: Change capture cannot read required historical database logs after source retention.
Incorrect Answers
C:This would validate a different case: A Glue job joins a tiny lookup table to billions of rows and performs a full distributed shuffle. It does not verify the outcome required here.
D:Restart full load repeatedly without protecting CDC checkpoints. That shortcut conflicts with the stated requirement.
E:That corrective action is for a different case: A clickstream pipeline converts all nested attributes to strings before storage, making numeric analytics unreliable. It does not resolve this incident.
Question 162
A Glue job begins consuming twice its normal DPU budget after a transformation adds a repeated cross join. Which technical dependency most directly explains this behavior?
- Recipe selection and deployment version are not aligned.
- The transformation treats identifiers as numeric measures rather than text keys.
- Job terminal status is not equivalent to acceptance of the produced data product.
- Changed query logic multiplies intermediate data and compute cost.
Explanation
Correct Answer
D:Changed query logic multiplies intermediate data and compute cost. The corresponding fix is to profile physical plans and remove unintended cross joins or use reviewed predicates.
Incorrect Answers
A:This diagnosis addresses another AWS case: A Glue DataBrew recipe was changed interactively but the production pipeline still applies a previous published recipe version. The dependency here is different.
B:This diagnosis addresses another AWS case: An analyst creates a Glue DataBrew visual cleaning step that trims all leading zeros from product IDs, breaking lookups. The dependency here is different.
C:This diagnosis addresses another AWS case: A Glue ETL job completes with warnings but the orchestrator assumes success despite a downstream quality check failing. The dependency here is different.
Question 163
A vector retrieval index stores embeddings from two incompatible model versions in one dimension-dependent collection. Which engineering change best addresses the underlying issue?
- Inventory schema conversion separately, apply validated DDL and rehearse dependency ordering.
- Set separately reviewed current and noncurrent version lifecycle policies.
- Move the transactional system of record to a suitable relational operational database and replicate analysis data to Redshift.
- Separate or migrate embeddings under explicit model versions and index compatibility rules.
Explanation
Correct Answer
D:Separate or migrate embeddings under explicit model versions and index compatibility rules. It directly addresses the case cause (Embedding dimensionality and semantic spaces are not aligned.) and should be verified by: Queries return comparable relevant neighbors from a consistent model representation.
Incorrect Answers
A:That change addresses an AWS DMS migration creates a new database table but foreign-key dependencies fail during cutover because schema compatibility was never rehearsed; it would not repair this incident.
B:That change addresses an S3 lifecycle rule expires noncurrent object versions immediately, preventing recovery from accidental overwrites; it would not repair this incident.
C:That change addresses a Redshift analytics warehouse holds transactional checkout rows that require thousands of short atomic row updates per second; it would not repair this incident.
Question 164
A Step Functions state invokes a Lambda using a role that trusts EC2 instead of the Step Functions service. Which engineering change best addresses the underlying issue?
- Use approved Macie sensitive-data discovery and validated data classifications with access review.
- Configure the appropriate service-principal trust and scoped invocation policy.
- Use AWS Config resource history/rules alongside CloudTrail API events as appropriate.
- Grant scoped data-location and catalog permissions alongside required IAM policies.
Explanation
Correct Answer
B:Configure the appropriate service-principal trust and scoped invocation policy. It directly addresses the case cause (The role trust policy does not admit the actual service principal.) and should be verified by: A controlled state machine execution invokes only its intended function.
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 an AWS Config rule flags altered S3 encryption settings but the team uses CloudTrail alone as its continuous current-state configuration inventory; it would not repair this incident.
D:That change addresses an AWS Glue job writes to a governed S3 target but lacks the Lake Formation data-location access permission required for its workflow; it would not repair this incident.
Question 165
A Redshift data analyst has a role granting broad schema CREATE and DROP despite requiring only SELECT on a few views. Which technical dependency most directly explains this behavior?
- Object-level S3 reads require appropriate data-event collection scope.
- Network reachability is distinct from the execution role's S3 authorization.
- The published data access layer does not implement required masking or view restrictions.
- Database privilege scope exceeds the analyst's reporting purpose.
Explanation
Correct Answer
D:Database privilege scope exceeds the analyst's reporting purpose. The corresponding fix is to define and grant a read-only database role on approved schemas and views.
Incorrect Answers
A:This diagnosis addresses another AWS case: An S3 data-access investigation searches CloudTrail for object reads but only management events were enabled. The dependency here is different.
B:This diagnosis addresses another AWS case: 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. The dependency here is different.
C:This diagnosis addresses another AWS case: A Redshift view exposes unmasked customer SSNs to a general BI role despite a requirement for partial disclosure. The dependency here is different.
Question 166
An ETL task finishes but its success event omits the S3 prefix and schema version needed downstream. Which engineering change best addresses the underlying issue?
- Evaluate enhanced fan-out registered consumers or a revised shard capacity plan.
- Publish versioned manifest metadata containing output location, partition, checksum, and schema identity.
- Check Glue connection subnet, ENIs, VPC routing, DNS, and the source's inbound rule.
- Use stable event identities and a sink merge/conditional-write design tied to checkpoint semantics.
Explanation
Correct Answer
B:Publish versioned manifest metadata containing output location, partition, checksum, and schema identity. It directly addresses the case cause (Workflow handoff lacks a complete machine-readable output contract.) and should be verified by: The consumer selects the exact intended output without relying on a guessed path.
Incorrect Answers
A:That change addresses three independent Kinesis applications compete for shared shard read throughput and their IteratorAge rises together; it would not repair this incident.
C: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.
D:That change addresses a Glue streaming job writes duplicate target rows when a microbatch is retried after a worker restart; it would not repair this incident.
Question 167
After resolving the following incident, which ongoing safeguard most directly prevents recurrence? An EMR workflow submits five jobs simultaneously but two require the first job's generated HDFS staging output.
- Alert on source-to-availability freshness and watermark breaches.
- Validate log persistence during cluster termination drills.
- Test analytic calculations against shuffled and missing-day series.
- Review dependency edges and intermediate outputs on each workflow change.
Explanation
Correct Answer
D:Review dependency edges and intermediate outputs on each workflow change. This safeguards against a recurring cause: Workflow execution order lacks explicit job dependencies.
Incorrect Answers
A:That safeguard addresses another case: A daily S3 data lake output is present but the last successful ETL timestamp is two days old. It is not the control for this recurring failure.
B:That safeguard addresses another case: An EMR job intermittently fails due to capacity interruptions but its logs are stored only on the terminated instance. It is not the control for this recurring failure.
C:That safeguard addresses another case: A data science notebook uses a rolling 7-day average without ordering by event date, so results change with input row order. It is not the control for this recurring failure.
Question 168
A processing job ingests gzipped files but its connector treats their contents as uncompressed text and creates corrupt rows. Which technical dependency most directly explains this behavior?
- Linear repeated lookups are inefficient for a high-cardinality membership workload.
- Input compression settings do not match the actual object encoding.
- Producer bootstrap configuration does not follow the advertised Kafka broker endpoint set.
- The ingestion client ignores pagination tokens or cursor continuation.
Explanation
Correct Answer
B:Input compression settings do not match the actual object encoding. The corresponding fix is to configure supported decompression and validate input format before parsing.
Incorrect Answers
A:This diagnosis addresses another AWS case: A large ETL data structure uses a list for repeated membership checks and CPU use grows unexpectedly. The dependency here is different.
C:This diagnosis addresses another AWS case: An MSK producer succeeds only intermittently after brokers change because its connection string contains one retired broker address. The dependency here is different.
D:This diagnosis addresses another AWS case: A daily batch extraction reads only the first page of a vendor REST API and silently loses subsequent records. The dependency here is different.
Question 169
After resolving the following incident, which ongoing safeguard most directly prevents recurrence? A customer expects fast key-value reads over frequently accessed session state yet stores every session in a multi-megabyte compressed S3 archive.
- Review hot/cold access patterns and storage-tier choices.
- Verify legal-hold operations in compliance test scenarios.
- Benchmark partition count and size distributions.
- Log catalog, database and table identity in query runs.
Explanation
Correct Answer
A:Review hot/cold access patterns and storage-tier choices. This safeguards against a recurring cause: The object layout introduces avoidable fetch/decompression overhead for granular hot data.
Incorrect Answers
B:That safeguard addresses another case: A legal-hold dataset is subject to an S3 Lifecycle expiration rule that would remove evidence at the usual age. It is not the control for this recurring failure.
C: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.
D:That safeguard addresses another case: Two Athena workgroups query identically named tables but one references a different data catalog and gets old records. It is not the control for this recurring failure.
Question 170
A dataset uses Iceberg but Spark and Athena query different catalogs and show conflicting table snapshots. Which engineering change best addresses the underlying issue?
- Validate retention requirements and apply supported retention/lock controls before approving lifecycle changes.
- Align approved partition key definitions and S3 path generation or repair registered metadata.
- Join using correct surrogate keys or as-of effective dates for SCD history.
- Unify the supported catalog/table identity and validate snapshot visibility across engines.
Explanation
Correct Answer
D:Unify the supported catalog/table identity and validate snapshot visibility across engines. It directly addresses the case cause (Consumers are not referencing the same authoritative table metadata location and snapshot.) and should be verified by: Both engines read the same committed table snapshot within planned freshness bounds.
Incorrect Answers
A:That change addresses an S3 data product has an approved seven-year retention requirement, but an engineer adds a 30-day expiration lifecycle rule; it would not repair this incident.
B:This change is appropriate to another case: A table claims a `region` partition key but the written S3 paths use `geography=...`, so Athena pruning fails. It does not directly repair this incident.
C:That change addresses a warehouse fact table is joined to customer history using only customer ID, multiplying matches across changing customer versions; it would not repair this incident.
AWS Certified Data Engineer - Associate DEA-C01 Practice Tests