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

looks like 'A' it is.

Answer should be A, 1. Consistent View is no more required 2. Though schema is stable in this running Glue Crawler is one of the way to get the partition metadata updated

I think this question is just outdated. For what the question says, B should be the answer. A is too broad, as it doesn't mention that it needs something to trigger the crawler (like a Lambda). And it states that the schema is stable, so no need to run crawler all the time a file is updated. B doesn't need to mention s3 because the "enable consistent view" already means that! It's out dated because Amazon got rid off the consistent view from EMR. But looking 3 years back, B would be the perfect answer.

A: I passed the test

Answer is A

I think answer is A. It can also be that the question is bit outdated , as now S3 has strong read after write consistency , EMRFS consistent view might not make sense now.

I think it's A You no longer need to use EMRFS Consistent View as Amazon S3 supports strong read-after-write Consistency. See Strong read-after-write consistency. This works with all Amazon EMR versions. https://docs.aws.amazon.com/emr/latest/ManagementGuide/emr-plan-consistent-view.html

I believe it is B. The key point is "It is vital that the data from the reports and associated analytics is completely up to date based on the data in Amazon S3." EMRFS Consistent view allows EMR clusters to check for list and read-after-write consistency for Amazon S3 objects written by or synced with EMRFS. If you directly delete objects from Amazon S3 that are tracked in EMRFS metadata, EMRFS treats the object as inconsistent and throws an exception after it has exhausted retries. Use EMRFS to delete objects in Amazon S3 that are tracked using consistent view. Alternatively, you can use the emrfs command line to purge metadata entries for objects that have been directly deleted, or you can sync the consistent view with Amazon S3 immediately after you delete the objects. https://docs.aws.amazon.com/emr/latest/ManagementGuide/emr-plan-consistent-view.html To run Glue Crawlers when S3 is refreshed needs S3 Trigger Lambda functions that run the crawler. It seems too much of an overhead especially when EMRFS consistent view / sync command can maintain consistency with already provisioned EMR cluster.

Glue crawler is responsible for the schema definition , which is mentioned as stable in this case .A glue ETL job could have moved the data .Having said that , I go for B

B is correct. Because schema is stable, you don't need to run Glue crawler again. Moreover, data stored in S3 therefore EMRFS is needed and with consistent view, data is updated.

Correct Answer is A

Agree with A