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 900
An AWS Config rule flags altered S3 encryption settings but the team uses CloudTrail alone as its continuous current-state configuration inventory. Select THREE complementary measures that correctly repair and validate, and prevent recurrence of this failure.
- Publish ownership, purpose, classification and scoped project access before sharing.
- Conclude an unchanged API event count proves no configuration drift.
- A controlled bucket configuration change is detected with historical and current evidence.
- Map required change evidence to the appropriate audit services.
- Use AWS Config resource history/rules alongside CloudTrail API events as appropriate.
- The crawler accesses the RDS schema from its actual VPC context.
Explanation
Correct Answers
C:A controlled bucket configuration change is detected with historical and current evidence. This is the observable result required before accepting the correction.
D:Map required change evidence to the appropriate audit services. This protects against the following risk: API activity history does not directly replace configuration-state/compliance evaluation.
E:Use AWS Config resource history/rules alongside CloudTrail API events as appropriate. The underlying cause is: API activity history does not directly replace configuration-state/compliance evaluation.
Incorrect Answers
A:That corrective action is for a different case: A SageMaker Catalog project shares a data product broadly across teams without recording owner and allowed purpose. It does not resolve this incident.
B:Conclude an unchanged API event count proves no configuration drift. That shortcut conflicts with the stated requirement.
F:This would validate a different case: A Glue crawler in a VPC fails connection to a private RDS source even with the right IAM service role. It does not verify the outcome required here.
Question 901
A dataset uses Iceberg but Spark and Athena query different catalogs and show conflicting table snapshots. Select TWO complementary measures that correctly repair and validate this failure.
- Reassess partition keys/granularity and apply efficient columnar file layout.
- Old records remain readable and new optional fields are preserved for updated consumers.
- Overwrite Iceberg metadata files manually to force a common view.
- Unify the supported catalog/table identity and validate snapshot visibility across engines.
- Both engines read the same committed table snapshot within planned freshness bounds.
Explanation
Correct Answers
D:Unify the supported catalog/table identity and validate snapshot visibility across engines. The underlying cause is: Consumers are not referencing the same authoritative table metadata location and snapshot.
E:Both engines read the same committed table snapshot within planned freshness bounds. This is the observable result required before accepting the correction.
Incorrect Answers
A:That corrective action is for a different case: An Athena table uses daily partitions on a timestamp with millions of near-empty partition folders. It does not resolve this incident.
B:This would validate a different case: A lake dataset adds an optional JSON field and an older consumer fails because it expects an exact fixed set of keys. It does not verify the outcome required here.
C:Overwrite Iceberg metadata files manually to force a common view. That shortcut conflicts with the stated requirement.
Question 902
After resolving the following incident, which ongoing safeguard most directly prevents recurrence? A scheduled ETL uses an API token embedded in source code; rotation breaks the batch without an alert.
- Alert on source-to-availability freshness and watermark breaches.
- Specify measurement units and distinct-key definitions beside reports.
- Track secret age and test rotation during disaster-recovery drills.
- Review service log-retention settings when compliance requirements change.
Explanation
Correct Answer
C:Track secret age and test rotation during disaster-recovery drills. This safeguards against a recurring cause: Credential retrieval and rotation are not part of the workload lifecycle.
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: A marketing report uses COUNT(*) of event records as its active user metric and overstates adoption when users retry. It is not the control for this recurring failure.
D:That safeguard addresses another case: A Lambda processor logs errors but its CloudWatch Logs retention is shorter than the postmortem evidence requirement. It is not the control for this recurring failure.
Question 903
After resolving the following incident, which ongoing safeguard most directly prevents recurrence? A data quality gate compares raw and target record totals without accounting for intentional filter exclusions, falsely failing clean batches.
- Maintain row-count ledgers through ETL stages.
- Define alarm thresholds using service objectives and error budgets.
- Review dependency edges and intermediate outputs on each workflow change.
- Test idempotency and unknown-success network failure scenarios.
Explanation
Correct Answer
A:Maintain row-count ledgers through ETL stages. This safeguards against a recurring cause: The reconciliation rule ignores documented transformation semantics and accepted rejects.
Incorrect Answers
B:That safeguard addresses another case: A monitoring rule sees one Athena query failure and pages the full team despite a known transient backend retry. 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.
D:That safeguard addresses another case: A pipeline calls an AWS SDK to invoke Glue but drops the request token on network timeout and starts duplicate ETL runs. It is not the control for this recurring failure.
Question 904
A team applies a reviewed fix for this situation: An application seeks low-latency semantic recommendations but indexes product names as plain text without generated embeddings. Which observed outcome would most convincingly validate the fix?
- A finance analyst can identify the approved authoritative dataset and owner.
- Compliance fixtures remain available for the required duration.
- Historical snapshots and new rows remain queryable during the migration.
- Test similar products rank appropriately for documented benchmark queries.
Explanation
Correct Answer
D:Test similar products rank appropriately for documented benchmark queries. This verifies the result of generate versioned embeddings and store/index vectors in a supported eligible vector-capable service.
Incorrect Answers
A:This would verify another situation: An analytics team relies on Glue technical table names to determine which datasets are permitted for finance reporting. It does not validate the current case.
B:This would verify another situation: An S3 data product has an approved seven-year retention requirement, but an engineer adds a 30-day expiration lifecycle rule. 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.
Question 905
A Glue PySpark job fails when an upstream field changes from integer to string in some JSON documents. Which technical dependency most directly explains this behavior?
- Schema inference is unstable across source data evolution.
- The event identity is not unique across simultaneously generated records.
- The delivery layout lacks event-derived partition selection.
- The workflow treats the service invocation acknowledgement as a completed workload.
Explanation
Correct Answer
A:Schema inference is unstable across source data evolution. The corresponding fix is to apply an explicit compatible schema or deliberate conversion and quarantine unparseable values.
Incorrect Answers
B:This diagnosis addresses another AWS case: A mobile event producer uses timestamp as the only deduplication key and collapses unrelated events recorded in one millisecond. The dependency here is different.
C:This diagnosis addresses another AWS case: A Firehose stream delivering transactions to S3 mixes every customer into the same prefix, making Athena queries scan all tenants. The dependency here is different.
D:This diagnosis addresses another AWS case: A Step Functions pipeline sends a notification before the ETL task's asynchronous execution actually completes. The dependency here is different.
Question 906
A team applies a reviewed fix for this situation: An application sends semi-structured documents to an LLM to classify regulated labels but stores model output without schema checking. Which observed outcome would most convincingly validate the fix?
- Producer reconnects and publishes through broker failover without hard-coded single-host dependency.
- A load rehearsal stays within accepted throttle and freshness targets.
- Malformed or ungrounded responses are quarantined while valid labels pass contract checks.
- Two distinct same-timestamp events survive, while a retried ID deduplicates.
Explanation
Correct Answer
C:Malformed or ungrounded responses are quarantined while valid labels pass contract checks. This verifies the result of validate the model response against an explicit schema, use bounded retries and route uncertain results for review.
Incorrect Answers
A:This would verify another situation: An MSK producer succeeds only intermittently after brokers change because its connection string contains one retired broker address. It does not validate the current case.
B:This would verify another situation: A Lambda ETL function exhausts concurrency during a flash sale, causing fresh events to be throttled. It does not validate the current case.
D:This would verify another situation: A mobile event producer uses timestamp as the only deduplication key and collapses unrelated events recorded in one millisecond. It does not validate the current case.
Question 907
A team applies a reviewed fix for this situation: An engineer adds a new processing step to an AWS Glue workflow but never connects its trigger to the existing dependency chain. Which observed outcome would most convincingly validate the fix?
- A known delayed event updates the intended window according to policy.
- A product ID such as 00027 remains unchanged after the approved cleaning step.
- A controlled workflow run invokes the added job exactly in the expected order.
- Independent sampled and held-out metrics agree within the predeclared tolerance.
Explanation
Correct Answer
C:A controlled workflow run invokes the added job exactly in the expected order. This verifies the result of add and validate the correct conditional trigger path from the predecessor job.
Incorrect Answers
A: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.
B:This would verify another situation: An analyst creates a Glue DataBrew visual cleaning step that trims all leading zeros from product IDs, breaking lookups. It does not validate the current case.
D:This would verify another situation: An Athena Spark notebook reads only a handful of development files yet a manager interprets its average as an entire production trend. It does not validate the current case.
Question 908
A team applies a reviewed fix for this situation: A Lambda Kinesis event-source mapping repeatedly delivers the same batch after one malformed record fails. Which observed outcome would most convincingly validate the fix?
- Only the matching authorized callback advances the waiting workflow.
- The malformed record is isolated and good records do not create duplicate side effects.
- Peak concurrent calls stay bounded and all tasks finish without escalating throttles.
- Valid dates load accurately and malformed rows are recorded for repair.
Explanation
Correct Answer
B:The malformed record is isolated and good records do not create duplicate side effects. This verifies the result of use supported partial batch failure handling and idempotent sink writes with a failure destination.
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.
C:This would verify another situation: A pipeline launches thousands of concurrent Step Functions Map tasks and saturates a small partner API. It does not validate the current case.
D:This would verify another situation: A Redshift COPY import fails on a changed date format in one batch even though prior files loaded. It does not validate the current case.
Question 909
An S3 replication configuration excludes delete markers, but a team assumes target data will reflect source deletes instantly. Which engineering change best addresses the underlying issue?
- Review supported replication/delete-marker configuration and establish reconciliation monitoring.
- Benchmark supported HNSW or other index choices against ground-truth neighbors and query latency.
- Grant scoped S3 and catalog/Lake Formation access to the Redshift authorized role.
- Design a supported Apache Iceberg table with compatible catalog and compute engines.
Explanation
Correct Answer
A:Review supported replication/delete-marker configuration and establish reconciliation monitoring. It directly addresses the case cause (Replication configuration and timing do not satisfy the assumed deletion semantics.) and should be verified by: A controlled delete produces the documented target behavior within accepted lag.
Incorrect Answers
B:That change addresses an Aurora PostgreSQL vector workload uses a vector index tuned for approximate nearest neighbors without checking recall for a new embedding model; it would not repair this incident.
C:That change addresses a Redshift Spectrum external table points to S3 partitions whose IAM role cannot read the new prefix after an account move; it would not repair this incident.
D:That change addresses a team needs ACID updates and time-travel queries against a governed S3 lake but writes plain Parquet files with no table transaction metadata; it would not repair this incident.
Question 910
A Glue crawler crawls the entire lake for every hourly feed and adds unexpected tables from temporary staging prefixes. Which technical dependency most directly explains this behavior?
- Retention policy must not override active preservation requirements.
- Crawler scope is broader than the governed dataset and includes nonauthoritative paths.
- The warehouse load lacks deterministic upsert/merge semantics.
- Raw object files do not by themselves provide open-table transaction semantics.
Explanation
Correct Answer
B:Crawler scope is broader than the governed dataset and includes nonauthoritative paths. The corresponding fix is to restrict crawler targets, table prefixes and schema-change behavior to approved locations.
Incorrect Answers
A:This diagnosis addresses another AWS case: A legal-hold dataset is subject to an S3 Lifecycle expiration rule that would remove evidence at the usual age. The dependency here is different.
C:This diagnosis addresses another AWS case: A Redshift reporting pipeline accumulates duplicate business keys after retries because it appends without reconciling current versions. The dependency here is different.
D:This diagnosis addresses another AWS case: A team needs ACID updates and time-travel queries against a governed S3 lake but writes plain Parquet files with no table transaction metadata. The dependency here is different.
AWS Certified Data Engineer - Associate DEA-C01 Practice Tests