Q56 — AWS DVA-C02 Ch.3

Question 56 of 100 | ← Chapter 3

A development team uses AWS Elastic Beanstalk for application deployments. The team configured an application version lifecycle policy to limit the number of application versions to 25. However, even with this lifecycle policy enabled, source bundles are still being deleted from the Amazon S3 source bucket. What should the development team do in the Elastic Beanstalk application version lifecycle settings to retain source bundles in the S3 bucket?

• A. Enable versioning on the source bundle S3 bucket.
• B. Disable the S3 bucket lifecycle policy to prevent source bundle archival.
• 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 source bundles in Amazon S3. ✓

Correct Answer: D. Update the Elastic Beanstalk application version lifecycle policy to retain source bundles in Amazon S3.

Explanation

Elastic Beanstalk’s application version lifecycle policy controls retention of application versions *within Elastic Beanstalk*, but by default may delete associated source bundles from S3 unless explicitly configured otherwise. Option D directly addresses the requirement by enabling the 'Retain source bundles in Amazon S3' setting in the lifecycle configuration—this prevents deletion of source bundles from S3 regardless of version count limits. Option A (S3 versioning) protects against accidental deletion but does not stop Elastic Beanstalk from deleting the objects. Option B confuses S3 bucket lifecycle rules (unrelated to Elastic Beanstalk behavior). Option C increases version count but does not affect source bundle retention. Therefore, Option D is correct.