Amazon AWS Certified Data Engineer - Associate DEA-C01 Practice Test 57
Question 560
A cross-account Data Catalog table is visible but Athena rejects access to the referenced S3 objects. Which AWS design or configuration BEST satisfies the stated processing requirement?
- In this operational case, configure supported catalog resource sharing and cross-account permissions for both metadata and underlying data.
- In this operational case, assume a Glue resource link creates a copied dataset by itself.
- In this operational case, grant all consumer accounts AdministratorAccess as a general sharing solution.
- In this operational case, make the producer S3 bucket publicly readable to fix resource links.
Explanation
Correct Answer
A:Validate with catalog resource link, LF grants, S3 bucket policy, KMS permissions and Athena authorization trace. This directly addresses Cross-account Glue catalog and Lake Formation resource links.
Incorrect Answers
B:Assume a Glue resource link creates a copied dataset by itself. Catalog visibility and permission to read underlying governed data are independent controls. Inspect catalog resource link, LF grants, S3 bucket policy, KMS permissions and Athena authorization trace.
C:Granting a Data Catalog table name alone cannot bypass missing S3 or KMS access. In this specific operating situation, a cross-account Data Catalog table is visible but Athena rejects access to the referenced S3 objects.
D:This does not meet Cross-account Glue catalog and Lake Formation resource links. The supported design is to configure supported catalog resource sharing and cross-account permissions for both metadata and underlying data.
Question 561
A cross-account Data Catalog table is visible but Athena rejects access to the referenced S3 objects. Which evidence would BEST verify that the intended pipeline outcome occurred?
- 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.
- The relevant validation evidence is catalog resource link, LF grants, S3 bucket policy, KMS permissions and Athena authorization trace.
Explanation
Correct Answer
D:Catalog visibility and permission to read underlying governed data are independent controls.
Incorrect Answers
A:A resource ARN alone without any current data-plane observation. This is not sufficient evidence for Cross-account Glue catalog and Lake Formation resource links. Check catalog resource link, LF grants, S3 bucket policy, KMS permissions and Athena authorization trace. Catalog visibility and permission to read underlying governed data are independent controls.
B:A renamed resource label that does not show an authorization or processing result. This is not sufficient evidence for Cross-account Glue catalog and Lake Formation resource links. Check catalog resource link, LF grants, S3 bucket policy, KMS permissions and Athena authorization trace. Catalog visibility and permission to read underlying governed data are independent controls.
C:A browser screenshot from another AWS account and time period. This is not sufficient evidence for Cross-account Glue catalog and Lake Formation resource links. Check catalog resource link, LF grants, S3 bucket policy, KMS permissions and Athena authorization trace. Catalog visibility and permission to read underlying governed data are independent controls.
Question 562
A cross-account Data Catalog table is visible but Athena rejects access to the referenced S3 objects. Which underlying AWS service principle BEST explains the recommended approach?
- The governing design principle is that a pipeline schedule guarantees that every downstream source record was processed correctly.
- The governing design principle is that catalog visibility and permission to read underlying governed data are independent controls.
- 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 every AWS managed service uses the same consistency, retry and query-processing semantics.
Explanation
Correct Answer
B:Implement by choosing to configure supported catalog resource sharing and cross-account permissions for both metadata and underlying data. This is the relevant technical mechanism for Cross-account Glue catalog and Lake Formation resource links.
Incorrect Answers
A:A pipeline schedule guarantees that every downstream source record was processed correctly. That generalization conflicts with Cross-account Glue catalog and Lake Formation resource links. Instead catalog visibility and permission to read underlying governed data are independent controls. Check catalog resource link, LF grants, S3 bucket policy, KMS permissions and Athena authorization trace.
C:A CloudWatch metric label is equivalent to a successful target table data-quality validation. That generalization conflicts with Cross-account Glue catalog and Lake Formation resource links. Instead catalog visibility and permission to read underlying governed data are independent controls. Check catalog resource link, LF grants, S3 bucket policy, KMS permissions and Athena authorization trace.
D:Every AWS managed service uses the same consistency, retry and query-processing semantics. That generalization conflicts with Cross-account Glue catalog and Lake Formation resource links. Instead catalog visibility and permission to read underlying governed data are independent controls. Check catalog resource link, LF grants, S3 bucket policy, KMS permissions and Athena authorization trace.
Question 563
A cross-account Data Catalog table is visible but Athena rejects access to the referenced S3 objects. An incorrect proposal is: Make the producer S3 bucket publicly readable to fix resource links. What material risk would follow from the proposed incorrect shortcut?
- The concrete failure is that granting a Data Catalog table name alone cannot bypass missing S3 or KMS access.
- 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.
Explanation
Correct Answer
A:The safer implementation is to configure supported catalog resource sharing and cross-account permissions for both metadata and underlying data.
Incorrect Answers
B:That unrelated assertion does not explain the actual Cross-account Glue catalog and Lake Formation resource links risk. The relevant failure is that granting a Data Catalog table name alone cannot bypass missing S3 or KMS access.
C:That unrelated assertion does not explain the actual Cross-account Glue catalog and Lake Formation resource links risk. Check catalog resource link, LF grants, S3 bucket policy, KMS permissions and Athena authorization trace.
D:That unrelated assertion does not explain the actual Cross-account Glue catalog and Lake Formation resource links risk.
Question 564
A cross-account Data Catalog table is visible but Athena rejects access to the referenced S3 objects. The observed failure is: Granting a Data Catalog table name alone cannot bypass missing S3 or KMS access. Which recovery action BEST restores the required data-processing state?
- The supported recovery step is to validate metadata discovery and an actual governed query using the consumer role.
- The supported recovery step is to grant all consumer accounts AdministratorAccess as a general sharing solution.
- The supported recovery step is to make the producer S3 bucket publicly readable to fix resource links.
- The supported recovery step is to assume a Glue resource link creates a copied dataset by itself.
Explanation
Correct Answer
A:This addresses the observed Cross-account Glue catalog and Lake Formation resource links failure while preserving the required contract. Recheck catalog resource link, LF grants, S3 bucket policy, KMS permissions and Athena authorization trace.
Incorrect Answers
B:Grant all consumer accounts AdministratorAccess as a general sharing solution. Granting a Data Catalog table name alone cannot bypass missing S3 or KMS access. Instead validate metadata discovery and an actual governed query using the consumer role.
C:Make the producer S3 bucket publicly readable to fix resource links. Granting a Data Catalog table name alone cannot bypass missing S3 or KMS access. Instead validate metadata discovery and an actual governed query using the consumer role.
D:Assume a Glue resource link creates a copied dataset by itself. Granting a Data Catalog table name alone cannot bypass missing S3 or KMS access. Instead validate metadata discovery and an actual governed query using the consumer role.
Question 565
An EMR Hive workload and an Athena workload reference inconsistent schema definitions for the same S3 tables. Which AWS design or configuration BEST satisfies the stated processing requirement?
- Assume an S3 bucket name alone synchronizes all Hive metastore schemas.
- Copy only table titles without partition metadata during catalog migration.
- Use a supported shared catalog or synchronized Hive-compatible metadata integration with consistent table and partition definitions.
- Ignore schema mismatches because both engines can list the same files.
Explanation
Correct Answer
C:Validate with metastore endpoint, Glue catalog IDs, table schema, partition count and query parity across engines. Analytical engines must agree on table metadata to interpret shared S3 data consistently.
Incorrect Answers
A:This does not meet Apache Hive metastore compatibility with AWS Glue catalog. Allowing two independent mutable catalog sources to drift can return incompatible query results.
B:Copy only table titles without partition metadata during catalog migration. Analytical engines must agree on table metadata to interpret shared S3 data consistently. Inspect metastore endpoint, Glue catalog IDs, table schema, partition count and query parity across engines.
D:Allowing two independent mutable catalog sources to drift can return incompatible query results. The appropriate action is to use a supported shared catalog or synchronized Hive-compatible metadata integration with consistent table and partition definitions.
Question 566
An EMR Hive workload and an Athena workload reference inconsistent schema definitions for the same S3 tables. Which evidence would BEST verify that the intended pipeline outcome occurred?
- 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.
- Metastore endpoint, Glue catalog IDs, table schema, partition count and query parity across engines.
Explanation
Correct Answer
D:Analytical engines must agree on table metadata to interpret shared S3 data consistently. These observations directly test Apache Hive metastore compatibility with AWS Glue catalog.
Incorrect Answers
A:A resource ARN alone without any current data-plane observation. This is not sufficient evidence for Apache Hive metastore compatibility with AWS Glue catalog. Check metastore endpoint, Glue catalog IDs, table schema, partition count and query parity across engines. Analytical engines must agree on table metadata to interpret shared S3 data consistently.
B:A dashboard color with no source event or data row evidence. This is not sufficient evidence for Apache Hive metastore compatibility with AWS Glue catalog. Check metastore endpoint, Glue catalog IDs, table schema, partition count and query parity across engines. Analytical engines must agree on table metadata to interpret shared S3 data consistently.
C:A browser screenshot from another AWS account and time period. This is not sufficient evidence for Apache Hive metastore compatibility with AWS Glue catalog. Check metastore endpoint, Glue catalog IDs, table schema, partition count and query parity across engines. Analytical engines must agree on table metadata to interpret shared S3 data consistently.
Question 567
An EMR Hive workload and an Athena workload reference inconsistent schema definitions for the same S3 tables. Which underlying AWS service principle BEST explains the recommended approach?
- 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.
- Analytical engines must agree on table metadata to interpret shared S3 data consistently.
- Every AWS managed service uses the same consistency, retry and query-processing semantics.
Explanation
Correct Answer
C:This is the relevant technical mechanism for Apache Hive metastore compatibility with AWS Glue catalog.
Incorrect Answers
A:An S3 bucket prefix guarantees exactly-once multi-service transactions without an output commit. That generalization conflicts with Apache Hive metastore compatibility with AWS Glue catalog. Instead analytical engines must agree on table metadata to interpret shared S3 data consistently. Check metastore endpoint, Glue catalog IDs, table schema, partition count and query parity across engines.
B:A CloudWatch metric label is equivalent to a successful target table data-quality validation. That generalization conflicts with Apache Hive metastore compatibility with AWS Glue catalog. Instead analytical engines must agree on table metadata to interpret shared S3 data consistently. Check metastore endpoint, Glue catalog IDs, table schema, partition count and query parity across engines.
D:Every AWS managed service uses the same consistency, retry and query-processing semantics. That generalization conflicts with Apache Hive metastore compatibility with AWS Glue catalog. Instead analytical engines must agree on table metadata to interpret shared S3 data consistently. Check metastore endpoint, Glue catalog IDs, table schema, partition count and query parity across engines.
Question 568
An EMR Hive workload and an Athena workload reference inconsistent schema definitions for the same S3 tables. An incorrect proposal is: Assume an S3 bucket name alone synchronizes all Hive metastore schemas. What material risk would follow from the proposed incorrect shortcut?
- The presence of an accurate job timestamp automatically created unauthorized database credentials.
- Inspecting an existing Athena query plan itself deleted every production table.
- Allowing two independent mutable catalog sources to drift can return incompatible query results.
- The dashboard theme independently caused an unrelated source database failure.
Explanation
Correct Answer
C:This is why the incorrect shortcut does not meet Apache Hive metastore compatibility with AWS Glue catalog.
Incorrect Answers
A:The presence of an accurate job timestamp automatically created unauthorized database credentials. That unrelated assertion does not explain the actual Apache Hive metastore compatibility with AWS Glue catalog risk. The relevant failure is that allowing two independent mutable catalog sources to drift can return incompatible query results. Check metastore endpoint, Glue catalog IDs, table schema, partition count and query parity across engines.
B:Inspecting an existing Athena query plan itself deleted every production table. That unrelated assertion does not explain the actual Apache Hive metastore compatibility with AWS Glue catalog risk. The relevant failure is that allowing two independent mutable catalog sources to drift can return incompatible query results. Check metastore endpoint, Glue catalog IDs, table schema, partition count and query parity across engines.
D:The dashboard theme independently caused an unrelated source database failure. That unrelated assertion does not explain the actual Apache Hive metastore compatibility with AWS Glue catalog risk. The relevant failure is that allowing two independent mutable catalog sources to drift can return incompatible query results. Check metastore endpoint, Glue catalog IDs, table schema, partition count and query parity across engines.
Question 569
An EMR Hive workload and an Athena workload reference inconsistent schema definitions for the same S3 tables. The observed failure is: Allowing two independent mutable catalog sources to drift can return incompatible query results. Which recovery action BEST restores the required data-processing state?
- Copy only table titles without partition metadata during catalog migration.
- Ignore schema mismatches because both engines can list the same files.
- Reconcile catalog metadata and compare representative Hive and Athena read results.
- Assume an S3 bucket name alone synchronizes all Hive metastore schemas.
Explanation
Correct Answer
C:This addresses the observed Apache Hive metastore compatibility with AWS Glue catalog failure while preserving the required contract.
Incorrect Answers
A:Copy only table titles without partition metadata during catalog migration. Allowing two independent mutable catalog sources to drift can return incompatible query results. Instead reconcile catalog metadata and compare representative Hive and Athena read results.
B:Ignore schema mismatches because both engines can list the same files. Allowing two independent mutable catalog sources to drift can return incompatible query results. Instead reconcile catalog metadata and compare representative Hive and Athena read results.
D:Assume an S3 bucket name alone synchronizes all Hive metastore schemas. Allowing two independent mutable catalog sources to drift can return incompatible query results. Instead reconcile catalog metadata and compare representative Hive and Athena read results.
Question 570
A migration from a self-managed Hive metastore to Glue causes wrong partition metadata for downstream jobs. What is the MOST appropriate targeted implementation for this data-engineering situation?
- In this operational case, use a supported shared catalog or synchronized Hive-compatible metadata integration with consistent table and partition definitions.
- In this operational case, copy only table titles without partition metadata during catalog migration.
- In this operational case, ignore schema mismatches because both engines can list the same files.
- In this operational case, assume an S3 bucket name alone synchronizes all Hive metastore schemas.
Explanation
Correct Answer
A:Validate with metastore endpoint, Glue catalog IDs, table schema, partition count and query parity across engines. This directly addresses Apache Hive metastore compatibility with AWS Glue catalog.
Incorrect Answers
B:Copy only table titles without partition metadata during catalog migration. Analytical engines must agree on table metadata to interpret shared S3 data consistently. Inspect metastore endpoint, Glue catalog IDs, table schema, partition count and query parity across engines.
C:Allowing two independent mutable catalog sources to drift can return incompatible query results. Ignore schema mismatches because both engines can list the same files.
D:This does not meet Apache Hive metastore compatibility with AWS Glue catalog. The supported design is to use a supported shared catalog or synchronized Hive-compatible metadata integration with consistent table and partition definitions.