Your network contains a Webbased Application that runs on Windows Server 2003. You plan to
migrate the Webbased Application to Windows Server 2008 R2. You need to recommend a server
configuration to support the Webbased Application. The server configuration must meet the
following requirements:
• Ensure that the Application is available to all users if a single server fails
• Support the installation of .NET Applications
• Minimize software costs
What should you recommend?
A.
Install the Server Core installation of Windows Server 2008 R2 Standard on two servers. Configure
the servers in a Network Load Balancing cluster.
B.
Install the full installation of Windows Server 2008 R2 Web on two servers. Configure the servers
in a Network Load Balancing cluster.
C.
Install the full installation of Windows Server 2008 R2 Enterprise on two servers. Configure the
servers in a failover cluster.
D.
Install the full installation of Windows Server 2008 R2 Datacenter on two servers. Configure the
servers in a failover cluster.
Explanation:
Web Edition meets the requirements
Windows Web Server 2008 R2
Windows Web Server 2008 R2 is designed to function specifically as a Web application server.
Other roles, such as Windows Deployment Server and Active Directory Domain Services (AD DS), are
not supported on Windows Web Server 2008 R2. You deploy this server role either on a screened
subnet to support a website viewable to external hosts or as an intranet server. As appropriate given
its stripped-down role, Windows Web Server 2008 R2 does not support the high-powered hardware
configurations that other editions of Windows Server 2008 R2 do. Windows Web Server 2008 R2 has
the following properties:
: Supports a maximum of 32 GB of RAM and 4 sockets in symmetric multiprocessing (SMP)
configuration
You should plan to deploy Windows Web Server 2008 R2 in the Server Core configuration, which
minimizes its attack surface, something that is very important on a server that interacts with hosts
external to your network environment. You should plan to deploy the full version of Windows Web
Server 2008 R2 only if your organization’s web applications rely on features that are not available in
the Server Core version of Windows Web Server 2008 R2. Unlike the Server Core version of Windows
Web Server 2008, Windows Web Server 2008 R2 supports a greater amount of Internet Information
Services (IIS) functionality.
Configuring Windows Network Load Balancing
While DNS Round Robin is a simple way of distributing requests, Windows Server 2008 NLB is a much
more robust form of providing high availability to applications. Using NLB, an administrator can
configure multiple servers to operate as a single cluster and control the usage ot the cluster in near
real-time.
Why Failover Cluster will not work.
Contrast DNS Round Robin and NLB with Failover Clustering, another availability technology in
Windows Server 2008. Formerly known as server clustering, Failover Clustering creates a group of
computers that all have access lo the same data store or disk resource or network share. The
applicationsjunning on aJailoverCluster must be cluster-aware. Failover Clustering has had some
changes since Windows Server 2003. Lesson 2 will cover these changes.