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-C02 Topic 3 Question 19 Discussion

Actual exam question for Amazon's DOP-C02 exam
Question #: 19
Topic #: 3
[All DOP-C02 Questions]

A company's application runs on Amazon EC2 instances. The application writes to a log file that records the username, date, time: and source IP address of the login. The log is published to a log group in Amazon CloudWatch Logs

The company is performing a root cause analysis for an event that occurred on the previous day The company needs to know the number of logins for a specific user from the past 7 days

Which solution will provide this information'?

Show Suggested Answer Hide Answer

Contribute your Thoughts:

Noah
6 months ago
I agree. Let's choose between option C and A for our solution to determine the number of logins for the specific user over the past 7 days.
upvoted 0 times
...
Corazon
6 months ago
I think we should go with either option C or A, as both seem like they would give us the information we need for the analysis.
upvoted 0 times
...
Mitsue
6 months ago
I see your point, but I think option C is better because it specifically uses an aggregation function to count the logins, which could be more accurate.
upvoted 0 times
...
Gilma
6 months ago
But what about option A? Creating a CloudWatch Logs metric filter and publishing a CloudWatch metric also seems like a viable solution.
upvoted 0 times
...
Floyd
6 months ago
I agree, option C seems like the most efficient way to get the information we need for the root cause analysis.
upvoted 0 times
...
Fatima
6 months ago
I think option C is the best solution, as it allows us to use an aggregation function to count the number of logins for the specific user over the past 7 days.
upvoted 0 times
...
Josephine
6 months ago
I think creating a CloudWatch Logs subscription with a filter pattern and publishing a metric summing the logins over the past 7 days is the best option
upvoted 0 times
...
Ashlee
6 months ago
But wouldn't creating a CloudWatch dashboard with a number widget and using a filter pattern directly from the log group be more efficient?
upvoted 0 times
...
Thurman
7 months ago
I disagree. I believe creating a CloudWatch Logs metric filter and publishing a metric summing the logins over the past 7 days is the way to go
upvoted 0 times
...
Ashlee
7 months ago
I think the solution is to create a CloudWatch Logs Insights query to count the logins over the past 7 days
upvoted 0 times
...
Garry
8 months ago
I was leaning towards D, but now I think C is the better choice. Creating a dashboard just to display the login count seems a bit excessive. The Logs Insights query is more efficient.
upvoted 0 times
...
Clorinda
8 months ago
Yeah, C is the way to go. The other options involve creating additional metrics or dashboards, which might be overkill for this particular use case. The Logs Insights query is a nice, clean solution.
upvoted 0 times
...
Linwood
8 months ago
I agree, C seems like the most direct approach. The question is specifically asking for the number of logins, and the CloudWatch Logs Insights query can provide that aggregated data directly from the log group.
upvoted 0 times
Carmela
8 months ago
C) Create a CloudWatch Logs Insights query that uses an aggregation function to count the number of logins for the username over the past 7 days. Run the query against the log group.
upvoted 0 times
...
Paulina
8 months ago
A) Create a CloudWatch Logs metric filter on the log group Use a filter pattern that matches the username. Publish a CloudWatch metric that sums the number of logins over the past 7 days.
upvoted 0 times
...
...
Lenna
8 months ago
This seems like a straightforward question about analyzing log data in CloudWatch. I think the best solution is C - creating a CloudWatch Logs Insights query to count the number of logins for the specific user over the past 7 days.
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