Amazon AWS Certified Data Engineer - Associate DEA-C01 Exam Dumps, Practice Test Questions

100% Latest & Updated Amazon AWS Certified Data Engineer - Associate DEA-C01 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!

Amazon AWS Certified Data Engineer - Associate DEA-C01 Premium Bundle
$79.97
$59.98

AWS Certified Data Engineer - Associate DEA-C01 Premium Bundle

  • Premium File: 366 Questions & Answers. Last update: Nov 2, 2026
  • Training Course: 273 Video Lectures
  • Study Guide: 809 Pages
  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates

AWS Certified Data Engineer - Associate DEA-C01 Premium Bundle

Amazon AWS Certified Data Engineer - Associate DEA-C01 Premium Bundle
  • Premium File: 366 Questions & Answers. Last update: Nov 2, 2026
  • Training Course: 273 Video Lectures
  • Study Guide: 809 Pages
  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates
$79.97
$59.98

Amazon AWS Certified Data Engineer - Associate DEA-C01 Practice Test 104

Question 1030

A Glue job reading nested JSON flattens arrays incorrectly and duplicates parent order totals. Which technical dependency most directly explains this behavior?

  1. Publishing events is not equivalent to having a viable incident notification path.
  2. The transformation changes record granularity without an explicit explode/join design.
  3. A retried write lacks an idempotent state transition or conditional guard.
  4. The event identity is not unique across simultaneously generated records.

Explanation

Correct Answer

B:

The transformation changes record granularity without an explicit explode/join design. The corresponding fix is to normalize arrays with stable parent identifiers and aggregate only at the intended business grain.

Incorrect Answers

A:

This diagnosis addresses another AWS case: A multi-account data pipeline sends operational alerts through an SNS topic that no engineer subscribes to. The dependency here is different.

C:

This diagnosis addresses another AWS case: An ingestion app writes identical DynamoDB item updates after a network retry and an audit counter increments twice. The dependency here is different.

D:

This diagnosis addresses another AWS case: A mobile event producer uses timestamp as the only deduplication key and collapses unrelated events recorded in one millisecond. The dependency here is different.

Question 1031

A production Glue workflow receives the same completed-file notification twice and creates two warehouse loads. Select TWO complementary measures that correctly repair and validate this failure.

  1. Pin and test dependency versions within the supported Glue runtime and publish a locked artifact.
  2. Duplicate notifications create one committed warehouse batch and auditable duplicate attempts.
  3. Assume repeated identical file notifications are impossible.
  4. Producer reconnects and publishes through broker failover without hard-coded single-host dependency.
  5. Use a stable manifest identifier with transactional state before launching or committing loads.

Explanation

Correct Answers

B:

Duplicate notifications create one committed warehouse batch and auditable duplicate attempts. This is the observable result required before accepting the correction.

E:

Use a stable manifest identifier with transactional state before launching or committing loads. The underlying cause is: Orchestration does not deduplicate at the batch commit boundary.

Incorrect Answers

A:

That corrective action is for a different case: A Glue processing library has no pinned dependency versions and a release pulls a new incompatible parser. It does not resolve this incident.

C:

Assume repeated identical file notifications are impossible. That shortcut conflicts with the stated requirement.

D:

This would validate a different case: An MSK producer succeeds only intermittently after brokers change because its connection string contains one retired broker address. It does not verify the outcome required here.

Question 1032

After resolving the following incident, which ongoing safeguard most directly prevents recurrence? An Athena query against a Lake Formation resource succeeds for the analyst, yet a separate Glue ETL role cannot read that same table.

  1. Review residency control coverage across data services after architecture changes.
  2. Maintain a workload-principal access matrix for governed datasets.
  3. Review role ownership and permissions after organizational changes.
  4. Run privacy checks on log fields and permissions.

Explanation

Correct Answer

B:

Maintain a workload-principal access matrix for governed datasets. This safeguards against a recurring cause: Lake Formation grants and role identities are evaluated per workload principal.

Incorrect Answers

A:

That safeguard addresses another case: A project migrates its authoritative EU records to another AWS Region and management assumes an S3 bucket policy alone enforces future residency. It is not the control for this recurring failure.

C:

That safeguard addresses another case: A data engineering service uses one unrestricted role for production ETL, development notebooks and reporting. It is not the control for this recurring failure.

D:

That safeguard addresses another case: A central CloudWatch Logs group for Glue jobs retains all raw customer payloads in debug messages across many teams. It is not the control for this recurring failure.

Question 1033

