Loading
Pick a focused question that fits your time, stack, and interview goal.
491 results across 1 active filter
Page 14 of 21
Explains when backend work belongs in a queue instead of slow or unreliable inline request handling.
Predicts how the built-in container resolves repeated service registrations and chooses explicit selection without service-location logic.
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.
Compares OpenTelemetry-based Azure Monitor instrumentation with older Application Insights SDK patterns for .NET services.
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.
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 ASP.NET mapping.