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 520
An S3 event notification triggers Glue for every file of a large export, producing hundreds of competing jobs. Which engineering change best addresses the underlying issue?
- Use supported synchronous integration or task token/wait-and-poll completion logic.
- Aggregate object events or publish a manifest/ready signal and start bounded ETL batches.
- Normalize timestamp types during ingestion and optimize the relevant table layout.
- Inspect DAG import errors and validate packaging dependencies before deployment.
Explanation
Correct Answer
B:Aggregate object events or publish a manifest/ready signal and start bounded ETL batches. It directly addresses the case cause (The event-to-job design starts a run per object without a batch completion boundary.) and should be verified by: One controlled export yields the intended bounded job count and all objects are processed.
Incorrect Answers
A: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.
C:That change addresses a Redshift query repeatedly casts a large timestamp string field during aggregation and consumes excess CPU; it would not repair this incident.
D:That change addresses an MWAA DAG was deployed but its Python import fails, so no scheduled run appears; it would not repair this incident.
Question 521
A team applies a reviewed fix for this situation: A scheduled ETL uses an API token embedded in source code; rotation breaks the batch without an alert. Which observed outcome would most convincingly validate the fix?
- Execution plan and runtime return within accepted bounds with identical answers.
- Consumer lag decreases under a measured production-like load.
- A forced retry produces totals matching an independent known fixture.
- A test rotation preserves authorized API access without redeploying embedded credentials.
Explanation
Correct Answer
D:A test rotation preserves authorized API access without redeploying embedded credentials. This verifies the result of move credentials to a protected managed secret and implement controlled refresh and failure alerts.
Incorrect Answers
A:This would verify another situation: A Redshift reporting job suddenly spends time redistributing a large fact table after a schema change. It does not validate the current case.
B:This would verify another situation: A Kinesis consumer reports healthy CPU yet its IteratorAge grows for hours during normal traffic. It does not validate the current case.
C:This would verify another situation: A Spark aggregation produces incorrect category totals because one hot key is dropped after a task retry and the target doesn't reconcile. It does not validate the current case.
Question 522
A Redshift datashare exposes more tables than a partner is contractually allowed to query. Select THREE complementary measures that correctly repair and validate, and prevent recurrence of this failure.
- Reconcile datashare permissions against the sharing agreement each release.
- The partner can query intended views without accessing unrelated source objects.
- The user obtains aggregate headcount without querying raw compensation fields.
- Apply account/organization guardrails, regional resource rules and audited exception processes.
- Give the external consumer unrestricted access to every database.
- Restrict authorized shared schema/object grants and verify consumer access.
Explanation
Correct Answers
A:Reconcile datashare permissions against the sharing agreement each release. This protects against the following risk: Data sharing scope was defined too broadly for the partner's agreed dataset.
B:The partner can query intended views without accessing unrelated source objects. This is the observable result required before accepting the correction.
F:Restrict authorized shared schema/object grants and verify consumer access. The underlying cause is: Data sharing scope was defined too broadly for the partner's agreed dataset.
Incorrect Answers
C:This would validate a different case: A Lake Formation table exposes a private salary column through a broad Athena SELECT grant when an analyst needs only aggregated headcount. It does not verify the outcome required here.
D:That corrective action is for a different case: 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 resolve this incident.
E:Give the external consumer unrestricted access to every database. That shortcut conflicts with the stated requirement.
Question 523
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. Select THREE complementary measures that correctly repair and validate, and prevent recurrence of this failure.
- Assign supported domain/project membership and dataset entitlements through reviewed workflows.
- Test project access with allowed and denied member fixtures.
- Define and grant a read-only database role on approved schemas and views.
- A nominated team member can access only the project assets approved for the role.
- A sample output meets organizational reidentification risk requirements.
- Grant all account users global data administrator privileges.
Explanation
Correct Answers
A:Assign supported domain/project membership and dataset entitlements through reviewed workflows. The underlying cause is: Studio domain/project membership and resource governance are separate access contexts.
B:Test project access with allowed and denied member fixtures. This protects against the following risk: Studio domain/project membership and resource governance are separate access contexts.
D:A nominated team member can access only the project assets approved for the role. This is the observable result required before accepting the correction.
Incorrect Answers
C:That corrective action is for a different case: A Redshift data analyst has a role granting broad schema CREATE and DROP despite requiring only SELECT on a few views. It does not resolve this incident.
E:This would validate a different case: A tokenization pipeline uses a deterministic unkeyed hash on low-entropy postal identifiers and calls them irreversibly anonymous. It does not verify the outcome required here.
F:Grant all account users global data administrator privileges. That shortcut conflicts with the stated requirement.
Question 524
A feed arrives with 30% fewer rows than normal, but a transformation succeeds and marks the data product complete. Which engineering change best addresses the underlying issue?
- Check expected row counts against source manifest and tolerances before release.
- Convert to validated decimal types upstream or with explicit safe casts before aggregation.
- Profile physical plans and remove unintended cross joins or use reviewed predicates.
- Join on documented unique customer identifiers and enforce suitable grain.
Explanation
Correct Answer
A:Check expected row counts against source manifest and tolerances before release. It directly addresses the case cause (Runtime success is not equivalent to expected source completeness.) and should be verified by: A deliberately truncated file triggers a quality alert and prevents false success.
Incorrect Answers
B:That change addresses an Athena SQL query sums decimal prices stored as strings and uses lexicographic ordering on text; it would not repair this incident.
C:That change addresses a Glue job begins consuming twice its normal DPU budget after a transformation adds a repeated cross join; it would not repair this incident.
D:That change addresses a Redshift SQL view joins two tables on customer name, and a same-name collision merges unrelated accounts; it would not repair this incident.
Question 525
An MWAA scheduled data DAG waits forever for an upstream batch because the external task reports completion through a different status name. Select TWO complementary measures that correctly repair and validate this failure.
- A completed upstream fixture unblocks the DAG while failures follow the error path.
- Inspect the service response contract and update the sensor or operator success conditions.
- Check expected row counts against source manifest and tolerances before release.
- Mark every unknown task state as success to clear the backlog.
- An injected null key blocks publication and supplies a triage record.
Explanation
Correct Answers
A:A completed upstream fixture unblocks the DAG while failures follow the error path. This is the observable result required before accepting the correction.
B:Inspect the service response contract and update the sensor or operator success conditions. The underlying cause is: The workflow's sensor condition does not match the actual upstream terminal status.
Incorrect Answers
C:That corrective action is for a different case: A feed arrives with 30% fewer rows than normal, but a transformation succeeds and marks the data product complete. It does not resolve this incident.
D:Mark every unknown task state as success to clear the backlog. That shortcut conflicts with the stated requirement.
E:This would validate a different case: A batch containing a required `customer_id` null value is committed to Redshift and breaks joins the next day. It does not verify the outcome required here.
Question 526
A team applies a reviewed fix for this situation: A DynamoDB-backed application needs to redact sensitive values before exporting analytics but relies only on table encryption. Which observed outcome would most convincingly validate the fix?
- Controlled events from the missing day are queryable after catalog correction.
- A controlled decrypt action can be attributed to the intended assumed role.
- The partner can query intended views without accessing unrelated source objects.
- A test export contains permitted pseudonyms and omits restricted raw fields.
Explanation
Correct Answer
D:A test export contains permitted pseudonyms and omits restricted raw fields. This verifies the result of apply approved tokenization, masking, or projection before data exits the trusted boundary.
Incorrect Answers
A:This would verify another situation: An Athena query for CloudTrail logs shows a missing day because the log data lake partitions were never registered. It does not validate the current case.
B:This would verify another situation: An ETL role invokes KMS Decrypt repeatedly, but the pipeline's incident review examines only application logs without recording AWS API actor identity. It does not validate the current case.
C:This would verify another situation: A Redshift datashare exposes more tables than a partner is contractually allowed to query. It does not validate the current case.
Question 527
A team applies a reviewed fix for this situation: A customer expects fast key-value reads over frequently accessed session state yet stores every session in a multi-megabyte compressed S3 archive. Which observed outcome would most convincingly validate the fix?
- Expired sessions are denied immediately even if the physical item persists briefly.
- Session lookups meet the accepted p95 target without unnecessary archive reads.
- A conflicting schema change is rejected before the production job runs.
- Archive row counts and key sets reconcile with the source snapshot.
Explanation
Correct Answer
B:Session lookups meet the accepted p95 target without unnecessary archive reads. This verifies the result of separate hot operational state from archival S3 objects using a measured suitable database/cache.
Incorrect Answers
A:This would verify another situation: A DynamoDB table contains session records with expired timestamps but items remain visible immediately after expiry. It does not validate the current case.
C:This would verify another situation: Two developers independently edit Glue Data Catalog schema types during release, and a job fails after the last writer wins. It does not validate the current case.
D:This would verify another situation: A DynamoDB archival pipeline uses Scan without pagination and misses records beyond the first page. It does not validate the current case.
Question 528
A DMS CDC task finishes a full-load phase but stops capturing source table changes when the source transaction log expires. Which engineering change best addresses the underlying issue?
- Evaluate a broadcast join or other optimized join strategy within Glue/Spark memory limits.
- Retry bounded transient exceptions and catch permanent validation failures for quarantine.
- Choose a stable order identity and the correct aggregation or distinct-current-state logic.
- Align source transaction-log retention, DMS checkpoints, and CDC task health with the recovery objective.
Explanation
Correct Answer
D:Align source transaction-log retention, DMS checkpoints, and CDC task health with the recovery objective. It directly addresses the case cause (Change capture cannot read required historical database logs after source retention.) and should be verified by: A source insert or update reaches the target after an interruption and restart.
Incorrect Answers
A:That change addresses a Glue job joins a tiny lookup table to billions of rows and performs a full distributed shuffle; it would not repair this incident.
B:That change addresses a Step Functions state retries every failure including invalid schema, consuming budget without possibility of success; it would not repair this incident.
C:That change addresses a nightly aggregation counts an order once per status-change event rather than once per order ID; it would not repair this incident.
Question 529
A multi-account data pipeline sends operational alerts through an SNS topic that no engineer subscribes to. Which technical dependency most directly explains this behavior?
- Network routing or security groups block the ETL job's actual source path.
- Input compression settings do not match the actual object encoding.
- Infrastructure drift makes deployments non-repeatable.
- Publishing events is not equivalent to having a viable incident notification path.
Explanation
Correct Answer
D:Publishing events is not equivalent to having a viable incident notification path. The corresponding fix is to configure validated subscriptions, policies and controlled test notifications.
Incorrect Answers
A:This diagnosis addresses another AWS case: A Glue connection to a source RDS database times out, although the JDBC credentials are valid. The dependency here is different.
B:This diagnosis addresses another AWS case: A processing job ingests gzipped files but its connector treats their contents as uncompressed text and creates corrupt rows. The dependency here is different.
C:This diagnosis addresses another AWS case: A serverless pipeline deploys with hand-edited IAM and S3 settings that differ among test and production accounts. The dependency here is different.
Question 530
A team changes an analytics library but releases a job without checking distributed task serialization compatibility. Select TWO complementary measures that correctly repair and validate this failure.
- Distribute records across suitable high-cardinality partition keys while preserving required per-entity ordering.
- Assume local notebook imports prove distributed cluster compatibility.
- Run end-to-end tests on the actual Glue/EMR executor runtime and compatible libraries.
- The published job serializes work to executors and produces correct output.
- Replayed identical events create one accepted workflow while independent batches proceed.
Explanation
Correct Answers
C:Run end-to-end tests on the actual Glue/EMR executor runtime and compatible libraries. The underlying cause is: Developer tests omit execution-context serialization and worker runtime dependencies.
D:The published job serializes work to executors and produces correct output. This is the observable result required before accepting the correction.
Incorrect Answers
A:That corrective action is for 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 resolve this incident.
B:Assume local notebook imports prove distributed cluster compatibility. That shortcut conflicts with the stated requirement.
E:This would validate a different case: An EventBridge rule matches both replayed and new events and starts two identical pipelines for the same batch. It does not verify the outcome required here.
AWS Certified Data Engineer - Associate DEA-C01 Practice Tests