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.
95 results across 1 active filter
Page 4 of 4
Implements safe redaction of known sensitive keys in a dictionary before logging.
Persists a job and outbox command before returning a status URL for long-running work.
Produces field-keyed validation errors through one reusable endpoint boundary.
Explains safe error responses for auth failures, validation failures, server errors, and sensitive resource access.
Wraps a pooled DbContext factory so every request assigns tenant state before a global query filter can run.
Protects source, dependencies, workflows, build identities, runners, artifacts, and deployment verification while preserving traceability and patch response.
Separates identity issuance, untrusted client behavior, API authorization, tenant isolation, resource checks, and token-handling responsibilities.
Explains identity versus permission checks in API request handling and why both boundaries need server-side enforcement.
Explains session state choices for scaled-out ASP.NET Core APIs and when Redis-backed state is appropriate.
Authorizes metadata before opening storage and streams the file with safe headers and range support.
Expresses allowed and denied capability combinations as one parameterized API integration test.
Proves that one authenticated user cannot read or modify another user's private resource.
Explains the boundary between OAuth/OIDC identity, application users, claims mapping, roles, and app-specific permissions.
Explains when a Next.js route layer helps with cookies, tokens, aggregation, and UI-specific API adaptation.
Explains policy-based authorization, requirements, handlers, claims, capabilities, and resource-aware checks.
Explains route handlers as a frontend server boundary for cookies, API adaptation, auth, and backend calls.
Explains Redis-backed rate-limit counters, atomic increments, windows, identity keys, and fallback behavior.
Explains HTTPS, HSTS, secure cookies, HttpOnly, SameSite, no-store, and practical API/browser security hardening.
Explains structured logging fields, safe context, redaction, event naming, and avoiding secret or personal-data leaks.
Explains JWT validation, trusted issuers, audiences, expiration, signing keys, claims, and server-side authorization boundaries.
Covers configuration that must stay with a slot, such as connection strings, secrets, callback URLs, and staging-only settings.
Covers custom domains, TLS, HTTPS, allowed hosts, CORS boundaries, and production-facing endpoint hygiene for App Service APIs.
Explains why memory diagnostics need access control, retention limits, and careful handling of secrets and user data.