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 390
A Redshift datashare grants partner analysts access to a customer data mart without a purpose or term limit. Which technical dependency most directly explains this behavior?
- Data sharing lifecycle does not reflect approved contractual authorization.
- Cryptographic permissions exceed the data processing task's required keys.
- The published data access layer does not implement required masking or view restrictions.
- At-rest encryption does not secure data transmission on an external path.
Explanation
Correct Answer
A:Data sharing lifecycle does not reflect approved contractual authorization. The corresponding fix is to scope shared views, roles and periodic reauthorization with a documented owner.
Incorrect Answers
B:This diagnosis addresses another AWS case: A Glue data job decrypts source objects using a wildcard KMS permission spanning unrelated client keys. The dependency here is different.
C:This diagnosis addresses another AWS case: A Redshift view exposes unmasked customer SSNs to a general BI role despite a requirement for partial disclosure. The dependency here is different.
D:This diagnosis addresses another AWS case: An S3 export writes regulated data to an unencrypted partner endpoint despite source-at-rest SSE-KMS protection. The dependency here is different.
Question 391
An S3 table is tagged `classification=restricted`, but its Lake Formation LF-Tag grant allows a broad organizational unit with no business need. Select TWO complementary measures that correctly repair and validate this failure.
- Restore least-privilege S3 actions and evaluate the role's endpoint and bucket policies.
- Narrow LF-Tag permissions to reviewed principals and classify data assets consistently.
- An approved data steward queries the table while a nonmember receives denial.
- Replace classification tags with free-form public comments.
- A test export contains permitted pseudonyms and omits restricted raw fields.
Explanation
Correct Answers
B:Narrow LF-Tag permissions to reviewed principals and classify data assets consistently. The underlying cause is: Attribute-based permissions have a policy scope broader than the approved audience.
C:An approved data steward queries the table while a nonmember receives denial. This is the observable result required before accepting the correction.
Incorrect Answers
A:That corrective action is for a different 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. It does not resolve this incident.
D:Replace classification tags with free-form public comments. That shortcut conflicts with the stated requirement.
E:This would validate a different case: A DynamoDB-backed application needs to redact sensitive values before exporting analytics but relies only on table encryption. It does not verify the outcome required here.
Question 392
A mobile event producer uses timestamp as the only deduplication key and collapses unrelated events recorded in one millisecond. Select TWO complementary measures that correctly repair and validate this failure.
- A representative run meets runtime targets with equivalent schema and values.
- Use stable producer event IDs and appropriate per-source sequence information.
- Drop all events whose timestamps repeat.
- Validate upstream schema and use appropriate supported COPY date parsing or a staging correction.
- Two distinct same-timestamp events survive, while a retried ID deduplicates.
Explanation
Correct Answers
B:Use stable producer event IDs and appropriate per-source sequence information. The underlying cause is: The event identity is not unique across simultaneously generated records.
E:Two distinct same-timestamp events survive, while a retried ID deduplicates. This is the observable result required before accepting the correction.
Incorrect Answers
A:This would validate a different case: A PySpark transformation uses Python row-by-row loops to parse simple scalar fields and runs slowly. It does not verify the outcome required here.
C:Drop all events whose timestamps repeat. That shortcut conflicts with the stated requirement.
D:That corrective action is for a different case: A Redshift COPY import fails on a changed date format in one batch even though prior files loaded. It does not resolve this incident.
Question 393
An S3 lifecycle rule expires noncurrent object versions immediately, preventing recovery from accidental overwrites. Which technical dependency most directly explains this behavior?
- The modeled fact grain is inconsistent across record types.
- Catalog recreation destroys governance metadata and stable table identity.
- Noncurrent-version retention is shorter than the required rollback window.
- Schema discovery crosses incompatible source populations in one catalog grouping.
Explanation
Correct Answer
C:Noncurrent-version retention is shorter than the required rollback window. The corresponding fix is to set separately reviewed current and noncurrent version lifecycle policies.
Incorrect Answers
A:This diagnosis addresses another AWS case: A Redshift star schema mixes order-line and order-header facts in the same table and reports double-count revenue. The dependency here is different.
B:This diagnosis addresses another AWS case: An ETL job drops a Glue Data Catalog table and recreates it daily, deleting important tags and permissions. The dependency here is different.
D:This diagnosis addresses another AWS case: A Glue crawler discovers an S3 path containing two incompatible CSV header layouts and produces a wide schema with ambiguous columns. The dependency here is different.
Question 394
An Athena query uses SELECT * on a wide Parquet table, although the report needs two measures and a date. Select THREE complementary measures that correctly repair and validate, and prevent recurrence of this failure.
- Monitor bytes scanned per report and require column selection in review.
- Profile physical plans and remove unintended cross joins or use reviewed predicates.
- Increase query concurrency to counter avoidable data scanning.
- A known filtered fixture passes with every source record accounted for.
- Scanned data falls while selected measure results match the original report.
- Select only needed fields and apply effective partition predicates where applicable.
Explanation
Correct Answers
A:Monitor bytes scanned per report and require column selection in review. This protects against the following risk: The query unnecessarily reads columns beyond its actual projection.
E:Scanned data falls while selected measure results match the original report. This is the observable result required before accepting the correction.
F:Select only needed fields and apply effective partition predicates where applicable. The underlying cause is: The query unnecessarily reads columns beyond its actual projection.
Incorrect Answers
B:That corrective action is for a different case: A Glue job begins consuming twice its normal DPU budget after a transformation adds a repeated cross join. It does not resolve this incident.
C:Increase query concurrency to counter avoidable data scanning. That shortcut conflicts with the stated requirement.
D:This would validate a different case: A data quality gate compares raw and target record totals without accounting for intentional filter exclusions, falsely failing clean batches. It does not verify the outcome required here.
Question 395
A CloudWatch dashboard mixes Glue processed-record counts with Kinesis PutRecords count and calls them identical pipeline throughput. Select THREE complementary measures that correctly repair and validate, and prevent recurrence of this failure.
- Publish metric definitions and lag counters alongside throughput.
- The report matches known numeric test totals and identifies malformed values.
- A controlled retry is reflected correctly without falsely multiplying business events.
- Define consistent stage-level event counts and correlate stable IDs at checkpoints.
- Add service operation counts together to estimate unique data rows.
- Validate supported cross-Region target patterns and scoped invocation permissions.
Explanation
Correct Answers
A:Publish metric definitions and lag counters alongside throughput. This protects against the following risk: Service metrics represent different stages and may count retries or batches differently.
C:A controlled retry is reflected correctly without falsely multiplying business events. This is the observable result required before accepting the correction.
D:Define consistent stage-level event counts and correlate stable IDs at checkpoints. The underlying cause is: Service metrics represent different stages and may count retries or batches differently.
Incorrect Answers
B:This would validate a different case: An Athena SQL query sums decimal prices stored as strings and uses lexicographic ordering on text. It does not verify the outcome required here.
E:Add service operation counts together to estimate unique data rows. That shortcut conflicts with the stated requirement.
F:That corrective action is for a different case: An EventBridge schedule was configured in one Region but the receiving Step Functions state machine lives in another without a reviewed target design. It does not resolve this incident.
Question 396
A Redshift UNLOAD writes reporting data to an S3 bucket in another account but fails with access denied. Which engineering change best addresses the underlying issue?
- Benchmark supported HNSW or other index choices against ground-truth neighbors and query latency.
- Grant scoped bucket permissions and necessary KMS access to the Redshift execution role.
- Offload reporting to an appropriately refreshed warehouse, replica or approved analytical system.
- Use a supported strongly consistent base-table or local-index read design where necessary.
Explanation
Correct Answer
B:Grant scoped bucket permissions and necessary KMS access to the Redshift execution role. It directly addresses the case cause (The UNLOAD role and destination policy do not authorize the intended cross-account write.) and should be verified by: A controlled UNLOAD produces output in only the approved S3 prefix.
Incorrect Answers
A:That change addresses an Aurora PostgreSQL vector workload uses a vector index tuned for approximate nearest neighbors without checking recall for a new embedding model; it would not repair this incident.
C:That change addresses an operational RDS database has a complex read-only report consuming most CPU at peak checkout time; it would not repair this incident.
D:That change addresses a DynamoDB application requires strongly consistent reads immediately after a successful critical write but queries a global secondary index; it would not repair this incident.
Question 397
A team applies a reviewed fix for this situation: A SAM deployment packages an outdated Lambda handler because build artifacts from a previous branch were reused. Which observed outcome would most convincingly validate the fix?
- Notifications fire only after the transform reaches a recorded successful terminal state.
- Producer reconnects and publishes through broker failover without hard-coded single-host dependency.
- The deployed function identifies the intended release and completes a fixture invocation.
- Two distinct same-timestamp events survive, while a retried ID deduplicates.
Explanation
Correct Answer
C:The deployed function identifies the intended release and completes a fixture invocation. This verifies the result of use reproducible clean builds and validate the packaged Lambda handler in CI.
Incorrect Answers
A: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.
B:This would verify another situation: An MSK producer succeeds only intermittently after brokers change because its connection string contains one retired broker address. It does not validate the current case.
D: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.
Question 398
After resolving the following incident, which ongoing safeguard most directly prevents recurrence? A QuickSight dashboard compares two branch cost reports, one in local currency and one in USD, without conversion.
- Check measure units and aggregation grain in dashboard reviews.
- Test alert-delivery failure modes separately from ETL completion.
- Review dependency edges and intermediate outputs on each workflow change.
- Build SDK orchestration tests for all Athena terminal states.
Explanation
Correct Answer
A:Check measure units and aggregation grain in dashboard reviews. This safeguards against a recurring cause: Visualization dimensions and units are inconsistent between sources.
Incorrect Answers
B:That safeguard addresses another case: A Step Functions run is marked succeeded although a downstream notification publish fails and no incident ticket is opened. It is not the control for this recurring failure.
C:That safeguard addresses another case: An EMR workflow submits five jobs simultaneously but two require the first job's generated HDFS staging output. It is not the control for this recurring failure.
D: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.
Question 399
A lake stores customer location coordinates as one unparsed text field while downstream joins require numeric latitude and longitude. Which engineering change best addresses the underlying issue?
- Add supported partition projection or update Glue partitions in the ingestion workflow.
- Generate versioned embeddings and store/index vectors in a supported eligible vector-capable service.
- Apply application-level expiry checks where strict visibility is required and keep TTL for eventual cleanup.
- Model validated numeric coordinate fields with units and location quality checks.
Explanation
Correct Answer
D:Model validated numeric coordinate fields with units and location quality checks. It directly addresses the case cause (Schema representation prevents typed spatial validation and query optimization.) and should be verified by: Invalid coordinates are rejected and valid ones support intended filters.
Incorrect Answers
A:That change addresses an Athena query of yesterday's S3 partition returns zero rows because its table metadata lacks that partition; it would not repair this incident.
B:That change addresses an application seeks low-latency semantic recommendations but indexes product names as plain text without generated embeddings; it would not repair this incident.
C:That change addresses a DynamoDB table contains session records with expired timestamps but items remain visible immediately after expiry; it would not repair this incident.
Question 400
A team applies a reviewed fix for this situation: A warehouse fact table is joined to customer history using only customer ID, multiplying matches across changing customer versions. Which observed outcome would most convincingly validate the fix?
- A test compressed object creates the expected typed catalog columns.
- A finance analyst can identify the approved authoritative dataset and owner.
- A conflicting schema change is rejected before the production job runs.
- A test order maps to exactly the customer attributes valid at transaction time.
Explanation
Correct Answer
D:A test order maps to exactly the customer attributes valid at transaction time. This verifies the result of join using correct surrogate keys or as-of effective dates for SCD history.
Incorrect Answers
A:This would verify another situation: An S3 prefix contains `.json.gz` objects but the Glue crawler labels them as raw JSON and downstream parsers fail. It does not validate the current case.
B:This would verify another situation: An analytics team relies on Glue technical table names to determine which datasets are permitted for finance reporting. It does not validate the current case.
C:This would verify another situation: Two developers independently edit Glue Data Catalog schema types during release, and a job fails after the last writer wins. It does not validate the current case.
AWS Certified Data Engineer - Associate DEA-C01 Practice Tests