A CSA needs to apply new OS security patches to the application cluster server farm in a public cloud provider. The CSA wants to ensure the security patch and configuration are consistent for all memb

Updating runbook procedures is a good process step but does not directly ensure the technical consistency of the server farm members during the actual patching and configuration.

Leveraging infrastructure as code (IaC) to replace each server farm member aligns with the "immutable infrastructure" approach. This ensures consistency by provisioning new servers with the desired patched OS and configuration from an IaC definition, then swapping them in, rather than modifying existing servers and minimizing configuration drift.

Configuring and patching each server individually is highly prone to human error and configuration drift, making it difficult to ensure consistency across all members of a server farm.

Snapshotting servers before patching provides a rollback point, which is a good practice for disaster recovery, but it does not ensure that the patching process itself results in consistent configurations across all servers.