A Redshift datashare grants partner analysts access to a customer data mart without a purpose or term limit. Which engineering change best addresses the underlying issue?

  1. Review the required access-point and identity/bucket permissions for the approved path.
  2. Apply approved protected S3 retention, access and lifecycle safeguards for logs.
  3. Apply supported dynamic data masking or carefully governed masked views and role access.
  4. Scope shared views, roles and periodic reauthorization with a documented owner.

Explanation

Correct Answer

D:

Scope shared views, roles and periodic reauthorization with a documented owner. It directly addresses the case cause (Data sharing lifecycle does not reflect approved contractual authorization.) and should be verified by: The partner accesses only intended assets and access ends when approval expires.

Incorrect Answers

A:

That change addresses an S3 lake access point exists but a cross-account principal still receives AccessDenied when its IAM and bucket policies are not aligned; it would not repair this incident.

B:

That change addresses an organization exports audit logs to S3 without lifecycle retention review and required records expire before annual audit; 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.

Question 1034

A team applies a reviewed fix for this situation: A DynamoDB table needs lookup by email but stores only user ID and relies on full-table Scan for each login. Which observed outcome would most convincingly validate the fix?

  1. Aged test objects transition as expected while required retrieval remains possible.
  2. Email lookups avoid full scans and return authorized intended records.
  3. Representative spatial lookups return correctly without full-table scans.
  4. Consumers retain table permissions while newly published partitions appear.

Explanation

Correct Answer

B:

Email lookups avoid full scans and return authorized intended records. This verifies the result of model an appropriate secondary index with correct uniqueness and consistency expectations.

Incorrect Answers

A:

This would verify another situation: A data lake keeps years of detailed application logs in S3 Standard despite infrequent historical access and an approved 90-day hot tier. It does not validate the current case.

C:

This would verify another situation: A geospatial data catalog is placed in DynamoDB with no defined access key and engineers scan the entire table for each location. It does not validate the current case.

D:

This would verify another situation: An ETL job drops a Glue Data Catalog table and recreates it daily, deleting important tags and permissions. It does not validate the current case.

Question 1035

An ETL role invokes KMS Decrypt repeatedly, but the pipeline's incident review examines only application logs without recording AWS API actor identity. Select THREE complementary measures that correctly repair and validate, and prevent recurrence of this failure.

  1. Correlate CloudTrail and applicable KMS/service logs with job execution context.
  2. A controlled decrypt action can be attributed to the intended assumed role.
  3. Disable CloudTrail to reduce investigation noise.
  4. Grant scoped KMS decrypt through both applicable IAM and key policy controls.
  5. Link pipeline run IDs to audit role and request context.
  6. An ordinary BI user sees only the approved masked representation.

Explanation

Correct Answers

A:

Correlate CloudTrail and applicable KMS/service logs with job execution context. The underlying cause is: Operational logs omit relevant cloud audit-plane evidence.

B:

A controlled decrypt action can be attributed to the intended assumed role. This is the observable result required before accepting the correction.

E:

Link pipeline run IDs to audit role and request context. This protects against the following risk: Operational logs omit relevant cloud audit-plane evidence.

Incorrect Answers

C:

Disable CloudTrail to reduce investigation noise. That shortcut conflicts with the stated requirement.

D:

That corrective action is for a different case: A Glue job reads an S3 object encrypted with a customer-managed KMS key and fails even though it has `s3:GetObject`. It does not resolve this incident.

F:

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 1036

A lake-to-warehouse pipeline removes raw PII from visible tables but keeps an untracked temporary S3 staging prefix indefinitely. Which technical dependency most directly explains this behavior?

  1. The audit evidence store's retention does not match compliance requirements.
  2. The role trust policy does not admit the actual service principal.
  3. Audit query coverage does not match the monitored account/Region scope.
  4. Data minimization rules are not applied to every intermediate copy.

Explanation

Correct Answer

D:

Data minimization rules are not applied to every intermediate copy. The corresponding fix is to inventory staging artifacts and enforce approved secure cleanup/retention and access.

Incorrect Answers

A:

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.

B:

This diagnosis addresses another AWS case: A Step Functions state invokes a Lambda using a role that trusts EC2 instead of the Step Functions service. The dependency here is different.

C:

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 1037

An ETL job drops a Glue Data Catalog table and recreates it daily, deleting important tags and permissions. Select THREE complementary measures that correctly repair and validate, and prevent recurrence of this failure.

  1. Treat catalog identities and permissions as persistent infrastructure.
  2. Add correct scoped KMS decrypt permissions and key-policy authorization for the loading role.
  3. Update supported partitions and schema in place instead of drop-and-create.
  4. Queries return comparable relevant neighbors from a consistent model representation.
  5. Consumers retain table permissions while newly published partitions appear.
  6. Grant administrator access to every downstream reader before recreating tables.

