Pick a focused question that fits your time, stack, and interview goal.
How much time do you have?
Show one-drill sessions you can finish now.
206 results across 1 active filter
Page 8 of 9
Explains identity versus permission checks in API request handling and why both boundaries need server-side enforcement.
Chooses event retention and compaction from consumer outage, replay, rebuild, audit, and disaster-recovery requirements rather than storage cost alone.
Sets bounded timeout and deadline policies across callers, APIs, databases, and external services without hiding unknown outcomes.
Authorizes metadata before opening storage and streams the file with safe headers and range support.
Selects synchronous calls, asynchronous messaging, or a deliberate combination based on user feedback, coupling, latency, durability, and failure behavior.
Expresses allowed and denied capability combinations as one parameterized API integration test.
Proves repeated requests with one idempotency key create one resource and return a consistent result.
Proves that one authenticated user cannot read or modify another user's private resource.
Uses a controllable fake HTTP handler to prove request cancellation reaches a downstream dependency.
Walks API pages through equal sort values and verifies no duplicate or missing resource ids.
Verifies status, content type, stable error extensions, and field errors for an invalid API request.
Diagnose an ASP.NET Core API that becomes slow because request threads are blocked or exhausted.
Explains tracing one user action across browser, frontend server, API, dependencies, logs, metrics, and safe diagnostics.
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.
Uses EF Core context pooling only when reusable context state, tenant isolation, and underlying connection state are controlled and tested.
Explains delayed delivery, scheduled work, reminders, retry timing, cancellation, and clock-related trade-offs.
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 route handlers as a frontend server boundary for cookies, API adaptation, auth, and backend calls.
Use OpenAPI for API design, client integration, testing, and contract review in ASP.NET Core services.