You are the messaging engineer for your company. Your company has offices in Tokyo, New York, and Vancouver.

Your company will grow its workforce by 30 percent during the next three years. You plan to deploy Exchange Server 2007.

You need to deploy the Exchange Server 2007 Mailbox servers to meet the following requirements:

If a single server fails, maintain mailbox access.

Allow the installation of additional nodes into planned clustered Mailbox servers.

What should you do?

A.
Create a cluster continuous replication cluster. Place one node in the Tokyo office and one node in the New
York office.

B.
Deploy a Mailbox server in each office. Configure local continuous replication for each storage group and
configure a Network Load Balancing cluster.

C.
Create a single copy cluster in each office. Install an active clustered Mailbox server and a passive clustered
Mailbox server in each office.

D.
Create one single copy cluster. Install one active clustered Mailbox server in the Tokyo office and one
active clustered Mailbox server in the New York office. Install a passive clustered Mailbox server in the
Vancouver office.

Explanation:
A Single Copy Cluster is a clustered mailbox server using shared storage in a failover configuration, permitting multiple servers to manage a single copy of the storage groups.

Exchange 2007 Improvements:

1. Clustered mailbox server install directly integrated into Setup. As a result, clustered and non-clustered Setup experience similar, reducing learning curve traditionally associated with clustered apps.

2. Tasks that previously demanded Cluster Administrator can now be handled using Exchange management tools.

3. At completion of Setup, clustered mailbox server is fully up and running with optimal default settings, eliminating need for extensive admin tweaking.

SCCs require the use of a shared-nothing architecture, which includes shared disk storage. This means that, although all nodes can access shared data, they cant do so at the same time.

In SCC, the Mailbox server uses its own network identity, not that of any individual cluster node. This is termed the Clustered Mailbox Server. If the node running such a server fails, the cluster briefly goes offline, until another node can take control of the server and bring it back online. Storage Groups and databases of such a Clustered Mailbox Server are hosted on shared storage, available to each possible node. When failover takes place, control over this shared storage is transferred to the new host node.

For node maintenance, use Move-ClusteredMailboxServer to manually transfer the cluster across possible nodes. This process is known as a handoff.

http://technet.microsoft.com/en-us/library/bb125217.aspx