Lync iApp - only reverse proxy for Lync Web Services

Short answer - If you aren't using the up-to-date iApp, grab it, as that actually separates out the Reverse Proxy section. It sounds like question 2 above reflects the older version where it insisted you had to deploy Edge External load balancing within the iApp first to dig through to the question.

Long answer - Lync reverse proxy works like this.

On your internal load balancer, if you have more than one FE/DIR you may be load balancing the pools. You should deploy your "internal reverse proxy interface" to point at these servers. If you do not use your load balancer on this, it doesn't matter.

On your external load balancer, you should find the section "Would you like to create a BIG-IP virtual server to act as a reverse proxy for external Lync web services?" and state yes. You can point this at your 4443 listener on your internal FE load balancer pool, or you can point it directly at your FE server if you just have the one.