Pick a focused question that fits your time, stack, and interview goal.
How much time do you have?
Show one-drill sessions you can finish now.
1345 results
Page 9 of 57
Explains high database CPU after an API change with practical .NET data-access examples and production trade-offs.
Diagnose a post-swap HTTP 500 from supplied database-migration evidence and choose a safe mitigation.
Explains why server HTML and client render can disagree, how to debug it, and how to avoid mismatch-prone code.
Diagnose missing trace continuity when an API enqueues work processed by an Azure worker.
Diagnose a .NET API that cannot connect to Azure SQL using managed identity.
Investigate a .NET API that appears to run but sends little or no telemetry to Application Insights.
Explains how to troubleshoot absent logs or telemetry by checking configuration, sampling, sinks, levels, deployment, and correlation.
Investigate messages that repeatedly fail and move to a poison queue or dead-letter queue.
Explains a constraint-first approach to responsive layout, intrinsic sizing, overflow, and content resilience.
Explains how to decide if caching is the right fix for a slow API endpoint instead of query tuning or contract changes.
Implements duplicate suppression while preserving the first event for each idempotency key.
Builds an interaction-triggered deferrable view with a stable accessible placeholder and deterministic tests for placeholder, loading, error, and completion.
Turns business recovery targets into right-sized backup, restore, standby, failover, validation, ownership, and rehearsal plans.
Define logs, metrics, traces, alerts, and dashboards needed to operate an ASP.NET Core API in production.
Explains how to design DTOs, response shapes, UI needs, API compatibility, and frontend/backend ownership for a feature.
Distinguishes callable delegate values from publisher-controlled events and makes subscription lifetime explicit.
Distinguishes explicit dependency injection from runtime service lookup and identifies the narrow framework boundaries where scoped resolution is legitimate.
Keeps business policy independent from infrastructure while centralizing concrete dependency assembly at the application edge.
Explains the difference between deploying code and releasing functionality to users using feature flags.
Designs an async export flow for large reports without blocking API requests or exhausting database and memory resources.
Designs dashboard APIs with precomputed metrics, freshness rules, query cost control, and drill-down support.
Combines restrained autonomy, curated tools, durable state, approval, memory, recovery, MCP trust, evaluation, and operational controls.
Designs explicit workflow states, allowed transitions, guard rules, audit history, idempotency, and operational repair paths.
Design API error handling across validation errors, conflicts, auth failures, not-found responses, and unexpected exceptions.