Explanation/Reference:
Explanation:
The company is developing an application named App1. App1 is a multi-tier application that will be sold as a service to customers.
Each instance of App1 is comprised of the following three tiers:
A web front end

A middle tier that uses Windows Communication Foundation (WCF)

A Microsoft SQL Server 2008 R2 database on the back end

Each tier will be hosted on one or more virtual machines. Multiple tiers cannot coexist on the same virtual machine.
When customers purchase App1, they can select from one of the following service levels:
Standard: Uses a single instance of each virtual machine required by App1. If a virtual machine

becomes unresponsive, the virtual machine must be restarted.
Enterprise: Uses multiple instances of each virtual machine required by App1 to provide high-

availability and fault tolerance.
All virtual hard disk (VHD) files for App1 will be stored in a file share. The VHDs must be available if a server fails.
You plan to deploy an application named App2. App2 is comprised of the following two tiers:
A web front end

A dedicated SQL Server 2008 R2 database on the back end

App2 will be hosted on a set of virtual machines in a Hyper-V cluster in the Miami office. The virtual machines will use dynamic IP addresses. A copy of the App2 virtual machines will be maintained in the Seattle office.
App2 will be used by users from a partner company named Trey Research. Trey Research has a single Active Directory domain named treyresearch.com. Treyresearch.com contains a server that has the Active Directory Federation Services server role and all of the Active Directory Federation Services (AD FS) role services installed.
You can use the following procedure to create a virtual IP (VIP) template for a hardware load balancer. A virtual IP template contains load balancer-related configuration settings for a specific type of network traffic. For example, you could create a template that specifies the load balancing behavior for HTTPS traffic on a specific load balancer manufacturer and model. These templates represent the best practices from a load balancer configuration standpoint.