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.
405 results across 1 active filter
Page 11 of 17
Processes a large import in chunks with fresh DbContexts, idempotent keys, cancellation, and bounded tracker growth.
Explains how to respond to a production incident caused by a bad release.
Verifies the exact request bytes, rejects stale signatures, deduplicates event ids, and queues processing durably.
Explains how to inspect EF Core generated SQL and connect LINQ shape to database execution behavior.
Uses WebApplicationFactory with test-only authentication and isolated dependencies to exercise the real ASP.NET Core pipeline.
Uses the real ASP.NET Core pipeline while replacing only environment-specific boundaries deliberately.
Designs consumer-focused contracts that reduce accidental authority and coupling without producing meaningless one-method wrappers.
Explains delete-on-write, versioned keys, event-driven invalidation, and the race conditions around cache freshness.
Investigates a growing-data EF Core slowdown through one correlated request, generated SQL, representative parameters, execution plan, waits, query shape, measured repair, and guarded rollout.
Explains how to triage post-release 500 errors using deployment correlation, logs, traces, feature flags, and rollback safety.
Explains how to diagnose 401/403 spikes across token validation, identity provider issues, clock skew, deployment changes, and abuse.
Chooses the correct typed-options lifetime, validates required configuration early, and handles runtime changes deliberately.
Compares rollback, reset, schema, database, and tenant isolation without hiding transaction or parallelism limits.
Uses per-dependency concurrency limits, queues, pools, and workload partitions to stop one failing path from exhausting the whole API.
Treats serializer naming, nulls, enums, converters, dates, references, and polymorphism as versioned client-facing behavior.
Separates the ASP.NET Core HTTP server from proxy, TLS, load-balancing, process-management, and forwarded-header responsibilities.
Explains when LINQ is enough, when raw SQL is clearer, and how to keep raw SQL safe and maintainable.
Explains the small set of Kubernetes resources needed to run and expose a replicated stateless API without drowning the answer in platform vocabulary.
Design a bounded-concurrency approach for calling an external API safely from .NET code.
Explains substitutability through inputs, outputs, side effects, and failure behavior rather than inheritance syntax alone.
Uses `AsSplitQuery` deliberately for a tracked aggregate with multiple collections and explains its consistency boundary.
Compare lock and SemaphoreSlim for protecting shared state and coordinating async workflows.
Explains field-level and form-level error mapping from API responses into a usable frontend form experience.
Relies on a database unique constraint and translates only the expected provider error into a domain conflict.