After a cloud infrastructure migration, a large enterprise updated the server naming conventions to comply with the new IT governance policies. Soon after, administrators reported that the automated scaling feature for handling high-load events was no longer functioning correctly, leading to performance degradation during peak usage. Prior to the migration, the automated scaling was based on server metrics and predefined resource tags. What is the MOST likely reason the automated scaling feature is not operational?
There is an intermittent connectivity issue between the cloud infrastructure and the scaling service.
Resource tags defining which servers to scale were not updated to match the new server naming conventions.
Administrators accidentally disabled the automated scaling feature post-migration.
The scaling service software version is incompatible with the new servers' operating system.