Loading
Pick a focused question that fits your time, stack, and interview goal.
473 results across 1 active filter
Page 20 of 20
Explains Aspire as a code-first application model and developer experience without confusing it with a production runtime or architecture style.
Covers custom domains, TLS, HTTPS, allowed hosts, CORS boundaries, and production-facing endpoint hygiene for App Service APIs.
Explains a practical CI/CD pipeline for .NET applications from code change to deployment verification.
Practices incident response after an OOM: restore service, collect evidence, identify trigger, and prevent recurrence.
Distinguishes deterministic cleanup from finalization and explains resource ownership in normal application code.
Explains asynchronous cleanup for resources whose shutdown path needs async work, such as flushing or closing remote connections.
Compares Azure hosting choices for a .NET API using operational complexity, scaling model, deployment ownership, and workload shape.
Covers large exports, uploads, and API responses where bounded memory matters more than convenience.
Explains minimal APIs, endpoint groups, dependency injection, typed results, filters, and when they fit real services.
Introduces lower-level allocation tools while emphasizing measurement, ownership, and safe usage.
Explains returning EF entities from APIs with practical .NET data-access examples and production trade-offs.
Covers the Large Object Heap, big buffers, fragmentation pressure, and practical ways to avoid loading too much at once.
Explains how middleware order affects authentication, authorization, error handling, routing, CORS, and response behavior.
Explains cache memory growth, eviction, size limits, stale data, and why cache design needs explicit bounds.
Reviews a captive scoped dependency as both a lifetime and concurrency bug, then replaces it with explicit per-operation scopes and minimal immutable work data.
Diagnoses lost struct mutations and explains how readonly access can trigger defensive copies.
Explains local filesystem limits, multiple instances, in-memory state, distributed cache, durable storage, and scale-out-safe API design.