Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Amazon Exam DOP-C01 Topic 6 Question 87 Discussion

Actual exam question for Amazon's DOP-C01 exam
Question #: 87
Topic #: 6
[All DOP-C01 Questions]

A company is using tagging to allocate AWS costs. The company has Amazon EC2 instances that run in Auto Scaling groups. The Amazon Elastic Block Store (Amazon EBS) volumes that are attached to the EC2 instances are being created without the appropriate cost center tags. A DevOps engineer must ensure that the new EBS volumes are properly tagged.

What is the MOST efficient solution that meets this requirement?

Show Suggested Answer Hide Answer
Suggested Answer: B

Contribute your Thoughts:

Charlene
5 months ago
Alright, I see your point. Maybe option C is the way to go.
upvoted 0 times
...
Kaycee
6 months ago
I agree with Della, option C seems like the most effective solution.
upvoted 0 times
...
Della
6 months ago
Because setting the PropagateAtLaunch property to true ensures that all future EBS volumes will have the cost center tags.
upvoted 0 times
...
Charlene
6 months ago
Why do you think option C is better?
upvoted 0 times
...
Della
6 months ago
I disagree, I believe option C is more efficient.
upvoted 0 times
...
Charlene
6 months ago
I think option D is the best solution.
upvoted 0 times
...
Josefa
6 months ago
But wouldn't updating the Auto Scaling group launch template to include the cost center tags be more efficient in the long run?
upvoted 0 times
...
Devorah
7 months ago
I think using Tag Editor to search for EBS volumes that are missing the tags is the way to go. It's quick and direct.
upvoted 0 times
...
Lenora
7 months ago
I disagree, I believe creating a lifecycle hook on the autoscaling:EC2_INSTANCE_TERMINATING instance state is a better option.
upvoted 0 times
...
Josefa
7 months ago
I think the most efficient solution would be to update the Auto Scaling group to include the cost center tags and set PropagateAtLaunch to true.
upvoted 0 times
...
Magda
8 months ago
I can see the appeal of that, but I'm still not convinced it's the most efficient. What if we have a lot of existing volumes that need to be tagged?
upvoted 0 times
...
Corinne
8 months ago
That's a good idea, but it feels a bit manual. I'm still leaning towards the launch template solution. It's the most foolproof way to ensure all new volumes are properly tagged.
upvoted 0 times
...
Gayla
8 months ago
True, but then we'd have to remember to set the PropagateAtLaunch property. That could be easy to forget.
upvoted 0 times
...
Margarett
8 months ago
Ooh, good point. We definitely don't want to deal with that. Maybe option D is the way to go - using the Tag Editor to find and fix the untagged volumes.
upvoted 0 times
Alita
7 months ago
All set now. The new EBS volumes should be properly tagged for cost allocation.
upvoted 0 times
...
Terry
7 months ago
Great, let's get those cost center tags added to the volumes using Tag Editor.
upvoted 0 times
...
Kaitlyn
8 months ago
Agreed. Let's go ahead and use Tag Editor to fix the untagged EBS volumes.
upvoted 0 times
...
Kenneth
8 months ago
It will definitely help keep track of costs and allocations. Let's go with option D.
upvoted 0 times
...
Man
8 months ago
That seems like the most straightforward solution. It's important to ensure all resources are properly tagged.
upvoted 0 times
...
Clare
8 months ago
Yeah, we can search for the EBS volumes that are missing tags and add the cost center tags.
upvoted 0 times
...
Emilio
8 months ago
Option D sounds like a good idea. Let's use Tag Editor to find the untagged volumes.
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