AWS Certified Developer – Associate — Question 377

A development team uses AWS Elastic Beanstalk for application deployment. The development team has configured the application version lifecycle policy to limit the number of application versions to 25. However, even with the application version lifecycle policy, the source bundle is deleted from the Amazon S3 source bucket.
What should the development team do in the Elastic Beanstalk application version lifecycle settings to retain the source code in the S3 bucket?

Answer options

• A. Enable versioning on the source bundle S3 bucket.
• B. Disable the S3 bucket lifecycle policy to avoid the archiving of the source bundle.
• C. Update the Elastic Beanstalk application version lifecycle policy to increase the version quota to 50.
• D. Update the Elastic Beanstalk application version lifecycle policy to retain the source bundle in Amazon S3.

Correct answer: D

Explanation

When configuring an AWS Elastic Beanstalk application version lifecycle policy, you can choose to retain the source bundle in Amazon S3 even when the application version is deleted. Selecting this option ensures the source code remains intact in the S3 bucket while still enforcing the lifecycle limit on the Elastic Beanstalk console. Modifying S3 bucket settings or raising the version limit to 50 will not prevent the eventual deletion of source bundles when the limit is reached.