Kong FAQs for DevOps Interviews: Quick Answers (2027)
36 Kong FAQs for DevOps interviews with short answers: entities, default ports, DB-less vs hybrid, decK, Ingress Controller, rate limiting, plugins.
Kong FAQs in DevOps interviews are short concept checks: what Kong Gateway is, its core entities (Services, Routes, Consumers, Plugins, Upstreams), its default ports, the difference between traditional, DB-less and hybrid deployments, and how it runs on Kubernetes. This page gives a two or three sentence answer to each, the length an interviewer expects in a quick round.
Use it as a fast revision sheet. Longer answers are in our main Kong API Gateway interview questions, and production problems are covered on the keeper page, scenario-based Kong interview questions. For hands-on configuration see 75+ Kong hands-on config questions, and for a study schedule, the 4-week Kong prep plan. Facts were checked against developer.konghq.com in November 2026.
Key takeaways
- Kong Gateway is an API gateway built on NGINX and OpenResty, extended with Lua (and other languages through plugin servers).
- The five entities to name first: Service, Route, Consumer, Plugin and Upstream (with Targets).
- Default ports: proxy 8000/8443, Admin API 8001/8444, Kong Manager 8002/8445, hybrid cluster 8005 and telemetry 8006.
- DB-less mode makes the Admin API read-only; configuration comes from a declarative file.
- Hybrid mode splits a control plane, which holds configuration, from data planes, which proxy traffic.
- decK manages configuration as code; the Kong Ingress Controller runs Kong on Kubernetes.
Quick reference table
| Term | One-line answer |
|---|---|
| Service | An upstream API or microservice Kong forwards to |
| Route | Rules that match client requests and send them to a Service |
| Consumer | An identity (app or user) that calls your APIs |
| Plugin | Extra behaviour such as auth, rate limiting or logging |
| Upstream / Target | A load-balanced group of backend hosts and the hosts in it |
| Admin API | REST API that configures Kong |
| decK | CLI for declarative configuration and drift checks |
| Konnect | Kong's SaaS control plane for managing gateways |
Freshers: basics
1. What is Kong Gateway?
An API gateway that sits in front of your services and handles routing, authentication, rate limiting, transformations and observability. It is built on NGINX and OpenResty.
2. Why use an API gateway?
To keep cross-cutting concerns such as authentication, throttling and logging in one place instead of rebuilding them in every service, and to give clients a single entry point.
3. What is a Service in Kong?
The definition of a backend: protocol, host, port and path. Kong forwards matched requests to it.
4. What is a Route?
A set of matching rules (paths, hosts, methods, headers, SNI) attached to a Service. A Service can have many Routes.
5. What is a Consumer?
An identity that uses your APIs. Credentials such as API keys or JWT secrets attach to Consumers, and plugins can apply per Consumer.
6. What is a plugin?
A module that runs during the request or response lifecycle to add behaviour. Kong ships bundled plugins for authentication, security, traffic control, transformations, logging and analytics.
7. At what levels can a plugin be applied?
Globally, or scoped to a Service, Route, Consumer, or combinations of them. A more specific scope takes precedence over a less specific one.
8. What are Kong's default ports?
8000 (HTTP) and 8443 (HTTPS) for proxy traffic, 8001 and 8444 for the Admin API, 8002 and 8445 for Kong Manager, and 8005 and 8006 for hybrid mode cluster and telemetry traffic.
9. Why should the Admin API not be public?
Anyone who reaches it can change all routing and security. Bind it to localhost or a private network, protect it with RBAC where available, and expose it only through controlled access.
10. Which database does Kong use?
PostgreSQL in traditional mode. DB-less mode keeps configuration in memory from a declarative file instead.
11. What is Kong Manager?
The web UI for viewing and editing Kong entities, served on port 8002 by default.
12. What are Upstreams and Targets?
An Upstream is a virtual hostname with a load-balancing algorithm and health checks; Targets are the backend host and port pairs behind it. A Service points at the Upstream name.
2 to 5 years: deployment and operations
13. What deployment topologies does Kong support?
Traditional (nodes share a database), DB-less (each node loads a declarative file), and hybrid (a control plane with a database pushes configuration to data planes). Konnect is a managed version of the hybrid model.
14. What are the limits of DB-less mode?
The Admin API is read-only for changes, configuration must fit in memory, plugins that need a database do not work, and you update by reloading a new declarative file.
15. How does hybrid mode work?
The control plane stores configuration and serves the Admin API. Data planes connect over mutual TLS on the cluster port, receive configuration and proxy traffic. If the control plane is down, data planes keep serving with their cached configuration.
16. What version rule applies between control plane and data planes?
Data planes must be the same major version and must not run a newer minor version than the control plane. Upgrade the control plane first.
17. What is decK?
A command-line tool that exports, diffs and syncs Kong configuration as YAML or JSON, so changes go through Git and review.
deck gateway dump -o kong.yaml # export current config
deck gateway diff kong.yaml # preview changes
deck gateway sync kong.yaml # apply
18. What is the Kong Ingress Controller?
A Kubernetes controller that turns Ingress, Gateway API resources and Kong custom resources into Kong configuration. Kong recommends the Gateway API for new setups.
19. Which rate limiting policies exist?
local counts per node, cluster stores counters in the database, and redis uses a shared Redis. The cluster policy is not supported in hybrid mode or Konnect, so Redis is the usual shared option there.
20. What authentication plugins are common?
Key Authentication, Basic Authentication, JWT, OAuth 2.0, HMAC, ACL for group-based access and, in Enterprise, OpenID Connect.
21. How do you observe Kong?
With the Prometheus plugin for metrics, OpenTelemetry for traces, and logging plugins such as HTTP Log, File Log or TCP Log. The Status API reports node health.
22. What do strip_path and preserve_host do?
strip_path (default true) removes the matched path prefix before forwarding. preserve_host (default false) sends the client's Host header to the upstream instead of the Service host.
23. How does Kong handle a failing backend?
Upstream health checks: active checks probe Targets, passive checks watch real traffic, and unhealthy Targets are taken out of rotation. Service settings also define timeouts and retries.
24. How do you write a custom plugin?
Most custom plugins are written in Lua against the Plugin Development Kit. Kong also supports Go, JavaScript and Python plugin servers.
25. What is the difference between Kong Gateway open source and Enterprise?
Enterprise adds features such as RBAC, workspaces, extra plugins (for example OpenID Connect) and support. Check Kong's current product pages, since packaging changes.
Senior: design and governance
26. Kong or a cloud provider's API gateway?
Kong runs anywhere, including on-premises and across clouds, and is extensible with plugins. A managed cloud gateway removes operations work but ties you to that provider. Our comparison of managed cloud API gateways helps frame the answer.
27. How do you run Kong configuration through CI/CD?
Keep decK files in Git, lint and diff them in merge requests, and sync from a pipeline to each environment. With Konnect or hybrid mode, the pipeline targets the control plane only.
28. How would you make Kong highly available?
Several data plane nodes behind a load balancer across zones, a resilient control plane (or Konnect), and shared state such as Redis for rate limits where needed.
29. How do you separate teams on one Kong deployment?
Workspaces and RBAC in Enterprise, or separate control plane groups in Konnect, so each team manages only its own entities.
30. Is Kong Mesh the same as Kong Gateway?
No. Kong Mesh is a separate service mesh product built on Kuma for service-to-service traffic. Kong Gateway handles north-south API traffic.
Scenario FAQs
31. A route returns 404 "no Route matched". What do you check first?
The request's host, path and method against the Route definition, whether strip_path or path handling changed the request, and that the latest configuration reached the node.
32. Clients get 429 too early after scaling to more nodes. Why?
Probably the local policy combined with uneven load balancing, or limits set without considering node count. Switch to Redis for shared counters when exact limits matter.
33. You need to stop Admin API changes in production. How?
Use DB-less or hybrid mode with changes only through decK in CI, and keep the Admin API private.
34. A plugin should apply to every route except one. How?
Apply it globally and override on that route, or scope it to the Services that need it rather than globally. Prefer explicit scoping for clarity.
35. A data plane shows old configuration. What do you check?
Its connection to the control plane on port 8005, certificate validity for the mTLS link, version compatibility, and the control plane logs for sync errors.
36. How would you migrate from NGINX config to Kong?
Map each server and location block to Services and Routes, map auth and rate limit directives to plugins, express it all in a decK file, and cut over traffic gradually.
Pairs of terms candidates mix up
Quick rounds often test whether you can separate two similar ideas in one sentence each. These come up most.
| Pair | The difference |
|---|---|
| Service vs Route | The Service is where traffic goes; the Route decides which requests go there. |
| Upstream vs Service | The Upstream load-balances across Targets; the Service can point at an Upstream name or a single host. |
| Admin API vs proxy | The Admin API (8001/8444) changes configuration; the proxy (8000/8443) carries client traffic. |
| DB-less vs hybrid | DB-less nodes each load a file; hybrid data planes get configuration from a control plane that has a database. |
| Kong Manager vs Konnect | Kong Manager is the UI of a self-managed gateway; Konnect is Kong's hosted control plane. |
| Kong Gateway vs Kong Mesh | The gateway handles traffic entering your platform; the mesh handles traffic between services. |
| Ingress vs Gateway API | Both configure Kong through the Ingress Controller; the Gateway API is the newer, more expressive Kubernetes standard Kong recommends. |
| local vs redis rate limiting | local counts on each node separately; redis shares counters so limits hold across all nodes. |
If you can explain each row and then name the command or setting behind it, you are ready for the quick-fire part of most Kong interviews.
Where this fits
Kong usually appears in DevOps interviews alongside Kubernetes, CI/CD and observability. Our DevOps training in Pune (Kharadi classroom or live online) covers these together, and self-hosted API gateways compared shows where Kong sits among alternatives.
FAQ
What is Kong used for in DevOps?
As an API gateway that centralises routing, authentication, rate limiting and observability for microservices, configured as code with decK or Kubernetes resources.
What port does the Kong Admin API use?
8001 for HTTP and 8444 for HTTPS by default. Proxy traffic uses 8000 and 8443.
What is DB-less mode in Kong?
A mode where each node loads configuration from a declarative file into memory with no database, and the Admin API cannot change configuration.
What is hybrid mode in Kong?
A split between a control plane that holds configuration and data planes that proxy traffic and receive configuration over mutual TLS.
Which database does Kong support?
PostgreSQL in traditional and hybrid control plane deployments.
What is decK?
Kong's command-line tool for exporting, diffing and syncing declarative configuration.
How does Kong run on Kubernetes?
Through the Kong Ingress Controller, which configures Kong from Ingress, Gateway API and Kong custom resources.
References
What's Your Reaction?
Like
0
Dislike
0
Love
0
Funny
0
Angry
0
Sad
0
Wow
0