FlexiToner uses AWS to query 10 years’ worth of historical data and get results, with the flexibility to explore data for deeper insights. Movable Ink provides real -time personalization of marketing emails based on a wide range of user, device, and contextual data, driving higher response rates and better customer experiences. Also FlexiToner hosts log files captured from web servers running out of different EC2 machines
FlexiToner has lot of data assets available in structured, semi-structured and unstructured data forms containing emails, logs, structured data from databases in csv files with formats in CSV, LOG, JSON and binary formats like Parquet and ORC. FlexiToner is interested to build a data lake out of all the files stored on S3 and provide Data Lake as a service to users from different departments based on pay per queries run. FlexiToner understands that Athena provides this facility OOTB.Consider the below structure in S3. When AWS Glue Crawler scans Amazon S3 and detects multiple directories, it uses a heuristic to determine where the root for a table is in the directory structure, and which directories are partitions for the table. What solutions are possible? Select 2 options.

Answer options:

A.If the schema for table1 and table2 are similar, and a single data source is set to
s3://bucket01/folder1/ in AWS Glue, the crawler may create a single table with two partition columns: one partition column that contains table1 and table2, and a second partition column that contains partition1 through partition5.
B.If the schema for table1 and table2 are similar, and uses different data source is set to
s3://bucket01/folder1/table1 and s3://bucket01/folder1/table2 in AWS Glue, the crawler may
create two tables
C.If the schema for table1 and table2 are similar, and uses different data sources is set to
s3://bucket01/folder1/table1 and s3://bucket01/folder1/table2 in AWS Glue, the crawler may create only one table
D.If the schema for table1 and table2 are similar, and a single data source is set to
s3://bucket01/folder1/ in AWS Glue, the crawler may create a single table with single partition
column: one partition column that contains table1 and table2

Answer: A, B
Option A is correct - When an AWS Glue Crawler scans Amazon S3 and detects multiple directories, it uses a heuristic to determine where the root for a table is in the directory structure, and which directories are partitions for the table. In some cases, where the schema detected in two or more directories is similar, the crawler may treat them as partitions instead of separate tables. One way to help the crawler discover individual tables is to add each table`s root directory as a data store for the crawler.
If the schema for table1 and table2 are similar, and a single data source is set to s3://bucket01/folder1/ in AWS Glue, the crawler may create a single table with two partition columns: one partition column that contains table1 and table2, and a second partition column that contains partition1 through partition5. 
https://docs.aws.amazon.com/athena/latest/ug/glue-best-practices.html
Option B is correct - When an AWS Glue Crawler scans Amazon S3 and detects multiple directories, it uses a heuristic to determine where the root for a table is in the directory structure, and which directories are partitions for the table. In some cases, where the schema detected in two or more directories is similar, the crawler may treat them as partitions instead of separate tables. One way to help the crawler discover individual tables is to add each table`s root directory as a data store for the crawler.
To have the AWS Glue crawler create two separate tables, set the crawler to have two data sources, s3://bucket01/folder1/table1/ and s3://bucket01/folder1/table2 
https://docs.aws.amazon.com/athena/latest/ug/glue-best-practices.html
Option C is incorrect - multiple directories, it uses a heuristic to determine where the root for a table is in the directory structure, and which directories are partitions for the table. In some cases, where the schema detected in two or more directories is similar, the crawler may treat them as partitions instead of separate tables. One way to help the crawler discover individual tables is to add each table`s root directory as a data store for the crawler.
To have the AWS Glue crawler create two separate tables, set the crawler to have two data sources, s3://bucket01/folder1/table1/ and s3://bucket01/folder1/table2 https://docs.aws.amazon.com/athena/latest/ug/glue-best-practices.html
Option D is incorrect - When an AWS Glue Crawler scans Amazon S3 and detects multiple directories, it uses a heuristic to determine where the root for a table is in the directory structure, and which directories are partitions for the table. In some cases, where the schema detected in two or more directories is similar, the crawler may treat them as partitions instead of separate tables. One way to help the crawler discover individual tables is to add each table`s root directory as a data store for the crawler.
If the schema for table1 and table2 are similar, and a single data source is set to s3://bucket01/folder1/ in AWS Glue, the crawler may create a single table with two partition columns: one partition column that contains table1 and table2, and a second partition column that contains partition1 through partition5. 
https://docs.aws.amazon.com/athena/latest/ug/glue-best-practices.html