Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Amazon Exam BDS-C00 Topic 3 Question 77 Discussion

Actual exam question for Amazon's BDS-C00 exam
Question #: 77
Topic #: 3
[All BDS-C00 Questions]

A user has created a launch configuration for Auto Scaling where CloudWatch detailed monitoring is disabled. The user wants to now enable detailed monitoring. How can the user achieve this?

Show Suggested Answer Hide Answer
Suggested Answer: B

Contribute your Thoughts:

Eileen
1 months ago
The user should have known that disabling detailed monitoring in the launch config would disable it for the entire group. Option C FTW!
upvoted 0 times
Mitzie
22 hours ago
The user should have known that disabling detailed monitoring in the launch config would affect the entire group.
upvoted 0 times
...
Ollie
2 days ago
I agree, updating the Launch config with CLI to set InstanceMonitoring.Enabled = true is the way to go.
upvoted 0 times
...
Kimberlie
3 days ago
Option C is the correct way to enable detailed monitoring in the launch configuration.
upvoted 0 times
...
...
Quiana
2 months ago
Definitely go with Option C. Trying to change the Auto Scaling group or creating a new launch config seems like overkill.
upvoted 0 times
King
4 days ago
I think Option C is the way to go.
upvoted 0 times
...
Jeff
9 days ago
Great, thanks for the advice. I'll go ahead and update the Launch config with Option C.
upvoted 0 times
...
Felton
16 days ago
I agree. It's the most straightforward way to enable detailed monitoring.
upvoted 0 times
...
Alex
1 months ago
That makes sense. It's a simple solution without having to change the Auto Scaling group.
upvoted 0 times
...
Noah
2 months ago
Option C is the way to go. Just update the Launch config with CLI to set InstanceMonitoring.Enabled = true.
upvoted 0 times
...
...
Gwenn
2 months ago
Haha, I guess the user should have enabled detailed monitoring from the start. Gotta love those little oversights, right?
upvoted 0 times
...
Katy
2 months ago
I'm not sure. Maybe creating a new Launch Config with detail monitoring enabled and updating the Auto Scaling group could also work.
upvoted 0 times
...
Taryn
2 months ago
I agree with Sylvie. Option C is the correct answer here. Updating the launch config is the way to enable detailed monitoring.
upvoted 0 times
Reita
2 months ago
Yes, I agree. That's the way to go to enable detailed monitoring for the Auto Scaling group.
upvoted 0 times
...
Ira
2 months ago
I think option C is the correct answer. Updating the launch config with CLI to set InstanceMonitoring.Enabled = true will enable detailed monitoring.
upvoted 0 times
...
...
Glendora
2 months ago
I agree with Lelia. That seems like the correct way to enable detailed monitoring.
upvoted 0 times
...
Sylvie
2 months ago
Option C seems the most straightforward way to enable detailed monitoring. Updating the launch config directly is the way to go.
upvoted 0 times
...
Lelia
2 months ago
I think the user should update the Launch config with CLI to set InstanceMonitoring.Enabled = true.
upvoted 0 times
...
Sabrina
2 months ago
I'm not sure. Maybe creating a new Launch Config with detail monitoring enabled and updating the Auto Scaling group could also work.
upvoted 0 times
...
Elfrieda
2 months ago
I agree with Yaeko. That seems like the correct way to enable detailed monitoring.
upvoted 0 times
...
Yaeko
3 months ago
I think the user should update the Launch config with CLI to set InstanceMonitoring.Enabled = true.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77