Maximum Number of Auto Scaling Group Instances for AWS Elastic Beanstalk with Node.js Application

Correct Answer -B.

There are several methods to modify the configuration settings in Elastic Beanstalk.

Please refer to.

https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/command-options.html#configuration-options-recommendedvalues

for the priorities of various configuration options.

Option A is incorrect: Because the configuration settings in the AWS console belong to the ones applied directly to the environment.

This is the highest priority, and the environment can be created successfully.

Option B is CORRECT: The priorities are “configurations in AWS console” > “configurations in .ebextensions” > “default value”

Therefore, the maximum value of ASG will be 10.

Options C and D are incorrect: Refer to the explanations in Option.

B.

The maximum number of instances in an Elastic Beanstalk environment can be set in two ways:

1. Using the AWS console during environment creation.
2. Using configuration files in the .ebextensions folder in the source bundle.

In this scenario, the DevOps engineer modified the maximum number of instances to 10 in the AWS console during environment creation. However, there is a configuration file in the .ebextensions folder that sets the maximum number of instances to 5.

When Elastic Beanstalk creates an environment, it first applies the settings defined in the console, then it applies the settings defined in configuration files.

So, in this case, the maximum number of instances would be 5, as defined in the .ebextensions configuration file. This is because the .ebextensions configuration file settings override the settings defined in the AWS console.

Therefore, the correct answer is C: The maximum number is 5.