A fleet can look deployed while one machine quietly runs yesterday’s code. Deployment validation checks each target for the intended build and catches mismatches before the rollout proceeds. section 13.9.3
Seven updated, one forgotten
In Knight Capital’s eight-server deployment, seven servers received the new files and one remained on the old binary. A check for the matching build across all targets could have caught the mismatch before production opened. section 13.9.1 section 13.9.3
Figure 13.13 The Knight Capital Failure: Because no automated deployment verification checked that all eight servers were synchronized, one mismatched node acted like an automated firehose for unauthorized trades.

See how one out-of-sync server can undermine an otherwise completed deployment. section 13.9.1