Explanation

Correct Answers

A:

Treat catalog identities and permissions as persistent infrastructure. This protects against the following risk: Catalog recreation destroys governance metadata and stable table identity.

C:

Update supported partitions and schema in place instead of drop-and-create. The underlying cause is: Catalog recreation destroys governance metadata and stable table identity.

E:

Consumers retain table permissions while newly published partitions appear. This is the observable result required before accepting the correction.

Incorrect Answers

B:

That corrective action is for a different case: A Redshift COPY command reads encrypted S3 files but the IAM role lacks decryption permission for the customer KMS key. It does not resolve this incident.

D:

This would validate a different case: A vector retrieval index stores embeddings from two incompatible model versions in one dimension-dependent collection. It does not verify the outcome required here.

F:

Grant administrator access to every downstream reader before recreating tables. That shortcut conflicts with the stated requirement.

Question 1038

A team applies a reviewed fix for this situation: A Redshift reporting pipeline accumulates duplicate business keys after retries because it appends without reconciling current versions. Which observed outcome would most convincingly validate the fix?

  1. A conflicting schema change is rejected before the production job runs.
  2. A controlled subject deletion is absent from permitted current and derived query paths.
  3. Replaying the same batch leaves one intended current version per key.
  4. Both controlled queries return the expected published dataset version.

Explanation

Correct Answer

C:

Replaying the same batch leaves one intended current version per key. This verifies the result of use staging with a reviewed MERGE or idempotent replace pattern keyed by business identity.

Incorrect Answers

A:

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.

B:

This would verify another situation: An analytics partition must be removed under a deletion request, yet its historical copies persist in untracked S3 archive paths. It does not validate the current case.

D:

This would verify another situation: Two Athena workgroups query identically named tables but one references a different data catalog and gets old records. It does not validate the current case.

Question 1039

A Redshift COPY import fails on a changed date format in one batch even though prior files loaded. Which engineering change best addresses the underlying issue?

  1. Validate upstream schema and use appropriate supported COPY date parsing or a staging correction.
  2. Separate durable per-application checkpoints and verify replay position semantics.
  3. Set supported concurrency/batch controls and scale throughput using measured sink limits.
  4. Right-size supported Lambda ephemeral storage or stream/process in bounded chunks.

Explanation

Correct Answer

A:

Validate upstream schema and use appropriate supported COPY date parsing or a staging correction. It directly addresses the case cause (Incoming data representation no longer matches the table's expected date parsing.) and should be verified by: Valid dates load accurately and malformed rows are recorded for repair.

Incorrect Answers

B:

That change addresses two Kinesis consumers must independently recover after a deployment, but one team reuses the other's checkpoint store; it would not repair this incident.

C:

That change addresses an SQS-backed processor overwhelms a downstream database after scaling consumers without any concurrency cap; it would not repair this incident.

D:

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.

Question 1040

After resolving the following incident, which ongoing safeguard most directly prevents recurrence? A streaming producer writes compressed messages into a format the Lambda consumer assumes is plain UTF-8.

  1. Associate build artifacts with immutable source hashes.
  2. Record dimension-size thresholds and explain plans for joins.
  3. Add lifecycle checks for persistence and executor memory use.
  4. Version binary-format contracts and include golden sample fixtures.

Explanation

Correct Answer

D:

Version binary-format contracts and include golden sample fixtures. This safeguards against a recurring cause: Producer and consumer disagree on message framing and compression encoding.

Incorrect Answers

A:

That safeguard addresses another case: A SAM deployment packages an outdated Lambda handler because build artifacts from a previous branch were reused. It is not the control for this recurring failure.

B:

That safeguard addresses another case: A Glue job joins a tiny lookup table to billions of rows and performs a full distributed shuffle. It is not the control for this recurring failure.

C:

That safeguard addresses another case: An EMR Spark pipeline runs near memory limits because it caches multiple large datasets and never releases them. It is not the control for this recurring failure.

AWS Certified Data Engineer - Associate DEA-C01 Practice Tests

UP

SPECIAL OFFER: GET 10% OFF

This is ONE TIME OFFER

ExamSnap Discount Offer
Enter Your Email Address to Receive Your 10% Off Discount Code

A confirmation link will be sent to this email address to verify your login. *We value your privacy. We will not rent or sell your email address.

Download Free Demo of VCE Exam Simulator

Experience Avanset VCE Exam Simulator for yourself.

Simply submit your e-mail address below to get started with our interactive software demo of your free trial.

Free Demo Limits: In the demo version you will be able to access only first 5 questions from exam.