API & Microservices interview questions

1. A.an independently deployable service owning one business capability and its own data
2. B.a pattern that stops calling a failing dependency for a cooldown period to prevent cascading failure
3. C.a high-performance RPC framework using HTTP/2 and protobuf, common for low-latency service-to-service calls
4. D.an HTTP interface exposing resources via verbs (GET/POST/PUT/DELETE) and status codes

Answer + AI explanation with Pro

1. A.Service mesh
2. B.gRPC
3. C.Microservice
4. D.REST API

Answer + AI explanation with Pro

1. A.REST API — an HTTP interface exposing resources via verbs (GET/POST/PUT/DELETE) and status codes
2. B.REST API — a client-supplied token letting a server safely deduplicate retried write requests
3. C.REST API — a pattern that stops calling a failing dependency for a cooldown period to prevent cascading failure
4. D.REST API — a single entry point that routes, authenticates, rate-limits and aggregates calls to backend services

Answer + AI explanation with Pro

1. A.a client-supplied token letting a server safely deduplicate retried write requests
2. B.a single entry point that routes, authenticates, rate-limits and aggregates calls to backend services
3. C.a high-performance RPC framework using HTTP/2 and protobuf, common for low-latency service-to-service calls
4. D.an independently deployable service owning one business capability and its own data

Answer + AI explanation with Pro

1. A.Service mesh
2. B.Circuit breaker
3. C.Idempotency key
4. D.Microservice

Answer + AI explanation with Pro

1. A.Microservice — a client-supplied token letting a server safely deduplicate retried write requests
2. B.Microservice — an independently deployable service owning one business capability and its own data
3. C.Microservice — an infrastructure layer (e.g. Istio) handling mTLS, retries and traffic policy between services transparently
4. D.Microservice — a single entry point that routes, authenticates, rate-limits and aggregates calls to backend services

Answer + AI explanation with Pro

1. A.a pattern that stops calling a failing dependency for a cooldown period to prevent cascading failure
2. B.an HTTP interface exposing resources via verbs (GET/POST/PUT/DELETE) and status codes
3. C.a single entry point that routes, authenticates, rate-limits and aggregates calls to backend services
4. D.an independently deployable service owning one business capability and its own data

Answer + AI explanation with Pro

1. A.REST API
2. B.gRPC
3. C.Circuit breaker
4. D.API gateway

Answer + AI explanation with Pro

1. A.API gateway — a client-supplied token letting a server safely deduplicate retried write requests
2. B.API gateway — a single entry point that routes, authenticates, rate-limits and aggregates calls to backend services
3. C.API gateway — an infrastructure layer (e.g. Istio) handling mTLS, retries and traffic policy between services transparently
4. D.API gateway — an independently deployable service owning one business capability and its own data

Answer + AI explanation with Pro

1. A.a pattern that stops calling a failing dependency for a cooldown period to prevent cascading failure
2. B.an infrastructure layer (e.g. Istio) handling mTLS, retries and traffic policy between services transparently
3. C.a client-supplied token letting a server safely deduplicate retried write requests
4. D.a high-performance RPC framework using HTTP/2 and protobuf, common for low-latency service-to-service calls

Answer + AI explanation with Pro

1. A.gRPC
2. B.Microservice
3. C.Service mesh
4. D.Idempotency key

Answer + AI explanation with Pro

1. A.gRPC — a client-supplied token letting a server safely deduplicate retried write requests
2. B.gRPC — an independently deployable service owning one business capability and its own data
3. C.gRPC — an HTTP interface exposing resources via verbs (GET/POST/PUT/DELETE) and status codes
4. D.gRPC — a high-performance RPC framework using HTTP/2 and protobuf, common for low-latency service-to-service calls

Answer + AI explanation with Pro

1. A.an HTTP interface exposing resources via verbs (GET/POST/PUT/DELETE) and status codes
2. B.a client-supplied token letting a server safely deduplicate retried write requests
3. C.a pattern that stops calling a failing dependency for a cooldown period to prevent cascading failure
4. D.a high-performance RPC framework using HTTP/2 and protobuf, common for low-latency service-to-service calls

Answer + AI explanation with Pro

1. A.REST API
2. B.Idempotency key
3. C.Circuit breaker
4. D.Microservice

Answer + AI explanation with Pro

1. A.Idempotency key — a single entry point that routes, authenticates, rate-limits and aggregates calls to backend services
2. B.Idempotency key — an HTTP interface exposing resources via verbs (GET/POST/PUT/DELETE) and status codes
3. C.Idempotency key — an independently deployable service owning one business capability and its own data
4. D.Idempotency key — a client-supplied token letting a server safely deduplicate retried write requests

Answer + AI explanation with Pro

1. A.a high-performance RPC framework using HTTP/2 and protobuf, common for low-latency service-to-service calls
2. B.an independently deployable service owning one business capability and its own data
3. C.a pattern that stops calling a failing dependency for a cooldown period to prevent cascading failure
4. D.an infrastructure layer (e.g. Istio) handling mTLS, retries and traffic policy between services transparently

Answer + AI explanation with Pro

1. A.REST API
2. B.Circuit breaker
3. C.Service mesh
4. D.gRPC

Answer + AI explanation with Pro

1. A.Service mesh — an HTTP interface exposing resources via verbs (GET/POST/PUT/DELETE) and status codes
2. B.Service mesh — an infrastructure layer (e.g. Istio) handling mTLS, retries and traffic policy between services transparently
3. C.Service mesh — a high-performance RPC framework using HTTP/2 and protobuf, common for low-latency service-to-service calls
4. D.Service mesh — an independently deployable service owning one business capability and its own data

Answer + AI explanation with Pro

1. A.a high-performance RPC framework using HTTP/2 and protobuf, common for low-latency service-to-service calls
2. B.a pattern that stops calling a failing dependency for a cooldown period to prevent cascading failure
3. C.a client-supplied token letting a server safely deduplicate retried write requests
4. D.an HTTP interface exposing resources via verbs (GET/POST/PUT/DELETE) and status codes

Answer + AI explanation with Pro

1. A.API gateway
2. B.REST API
3. C.Circuit breaker
4. D.Idempotency key

Answer + AI explanation with Pro

1. A.Circuit breaker — a client-supplied token letting a server safely deduplicate retried write requests
2. B.Circuit breaker — a single entry point that routes, authenticates, rate-limits and aggregates calls to backend services
3. C.Circuit breaker — a pattern that stops calling a failing dependency for a cooldown period to prevent cascading failure
4. D.Circuit breaker — an independently deployable service owning one business capability and its own data

Answer + AI explanation with Pro