You are using Elastic Beanstalk for your development team. You are responsible for deploying multiple versions of your application. How can you ensure, in an ideal way, that you don’t cross the application version limit in Elastic beanstalk?

Answer options:

A.Create a lambda function to delete the older versions.
B.Create a script to delete the older versions.
C.Use AWSConfig to delete the older versions
D.Use lifecyle policies in Elastic beanstalk

Answer - D
The AWS Documentation mentions
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 to delete application versions when the total number of versions for an application exceeds a specified number.
For more information on Elastic Beanstalk lifecycle policies please see the below link:
http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/applications-lifecycle.html