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 760
After resolving the following incident, which ongoing safeguard most directly prevents recurrence? A PySpark transformation uses Python row-by-row loops to parse simple scalar fields and runs slowly.
- Record end-to-end latency separately from producer acknowledgement.
- Profile costly UDFs before accepting new ETL code.
- Monitor Lambda concurrent executions and event-source lag together.
- Apply schema and timestamp quality tests at ingress.
Explanation
Correct Answer
B:Profile costly UDFs before accepting new ETL code. This safeguards against a recurring cause: Per-record interpreter overhead replaces optimized distributed expressions.
Incorrect Answers
A:That safeguard addresses another case: A Firehose pipeline is expected to deliver individual records instantly, yet it buffers batches before S3 delivery. It is not the control for this recurring failure.
C:That safeguard addresses another case: A Lambda ETL function exhausts concurrency during a flash sale, causing fresh events to be throttled. It is not the control for this recurring failure.
D:That safeguard addresses another case: A data ingestion service accepts API JSON but passes inconsistent event time zones to downstream partitions. It is not the control for this recurring failure.
Question 761
A team applies a reviewed fix for this situation: A Lake Formation table exposes a private salary column through a broad Athena SELECT grant when an analyst needs only aggregated headcount. Which observed outcome would most convincingly validate the fix?
- The user obtains aggregate headcount without querying raw compensation fields.
- An ordinary BI user sees only the approved masked representation.
- The crawler accesses the RDS schema from its actual VPC context.
- A controlled state machine execution invokes only its intended function.
Explanation
Correct Answer
A:The user obtains aggregate headcount without querying raw compensation fields. This verifies the result of apply supported column-level permissions or a governed aggregate view and deny raw salary access.
Incorrect Answers
B:This would verify another situation: A Redshift view exposes unmasked customer SSNs to a general BI role despite a requirement for partial disclosure. It does not validate the current case.
C:This would verify another situation: A Glue crawler in a VPC fails connection to a private RDS source even with the right IAM service role. It does not validate the current case.
D:This would verify another situation: A Step Functions state invokes a Lambda using a role that trusts EC2 instead of the Step Functions service. It does not validate the current case.
Question 762
A team applies a reviewed fix for this situation: A marketing report uses COUNT(*) of event records as its active user metric and overstates adoption when users retry. Which observed outcome would most convincingly validate the fix?
- A controlled workflow run invokes the added job exactly in the expected order.
- A user with several event retries contributes once to unique-user counts.
- A maximum-size sample completes with a checkpointed durable output.
- Report generation uses only a successful query's actual result location.
Explanation
Correct Answer
B:A user with several event retries contributes once to unique-user counts. This verifies the result of aggregate by validated stable user identity and the intended time-window rules.
Incorrect Answers
A:This would verify another situation: An engineer adds a new processing step to an AWS Glue workflow but never connects its trigger to the existing dependency chain. It does not validate the current case.
C:This would verify another situation: A monthly data load uses Lambda to copy hundreds of gigabytes in a single invocation and repeatedly times out. It does not validate the current case.
D: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.
Question 763
A team applies a reviewed fix for this situation: A mobile event producer uses timestamp as the only deduplication key and collapses unrelated events recorded in one millisecond. Which observed outcome would most convincingly validate the fix?
- Two distinct same-timestamp events survive, while a retried ID deduplicates.
- Hot-key tasks finish within acceptable time with unchanged aggregates.
- A forced timeout yields one authoritative committed output for the batch.
- Valid dates load accurately and malformed rows are recorded for repair.
Explanation
Correct Answer
A:Two distinct same-timestamp events survive, while a retried ID deduplicates. This verifies the result of use stable producer event IDs and appropriate per-source sequence information.
Incorrect Answers
B:This would verify another situation: An EMR Spark job sends all rows for a popular customer to one reducer and fails despite plenty of idle cores. It does not validate the current case.
C:This would verify another situation: An orchestrator invokes a Lambda that writes to S3 then times out; the retry writes a second output under a new random key. 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 764
An ETL task finishes but its success event omits the S3 prefix and schema version needed downstream. Which technical dependency most directly explains this behavior?
- Ephemeral storage is insufficient for the actual intermediate workload.
- Workflow handoff lacks a complete machine-readable output contract.
- Batch and streaming clients compete without workload isolation or rate budgets.
- Change capture cannot read required historical database logs after source retention.
Explanation
Correct Answer
B:Workflow handoff lacks a complete machine-readable output contract. The corresponding fix is to publish versioned manifest metadata containing output location, partition, checksum, and schema identity.
Incorrect Answers
A:This diagnosis addresses another AWS case: A Lambda ETL process writes temporary files larger than its configured /tmp capacity and receives storage errors. The dependency here is different.
C: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.
D:This diagnosis addresses another AWS case: A DMS CDC task finishes a full-load phase but stops capturing source table changes when the source transaction log expires. The dependency here is different.
Question 765
A fraud detector needs to reread yesterday's Kinesis records but the stream uses its short default retention window. Which technical dependency most directly explains this behavior?
- Skewed join/group keys concentrate disproportionate workload in one task.
- The consumer's recovery period exceeds the stream's retained data duration.
- Queue-consumer concurrency exceeds the sink's sustainable write capacity.
- The warehouse is storing a frequently analyzed typed attribute in an inefficient representation.
Explanation
Correct Answer
B:The consumer's recovery period exceeds the stream's retained data duration. The corresponding fix is to configure sufficient Kinesis retention and checkpoint offsets before the outage window expires.
Incorrect Answers
A:This diagnosis addresses another AWS case: An EMR Spark job sends all rows for a popular customer to one reducer and fails despite plenty of idle cores. The dependency here is different.
C:This diagnosis addresses another AWS case: An SQS-backed processor overwhelms a downstream database after scaling consumers without any concurrency cap. The dependency here is different.
D:This diagnosis addresses another AWS case: A Redshift query repeatedly casts a large timestamp string field during aggregation and consumes excess CPU. The dependency here is different.
Question 766
A Firehose pipeline is expected to deliver individual records instantly, yet it buffers batches before S3 delivery. Select TWO complementary measures that correctly repair and validate this failure.
- Run contract and integration tests on the packaged pipeline artifact with versioned parameters.
- Choose suitable supported buffering and verify whether the freshness SLA fits Firehose delivery.
- Set an unsupported zero-buffer option for a dynamically partitioned stream.
- A representative time-window report has correct results with lower CPU/runtime.
- Observed record-to-S3 latency meets the documented achievable target.
Explanation
Correct Answers
B:Choose suitable supported buffering and verify whether the freshness SLA fits Firehose delivery. The underlying cause is: Delivery buffering settings and destination behavior conflict with the required freshness.
E:Observed record-to-S3 latency meets the documented achievable target. This is the observable result required before accepting the correction.
Incorrect Answers
A:That corrective action is for a different case: A code deployment changes an ETL function's parameter name but unit tests exercise only the old pipeline entry point. It does not resolve this incident.
C:Set an unsupported zero-buffer option for a dynamically partitioned stream. That shortcut conflicts with the stated requirement.
D:This would validate a different case: A Redshift query repeatedly casts a large timestamp string field during aggregation and consumes excess CPU. It does not verify the outcome required here.
Question 767
A Step Functions state invokes a Lambda using a role that trusts EC2 instead of the Step Functions service. Which technical dependency most directly explains this behavior?
- Audit query coverage does not match the monitored account/Region scope.
- Data sharing lifecycle does not reflect approved contractual authorization.
- The role trust policy does not admit the actual service principal.
- Business catalog sharing lacks stewardship and usage-governance metadata.
Explanation
Correct Answer
C:The role trust policy does not admit the actual service principal. The corresponding fix is to configure the appropriate service-principal trust and scoped invocation policy.
Incorrect Answers
A: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.
B:This diagnosis addresses another AWS case: A Redshift datashare grants partner analysts access to a customer data mart without a purpose or term limit. The dependency here is different.
D:This diagnosis addresses another AWS case: A SageMaker Catalog project shares a data product broadly across teams without recording owner and allowed purpose. The dependency here is different.
Question 768
An MWAA DAG was deployed but its Python import fails, so no scheduled run appears. Select THREE complementary measures that correctly repair and validate, and prevent recurrence of this failure.
- Inspect DAG import errors and validate packaging dependencies before deployment.
- Create cron triggers against a DAG that the scheduler cannot load.
- Configure appropriate reserved/provisioned concurrency and buffer events to match sustainable throughput.
- The loader processes the complete expected byte count and checksum only once.
- Require DAG import and syntax checks in CI.
- The DAG parses and a controlled run completes its expected task graph.
Explanation
Correct Answers
A:Inspect DAG import errors and validate packaging dependencies before deployment. The underlying cause is: The scheduler cannot parse the DAG file and therefore cannot schedule its tasks.
E:Require DAG import and syntax checks in CI. This protects against the following risk: The scheduler cannot parse the DAG file and therefore cannot schedule its tasks.
F:The DAG parses and a controlled run completes its expected task graph. This is the observable result required before accepting the correction.
Incorrect Answers
B:Create cron triggers against a DAG that the scheduler cannot load. That shortcut conflicts with the stated requirement.
C:That corrective action is for a different case: A Lambda ETL function exhausts concurrency during a flash sale, causing fresh events to be throttled. It does not resolve this incident.
D:This would validate a different case: A partner uploads a CSV over SFTP to Transfer Family but a load starts before the file finishes writing. It does not verify the outcome required here.
Question 769
An MSK consumer group repeatedly rebalances during long processing, causing duplicate deliveries. Which engineering change best addresses the underlying issue?
- Apply an explicit compatible schema or deliberate conversion and quarantine unparseable values.
- Write to a versioned staging output and promote only a complete validated partition.
- Tune consumption, heartbeat/poll behavior, batch sizes and idempotent processing to the workload.
- Use an appropriate hashed lookup structure while preserving deterministic output behavior.
Explanation
Correct Answer
C:Tune consumption, heartbeat/poll behavior, batch sizes and idempotent processing to the workload. It directly addresses the case cause (Processing exceeds configured consumer poll or session expectations without adequate checkpoint strategy.) and should be verified by: Rebalances settle and no duplicate record creates a second downstream business event.
Incorrect Answers
A:That change addresses a Glue PySpark job fails when an upstream field changes from integer to string in some JSON documents; it would not repair this incident.
B:That change addresses a Glue workflow reruns yesterday's partition after a partially failed daily job but overwrites already-approved historical results; it would not repair this incident.
D:That change addresses a large ETL data structure uses a list for repeated membership checks and CPU use grows unexpectedly; it would not repair this incident.
Question 770
A data engineering service uses one unrestricted role for production ETL, development notebooks and reporting. Which engineering change best addresses the underlying issue?
- Apply approved tokenization, masking, or projection before data exits the trusted boundary.
- Scope KMS actions to intended keys and add appropriate conditions where supported.
- Apply supported dynamic data masking or carefully governed masked views and role access.
- Separate service roles and policies by environment, workload and required resources.
Explanation
Correct Answer
D:Separate service roles and policies by environment, workload and required resources. It directly addresses the case cause (Shared broadly privileged identities obscure duties and violate least privilege.) and should be verified by: Development cannot write production data while ETL still runs correctly.
Incorrect Answers
A:That change addresses a DynamoDB-backed application needs to redact sensitive values before exporting analytics but relies only on table encryption; it would not repair this incident.
B:That change addresses a Glue data job decrypts source objects using a wildcard KMS permission spanning unrelated client keys; it would not repair this incident.
C:That change addresses a Redshift view exposes unmasked customer SSNs to a general BI role despite a requirement for partial disclosure; it would not repair this incident.
AWS Certified Data Engineer - Associate DEA-C01 Practice Tests