exam questions

Exam AWS DevOps Engineer Professional All Questions

View all questions & answers for the AWS DevOps Engineer Professional exam

Exam AWS DevOps Engineer Professional topic 1 question 28 discussion

Exam question from Amazon's AWS DevOps Engineer Professional
Question #: 28
Topic #: 1
[All AWS DevOps Engineer Professional Questions]

An application has microservices spread across different AWS accounts and is integrated with an on-premises legacy system for some of its functionality.
Because of the segmented architecture and missing logs, every time the application experiences issues, it is taking too long to gather the logs to identify the issues. A DevOps Engineer must fix the log aggregation process and provide a way to centrally analyze the logs.
Which is the MOST efficient and cost-effective solution?

  • A. Collect system logs and application logs by using the Amazon CloudWatch Logs agent. Use the Amazon S3 API to export on-premises logs, and store the logs in an S3 bucket in a central account. Build an Amazon EMR cluster to reduce the logs and derive the root cause.
  • B. Collect system logs and application logs by using the Amazon CloudWatch Logs agent. Use the Amazon S3 API to import on-premises logs. Store all logs in S3 buckets in individual accounts. Use Amazon Macie to write a query to search for the required specific event-related data point.
  • C. Collect system logs and application logs using the Amazon CloudWatch Logs agent. Install the CloudWatch Logs agent on the on-premises servers. Transfer all logs from AWS to the on-premises data center. Use an Amazon Elasticsearch Logstash Kibana stack to analyze logs on premises.
  • D. Collect system logs and application logs by using the Amazon CloudWatch Logs agent. Install a CloudWatch Logs agent for on-premises resources. Store all logs in an S3 bucket in a central account. Set up an Amazon S3 trigger and an AWS Lambda function to analyze incoming logs and automatically identify anomalies. Use Amazon Athena to run ad hoc queries on the logs in the central account.
Show Suggested Answer Hide Answer
Suggested Answer: D 🗳️

Comments

Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
marwan
Highly Voted 3 years, 8 months ago
I believe D is the correct answer
upvoted 22 times
...
Raj9
Highly Voted 3 years, 7 months ago
A - when cloud watch agent can push the logs automatically, there is no reason to use s3 api B - when cloud watch agent can push the logs automatically, there is no reason to use s3 api. Also Macie is for PII C - "Transfer all logs from AWS to the on-premises data cente" make it a bad choice. Also ELK is more expensive and will need EC2 provisioning D - will work
upvoted 12 times
...
frizzolo
Most Recent 1 year, 9 months ago
Selected Answer: D
D is right
upvoted 1 times
...
Piccaso
2 years, 4 months ago
Selected Answer: D
A and B are excluded because CloudWatch Logs Agent is a good solution. Between C and D, I prefer D, because C transfer logs from AWS to on-premises ...
upvoted 1 times
frizzolo
1 year, 9 months ago
Why transferring logs to on-premise resources is a good thing?
upvoted 1 times
...
...
Bulti
2 years, 4 months ago
D is the correct answer
upvoted 1 times
...
colinquek
2 years, 9 months ago
Selected Answer: D
will work
upvoted 2 times
...
xxxdolorxxx
3 years, 7 months ago
I believe it's D.
upvoted 1 times
...
WhyIronMan
3 years, 7 months ago
I'll go with D
upvoted 3 times
...
dnevado
3 years, 7 months ago
D definitely. Agent on premise and collect logs in S3 centralized
upvoted 1 times
...
jackdryan
3 years, 7 months ago
I'll go with D
upvoted 4 times
...
ChauPhan
3 years, 7 months ago
C looks fine if the logs transfer to AWS ElasticSearch not the on-premise data center. I'll go with D
upvoted 1 times
...
df1228
3 years, 7 months ago
I choose D
upvoted 1 times
...
Augustoosouza
3 years, 7 months ago
Another important factor is "Install the CloudWatch Logs agent on the on-premises servers" without that we can't get logs from local servers. I choose D.
upvoted 2 times
...
hanou
3 years, 8 months ago
Why not A ?
upvoted 1 times
xlFireman
3 years, 7 months ago
EMR cluster would be too complicated and more cost. Exporting logs from on premise to AWS using the CLI would be also costly and inefficient. You want the Unified CW Logs Agent.
upvoted 1 times
...
...
yassu
3 years, 8 months ago
D is correct
upvoted 1 times
...
AlexTun
3 years, 8 months ago
C - logs aggregation https://medium.com/@sid_sharma/aws-emr-log-aggregation-and-visualization-using-lambda-elasticsearch-and-kibana-5b734fd5f812
upvoted 4 times
xlFireman
3 years, 7 months ago
Incorrect, we want the most cost efficient method. This method described in C would accrue a lot of charges to move all the log files to AWS (existing and future logs). D's description just inputs current and future log files to an S3 bucket. Additionally, setting up an ELK stack would incur much more cost than an S3 data events > lambda function and Athena on top of that.
upvoted 1 times
...
...
xaocho
3 years, 8 months ago
It is D
upvoted 1 times
...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel
Loading ...