ASP.NET Core Interview Question #249
How would you review an ASP.NET Core application before a production release?
Senior ASP.NET Core Real-World Scenarios Senior Advanced
Quick Interview Answer
Verify that Release builds and automated tests pass, configuration is valid, migrations are reviewed, secrets are externalized, and production error handling does not expose internals. Review authentication, authorization, anti-forgery requirements, CORS, upload/request limits, forwarded headers, HTTPS, and security-sensitive cookies.
Detailed Explanation
Verify that Release builds and automated tests pass, configuration is valid, migrations are reviewed, secrets are externalized, and production error handling does not expose internals. Review authentication, authorization, anti-forgery requirements, CORS, upload/request limits, forwarded headers, HTTPS, and security-sensitive cookies.
Confirm logging, metrics, tracing, health checks, backups, rollback procedures, and dependency monitoring. Load-test critical paths when capacity matters and verify that database indexes and expensive queries are understood.
A production-readiness review should include application code, database, hosting, networking, security, observability, and operational recovery—not just whether the application compiles.
Code Example
# Typical release checks
dotnet restore
dotnet build -c Release --no-restore
dotnet test -c Release --no-build
dotnet publish -c Release --no-build -o publish
# Then validate deployment configuration,
# migrations, health, security, and rollback.