Loading
Pick a focused question that fits your time, stack, and interview goal.
491 results across 1 active filter
Page 13 of 21
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.
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.
Controls nondeterministic inputs without weakening production behavior or hard-coding test-only branches.
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.
Implements interval merging for scheduling-style time ranges with sorted output.
Compares merge and rebase in team workflows, including history clarity, conflict handling, and shared branch safety.
Compare middleware and filters by scope, timing, endpoint context, and practical use cases.
Explains how to deploy database changes safely with .NET APIs using backward-compatible steps.
Compare request binding and validation responsibilities in ASP.NET Core APIs.
Starts object-oriented design from cohesive state and behavior instead of creating classes for every noun in a requirement.
Chooses between a modular monolith and microservices using domain boundaries, team ownership, scaling, deployment, data consistency, and operational cost.
Explains operational signals for queue-backed systems and how to respond when consumers fall behind.
Turns a useful Aspire development model into explicit production infrastructure without treating the local AppHost as the runtime platform.