Your company has asked you to maintain an application using Elastic Beanstalk. At times, you normally hit the application version limit when deploying new versions of the application. Which of the following is the most effective way to manage this issue?

Answer options:

A.Create multiple environments and deploy the different versions to different environments.
B.Create an Application Version Lifecycle policy.
C.Create multiple applications and deploy the different versions to different applications.
D.Delete the application versions manually.

Answer – B
The AWS Documentation mentions the following.
Each time you upload a new version of your application with the Elastic Beanstalk console or the EB CLI, Elastic Beanstalk creates an application version. If you don`t delete versions that you no longer use, you will eventually reach the application version limit and be unable to create new versions of that application.
You can avoid hitting the limit by applying an application version lifecycle policy to your applications. A lifecycle policy tells Elastic Beanstalk to delete application versions that are old or delete application versions when the total number of versions for an application exceeds a specified number.
Options A and C are invalid because they are not the right approaches when managing the deployment of application versions.
Option D, even though possible, is not the most effective way.
For more information on the application lifecycle, please refer to the below URL-
https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/applications-lifecycle.html