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 300
An S3 data-access investigation searches CloudTrail for object reads but only management events were enabled. Which engineering change best addresses the underlying issue?
- Configure the intended Lambda execution role with scoped API permissions.
- Assign supported domain/project membership and dataset entitlements through reviewed workflows.
- Grant scoped Lake Formation SELECT and required catalog permissions to the authorized principal.
- Enable reviewed CloudTrail data events for the required S3 buckets or prefixes.
Explanation
Correct Answer
D:Enable reviewed CloudTrail data events for the required S3 buckets or prefixes. It directly addresses the case cause (Object-level S3 reads require appropriate data-event collection scope.) and should be verified by: A controlled object read produces a traceable data event with expected context.
Incorrect Answers
A:That change addresses a Lambda data extractor assumes an EC2 instance profile is available when running as a Lambda function; it would not repair this incident.
B:That change addresses 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; it would not repair this incident.
C:That change addresses a Lake Formation-enabled S3 table is visible in Glue Data Catalog, but Athena SELECT is denied to the analyst role; it would not repair this incident.
Question 301
After resolving the following incident, which ongoing safeguard most directly prevents recurrence? A retail clickstream uses one Kinesis partition key equal to a constant and one shard is throttled while other shards idle.
- Test representative key distributions and monitor per-shard metrics during releases.
- Profile costly UDFs before accepting new ETL code.
- Benchmark representative column-selective queries before format standardization.
- Use idempotent publish/rollback contracts for every scheduled batch.
Explanation
Correct Answer
A:Test representative key distributions and monitor per-shard metrics during releases. This safeguards against a recurring cause: A fixed partition key concentrates writes on one hash range.
Incorrect Answers
B:That safeguard addresses another case: A PySpark transformation uses Python row-by-row loops to parse simple scalar fields and runs slowly. It is not the control for this recurring failure.
C:That safeguard addresses another case: An ETL job writes CSV to a large analytics lake and Athena scans every column for two-field reports. It is not the control for this recurring failure.
D:That safeguard addresses another case: A Glue workflow reruns yesterday's partition after a partially failed daily job but overwrites already-approved historical results. It is not the control for this recurring failure.
Question 302
An EventBridge schedule was configured in one Region but the receiving Step Functions state machine lives in another without a reviewed target design. Which technical dependency most directly explains this behavior?
- Pipeline retry handling and final quality checks do not preserve all expected groups.
- The sample is too small or unrepresentative for a claimed whole-population guarantee.
- The schedule target's Region, ARN, role, or cross-account authorization is misconfigured.
- The pipeline lacks stable event-level uniqueness validation.
Explanation
Correct Answer
C:The schedule target's Region, ARN, role, or cross-account authorization is misconfigured. The corresponding fix is to validate supported cross-Region target patterns and scoped invocation permissions.
Incorrect Answers
A:This diagnosis addresses another AWS case: A Spark aggregation produces incorrect category totals because one hot key is dropped after a task retry and the target doesn't reconcile. The dependency here is different.
B:This diagnosis addresses another AWS case: A streaming pipeline evaluates quality from a random sample of 10 messages and assumes it proves a million-row batch is correct. The dependency here is different.
D:This diagnosis addresses another AWS case: A daily sensor batch is duplicated after retry, causing every aggregate event count to double. The dependency here is different.
Question 303
A daily Python ingestion script calls S3 ListObjectsV2 only once and misses most keys after data growth. Which technical dependency most directly explains this behavior?
- The SDK client ignores paginated object listing.
- The join excludes the population that must remain in the denominator.
- A display label is not a stable relational join key.
- The workflow's success criteria omit an operationally required delivery dependency.
Explanation
Correct Answer
A:The SDK client ignores paginated object listing. The corresponding fix is to use the supported paginator/continuation token and durable inventory checkpoints.
Incorrect Answers
B:This diagnosis addresses another AWS case: An Athena view compares monthly cohorts using an inner join that drops customers with no activity, overstating retention. The dependency here is different.
C:This diagnosis addresses another AWS case: A Redshift SQL view joins two tables on customer name, and a same-name collision merges unrelated accounts. The dependency here is different.
D:This diagnosis addresses another AWS case: A Step Functions run is marked succeeded although a downstream notification publish fails and no incident ticket is opened. The dependency here is different.
Question 304
An ETL task finishes but its success event omits the S3 prefix and schema version needed downstream. Select THREE complementary measures that correctly repair and validate, and prevent recurrence of this failure.
- Limit partitioned reads and schedule extraction within source performance budgets.
- Derive the output prefix from the current wall-clock date alone.
- Publish versioned manifest metadata containing output location, partition, checksum, and schema identity.
- Schema-check workflow handoffs and reject incomplete manifests.
- Two distinct same-timestamp events survive, while a retried ID deduplicates.
- The consumer selects the exact intended output without relying on a guessed path.
Explanation
Correct Answers
C:Publish versioned manifest metadata containing output location, partition, checksum, and schema identity. The underlying cause is: Workflow handoff lacks a complete machine-readable output contract.
D:Schema-check workflow handoffs and reject incomplete manifests. This protects against the following risk: Workflow handoff lacks a complete machine-readable output contract.
F:The consumer selects the exact intended output without relying on a guessed path. This is the observable result required before accepting the correction.
Incorrect Answers
A:That corrective action is for a different case: A Glue JDBC extraction overloads a small OLTP database when hundreds of partitions open simultaneous connections. It does not resolve this incident.
B:Derive the output prefix from the current wall-clock date alone. That shortcut conflicts with the stated requirement.
E:This would validate a different case: A mobile event producer uses timestamp as the only deduplication key and collapses unrelated events recorded in one millisecond. It does not verify the outcome required here.
Question 305
A CloudTrail Lake query lists IAM role changes but its event filter omits the Regions holding the relevant data pipelines. Which engineering change best addresses the underlying issue?
- Confirm event data store selectors and query filters include intended account and Region events.
- Restrict authorized shared schema/object grants and verify consumer access.
- Narrow LF-Tag permissions to reviewed principals and classify data assets consistently.
- Grant explicit least-privilege permissions to the Glue execution role and verify the data access path.
Explanation
Correct Answer
A:Confirm event data store selectors and query filters include intended account and Region events. It directly addresses the case cause (Audit query coverage does not match the monitored account/Region scope.) and should be verified by: A synthetic approved role change in a test Region is queryable by the auditor.
Incorrect Answers
B:That change addresses a Redshift datashare exposes more tables than a partner is contractually allowed to query; it would not repair this incident.
C:That change addresses an S3 table is tagged `classification=restricted`, but its Lake Formation LF-Tag grant allows a broad organizational unit with no business need; it would not repair this incident.
D:That change addresses an Athena query against a Lake Formation resource succeeds for the analyst, yet a separate Glue ETL role cannot read that same table; it would not repair this incident.
Question 306
A team applies a reviewed fix for this situation: An Athena SQL query sums decimal prices stored as strings and uses lexicographic ordering on text. Which observed outcome would most convincingly validate the fix?
- The report matches known numeric test totals and identifies malformed values.
- A repeated batch does not change the accepted distinct event count.
- A controlled scheduled event starts the intended execution once.
- A terminated cluster's step and executor logs remain available for diagnosis.
Explanation
Correct Answer
A:The report matches known numeric test totals and identifies malformed values. This verifies the result of convert to validated decimal types upstream or with explicit safe casts before aggregation.
Incorrect Answers
B:This would verify another situation: A daily sensor batch is duplicated after retry, causing every aggregate event count to double. It does not validate the current case.
C:This would verify another situation: An EventBridge schedule was configured in one Region but the receiving Step Functions state machine lives in another without a reviewed target design. It does not validate the current case.
D:This would verify another situation: An EMR job intermittently fails due to capacity interruptions but its logs are stored only on the terminated instance. It does not validate the current case.
Question 307
A team applies a reviewed fix for this situation: A data ingestion service accepts API JSON but passes inconsistent event time zones to downstream partitions. Which observed outcome would most convincingly validate the fix?
- Cross-region events land in the correct expected hourly event-time partitions.
- Replica or source CPU stays bounded while expected rows are extracted.
- A fixture with two nested lines produces correct line and order totals.
- Join output stays correct while shuffle cost and job duration decline.
Explanation
Correct Answer
A:Cross-region events land in the correct expected hourly event-time partitions. This verifies the result of validate timestamp offsets and write a canonical UTC event-time field while retaining the source timestamp.
Incorrect Answers
B:This would verify another situation: A Glue JDBC extraction overloads a small OLTP database when hundreds of partitions open simultaneous connections. It does not validate the current case.
C:This would verify another situation: A Glue job reading nested JSON flattens arrays incorrectly and duplicates parent order totals. It does not validate the current case.
D: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.
Question 308
A Lambda ETL process writes temporary files larger than its configured /tmp capacity and receives storage errors. Select TWO complementary measures that correctly repair and validate this failure.
- Return correctly structured transformed records and audit failure routing.
- Shard write throttling falls and event order within each chosen entity remains stable.
- A maximum-size fixture completes without filling local temporary storage.
- Right-size supported Lambda ephemeral storage or stream/process in bounded chunks.
- Move temporary files into the function deployment package.
Explanation
Correct Answers
C:A maximum-size fixture completes without filling local temporary storage. This is the observable result required before accepting the correction.
D:Right-size supported Lambda ephemeral storage or stream/process in bounded chunks. The underlying cause is: Ephemeral storage is insufficient for the actual intermediate workload.
Incorrect Answers
A:That corrective action is for a different case: A Firehose transformation Lambda returns malformed record status envelopes and some messages enter an error prefix. It does not resolve this incident.
B:This would validate a different case: A retail clickstream uses one Kinesis partition key equal to a constant and one shard is throttled while other shards idle. It does not verify the outcome required here.
E:Move temporary files into the function deployment package. That shortcut conflicts with the stated requirement.
Question 309
A team applies a reviewed fix for this situation: A Redshift query repeatedly casts a large timestamp string field during aggregation and consumes excess CPU. Which observed outcome would most convincingly validate the fix?
- A representative time-window report has correct results with lower CPU/runtime.
- Replayed identical events create one accepted workflow while independent batches proceed.
- Rebalances settle and no duplicate record creates a second downstream business event.
- A simulated transient failure recovers and persistent failures produce timely alerts.
Explanation
Correct Answer
A:A representative time-window report has correct results with lower CPU/runtime. This verifies the result of normalize timestamp types during ingestion and optimize the relevant table layout.
Incorrect Answers
B:This would verify another situation: An EventBridge rule matches both replayed and new events and starts two identical pipelines for the same batch. It does not validate the current case.
C:This would verify another situation: An MSK consumer group repeatedly rebalances during long processing, causing duplicate deliveries. It does not validate the current case.
D: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.
Question 310
A mobile event producer uses timestamp as the only deduplication key and collapses unrelated events recorded in one millisecond. Which technical dependency most directly explains this behavior?
- The event identity is not unique across simultaneously generated records.
- Retries use non-idempotent output identity with uncertain prior completion.
- The processing layout prevents distributed parallelism.
- Row-based text storage undermines predicate and column projection efficiencies.
Explanation
Correct Answer
A:The event identity is not unique across simultaneously generated records. The corresponding fix is to use stable producer event IDs and appropriate per-source sequence information.
Incorrect Answers
B:This diagnosis addresses another AWS case: An orchestrator invokes a Lambda that writes to S3 then times out; the retry writes a second output under a new random key. The dependency here is different.
C:This diagnosis addresses another AWS case: A data transformation uses one Spark partition for a terabyte input and only one executor stays busy. The dependency here is different.
D:This diagnosis addresses another AWS case: An ETL job writes CSV to a large analytics lake and Athena scans every column for two-field reports. The dependency here is different.
AWS Certified Data Engineer - Associate DEA-C01 Practice Tests