Loading
Pick a focused question that fits your time, stack, and interview goal.
613 results across 1 active filter
Page 21 of 26
Reviews a proposed response-field rename by finding consumers, classifying the break, choosing a migration path, and proving rollout and removal are safe.
Reviews and stages destructive EF Core schema changes around live data, locks, mixed application versions, recovery, and rollback.
Compares rollback and roll-forward decisions after a failed production deployment.
Coordinates old and new application versions, expand-and-contract schema changes, migration ownership, readiness, and rollback during rolling releases.
Places identity, optional selection controls, command representations, headers, and files in predictable HTTP locations while accounting for security, caching, limits, and model binding.
Reduces container privileges through non-root execution, minimal images, controlled filesystems, and explicit capability requirements.
Explains how callers use one contract while runtime dispatch selects implementation, then connects that mechanism to extensible behavior.
Explains HTTP safety and idempotency, then connects those guarantees to retries, side effects, and API design.
Persists domain state and its outbox message in one SaveChanges transaction without publishing inside the request transaction.
Explains how multiple worker instances share queue work and what limits safe scaling.
Wraps a pooled DbContext factory so every request assigns tenant state before a global query filter can run.
Explains safe handling of secrets and environment-specific configuration in CI/CD pipelines.
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.
Uses separate models where they protect contracts, invariants, or storage evolution while avoiding repetitive mapping with no boundary value.
Explains identity versus permission checks in API request handling and why both boundaries need server-side enforcement.
Explains cached value serialization, schema versioning, deploy compatibility, and safe handling of old payloads.
Explains Next.js server/client component boundaries, interactivity, data access, serialization, and bundle impact.
Sets bounded timeout and deadline policies across callers, APIs, databases, and external services without hiding unknown outcomes.
Builds dependency-specific timeout budgets that contain slow SQL, HTTP, and cache calls without creating unsafe retries or ambiguous writes.
Explains EF Core shadow properties for audit or infrastructure columns with practical .NET data-access examples and production trade-offs.
Explains the output shape of core LINQ transformations and uses them without hiding empty groups, duplicate keys, or excessive buffering.
Applies single responsibility to reasons for change, cohesive behavior, and maintainable service boundaries instead of counting methods.
Builds fast, safe deployment smoke checks that verify readiness and one critical business path, then combine their result with live telemetry to promote, pause, or roll back.