Loading
Pick a focused question that fits your time, stack, and interview goal.
439 results across 1 active filter
Page 13 of 19
Builds a story about helping a teammate grow while still moving the work forward.
Compares merge and rebase in team workflows, including history clarity, conflict handling, and shared branch safety.
Compare middleware and filters by scope, timing, endpoint context, and practical use cases.
Explains how to deploy database changes safely with .NET APIs using backward-compatible steps.
Builds a story about handling a missed estimate transparently and recovering with a realistic plan.
Compare request binding and validation responsibilities in ASP.NET Core APIs.
Chooses between a modular monolith and microservices using domain boundaries, team ownership, scaling, deployment, data consistency, and operational cost.
Explains how to monitor external and internal dependencies after a .NET service release.
Predicts how the built-in container resolves repeated service registrations and chooses explicit selection without service-location logic.
Separates OAuth authorization from OpenID Connect authentication and explains why modern interactive clients use authorization code with PKCE.
Uses stable extension points for genuinely variable behavior while avoiding speculative abstractions and configuration-driven branching.
Compares OpenTelemetry-based Azure Monitor instrumentation with older Application Insights SDK patterns for .NET services.
Explains versioning and releasing shared .NET libraries or NuGet packages safely.
Compare Parallel.ForEachAsync and Task.WhenAll for processing collections with async work and controlled concurrency.
Places invariants and state transitions near the data they protect while keeping orchestration and infrastructure out of domain entities.
Explains how to verify a .NET release after deployment using smoke tests, metrics, logs, and business signals.
Explains what happens when a hot key expires and how request coalescing, TTL jitter, background refresh, and stale serving help.
Explains frontend guards, backend idempotency, pending state, retries, and duplicate-safe mutation design.
Explains insecure direct object reference risks and how APIs enforce ownership, tenant scope, and authorization per resource.
Explains why request DTOs should expose only allowed fields and how server-owned fields stay protected.
Updates only public mutable fields and leaves ownership, status, and audit values server-controlled.
Secures webhooks, previews, imports, and remote-file fetches with destination policy, DNS and redirect defenses, egress controls, limits, and observability.
Uses RFC 9457 Problem Details as a stable, safe error contract with documented problem types, actionable extensions, and centralized ASP.NET mapping.
Explains EF Core projections for API read models that need related names, counts, and summaries without loading full graphs.