Amazon AWS Certified Data Engineer - Associate DEA-C01 Practice Test 60
Question 590
A metadata crawler discovers a database yet cannot list schemas after its role loses network access. What validation evidence distinguishes a correct implementation from a dashboard-only change?
- The relevant validation evidence is crawler connection ARN, secret rotation state, JDBC errors, subnet routes and catalog run logs.
- The relevant validation evidence is a resource ARN alone without any current data-plane observation.
- The relevant validation evidence is a renamed resource label that does not show an authorization or processing result.
- The relevant validation evidence is a browser screenshot from another AWS account and time period.
Explanation
Correct Answer
A:Cataloging a private external source requires connectivity and authorization before a crawler can inspect schemas.
Incorrect Answers
B:A resource ARN alone without any current data-plane observation. This is not sufficient evidence for Glue connection secrets and cataloging external sources. Check crawler connection ARN, secret rotation state, JDBC errors, subnet routes and catalog run logs. Cataloging a private external source requires connectivity and authorization before a crawler can inspect schemas.
C:A renamed resource label that does not show an authorization or processing result. This is not sufficient evidence for Glue connection secrets and cataloging external sources. Check crawler connection ARN, secret rotation state, JDBC errors, subnet routes and catalog run logs. Cataloging a private external source requires connectivity and authorization before a crawler can inspect schemas.
D:A browser screenshot from another AWS account and time period. This is not sufficient evidence for Glue connection secrets and cataloging external sources. Check crawler connection ARN, secret rotation state, JDBC errors, subnet routes and catalog run logs. Cataloging a private external source requires connectivity and authorization before a crawler can inspect schemas.
Question 591
A metadata crawler discovers a database yet cannot list schemas after its role loses network access. Which design principle is consistent with the stated data-processing contract?
- The governing design principle is that a pipeline schedule guarantees that every downstream source record was processed correctly.
- The governing design principle is that a CloudWatch metric label is equivalent to a successful target table data-quality validation.
- The governing design principle is that cataloging a private external source requires connectivity and authorization before a crawler can inspect schemas.
- The governing design principle is that every AWS managed service uses the same consistency, retry and query-processing semantics.
Explanation
Correct Answer
C:Verify with crawler connection ARN, secret rotation state, JDBC errors, subnet routes and catalog run logs. Implement by choosing to configure the Glue connection, supported Secrets Manager credential and VPC network path for external catalog discovery.
Incorrect Answers
A:A pipeline schedule guarantees that every downstream source record was processed correctly. That generalization conflicts with Glue connection secrets and cataloging external sources. Instead cataloging a private external source requires connectivity and authorization before a crawler can inspect schemas. Check crawler connection ARN, secret rotation state, JDBC errors, subnet routes and catalog run logs.
B:A CloudWatch metric label is equivalent to a successful target table data-quality validation. That generalization conflicts with Glue connection secrets and cataloging external sources. Instead cataloging a private external source requires connectivity and authorization before a crawler can inspect schemas. Check crawler connection ARN, secret rotation state, JDBC errors, subnet routes and catalog run logs.
D:Every AWS managed service uses the same consistency, retry and query-processing semantics. That generalization conflicts with Glue connection secrets and cataloging external sources. Instead cataloging a private external source requires connectivity and authorization before a crawler can inspect schemas. Check crawler connection ARN, secret rotation state, JDBC errors, subnet routes and catalog run logs.
Question 592
A metadata crawler discovers a database yet cannot list schemas after its role loses network access. An incorrect proposal is: Embed a permanent production database password in a public crawler description. What issue should reviewers anticipate if the shortcut is adopted?
- The concrete failure is that the presence of an accurate job timestamp automatically created unauthorized database credentials.
- The concrete failure is that inspecting an existing Athena query plan itself deleted every production table.
- The concrete failure is that a harmless resource display-name edit caused all prior ETL jobs to lose their source schemas.
- The concrete failure is that a valid crawler schedule cannot overcome expired credentials or an unreachable database port.
Explanation
Correct Answer
D:This is why the incorrect shortcut does not meet Glue connection secrets and cataloging external sources. The safer implementation is to configure the Glue connection, supported Secrets Manager credential and VPC network path for external catalog discovery.
Incorrect Answers
A:The presence of an accurate job timestamp automatically created unauthorized database credentials. That unrelated assertion does not explain the actual Glue connection secrets and cataloging external sources risk. The relevant failure is that a valid crawler schedule cannot overcome expired credentials or an unreachable database port. Check crawler connection ARN, secret rotation state, JDBC errors, subnet routes and catalog run logs.
B:Inspecting an existing Athena query plan itself deleted every production table. That unrelated assertion does not explain the actual Glue connection secrets and cataloging external sources risk. The relevant failure is that a valid crawler schedule cannot overcome expired credentials or an unreachable database port. Check crawler connection ARN, secret rotation state, JDBC errors, subnet routes and catalog run logs.
C:A harmless resource display-name edit caused all prior ETL jobs to lose their source schemas. That unrelated assertion does not explain the actual Glue connection secrets and cataloging external sources risk. The relevant failure is that a valid crawler schedule cannot overcome expired credentials or an unreachable database port. Check crawler connection ARN, secret rotation state, JDBC errors, subnet routes and catalog run logs.
Question 593
A metadata crawler discovers a database yet cannot list schemas after its role loses network access. The observed failure is: A valid crawler schedule cannot overcome expired credentials or an unreachable database port. Which response repairs the underlying problem without unnecessary privilege or data loss?
- The supported recovery step is to delete all existing catalog tables whenever a connection attempt times out.
- The supported recovery step is to embed a permanent production database password in a public crawler description.
- The supported recovery step is to assume S3 ListBucket permission alone grants JDBC database privileges.
- The supported recovery step is to repair source connectivity and credential reference and validate one catalog table refresh.
Explanation
Correct Answer
D:This addresses the observed Glue connection secrets and cataloging external sources failure while preserving the required contract. Recheck crawler connection ARN, secret rotation state, JDBC errors, subnet routes and catalog run logs.
Incorrect Answers
A:Delete all existing catalog tables whenever a connection attempt times out. A valid crawler schedule cannot overcome expired credentials or an unreachable database port. Instead repair source connectivity and credential reference and validate one catalog table refresh.
B:Embed a permanent production database password in a public crawler description. A valid crawler schedule cannot overcome expired credentials or an unreachable database port. Instead repair source connectivity and credential reference and validate one catalog table refresh.
C:Assume S3 ListBucket permission alone grants JDBC database privileges. A valid crawler schedule cannot overcome expired credentials or an unreachable database port. Instead repair source connectivity and credential reference and validate one catalog table refresh.
Question 594
A lake keeps old immutable daily files in S3 Standard although queries rarely access records older than a year. What architecture action addresses the stated source-to-target behavior?
- Assume every S3 class allows identical immediate SQL access without retrieval.
- Delete all recent objects because their key names contain an old year.
- Configure S3 Lifecycle transitions consistent with access frequency, minimum durations and retrieval latency.
- Choose a Glacier archive tier solely from the size of one object.
Explanation
Correct Answer
C:This directly addresses S3 Lifecycle tier transition by access pattern. S3 storage classes trade storage cost against retrieval charges, minimum duration and access behavior.
Incorrect Answers
A:Blindly transitioning hot data to archival classes can increase end-to-end query cost and delay access. This does not meet S3 Lifecycle tier transition by access pattern.
B:Delete all recent objects because their key names contain an old year. S3 storage classes trade storage cost against retrieval charges, minimum duration and access behavior. Inspect object age, storage-class inventory, lifecycle rule filters, retrieval fees and query frequency.
D:Blindly transitioning hot data to archival classes can increase end-to-end query cost and delay access. The appropriate action is to configure S3 Lifecycle transitions consistent with access frequency, minimum durations and retrieval latency.
Question 595
A lake keeps old immutable daily files in S3 Standard although queries rarely access records older than a year. What validation evidence distinguishes a correct implementation from a dashboard-only change?
- A resource ARN alone without any current data-plane observation.
- A dashboard color with no source event or data row evidence.
- A browser screenshot from another AWS account and time period.
- Object age, storage-class inventory, lifecycle rule filters, retrieval fees and query frequency.
Explanation
Correct Answer
D:These observations directly test S3 Lifecycle tier transition by access pattern. S3 storage classes trade storage cost against retrieval charges, minimum duration and access behavior.
Incorrect Answers
A:A resource ARN alone without any current data-plane observation. This is not sufficient evidence for S3 Lifecycle tier transition by access pattern. Check object age, storage-class inventory, lifecycle rule filters, retrieval fees and query frequency. S3 storage classes trade storage cost against retrieval charges, minimum duration and access behavior.
B:A dashboard color with no source event or data row evidence. This is not sufficient evidence for S3 Lifecycle tier transition by access pattern. Check object age, storage-class inventory, lifecycle rule filters, retrieval fees and query frequency. S3 storage classes trade storage cost against retrieval charges, minimum duration and access behavior.
C:A browser screenshot from another AWS account and time period. This is not sufficient evidence for S3 Lifecycle tier transition by access pattern. Check object age, storage-class inventory, lifecycle rule filters, retrieval fees and query frequency. S3 storage classes trade storage cost against retrieval charges, minimum duration and access behavior.
Question 596
A lake keeps old immutable daily files in S3 Standard although queries rarely access records older than a year. Which design principle is consistent with the stated data-processing contract?
- S3 storage classes trade storage cost against retrieval charges, minimum duration and access behavior.
- An S3 bucket prefix guarantees exactly-once multi-service transactions without an output commit.
- A CloudWatch metric label is equivalent to a successful target table data-quality validation.
- Every AWS managed service uses the same consistency, retry and query-processing semantics.
Explanation
Correct Answer
A:Implement by choosing to configure S3 Lifecycle transitions consistent with access frequency, minimum durations and retrieval latency. This is the relevant technical mechanism for S3 Lifecycle tier transition by access pattern.
Incorrect Answers
B:An S3 bucket prefix guarantees exactly-once multi-service transactions without an output commit. That generalization conflicts with S3 Lifecycle tier transition by access pattern. Instead s3 storage classes trade storage cost against retrieval charges, minimum duration and access behavior. Check object age, storage-class inventory, lifecycle rule filters, retrieval fees and query frequency.
C:A CloudWatch metric label is equivalent to a successful target table data-quality validation. That generalization conflicts with S3 Lifecycle tier transition by access pattern. Instead s3 storage classes trade storage cost against retrieval charges, minimum duration and access behavior. Check object age, storage-class inventory, lifecycle rule filters, retrieval fees and query frequency.
D:Every AWS managed service uses the same consistency, retry and query-processing semantics. That generalization conflicts with S3 Lifecycle tier transition by access pattern. Instead s3 storage classes trade storage cost against retrieval charges, minimum duration and access behavior. Check object age, storage-class inventory, lifecycle rule filters, retrieval fees and query frequency.
Question 597
A lake keeps old immutable daily files in S3 Standard although queries rarely access records older than a year. An incorrect proposal is: Assume every S3 class allows identical immediate SQL access without retrieval. What issue should reviewers anticipate if the shortcut is adopted?
- The presence of an accurate job timestamp automatically created unauthorized database credentials.
- Inspecting an existing Athena query plan itself deleted every production table.
- The dashboard theme independently caused an unrelated source database failure.
- Blindly transitioning hot data to archival classes can increase end-to-end query cost and delay access.
Explanation
Correct Answer
D:This is why the incorrect shortcut does not meet S3 Lifecycle tier transition by access pattern. S3 storage classes trade storage cost against retrieval charges, minimum duration and access behavior.
Incorrect Answers
A:The presence of an accurate job timestamp automatically created unauthorized database credentials. That unrelated assertion does not explain the actual S3 Lifecycle tier transition by access pattern risk. The relevant failure is that blindly transitioning hot data to archival classes can increase end-to-end query cost and delay access. Check object age, storage-class inventory, lifecycle rule filters, retrieval fees and query frequency.
B:Inspecting an existing Athena query plan itself deleted every production table. That unrelated assertion does not explain the actual S3 Lifecycle tier transition by access pattern risk. The relevant failure is that blindly transitioning hot data to archival classes can increase end-to-end query cost and delay access. Check object age, storage-class inventory, lifecycle rule filters, retrieval fees and query frequency.
C:The dashboard theme independently caused an unrelated source database failure. That unrelated assertion does not explain the actual S3 Lifecycle tier transition by access pattern risk. The relevant failure is that blindly transitioning hot data to archival classes can increase end-to-end query cost and delay access. Check object age, storage-class inventory, lifecycle rule filters, retrieval fees and query frequency.
Question 598
A lake keeps old immutable daily files in S3 Standard although queries rarely access records older than a year. The observed failure is: Blindly transitioning hot data to archival classes can increase end-to-end query cost and delay access. Which response repairs the underlying problem without unnecessary privilege or data loss?
- Delete all recent objects because their key names contain an old year.
- Choose a Glacier archive tier solely from the size of one object.
- Simulate lifecycle costs and test a restored older partition before broad transition.
- Assume every S3 class allows identical immediate SQL access without retrieval.
Explanation
Correct Answer
C:This addresses the observed S3 Lifecycle tier transition by access pattern failure while preserving the required contract. S3 storage classes trade storage cost against retrieval charges, minimum duration and access behavior.
Incorrect Answers
A:Delete all recent objects because their key names contain an old year. Blindly transitioning hot data to archival classes can increase end-to-end query cost and delay access. Instead simulate lifecycle costs and test a restored older partition before broad transition.
B:Choose a Glacier archive tier solely from the size of one object. Blindly transitioning hot data to archival classes can increase end-to-end query cost and delay access. Instead simulate lifecycle costs and test a restored older partition before broad transition.
D:Assume every S3 class allows identical immediate SQL access without retrieval. Blindly transitioning hot data to archival classes can increase end-to-end query cost and delay access. Instead simulate lifecycle costs and test a restored older partition before broad transition.
Question 599
A transition rule moves frequently queried parquet partitions to a storage class with unexpected retrieval costs. Which AWS design or configuration BEST satisfies the stated processing requirement?
- In this operational case, delete all recent objects because their key names contain an old year.
- In this operational case, choose a Glacier archive tier solely from the size of one object.
- In this operational case, configure S3 Lifecycle transitions consistent with access frequency, minimum durations and retrieval latency.
- In this operational case, assume every S3 class allows identical immediate SQL access without retrieval.
Explanation
Correct Answer
C:This directly addresses S3 Lifecycle tier transition by access pattern. Validate with object age, storage-class inventory, lifecycle rule filters, retrieval fees and query frequency.
Incorrect Answers
A:Delete all recent objects because their key names contain an old year. S3 storage classes trade storage cost against retrieval charges, minimum duration and access behavior. Inspect object age, storage-class inventory, lifecycle rule filters, retrieval fees and query frequency.
B:Blindly transitioning hot data to archival classes can increase end-to-end query cost and delay access. Choose a Glacier archive tier solely from the size of one object.
D:Blindly transitioning hot data to archival classes can increase end-to-end query cost and delay access. The supported design is to configure S3 Lifecycle transitions consistent with access frequency, minimum durations and retrieval latency.
Question 600
A transition rule moves frequently queried parquet partitions to a storage class with unexpected retrieval costs. Which evidence would BEST verify that the intended pipeline outcome occurred?
- The relevant validation evidence is a successful ping to an unrelated service that did not process the data.
- The relevant validation evidence is object age, storage-class inventory, lifecycle rule filters, retrieval fees and query frequency.
- The relevant validation evidence is a resource ARN alone without any current data-plane observation.
- The relevant validation evidence is a dashboard color with no source event or data row evidence.
Explanation
Correct Answer
B:These observations directly test S3 Lifecycle tier transition by access pattern. In this specific operating situation, a transition rule moves frequently queried parquet partitions to a storage class with unexpected retrieval costs.
Incorrect Answers
A:A successful ping to an unrelated service that did not process the data. This is not sufficient evidence for S3 Lifecycle tier transition by access pattern. Check object age, storage-class inventory, lifecycle rule filters, retrieval fees and query frequency. S3 storage classes trade storage cost against retrieval charges, minimum duration and access behavior.
C:A resource ARN alone without any current data-plane observation. This is not sufficient evidence for S3 Lifecycle tier transition by access pattern. Check object age, storage-class inventory, lifecycle rule filters, retrieval fees and query frequency. S3 storage classes trade storage cost against retrieval charges, minimum duration and access behavior.
D:A dashboard color with no source event or data row evidence. This is not sufficient evidence for S3 Lifecycle tier transition by access pattern. Check object age, storage-class inventory, lifecycle rule filters, retrieval fees and query frequency. S3 storage classes trade storage cost against retrieval charges, minimum duration and access behavior.