you need to version control this processing job and al…

You need to run a very large batch data processing job one time per day. The source data exists entirely in S3, and the output of the processing job should also be written to S3 when finished. If you need to version control this processing job and all setup and teardown logic for the system, what approach should you use?

http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-emr-cluster.html

You need to run a very large batch data processing job one time per day. The source data exists entirely in S3, and the output of the processing job should also be written to S3 when finished. If you need to version control this processing job and all setup and teardown logic for the system, what approach should you use?

http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-emr-cluster.html

A.
Model an AWS EMR job in AWS Elastic Beanstalk.

B.
Model an AWS EMR job in AWS CloudFormation.

C.
Model an AWS EMR job in AWS OpsWorks.

D.
Model an AWS EMR job in AWS CLI Composer.

Explanation:
Explanation/Reference:
To declaratively model build and destroy of a cluster, you need to use AWS CloudFormation. OpsWorks and Elastic
Beanstalk cannot directly model EMR Clusters. The CLI is not declarative, and CLI Composer does not exist.



Leave a Reply 0

Your email address will not be published. Required fields are marked *