Loading
Pick a focused question that fits your time, stack, and interview goal.
405 results across 1 active filter
Page 16 of 17
Attaches a key-only stub and marks one property modified for a narrow update while naming the rules this pattern bypasses.
Explains closed, open, and half-open behavior, failure classification, recovery probes, and the limits of circuit breakers.
Explains the boundary between OAuth/OIDC identity, application users, claims mapping, roles, and app-specific permissions.
Explains when a Next.js route layer helps with cookies, tokens, aggregation, and UI-specific API adaptation.
Explains policy-based authorization, requirements, handlers, claims, capabilities, and resource-aware checks.
Explains the cache-aside pattern for read-heavy endpoints and how misses, TTLs, and source-of-truth reads fit together.
Explains saturation signals and how systems shed, queue, throttle, or degrade before cascading failure.
Use correlation IDs, structured logs, and logging scopes to make API failures traceable in production.
Uses EF Core context pooling only when reusable context state, tenant isolation, and underlying connection state are controlled and tested.
Explains when EF Core compiled queries help, what they do not fix, and how to measure their value.
Explains how query tags, request correlation, and telemetry help connect slow SQL back to code paths.
Explains when set-based EF Core updates are better than loading entities and where lifecycle behavior can differ.
Connects HTTP preconditions to atomic database concurrency checks and honest 412 or 428 API behavior.
Explains the different diagnostic roles of logs, metrics, and traces during backend production issues.
Use OpenAPI for API design, client integration, testing, and contract review in ASP.NET Core services.
Explains Redis-backed rate-limit counters, atomic increments, windows, identity keys, and fallback behavior.
Explains the risks of Redis-based distributed locks and when database constraints, queues, or idempotency are safer.
Explains middleware continuation, terminal delegates, path branches, short-circuiting, and two-way request and response flow.
Explains HTTPS, HSTS, secure cookies, HttpOnly, SameSite, no-store, and practical API/browser security hardening.
Explains structured logging fields, safe context, redaction, event naming, and avoiding secret or personal-data leaks.
Use SemaphoreSlim to bound concurrent asynchronous work without blocking threads unnecessarily.
Use Task.WhenAll to run independent asynchronous I/O operations concurrently while handling exceptions, cancellation, and dependency limits.
Explains JWT validation, trusted issuers, audiences, expiration, signing keys, claims, and server-side authorization boundaries.
Captures test activities to prove one incoming request and its outgoing HTTP dependency share trace context.