Loading
Pick a focused question that fits your time, stack, and interview goal.
690 results
Page 9 of 29
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.
Designs a file workflow with metadata, durable storage, validation, access control, scanning, and safe downloads.
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.
Designs a safe admin import flow with upload staging, validation, preview, confirmation, idempotency, and rollback strategy.
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 comments with permissions, threading, mentions, notifications, editing history, and moderation concerns.
Designs draft, review, publish, rollback, and audit behavior for content managed by editors and admins.
Designs a sharding strategy with a stable key, balanced load, routing, resharding, cross-shard limits, and operational ownership.
Designs deletion, retention, soft delete, hard delete, backups, audit records, and asynchronous cleanup across related data.
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 how client-side validation, server-side validation, DTOs, domain rules, and user feedback work together.
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.
Explains practical UI states for data fetching, empty results, partial failure, retry, and accessible recovery.
Explains list/detail API boundaries, route state, prefetching, selected item behavior, and avoiding over-fetching.
Designs user reports, moderation queues, actions, audit history, abuse controls, and appeal-friendly decisions.