AWS Elastic Beanstalk - top questions - Certified Developer exam

Hello Cloud Learners,
In the process of preparing for the exam, I find examples of questions on the Internet. I will post them here and on my site all topics at once, along with explanations.
I hope this will be helpful to those who want to quickly go over the questions on each topic, as I plan to do.

You are building a web application that will run in an AWS ElasticBeanstalk environment. You need to add and configure an Amazon ElastiCache cluster into the environment immediately after the application is deployed.
What is the most efficient method to ensure that the cluster is deployed immediately after the EB application is deployed?

1. Use the AWS Management Console to create and configure the cluster.
2. Create a cron job to schedule the cluster deployment using the aws cloudformation deploy command
3. Create a configuration file with the .config extension and place it into the .ebextensions folder in the application package.
4. Build an AWS Lambda function that polls to the ElasticBeanstalk environment deployments and create and configure the Amazon ElastiCache cluster.

Emily is building a web application using AWS ElasticBeanstalk. The application uses static images like icons, buttons and logos. Emily is looking for a way to serve these static images in a performant way that will not disrupt user sessions.
Which of the following options would meet this requirement?

1. Use an Amazon Elastic File System (EFS) volume to serve the static image files.
2. Configure the AWS ElasticBeanstalk proxy server to serve the static image files.
3. Use an Amazon S3 bucket to serve the static image files.
4. Use an Amazon Elastic Block Store (EBS) volume to serve the static image files.

When working with a published version of the AWS Lambda function, you should note that the _____.

1. Use the AWS Management Console to create and configure the cluster.
2. Create a cron job to schedule the cluster deployment using the aws cloudformation deploy command
3. Create a configuration file with the .config extension and place it into the .ebextensions folder in the application package.
4. Build an AWS Lambda function that polls to the ElasticBeanstalk environment deployments and create and configure the Amazon ElastiCache cluster.

An online shopping platform has been deployed to AWS using Elastic Beanstalk. They simply uploaded their Node.js application, and Elastic Beanstalk automatically handles the details of capacity provisioning, load balancing, scaling, and application health monitoring. Since the entire deployment process is automated, the DevOps team is not sure where to get the application log files of their shopping platform.
In Elastic Beanstalk, where does it store the application files and server log files?

1. Application files are stored in S3. The server log files can only be stored in the attached EBS volumes of the EC2 instances, which were launched by AWS Elastic Beanstalk.
2. Application files are stored in S3. The server log files can be stored directly in Glacier or in CloudWatch Logs.
3. Application files are stored in S3. The server log files can be optionally stored in CloudTrail or in CloudWatch Logs.
4. Application files are stored in S3. The server log files can also optionally be stored in S3 or in CloudWatch Logs.

A former colleague reached out to you for consultation. He uploads a Django project in Elastic Beanstalk through CLI using instructions he read in a blog post, but for some reason he could not create the environment he needs for his project. He encounters an error message saying “The instance profile aws-elasticbeanstalk-ec2-role associated with the environment does not exist.”
What are the possible causes of this issue? (Select TWO.)

1. He selected the wrong platform for the Django code.
2. Elastic Beanstalk CLI did not create one because your IAM role has no permission to create roles.
3. Instance profile container for the role needs to be manually replaced every time a new environment is launched.
4. You have not associated an Elastic Beanstalk role to your CLI.
5. IAM role already exists but has insufficient permissions that Elastic Beanstalk needs.

• Notes about Elastic Beanstalk can be found here and here
• Full set with questions on all topics and explanation can be found here