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

- Free Preparation Discussions

Amazon Exam SOA-C02 Topic 5 Question 90 Discussion

Actual exam question for Amazon's SOA-C02 exam
Question #: 90
Topic #: 5
[All SOA-C02 Questions]

A company hosts a web application on an Amazon EC2 instance. The web server logs are published to Amazon CloudWatch Logs. The log events have the same structure and include the HTTP response codes that are associated with the user requests. The company needs to monitor the number of times that the web server returns an HTTP 404 response.

What is the MOST operationally efficient solution that meets these requirements?

Show Suggested Answer Hide Answer
Suggested Answer: A

Using the ALB's RequestCount metric will allow the SysOps administrator to collect information about total requests for a 2-week period and determine when requests exceeded the threshold of 100 requests per second. Configuring a time range of 2 weeks and a period of 1 minute will ensure that the data can be accurately examined to determine peak traffic times and volumes.


Contribute your Thoughts:

Brandon
28 days ago
Option C sounds like the most 'Lambda-rrific' solution. Just don't forget to set the function to auto-scale or you might end up with a big AWS bill.
upvoted 0 times
...
Vallie
1 months ago
I'd go with option A. It's the easiest way to set it and forget it. Plus, who needs a degree in computer science to monitor 404 errors?
upvoted 0 times
Ilene
11 days ago
Option A sounds good to me. Easy and efficient.
upvoted 0 times
...
...
Cathrine
1 months ago
Option B with a CloudWatch Logs subscription filter could work, but it might be overkill for just counting 404 responses.
upvoted 0 times
Naomi
2 days ago
Yeah, Option B might be too complex for just counting 404 responses. Option A is definitely the way to go.
upvoted 0 times
...
Jose
4 days ago
I agree, Option A would be the most operationally efficient way to monitor the number of 404 responses.
upvoted 0 times
...
Martina
9 days ago
Option A with a CloudWatch metric filter for HTTP 404 responses seems like the simplest solution.
upvoted 0 times
...
...
Jame
1 months ago
Option D is a good choice if you want to automate the process and run the query on a schedule. A script is a simple yet effective solution.
upvoted 0 times
It would definitely save time and effort in monitoring the HTTP 404 responses.
upvoted 0 times
...
Erinn
2 days ago
I agree, using a script to run the query on a schedule is efficient.
upvoted 0 times
...
Keneth
11 days ago
Option D sounds like a good choice for automation.
upvoted 0 times
...
...
Clorinda
2 months ago
I like option C. Using a Lambda function to run a CloudWatch Logs Insights query gives you more flexibility and control over the monitoring.
upvoted 0 times
Benedict
8 days ago
D: I think option D could work too, running a script for the query.
upvoted 0 times
...
Mindy
18 days ago
C: I prefer option C. Using a Lambda function gives more control over the monitoring.
upvoted 0 times
...
Ashlee
24 days ago
B: I agree with you, option A seems like the most straightforward solution.
upvoted 0 times
...
Vanda
1 months ago
A: I think option A is the best choice. It's simple and efficient.
upvoted 0 times
...
...
Dyan
2 months ago
I prefer option C, creating an AWS Lambda function to run a CloudWatch Logs Insights query. It gives more flexibility in monitoring the log events.
upvoted 0 times
...
Helga
2 months ago
I agree with Billye. Creating a metric filter would be the easiest way to monitor the HTTP 404 responses.
upvoted 0 times
...
Billye
2 months ago
I think the most operationally efficient solution is to create a CloudWatch Logs metric filter.
upvoted 0 times
...
Melissa
2 months ago
Option A seems the most straightforward and efficient solution. Creating a CloudWatch Logs metric filter to count the 404 responses directly addresses the requirement.
upvoted 0 times
Arlette
1 months ago
A) Create a CloudWatch Logs metric filter that counts the number of times that the web server returns an HTTP 404 response.
upvoted 0 times
...
Marya
1 months ago
A) Create a CloudWatch Logs metric filter that counts the number of times that the web server returns an HTTP 404 response.
upvoted 0 times
...
Aron
1 months ago
B) Create a CloudWatch Logs subscription filter that counts the number of times that the web server returns an HTTP 404 response.
upvoted 0 times
...
Jovita
2 months ago
A) Create a CloudWatch Logs metric filter that counts the number of times that the web server returns an HTTP 404 response.
upvoted 0 times
...
...
Phuong
2 months ago
I prefer option C, creating an AWS Lambda function to run a CloudWatch Logs Insights query. It gives more flexibility in monitoring the log events.
upvoted 0 times
...
Reta
2 months ago
I agree with Gregoria. Creating a metric filter would be the easiest way to monitor the HTTP 404 responses.
upvoted 0 times
...
Gregoria
2 months ago
I think the most operationally efficient solution is to create a CloudWatch Logs metric filter.
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