1) How many copies of Database can DAG host in Exchange 2010

A Database Availability Group is a group of up to 16 Exchange Server 2010

servers that are installed with the Mailbox server role. Each server that is
a member of the DAG is capable of hosting active or passive copies of
mailbox databases that reside on servers in the group.

2) Advantages of DAG
All of the Mailbox servers within the Exchange 2010 DAG can be active
and in use at all times to some capacity
Each mailbox database can failover/switchover when necessary without
impacting the mailbox users connected to other mailbox databases within
the DAG, for example when installing updates on DAG members
Unlike previous versions of Exchange Server (particularly Exchange Server
2007) Exchange Server 2010 has just one high availability feature for
Mailbox servers for all high availability deployment scenarios
When you create a Database Availability Group the underlying Windows
Failover Cluster is automatically created and configured for you
A Database Availability Group can be created at any time without
requiring Exchange Server 2010 to be removed and reinstalled from the
server, unlike previous versions that required that clusters be established
first before Exchange was installed
Exchange Server 2010 DAG members can host other server roles, unlike
Exchange Server 2007 that prevented clustered Mailbox servers from
hosting other roles

3) What is Quorum
Its a voting process in which a majority of voting members must be
present to make a decision

4) How a Quorum is achieved in DAG where there are even number of

servers/nodes.
To achieve quorum for a DAG with an even number of member servers
another server in the same site is designated as a File Share Witness for
the cluster. This is typically a Hub Transport server though it can
technically be any compatible Windows server. To achieve quorum for a
DAG with an even number of member servers another server in the same
site is designated as a File Share Witness for the cluster. This is typically a
Hub Transport server though it can technically be any compatible Windows
server.
5) What are the two ways of Database replication in Exchange 2010 DAG
File mode replication and Block mode replication

 File Mode replication: - With file mode replication as each transaction log is
written and then closed off (once it reaches 1Mb in size) it is then copied
to each member of the DAG that also holds a copy of that mailbox
database. The other members receive the file into their replay queue, and
then replay the transaction log file into their own passive copy of the
database. File mode replication is used to bring mailbox database copies
into sync with each other (e.g. during the initial sync process when a new
database copy is added).
Block mode replication: - Once Databases are in sync the DAG members
switch to block mode replication. In block mode replication each
database transaction is written to the log buffer on the active server and
also sent to the log buffer of DAG members hosting passive copies of the
database. When the log buffer becomes full each DAG member then builds
their own transaction log files from their own log buffer

6) Which DAG replication mode has advantage over the other?

Block mode replication has an advantage over file mode replication in
failure scenarios, because each DAG member is completely up to date
with all changes to the active database. Block mode replication has an
advantage over file mode replication in failure scenarios, because each
DAG member is completely up to date with all changes to the active
database.

7) Why do you we uncheck register this connection address in DNS setting in

DAG secondary interface?
Because the Mailbox servers are configured with dual interfaces it is
important to make sure that the secondary interface is not configured to
register itself in DNS. Open the TCP/IPv4 properties for the secondary
interface one each server, click the Advanced button, navigate to the DNS
tab and untick Register this connections address in DNS

8) What is the difference between Exchange 2007 CAs and Exchange 2010
CAS connectivity and use.
In Exchange 2007 CAS server was used for Client Connections for services
such as Outlook Web Access, ActiveSync, Outlook Anywhere, and other
web services. However a mailbox user still connected directly to the
Exchange 2007 Mailbox server for mailbox and public folder access
In Exchange Server 2010 the Client Access server role was expanded to
include a new service called the RPC Client Access Service. This service
allows Outlook clients to connect via MAPI/RPC to the Client Access server
for mailbox access, however they do still connect directly to mailbox
servers for public folder access

9) What are the advantages of RPC Client access service

 Connections to mailbox resources are made via a common path

Connection throttling and other rules can be applied to mailbox
connectivity
The end user experience during Mailbox server failovers and mailbox
moves is improved
The RPC Client Access service can be made highly available using feature
CAS Array.

10)

What is a CAS Array

The Client Access Server array is simply an object in Active Directory that
associates a DNS name with the RPC Client Access Service for a particular
AD Site.

11)

What are the basic requirements to create a CAS Array

Create the CAS Array object in Active Directory
Configure a DNS record for the CAS Array name pointing to an IP address
for a Client Access server
Configure the RPCClientAccessServer attribute on the mailbox databases
in that site

12)

How to create a CAS array

New-ClientAccessArray -Name CASRRAY name -Fqdn CASArray FQDNSite Name

13)

How to configure DNS for Client Access Array

Configure a DNS A record for the FQDN you specified when creating the
CAS Array object.

14)

How to configure Client access Array in NLB.

Create NLB Cluster by adding the CAS servers who will be members of the
Cluster.
Register a DNS record for NLB Cluster name
Create a CAR Array from management Shell by typing NewClientAccessarray -Siet Site name fqdn FQDN of CASArray
Update existing Mailbox Databases RPC Client Access Server attribute to
point to CASArray name
Any new database will automatically be pointed to new CAS Array.

15)

How to configure RPC Client Access attribute in Exchange Databases

BY running the command
Get-MailboxDatabase | Set-RpcClientaccessServer FQDN of CAS Array

16)

How can we configure High availability for CAS Arrays

The configuration of the CAS Array itself is the same, however instead of
pointing the DNS record at the IP address of a single Client Access server
you would point it at the virtual IP of a load balanced array of servers
The load balancing can be achieved in multiple ways:
By deploying a Windows Network Load Balancing (NLB) cluster for the
Client Access Servers
By deploying a virtual or hardware-based load balancer appliance
By Deploying a DNS round robin for Load balance (Disadvantage)

17)

What are the best practices for Exchange 2010 CAR Arrays
Always configure CAS Array in your Exchange 2010 Sites
Configure the CAS array before you provision Mailbox database or Mailbox
users to Exchange 2010 in that site

18)

What are the benefits of CAS Array

making it easy to scale out the CAS Array name to multiple Exchange
2010 Client Access servers
making it simpler to replace a Client Access server with a new one of a
different name
migrating the MAPI endpoint to future versions of Exchange Server

19)

Can DAG and NLB configured for CAR Array server co-exist on the
same server?
DAG members user Windows Failover Cluster which cannot co-exist with
NLB