Loading
Pick a focused question that fits your time, stack, and interview goal.
439 results across 1 active filter
Page 2 of 19
Builds a small, immutable, non-root .NET runtime image with controlled inputs, external configuration, graceful lifecycle behavior, and a practical patching strategy.
Compares build artifacts and deployment packages in a .NET release pipeline.
Implements bounded filtering and deterministic keyset pagination without accepting arbitrary query expressions.
Creates a resource through an explicit request DTO and returns typed 201, 409, and validation outcomes.
Explains permission-aware navigation, guarded routes, server authorization, stale capabilities, and safe 401/403 handling.
Explains composing dynamic LINQ filters while keeping query execution in SQL and index-friendly.
Compares caching response-shaped read models with caching domain entities or raw database objects.
Design background jobs that handle cancellation, retries, and duplicate execution without corrupting external state.
Use CancellationToken to stop wasted work when clients disconnect, timeouts expire, or background operations are being shut down.
Explain why CancellationTokenSource lifetime matters and how careless timeout creation can leak timers or resources.
Explains dependency duration, error rate, timeout rate, query tagging, Redis latency, HTTP downstream calls, and endpoint correlation.
Use Channel<T> to coordinate producer/consumer background processing inside a .NET service while respecting backpressure and shutdown.
Builds a story about resisting unnecessary complexity and choosing maintainable design.
Explains how TTL choices balance freshness, load reduction, user expectations, and operational safety.
Maps business invariants and stale-data tolerance to strong or eventual consistency, explicit failure behavior, reconciliation, and user-visible state.
Reason through mitigation choices during a live App Service production incident.
Maps creation, updates, asynchronous work, validation, authorization, conflicts, and failures to useful HTTP outcomes.
Explains when optimistic UI is worth it, when to wait for server confirmation, and how to recover from rejected mutations.
Compares rollback, roll-forward, feature kill switches, scaling, and degraded mode as incident mitigations.
Selects small structural and behavioral patterns from the problem being solved instead of pattern-name recognition.
Chooses database test infrastructure by the provider behavior a test must prove.
Builds a proportionate test plan from blast radius, failure probability, detectability, and reversibility.
Explains inward dependency flow, stable business policy, adapters, and when a smaller project structure is enough.
Review async .NET code that does not accept or propagate CancellationToken and explain the practical production risk.