Bird
0
0

A developer configures an API Gateway to route requests but clients receive 404 errors. What is a common misconfiguration causing this?

medium📝 Debug Q7 of 15
Rest API - Advanced Patterns
A developer configures an API Gateway to route requests but clients receive 404 errors. What is a common misconfiguration causing this?
AThe gateway is using HTTPS but client sends HTTP.
BThe backend service is overloaded but gateway is healthy.
CThe gateway is caching stale responses.
DThe route path in the gateway does not match the client request path.
Step-by-Step Solution
Solution:

  1. Step 1: Analyze 404 error meaning

    404 means resource not found, often due to incorrect routing paths.

  2. Step 2: Identify gateway misconfiguration

    If gateway route path does not match client request, it cannot forward correctly, causing 404.

  3. Final Answer:

    The route path in the gateway does not match the client request path. -> Option D

  4. Quick Check:

    404 error = route path mismatch [OK]
Quick Trick: Check route paths match client requests exactly [OK]
Common Mistakes:
MISTAKES
  • Blaming backend overload for 404
  • Assuming caching causes 404
  • Confusing HTTP/HTTPS mismatch with 404

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Rest API Quizzes
API Documentation - OpenAPI Specification (Swagger) - Quiz 13medium API Documentation - Why documentation drives adoption - Quiz 10hard API Testing and Monitoring - API monitoring and alerting - Quiz 4medium API Testing and Monitoring - Integration testing - Quiz 14medium API Testing and Monitoring - Contract testing - Quiz 1easy API Testing and Monitoring - Contract testing - Quiz 2easy Advanced Patterns - Why advanced patterns solve real problems - Quiz 7medium Caching Strategies - If-None-Match and 304 responses - Quiz 2easy Webhooks and Events - Retry and failure handling - Quiz 11easy Webhooks and Events - Why webhooks push notifications - Quiz 5medium