Answer-first summary for fast verification
Answer: Use a Lifecycle Policy
Overall explanation Correct option: Use a Lifecycle Policy 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 old application versions or to delete application versions when the total number of versions for an application exceeds a specified number. Elastic Beanstalk applies an application's lifecycle policy each time you create a new application version and deletes up to 100 versions each time the lifecycle policy is applied. Elastic Beanstalk deletes old versions after creating the new version and does not count the new version towards the maximum number of versions defined in the policy.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
Your organization has implemented a complete Continuous Integration/Continuous Deployment (CI/CD) pipeline using AWS CodePipeline, with deployments managed on AWS Elastic Beanstalk. This system has been functioning well for over a year. However, you are now nearing the maximum capacity for the number of application versions that Elastic Beanstalk can store.
What steps can you take to delete older, unused application versions in Elastic Beanstalk to make room for new versions?
A
Define a Lambda function
B
Use Worker Environments
C
Setup an .ebextensions file
D
Use a Lifecycle Policy
No comments yet.