Microservices API Gateway and Management 3

Question 1

Which task is typically NOT a responsibility of an API gateway?

Accepted Answer

Implementing core business logic of a service

Answer

Business logic belongs in the microservices themselves; the gateway handles cross-cutting concerns like auth and routing.

Question 2

What does API versioning via the URL path look like?

Accepted Answer

/v1/orders and /v2/orders

Answer

Path-based versioning embeds the version directly in the URL, e.g. /v1/ and /v2/, letting clients pick a version explicitly.

Question 3

In service mesh terminology, what handles east-west (service-to-service) traffic while a gateway handles north-south traffic?

Accepted Answer

Sidecar proxies

Answer

Service meshes use sidecar proxies for internal east-west traffic, whereas the gateway manages external north-south traffic.

Question 4

What is the benefit of response caching at the gateway?

Accepted Answer

Reduced load on backend services and lower latency for repeated requests

Answer

Caching common responses at the gateway serves repeated requests quickly without hitting backend services.

Question 5

Which header is commonly injected by a gateway to enable distributed tracing across services?

Accepted Answer

A correlation/trace ID header

Answer

Gateways add a correlation or trace ID so a request can be followed across multiple microservices in tracing tools.

Microservices Practice Test