Exam AWS Certified Machine Learning - Specialty All Questions

View all questions & answers for the AWS Certified Machine Learning - Specialty exam

Exam AWS Certified Machine Learning - Specialty topic 1 question 90 discussion

Exam question from Amazon's AWS Certified Machine Learning - Specialty

Question #: 90
Topic #: 1

[All AWS Certified Machine Learning - Specialty Questions]

A Machine Learning Specialist is planning to create a long-running Amazon EMR cluster. The EMR cluster will have 1 master node, 10 core nodes, and 20 task nodes. To save on costs, the Specialist will use Spot Instances in the EMR cluster.
Which nodes should the Specialist launch on Spot Instances?

A. Master node
B. Any of the core nodes
C. Any of the task nodes
D. Both core and task nodes

Show Suggested Answer

Suggested Answer: C 🗳️

by ac71 at Feb. 3, 2021, 4:01 a.m.

Disclaimers:

- ExamTopics website is not related to, affiliated with, endorsed or authorized by Amazon.
- Trademarks, certification & product names are used for reference only and belong to Amazon.

Comments

Submit Cancel

[Removed]

Highly Voted 2 years, 8 months ago

Answer is C. https://docs.aws.amazon.com/emr/latest/ManagementGuide/emr-plan-instances-guidelines.html

upvoted 23 times

Sneep

1 year, 5 months ago

It's definitely C. The fact that this site indicates A is a clear sign that answers are just randomly selected, it would make zero sense to spot-instance the master node for an EMR cluster. Make sure you look at discussions for all of these questions.

upvoted 4 times

...

SophieSu

Highly Voted 2 years, 8 months ago

C is the correct answer. "Long-Running Clusters and Data Warehouses If you are running a persistent Amazon EMR cluster that has a predictable variation in computational capacity, such as a data warehouse, you can handle peak demand at lower cost with Spot Instances. You can launch your master and core instance groups as On-Demand Instances to handle the normal capacity and launch task instance groups as Spot Instances to handle your peak load requirements."

upvoted 10 times

...

teka112233

Most Recent 10 months, 1 week ago

Selected Answer: C

According to :https://docs.aws.amazon.com/emr/latest/ManagementGuide/emr-plan-instances-guidelines.html The task nodes process data but do not hold persistent data in HDFS. If they terminate because the Spot price has risen above your maximum Spot price, no data is lost and the effect on your cluster is minimal. When you launch one or more task instance groups as Spot Instances, Amazon EMR provisions as many task nodes as it can, using your maximum Spot price. This means that if you request a task instance group with six nodes, and only five Spot Instances are available at or below your maximum Spot price, Amazon EMR launches the instance group with five nodes, adding the sixth later if possible.

upvoted 1 times

...

Khalil11

1 year, 2 months ago

Selected Answer: C

The correct answer is C

upvoted 1 times

...

Sylzys

1 year, 3 months ago

Selected Answer: C

I don't get why the wrong answer are still not updated after more than 1 year of everyone showing docs proving answer C..

upvoted 3 times

gusta_dantas

11 months, 1 week ago

1 and a half year and still wrong.. Incredible!

upvoted 2 times

...

AjoseO

1 year, 4 months ago

Selected Answer: C

Long-running clusters and data warehouses If you are running a persistent Amazon EMR cluster that has a predictable variation in computational capacity, such as a data warehouse, you can handle peak demand at lower cost with Spot Instances. You can launch your primary and core instance groups as On-Demand Instances to handle the normal capacity and launch the task instance group as Spot Instances to handle your peak load requirements.

upvoted 1 times

...

SK27

1 year, 6 months ago

Selected Answer: C

Only task nodes can be deleted without losing data.

upvoted 1 times

...

Twist3d

1 year, 6 months ago

C, If you want to cut cost on an EMR cluster in the most efficient way, use spot instances on the task nodes because it, task nodes do not store data so no risk of data loss

upvoted 1 times

...

ovokpus

2 years ago

Selected Answer: C

For Long running jobs, you do not want to compromise the Master node(sudden termination) or the core nodes (HDFS data loss). Spot Instances on 20 task nodes are enough cost savings without compromising the job. Hence, C

upvoted 3 times

...

Jump09

2 years ago

If your primary concern is the cost, then you can run the master node on spot instances.

upvoted 1 times

Jump09

2 years ago

Adding the related reference from the AWS documentation: Master node on a Spot Instance The master node controls and directs the cluster. When it terminates, the cluster ends, so you should only launch the master node as a Spot Instance if you are running a cluster where sudden termination is acceptable. This might be the case if you are testing a new application, have a cluster that periodically persists data to an external store such as Amazon S3, or are running a cluster where cost is more important than ensuring the cluster's completion.

upvoted 1 times

Jump09

2 years ago

In the question , there are no specific conditions mentioned except the concern with the COST, thus I think the answer should be A.

upvoted 1 times

...

benson2021

2 years, 8 months ago

Answer: C. https://aws.amazon.com/getting-started/hands-on/optimize-amazon-emr-clusters-with-ec2-spot/ Amazon recommends using On-Demand instances for Master and Core nodes unless you are launching highly ephemeral workloads.

upvoted 5 times

...

xpada001

2 years, 8 months ago

Answer should be C.

upvoted 3 times

...

ac71

2 years, 8 months ago

Only master node is incorrect. Either use all on spot or only task or core on spot. As per: https://docs.aws.amazon.com/emr/latest/ManagementGuide/emr-plan-instances-guidelines.html Better to use only task node on spot for long running tasks/jobs

upvoted 3 times

MahEid

2 years, 7 months ago

Answer is C you should only run core nodes on Spot Instances /*when partial HDFS data loss is tolerable*/ Question is what "Should" be launched as spot instance

upvoted 1 times

...