Q68 — AWS DVA-C02 Ch.2

Question 68 of 100 | ← Chapter 2

A developer is troubleshooting an Amazon API Gateway API. When clients attempt to access the API endpoint, they consistently receive HTTP 400 response errors. How can the developer determine the root cause of these errors?

• A. Create an Amazon Kinesis Data Firehose delivery stream to receive API call logs from API Gateway. Configure Amazon CloudWatch Logs as the delivery stream destination.
• B. Enable AWS CloudTrail Insights and create a trail. Specify the Amazon Resource Name (ARN) of the API stage for the trail.
• C. Enable AWS X-Ray for the API stage. Create an Amazon CloudWatch Logs log group. Specify the ARN of the log group for the API stage.
• D. Enable execution logging and access logging for the API stage in Amazon CloudWatch Logs. Create a CloudWatch Logs log group. Specify the ARN of the log group for the API stage. ✓

Correct Answer: D. Enable execution logging and access logging for the API stage in Amazon CloudWatch Logs. Create a CloudWatch Logs log group. Specify the ARN of the log group for the API stage.

Explanation

HTTP 400 errors indicate client-side request errors. According to AWS documentation, API Gateway execution logs contain detailed information about request/response payloads, parameters, and errors—enabling precise root-cause analysis. Enabling both execution and access logging (option D) captures comprehensive diagnostic data including error details, whereas CloudTrail (B) logs management events—not request-level errors—and X-Ray (C) focuses on trace latency, not request validation failures. Kinesis Firehose (A) adds unnecessary complexity and isn’t natively integrated for API Gateway error diagnostics.