DRAG DROP - You have an Azure subscription that contains the resources shown in the following table. 
Looks like the right sequence is remove the public IPs from vm1 and vm2, create a health probe and backend pool on lb1, then add the load balancing rule. Standard LB can't work with VMs that have basic public IPs still attached. Saw a similar question on my last mock so I think that's correct but let me know if you see a catch.
This comes up a lot in labs and the official practice tests: remove public IPs from vm1/vm2 first, set up health probe and backend pool, then add the LB rule. Pretty sure that's the sequence from Microsoft docs but let me know if there's a different twist here.
- Remove public IP addresses from vm1 and vm2
- Create a health probe and backend pool on lb1
- Create a load balancing rule on lb1
