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

Resilience & Dependency Failures Essentials

Timeout budgets, safe retries, circuit breakers, bulkheads, degraded behavior, health, dependency telemetry, overload protection, integration boundaries, incident mitigation, and availability trade-offs.

16 drillsPractice one at a timeOrdered pathConcept questionComparison questionSystem designDebugging scenario

Recommended start

Timeout Budgets

Sets bounded timeout and deadline policies across callers, APIs, databases, and external services without hiding unknown outcomes.

Medium~7 minStep 1 of 16

Practice this drill Choose another

Search

16 of 16 shown

1Timeout BudgetsRecommended startSets bounded timeout and deadline policies across callers, APIs, databases, and external services without hiding unknown outcomes.Concept questionMedium~7 min.NETASP.NET CorePractice 2Safe RetriesClassifies retryable outcomes and applies bounded attempts, exponential backoff, jitter, deadlines, and idempotency.Concept questionMedium~7 min.NETASP.NET CorePractice 3Circuit BreakersExplains closed, open, and half-open behavior, failure classification, recovery probes, and the limits of circuit breakers.Concept questionMedium~7 min.NETASP.NET CorePractice 4Bulkhead IsolationUses per-dependency concurrency limits, queues, pools, and workload partitions to stop one failing path from exhausting the whole API.Concept questionHard~9 min.NETASP.NET CorePractice 5Degraded ResponsesChooses safe cached, partial, pending, read-only, or unavailable behavior and makes degraded state explicit to clients and operators.Concept questionMedium~7 min.NETASP.NET CorePractice 6Health ChecksExplains health checks that prove an API can serve traffic without becoming fragile dependency probes.Comparison questionMedium~7 min.NETApplication InsightsASP.NET CorePractice 7DependenciesExplains dependency duration, error rate, timeout rate, query tagging, Redis latency, HTTP downstream calls, and endpoint correlation.Concept questionMedium~7 min.NETApplication InsightsASP.NET CorePractice 8Alerts and SLOsExplains alert design based on user-impact symptoms, SLOs, burn rate, thresholds, and avoiding noisy cause-only alerts.Concept questionMedium~7 min.NETApplication InsightsASP.NET CorePractice 9BackpressureExplains saturation signals and how systems shed, queue, throttle, or degrade before cascading failure.Concept questionHard~9 min.NETApplication InsightsASP.NET CorePractice 10Sync vs Async BoundariesSelects synchronous calls, asynchronous messaging, or a deliberate combination based on user feedback, coupling, latency, durability, and failure behavior.Comparison questionMedium~7 min.NETASP.NET CoreAzure Service BusPractice 11Webhook IngestionDesigns authenticated, replay-resistant webhook intake with durable acknowledgement, idempotent asynchronous processing, ordering policy, and reconciliation.System designHard~20 min.NETApplication InsightsASP.NET CorePractice 12Integration SyncDesigns synchronization with an external system using cursors, retries, idempotency, rate limits, and reconciliation.System designHard~20 min.NETApplication InsightsASP.NET CorePractice 13Dependency LatencyExplains how to diagnose and mitigate a downstream dependency slowing the API through timeouts, retries, and degraded behavior.Debugging scenarioMedium~10 min.NETApplication InsightsASP.NET CorePractice 14Mitigation ChoiceCompares rollback, roll-forward, feature kill switches, scaling, and degraded mode as incident mitigations.Comparison questionMedium~7 min.NETApplication InsightsASP.NET CorePractice 15Consistency Trade-offsMaps business invariants and stale-data tolerance to strong or eventual consistency, explicit failure behavior, reconciliation, and user-visible state.Architecture scenarioHard~12 min.NETASP.NET CoreSQL ServerPractice 16IHttpClientFactory lifetimeExplains how IHttpClientFactory separates short-lived clients from pooled handlers and how concurrency, DNS, resilience, and DI lifetimes still require judgment.Concept questionMedium~7 min.NETASP.NET CorePractice

Practice order

16 drillsOne at a time

1Timeout BudgetsUp next / Medium / ~7 min
2Safe RetriesMedium / ~7 min
3Circuit BreakersMedium / ~7 min
4Bulkhead IsolationHard / ~9 min
5Degraded ResponsesMedium / ~7 min
6Health ChecksMedium / ~7 min
7DependenciesMedium / ~7 min
8Alerts and SLOsMedium / ~7 min

+8 more drills in this section