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

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

A company has a mobile application that makes HTTP API calls to an Application Load Balancer (ALB). The ALB routes requests to an AWS Lambda function. Many different versions of the application are in use at any given time, including versions that are in testing by a subset of users. The version of the application is defined in the user-agent header that is sent with all requests to the API.

After a series of recent changes to the API, the company has observed issues with the application. The company needs to gather a metric for each API operation by response code for each version of the application that is in use. A DevOps engineer has modified the Lambda function to extract the API operation name, version information from the user-agent header and response code.

Which additional set of actions should the DevOps engineer take to gather the required metrics?

Show Suggested Answer Hide Answer

Contribute your Thoughts:

Earleen
20 days ago
Haha, 'response metadata'? That sounds like a great way to confuse everyone. I'd steer clear of that one!
upvoted 0 times
...
Arlen
21 days ago
Wait, did you say 'response metadata'? I think I'd rather go with an option that doesn't involve that. Yikes!
upvoted 0 times
...
Nieves
22 days ago
Option A seems a bit too manual for my liking. I'd prefer a more automated solution like B or D.
upvoted 0 times
...
Edelmira
24 days ago
I don't know, I'm leaning towards C. Getting the data directly from the ALB access logs and then using a metric filter seems like the simplest option.
upvoted 0 times
Audry
7 days ago
I think C could work, but D might provide more detailed insights.
upvoted 0 times
...
...
Lasandra
28 days ago
I'd go with D. Using X-Ray to capture the data and then have CloudWatch pull the metrics from there seems like a more robust solution.
upvoted 0 times
Ahmed
4 days ago
I agree, using X-Ray for capturing the data and CloudWatch for metrics sounds like a solid plan.
upvoted 0 times
...
Louvenia
12 days ago
D) Configure AWS X-Ray integration on the Lambda function. Modify the Lambda function to create an X-Ray subsegment with the API operation name, response code, and version number. Configure X-Ray insights to extract an aggregated metric for each API operation name and to publish the metric to Amazon CloudWatch. Specify response code and application version as dimensions for the metric.
upvoted 0 times
...
...
Georgeanna
1 months ago
Hmm, I think option B is the way to go. Writing the data to CloudWatch Logs and then using Insights to populate the metrics sounds like a pretty straightforward approach.
upvoted 0 times
Eladia
1 days ago
Yeah, writing the data to CloudWatch Logs and then using Insights to populate the metrics seems efficient.
upvoted 0 times
...
Vanna
2 days ago
Option B does sound like a straightforward approach. It's important to have a clear method for collecting and analyzing the data.
upvoted 0 times
...
Bok
14 days ago
Yeah, writing the data to CloudWatch Logs and then querying it with Insights seems like an efficient way to gather the required metrics.
upvoted 0 times
...
Fletcher
18 days ago
I agree, option B seems like a good choice. Using CloudWatch Logs and Insights for metrics makes sense.
upvoted 0 times
...
Tu
24 days ago
I agree, option B seems like a good choice. Using CloudWatch Logs and Insights for metrics makes sense.
upvoted 0 times
...
...
Lauran
2 months ago
I'm not sure about option A. I think option D with AWS X-Ray integration could provide more detailed insights and a better way to track the metrics we need.
upvoted 0 times
...
Stanford
2 months ago
I agree with Lottie. Option A provides a clear path to gather the metrics we need, and using CloudWatch Logs for this purpose makes sense.
upvoted 0 times
...
Lottie
2 months ago
I think option A is the best choice. Writing logs to CloudWatch Logs and using metric filters seems like a straightforward way to gather the required metrics.
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