Skip to content

Tracks Drills Topics Technologies Tech stacks Skill areas

Tracks Drills Guides

Loading

Aporeon

Technical interview practice, from one developer to another.

Guides About Editorial standards Support Privacy Terms Refund policy

Production

Production debugging, logging, dependency failures, performance, rate limiting, and operational behavior.

22 drillsPractice one at a timeOrdered pathArchitecture scenarioDebugging scenarioConcept questionComparison question

Recommended start

Correlation IDs

Use correlation IDs, structured logs, and logging scopes to make API failures traceable in production.

Medium~10 minStep 1 of 22

Practice this drill Choose another

Search

22 of 22 shown

1Correlation IDsRecommended startUse correlation IDs, structured logs, and logging scopes to make API failures traceable in production.Architecture scenarioMedium~10 min.NETASP.NET CoreC#Practice 2Dependency TimeoutsBuilds dependency-specific timeout budgets that contain slow SQL, HTTP, and cache calls without creating unsafe retries or ambiguous writes.Architecture scenarioMedium~10 min.NETASP.NET CoreC#Practice 3Slow API DiagnosisInvestigate a slow API by checking database queries, blocking async, dependency latency, serialization, logging, and runtime pressure.Debugging scenarioHard~12 min.NETASP.NET CoreC#Practice 4401 vs 403 DebuggingDebugs ASP.NET Core authentication challenges and authorization forbids across schemes, token validation, policies, claims, tenants, and resource checks.Debugging scenarioMedium~10 min.NETASP.NET CoreC#Practice 5Broken ValidationInvestigate an endpoint accepting invalid data or returning inconsistent validation errors.Debugging scenarioMedium~10 min.NETASP.NET CoreC#Practice 6No Correlation IDHandle a production support case where logs exist but related request events cannot be connected.Debugging scenarioMedium~10 min.NETASP.NET CoreC#Practice 7Dependency Timeout IncidentInvestigate and mitigate API failures caused by a slow or failing downstream dependency.Debugging scenarioHard~12 min.NETASP.NET CoreC#Practice 8Rate LimitingDesign and debug rate limiting while protecting the API without blocking legitimate users and integrations.Architecture scenarioHard~12 min.NETASP.NET CoreC#Practice 9Duplicate Create RetryInvestigate and fix an API where client retries create duplicate orders, payments, or records.Debugging scenarioHard~12 min.NETASP.NET CoreC#Practice 10Thread Pool StarvationDiagnose an ASP.NET Core API that becomes slow because request threads are blocked or exhausted.Debugging scenarioHard~12 min.NETASP.NET CoreC#Practice 11API ObservabilityDefine logs, metrics, traces, alerts, and dashboards needed to operate an ASP.NET Core API in production.Architecture scenarioHard~12 min.NETASP.NET CoreC#Practice 12Batch Memory SafetyCovers chunking, bounded concurrency, scoped dependencies, progress, retries, and avoiding full-dataset memory spikes.Architecture scenarioHard~12 min.NETASP.NET CoreC#Practice 13Heap Dump ComparisonExplains when to capture dumps, what to compare, and how to use roots without turning dumps into guesswork.Debugging scenarioHard~12 min.NETASP.NET CoreC#Practice 14LOH PressureTurns LOH theory into an API investigation around large payloads, buffers, serialization, and concurrency.Debugging scenarioHard~12 min.NETASP.NET CoreC#Practice 15Memory MetricsIdentifies useful memory and GC signals for alerting without overwhelming the team with noisy telemetry.Concept questionMedium~7 min.NETASP.NET CoreC#Practice 16Upload Memory LeakUses file upload processing to practice bounded memory, stream ownership, temporary files, and retained buffers.Debugging scenarioHard~12 min.NETASP.NET CoreC#Practice 17Dump SecurityExplains why memory diagnostics need access control, retention limits, and careful handling of secrets and user data.Concept questionMedium~7 min.NETASP.NET CoreC#Practice 18Application Insights BaselineCovers useful request, dependency, exception, log, metric, and availability telemetry for a production .NET API.Concept questionEasy~5 min.NETApplication InsightsASP.NET CorePractice 19OpenTelemetry vs App Insights SDKCompares OpenTelemetry-based Azure Monitor instrumentation with older Application Insights SDK patterns for .NET services.Comparison questionMedium~7 min.NETApplication InsightsASP.NET CorePractice 20Correlation and TracingExplains correlation IDs, distributed tracing, dependency telemetry, message boundaries, and logs across App Service, queues, and downstream APIs.Concept questionMedium~7 min.NETApplication InsightsASP.NET CorePractice 21Azure Monitor AlertsCovers symptom-based alerting for latency, error rate, availability, dependency failures, queue length, and resource pressure.Concept questionMedium~7 min.NETApplication InsightsAzurePractice 22Scale-Out StateExplains scale-out bugs from in-memory sessions, local caches, background queues, uploaded files, and per-instance behavior.Debugging scenarioMedium~10 min.NETApplication InsightsASP.NET CorePractice

Practice order

22 drillsOne at a time

1Correlation IDsUp next / Medium / ~10 min
2Dependency TimeoutsMedium / ~10 min
3Slow API DiagnosisHard / ~12 min
4401 vs 403 DebuggingMedium / ~10 min
5Broken ValidationMedium / ~10 min
6No Correlation IDMedium / ~10 min
7Dependency Timeout IncidentHard / ~12 min
8Rate LimitingHard / ~12 min

+14 more drills in this section