Which application migration strategy meets this requirement?
Re-host
Re-platform
Re-factor/re-architect
Retire
Explanations:
Re-hosting would involve moving the existing custom tooling and infrastructure to the cloud with minimal changes, but it does not optimize workloads or improve efficiency during the migration.
Re-platforming involves making some optimizations or changes to the platform (e.g., using cloud-native services for better performance or efficiency), which aligns with the requirement to optimize workloads while migrating without rewriting the custom tooling.
Re-factoring or re-architecting would involve a significant overhaul of the existing tooling and infrastructure, which is out of scope for the project since the company does not want to completely rewrite the tooling.
Retiring would imply abandoning the existing labs or workloads entirely, which is not aligned with the goal of migrating and optimizing them.
I rank that the answer is:
Re-platform