Loading
Pick a focused question that fits your time, stack, and interview goal.
199 results across 1 active filter
Page 3 of 9
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.
Explains high database CPU after an API change with practical .NET data-access examples and production trade-offs.
Investigate production HTTP 500 errors that start immediately after a deployment slot swap.
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 how to decide if caching is the right fix for a slow API endpoint instead of query tuning or contract changes.
Define logs, metrics, traces, alerts, and dashboards needed to operate an ASP.NET Core API in production.
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.
Explains how EF Core SaveChanges, transactions, and an outbox keep database changes and messages consistent.
Makes POST retries return one durable business outcome by combining scoped keys, request identity, atomic ownership, response replay, and reconciliation.
Builds a race-safe upsert around database-enforced identity, explicit conflict semantics, retries, ordering, and side-effect boundaries.
Explains dashboard panels that help an API owner see user impact, dependency health, releases, and current incidents.
Explains how systems behave when the broker is down or slow and how backpressure protects callers and dependencies.
Explains health checks that prove an API can serve traffic without becoming fragile dependency probes.
Protects transactional traffic from reporting load through freshness requirements, bounded asynchronous jobs, tuned summaries, workload isolation, replicas or warehouses, and explicit capacity gates.
Explains retry strategy for transient failures and poison-message handling for permanent failures.
Uses field data, lab evidence, and release correlation to diagnose LCP, INP, and CLS regressions without guessing.