Back to AWS Elastic Beanstalk

AWS Elastic Beanstalk Configuration

5 minutes 5 Questions

AWS Elastic Beanstalk Configuration provides options and settings to customize the infrastructure, software stack, and environment of your Beanstalk application. You can define settings like instance type, Amazon RDS integration, environment variables, and many other aspects of your application. Yo…

Test mode:
Start practice test
AWS Certified Solutions Architect - AWS Elastic Beanstalk Configuration Example Questions

Test your knowledge of AWS Elastic Beanstalk Configuration

Question 1

You have set up an AWS Elastic Beanstalk application consisting of a three-tier architecture, and you'd like to enable SSL certificates for customer-facing communication. Which approach should you take?

Correct Answer: Attach an SSL certificate to an Elastic Load Balancer.

Securing customer-facing communication can be achieved by attaching an SSL certificate to an Elastic Load Balancer. The Elastic Load Balancer will decrypt SSL traffic from clients and forward it to the backend instances, ensuring secure data transmission for customer-facing communication.

Question 2

An Elastic Beanstalk application stores user-uploaded images in an Amazon S3 bucket. Images are often accessed during the first 30 days after upload but only rarely thereafter. They must remain immediately accessible when needed, and the business accepts the risk of losing them if a single Availability Zone fails after the first 30 days. Images can be permanently deleted 180 days after upload. Without changing application code, which strategy best minimizes storage costs?

Correct Answer: Use S3 lifecycle policies to transition objects to S3 One Zone-Infrequent Access and then delete them after a set period.

S3 lifecycle policies automate moving objects to lower-cost storage classes and expiring them when they are no longer needed. S3 One Zone-Infrequent Access provides the same low-latency access as Standard at a lower cost by storing data in a single Availability Zone, making it a good fit for non-critical data that is rarely accessed but must remain immediately retrievable. After the defined retention period, expiring (deleting) the objects eliminates ongoing storage costs. The other options do not address S3 storage cost: increasing RDS storage is unrelated, compressing/archiving on EC2 is operationally fragile and not durable or scalable, and moving to EBS is typically more expensive than S3 and ties data to instances and AZs.

Question 3

You are deploying a .NET application to AWS Elastic Beanstalk that depends on third-party OS-level libraries not included with the runtime. What is the recommended way to ensure these libraries are installed on every instance during deployments?

Correct Answer: Add an .ebextensions/*.config file to install the required libraries during deployment (for example, using packages/commands or scripts).

The recommended way to install third-party libraries on Elastic Beanstalk instances is to include an .ebextensions/*.config file in your application source bundle that installs packages and runs scripts during deployment. On Amazon Linux 2 or newer Windows Server platforms, you can also use platform hooks (.platform/hooks) to run installation scripts at the appropriate lifecycle stage. Using a custom AMI is not supported for managed platforms and is unnecessarily heavy, the aws:elasticbeanstalk:application:environment namespace only sets environment variables (it does not execute hooks), and CloudFormation custom resources do not run on the EC2 instances to install OS-level dependencies during deployment.

More AWS Elastic Beanstalk Configuration questions
18 questions (total)
Start 18 question test