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.
465 results across 1 active filter
Page 13 of 20
Explains how to deploy database changes safely with .NET APIs using backward-compatible steps.
Compare request binding and validation responsibilities in ASP.NET Core APIs.
Starts object-oriented design from cohesive state and behavior instead of creating classes for every noun in a requirement.
Chooses between a modular monolith and microservices using domain boundaries, team ownership, scaling, deployment, data consistency, and operational cost.
Explains operational signals for queue-backed systems and how to respond when consumers fall behind.
Turns a useful Aspire development model into explicit production infrastructure without treating the local AppHost as the runtime platform.
Explains when backend work belongs in a queue instead of slow or unreliable inline request handling.
Explains multi-tenant data filtering with practical .NET data-access examples and production trade-offs.
Uses nullable annotations as a compile-time contract while still validating untrusted and legacy runtime inputs.
Separates OAuth authorization from OpenID Connect authentication and explains why modern interactive clients use authorization code with PKCE.
Explains offset versus cursor pagination with practical .NET data-access examples and production trade-offs.
Uses stable extension points for genuinely variable behavior while avoiding speculative abstractions and configuration-driven branching.
Designs an EF Core optimistic-concurrency contract around tokens, conflict policy, HTTP semantics, merge behavior, and real relational tests.
Uses a transactional outbox to make a local state change durably publishable while accepting at-least-once delivery and operating the backlog safely.
Separates compile-time overload selection from runtime virtual dispatch and diagnoses method hiding through a base reference.
Chooses between EF Core complex types, owned entities, and regular entities from value semantics, identity, ownership, querying, and storage needs.
Implements descending keyset pagination with a compound cursor and stable ordering.
Parses a simple filter expression into a validated dictionary without accepting arbitrary keys.
Uses type, property, relational, and list patterns to express decisions while keeping null and unhandled cases explicit.
Places invariants and state transitions near the data they protect while keeping orchestration and infrastructure out of domain entities.
Explains how to verify a .NET release after deployment using smoke tests, metrics, logs, and business signals.
Preserves order only within the business key that requires it, while handling hot keys, gaps, stale events, replay, and poison messages explicitly.
Explains what happens when a hot key expires and how request coalescing, TTL jitter, background refresh, and stale serving help.
Explains insecure direct object reference risks and how APIs enforce ownership, tenant scope, and authorization per resource.