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.
465 results across 1 active filter
Page 5 of 20
Investigate resource spikes on App Service after a new .NET API release.
Diagnoses duplicate processing from Azure Service Bus lock loss or Storage Queue visibility behavior without repeating generic idempotency theory.
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.
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.
Implements duplicate suppression while preserving the first event for each idempotency key.
Define logs, metrics, traces, alerts, and dashboards needed to operate an ASP.NET Core API in production.
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.
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.
Designs feature flag storage, targeting, safe defaults, auditability, and rollout observability for backend behavior.
Explains batching, tracking control, idempotency, validation, and operational safety for large EF Core imports.
Explains alert design based on user-impact symptoms, SLOs, burn rate, thresholds, and avoiding noisy cause-only alerts.
Explains useful message metadata for tracing, idempotency, ownership, versioning, and support diagnostics.
Designs tenant isolation across API, data, cache, background jobs, search, and admin access.
Designs an activity feed with event capture, fan-out strategy, pagination, privacy, and read performance.
Introduces API versions only for unavoidable breaks, with explicit routing, versioned documentation, migration support, telemetry, deprecation, and removal criteria.