You have 10 Hyper-V hosts that run Windows Server 2016.
Each Hyper-V host has eight virtual machines that run a distributed web application named App1.
You plan to implement a Software Load Balancing (SLB) solution for client access to App1.
You deploy two new virtual machines named SLB1 and SLB2.
You need to install the required components on the Hyper-V hosts and the new servers for the planned
implementation.
Which components should you install? Choose Two.

A.
Component to install on SLB1 and SLB2: SLB Host Agent

B.
Component to install on SLB1 and SLB2: Network Load Balancing (NLB)

C.
Component to install on SLB1 and SLB2: SLB Multiplexer (MUX)

D.
Component to install on each Hyper-V host:SLB Host Agent

E.
Component to install on each Hyper-V host:SLB Multiplexer (MUX)

F.
Component to install on each Hyper-V host:Host Guardian Service server role

Explanation:
https://blogs.technet.microsoft.com/tip_of_the_day/2016/06/28/tip-of-the-day-demystifying-software-definednetworking-terms-the-components/
https://technet.microsoft.com/en-us/library/mt632286.aspx
SLB Host Agent – When you deploy SLB, you must use System Center, Windows PowerShell, or another
management application to deploy the SLB Host Agent on
every Hyper-V host computer.
You can install the SLB Host Agent on all versions of Windows Server 2016 that provide Hyper-V support,
including Nano Server.
SLB MUX – Part of the Software Load Balancer (SLB on Windows Server 2016, the SLB MUX processes
inbound network traffic and maps VIPs (virtual IPs) to
DIPs (datacenter IPs), then forwards the traffic to the correct DIP. Each MUX also uses BGP to publish VIP
routes to edge routers. BGP Keep Alive notifies MUXes
when a MUX fails, which allows active MUXes to redistribute the load in case of a MUX failure – essentially
providing load balancing for the load balancers.