Interview Q&A

Master technical and career interviews with structured answers—short definition, real examples, pitfalls, and how to answer in 60–90 seconds.

4608 total questions 4508 technical 100 career & HR 4272 from PDF library

Showing 1–3 of 3

Popular tracks

Senior PDF
What does "client-server architecture" mean in REST?

Short answer: It means REST APIs separate the client (frontend/UI) and server (backend logic, database). The client is responsible for UI and user interactions. The server manages data, business logic, and security. This…

REST API Read answer
Senior PDF
What is an API Gateway, and when would you use it in an architecture?

Short answer: API Gateway is a single entry point for APIs in a microservices architecture. Handles routing, load balancing, authentication, rate limiting, logging, monitoring. Examples: Kong, NGINX, AWS API Gateway, Azu…

REST API Read answer
Senior PDF
How do you manage dependencies and interactions between multiple microservices in REST?

Short answer: Use an API Gateway for routing and orchestration. Implement service discovery (Consul, Eureka). Use message queues/event buses (RabbitMQ, Kafka) for async communication. Apply circuit breakers (Polly in .NE…

REST API Read answer

ASP.NET Web API ASP.NET Core Web API Tutorial · REST API

Short answer: It means REST APIs separate the client (frontend/UI) and server (backend logic, database). The client is responsible for UI and user interactions. The server manages data, business logic, and security. This separation improves scalability and flexibility. 👉 Example: Client: React.js front-end making API calls. Server: ASP.NET Core Web API handling requests.

Real-world example (ShopNest)

Creating an order is POST /api/orders → 201 with Location header. Fetching is GET /api/orders/{id} → 200 or 404.

Say this in the interview

  1. Define — one clear sentence (the short answer above).
  2. Example — relate it to a project like ShopNest or your real work.
  3. Trade-off — when you would not use it.
Permalink & share

ASP.NET Web API ASP.NET Core Web API Tutorial · REST API

Short answer: API Gateway is a single entry point for APIs in a microservices architecture. Handles routing, load balancing, authentication, rate limiting, logging, monitoring. Examples: Kong, NGINX, AWS API Gateway, Azure API Management. Use when: You have multiple microservices. Need centralized authentication/security. Need rate limiting or monitoring.

Real-world example (ShopNest)

ShopNest exposes REST APIs for cart and checkout. Controllers stay thin; business rules live in application services.

Say this in the interview

  1. Define — one clear sentence (the short answer above).
  2. Example — relate it to a project like ShopNest or your real work.
  3. Trade-off — when you would not use it.
Permalink & share

ASP.NET Web API ASP.NET Core Web API Tutorial · REST API

Short answer: Use an API Gateway for routing and orchestration. Implement service discovery (Consul, Eureka). Use message queues/event buses (RabbitMQ, Kafka) for async communication. Apply circuit breakers (Polly in .NET) to handle failures. Implement distributed tracing (Jaeger, Zipkin, OpenTelemetry).

Real-world example (ShopNest)

Creating an order is POST /api/orders → 201 with Location header. Fetching is GET /api/orders/{id} → 200 or 404.

Say this in the interview

  1. Define — one clear sentence (the short answer above).
  2. Example — relate it to a project like ShopNest or your real work.
  3. Trade-off — when you would not use it.
Permalink & share
Toolliyo Assistant
Ask about tutorials, ebooks, training, pricing, mentor services, and support. I use public site content only—not admin or internal tools.

care@toolliyo.com

Need callback? Share your details