Skip to content

Tracks Drills Topics Technologies Tech stacks Skill areas

Tracks Drills Topics

Loading

Aporeon

Technical interview practice, from one developer to another.

About Privacy Terms

.NET Full Stack

API Reliability & Operations

Authentication boundaries, cancellation, timeouts, retries, rate limiting, observability, and production debugging.

14 drillsPractice one at a timeOrdered pathComparison questionArchitecture scenarioDebugging scenarioSystem design

Recommended start

AuthN vs AuthZ

Separates identity establishment from permission decisions and applies ASP.NET Core schemes, policies, tenant boundaries, ownership checks, and correct challenge or forbid behavior.

Easy~5 minStep 1 of 14

Practice this drill Choose another

Search

14 of 14 shown

1AuthN vs AuthZRecommended startSeparates identity establishment from permission decisions and applies ASP.NET Core schemes, policies, tenant boundaries, ownership checks, and correct challenge or forbid behavior.Comparison questionEasy~5 min.NETASP.NET CoreC#Practice 2Correlation IDsUse correlation IDs, structured logs, and logging scopes to make API failures traceable in production.Architecture scenarioMedium~10 min.NETASP.NET CoreC#Practice 3Dependency 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 4EF Core CancellationExplain why request cancellation should flow into EF Core queries and where it does or does not help.Architecture scenarioMedium~10 min.NETASP.NET CoreC#Practice 5Slow 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 6401 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 7Broken ValidationInvestigate an endpoint accepting invalid data or returning inconsistent validation errors.Debugging scenarioMedium~10 min.NETASP.NET CoreC#Practice 8No Correlation IDHandle a production support case where logs exist but related request events cannot be connected.Debugging scenarioMedium~10 min.NETASP.NET CoreC#Practice 9Dependency Timeout IncidentInvestigate and mitigate API failures caused by a slow or failing downstream dependency.Debugging scenarioHard~12 min.NETASP.NET CoreC#Practice 10Rate LimitingDesign and debug rate limiting while protecting the API without blocking legitimate users and integrations.Architecture scenarioHard~12 min.NETASP.NET CoreC#Practice 11Duplicate Create RetryInvestigate and fix an API where client retries create duplicate orders, payments, or records.Debugging scenarioHard~12 min.NETASP.NET CoreC#Practice 12Thread 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 13API 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 14Security BoundariesSeparates identity issuance, untrusted client behavior, API authorization, tenant isolation, resource checks, and token-handling responsibilities.System designHard~20 min.NETASP.NET CoreC#Practice

Practice order

14 drillsOne at a time

1AuthN vs AuthZUp next / Easy / ~5 min
2Correlation IDsMedium / ~10 min
3Dependency TimeoutsMedium / ~10 min
4EF Core CancellationMedium / ~10 min
5Slow API DiagnosisHard / ~12 min
6401 vs 403 DebuggingMedium / ~10 min
7Broken ValidationMedium / ~10 min
8No Correlation IDMedium / ~10 min

+6 more drills in this section