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.
1345 results
Page 37 of 57
Explains what happens when a hot key expires and how request coalescing, TTL jitter, background refresh, and stale serving help.
Guards a mutation immediately, exposes pending state, and restores the command after failure.
Finds circular lock acquisition and replaces timing-dependent nested locking with a stable order or a simpler ownership boundary.
Explains frontend guards, backend idempotency, pending state, retries, and duplicate-safe mutation design.
Explains insecure direct object reference risks and how APIs enforce ownership, tenant scope, and authorization per resource.
Explains why request DTOs should expose only allowed fields and how server-owned fields stay protected.
Updates only public mutable fields and leaves ownership, status, and audit values server-controlled.
Secures webhooks, previews, imports, and remote-file fetches with destination policy, DNS and redirect defenses, egress controls, limits, and observability.
Uses RFC 9457 Problem Details as a stable, safe error contract with documented problem types, actionable extensions, and centralized framework mapping.
Explains EF Core projections for API read models that need related names, counts, and summaries without loading full graphs.
Builds a read-only EF Core projection with aggregates, stable ordering, and bounded results instead of loading an entity graph.
Explain why request cancellation should flow into EF Core queries and where it does or does not help.
Explains correlation IDs across request logs, dependency calls, queues, workers, and support investigations.
Carries the ASP.NET Core request token into a bounded EF Core query while keeping cancellation separate from business rollback guarantees.
Builds a typed functional canDeactivate guard and editor contract that protects dirty work until a save has actually succeeded.
Maps a named capability to an ASP.NET Core policy and enforces it at the endpoint boundary.
Explains token storage, cookies, XSS, CSRF, and why browser UI never replaces server authorization.
Explains where secrets and tokens should live, what not to log, how rotation works, and how client storage changes risk.
Uses fake time and HttpTestingController to complete requests out of order and prove latest-query state, recovery, and teardown.
Combines ThreadPool counters, repeated stack snapshots, and wait-event traces to distinguish blocked workers from CPU or dependency pressure.
Compare public and internal APIs in terms of compatibility, documentation, security, support, and evolution speed.
Builds a story about challenging a risky requirement while staying constructive and product-oriented.
Compares replacement and partial-update semantics, including omitted fields, patch formats, validation, and concurrency.
Explains useful quality gates for .NET CI pipelines, including tests, analysis, security, migrations, and smoke checks.