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 600
A team applies a reviewed fix for this situation: An Athena query uses SELECT * on a wide Parquet table, although the report needs two measures and a date. Which observed outcome would most convincingly validate the fix?
- An injected null key blocks publication and supplies a triage record.
- Scanned data falls while selected measure results match the original report.
- Report generation uses only a successful query's actual result location.
- A controlled event is consumed and appears in the authorized downstream sink.
Explanation
Correct Answer
B:Scanned data falls while selected measure results match the original report. This verifies the result of select only needed fields and apply effective partition predicates where applicable.
Incorrect Answers
A:This would verify another situation: A batch containing a required `customer_id` null value is committed to Redshift and breaks joins the next day. It does not validate the current case.
C:This would verify another situation: An Athena automated report tries to read query results immediately after StartQueryExecution returns a query ID. It does not validate the current case.
D:This would verify another situation: A Kinesis stream is receiving writes but downstream analytics remain empty after the consumer IAM role lost read permission. It does not validate the current case.
Question 601
An S3 data product has an approved seven-year retention requirement, but an engineer adds a 30-day expiration lifecycle rule. Select THREE complementary measures that correctly repair and validate, and prevent recurrence of this failure.
- Approve cleanup solely from short-term storage cost estimates.
- Compliance fixtures remain available for the required duration.
- Validate retention requirements and apply supported retention/lock controls before approving lifecycle changes.
- Invalid coordinates are rejected and valid ones support intended filters.
- Require governance signoff for expiration policy changes.
- Use staging with a reviewed MERGE or idempotent replace pattern keyed by business identity.
Explanation
Correct Answers
B:Compliance fixtures remain available for the required duration. This is the observable result required before accepting the correction.
C:Validate retention requirements and apply supported retention/lock controls before approving lifecycle changes. The underlying cause is: Object lifecycle configuration conflicts with required retention and legal policy.
E:Require governance signoff for expiration policy changes. This protects against the following risk: Object lifecycle configuration conflicts with required retention and legal policy.
Incorrect Answers
A:Approve cleanup solely from short-term storage cost estimates. That shortcut conflicts with the stated requirement.
D:This would validate a different case: A lake stores customer location coordinates as one unparsed text field while downstream joins require numeric latitude and longitude. It does not verify the outcome required here.
F:That corrective action is for a different case: A Redshift reporting pipeline accumulates duplicate business keys after retries because it appends without reconciling current versions. It does not resolve this incident.
Question 602
An S3 lake access point exists but a cross-account principal still receives AccessDenied when its IAM and bucket policies are not aligned. Which technical dependency most directly explains this behavior?
- Data sharing scope was defined too broadly for the partner's agreed dataset.
- Permission evaluation spans identity, access-point, bucket and organizational controls.
- The audit evidence store's retention does not match compliance requirements.
- Audit query coverage does not match the monitored account/Region scope.
Explanation
Correct Answer
B:Permission evaluation spans identity, access-point, bucket and organizational controls. The corresponding fix is to review the required access-point and identity/bucket permissions for the approved path.
Incorrect Answers
A:This diagnosis addresses another AWS case: A Redshift datashare exposes more tables than a partner is contractually allowed to query. The dependency here is different.
C:This diagnosis addresses another AWS case: An organization exports audit logs to S3 without lifecycle retention review and required records expire before annual audit. The dependency here is different.
D:This diagnosis addresses another AWS case: A CloudTrail Lake query lists IAM role changes but its event filter omits the Regions holding the relevant data pipelines. The dependency here is different.
Question 603
A team applies a reviewed fix for this situation: A distributed Spark process collects a large dataset to the driver and crashes from memory exhaustion. Which observed outcome would most convincingly validate the fix?
- Reports return correct current results with reduced repeated computation.
- Driver memory remains stable while full dataset results are produced.
- Join output stays correct while shuffle cost and job duration decline.
- Duplicate notifications create one committed warehouse batch and auditable duplicate attempts.
Explanation
Correct Answer
B:Driver memory remains stable while full dataset results are produced. This verifies the result of keep transformations distributed and collect only bounded diagnostic samples.
Incorrect Answers
A:This would verify another situation: A Redshift transformation materializes a complex subquery repeatedly in one reporting workflow and exceeds its compute budget. It does not validate the current case.
C:This would verify another situation: A Spark pipeline includes a wide shuffle stage because it joins on a function applied to both tables, preventing efficient key reuse. It does not validate the current case.
D:This would verify another situation: A production Glue workflow receives the same completed-file notification twice and creates two warehouse loads. It does not validate the current case.
Question 604
A team applies a reviewed fix for this situation: An EMR Spark job sends all rows for a popular customer to one reducer and fails despite plenty of idle cores. Which observed outcome would most convincingly validate the fix?
- The consumer selects the exact intended output without relying on a guessed path.
- The new deployment fails validation before production if a required parameter is missing.
- Hot-key tasks finish within acceptable time with unchanged aggregates.
- Duplicate notifications create one committed warehouse batch and auditable duplicate attempts.
Explanation
Correct Answer
C:Hot-key tasks finish within acceptable time with unchanged aggregates. This verifies the result of inspect key distribution and apply skew-aware partitioning, salting, or alternate aggregation strategy.
Incorrect Answers
A: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.
B:This would verify another situation: A code deployment changes an ETL function's parameter name but unit tests exercise only the old pipeline entry point. It does not validate the current case.
D:This would verify another situation: A production Glue workflow receives the same completed-file notification twice and creates two warehouse loads. It does not validate the current case.
Question 605
A workflow branches on a job-status string but overlooks the Cancelled terminal state, leaving executions stuck. Which engineering change best addresses the underlying issue?
- Precompute consistent normalized join keys and select suitable partitioning and join strategies.
- Evaluate a compatible materialized view or staged aggregate with an explicit refresh policy.
- Preserve currency metadata, convert only at an explicit approved rate and aggregation grain.
- Model all documented terminal statuses with success, retryable, and failure branches.
Explanation
Correct Answer
D:Model all documented terminal statuses with success, retryable, and failure branches. It directly addresses the case cause (The state machine lacks complete terminal-status handling.) and should be verified by: Injected cancelled and failed jobs exit with correctly classified outcomes.
Incorrect Answers
A:That change addresses a Spark pipeline includes a wide shuffle stage because it joins on a function applied to both tables, preventing efficient key reuse; it would not repair this incident.
B: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.
C:That change addresses a batch ETL task combines USD and EUR amounts under the same column and computes invalid totals; it would not repair this incident.
Question 606
An MWAA scheduled data DAG waits forever for an upstream batch because the external task reports completion through a different status name. Which technical dependency most directly explains this behavior?
- Events and distinct users are different measurement grains.
- The workflow's sensor condition does not match the actual upstream terminal status.
- Failure evidence is lost with ephemeral compute nodes.
- Presence checking does not enforce the field's required format contract.
Explanation
Correct Answer
B:The workflow's sensor condition does not match the actual upstream terminal status. The corresponding fix is to inspect the service response contract and update the sensor or operator success conditions.
Incorrect Answers
A:This diagnosis addresses another AWS case: A marketing report uses COUNT(*) of event records as its active user metric and overstates adoption when users retry. The dependency here is different.
C:This diagnosis addresses another AWS case: An EMR job intermittently fails due to capacity interruptions but its logs are stored only on the terminated instance. The dependency here is different.
D:This diagnosis addresses another AWS case: A Glue data quality rule checks only that an email column is nonnull but accepts invalid malformed addresses. The dependency here is different.
Question 607
A daily Python ingestion script calls S3 ListObjectsV2 only once and misses most keys after data growth. Which engineering change best addresses the underlying issue?
- Run a null/uniqueness check in Glue or SQL and quarantine failing rows or batches.
- Use the supported paginator/continuation token and durable inventory checkpoints.
- Examine iterator age, shard utilization, downstream latency and consumer parallelism.
- Inspect consumer access-denied logs and restore narrowly scoped Kinesis permissions.
Explanation
Correct Answer
B:Use the supported paginator/continuation token and durable inventory checkpoints. It directly addresses the case cause (The SDK client ignores paginated object listing.) and should be verified by: An inventory fixture beyond one page reconciles with all expected object keys.
Incorrect Answers
A:That change addresses a batch containing a required `customer_id` null value is committed to Redshift and breaks joins the next day; it would not repair this incident.
C:That change addresses a Kinesis consumer reports healthy CPU yet its IteratorAge grows for hours during normal traffic; it would not repair this incident.
D:That change addresses a Kinesis stream is receiving writes but downstream analytics remain empty after the consumer IAM role lost read permission; it would not repair this incident.
Question 608
A large historical data export shares the same small API rate limit as near-real-time orders and delays critical events. Which engineering change best addresses the underlying issue?
- Repartition data with appropriate cardinality and avoid bottlenecking single-stage operations.
- Separate ingestion capacity budgets and backpressure with appropriate queues or schedules.
- Right-size supported Lambda ephemeral storage or stream/process in bounded chunks.
- Use supported Spark SQL built-in transformations and predicate pushdown where possible.
Explanation
Correct Answer
B:Separate ingestion capacity budgets and backpressure with appropriate queues or schedules. It directly addresses the case cause (Batch and streaming clients compete without workload isolation or rate budgets.) and should be verified by: Critical orders stay within latency SLA during a backfill rehearsal.
Incorrect Answers
A:That change addresses a data transformation uses one Spark partition for a terabyte input and only one executor stays busy; it would not repair this incident.
C:That change addresses a Lambda ETL process writes temporary files larger than its configured /tmp capacity and receives storage errors; it would not repair this incident.
D:That change addresses a PySpark transformation uses Python row-by-row loops to parse simple scalar fields and runs slowly; it would not repair this incident.
Question 609
After resolving the following incident, which ongoing safeguard most directly prevents recurrence? A Glue workflow reruns yesterday's partition after a partially failed daily job but overwrites already-approved historical results.
- Use idempotent publish/rollback contracts for every scheduled batch.
- Reserve capacity and test concurrent backfill scenarios.
- Add retry/replay regression tests to API clients.
- Record source revision and artifact hash on every job run.
Explanation
Correct Answer
A:Use idempotent publish/rollback contracts for every scheduled batch. This safeguards against a recurring cause: Retry logic does not isolate staging and atomic commit boundaries.
Incorrect Answers
B:That safeguard addresses another case: A large historical data export shares the same small API rate limit as near-real-time orders and delays critical events. It is not the control for this recurring failure.
C:That safeguard addresses another case: An ingestion app writes identical DynamoDB item updates after a network retry and an audit counter increments twice. It is not the control for this recurring failure.
D:That safeguard addresses another case: A data engineering team manually changes Glue scripts on S3 without source control or a rollback identifier. It is not the control for this recurring failure.
Question 610
An Athena query reads huge raw JSON partitions for a narrow timestamp filter and scans far more bytes than expected. Which technical dependency most directly explains this behavior?
- Crawler scope is broader than the governed dataset and includes nonauthoritative paths.
- A lake table lacks effective columnar layout and pruning for its query pattern.
- Partition granularity is too fine for data volume and query predicates.
- Schema discovery crosses incompatible source populations in one catalog grouping.
Explanation
Correct Answer
B:A lake table lacks effective columnar layout and pruning for its query pattern. The corresponding fix is to use appropriately partitioned Parquet or another supported format, and verify partition predicates.
Incorrect Answers
A:This diagnosis addresses another AWS case: A Glue crawler crawls the entire lake for every hourly feed and adds unexpected tables from temporary staging prefixes. The dependency here is different.
C:This diagnosis addresses another AWS case: An Athena table uses daily partitions on a timestamp with millions of near-empty partition folders. The dependency here is different.
D:This diagnosis addresses another AWS case: A Glue crawler discovers an S3 path containing two incompatible CSV header layouts and produces a wide schema with ambiguous columns. The dependency here is different.
AWS Certified Data Engineer - Associate DEA-C01 Practice Tests