Loading
Pick a focused question that fits your time, stack, and interview goal.
613 results across 1 active filter
Page 18 of 26
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.
Explains versioning and releasing shared .NET libraries or NuGet packages safely.
Implements descending keyset pagination with a compound cursor and stable ordering.
Compare Parallel.ForEachAsync and Task.WhenAll for processing collections with async work and controlled concurrency.
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.
Chooses a parallel API based on whether the workload is a data query or an imperative loop and keeps CPU work pure, bounded, and measurable.
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.
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 ASP.NET 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.