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.
167 results across 1 active filter
Page 7 of 7
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.
Explains when a Next.js route layer helps with cookies, tokens, aggregation, and UI-specific API adaptation.
Use correlation IDs, structured logs, and logging scopes to make API failures traceable in production.
Use OpenAPI for API design, client integration, testing, and contract review in ASP.NET Core services.
Explains read models for complex API screens with practical .NET data-access examples and production trade-offs.
Explains middleware continuation, terminal delegates, path branches, short-circuiting, and two-way request and response flow.
Implements a small validation helper for date ranges with clear error messages.
Chooses code organization from change locality, shared policy, and cross-cutting needs rather than adopting one folder structure universally.
Explains LINQ deferred execution with EF Core with practical .NET data-access examples and production trade-offs.
Explains how route values, query strings, headers, and request bodies become typed endpoint input.
Explains N+1 queries in EF Core with practical .NET data-access examples and production trade-offs.
Explains Aspire as a code-first application model and developer experience without confusing it with a production runtime or architecture style.
Covers large exports, uploads, and API responses where bounded memory matters more than convenience.
Explains minimal APIs, endpoint groups, dependency injection, typed results, filters, and when they fit real services.
Explains returning EF entities from APIs with practical .NET data-access examples and production trade-offs.
Explains how middleware order affects authentication, authorization, error handling, routing, CORS, and response behavior.
Reviews a captive scoped dependency as both a lifetime and concurrency bug, then replaces it with explicit per-operation scopes and minimal immutable work data.
Explains how to choose an E2E flow, control test data, avoid brittleness, and cover frontend/API integration risk.