New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Amazon BDS-C00 Exam - 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:

0/2000 characters
Truman
3 months ago
Not sure about that, seems like a hassle to create a new config.
upvoted 0 times
...
Omer
3 months ago
Wait, isn't there a way to just enable it in the console?
upvoted 0 times
...
Kattie
4 months ago
Actually, you can also update the existing config with the CLI.
upvoted 0 times
...
Chantell
4 months ago
I agree, option D is the way to go!
upvoted 0 times
...
Charlene
4 months ago
You need to create a new Launch Config for detailed monitoring.
upvoted 0 times
...
Christiane
4 months ago
I believe you can change settings in the AWS console, but I’m not sure if that applies to launch configurations specifically.
upvoted 0 times
...
Dannette
4 months ago
I’m a bit confused about the CLI options. Was it InstanceMonitoringDisabled or something else we had to set to enable detailed monitoring?
upvoted 0 times
...
Antonette
5 months ago
I think I practiced a similar question where we had to enable monitoring, and I feel like creating a new launch config was the right approach.
upvoted 0 times
...
Janey
5 months ago
I remember something about launch configurations, but I'm not sure if you can just update them directly for monitoring settings.
upvoted 0 times
...
Merlyn
5 months ago
This seems like a straightforward question about auditing sales invoices and shipping documents. I'll need to carefully review the options and think through the typical errors an auditor would be checking for.
upvoted 0 times
...
Josefa
5 months ago
I'm a bit stumped on this one. I know SD-WAN uses some kind of routing protocol, but I can't recall which one off the top of my head. I'll have to think about it or maybe try to eliminate some of the options.
upvoted 0 times
...
Lorrie
5 months ago
This seems like a straightforward question about tracking customer relationships. I think I'll go with option C - adding the related company to the first company's partner related list with supplier as the value.
upvoted 0 times
...
Benton
5 months ago
I feel like the with statement is related to catching errors as well. Maybe option D could be right? I can't recall if it specifically handles exceptions for NETCONF connections.
upvoted 0 times
...
Eileen
10 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
8 months ago
The user should have known that disabling detailed monitoring in the launch config would affect the entire group.
upvoted 0 times
...
Ollie
8 months ago
I agree, updating the Launch config with CLI to set InstanceMonitoring.Enabled = true is the way to go.
upvoted 0 times
...
Kimberlie
8 months ago
Option C is the correct way to enable detailed monitoring in the launch configuration.
upvoted 0 times
...
...
Quiana
10 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
Yoko
8 months ago
Thanks for the advice, I'll go ahead and update the Launch config with Option C.
upvoted 0 times
...
Donte
8 months ago
That makes sense, it's a simple update without having to change the Auto Scaling group or create a new launch config.
upvoted 0 times
...
Javier
8 months ago
Agreed, updating the Launch config with CLI to set InstanceMonitoring.Enabled = true is the most straightforward solution.
upvoted 0 times
...
King
8 months ago
I think Option C is the way to go.
upvoted 0 times
...
Jeff
9 months ago
Great, thanks for the advice. I'll go ahead and update the Launch config with Option C.
upvoted 0 times
...
Felton
9 months ago
I agree. It's the most straightforward way to enable detailed monitoring.
upvoted 0 times
...
Alex
10 months ago
That makes sense. It's a simple solution without having to change the Auto Scaling group.
upvoted 0 times
...
Noah
10 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
10 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
10 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
10 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
10 months ago
Yes, I agree. That's the way to go to enable detailed monitoring for the Auto Scaling group.
upvoted 0 times
...
Ira
10 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
10 months ago
I agree with Lelia. That seems like the correct way to enable detailed monitoring.
upvoted 0 times
...
Sylvie
10 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
10 months ago
I think the user should update the Launch config with CLI to set InstanceMonitoring.Enabled = true.
upvoted 0 times
...
Sabrina
11 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
11 months ago
I agree with Yaeko. That seems like the correct way to enable detailed monitoring.
upvoted 0 times
...
Yaeko
11 months ago
I think the user should update the Launch config with CLI to set InstanceMonitoring.Enabled = true.
upvoted 0 times
...

Save Cancel