DVA-C02 · Question #196
A developer is troubleshooting an Amazon API Gateway API. Clients are receiving HTTP 400 response errors when the clients try to access an endpoint of the API. How can the developer determine the…
The correct answer is D. Turn on execution logging and access logging in Amazon CloudWatch Logs for the API stage. Error code 400 means bad request. https://docs.aws.amazon.com/apigateway/latest/developerguide/set-up-logging.html The logged data includes errors or execution traces (such as request or response parameter values or payloads).
Question
A developer is troubleshooting an Amazon API Gateway API. Clients are receiving HTTP 400 response errors when the clients try to access an endpoint of the API. How can the developer determine the cause of these errors?
Options
- ACreate an Amazon Kinesis Data Firehose delivery stream to receive API call logs from API
- BTurn on AWS CloudTrail Insights and create a trail. Specify the Amazon Resource Name (ARN)
- CTurn on AWS X-Ray for the API stage. Create an Amazon CloudWatch Logs log group. Specify
- DTurn on execution logging and access logging in Amazon CloudWatch Logs for the API stage.
How the community answered
(19 responses)- A11% (2)
- C5% (1)
- D84% (16)
Explanation
Error code 400 means bad request. https://docs.aws.amazon.com/apigateway/latest/developerguide/set-up-logging.html The logged data includes errors or execution traces (such as request or response parameter values or payloads).
Community Discussion
No community discussion yet for this question.