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.
473 results across 1 active filter
Page 6 of 20
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.
Designs tenant isolation across API, data, cache, background jobs, search, and admin access.
Designs an activity feed with event capture, fan-out strategy, pagination, privacy, and read performance.
Introduces API versions only for unavoidable breaks, with explicit routing, versioned documentation, migration support, telemetry, deprecation, and removal criteria.
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.
Designs email, in-app, and push-style notification delivery with preferences, retries, and idempotent side effects.
Designs realistic load, stress, spike, and soak tests from workload assumptions and SLOs while correlating client results with server bottlenecks.
Designs synchronization with an external system using cursors, retries, idempotency, rate limits, and reconciliation.
Explains reset-token generation, hashing, expiration, generic responses, session revocation, and abuse controls.
Explains soft delete in EF Core APIs with practical .NET data-access examples and production trade-offs.
Designs a multi-service business workflow using local transactions, durable progress, idempotency, retries, and domain-specific compensation.
Explains password verification, hashing, throttling, generic errors, lockout, and safe login telemetry.
Explains dashboard panels that help an API owner see user impact, dependency health, releases, and current incidents.
Places contract, use-case, domain, authorization, and database validation at the boundaries that can enforce each rule consistently.
Designs authenticated, replay-resistant webhook intake with durable acknowledgement, idempotent asynchronous processing, ordering policy, and reconciliation.
Chooses response cache directives for public, private, sensitive, and revalidated API data without leaking user-specific content.
Explains cache-key scope for tenant, user, role, locale, filters, response version, and security-sensitive reads.
Designs a sharding strategy with a stable key, balanced load, routing, resharding, cross-shard limits, and operational ownership.
Explains why message handlers must tolerate duplicate delivery and how idempotency protects side effects.
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.
Chooses safe cached, partial, pending, read-only, or unavailable behavior and makes degraded state explicit to clients and operators.