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 140
After resolving the following incident, which ongoing safeguard most directly prevents recurrence? A multi-account data pipeline sends operational alerts through an SNS topic that no engineer subscribes to.
- Test poison-message recovery and batch retry behavior.
- Inspect Spark physical plans and skewed partitions after release.
- Maintain supported language/runtime compatibility evidence in release reviews.
- Review subscription ownership and dead-letter paths periodically.
Explanation
Correct Answer
D:Review subscription ownership and dead-letter paths periodically. This safeguards against a recurring cause: Publishing events is not equivalent to having a viable incident notification path.
Incorrect Answers
A:That safeguard addresses another case: A Lambda Kinesis event-source mapping repeatedly delivers the same batch after one malformed record fails. It is not the control for this recurring failure.
B:That safeguard addresses another case: A data transformation uses one Spark partition for a terabyte input and only one executor stays busy. It is not the control for this recurring failure.
C:That safeguard addresses another case: A team changes an analytics library but releases a job without checking distributed task serialization compatibility. It is not the control for this recurring failure.
Question 141
A Glue connection to a source RDS database times out, although the JDBC credentials are valid. Select TWO complementary measures that correctly repair and validate this failure.
- A controlled JDBC connection from the Glue execution context succeeds.
- Inspect key distribution and apply skew-aware partitioning, salting, or alternate aggregation strategy.
- Check Glue connection subnet, ENIs, VPC routing, DNS, and the source's inbound rule.
- Grant 0.0.0.0/0 database ingress solely to make the job connect.
- Shuffle volume declines and matching output rows remain identical.
Explanation
Correct Answers
A:A controlled JDBC connection from the Glue execution context succeeds. This is the observable result required before accepting the correction.
C:Check Glue connection subnet, ENIs, VPC routing, DNS, and the source's inbound rule. The underlying cause is: Network routing or security groups block the ETL job's actual source path.
Incorrect Answers
B:That corrective action is for a different case: An EMR Spark job sends all rows for a popular customer to one reducer and fails despite plenty of idle cores. It does not resolve this incident.
D:Grant 0.0.0.0/0 database ingress solely to make the job connect. That shortcut conflicts with the stated requirement.
E: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.
Question 142
Two Athena workgroups query identically named tables but one references a different data catalog and gets old records. Select TWO complementary measures that correctly repair and validate this failure.
- Validate retention requirements and apply supported retention/lock controls before approving lifecycle changes.
- Qualify or configure the intended catalog/database and verify metadata references.
- Both engines read the same committed table snapshot within planned freshness bounds.
- Rename all tables to today's date without changing the catalog.
- Both controlled queries return the expected published dataset version.
Explanation
Correct Answers
B:Qualify or configure the intended catalog/database and verify metadata references. The underlying cause is: Query context includes the catalog and database, not just table name.
E:Both controlled queries return the expected published dataset version. This is the observable result required before accepting the correction.
Incorrect Answers
A:That corrective action is for a different case: An S3 data product has an approved seven-year retention requirement, but an engineer adds a 30-day expiration lifecycle rule. It does not resolve this incident.
C:This would validate a different case: A dataset uses Iceberg but Spark and Athena query different catalogs and show conflicting table snapshots. It does not verify the outcome required here.
D:Rename all tables to today's date without changing the catalog. That shortcut conflicts with the stated requirement.
Question 143
An Iceberg table's snapshot history grows as frequent small commits accumulate and query planning becomes slow. Which engineering change best addresses the underlying issue?
- Use a supported strongly consistent base-table or local-index read design where necessary.
- Use staged validation and controlled retention/cleanup of replaced snapshots.
- Add supported partition projection or update Glue partitions in the ingestion workflow.
- Run supported snapshot expiration and metadata cleanup with retention safeguards.
Explanation
Correct Answer
D:Run supported snapshot expiration and metadata cleanup with retention safeguards. It directly addresses the case cause (Table metadata maintenance does not match commit frequency and retention needs.) and should be verified by: Planning overhead falls while required rollback snapshots remain available.
Incorrect Answers
A:That change addresses a DynamoDB application requires strongly consistent reads immediately after a successful critical write but queries a global secondary index; it would not repair this incident.
B:That change addresses a nightly lake job publishes versioned S3 snapshots but deletes all old snapshots before the replacement is fully validated; it would not repair this incident.
C:That change addresses an Athena query of yesterday's S3 partition returns zero rows because its table metadata lacks that partition; it would not repair this incident.
Question 144
A Redshift transformation materializes a complex subquery repeatedly in one reporting workflow and exceeds its compute budget. Which technical dependency most directly explains this behavior?
- The consuming workflow lacks a reliable transfer-completion boundary.
- Repeated equivalent computation is not reused or pre-aggregated appropriately.
- The callback correlation contract is missing or insecure.
- Batch and streaming clients compete without workload isolation or rate budgets.
Explanation
Correct Answer
B:Repeated equivalent computation is not reused or pre-aggregated appropriately. The corresponding fix is to evaluate a compatible materialized view or staged aggregate with an explicit refresh policy.
Incorrect Answers
A:This diagnosis addresses another AWS case: A partner uploads a CSV over SFTP to Transfer Family but a load starts before the file finishes writing. The dependency here is different.
C:This diagnosis addresses another AWS case: A Step Functions Standard workflow waits for an external vendor callback but the task token is lost in logs. The dependency here is different.
D:This diagnosis addresses another AWS case: A large historical data export shares the same small API rate limit as near-real-time orders and delays critical events. The dependency here is different.
Question 145
After resolving the following incident, which ongoing safeguard most directly prevents recurrence? A Glue crawler crawls the entire lake for every hourly feed and adds unexpected tables from temporary staging prefixes.
- Document fact grain and validate cardinality in data model reviews.
- Add temporal join and duplicate-cardinality tests to dimensional models.
- Test range, nullability and precision for geospatial attributes.
- Manage catalog scope through IaC and exclusion regression tests.
Explanation
Correct Answer
D:Manage catalog scope through IaC and exclusion regression tests. This safeguards against a recurring cause: Crawler scope is broader than the governed dataset and includes nonauthoritative paths.
Incorrect Answers
A: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.
B:That safeguard addresses another case: A warehouse fact table is joined to customer history using only customer ID, multiplying matches across changing customer versions. It is not the control for this recurring failure.
C:That safeguard addresses another case: A lake stores customer location coordinates as one unparsed text field while downstream joins require numeric latitude and longitude. It is not the control for this recurring failure.
Question 146
A data lake copies SSE-KMS objects across AWS accounts but the destination principal cannot decrypt the replica. Which technical dependency most directly explains this behavior?
- Studio domain/project membership and resource governance are separate access contexts.
- Attribute-based permissions have a policy scope broader than the approved audience.
- Cross-account cryptographic key and replica policies do not match the consumer identities.
- Underlying S3 IAM rights alone do not satisfy applicable Lake Formation location governance.
Explanation
Correct Answer
C:Cross-account cryptographic key and replica policies do not match the consumer identities. The corresponding fix is to configure supported KMS key policy, IAM and replication encryption settings for the intended accounts.
Incorrect Answers
A:This diagnosis addresses another AWS case: An admin provisions a SageMaker Unified Studio project but the intended team cannot open governed domain assets despite being added to a general account group. The dependency here is different.
B:This diagnosis addresses another AWS case: An S3 table is tagged `classification=restricted`, but its Lake Formation LF-Tag grant allows a broad organizational unit with no business need. The dependency here is different.
D:This diagnosis addresses another AWS case: An AWS Glue job writes to a governed S3 target but lacks the Lake Formation data-location access permission required for its workflow. The dependency here is different.
Question 147
A warehouse fact table is joined to customer history using only customer ID, multiplying matches across changing customer versions. Which engineering change best addresses the underlying issue?
- Design a supported Apache Iceberg table with compatible catalog and compute engines.
- Join using correct surrogate keys or as-of effective dates for SCD history.
- Apply reviewed S3 Lifecycle transition rules to suitable eligible storage classes.
- Create governed business catalog descriptions and owner/lineage metadata in the supported catalog product.
Explanation
Correct Answer
B:Join using correct surrogate keys or as-of effective dates for SCD history. It directly addresses the case cause (Dimension joins ignore the effective time range for slowly changing records.) and should be verified by: A test order maps to exactly the customer attributes valid at transaction time.
Incorrect Answers
A: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.
C:That change addresses a data lake keeps years of detailed application logs in S3 Standard despite infrequent historical access and an approved 90-day hot tier; it would not repair this incident.
D:That change addresses an analytics team relies on Glue technical table names to determine which datasets are permitted for finance reporting; it would not repair this incident.
Question 148
After resolving the following incident, which ongoing safeguard most directly prevents recurrence? A pipeline launches thousands of concurrent Step Functions Map tasks and saturates a small partner API.
- Include sink recovery and duplicate tests in streaming deployment gates.
- Review cost per processed gigabyte and peak worker utilization.
- Test Map concurrency under real vendor budgets before promotion.
- Audit ownership and naming of consumer checkpoints.
Explanation
Correct Answer
C:Test Map concurrency under real vendor budgets before promotion. This safeguards against a recurring cause: Map concurrency is uncapped relative to external rate limits.
Incorrect Answers
A: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.
B:That safeguard addresses another case: A Glue job uses a fixed worker count at peak and wastes compute on tiny nightly delta batches. It is not the control for this recurring failure.
D:That safeguard addresses another case: Two Kinesis consumers must independently recover after a deployment, but one team reuses the other's checkpoint store. It is not the control for this recurring failure.
Question 149
A team applies a reviewed fix for this situation: A Firehose stream delivering transactions to S3 mixes every customer into the same prefix, making Athena queries scan all tenants. Which observed outcome would most convincingly validate the fix?
- Injected cancelled and failed jobs exit with correctly classified outcomes.
- A representative time-window report has correct results with lower CPU/runtime.
- A tenant query scans only the relevant partitions and records appear under expected prefixes.
- Multiple tasks use the available cluster and total runtime improves.
Explanation
Correct Answer
C:A tenant query scans only the relevant partitions and records appear under expected prefixes. This verifies the result of create a supported Firehose dynamic-partitioning delivery stream with well-chosen keys and S3 prefixes.
Incorrect Answers
A:This would verify another situation: A workflow branches on a job-status string but overlooks the Cancelled terminal state, leaving executions stuck. It does not validate the current case.
B:This would verify another situation: A Redshift query repeatedly casts a large timestamp string field during aggregation and consumes excess CPU. It does not validate the current case.
D:This would verify another situation: A data transformation uses one Spark partition for a terabyte input and only one executor stays busy. It does not validate the current case.
Question 150
After resolving the following incident, which ongoing safeguard most directly prevents recurrence? An online session store uses S3 object listing as a low-latency millisecond key lookup service and response times are erratic.
- Test functional expiration separately from background storage cleanup.
- Benchmark the required access patterns before choosing a data store.
- Record representative access patterns and authorization boundaries.
- Review lifecycle policies against audit and restore objectives annually.
Explanation
Correct Answer
B:Benchmark the required access patterns before choosing a data store. This safeguards against a recurring cause: Object storage access patterns do not match the required high-frequency key-value access.
Incorrect Answers
A:That safeguard addresses another case: A DynamoDB table contains session records with expired timestamps but items remain visible immediately after expiry. It is not the control for this recurring failure.
C:That safeguard addresses another case: A DynamoDB table uses composite key `tenant#date` but most reads are by `transaction_id` only and become scans. It is not the control for this recurring failure.
D:That safeguard addresses another case: A data lake keeps years of detailed application logs in S3 Standard despite infrequent historical access and an approved 90-day hot tier. It is not the control for this recurring failure.
AWS Certified Data Engineer - Associate DEA-C01 Practice Tests