An application has a short peak with proven CPU saturation and spare supported infrastructure capacity. Which action is worth testing?

1. Add unrelated network routes without changing the measured bottleneck.
2. Remove all backups to reduce application SQL parsing.
3. Assume scaling necessarily repairs inefficient SQL and locking issues too.
4. A supported online CPU allocation increase with before-and-after workload measurements.