# Validate your deployment Validation proves the deployment works and holds up under load. Harden the deployment first, then measure it, so that the numbers reflect the configuration you will actually run. ## Harden first [#harden-first] * Confirm the deployment reports healthy in [Health check](/beta-docs/admin/monitoring/health-check/). * Turn on the telemetry you need to interpret a load test, including [metrics](/beta-docs/admin/monitoring/metrics/) and [logs](/beta-docs/admin/monitoring/logs/). * Apply the controls a security reviewer expects, such as [audit logs](/beta-docs/admin/security/audit-logs/) and [database encryption](/beta-docs/admin/security/database-encryption/). ## Then measure [#then-measure] * Run a load test that reflects your expected usage with [Scale testing](/beta-docs/install/validate/scale-testing/). * Compare the results against the size target you chose in [Plan your deployment](/beta-docs/install/plan/). A result that misses the target is a planning question, not a testing failure. ## Before you move on [#before-you-move-on] You should have a template developers can build a workspace from, a successful workspace build by someone other than the person who installed Coder, and a load test result you're willing to show the team that owns the infrastructure. Next: [Operate and maintain](/beta-docs/install/operate/).