Question 178:
You are an AWS DevOps engineer in a company, and you created a job in Jenkins to use a script to build an Elastic Beanstalk environment. An eb config command has been used to configure a Security Group for an Elastic Load Balancer. After some time, another colleague found that the Security Group should be changed to another one. He modified this configuration option with a config file in the .ebextensions folder. However, when the Jenkins job was rebuilt, the Security Group did not change to the new one. What is the reason and how would you fix this issue?
Answer options:
A.Security Group name cannot be changed in the .ebextensions config file. The eb config in the script needs to be modified to use the correct Security Group. B.The .ebextensions config file was processed first. And eb config ran next and overrode the .ebextensions config file. Modify the script in Jenkins so that the .ebextensions config file is processed after eb config. C.When there is a conflict for the configurations in .ebextensions and eb config, the default value of the option is used. The Security Group settings in eb config should be removed to avoid a conflict. D.The settings in the .ebextensions folder cannot override that in the EB CLI command. Remove the configuration settings for Security Group in eb config command.