Loading
Pick a focused question that fits your time, stack, and interview goal.
591 results across 1 active filter
Page 2 of 25
Explains trusted tenant context, membership checks, tenant-scoped queries, cache keys, and background job propagation.
Explains dynamic filters and SQL injection risk with practical .NET data-access examples and production trade-offs.
Builds a story about protecting quality while still making practical delivery decisions.
Explains when a value is wrapped as an object, why unboxing is exact, and how generic APIs can avoid hidden allocations.
Designs a pragmatic branching strategy for normal releases, hotfixes, and production traceability.
Explains URL-backed filters, API query parameters, pagination, sorting, empty states, and shareable list views.
Explains admin list/edit/delete workflows with capability checks, audit events, confirmation, validation, and recovery.
Checks health, authentication, and one critical read flow after deployment without creating persistent business data.
Implements a safe in-memory paging helper with metadata and boundary handling.
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.
Implements invoice total calculation with quantity, unit price, percentage discount, and rounding.
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.
Chooses contracts and shared implementation based on substitutability, state ownership, evolution, and inheritance constraints.
Builds a story about resisting unnecessary complexity and choosing maintainable design.