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 DVA-C02 Exam - Topic 1 Question 7 Discussion

Posted by Levi on Mar 31, 2023 at 07:35 PM

A developer is building a web application that uses Amazon API Gateway to expose an AWS Lambda function to process requests from clients. During testing, the developer notices that the API Gateway times out even though the Lambda function finishes under the set time limit.

Which of the following API Gateway metrics in Amazon CloudWatch can help the developer troubleshoot the issue? (Choose two.)

Suggested Answer: B

Get Premium DVA-C02 Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test
33 comments · newest first
VE
Vernice 11 months ago
I'm surprised the Lambda finishes in time but still times out!
PH
Phillip 12 months ago
I think CacheMissCount is less relevant here, though.
GL
Glendora 12 months ago
Wait, isn't CacheHitCount also important for performance?
DI
Diane 1 year ago
Totally agree, those will show where the delay is happening!
CA
Candida 1 year ago
IntegrationLatency and Latency are key metrics to check.
MA
Mary 1 year ago
I feel like CacheMissCount might not be relevant for this timeout issue, but I could be wrong. I’d focus on IntegrationLatency and Latency instead.
DE
Deeanna 1 year ago
I practiced a similar question, and I believe IntegrationLatency is definitely one of the metrics to check. The other one might be Latency, but I’m not completely confident.
AL
Albina 1 year ago
I'm not entirely sure, but I remember something about CacheHitCount being useful for performance issues. Maybe it could help here?
GE
Gerry 1 year ago
I think we should look at IntegrationLatency and Latency metrics since they relate to how long the API Gateway takes to process requests.
FR
Francine 1 year ago
I think the answer is A. A full mesh of iBGP peers is required to ensure proper route propagation inside a transit AS.
RE
Renea 1 year ago
This question seems straightforward, but I want to make sure I understand the key terms like "presale activity" and "customer-focused sales plan" before answering.
LA
Lamonica 1 year ago
I've got a good handle on this. The key is recognizing that JTWROS means "joint tenants with right of survivorship," so all the statements describe important aspects of how that type of account works.
RE
Rebecka 1 year ago
I'm just hoping the issue isn't 'user error' on the developer's part. You know, like forgetting to adjust the Lambda timeout or something. Happens to the best of us, I suppose.
NO
Noah 1 year ago
I'm going with B) IntegrationLatency and D) Latency as well. Gotta love it when the AWS docs are so clear and helpful, right? *sarcasm*
DE
Delpha 1 year ago
↳ replying to Noah
Let's check those metrics and see if we can figure out what's causing the timeout.
JU
Junita 1 year ago
↳ replying to Noah
I know, right? AWS documentation can be a bit confusing sometimes.
AL
Albina 1 year ago
↳ replying to Noah
Yeah, I agree. Those metrics should definitely help pinpoint the issue.
LE
Leah 1 year ago
Definitely, those two metrics will be crucial in pinpointing the issue. I'm curious to see if the Lambda function is taking too long to process the requests, or if there's some other bottleneck in the API Gateway setup.
SA
Salina 1 year ago
↳ replying to Leah
A: Let's monitor them closely to troubleshoot and optimize the performance.
SH
Sherly 1 year ago
↳ replying to Leah
B: Yeah, those metrics will show if the Lambda function or the API Gateway itself is causing the timeout.
XO
Xochitl 1 year ago
↳ replying to Leah
A: I think checking IntegrationLatency and Latency metrics in CloudWatch could help identify the issue.
KA
Kathrine 2 years ago
I think the correct answers are B) IntegrationLatency and D) Latency. These metrics will show us where the delay is happening, whether it's in the integration with the Lambda function or in the overall API Gateway response time.
LE
Leontine 1 year ago
↳ replying to Kathrine
D: And looking at Latency will give us an overall view of the API Gateway response time.
GI
Gilma 1 year ago
↳ replying to Kathrine
C: I think checking IntegrationLatency will show if there's a delay in the Lambda function processing the request.
NI
Nicolette 1 year ago
↳ replying to Kathrine
B: Yes, those metrics will help us pinpoint where the issue is occurring.
AY
Ayesha 1 year ago
↳ replying to Kathrine
A: I agree, B) IntegrationLatency and D) Latency are the key metrics to look at for troubleshooting.
VI
Vivan 1 year ago
↳ replying to Kathrine
Let's monitor them closely to troubleshoot the timeout problem.
AA
Aaron 1 year ago
↳ replying to Kathrine
Yes, those metrics will help us pinpoint the issue.
KA
Katy 1 year ago
↳ replying to Kathrine
Maybe there's a delay in the integration process.
JO
Johana 1 year ago
↳ replying to Kathrine
I agree, we should check IntegrationLatency and Latency.
ZA
Zack 2 years ago
I'm not sure, but I think CacheHitCount could also be useful to check for caching issues.
CY
Cyndy 2 years ago
I agree with Ligia, those metrics can show where the delay is happening.
LI
Ligia 2 years ago
I think IntegrationLatency and Latency can help troubleshoot the issue.
0/2000 characters

Save Cancel