OpsWork Load Balancer Integration: Steps and Processes

Steps to Attach a Load Balancer to a Layer in OpsWork

Prev Question Next Question

Question

What are the steps that get carried out by OpsWork when you attach a load balancer to a layer in OpsWork?

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D.

Answer- B, C, and D.

For the exam, remember that, after you attach a load balancer to a layer, AWS OpsWorks Stacks does the following.

Deregisters any currently registered instances.

Automatically registers the layer's instances when they come online and deregisters instances when they leave the online state, including load-based and time-based instances.

Automatically activates and deactivates the instances' Availability Zones.

Hence, options B, C, and D are CORRECT.

For more information on working with Opswork layer ELB's, please refer to the below link.

http://docs.aws.amazon.com/opsworks/latest/userguide/layers-elb.html

Please refer to page 218 on the below link.

https://docs.aws.amazon.com/opsworks/latest/userguide/opsworks-ug.pdf

When you attach a load balancer to a layer in OpsWorks, the following steps are carried out:

B. De-registers any currently registered instances: OpsWorks will de-register any instances that are currently registered with the load balancer, which means that the load balancer will stop sending traffic to these instances.

C. Automatically registers the layer's instances when they come online and de-registers instances when they go offline, including load-based and time-based instances: OpsWorks will automatically register any instances that are launched within the layer and are available for use. This includes instances launched based on load and time-based scaling policies. Similarly, when instances are terminated or become unavailable, OpsWorks will automatically de-register them from the load balancer.

D. Automatically starts routing requests to registered instances in their Availability Zones: Once instances are registered with the load balancer, OpsWorks will start routing traffic to them based on their Availability Zones. This ensures that traffic is distributed evenly across all available instances, and that instances in different Availability Zones are used as part of a high-availability configuration.

A. Terminates the EC2 Instances: This is not a step that is carried out when you attach a load balancer to a layer in OpsWorks. Instead, instances will be terminated based on the scaling policies that are configured for the layer, which may include load-based and time-based scaling policies.