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

- Free Preparation Discussions
Mail Us support@pass4success.com
Location PL
Mob_nav_barsMENU

Amazon Exam BDS-C00 Topic 8 Question 87 Discussion

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

You currently run your infrastructure on Amazon EC2 instances behind on Auto Scaling group. All logs for your application are currently written to ephemeral storage. Recently your company experienced a major bug in code that made it through testing and was ultimately deployed to your fleet. This bug triggered your Auto Scaling group to scale up and back down before you could successfully retrieve the logs off your server to better assist you in troubleshooting the bug.

Which technique should you use to make sure you are able to review your logs after your instances have shut down?

Show Suggested Answer Hide Answer
Suggested Answer: C

by Deeanna at Mar 04, 2024, 02:44 AM

Limited Time Offer

25%

Off

Get Premium BDS-C00 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Coletta
1 months ago
Option A is the correct answer. Configuring the ephemeral policies on your Auto Scaling group to back up on terminate is the most straightforward way to ensure you can access your logs.
upvoted 0 times
...
Fletcher
1 months ago
Haha, Option B is like trying to backup your logs by taking a snapshot of your hard drive. That's a bit overkill, don't you think?
upvoted 0 times
...
Yaeko
1 months ago
Option D seems a bit convoluted. Why set up an SNS alert when I can just use the CloudWatch Logs Agent like in Option C?
upvoted 0 times
Hailey
6 days ago
Yeah, Option C with CloudWatch Logs Agent is the best choice for ensuring you can review logs after instances shut down.
upvoted 0 times
...
Lauran
9 days ago
I agree, Option C is the most straightforward solution for backing up logs.
upvoted 0 times
...
Evette
13 days ago
Yeah, Option C seems like the most efficient choice for backing up logs.
upvoted 0 times
...
Harrison
14 days ago
Option C is definitely the way to go. It's simple and effective.
upvoted 0 times
...
Kris
15 days ago
I agree, Option C is much more straightforward than Option D.
upvoted 0 times
...
Phil
29 days ago
Option C is definitely the way to go. It's simple and effective.
upvoted 0 times
...
...
Angelica
2 months ago
I'm leaning towards Option E. Having the CloudWatch Logs Agent automatically copy the logs on scaling events sounds like a good way to ensure I can access the logs.
upvoted 0 times
Lynsey
14 days ago
User 4: Option E seems like the most efficient choice to make sure we can review the logs even after instances have shut down.
upvoted 0 times
...
Bobbye
18 days ago
User 3: I agree, having automated log copying would save a lot of time and ensure we don't miss any important information.
upvoted 0 times
...
Gerri
1 months ago
User 2: Yeah, that does sound like a reliable solution. It would definitely help in troubleshooting bugs more effectively.
upvoted 0 times
...
Lynda
1 months ago
User 1: I think Option E is the way to go. Having the CloudWatch Logs Agent automatically copy the logs on scaling events sounds like a good idea.
upvoted 0 times
...
...
Clorinda
2 months ago
I'm not sure about option C. Maybe we should consider option E and update our Scaling policy for automated CloudWatch Log copy.
upvoted 0 times
...
Geoffrey
2 months ago
I agree with Hillary. Configuring the CloudWatch Logs Agent to stream our logs seems like the best solution.
upvoted 0 times
...
Elise
2 months ago
Option C looks like the way to go. Sending logs to CloudWatch Logs seems like the most reliable method to ensure I can access them even after the instances are terminated.
upvoted 0 times
Benton
1 months ago
User 4: CloudWatch Logs Agent definitely seems like the best solution to make sure you can review your logs after instances have shut down.
upvoted 0 times
...
Theresia
1 months ago
User 3: I had a similar issue before, and using CloudWatch Logs Agent really saved me in troubleshooting the problem.
upvoted 0 times
...
Terrilyn
2 months ago
User 2: I agree, CloudWatch Logs Agent is a great way to ensure you have access to your logs even after instances are terminated.
upvoted 0 times
...
Gracie
2 months ago
User 1: Option C looks like the way to go. Sending logs to CloudWatch Logs seems like the most reliable method to ensure I can access them even after the instances are terminated.
upvoted 0 times
...
...
Hillary
2 months ago
I think we should use option C and install the CloudWatch Logs Agent on our AMI.
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