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 120
After resolving the following incident, which ongoing safeguard most directly prevents recurrence? A partner API returns HTTP 429, and a Glue ETL job immediately retries in tight loops until access is suspended.
- Monitor retry budgets and throttle rates per partner.
- Run schema/format contract tests before warehouse loading.
- Require test execution against deployable artifacts, not only helper functions.
- Check service response enums when revising orchestration logic.
Explanation
Correct Answer
A:Monitor retry budgets and throttle rates per partner. This safeguards against a recurring cause: Retry policy ignores rate limiting and server retry hints.
Incorrect Answers
B:That safeguard addresses another case: A Redshift COPY import fails on a changed date format in one batch even though prior files loaded. It is not the control for this recurring failure.
C:That safeguard addresses another case: A code deployment changes an ETL function's parameter name but unit tests exercise only the old pipeline entry point. It is not the control for this recurring failure.
D:That safeguard addresses another case: A workflow branches on a job-status string but overlooks the Cancelled terminal state, leaving executions stuck. It is not the control for this recurring failure.
Question 121
A team applies a reviewed fix for this situation: An ETL task finishes but its success event omits the S3 prefix and schema version needed downstream. Which observed outcome would most convincingly validate the fix?
- The consumer selects the exact intended output without relying on a guessed path.
- Shard write throttling falls and event order within each chosen entity remains stable.
- The deployed function identifies the intended release and completes a fixture invocation.
- Mixed old/new fixtures produce expected typed output or documented rejects.
Explanation
Correct Answer
A:The consumer selects the exact intended output without relying on a guessed path. This verifies the result of publish versioned manifest metadata containing output location, partition, checksum, and schema identity.
Incorrect Answers
B:This would verify another situation: A retail clickstream uses one Kinesis partition key equal to a constant and one shard is throttled while other shards idle. It does not validate the current case.
C:This would verify another situation: A SAM deployment packages an outdated Lambda handler because build artifacts from a previous branch were reused. It does not validate the current case.
D:This would verify another situation: A Glue PySpark job fails when an upstream field changes from integer to string in some JSON documents. It does not validate the current case.
Question 122
A Redshift COPY command reads encrypted S3 files but the IAM role lacks decryption permission for the customer KMS key. Select THREE complementary measures that correctly repair and validate, and prevent recurrence of this failure.
- A test encrypted file loads, while unrelated key access remains denied.
- Network redistribution and join latency improve with unchanged outputs.
- Include KMS access in data-load integration tests.
- Apply a stable catalog schema and quarantine malformed headers or records upstream.
- Remove encryption from the entire data lake to make COPY work.
- Add correct scoped KMS decrypt permissions and key-policy authorization for the loading role.
Explanation
Correct Answers
A:A test encrypted file loads, while unrelated key access remains denied. This is the observable result required before accepting the correction.
C:Include KMS access in data-load integration tests. This protects against the following risk: Storage read authorization does not supply the required cryptographic key access.
F:Add correct scoped KMS decrypt permissions and key-policy authorization for the loading role. The underlying cause is: Storage read authorization does not supply the required cryptographic key access.
Incorrect Answers
B:This would validate a different case: A small dimension table joins huge Redshift facts, but an unnecessarily EVEN distribution causes repeated data transfer. It does not verify the outcome required here.
D:That corrective action is for a different case: A crawler changes a decimal sales column to string after encountering a nonnumeric banner row in one export. It does not resolve this incident.
E:Remove encryption from the entire data lake to make COPY work. That shortcut conflicts with the stated requirement.
Question 123
An S3 export writes regulated data to an unencrypted partner endpoint despite source-at-rest SSE-KMS protection. Which technical dependency most directly explains this behavior?
- Shared broadly privileged identities obscure duties and violate least privilege.
- Data sharing lifecycle does not reflect approved contractual authorization.
- Database privilege scope exceeds the analyst's reporting purpose.
- At-rest encryption does not secure data transmission on an external path.
Explanation
Correct Answer
D:At-rest encryption does not secure data transmission on an external path. The corresponding fix is to require supported TLS transport and approved destination identity/key handling.
Incorrect Answers
A:This diagnosis addresses another AWS case: A data engineering service uses one unrestricted role for production ETL, development notebooks and reporting. 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.
C:This diagnosis addresses another AWS case: A Redshift data analyst has a role granting broad schema CREATE and DROP despite requiring only SELECT on a few views. The dependency here is different.
Question 124
A team applies a reviewed fix for this situation: A data engineering team manually changes Glue scripts on S3 without source control or a rollback identifier. Which observed outcome would most convincingly validate the fix?
- A forced mid-run failure leaves the previous published partition available.
- A failed release can restore the prior script and reproduce its output.
- Valid dates load accurately and malformed rows are recorded for repair.
- Notifications fire only after the transform reaches a recorded successful terminal state.
Explanation
Correct Answer
B:A failed release can restore the prior script and reproduce its output. This verifies the result of commit source and deploy immutable versioned scripts through a controlled pipeline.
Incorrect Answers
A:This would verify another situation: A Glue workflow reruns yesterday's partition after a partially failed daily job but overwrites already-approved historical results. It does not validate the current case.
C: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.
D:This would verify another situation: A Step Functions pipeline sends a notification before the ETL task's asynchronous execution actually completes. It does not validate the current case.
Question 125
After resolving the following incident, which ongoing safeguard most directly prevents recurrence? A lake dataset adds an optional JSON field and an older consumer fails because it expects an exact fixed set of keys.
- Benchmark the required access patterns before choosing a data store.
- Audit catalog lifecycle on organizational changes.
- Define backward/forward compatibility rules before source rollout.
- Review business classification and glossary terms during onboarding.
Explanation
Correct Answer
C:Define backward/forward compatibility rules before source rollout. This safeguards against a recurring cause: Schema evolution is treated as a breaking change despite an optional additive field.
Incorrect Answers
A:That safeguard addresses another case: An online session store uses S3 object listing as a low-latency millisecond key lookup service and response times are erratic. It is not the control for this recurring failure.
B:That safeguard addresses another case: A SageMaker Catalog project references a dataset whose owner changed but permissions and business definitions still point to the former team. It is not the control for this recurring failure.
D:That safeguard addresses another case: An analytics team relies on Glue technical table names to determine which datasets are permitted for finance reporting. It is not the control for this recurring failure.
Question 126
After resolving the following incident, which ongoing safeguard most directly prevents recurrence? A Redshift star schema mixes order-line and order-header facts in the same table and reports double-count revenue.
- Document fact grain and validate cardinality in data model reviews.
- Add schema compatibility checks before crawler runs.
- Audit catalog lifecycle on organizational changes.
- Track catalog and snapshot IDs across pipeline steps.
Explanation
Correct Answer
A:Document fact grain and validate cardinality in data model reviews. This safeguards against a recurring cause: The modeled fact grain is inconsistent across record types.
Incorrect Answers
B:That safeguard addresses another case: A Glue crawler discovers an S3 path containing two incompatible CSV header layouts and produces a wide schema with ambiguous columns. It is not the control for this recurring failure.
C:That safeguard addresses another case: A SageMaker Catalog project references a dataset whose owner changed but permissions and business definitions still point to the former team. It is not the control for this recurring failure.
D:That safeguard addresses another case: A dataset uses Iceberg but Spark and Athena query different catalogs and show conflicting table snapshots. It is not the control for this recurring failure.
Question 127
An ETL role invokes KMS Decrypt repeatedly, but the pipeline's incident review examines only application logs without recording AWS API actor identity. Which engineering change best addresses the underlying issue?
- Validate Glue network connection resources, subnets, SGs and database credentials together.
- Apply account/organization guardrails, regional resource rules and audited exception processes.
- Correlate CloudTrail and applicable KMS/service logs with job execution context.
- Apply approved tokenization, masking, or projection before data exits the trusted boundary.
Explanation
Correct Answer
C:Correlate CloudTrail and applicable KMS/service logs with job execution context. It directly addresses the case cause (Operational logs omit relevant cloud audit-plane evidence.) and should be verified by: A controlled decrypt action can be attributed to the intended assumed role.
Incorrect Answers
A:That change addresses a Glue crawler in a VPC fails connection to a private RDS source even with the right IAM service role; it would not repair this incident.
B:That change addresses a project migrates its authoritative EU records to another AWS Region and management assumes an S3 bucket policy alone enforces future residency; it would not repair this incident.
D: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.
Question 128
After resolving the following incident, which ongoing safeguard most directly prevents recurrence? A Spark pipeline includes a wide shuffle stage because it joins on a function applied to both tables, preventing efficient key reuse.
- Track transformation-key contracts and explain-plan changes.
- Use idempotent publish/rollback contracts for every scheduled batch.
- Test asynchronous lifecycle and timeouts during orchestration review.
- Test the network path independently of password verification.
Explanation
Correct Answer
A:Track transformation-key contracts and explain-plan changes. This safeguards against a recurring cause: On-the-fly key normalization causes expensive join planning and movement.
Incorrect Answers
B: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.
C:That safeguard addresses another case: A Step Functions pipeline sends a notification before the ETL task's asynchronous execution actually completes. It is not the control for this recurring failure.
D:That safeguard addresses another case: A Glue connection to a source RDS database times out, although the JDBC credentials are valid. It is not the control for this recurring failure.
Question 129
After resolving the following incident, which ongoing safeguard most directly prevents recurrence? A Step Functions state retries every failure including invalid schema, consuming budget without possibility of success.
- Record dimension-size thresholds and explain plans for joins.
- Define deployment acceptance criteria for contracts and IAM access.
- Track per-consumer lag and quota needs as readers are added.
- Maintain documented error classes and bounded retry budgets.
Explanation
Correct Answer
D:Maintain documented error classes and bounded retry budgets. This safeguards against a recurring cause: Transient and permanent errors are not classified in the retry and catch policy.
Incorrect Answers
A: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.
B:That safeguard addresses another case: A CI pipeline promotes an ETL artifact after syntax checks but without a representative integration job against staged data. It is not the control for this recurring failure.
C:That safeguard addresses another case: Three independent Kinesis applications compete for shared shard read throughput and their IteratorAge rises together. It is not the control for this recurring failure.
Question 130
A Lambda Kinesis event-source mapping repeatedly delivers the same batch after one malformed record fails. Select TWO complementary measures that correctly repair and validate this failure.
- Delete every error record before recording its source identifier.
- Convert cleaned data to appropriately compressed Parquet with suitable partitions.
- Backlog declines within SLA without excessive database connection or write failures.
- Use supported partial batch failure handling and idempotent sink writes with a failure destination.
- The malformed record is isolated and good records do not create duplicate side effects.
Explanation
Correct Answers
D:Use supported partial batch failure handling and idempotent sink writes with a failure destination. The underlying cause is: Batch failure and checkpoint behavior cause previously successful records to be retried.
E:The malformed record is isolated and good records do not create duplicate side effects. This is the observable result required before accepting the correction.
Incorrect Answers
A:Delete every error record before recording its source identifier. That shortcut conflicts with the stated requirement.
B:That corrective action is for a different case: An ETL job writes CSV to a large analytics lake and Athena scans every column for two-field reports. It does not resolve this incident.
C:This would validate a different case: An SQS-backed processor overwhelms a downstream database after scaling consumers without any concurrency cap. It does not verify the outcome required here.
AWS Certified Data Engineer - Associate DEA-C01 Practice Tests