Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Amazon Exam BDS-C00 Topic 2 Question 111 Discussion

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

A company is building a new application is AWS. The architect needs to design a system to collect application log events. The design should be a repeatable pattern that minimizes data loss if an application instance fails, and keeps a durable copy of all log data for at least 30 days.

What is the simplest architecture that will allow the architect to analyze the logs?

Show Suggested Answer Hide Answer
Suggested Answer: B

Contribute your Thoughts:

An
2 months ago
Option B seems the most flexible, with S3 and Elasticsearch providing a durable and searchable log solution. Plus, Lambda functions are always fun to tinker with.
upvoted 0 times
Johnson
12 days ago
That could work too, but I think the flexibility of S3 and Elasticsearch is worth considering.
upvoted 0 times
...
Dick
1 months ago
But wouldn't writing directly to Kinesis Firehose and loading into Redshift be more efficient for analysis?
upvoted 0 times
...
Gracia
1 months ago
I agree, using Lambda functions to load the events into Elasticsearch is a smart choice.
upvoted 0 times
...
Willie
2 months ago
Option B seems the most flexible, with S3 and Elasticsearch providing a durable and searchable log solution.
upvoted 0 times
...
...
Raymon
2 months ago
Haha, Option D is like taking a rocket to the grocery store. HDFS on EMR for simple log analysis? Talk about overkill!
upvoted 0 times
...
An
2 months ago
I'm not a fan of Option C. Depending on the CloudWatch Logs agent could introduce reliability issues, and I'd rather not add another service to the mix.
upvoted 0 times
Kristel
1 months ago
I see your point about Option C. Relying on the CloudWatch Logs agent could be risky.
upvoted 0 times
...
Rosamond
1 months ago
I agree, Option B also seems like a solid option. Using S3 and Lambda for analysis sounds reliable.
upvoted 0 times
...
Carey
2 months ago
Option A sounds like a good choice. Directly writing to Kinesis Firehose seems efficient.
upvoted 0 times
...
...
Jesusita
3 months ago
Option A looks like the simplest solution. Kinesis Firehose and Redshift are a robust combination for reliable log ingestion and analysis.
upvoted 0 times
Luisa
1 months ago
I think Option B could also work well, with S3 and Lambda to load events into Elasticsearch for analysis.
upvoted 0 times
...
Paris
1 months ago
I agree, using Kinesis Firehose to load events into Redshift makes it easy to analyze the logs.
upvoted 0 times
...
Kirby
1 months ago
Option A looks like the simplest solution. Kinesis Firehose and Redshift are a robust combination for reliable log ingestion and analysis.
upvoted 0 times
...
...
Lisha
3 months ago
I personally prefer option C. Using CloudWatch Logs agent seems like a simpler and more reliable approach.
upvoted 0 times
...
Dell
4 months ago
I disagree, I believe option B is better. Using S3 and Lambda function is a more cost-effective solution.
upvoted 0 times
...
Andrew
4 months ago
I think option A is the best choice. Kinesis Firehose can handle large volumes of data efficiently.
upvoted 0 times
...

Save Cancel