Exam AWS Certified Data Analytics - Specialty topic 1 question 66 discussion

C. https://docs.aws.amazon.com/glue/latest/dg/tables-described.html In this section : Updating Manually Created Data Catalog Tables Using Crawlers "The following are other reasons why you might want to manually create catalog tables and specify catalog tables as the crawler source: You want to choose the catalog table name and not rely on the catalog table naming algorithm. "

I think Option A is correct. AWS Glue crawlers automatically scan data in S3, recognize the format and schema, and create metadata tables in the AWS Glue Data Catalog. This eliminates manual schema definition, table creation and meets new partitions with minimal effort. We can specify the database in which the tables are created and control the naming of the tables through the crawler's configuration settings rather than relying on an automated naming algorithm. As new data is added to S3 in hourly, daily, and yearly partitions, running the crawler at regular intervals ensures that new partitions are discovered and added to the respective Data Catalog tables automatically. Option C uses the AWS Glue API to create a table, which is more manual than allowing a crawler to discover and manage tables and does not automatically address the ongoing discovery of new partitions.

C: I passed the test

Correct answer is C as the AWS Glue API CreateTable operation can be used to create a table in the Data Catalog and the AWS Glue crawler can be created and the table as the source can be specified. This meets the requirement of catalog table names and keeping the table updated with new data. B is incorrect. Although creating a new catalog table is right, the use of a Lambda function to update the table partitions entails a lot of development work. Remember that it is explicitly stated in the scenario that the solution should be implemented with the least configuration overhead. A is incorrect because you must create a new catalog table if you do not want to rely on the catalog table naming algorithm provided by AWS Glue. D is incorrect because this solution entails a lot of effort. A better and easier solution is to just create a new table in AWS Glue Data Catalog and set up an AWS Glue crawler.

The following are other reasons why you might want to manually create catalog tables and specify catalog tables as the crawler source: You want to choose the catalog table name and not rely on the catalog table naming algorithm. You want to prevent new tables from being created in the case where files with a format that could disrupt partition detection are mistakenly saved in the data source path.

Answer is C

My Answer is C

You need to use the API to be able to provide a custom name

https://docs.aws.amazon.com/glue/latest/dg/tables-described.html#update-manual-tables

Answer should be C.

C as per the linked provided not B read "Updating Manually Created Data Catalog Tables Using Crawlers" https://docs.aws.amazon.com/glue/latest/dg/tables-described.html

C is the right answer

I think there might be a miss typo in C, the table needs to be defined as target and not source

C for me.

Answer should be C.

Answer is C

Answer is C.