Loading
Pick a focused question that fits your time, stack, and interview goal.
84 results across 1 active filter
Page 3 of 4
Explains health checks that prove an API can serve traffic without becoming fragile dependency probes.
Designs user reports, moderation queues, actions, audit history, abuse controls, and appeal-friendly decisions.
Designs user preferences, channel rules, unsubscribe behavior, digest generation, and delivery suppression.
Designs layered public API protection with caller identity, quotas, burst limits, abuse signals, and client-friendly responses.
Designs authorization that combines roles, permissions, tenant context, resource ownership, and auditability.
Designs live updates with polling, server-sent events, or WebSockets while preserving authorization, ordering, scale, and fallback behavior.
Designs scheduled jobs with locking, idempotency, observability, retries, and safe operations across multiple instances.
Designs saved filters, scheduled matching, alert delivery, and freshness trade-offs for search-driven product workflows.
Designs search and filtering with controlled query contracts, indexing, pagination, ranking, and operational limits.
Designs plan entitlements, provider webhooks, idempotent billing updates, access checks, grace periods, and support overrides.
Designs a controlled support impersonation workflow with scoped access, approvals, visible banners, audit trails, and session boundaries.
Designs membership, role changes, removal, ownership transfer, and permission updates without weakening tenant boundaries.
Designs an invitation workflow with token security, expiry, membership creation, email delivery, and replay-safe onboarding.
Designs a settings service with defaults, validation, scoped preferences, caching, and safe rollout of new settings.
Explains a telemetry-driven path from slow endpoint symptoms to database, cache, dependency, CPU, or payload root cause.
Decide whether Azure SQL errors are transient platform faults or a real application/query regression.
Explains initial incident triage: confirm impact, mitigate, assign roles, preserve evidence, and communicate.
Explains health endpoints, readiness versus liveness, warm-up, dependency checks, and safe App Service health behavior.
Covers deployment logs, startup failures, runtime stack, app settings, missing files, Key Vault references, and post-deployment diagnosis.
Explains correlation IDs, distributed tracing, dependency telemetry, message boundaries, and logs across App Service, queues, and downstream APIs.
Investigates a growing-data EF Core slowdown through one correlated request, generated SQL, representative parameters, execution plan, waits, query shape, measured repair, and guarded rollout.
Explains how to triage post-release 500 errors using deployment correlation, logs, traces, feature flags, and rollback safety.
Explains how to diagnose 401/403 spikes across token validation, identity provider issues, clock skew, deployment changes, and abuse.
Compares OpenTelemetry-based Azure Monitor instrumentation with older Application Insights SDK patterns for .NET services.