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 940
A team needs ACID updates and time-travel queries against a governed S3 lake but writes plain Parquet files with no table transaction metadata. Which engineering change best addresses the underlying issue?
- Separate or explicitly model fact grain and join to dimensions at compatible levels.
- Design a supported Apache Iceberg table with compatible catalog and compute engines.
- Trace lineage and apply approved deletion to all eligible retained copies under policy.
- Apply approved standardized catalog classification tags or LF-Tags and validate inherited rules.
Explanation
Correct Answer
B:Design a supported Apache Iceberg table with compatible catalog and compute engines. It directly addresses the case cause (Raw object files do not by themselves provide open-table transaction semantics.) and should be verified by: Concurrent reads see committed snapshots and managed updates are queryable.
Incorrect Answers
A:That change addresses a Redshift star schema mixes order-line and order-header facts in the same table and reports double-count revenue; it would not repair this incident.
C:That change addresses an analytics partition must be removed under a deletion request, yet its historical copies persist in untracked S3 archive paths; it would not repair this incident.
D:That change addresses a data catalog stores PII labels only as free-text comments, so new tables bypass a tagging-based access process; it would not repair this incident.
Question 941
An Aurora PostgreSQL vector workload uses a vector index tuned for approximate nearest neighbors without checking recall for a new embedding model. Which engineering change best addresses the underlying issue?
- Benchmark supported HNSW or other index choices against ground-truth neighbors and query latency.
- Configure the supported classifier and decompression-aware source layout.
- Apply application-level expiry checks where strict visibility is required and keep TTL for eventual cleanup.
- Iterate with the supported LastEvaluatedKey mechanism and checkpoint progress.
Explanation
Correct Answer
A:Benchmark supported HNSW or other index choices against ground-truth neighbors and query latency. It directly addresses the case cause (Index configuration and vector characteristics affect speed/recall tradeoffs.) and should be verified by: Recall and latency meet agreed thresholds on representative embeddings.
Incorrect Answers
B:That change addresses an S3 prefix contains `.json.gz` objects but the Glue crawler labels them as raw JSON and downstream parsers fail; it would not repair this incident.
C:That change addresses a DynamoDB table contains session records with expired timestamps but items remain visible immediately after expiry; it would not repair this incident.
D:That change addresses a DynamoDB archival pipeline uses Scan without pagination and misses records beyond the first page; it would not repair this incident.
Question 942
After resolving the following incident, which ongoing safeguard most directly prevents recurrence? A daily S3 data lake output is present but the last successful ETL timestamp is two days old.
- Use key-format fixtures in data preparation recipes.
- Track cardinality and group-level drift in quality dashboards.
- Test workflow reachability and trigger states after DAG edits.
- Alert on source-to-availability freshness and watermark breaches.
Explanation
Correct Answer
D:Alert on source-to-availability freshness and watermark breaches. This safeguards against a recurring cause: Object existence alone does not prove the current scheduled partition is fresh.
Incorrect Answers
A:That safeguard addresses another case: An analyst creates a Glue DataBrew visual cleaning step that trims all leading zeros from product IDs, breaking lookups. It is not the control for this recurring failure.
B:That safeguard addresses another case: A Spark aggregation produces incorrect category totals because one hot key is dropped after a task retry and the target doesn't reconcile. It is not the control for this recurring failure.
C:That safeguard addresses another case: An engineer adds a new processing step to an AWS Glue workflow but never connects its trigger to the existing dependency chain. It is not the control for this recurring failure.
Question 943
A team applies a reviewed fix for this situation: An API payload includes optional addresses but a transformation fails when a nullable nested object is absent. Which observed outcome would most convincingly validate the fix?
- Fixtures with present, null, and missing fields receive expected values or rejects.
- A simulated transient failure recovers and persistent failures produce timely alerts.
- Peak concurrent calls stay bounded and all tasks finish without escalating throttles.
- Rebalances settle and no duplicate record creates a second downstream business event.
Explanation
Correct Answer
A:Fixtures with present, null, and missing fields receive expected values or rejects. This verifies the result of use nullable-aware extraction and document sensible default or reject handling per field.
Incorrect Answers
B:This would verify another situation: An AWS MWAA DAG has no task-level retries or SLA alerts, and a brief Glue API throttle causes a missed daily close. 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: An MSK consumer group repeatedly rebalances during long processing, causing duplicate deliveries. It does not validate the current case.
Question 944
A Lake Formation table exposes a private salary column through a broad Athena SELECT grant when an analyst needs only aggregated headcount. Select THREE complementary measures that correctly repair and validate, and prevent recurrence of this failure.
- Apply supported column-level permissions or a governed aggregate view and deny raw salary access.
- Include negative column-access tests in governed dataset onboarding.
- Configure the appropriate service-principal trust and scoped invocation policy.
- A deliberate invalid record yields actionable error metadata without raw PII.
- Mask the salary column only in one dashboard and leave raw query access open.
- The user obtains aggregate headcount without querying raw compensation fields.
Explanation
Correct Answers
A:Apply supported column-level permissions or a governed aggregate view and deny raw salary access. The underlying cause is: Data access governance does not constrain the columns needed for the approved use case.
B:Include negative column-access tests in governed dataset onboarding. This protects against the following risk: Data access governance does not constrain the columns needed for the approved use case.
F:The user obtains aggregate headcount without querying raw compensation fields. This is the observable result required before accepting the correction.
Incorrect Answers
C:That corrective action is for a different case: A Step Functions state invokes a Lambda using a role that trusts EC2 instead of the Step Functions service. It does not resolve this incident.
D:This would validate a different case: A central CloudWatch Logs group for Glue jobs retains all raw customer payloads in debug messages across many teams. It does not verify the outcome required here.
E:Mask the salary column only in one dashboard and leave raw query access open. That shortcut conflicts with the stated requirement.
Question 945
A Redshift table has highly skewed account IDs as a distribution key and one compute slice processes most rows. Which technical dependency most directly explains this behavior?
- Retention policy must not override active preservation requirements.
- Data migration alone does not resolve source/target schema and constraint differences.
- Logical key design concentrates physical write pressure.
- Join/distribution key cardinality is unsuitable for balanced data movement.
Explanation
Correct Answer
D:Join/distribution key cardinality is unsuitable for balanced data movement. The corresponding fix is to review AUTO or more distributed keys and measure skew and join plans.
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.
B:This diagnosis addresses another AWS case: An AWS DMS migration creates a new database table but foreign-key dependencies fail during cutover because schema compatibility was never rehearsed. The dependency here is different.
C:This diagnosis addresses another AWS case: A DynamoDB table uses the same partition key for all new daily events, producing throttled writes during each morning burst. The dependency here is different.
Question 946
A fraud detector needs to reread yesterday's Kinesis records but the stream uses its short default retention window. Which engineering change best addresses the underlying issue?
- Configure sufficient Kinesis retention and checkpoint offsets before the outage window expires.
- Use supported Map maximum concurrency and explicit backoff to respect provider quotas.
- Use supported synchronous integration or task token/wait-and-poll completion logic.
- Evaluate a compatible materialized view or staged aggregate with an explicit refresh policy.
Explanation
Correct Answer
A:Configure sufficient Kinesis retention and checkpoint offsets before the outage window expires. It directly addresses the case cause (The consumer's recovery period exceeds the stream's retained data duration.) and should be verified by: A replay starting at the intended timestamp retrieves the retained events.
Incorrect Answers
B:That change addresses a pipeline launches thousands of concurrent Step Functions Map tasks and saturates a small partner API; it would not repair this incident.
C:That change addresses a Step Functions pipeline sends a notification before the ETL task's asynchronous execution actually completes; it would not repair this incident.
D:That change addresses a Redshift transformation materializes a complex subquery repeatedly in one reporting workflow and exceeds its compute budget; it would not repair this incident.
Question 947
A team applies a reviewed fix for this situation: A Lake Formation-enabled S3 table is visible in Glue Data Catalog, but Athena SELECT is denied to the analyst role. Which observed outcome would most convincingly validate the fix?
- The analyst queries permitted columns while sensitive excluded fields remain inaccessible.
- A controlled bucket configuration change is detected with historical and current evidence.
- The partner accesses only intended assets and access ends when approval expires.
- An attempted unapproved replication or snapshot is blocked and logged.
Explanation
Correct Answer
A:The analyst queries permitted columns while sensitive excluded fields remain inaccessible. This verifies the result of grant scoped Lake Formation SELECT and required catalog permissions to the authorized principal.
Incorrect Answers
B:This would verify another situation: An AWS Config rule flags altered S3 encryption settings but the team uses CloudTrail alone as its continuous current-state configuration inventory. It does not validate the current case.
C: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.
D:This would verify another situation: A project migrates its authoritative EU records to another AWS Region and management assumes an S3 bucket policy alone enforces future residency. It does not validate the current case.
Question 948
A team applies a reviewed fix for this situation: A retail clickstream uses one Kinesis partition key equal to a constant and one shard is throttled while other shards idle. Which observed outcome would most convincingly validate the fix?
- A clean deployment reproduces expected resources and scoped permissions.
- The consumer selects the exact intended output without relying on a guessed path.
- Shard write throttling falls and event order within each chosen entity remains stable.
- Mixed old/new fixtures produce expected typed output or documented rejects.
Explanation
Correct Answer
C:Shard write throttling falls and event order within each chosen entity remains stable. This verifies the result of distribute records across suitable high-cardinality partition keys while preserving required per-entity ordering.
Incorrect Answers
A:This would verify another situation: A serverless pipeline deploys with hand-edited IAM and S3 settings that differ among test and production accounts. It does not validate the current case.
B: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 Glue PySpark job fails when an upstream field changes from integer to string in some JSON documents. It does not validate the current case.
Question 949
A personal-data deletion request removes a row from an Athena external table view but leaves original S3 objects and downstream extracts. Select TWO complementary measures that correctly repair and validate this failure.
- A controlled test subject is absent from eligible data products after verified deletion.
- Locate affected source and derivative assets via lineage and apply approved deletion/retention policy.
- Use an AWS Glue service role and approved short-lived credentials instead of hard-coded keys.
- Delete the Glue table description and declare all stored bytes erased.
- An ordinary BI user sees only the approved masked representation.
Explanation
Correct Answers
A:A controlled test subject is absent from eligible data products after verified deletion. This is the observable result required before accepting the correction.
B:Locate affected source and derivative assets via lineage and apply approved deletion/retention policy. The underlying cause is: Deleting catalog metadata does not erase all underlying or derived personal data.
Incorrect Answers
C:That corrective action is for a different case: A pipeline uses long-lived IAM user access keys embedded in a Glue script instead of an execution role. It does not resolve this incident.
D:Delete the Glue table description and declare all stored bytes erased. That shortcut conflicts with the stated requirement.
E: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.
Question 950
An S3-based table changes from hourly to daily partitions while old writers still publish hourly paths, giving inconsistent query results. Which engineering change best addresses the underlying issue?
- Migrate writers, metadata, and readers through a dual-read/reconciliation plan.
- Use a supported strongly consistent base-table or local-index read design where necessary.
- Align supported shared catalog integration or explicitly publish new partition metadata.
- Restrict crawler targets, table prefixes and schema-change behavior to approved locations.
Explanation
Correct Answer
A:Migrate writers, metadata, and readers through a dual-read/reconciliation plan. It directly addresses the case cause (Partition layout evolution was deployed without coordinating producers and catalog readers.) and should be verified by: A representative query returns both historical and new data exactly once.
Incorrect Answers
B: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.
C:That change addresses a Hive metastore-based EMR Spark job writes a new partition but Athena never sees it through Glue Data Catalog; it would not repair this incident.
D:That change addresses a Glue crawler crawls the entire lake for every hourly feed and adds unexpected tables from temporary staging prefixes; it would not repair this incident.
AWS Certified Data Engineer - Associate DEA-C01 Practice Tests