Before migrating production servers to the public cloud, a cloud engineer created and validated the performance baseline on the test environment. Due to on-premises resource constraints, the test…

Performing a stress test on the test environment is not helpful because the problem is occurring in the production environment, and the test environment is explicitly stated to not be an exact replication of production.

Increasing compute resources is a potential solution, but it is premature to do so without first identifying the root cause of the latency, as it might be a configuration or patch issue rather than a resource ceiling.

Security patches often include performance improvements, bug fixes, or address vulnerabilities that could introduce unexpected overhead or resource contention if missing. Ensuring all necessary patches are deployed on the new production cloud servers is a foundational step in troubleshooting unexpected performance issues after a migration, as unpatched systems can be a source of instability or inefficiency.

Identifying transit and/or receive discards at the edge router focuses on network layer issues, which might be a cause, but validating security patches is a more general and critical system-level check that should precede network-specific troubleshooting after a migration.