Loading
Pick a focused question that fits your time, stack, and interview goal.
584 results across 1 active filter
Page 13 of 25
Explains a practical approach to diagnosing failed builds, tests, package restore, environment issues, or flaky checks.
Explains a structured response to a failed production deployment in a .NET application.
Explains safe EF Core migrations with practical .NET data-access examples and production trade-offs.
Explains release notes and changelog thinking for engineering, QA, support, and product communication.
Explains semantic versioning for .NET applications and how it communicates release impact.
Explains transient database errors, retry strategy, EF Core execution strategy, idempotency, timeouts, and avoiding retry storms.
Propagates request cancellation through async dependencies while keeping committed side effects and timeout policy explicit.
Covers App Service app settings, environment-specific configuration, restarts, slot settings, and avoiding hard-coded production values.
Explains DbContext lifetime and unit-of-work boundaries with practical .NET data-access examples and production trade-offs.
Explain how Task.WhenAll behaves when one or more tasks fail and how to inspect failures safely.
Covers using managed identity and Microsoft Entra authentication for Azure SQL access from a .NET API.
Covers allocation rate, collection frequency, latency symptoms, and safe production steps for GC-heavy services.
Explains health endpoints, readiness versus liveness, warm-up, dependency checks, and safe App Service health behavior.
Covers queue-backed work, idempotency, retries, visibility timeout, poison messages, progress tracking, and choosing Storage Queues or Service Bus.
Covers deployment logs, startup failures, runtime stack, app settings, missing files, Key Vault references, and post-deployment diagnosis.
Gives a practical incident flow for memory growth using metrics, traffic correlation, heap evidence, and safe mitigation.
Explains same-artifact promotion, environment-specific configuration, approvals, smoke testing, drift detection, and production traceability.
Frames allocation reduction as measurement-driven API work rather than premature micro-optimization.
Explains a practical Git workflow for a .NET team using branches, pull requests, code review, and protected main branches.
Describes lazy iterator execution, state-machine behavior, early termination, resource disposal, and repeat-enumeration consequences.
Keeps HttpContext inside the active request, avoids concurrent access, and copies only immutable data needed by later work.
Explains how IHttpClientFactory separates short-lived clients from pooled handlers and how concurrency, DNS, resilience, and DI lifetimes still require judgment.
Chooses immutable values and controlled mutable entities based on identity, concurrency, invariants, allocation cost, and update semantics.
Validates size and signature, writes under a generated storage key, and keeps untrusted files outside the public web root.