Loading
Pick a focused question that fits your time, stack, and interview goal.
281 results across 1 active filter
Page 9 of 12
Compare public and internal APIs in terms of compatibility, documentation, security, support, and evolution speed.
Fits database command timeouts into endpoint latency budgets while diagnosing slow SQL, blocking, pool pressure, and uncertain write outcomes.
Investigate and fix a race condition caused by shared mutable state in a .NET service.
Separates restricted mutation access from a stable immutable value and chooses snapshots or structural sharing deliberately.
Implements safe redaction of known sensitive keys in a dictionary before logging.
Replaces a parent query plus one status query per row with one server-side projection.
Uses metadata-driven behavior deliberately and protects reflection-dependent code when publishing with trimming or ahead-of-time compilation.
Separates dependency registration from per-request middleware and endpoint composition in modern ASP.NET Core startup.
Uses two isolated EF Core contexts to reproduce a real optimistic-concurrency conflict through the API boundary.
Handles the request body as a forward-only resource, buffers only when necessary, and enforces limits before large input consumes the service.
Explains why committed headers cannot be replaced, how streaming failures behave, and how middleware preserves response ownership.
Implements a bounded async retry helper that respects cancellation and does not retry every exception blindly.
Wraps a complete explicit transaction in the provider execution strategy and creates fresh context state for each retry attempt.
Persists a job and outbox command before returning a status URL for long-running work.
Produces field-keyed validation errors through one reusable endpoint boundary.
Implements top-K frequency selection with deterministic tie-breaking.
Reviews a proposed response-field rename by finding consumers, classifying the break, choosing a migration path, and proving rollout and removal are safe.
Places identity, optional selection controls, command representations, headers, and files in predictable HTTP locations while accounting for security, caching, limits, and model binding.
Explains how callers use one contract while runtime dispatch selects implementation, then connects that mechanism to extensible behavior.
Persists domain state and its outbox message in one SaveChanges transaction without publishing inside the request transaction.
Wraps a pooled DbContext factory so every request assigns tenant state before a global query filter can run.
Separates identity issuance, untrusted client behavior, API authorization, tenant isolation, resource checks, and token-handling responsibilities.
Builds dependency-specific timeout budgets that contain slow SQL, HTTP, and cache calls without creating unsafe retries or ambiguous writes.
Explains EF Core shadow properties for audit or infrastructure columns with practical .NET data-access examples and production trade-offs.