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.
439 results across 1 active filter
Page 5 of 19
Investigate resource spikes on App Service after a new .NET API release.
Traces duplicate side effects across message delivery, lock ownership, settlement, durable job state, and external idempotency, then repairs affected users safely.
Investigate production HTTP 500 errors that start immediately after a deployment slot swap.
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 how to decide if caching is the right fix for a slow API endpoint instead of query tuning or contract changes.
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 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.
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.