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 230
A data catalog stores PII labels only as free-text comments, so new tables bypass a tagging-based access process. Select THREE complementary measures that correctly repair and validate, and prevent recurrence of this failure.
- Apply approved standardized catalog classification tags or LF-Tags and validate inherited rules.
- A newly onboarded sensitive table receives the intended governed classification.
- Depend on undocumented naming conventions for private-column protection.
- Model validated numeric coordinate fields with units and location quality checks.
- Test similar products rank appropriately for documented benchmark queries.
- Enforce required tag vocabulary in dataset onboarding.
Explanation
Correct Answers
A:Apply approved standardized catalog classification tags or LF-Tags and validate inherited rules. The underlying cause is: Inconsistent metadata taxonomies prevent reliable automated governance.
B:A newly onboarded sensitive table receives the intended governed classification. This is the observable result required before accepting the correction.
F:Enforce required tag vocabulary in dataset onboarding. This protects against the following risk: Inconsistent metadata taxonomies prevent reliable automated governance.
Incorrect Answers
C:Depend on undocumented naming conventions for private-column protection. That shortcut conflicts with the stated requirement.
D:That corrective action is for a different case: A lake stores customer location coordinates as one unparsed text field while downstream joins require numeric latitude and longitude. It does not resolve this incident.
E:This would validate a different case: An application seeks low-latency semantic recommendations but indexes product names as plain text without generated embeddings. It does not verify the outcome required here.
Question 231
After resolving the following incident, which ongoing safeguard most directly prevents recurrence? A Lambda ETL process writes temporary files larger than its configured /tmp capacity and receives storage errors.
- Review retention and recovery objectives whenever downstream processing latency changes.
- Record peak intermediate disk usage and test large inputs.
- Run schema/format contract tests before warehouse loading.
- Audit ownership and naming of consumer checkpoints.
Explanation
Correct Answer
B:Record peak intermediate disk usage and test large inputs. This safeguards against a recurring cause: Ephemeral storage is insufficient for the actual intermediate workload.
Incorrect Answers
A:That safeguard addresses another case: A fraud detector needs to reread yesterday's Kinesis records but the stream uses its short default retention window. It is not the control for this recurring failure.
C: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.
D:That safeguard addresses another case: Two Kinesis consumers must independently recover after a deployment, but one team reuses the other's checkpoint store. It is not the control for this recurring failure.
Question 232
A streaming producer writes compressed messages into a format the Lambda consumer assumes is plain UTF-8. Which technical dependency most directly explains this behavior?
- On-the-fly key normalization causes expensive join planning and movement.
- The transformation omits currency and units normalization.
- Excessive small objects create metadata and planning overhead.
- Producer and consumer disagree on message framing and compression encoding.
Explanation
Correct Answer
D:Producer and consumer disagree on message framing and compression encoding. The corresponding fix is to document and validate the record envelope and implement the matching decode path.
Incorrect Answers
A:This diagnosis addresses another AWS case: A Spark pipeline includes a wide shuffle stage because it joins on a function applied to both tables, preventing efficient key reuse. The dependency here is different.
B:This diagnosis addresses another AWS case: A batch ETL task combines USD and EUR amounts under the same column and computes invalid totals. The dependency here is different.
C:This diagnosis addresses another AWS case: A Lambda process writes individual small S3 JSON files for millions of events and downstream scans slow dramatically. The dependency here is different.
Question 233
An EMR Spark job sends all rows for a popular customer to one reducer and fails despite plenty of idle cores. Select TWO complementary measures that correctly repair and validate this failure.
- Set global parallelism to one to avoid uneven executors.
- Hot-key tasks finish within acceptable time with unchanged aggregates.
- Driver memory remains stable while full dataset results are produced.
- Inspect key distribution and apply skew-aware partitioning, salting, or alternate aggregation strategy.
- Return correctly structured transformed records and audit failure routing.
Explanation
Correct Answers
B:Hot-key tasks finish within acceptable time with unchanged aggregates. This is the observable result required before accepting the correction.
D:Inspect key distribution and apply skew-aware partitioning, salting, or alternate aggregation strategy. The underlying cause is: Skewed join/group keys concentrate disproportionate workload in one task.
Incorrect Answers
A:Set global parallelism to one to avoid uneven executors. That shortcut conflicts with the stated requirement.
C:This would validate a different case: A distributed Spark process collects a large dataset to the driver and crashes from memory exhaustion. It does not verify the outcome required here.
E: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.
Question 234
A dataset uses Iceberg but Spark and Athena query different catalogs and show conflicting table snapshots. Which technical dependency most directly explains this behavior?
- Retention policy must not override active preservation requirements.
- Consumers are not referencing the same authoritative table metadata location and snapshot.
- DynamoDB TTL deletion is asynchronous rather than an instantaneous query filter.
- The two metastore environments are not synchronized.
Explanation
Correct Answer
B:Consumers are not referencing the same authoritative table metadata location and snapshot. The corresponding fix is to unify the supported catalog/table identity and validate snapshot visibility across engines.
Incorrect Answers
A:This diagnosis addresses another AWS case: A legal-hold dataset is subject to an S3 Lifecycle expiration rule that would remove evidence at the usual age. The dependency here is different.
C:This diagnosis addresses another AWS case: A DynamoDB table contains session records with expired timestamps but items remain visible immediately after expiry. The dependency here is different.
D:This diagnosis addresses another AWS case: A Hive metastore-based EMR Spark job writes a new partition but Athena never sees it through Glue Data Catalog. The dependency here is different.
Question 235
A data lake keeps years of detailed application logs in S3 Standard despite infrequent historical access and an approved 90-day hot tier. Select THREE complementary measures that correctly repair and validate, and prevent recurrence of this failure.
- A controlled external-table query reads the intended new partition only.
- Review lifecycle policies against audit and restore objectives annually.
- Apply a stable catalog schema and quarantine malformed headers or records upstream.
- Apply reviewed S3 Lifecycle transition rules to suitable eligible storage classes.
- Aged test objects transition as expected while required retrieval remains possible.
- Delete every record immediately after it leaves the frequent-access tier.
Explanation
Correct Answers
B:Review lifecycle policies against audit and restore objectives annually. This protects against the following risk: Storage lifecycle no longer reflects retention and access patterns.
D:Apply reviewed S3 Lifecycle transition rules to suitable eligible storage classes. The underlying cause is: Storage lifecycle no longer reflects retention and access patterns.
E:Aged test objects transition as expected while required retrieval remains possible. This is the observable result required before accepting the correction.
Incorrect Answers
A:This would validate a different case: A Redshift Spectrum external table points to S3 partitions whose IAM role cannot read the new prefix after an account move. It does not verify the outcome required here.
C: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.
F:Delete every record immediately after it leaves the frequent-access tier. That shortcut conflicts with the stated requirement.
Question 236
After resolving the following incident, which ongoing safeguard most directly prevents recurrence? A DynamoDB table contains session records with expired timestamps but items remain visible immediately after expiry.
- Test functional expiration separately from background storage cleanup.
- Document consistency needs separately for each access pattern.
- Track metadata version and compatible migration steps per release.
- Review table size and plan evidence before overriding AUTO placement.
Explanation
Correct Answer
A:Test functional expiration separately from background storage cleanup. This safeguards against a recurring cause: DynamoDB TTL deletion is asynchronous rather than an instantaneous query filter.
Incorrect Answers
B:That safeguard addresses another case: A DynamoDB application requires strongly consistent reads immediately after a successful critical write but queries a global secondary index. It is not the control for this recurring failure.
C:That safeguard addresses another case: Two developers independently edit Glue Data Catalog schema types during release, and a job fails after the last writer wins. It is not the control for this recurring failure.
D:That safeguard addresses another case: A small dimension table joins huge Redshift facts, but an unnecessarily EVEN distribution causes repeated data transfer. It is not the control for this recurring failure.
Question 237
A team applies a reviewed fix for this situation: An S3 table is tagged `classification=restricted`, but its Lake Formation LF-Tag grant allows a broad organizational unit with no business need. Which observed outcome would most convincingly validate the fix?
- An approved data steward queries the table while a nonmember receives denial.
- The intended cross-account role reads only the allowed lake dataset.
- A controlled object cannot replicate to a disallowed Region, while authorized resilience works.
- Controlled events from the missing day are queryable after catalog correction.
Explanation
Correct Answer
A:An approved data steward queries the table while a nonmember receives denial. This verifies the result of narrow LF-Tag permissions to reviewed principals and classify data assets consistently.
Incorrect Answers
B:This would verify another situation: An S3 lake access point exists but a cross-account principal still receives AccessDenied when its IAM and bucket policies are not aligned. It does not validate the current case.
C:This would verify another situation: A data lake in an EU Region replicates raw customer records to an unapproved Region for convenience. It does not validate the current case.
D: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.
Question 238
After resolving the following incident, which ongoing safeguard most directly prevents recurrence? A fact table in Redshift filters mostly on event date but load order does not correlate with the filter, driving wide block scans.
- Test large scans and mid-scan interruption recovery.
- Revalidate role, bucket and key permissions after account boundary changes.
- Reassess sort-key benefit as query patterns evolve.
- Practice restore and replay consistency during recovery drills.
Explanation
Correct Answer
C:Reassess sort-key benefit as query patterns evolve. This safeguards against a recurring cause: The current sort/physical layout is unhelpful for common predicates.
Incorrect Answers
A:That safeguard addresses another case: A DynamoDB archival pipeline uses Scan without pagination and misses records beyond the first page. It is not the control for this recurring failure.
B:That safeguard addresses another case: A Redshift UNLOAD writes reporting data to an S3 bucket in another account but fails with access denied. It is not the control for this recurring failure.
D:That safeguard addresses another case: A cross-region disaster recovery table is restored from an old snapshot, and CDC replication starts from an incompatible new checkpoint. It is not the control for this recurring failure.
Question 239
After resolving the following incident, which ongoing safeguard most directly prevents recurrence? A data access policy permits all S3 prefixes under `reports/*`, unintentionally including payroll records stored beneath that path.
- Require negative privilege tests for wildcard policy changes.
- Scan pipeline artifacts for access keys and enforce role-based access.
- Use policy-simulator and negative-access tests during access changes.
- Test encrypted cross-account replication with intended and forbidden principals.
Explanation
Correct Answer
A:Require negative privilege tests for wildcard policy changes. This safeguards against a recurring cause: An IAM resource wildcard is broader than the intended least-privilege dataset.
Incorrect Answers
B:That safeguard addresses another case: A pipeline uses long-lived IAM user access keys embedded in a Glue script instead of an execution role. It is not the control for this recurring failure.
C:That safeguard addresses another case: An S3 lake access point exists but a cross-account principal still receives AccessDenied when its IAM and bucket policies are not aligned. It is not the control for this recurring failure.
D:That safeguard addresses another case: A data lake copies SSE-KMS objects across AWS accounts but the destination principal cannot decrypt the replica. It is not the control for this recurring failure.
Question 240
A team applies a reviewed fix for this situation: An Athena view compares monthly cohorts using an inner join that drops customers with no activity, overstating retention. Which observed outcome would most convincingly validate the fix?
- A new unrecognized code is flagged before the data reaches reports.
- A controlled fixture receives the exact reviewed cleaning steps.
- Athena reads only successfully committed transform output after the Glue run ends.
- A zero-activity test customer remains in denominator without fake activity.
Explanation
Correct Answer
D:A zero-activity test customer remains in denominator without fake activity. This verifies the result of retain the baseline cohort and left-join subsequent activity with explicit null handling.
Incorrect Answers
A:This would verify another situation: A Glue transformation produces 100% nonnull rows but an upstream category mapping is outdated and mislabels every new source code. It does not validate the current case.
B:This would verify another situation: A Glue DataBrew recipe was changed interactively but the production pipeline still applies a previous published recipe version. It does not validate the current case.
C:This would verify another situation: A Step Functions data pipeline invokes Glue using a request/response integration and immediately launches Athena against unfinished output. It does not validate the current case.
AWS Certified Data Engineer - Associate DEA-C01 Practice Tests