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 470
A team applies a reviewed fix for this situation: An Athena query of yesterday's S3 partition returns zero rows because its table metadata lacks that partition. Which observed outcome would most convincingly validate the fix?
- Compliance fixtures remain available for the required duration.
- Historical snapshots and new rows remain queryable during the migration.
- Yesterday's test row becomes queryable without a broad table recreation.
- A test order maps to exactly the customer attributes valid at transaction time.
Explanation
Correct Answer
C:Yesterday's test row becomes queryable without a broad table recreation. This verifies the result of add supported partition projection or update Glue partitions in the ingestion workflow.
Incorrect Answers
A:This would verify another situation: An S3 data product has an approved seven-year retention requirement, but an engineer adds a 30-day expiration lifecycle rule. It does not validate the current case.
B:This would verify another situation: A team adds a nonnullable required field to an Iceberg table but old rows have no value and downstream reads fail. It does not validate the current case.
D:This would verify another situation: A warehouse fact table is joined to customer history using only customer ID, multiplying matches across changing customer versions. It does not validate the current case.
Question 471
A team applies a reviewed fix for this situation: A Glue job begins consuming twice its normal DPU budget after a transformation adds a repeated cross join. Which observed outcome would most convincingly validate the fix?
- The report matches known numeric test totals and identifies malformed values.
- A high-precision fixture survives transformation without unexpected rounding loss.
- Correct row counts and bounded DPU-hours return in a repeatable fixture.
- A user with several event retries contributes once to unique-user counts.
Explanation
Correct Answer
C:Correct row counts and bounded DPU-hours return in a repeatable fixture. This verifies the result of profile physical plans and remove unintended cross joins or use reviewed predicates.
Incorrect Answers
A:This would verify another situation: An Athena SQL query sums decimal prices stored as strings and uses lexicographic ordering on text. It does not validate the current case.
B:This would verify another situation: An upstream system changes a decimal field from two to four digits of precision and rounding introduces revenue drift. It does not validate the current case.
D:This would verify another situation: A marketing report uses COUNT(*) of event records as its active user metric and overstates adoption when users retry. It does not validate the current case.
Question 472
After resolving the following incident, which ongoing safeguard most directly prevents recurrence? A streaming pipeline evaluates quality from a random sample of 10 messages and assumes it proves a million-row batch is correct.
- Report sample sizes and require full validation for critical keys.
- Use primary business keys and collision tests for join logic.
- Document sampling design and population coverage in analysis artifacts.
- Publish metric definitions and lag counters alongside throughput.
Explanation
Correct Answer
A:Report sample sizes and require full validation for critical keys. This safeguards against a recurring cause: The sample is too small or unrepresentative for a claimed whole-population guarantee.
Incorrect Answers
B:That safeguard addresses another case: A Redshift SQL view joins two tables on customer name, and a same-name collision merges unrelated accounts. It is not the control for this recurring failure.
C:That safeguard addresses another case: An Athena Spark notebook reads only a handful of development files yet a manager interprets its average as an entire production trend. It is not the control for this recurring failure.
D:That safeguard addresses another case: A CloudWatch dashboard mixes Glue processed-record counts with Kinesis PutRecords count and calls them identical pipeline throughput. It is not the control for this recurring failure.
Question 473
An AWS Glue job writes to a governed S3 target but lacks the Lake Formation data-location access permission required for its workflow. Which technical dependency most directly explains this behavior?
- Underlying S3 IAM rights alone do not satisfy applicable Lake Formation location governance.
- Network reachability is distinct from the execution role's S3 authorization.
- Audit query coverage does not match the monitored account/Region scope.
- Business catalog sharing lacks stewardship and usage-governance metadata.
Explanation
Correct Answer
A:Underlying S3 IAM rights alone do not satisfy applicable Lake Formation location governance. The corresponding fix is to grant scoped data-location and catalog permissions alongside required IAM policies.
Incorrect Answers
B:This diagnosis addresses another AWS case: A Glue job in a private VPC cannot read a governed S3 source after the executor role loses permission, although its worker network is healthy. 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.
D:This diagnosis addresses another AWS case: A SageMaker Catalog project shares a data product broadly across teams without recording owner and allowed purpose. The dependency here is different.
Question 474
A team applies a reviewed fix for this situation: A Glue PySpark job fails when an upstream field changes from integer to string in some JSON documents. Which observed outcome would most convincingly validate the fix?
- Mixed old/new fixtures produce expected typed output or documented rejects.
- A maximum-size fixture completes without filling local temporary storage.
- The DAG parses and a controlled run completes its expected task graph.
- A tenant query scans only the relevant partitions and records appear under expected prefixes.
Explanation
Correct Answer
A:Mixed old/new fixtures produce expected typed output or documented rejects. This verifies the result of apply an explicit compatible schema or deliberate conversion and quarantine unparseable values.
Incorrect Answers
B:This would verify another situation: A Lambda ETL process writes temporary files larger than its configured /tmp capacity and receives storage errors. It does not validate the current case.
C:This would verify another situation: An MWAA DAG was deployed but its Python import fails, so no scheduled run appears. 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 475
After resolving the following incident, which ongoing safeguard most directly prevents recurrence? A dataset uses Iceberg but Spark and Athena query different catalogs and show conflicting table snapshots.
- Track catalog and snapshot IDs across pipeline steps.
- Test version rollback and expiration dates before enabling cleanup.
- Use versioned data layout contracts and cutover rehearsals.
- Test functional expiration separately from background storage cleanup.
Explanation
Correct Answer
A:Track catalog and snapshot IDs across pipeline steps. This safeguards against a recurring cause: Consumers are not referencing the same authoritative table metadata location and snapshot.
Incorrect Answers
B:That safeguard addresses another case: An S3 lifecycle rule expires noncurrent object versions immediately, preventing recovery from accidental overwrites. It is not the control for this recurring failure.
C:That safeguard addresses another case: An S3-based table changes from hourly to daily partitions while old writers still publish hourly paths, giving inconsistent query results. It is not the control for this recurring failure.
D:That safeguard addresses another case: A DynamoDB table contains session records with expired timestamps but items remain visible immediately after expiry. It is not the control for this recurring failure.
Question 476
A fact table in Redshift filters mostly on event date but load order does not correlate with the filter, driving wide block scans. Select THREE complementary measures that correctly repair and validate, and prevent recurrence of this failure.
- Compliance fixtures remain available for the required duration.
- Align supported shared catalog integration or explicitly publish new partition metadata.
- Rebuild every query using ORDER BY without examining physical layout.
- Measure query plans and evaluate AUTO or an appropriate event-time sort design.
- A selective date query scans fewer blocks without losing late records.
- Reassess sort-key benefit as query patterns evolve.
Explanation
Correct Answers
D:Measure query plans and evaluate AUTO or an appropriate event-time sort design. The underlying cause is: The current sort/physical layout is unhelpful for common predicates.
E:A selective date query scans fewer blocks without losing late records. This is the observable result required before accepting the correction.
F:Reassess sort-key benefit as query patterns evolve. This protects against the following risk: The current sort/physical layout is unhelpful for common predicates.
Incorrect Answers
A:This would validate a different case: An S3 data product has an approved seven-year retention requirement, but an engineer adds a 30-day expiration lifecycle rule. It does not verify the outcome required here.
B:That corrective action is for 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 resolve this incident.
C:Rebuild every query using ORDER BY without examining physical layout. That shortcut conflicts with the stated requirement.
Question 477
After resolving the following incident, which ongoing safeguard most directly prevents recurrence? An S3 table is tagged `classification=restricted`, but its Lake Formation LF-Tag grant allows a broad organizational unit with no business need.
- Map required change evidence to the appropriate audit services.
- Test LF-TBAC allow and deny rules after tag updates.
- Keep lineage-based deletion runbooks and retention-exception records.
- Review residency control coverage across data services after architecture changes.
Explanation
Correct Answer
B:Test LF-TBAC allow and deny rules after tag updates. This safeguards against a recurring cause: Attribute-based permissions have a policy scope broader than the approved audience.
Incorrect Answers
A:That safeguard addresses another case: An AWS Config rule flags altered S3 encryption settings but the team uses CloudTrail alone as its continuous current-state configuration inventory. It is not the control for this recurring failure.
C:That safeguard addresses another case: A personal-data deletion request removes a row from an Athena external table view but leaves original S3 objects and downstream extracts. It is not the control for this recurring failure.
D: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.
Question 478
An Iceberg table's snapshot history grows as frequent small commits accumulate and query planning becomes slow. Which technical dependency most directly explains this behavior?
- Table metadata maintenance does not match commit frequency and retention needs.
- The two metastore environments are not synchronized.
- Raw object files do not by themselves provide open-table transaction semantics.
- External query credentials do not cover the current S3 resource and catalog context.
Explanation
Correct Answer
A:Table metadata maintenance does not match commit frequency and retention needs. The corresponding fix is to run supported snapshot expiration and metadata cleanup with retention safeguards.
Incorrect Answers
B: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.
C:This diagnosis addresses another AWS case: A team needs ACID updates and time-travel queries against a governed S3 lake but writes plain Parquet files with no table transaction metadata. The dependency here is different.
D:This diagnosis addresses another AWS case: A Redshift Spectrum external table points to S3 partitions whose IAM role cannot read the new prefix after an account move. The dependency here is different.
Question 479
A data team declares a successful cleanup because duplicate percentage fell, but the job also dropped valid unique rows. Which technical dependency most directly explains this behavior?
- Workflow execution order lacks explicit job dependencies.
- The schedule target's Region, ARN, role, or cross-account authorization is misconfigured.
- The workflow's sensor condition does not match the actual upstream terminal status.
- Single-metric quality scoring hides unintended data loss.
Explanation
Correct Answer
D:Single-metric quality scoring hides unintended data loss. The corresponding fix is to compare uniqueness, completeness, reconciliation, and distribution against known fixtures.
Incorrect Answers
A:This diagnosis addresses another AWS case: An EMR workflow submits five jobs simultaneously but two require the first job's generated HDFS staging output. The dependency here is different.
B:This diagnosis addresses another AWS case: An EventBridge schedule was configured in one Region but the receiving Step Functions state machine lives in another without a reviewed target design. The dependency here is different.
C:This diagnosis addresses another AWS case: An MWAA scheduled data DAG waits forever for an upstream batch because the external task reports completion through a different status name. The dependency here is different.
Question 480
A QuickSight dashboard compares two branch cost reports, one in local currency and one in USD, without conversion. Which technical dependency most directly explains this behavior?
- Failure evidence is lost with ephemeral compute nodes.
- The changed table layout or join pattern increases data movement.
- Visualization dimensions and units are inconsistent between sources.
- The workflow has no buffering or explicit throughput regulation at the ingress boundary.
Explanation
Correct Answer
C:Visualization dimensions and units are inconsistent between sources. The corresponding fix is to normalize currencies using approved rates and label dates, units and calculation rules.
Incorrect Answers
A:This diagnosis addresses another AWS case: An EMR job intermittently fails due to capacity interruptions but its logs are stored only on the terminated instance. The dependency here is different.
B:This diagnosis addresses another AWS case: A Redshift reporting job suddenly spends time redistributing a large fact table after a schema change. The dependency here is different.
D:This diagnosis addresses another AWS case: An orchestrated data processing task receives tens of thousands of S3 events, causing Lambda reserved concurrency exhaustion. The dependency here is different.
AWS Certified Data Engineer - Associate DEA-C01 Practice Tests