70-285 Designing a Microsoft Exchange Server 2003 Organization Practice Test

Demo Question 3.

Answer: B

Explanation: Regarding to the interviews and requirements we know : 1. Interview with CIO Requirement 5 : " We need to be able to apply service packs and security updates without affecting users' access to their mailboxes." 2. Interview with the Messaging Expert point 2: "We must have redundant servers for all messaging functions." 3. Interview with the Messaging Expert point 4: "We must also have dedicated servers for each mail function. 4. Messaging Infrastructure Technical requirements point 2 : " Users must be able to send and receive e-mail messages in the event of a single mailbox server failure." Therefore we need to design a redundant solution for The School of Fine Art. A cluster hosts one or more virtual servers. Each virtual server has the same kind of resources you would expect to find in a regular server-such as a network name and an IP address-and drives and application services and so forth. The servers that run the cluster service are called nodes. Each node hosts a virtual server and its resources. In a two-node cluster, if you create a single Exchange virtual server and assign it to one of the nodes, the other node does nothing until the first node fails. This is an active/passive cluster. If you create two or more Exchange virtual servers and host one on each of the nodes, then you have an active/active cluster. In an active/active cluster, if one of the underlying servers goes down-a node failure-the virtual Exchange server hosted by that node rolls over to the good node. Now that node hosts two virtual Exchange servers. This is certainly supported, but it presents a challenge to the Exchange designers. Microsoft did extensive improvements in the memory handling of both Windows Server 2003 and Exchange Server 2003 to improve cluster operations, but it's still possible to make too many demands on system memory to get a clean failover. In Exchange 2000, Microsoft recommended a maximum of 1900 concurrent connections when using active/active clustering, and it has not revised that number upward for Exchange 2003. In fact, its emphatic recommendation, is to avoid active/active clustering completely. Incorrect