Exam AWS Certified Developer Associate topic 1 question 210 discussion

You can't change load balancer type while cloning environment

Understand that Beanstalk does not support changing of loader balancer type, that's why we clone an existing environment instead of editing it directly (like D).

Currently, Beanstalk does not support changing of Load Balancer type. If you want to change the Load Balancer type, you need to create a new environment with the desired Load Balancer type. I see you have made changes to the environment resources out-of-band which is not recommended as it might break the environment like the issue that you are encountering. Therefore, to fix this issue, the only option we have is to create a new environment. <<< This answer from AWS support team link Below https://repost.aws/questions/QUEemsrTM_TPG3r_HdoG08EQ/how-to-remove-or-change-a-load-balancer-type-with-elastic-beanstalk

Is there even correct answer? For me it looks like it doesn't. B is closes, but 2nd step looks incorrect, since we need to deploy to new version of the app, don't we?

If we clone we also clone the type of load balancer. If we want an Application Load Balancer, we have to create a new environmment with the same configurations, deploy the application that is current running on the classic load balancer then use swap-environment-cnames action to point the same url to the new ALB

c,The Elastic Beanstalk environment is designed to abstract the underlying resources used to run the application. When the load balancer type is changed, the entire environment must be recreated with the new load balancer. Therefore, to migrate an Elastic Beanstalk environment from a Classic Load Balancer to an Application Load Balancer, the recommended steps are to clone the existing environment and associate it with the Application Load Balancer. After cloning, the same application version as used in the original environment is deployed to the new environment. Finally, the swap-environment-cnames action is run to swap the environment URLs so that the new environment takes over the traffic.

By cloning the existing environment and changing the associated load balancer type, the developers can create a new environment with an Application Load Balancer. They can then deploy the same application version as used in the original environment and run the swap-environment-cnames action to switch traffic from the old environment to the new one.

C is the correct answer here. Option B is incorrect because creating a new environment is not necessary and can result in additional cost and maintenance overhead.

you need to create a new environment with the desired Load Balancer type.

https://repost.aws/questions/QUEemsrTM_TPG3r_HdoG08EQ/how-to-remove-or-change-a-load-balancer-type-with-elastic-beanstalk

Never mind. Cloning will clone it with a classic load balancer. Won't let you change it. B it is.

Why B over C? Cloning the environment is a valid option

https://repost.aws/questions/QUEemsrTM_TPG3r_HdoG08EQ/how-to-remove-or-change-a-load-balancer-type-with-elastic-beanstalk

Will need to create a new application to change the ELB type