Exam AWS-SysOps topic 1 question 324 discussion

Enabling log file rotation to S3 allows Elastic Beanstalk to automatically rotate the log files and store them in an S3 bucket. This ensures that developers have access to the log files without granting them direct access to the Elastic Beanstalk infrastructure. They can then access the log files from the designated S3 bucket for debugging purposes.

Correct Answer: B It cannot be "D" anyway. How could one connect to every instance launched by Elastic Beanstalk in an auto scaling infrastructure? It doesn't make sense at all.

B is correct, beanstalk support log rotation for .net, here is the link https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/create_deploy_NET.container.console.html

https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/using-features.logging.html

saumenP is correct. Bundle logs are full logs for a wider range of log files, including logs from yum and cron and several logs from AWS CloudFormation. When you request bundle logs, an instance in your environment packages the full log files into a ZIP archive and uploads it to Amazon S3. Note Elastic Beanstalk Windows Server platforms do not support bundle logs.

B. Enable log file rotation to S3 within the Elastic Beanstalk configuration

Another moment: The infrastructure will scale up and down So every time a new instance added to login to it and rotate manually. Logically it's B

B should be the correct answer.

D should be correct. Elastic Beanstalk Windows Server platforms do not support bundle logs. On Windows Server, when you configure your application's log files for log rotation, the application must rotate the log files periodically