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

B. AWS DMS is not for this purpose, so A dropped. C would be costly since it literally replicates all data. There’s no “resource policies” in AWS Glue, so D dropped.

B is correct as AWS Glue can crawl data in different AWS Regions. When you define an Amazon S3 data store to crawl, you can choose whether to crawl a path in your account or another account. The output of the crawler is one or more metadata tables defined in the AWS Glue Data Catalog. A table is created for one or more files found in your data store. If all the Amazon S3 files in a folder have the same schema, the crawler creates one table. Also, if the Amaazon S3 object is partitioned, only one metadata table is created. A is wrong because you can't use AWS DMS with AWS Glue Data Catalog. C is incorrect because replicating the data in S3 means that your storage costs will also double. D is wrong because a resource-based policy is primarily used to provide IAM users and roles granular access to metadata definitions of databases, tables, connections, and user-defined functions, and not the actual S3 data.

A: DMS is not required to migrate data from one region to another. It can even be used to migrate data from an S3 bucket to another bucket in another account, but there are better and cheaper ways to do this (considering the volume of data, of course). B: It is the correct alternative. Glue crawlers can catalog data that is in different regions. It's simple to set up and not expensive. C: Cross-region works for data replication, but it will be duplicated unnecessarily. D: This type of permissions is best suited for LakeFormation and would not help catalog data that is in different regions.

Option D https://aws.amazon.com/blogs/big-data/configure-cross-region-table-access-with-the-aws-glue-catalog-and-aws-lake-formation/

going w B

B. Source: https://docs.aws.amazon.com/glue/latest/dg/crawler-data-stores.html. You can choose to crawl a path in your account or in another account. Crawlers use an AWS Identity and Access Management (IAM) role for permission to access your data stores. The role you pass to the crawler must have permission to access Amazon S3 paths and Amazon DynamoDB tables that are crawled. Another source: https://docs.aws.amazon.com/athena/latest/ug/querying-across-regions.html. Athena can query cross-region Athena supports the ability to query Amazon S3 data in an AWS Region that is different from the Region in which you are using Athena. Querying across Regions can be an option when moving the data is not practical or permissible, or if you want to query data across multiple regions. Even if Athena is not available in a particular Region, data from that Region can be queried from another Region in which Athena is available.

B is correct for context of this question but will be a bad implementation in real life. D can be good pattern but with help of Lakeformation.

B: I passed the test

the data is not encrypted so moving data is not "practical or permissible"?

D should be...

A, B, D simply wouldn't work because of lacking connection to the data source. The only thing that I am not sure is about the 'lowest cost'. It can be option B if the wording implies that the connectivity exits https://aws.amazon.com/blogs/big-data/create-cross-account-and-cross-region-aws-glue-connections/

D. See: https://docs.aws.amazon.com/glue/latest/dg/cross-account-access.html

That's why D is wrong? Each AWS account owns a single catalog in an AWS Region whose catalog ID is the same as the AWS account ID https://docs.aws.amazon.com/glue/latest/dg/glue-resource-policies.html

Both B and D will work. The answer is B because option D is a bit more expensive.

Must be D

B is correct D is wrong because there is no resource policies but only trust policy.

The lowest cost option is B. All other options are involved with greater cost, as data migration between regions costs more.