Loading
Pick a focused question that fits your time, stack, and interview goal.
460 drills fit a 10-minute session. Closest fits first.
Page 13 of 20
Explains refetching, targeted invalidation, stale data, optimistic updates, server truth, and user feedback after mutations.
Chooses the correct typed-options lifetime, validates required configuration early, and handles runtime changes deliberately.
Explains `IQueryable` versus `IEnumerable` in EF Core with practical .NET data-access examples and production trade-offs.
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.
Explains substitutability through inputs, outputs, side effects, and failure behavior rather than inheritance syntax alone.
Compare lock and SemaphoreSlim for protecting shared state and coordinating async workflows.
Designs logs, metrics, traces, dashboards, and alerts around user outcomes, service objectives, dependencies, saturation, privacy, cardinality, and actionable incident response.
Controls nondeterministic inputs without weakening production behavior or hard-coding test-only branches.
Explains field-level and form-level error mapping from API responses into a usable frontend form experience.
Chooses when to keep a sequence lazy and when to create a stable collection with ToList, ToArray, or another deliberate materialization.
Compares merge and rebase in team workflows, including history clarity, conflict handling, and shared branch safety.
Compare middleware and filters by scope, timing, endpoint context, and practical use cases.
Compare request binding and validation responsibilities in ASP.NET Core APIs.
Uses discriminated unions to represent valid UI states and make transitions exhaustive.
Chooses between a modular monolith and microservices using domain boundaries, team ownership, scaling, deployment, data consistency, and operational cost.
Explains how to monitor external and internal dependencies after a .NET service release.
Separates OAuth authorization from OpenID Connect authentication and explains why modern interactive clients use authorization code with PKCE.
Uses stable extension points for genuinely variable behavior while avoiding speculative abstractions and configuration-driven branching.
Compares OpenTelemetry-based Azure Monitor instrumentation with older Application Insights SDK patterns for .NET services.
Chooses between EF Core complex types, owned entities, and regular entities from value semantics, identity, ownership, querying, and storage needs.
Explains versioning and releasing shared .NET libraries or NuGet packages safely.