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 350
An ETL task in Glue times out only when a small fraction of keys dominate the daily partition. Select TWO complementary measures that correctly repair and validate this failure.
- Increase retry count on the same unmodified skewed job.
- A new unrecognized code is flagged before the data reaches reports.
- Compare uniqueness, completeness, reconciliation, and distribution against known fixtures.
- Long-running tasks improve without changing aggregate results.
- Inspect Spark stage metrics and split/salt hotspots or change skewed join strategy.
Explanation
Correct Answers
D:Long-running tasks improve without changing aggregate results. This is the observable result required before accepting the correction.
E:Inspect Spark stage metrics and split/salt hotspots or change skewed join strategy. The underlying cause is: Skew creates straggler executors and prevents completion within the SLA.
Incorrect Answers
A:Increase retry count on the same unmodified skewed job. That shortcut conflicts with the stated requirement.
B:This would validate a different case: A Glue transformation produces 100% nonnull rows but an upstream category mapping is outdated and mislabels every new source code. It does not verify the outcome required here.
C:That corrective action is for a different case: A data team declares a successful cleanup because duplicate percentage fell, but the job also dropped valid unique rows. It does not resolve this incident.
Question 351
An analytics team relies on Glue technical table names to determine which datasets are permitted for finance reporting. Which technical dependency most directly explains this behavior?
- Storage lifecycle no longer reflects retention and access patterns.
- The data model does not match the required predicate/access pattern.
- Object lifecycle configuration conflicts with required retention and legal policy.
- Physical metadata alone does not express authoritative business meaning and stewardship.
Explanation
Correct Answer
D:Physical metadata alone does not express authoritative business meaning and stewardship. The corresponding fix is to create governed business catalog descriptions and owner/lineage metadata in the supported catalog product.
Incorrect Answers
A:This diagnosis addresses another AWS case: A data lake keeps years of detailed application logs in S3 Standard despite infrequent historical access and an approved 90-day hot tier. The dependency here is different.
B:This diagnosis addresses another AWS case: A geospatial data catalog is placed in DynamoDB with no defined access key and engineers scan the entire table for each location. The dependency here is different.
C:This diagnosis addresses another AWS case: An S3 data product has an approved seven-year retention requirement, but an engineer adds a 30-day expiration lifecycle rule. The dependency here is different.
Question 352
A partner API returns HTTP 429, and a Glue ETL job immediately retries in tight loops until access is suspended. Which technical dependency most directly explains this behavior?
- Map concurrency is uncapped relative to external rate limits.
- Retries use non-idempotent output identity with uncertain prior completion.
- Per-record interpreter overhead replaces optimized distributed expressions.
- Retry policy ignores rate limiting and server retry hints.
Explanation
Correct Answer
D:Retry policy ignores rate limiting and server retry hints. The corresponding fix is to apply bounded exponential backoff, jitter, and documented API quotas with durable checkpoints.
Incorrect Answers
A:This diagnosis addresses another AWS case: A pipeline launches thousands of concurrent Step Functions Map tasks and saturates a small partner API. The dependency here is different.
B:This diagnosis addresses another AWS case: An orchestrator invokes a Lambda that writes to S3 then times out; the retry writes a second output under a new random key. The dependency here is different.
C:This diagnosis addresses another AWS case: A PySpark transformation uses Python row-by-row loops to parse simple scalar fields and runs slowly. The dependency here is different.
Question 353
A PySpark transformation uses Python row-by-row loops to parse simple scalar fields and runs slowly. Select TWO complementary measures that correctly repair and validate this failure.
- Increase the Glue job timeout without profiling transformation work.
- A representative run meets runtime targets with equivalent schema and values.
- Use supported Spark SQL built-in transformations and predicate pushdown where possible.
- Use an appropriate hashed lookup structure while preserving deterministic output behavior.
- A maximum-size fixture completes without filling local temporary storage.
Explanation
Correct Answers
B:A representative run meets runtime targets with equivalent schema and values. This is the observable result required before accepting the correction.
C:Use supported Spark SQL built-in transformations and predicate pushdown where possible. The underlying cause is: Per-record interpreter overhead replaces optimized distributed expressions.
Incorrect Answers
A:Increase the Glue job timeout without profiling transformation work. That shortcut conflicts with the stated requirement.
D:That corrective action is for a different case: A large ETL data structure uses a list for repeated membership checks and CPU use grows unexpectedly. It does not resolve this incident.
E:This would validate a different case: A Lambda ETL process writes temporary files larger than its configured /tmp capacity and receives storage errors. It does not verify the outcome required here.
Question 354
A team applies a reviewed fix for this situation: A serverless pipeline deploys with hand-edited IAM and S3 settings that differ among test and production accounts. Which observed outcome would most convincingly validate the fix?
- A clean deployment reproduces expected resources and scoped permissions.
- A source insert or update reaches the target after an interruption and restart.
- Two distinct same-timestamp events survive, while a retried ID deduplicates.
- A known new table's rows and later changes reach the approved target.
Explanation
Correct Answer
A:A clean deployment reproduces expected resources and scoped permissions. This verifies the result of declare reviewed environment-specific infrastructure using CloudFormation, CDK, or SAM.
Incorrect Answers
B:This would verify another situation: A DMS CDC task finishes a full-load phase but stops capturing source table changes when the source transaction log expires. It does not validate the current case.
C:This would verify another situation: A mobile event producer uses timestamp as the only deduplication key and collapses unrelated events recorded in one millisecond. It does not validate the current case.
D:This would verify another situation: An on-premises Oracle source feeds DMS, but newly added tables never appear in a configured migration. It does not validate the current case.
Question 355
An Athena view compares monthly cohorts using an inner join that drops customers with no activity, overstating retention. Which engineering change best addresses the underlying issue?
- Configure supported persistent log delivery to a controlled durable location.
- Check expected row counts against source manifest and tolerances before release.
- Move credentials to a protected managed secret and implement controlled refresh and failure alerts.
- Retain the baseline cohort and left-join subsequent activity with explicit null handling.
Explanation
Correct Answer
D:Retain the baseline cohort and left-join subsequent activity with explicit null handling. It directly addresses the case cause (The join excludes the population that must remain in the denominator.) and should be verified by: A zero-activity test customer remains in denominator without fake activity.
Incorrect Answers
A:That change addresses an EMR job intermittently fails due to capacity interruptions but its logs are stored only on the terminated instance; it would not repair this incident.
B:That change addresses a feed arrives with 30% fewer rows than normal, but a transformation succeeds and marks the data product complete; it would not repair this incident.
C:That change addresses a scheduled ETL uses an API token embedded in source code; rotation breaks the batch without an alert; it would not repair this incident.
Question 356
A vector retrieval index stores embeddings from two incompatible model versions in one dimension-dependent collection. Which technical dependency most directly explains this behavior?
- Embedding dimensionality and semantic spaces are not aligned.
- Query context includes the catalog and database, not just table name.
- Object lifecycle configuration conflicts with required retention and legal policy.
- The crawler classifier or file-format handling does not match actual data encoding.
Explanation
Correct Answer
A:Embedding dimensionality and semantic spaces are not aligned. The corresponding fix is to separate or migrate embeddings under explicit model versions and index compatibility rules.
Incorrect Answers
B:This diagnosis addresses another AWS case: Two Athena workgroups query identically named tables but one references a different data catalog and gets old records. The dependency here is different.
C:This diagnosis addresses another AWS case: An S3 data product has an approved seven-year retention requirement, but an engineer adds a 30-day expiration lifecycle rule. The dependency here is different.
D:This diagnosis addresses another AWS case: An S3 prefix contains `.json.gz` objects but the Glue crawler labels them as raw JSON and downstream parsers fail. The dependency here is different.
Question 357
An EventBridge schedule was configured in one Region but the receiving Step Functions state machine lives in another without a reviewed target design. Which engineering change best addresses the underlying issue?
- Normalize event time and use the required explicit UTC or business timezone boundaries.
- Rebuild and test connector libraries against the supported new Glue runtime.
- Validate supported cross-Region target patterns and scoped invocation permissions.
- Normalize currencies using approved rates and label dates, units and calculation rules.
Explanation
Correct Answer
C:Validate supported cross-Region target patterns and scoped invocation permissions. It directly addresses the case cause (The schedule target's Region, ARN, role, or cross-account authorization is misconfigured.) and should be verified by: A controlled scheduled event starts the intended execution once.
Incorrect Answers
A:That change addresses a daily sales pivot groups event timestamps by the viewer's local date and differs from the regulatory UTC day; it would not repair this incident.
B:That change addresses a data pipeline updates its Glue version but custom connector dependencies fail at initialization; it would not repair this incident.
D:That change addresses a QuickSight dashboard compares two branch cost reports, one in local currency and one in USD, without conversion; it would not repair this incident.
Question 358
A Lambda ETL process writes temporary files larger than its configured /tmp capacity and receives storage errors. Which technical dependency most directly explains this behavior?
- Ephemeral storage is insufficient for the actual intermediate workload.
- Consumer applications share state intended to represent separate progress positions.
- Delivery buffering settings and destination behavior conflict with the required freshness.
- Retry logic does not isolate staging and atomic commit boundaries.
Explanation
Correct Answer
A:Ephemeral storage is insufficient for the actual intermediate workload. The corresponding fix is to right-size supported Lambda ephemeral storage or stream/process in bounded chunks.
Incorrect Answers
B:This diagnosis addresses another AWS case: Two Kinesis consumers must independently recover after a deployment, but one team reuses the other's checkpoint store. The dependency here is different.
C:This diagnosis addresses another AWS case: A Firehose pipeline is expected to deliver individual records instantly, yet it buffers batches before S3 delivery. The dependency here is different.
D:This diagnosis addresses another AWS case: A Glue workflow reruns yesterday's partition after a partially failed daily job but overwrites already-approved historical results. The dependency here is different.
Question 359
After resolving the following incident, which ongoing safeguard most directly prevents recurrence? An Aurora PostgreSQL vector workload uses a vector index tuned for approximate nearest neighbors without checking recall for a new embedding model.
- Revalidate vector dimensions and retrieval metrics after model revisions.
- Audit catalog lifecycle on organizational changes.
- Require governance signoff for expiration policy changes.
- Benchmark partition count and size distributions.
Explanation
Correct Answer
A:Revalidate vector dimensions and retrieval metrics after model revisions. This safeguards against a recurring cause: Index configuration and vector characteristics affect speed/recall tradeoffs.
Incorrect Answers
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.
C:That safeguard addresses another case: An S3 data product has an approved seven-year retention requirement, but an engineer adds a 30-day expiration lifecycle rule. It is not the control for this recurring failure.
D:That safeguard addresses another case: An Athena table uses daily partitions on a timestamp with millions of near-empty partition folders. It is not the control for this recurring failure.
Question 360
An application seeks low-latency semantic recommendations but indexes product names as plain text without generated embeddings. Which technical dependency most directly explains this behavior?
- The two metastore environments are not synchronized.
- Lexical text indexing does not implement the intended vector similarity retrieval.
- Primary key design does not support a dominant lookup pattern.
- The UNLOAD role and destination policy do not authorize the intended cross-account write.
Explanation
Correct Answer
B:Lexical text indexing does not implement the intended vector similarity retrieval. The corresponding fix is to generate versioned embeddings and store/index vectors in a supported eligible vector-capable service.
Incorrect Answers
A: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 DynamoDB table uses composite key `tenant#date` but most reads are by `transaction_id` only and become scans. The dependency here is different.
D:This diagnosis addresses another AWS case: A Redshift UNLOAD writes reporting data to an S3 bucket in another account but fails with access denied. The dependency here is different.
AWS Certified Data Engineer - Associate DEA-C01 Practice Tests