Following the deployment of a new release, your team encounters severe issues that adversely affect the customer experience. The deployment strategy employed separates the old and new environments, allowing for independent operation and immediate traffic switching between the two. To mitigate these issues swiftly, what is the BEST course of action to revert to the previous, stable release?
Utilize function versioning and aliasing to revert the service to the prior stable codebase.
Switch production traffic to the environment running the last stable release using the console of the deployment service.
Create a fresh environment using the last stable release configuration and direct traffic there.
Redeploy the prior release as a new operation within the deployment service.