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 740
An API payload includes optional addresses but a transformation fails when a nullable nested object is absent. Select THREE complementary measures that correctly repair and validate, and prevent recurrence of this failure.
- Fill missing addresses with fabricated real customer details.
- Fixtures with present, null, and missing fields receive expected values or rejects.
- Use nullable-aware extraction and document sensible default or reject handling per field.
- Include sparse and schema-evolution samples in transformation tests.
- The DAG parses and a controlled run completes its expected task graph.
- Retry bounded transient exceptions and catch permanent validation failures for quarantine.
Explanation
Correct Answers
B:Fixtures with present, null, and missing fields receive expected values or rejects. This is the observable result required before accepting the correction.
C:Use nullable-aware extraction and document sensible default or reject handling per field. The underlying cause is: The pipeline assumes every optional path exists for every row.
D:Include sparse and schema-evolution samples in transformation tests. This protects against the following risk: The pipeline assumes every optional path exists for every row.
Incorrect Answers
A:Fill missing addresses with fabricated real customer details. That shortcut conflicts with the stated requirement.
E:This would validate a different case: An MWAA DAG was deployed but its Python import fails, so no scheduled run appears. It does not verify the outcome required here.
F:That corrective action is for a different case: A Step Functions state retries every failure including invalid schema, consuming budget without possibility of success. It does not resolve this incident.
Question 741
An S3 replication configuration excludes delete markers, but a team assumes target data will reflect source deletes instantly. Select TWO complementary measures that correctly repair and validate this failure.
- Review supported replication/delete-marker configuration and establish reconciliation monitoring.
- A controlled delete produces the documented target behavior within accepted lag.
- A multi-line order yields correct revenue and item counts in fixture reports.
- Assume every replicated bucket behaves as a synchronous mirror.
- Migrate writers, metadata, and readers through a dual-read/reconciliation plan.
Explanation
Correct Answers
A:Review supported replication/delete-marker configuration and establish reconciliation monitoring. The underlying cause is: Replication configuration and timing do not satisfy the assumed deletion semantics.
B:A controlled delete produces the documented target behavior within accepted lag. This is the observable result required before accepting the correction.
Incorrect Answers
C:This would validate a different case: A Redshift star schema mixes order-line and order-header facts in the same table and reports double-count revenue. It does not verify the outcome required here.
D:Assume every replicated bucket behaves as a synchronous mirror. That shortcut conflicts with the stated requirement.
E:That corrective action is for a different case: An S3-based table changes from hourly to daily partitions while old writers still publish hourly paths, giving inconsistent query results. It does not resolve this incident.
Question 742
A team applies a reviewed fix for this situation: A Redshift reporting job suddenly spends time redistributing a large fact table after a schema change. Which observed outcome would most convincingly validate the fix?
- Malformed fixture values fail quality checks without discarding unrelated valid records.
- A known delayed event updates the intended window according to policy.
- Execution plan and runtime return within accepted bounds with identical answers.
- A burst drains within the recovery SLA without widespread throttling.
Explanation
Correct Answer
C:Execution plan and runtime return within accepted bounds with identical answers. This verifies the result of inspect EXPLAIN and workload metrics; review distribution, sort and join design.
Incorrect Answers
A:This would verify another situation: A Glue data quality rule checks only that an email column is nonnull but accepts invalid malformed addresses. It does not validate the current case.
B:This would verify another situation: A nightly data product uses a moving seven-day window but incoming source events arrive late and are excluded without a watermark policy. It does not validate the current case.
D:This would verify another situation: An orchestrated data processing task receives tens of thousands of S3 events, causing Lambda reserved concurrency exhaustion. It does not validate the current case.
Question 743
A cross-account Lake Formation share is granted but the consumer account has not accepted its RAM invitation where required. Select THREE complementary measures that correctly repair and validate, and prevent recurrence of this failure.
- Add cross-account acceptance and resource-link tests to onboarding.
- An authorized consumer principal can resolve and read the shared table.
- An ordinary BI user sees only the approved masked representation.
- Copy the producer's entire S3 bucket into the consumer account publicly.
- Require supported TLS transport and approved destination identity/key handling.
- Complete supported AWS RAM share acceptance and consumer-side permission delegation.
Explanation
Correct Answers
A:Add cross-account acceptance and resource-link tests to onboarding. This protects against the following risk: Cross-account resource sharing has a recipient-side acceptance and grant step.
B:An authorized consumer principal can resolve and read the shared table. This is the observable result required before accepting the correction.
F:Complete supported AWS RAM share acceptance and consumer-side permission delegation. The underlying cause is: Cross-account resource sharing has a recipient-side acceptance and grant step.
Incorrect Answers
C: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.
D:Copy the producer's entire S3 bucket into the consumer account publicly. That shortcut conflicts with the stated requirement.
E:That corrective action is for a different case: An S3 export writes regulated data to an unencrypted partner endpoint despite source-at-rest SSE-KMS protection. It does not resolve this incident.
Question 744
A data team cannot determine whether a report column came from the original CRM source or an intermediate cleansing step. Which technical dependency most directly explains this behavior?
- Storage read authorization does not supply the required cryptographic key access.
- Dataset lineage and transformation provenance are not recorded.
- The two metastore environments are not synchronized.
- External query credentials do not cover the current S3 resource and catalog context.
Explanation
Correct Answer
B:Dataset lineage and transformation provenance are not recorded. The corresponding fix is to record source, transformations and versioned lineage in supported catalog/project metadata.
Incorrect Answers
A:This diagnosis addresses another AWS case: A Redshift COPY command reads encrypted S3 files but the IAM role lacks decryption permission for the customer KMS key. The dependency here is different.
C:This diagnosis addresses another AWS case: A Hive metastore-based EMR Spark job writes a new partition but Athena never sees it through Glue Data Catalog. The dependency here is different.
D:This diagnosis addresses another AWS case: A Redshift Spectrum external table points to S3 partitions whose IAM role cannot read the new prefix after an account move. The dependency here is different.
Question 745
A team applies a reviewed fix for this situation: An Aurora PostgreSQL vector workload uses a vector index tuned for approximate nearest neighbors without checking recall for a new embedding model. Which observed outcome would most convincingly validate the fix?
- A controlled subject deletion is absent from permitted current and derived query paths.
- Recall and latency meet agreed thresholds on representative embeddings.
- Historical snapshots and new rows remain queryable during the migration.
- Planning overhead falls while required rollback snapshots remain available.
Explanation
Correct Answer
B:Recall and latency meet agreed thresholds on representative embeddings. This verifies the result of benchmark supported HNSW or other index choices against ground-truth neighbors and query latency.
Incorrect Answers
A:This would verify another situation: An analytics partition must be removed under a deletion request, yet its historical copies persist in untracked S3 archive paths. It does not validate the current case.
C:This would verify another situation: A team adds a nonnullable required field to an Iceberg table but old rows have no value and downstream reads fail. It does not validate the current case.
D:This would verify another situation: An Iceberg table's snapshot history grows as frequent small commits accumulate and query planning becomes slow. It does not validate the current case.
Question 746
A processing job ingests gzipped files but its connector treats their contents as uncompressed text and creates corrupt rows. Which engineering change best addresses the underlying issue?
- Check Glue connection subnet, ENIs, VPC routing, DNS, and the source's inbound rule.
- Distribute records across suitable high-cardinality partition keys while preserving required per-entity ordering.
- Model all documented terminal statuses with success, retryable, and failure branches.
- Configure supported decompression and validate input format before parsing.
Explanation
Correct Answer
D:Configure supported decompression and validate input format before parsing. It directly addresses the case cause (Input compression settings do not match the actual object encoding.) and should be verified by: Decompressed samples match checksums and expected record counts.
Incorrect Answers
A: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.
B:That change addresses a retail clickstream uses one Kinesis partition key equal to a constant and one shard is throttled while other shards idle; it would not repair this incident.
C:That change addresses a workflow branches on a job-status string but overlooks the Cancelled terminal state, leaving executions stuck; it would not repair this incident.
Question 747
After resolving the following incident, which ongoing safeguard most directly prevents recurrence? An Athena view compares monthly cohorts using an inner join that drops customers with no activity, overstating retention.
- Test on-call subscriptions and runbooks during pipeline release.
- Require multidimensional quality gates before final publish.
- Review dependency edges and intermediate outputs on each workflow change.
- Test cohort queries against absent-activity fixtures.
Explanation
Correct Answer
D:Test cohort queries against absent-activity fixtures. This safeguards against a recurring cause: The join excludes the population that must remain in the denominator.
Incorrect Answers
A:That safeguard addresses another case: A Glue job has failed for three mornings but no CloudWatch alarm exists, so dashboards show stale data. It is not the control for this recurring failure.
B:That safeguard addresses another case: A data team declares a successful cleanup because duplicate percentage fell, but the job also dropped valid unique rows. It is not the control for this recurring failure.
C:That safeguard addresses another case: An EMR workflow submits five jobs simultaneously but two require the first job's generated HDFS staging output. It is not the control for this recurring failure.
Question 748
A warehouse unload creates thousands of tiny output files, raising downstream S3 request and processing overhead. Select THREE complementary measures that correctly repair and validate, and prevent recurrence of this failure.
- Merge all output into an unencrypted publicly readable object.
- Tune supported export parallelism and downstream compaction based on file size and latency.
- Qualify or configure the intended catalog/database and verify metadata references.
- The file layout reaches acceptable size targets with identical row counts.
- Measure object count and target file sizes after export.
- A test with a banner row keeps numeric fields correctly typed and records the reject.
Explanation
Correct Answers
B:Tune supported export parallelism and downstream compaction based on file size and latency. The underlying cause is: Output partitioning produces files much smaller than efficient batch units.
D:The file layout reaches acceptable size targets with identical row counts. This is the observable result required before accepting the correction.
E:Measure object count and target file sizes after export. This protects against the following risk: Output partitioning produces files much smaller than efficient batch units.
Incorrect Answers
A:Merge all output into an unencrypted publicly readable object. That shortcut conflicts with the stated requirement.
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.
F:This would validate a different case: A crawler changes a decimal sales column to string after encountering a nonnumeric banner row in one export. It does not verify the outcome required here.
Question 749
After resolving the following incident, which ongoing safeguard most directly prevents recurrence? A Redshift Spectrum external table points to S3 partitions whose IAM role cannot read the new prefix after an account move.
- Make partition-registration a verified publish step.
- Document a single metadata owner for cross-engine lake datasets.
- Benchmark partition count and size distributions.
- Test least-privilege access after bucket and role migrations.
Explanation
Correct Answer
D:Test least-privilege access after bucket and role migrations. This safeguards against a recurring cause: External query credentials do not cover the current S3 resource and catalog context.
Incorrect Answers
A:That safeguard addresses another case: An Athena query of yesterday's S3 partition returns zero rows because its table metadata lacks that partition. It is not the control for this recurring failure.
B:That safeguard addresses another case: A Hive metastore-based EMR Spark job writes a new partition but Athena never sees it through Glue Data Catalog. 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.
Question 750
A team applies a reviewed fix for this situation: A Glue streaming job writes duplicate target rows when a microbatch is retried after a worker restart. Which observed outcome would most convincingly validate the fix?
- The Lambda retrieves the intended object without an unrestricted internet route.
- A forced retry leaves one intended row per business event.
- The consumer selects the exact intended output without relying on a guessed path.
- The malformed record is isolated and good records do not create duplicate side effects.
Explanation
Correct Answer
B:A forced retry leaves one intended row per business event. This verifies the result of use stable event identities and a sink merge/conditional-write design tied to checkpoint semantics.
Incorrect Answers
A:This would verify another situation: A batch import uses a Lambda in a private subnet that cannot reach S3 because no NAT or S3 endpoint path is configured. It does not validate the current case.
C:This would verify another situation: An ETL task finishes but its success event omits the S3 prefix and schema version needed downstream. It does not validate the current case.
D:This would verify another situation: A Lambda Kinesis event-source mapping repeatedly delivers the same batch after one malformed record fails. It does not validate the current case.
AWS Certified Data Engineer - Associate DEA-C01 Practice Tests