Loading
Pick a focused question that fits your time, stack, and interview goal.
613 results across 1 active filter
Page 16 of 26
Uses per-dependency concurrency limits, queues, pools, and workload partitions to stop one failing path from exhausting the whole API.
Explains transaction isolation levels 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.
Designs a reliable CI test system with fast feedback, deliberate test stages, bounded parallelism, visible flakiness, useful diagnostics, and clear ownership.
Separates the ASP.NET Core HTTP server from proxy, TLS, load-balancing, process-management, and forwarded-header responsibilities.
Balances declarative transformations with explicit control flow when allocation, early exit, mutation, diagnostics, or complex state matters.
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.
Builds a story about learning a new technology in a structured way and applying it safely.
Design a bounded-concurrency approach for calling an external API safely from .NET code.
Predicts when an in-memory LINQ pipeline runs and prevents repeated work, changed results, and hidden side effects.
Explains LINQ translation boundaries with practical .NET data-access examples and production trade-offs.
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.
Designs logs, metrics, traces, dashboards, and alerts around user outcomes, service objectives, dependencies, saturation, privacy, cardinality, and actionable incident response.
Builds a story about choosing a pragmatic technical path under time pressure while preserving future safety.
Controls nondeterministic inputs without weakening production behavior or hard-coding test-only branches.
Uses declarative infrastructure, reviewed plans, environment parameters, protected deployment identities, state management, and drift control without hiding operational risk.
Maps a stable ProblemDetails validation contract to fields and a fallback form-level error.
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.
Chooses when to keep a sequence lazy and when to create a stable collection with ToList, ToArray, or another deliberate materialization.
Explains cache observability across hit rate, latency, source load, memory, evictions, stale data, and fallback behavior.