Answer-first summary for fast verification
Answer: Define a dev environment with a single instance and a 'load test' environment that has settings close to production environment
Define a dev environment with a single instance and a 'load test' environment that has settings close to production environment AWS Elastic Beanstalk makes it easy to create new environments for your application. You can create and manage separate environments for development, testing, and production use, and you can deploy any version of your application to any environment. Environments can be long-running or temporary. When you terminate an environment, you can save its configuration to recreate it later. It is common practice to have many environments for the same application. You can deploy multiple environments when you need to run multiple versions of an application. So for the given use-case, you can set up 'dev' and 'load test' environment.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
A .NET developer team is currently managing several ASP.NET web applications hosted on EC2 instances with IIS as the web server. The team needs to configure the deployment process to allow multiple versions of these applications to run in AWS Elastic Beanstalk. Specifically, they require one version for development and testing, and another version for load testing.
What would be the recommended method to achieve this requirement?
A
Define a dev environment with a single instance and a 'load test' environment that has settings close to production environment
B
You cannot have multiple development environments in Elastic Beanstalk, just one development and one production environment
C
Create an Application Load Balancer to route based on hostname so you can pass on parameters to the development Elastic Beanstalk environment. Create a file in .ebextensions/ to know how to handle the traffic coming from the ALB
D
Use only one Beanstalk environment and perform configuration changes using an Ansible script
No comments yet.