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 180
A data access policy permits all S3 prefixes under `reports/*`, unintentionally including payroll records stored beneath that path. Select THREE complementary measures that correctly repair and validate, and prevent recurrence of this failure.
- The report job reads its approved prefix but payroll reads fail.
- Require negative privilege tests for wildcard policy changes.
- Treat matching `reports` as sufficient proof the data is nonsensitive.
- Narrow bucket and access-point resource ARNs and test effective explicit deny boundaries.
- A synthetic approved role change in a test Region is queryable by the auditor.
- Assign supported domain/project membership and dataset entitlements through reviewed workflows.
Explanation
Correct Answers
A:The report job reads its approved prefix but payroll reads fail. This is the observable result required before accepting the correction.
B:Require negative privilege tests for wildcard policy changes. This protects against the following risk: An IAM resource wildcard is broader than the intended least-privilege dataset.
D:Narrow bucket and access-point resource ARNs and test effective explicit deny boundaries. The underlying cause is: An IAM resource wildcard is broader than the intended least-privilege dataset.
Incorrect Answers
C:Treat matching `reports` as sufficient proof the data is nonsensitive. That shortcut conflicts with the stated requirement.
E:This would validate a different case: A CloudTrail Lake query lists IAM role changes but its event filter omits the Regions holding the relevant data pipelines. It does not verify the outcome required here.
F:That corrective action is for a different case: 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 does not resolve this incident.
Question 181
A nightly data product uses a moving seven-day window but incoming source events arrive late and are excluded without a watermark policy. Which engineering change best addresses the underlying issue?
- Inspect the service response contract and update the sensor or operator success conditions.
- Poll GetQueryExecution with bounded backoff and handle FAILED/CANCELLED before reading results.
- Persist business run IDs and query existing job state before retrying execution creation.
- Implement event-time windows with a supported lateness allowance and correction/backfill strategy.
Explanation
Correct Answer
D:Implement event-time windows with a supported lateness allowance and correction/backfill strategy. It directly addresses the case cause (Data freshness and event-time completeness assumptions are not explicit.) and should be verified by: A known delayed event updates the intended window according to policy.
Incorrect Answers
A:That change addresses an MWAA scheduled data DAG waits forever for an upstream batch because the external task reports completion through a different status name; it would not repair this incident.
B:That change addresses an Athena automated report tries to read query results immediately after StartQueryExecution returns a query ID; it would not repair this incident.
C:That change addresses a pipeline calls an AWS SDK to invoke Glue but drops the request token on network timeout and starts duplicate ETL runs; it would not repair this incident.
Question 182
A personal-data deletion request removes a row from an Athena external table view but leaves original S3 objects and downstream extracts. Which technical dependency most directly explains this behavior?
- Principal-dependent authorization is being confused with data integrity.
- Database privilege scope exceeds the analyst's reporting purpose.
- Deleting catalog metadata does not erase all underlying or derived personal data.
- Underlying S3 IAM rights alone do not satisfy applicable Lake Formation location governance.
Explanation
Correct Answer
C:Deleting catalog metadata does not erase all underlying or derived personal data. The corresponding fix is to locate affected source and derivative assets via lineage and apply approved deletion/retention policy.
Incorrect Answers
A:This diagnosis addresses another AWS case: An S3 lake read works with an administrator role but fails with the production ETL role, and the team assumes the dataset is corrupt. The dependency here is different.
B: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.
D:This diagnosis addresses another AWS case: An AWS Glue job writes to a governed S3 target but lacks the Lake Formation data-location access permission required for its workflow. The dependency here is different.
Question 183
A Glue crawler discovers an S3 path containing two incompatible CSV header layouts and produces a wide schema with ambiguous columns. Select TWO complementary measures that correctly repair and validate this failure.
- Both engines read the same committed table snapshot within planned freshness bounds.
- Known files appear under the intended distinct catalog schemas.
- Separate source prefixes/classifiers and create versioned tables with validated schema mappings.
- Use appropriately partitioned Parquet or another supported format, and verify partition predicates.
- Manually drop mismatched columns without preserving raw data.
Explanation
Correct Answers
B:Known files appear under the intended distinct catalog schemas. This is the observable result required before accepting the correction.
C:Separate source prefixes/classifiers and create versioned tables with validated schema mappings. The underlying cause is: Schema discovery crosses incompatible source populations in one catalog grouping.
Incorrect Answers
A:This would validate a different case: A dataset uses Iceberg but Spark and Athena query different catalogs and show conflicting table snapshots. It does not verify the outcome required here.
D:That corrective action is for a different case: An Athena query reads huge raw JSON partitions for a narrow timestamp filter and scans far more bytes than expected. It does not resolve this incident.
E:Manually drop mismatched columns without preserving raw data. That shortcut conflicts with the stated requirement.
Question 184
After resolving the following incident, which ongoing safeguard most directly prevents recurrence? An S3-based table changes from hourly to daily partitions while old writers still publish hourly paths, giving inconsistent query results.
- Track catalog and snapshot IDs across pipeline steps.
- Test hot-key distributions before capacity increases.
- Use versioned data layout contracts and cutover rehearsals.
- Review lifecycle policies against audit and restore objectives annually.
Explanation
Correct Answer
C:Use versioned data layout contracts and cutover rehearsals. This safeguards against a recurring cause: Partition layout evolution was deployed without coordinating producers and catalog readers.
Incorrect Answers
A: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.
B:That safeguard addresses another case: A DynamoDB table uses the same partition key for all new daily events, producing throttled writes during each morning burst. It is not the control for this recurring failure.
D:That safeguard addresses another case: A data lake keeps years of detailed application logs in S3 Standard despite infrequent historical access and an approved 90-day hot tier. It is not the control for this recurring failure.
Question 185
An S3 lifecycle rule expires noncurrent object versions immediately, preventing recovery from accidental overwrites. Select THREE complementary measures that correctly repair and validate, and prevent recurrence of this failure.
- Athena and Spark recognize the same test partition and schema.
- Set separately reviewed current and noncurrent version lifecycle policies.
- Test version rollback and expiration dates before enabling cleanup.
- Reassess partition keys/granularity and apply efficient columnar file layout.
- Disable versioning to simplify accidental overwrite recovery.
- An overwritten fixture can be restored within the intended recovery interval.
Explanation
Correct Answers
B:Set separately reviewed current and noncurrent version lifecycle policies. The underlying cause is: Noncurrent-version retention is shorter than the required rollback window.
C:Test version rollback and expiration dates before enabling cleanup. This protects against the following risk: Noncurrent-version retention is shorter than the required rollback window.
F:An overwritten fixture can be restored within the intended recovery interval. This is the observable result required before accepting the correction.
Incorrect Answers
A:This would validate a different case: A Hive metastore-based EMR Spark job writes a new partition but Athena never sees it through Glue Data Catalog. It does not verify the outcome required here.
D:That corrective action is for a different case: An Athena table uses daily partitions on a timestamp with millions of near-empty partition folders. It does not resolve this incident.
E:Disable versioning to simplify accidental overwrite recovery. That shortcut conflicts with the stated requirement.
Question 186
A team applies a reviewed fix for this situation: A Step Functions data pipeline invokes Glue using a request/response integration and immediately launches Athena against unfinished output. Which observed outcome would most convincingly validate the fix?
- Athena reads only successfully committed transform output after the Glue run ends.
- Two-tenant fixture running totals are independent and correct.
- A repeated batch does not change the accepted distinct event count.
- The dashboard marks stale partitions before consumers treat them as current.
Explanation
Correct Answer
A:Athena reads only successfully committed transform output after the Glue run ends. This verifies the result of use supported wait-for-completion integration or a correctly bounded job-status polling loop.
Incorrect Answers
B:This would verify another situation: A Redshift window query uses SUM without the intended PARTITION BY and produces one cumulative total over all tenants. It does not validate the current case.
C: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.
D:This would verify another situation: A daily S3 data lake output is present but the last successful ETL timestamp is two days old. It does not validate the current case.
Question 187
An EventBridge rule matches both replayed and new events and starts two identical pipelines for the same batch. Which technical dependency most directly explains this behavior?
- The processing path sends unnecessary sensitive content to an external model workflow.
- Event delivery and replay are not protected by a stable idempotency key.
- The transformation changes record granularity without an explicit explode/join design.
- The warehouse is storing a frequently analyzed typed attribute in an inefficient representation.
Explanation
Correct Answer
B:Event delivery and replay are not protected by a stable idempotency key. The corresponding fix is to store an execution identity and use conditional state transitions before starting work.
Incorrect Answers
A:This diagnosis addresses another AWS case: An ETL pipeline calls a Bedrock model on full records containing account secrets merely to extract public product categories. The dependency here is different.
C:This diagnosis addresses another AWS case: A Glue job reading nested JSON flattens arrays incorrectly and duplicates parent order totals. 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 188
A team applies a reviewed fix for this situation: A data pipeline updates its Glue version but custom connector dependencies fail at initialization. Which observed outcome would most convincingly validate the fix?
- Independent sampled and held-out metrics agree within the predeclared tolerance.
- A maximum-size sample completes with a checkpointed durable output.
- A representative connector read works in the target runtime without fallback hacks.
- Consumers start only after the upstream staging output is committed.
Explanation
Correct Answer
C:A representative connector read works in the target runtime without fallback hacks. This verifies the result of rebuild and test connector libraries against the supported new Glue runtime.
Incorrect Answers
A:This would verify another situation: An Athena Spark notebook reads only a handful of development files yet a manager interprets its average as an entire production trend. It does not validate the current case.
B: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 EMR workflow submits five jobs simultaneously but two require the first job's generated HDFS staging output. It does not validate the current case.
Question 189
A team applies a reviewed fix for this situation: A workflow branches on a job-status string but overlooks the Cancelled terminal state, leaving executions stuck. Which observed outcome would most convincingly validate the fix?
- A replay starting at the intended timestamp retrieves the retained events.
- Injected cancelled and failed jobs exit with correctly classified outcomes.
- Small batches finish at lower cost without violating latency objectives.
- A tenant query scans only the relevant partitions and records appear under expected prefixes.
Explanation
Correct Answer
B:Injected cancelled and failed jobs exit with correctly classified outcomes. This verifies the result of model all documented terminal statuses with success, retryable, and failure branches.
Incorrect Answers
A:This would verify another situation: A fraud detector needs to reread yesterday's Kinesis records but the stream uses its short default retention window. It does not validate the current case.
C:This would verify another situation: A Glue job uses a fixed worker count at peak and wastes compute on tiny nightly delta batches. It does not validate the current case.
D:This would verify another situation: A Firehose stream delivering transactions to S3 mixes every customer into the same prefix, making Athena queries scan all tenants. It does not validate the current case.
Question 190
After resolving the following incident, which ongoing safeguard most directly prevents recurrence? An ETL task in Glue times out only when a small fraction of keys dominate the daily partition.
- Version orchestration status contracts and test alternate terminal states.
- Monitor per-task skew rather than average cluster CPU alone.
- Build SDK orchestration tests for all Athena terminal states.
- Require multidimensional quality gates before final publish.
Explanation
Correct Answer
B:Monitor per-task skew rather than average cluster CPU alone. This safeguards against a recurring cause: Skew creates straggler executors and prevents completion within the SLA.
Incorrect Answers
A:That safeguard addresses another case: An MWAA scheduled data DAG waits forever for an upstream batch because the external task reports completion through a different status name. It is not the control for this recurring failure.
C:That safeguard addresses another case: An Athena automated report tries to read query results immediately after StartQueryExecution returns a query ID. It is not the control for this recurring failure.
D:That safeguard addresses another case: A data team declares a successful cleanup because duplicate percentage fell, but the job also dropped valid unique rows. It is not the control for this recurring failure.
AWS Certified Data Engineer - Associate DEA-C01 Practice Tests