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

Drills

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.

Search

Track

Practice style

Level

More filters1

Topic

Technology

Tech stack

Skill area

24 results across 1 active filter

Page 1 of 1

Comparison questionEasy~7 min

AppHost vs ServiceDefaults responsibilities in .NET Aspire

Separates application composition in AppHost from reusable in-process defaults for telemetry, health, resilience, and service discovery.

.NET.NET AspireASP.NET CoreOpenTelemetry

Concept questionMedium

~7 min

Capture dependency telemetry for SQL, Redis, and HTTP calls

Explains dependency duration, error rate, timeout rate, query tagging, Redis latency, HTTP downstream calls, and endpoint correlation.

.NETApplication InsightsASP.NET CoreEF CoreOpenTelemetry+3

Practice drill

Comparison questionMedium~7 min

Choose rollback, roll-forward, or kill switch during incidents

Compares rollback, roll-forward, feature kill switches, scaling, and degraded mode as incident mitigations.

.NETApplication InsightsASP.NET CoreAzureAzure App Service+1

Comparison questionMedium~7 min

Compare OpenTelemetry and Application Insights instrumentation

Compares vendor-neutral OpenTelemetry concepts with Application Insights usage for .NET production services.

.NETApplication InsightsASP.NET CoreAzureOpenTelemetry

Concept questionHard~9 min

Control trace sampling, metric cardinality, and observability cost

Explains sampling, high-cardinality labels, retention, cost, and keeping enough signal for incident diagnosis.

.NETApplication InsightsASP.NET CoreOpenTelemetry

Concept questionMedium~7 min

Correlate incidents with releases and feature flags

Explains deployment markers, version telemetry, feature-flag state, commit traceability, and incident diagnosis after releases.

.NETApplication InsightsASP.NET CoreAzureOpenTelemetry

Concept questionEasy~5 min

Create runbooks and on-call handoffs that work

Explains what belongs in runbooks, how on-call handoff preserves context, and how operational docs stay useful.

.NETApplication InsightsASP.NET CoreOpenTelemetry

Debugging scenarioHard~10 min

Debug a distributed request with the Aspire dashboard

Uses resource state, structured logs, traces, metrics, health, and configuration evidence to isolate a cross-service failure.

.NET.NET AspireOpenTelemetry

Debugging scenarioMedium~10 min

Debug missing logs during an incident

Explains how to troubleshoot absent logs or telemetry by checking configuration, sampling, sinks, levels, deployment, and correlation.

.NETApplication InsightsASP.NET CoreAzureAzure App Service+1

Concept questionMedium~7 min

Design alerts around symptoms and SLOs

Explains alert design based on user-impact symptoms, SLOs, burn rate, thresholds, and avoiding noisy cause-only alerts.

.NETApplication InsightsASP.NET CoreAzureOpenTelemetry

Concept questionEasy~5 min

Design a useful API owner dashboard

Explains dashboard panels that help an API owner see user impact, dependency health, releases, and current incidents.

.NETApplication InsightsASP.NET CoreOpenTelemetry

Comparison questionMedium~7 min

Design health checks for readiness, liveness, and startup

Explains health checks that prove an API can serve traffic without becoming fragile dependency probes.

.NETApplication InsightsASP.NET CoreAzureAzure App Service+1

Debugging scenarioMedium~10 min

Diagnose a slow API endpoint with telemetry

Explains a telemetry-driven path from slow endpoint symptoms to database, cache, dependency, CPU, or payload root cause.

.NETApplication InsightsASP.NET CoreEF CoreOpenTelemetry+3

Debugging scenarioMedium~10 min

Handle the first 15 minutes of a production incident

Explains initial incident triage: confirm impact, mitigate, assign roles, preserve evidence, and communicate.

.NETApplication InsightsASP.NET CoreAzureAzure App Service+1

Debugging scenarioMedium~10 min

Investigate a spike in 500 errors after release

Explains how to triage post-release 500 errors using deployment correlation, logs, traces, feature flags, and rollback safety.

.NETApplication InsightsASP.NET CoreAzureAzure App Service+1

Debugging scenarioMedium~10 min

Investigate a spike in authentication failures

Explains how to diagnose 401/403 spikes across token validation, identity provider issues, clock skew, deployment changes, and abuse.

.NETApplication InsightsASP.NET CoreJWTOpenID Connect+1

Concept questionEasy~5 min

Propagate correlation IDs across APIs and workers

Explains correlation IDs across request logs, dependency calls, queues, workers, and support investigations.

.NETApplication InsightsASP.NET CoreAzure Service BusOpenTelemetry

Debugging scenarioMedium~10 min

Triage downstream dependency latency

Explains how to diagnose and mitigate a downstream dependency slowing the API through timeouts, retries, and degraded behavior.

.NETApplication InsightsASP.NET CoreOpenTelemetry

Debugging scenarioMedium~10 min

Triage queue backlog and consumer lag

Explains how to investigate queue age, backlog, worker health, poison messages, dependency failures, and safe catch-up.

.NETApplication InsightsASP.NET CoreAzure Service BusOpenTelemetry

Concept questionMedium~7 min

Turn incidents into regression guards

Explains post-incident review, root cause, contributing factors, action items, tests, alerts, runbooks, and ownership.

.NETApplication InsightsASP.NET CoreOpenTelemetry

Concept questionHard~9 min

Use capacity, load shedding, and backpressure signals

Explains saturation signals and how systems shed, queue, throttle, or degrade before cascading failure.

.NETApplication InsightsASP.NET CoreAzure Service BusEF Core+4

Comparison questionEasy~5 min

Use logs, metrics, and traces for API diagnosis

Explains the different diagnostic roles of logs, metrics, and traces during backend production issues.

.NETApplication InsightsASP.NET CoreOpenTelemetry

Concept questionMedium~7 min

Use structured logs without leaking sensitive data

Explains structured logging fields, safe context, redaction, event naming, and avoiding secret or personal-data leaks.

.NETApplication InsightsASP.NET CoreOpenTelemetry

Coding problemMedium~25 min

Verify trace propagation across an HTTP dependency

Captures test activities to prove one incoming request and its outgoing HTTP dependency share trace context.

.NETASP.NET CoreC#OpenTelemetryxUnit