Name:

Date:

Wilson Agomuo
3/9/2016

Exchange 2010
1. What are the various server roles associated with Exchange 2010?
Mailbox Role
Client Access Role
Hub Transport Role
Edge Transport Role
Unified Messaging Role
2. What is a CAS Array?
In addition to the RPC Client Access service, Exchange 2010 introduced a new logical
structure to the Exchange organization: the Client Access server array. When a Client
Access server array is defined in an Active Directory site, it serves as a single contact
point for all client connections within that Active Directory site. A Client Access server
array can include one or many Client Access servers. After a Client Access server array
is defined within an Active Directory site, all Client Access servers within that Active
Directory site are automatically part of the Client Access server array.

3. What is used for High Availability in Exchange 2010?

Microsoft Exchange Server 2010 enables you to deploy your Mailbox server
infrastructure using standalone Mailbox servers or Mailbox servers configured for mailbox
resiliency. Mailbox servers configured for mailbox resiliency employ a database
availability group (DAG) with multiple database copies efficiently distributed throughout
the DAG.
By deploying multiple database copies, you can:
Design a solution that mitigates the most common reason for using a backup.
Database copies provide protection against hardware, software, and data center
failures.
Increase database sizes up to 2 terabytes because your recovery mechanism is
another database copy and not restoration from backup.

Consider storage architecture alternatives to a traditional RAID configuration like

just a bunch of disks (JBOD), if you deploy three or more database copies. The
combination of JBOD and less expensive disks can result in cost savings for your
organization.

By distributing active databases across all the servers that participate within a
DAG, you can maximize the efficiency of your hardware.

4. What is DAC?
DAC mode is used to control the database mount on startup behavior of a DAG. This
control is designed to prevent split brain from occurring at the database level during a
datacenter switchback. Split brain, also known as split brain syndrome, is a condition that
results in a database copying being mounted as an active copy on two members of the
same DAG that are unable to communicate. Split brain is prevented using DAC mode
because DAC mode requires DAG members to obtain permission to mount databases
before they can be mounted.

5. How many nodes can you have in a DAG?

16 Mailbox servers

6. What does the file share witness do?

If your FSW doesn't affect mail flow at all. It's used to make sure that there is an odd
number of votes for the Dag members when deciding quorum.
Take for example, you have four Dag members in a Dag. If the network between
them gets severed in such a way that two of the members can talk to each other, and
the other two can (but not with the first two) how would they decide which one is the
Primary Active Manager? They can't. Neither of the halves have a majority of the
votes (there being four votes). With an FSW there are five possible votes, so if the
networks gets severed again it might result is 3 and 2, and the group that has the
three votes decides who the Primary Active Manager is.

7. What is Quorum?
Underneath every DAG is a Windows failover cluster. Failover clusters use the concept of
quorum, which uses a consensus of voters to ensure that only one subset of the cluster
members (which could mean all members or a majority of members) is functioning at one
time.
Quorum represents a shared view of members and resources, and the term quorum is
also used to describe the physical data that represents the configuration within the cluster
that's shared between all cluster members. As a result, all DAGs require their underlying
failover cluster to have quorum. If the cluster loses quorum, all DAG operations terminate
and all mounted databases hosted in the DAG dismount. In this event, administrator
intervention is required to correct the quorum problem and restore DAG operations.

8. How do you set up a CAS Array?

You must configure internal DNS entry
Configure Load Balancing Technology
Then create the CAS array
Configure a mailbox Database to use a CAS array
You can create a Client Access array within your Active Directory site by using the
following command. New-ClientAccessArray -Name name -Site site_name -FQDN
internal_only_CAS_Array_FQDN

9. Can you explain how failover works in Exchange 2010?

You need one cluster with two servers and with a DAG

10. What is CAS proxying and re-direction in Exchange 2010?

In a Microsoft Exchange Server 2010 organization, a Client Access server can act as a
proxy for other Client Access servers within the organization. This is useful when multiple
Client Access servers exist in different Active Directory sites in an organization, and at
least one of those sites isn't exposed to the Internet.
A Client Access server can also perform redirection for Microsoft Office Outlook Web App
URLs and for Exchange ActiveSync devices. Redirection is useful when users connect to
a Client Access server that isn't in their local Active Directory site, or if a mailbox has
moved between Active Directory sites. It's also useful if users should actually be using a
more effective URL. For example, users should be using a URL that's closer to the Active
Directory site in which their mailbox resides.

11. What are all the archiving features introduced in Exchange 2010?
In Microsoft Exchange Server 2010, personal archives provide users an alternative
storage location in which to store historical messaging data. A personal archive is an
additional mailbox (called an archive mailbox) enabled for a mailbox user.
Autodiscover is an Exchange 2010 service that provides configuration settings to
automatically configure Outlook clients. When delegates use Outlook to access an
Exchange 2010 SP1 mailbox, both the primary mailbox and the personal archive to which
they have access are visible from Outlook.

Moving Messages to the Archive Mailbox

Archive and Retention Policies
Default Archive and Retention Policy
Archive Quotas
Managing Archive Mailboxes

12. What is shadow redundancy?

Shadow redundancy in Microsoft Exchange Server 2010 provides a high availability
mechanism for messages for the entire time that the messages are in transit.
Exchange Server 2010 introduces the shadow redundancy feature to provide redundancy for
messages for the entire time they're in transit. The solution involves a technique similar to the
transport dumpster. With shadow redundancy, the deletion of a message from the transport
databases is delayed until the transport server verifies that all of the next hops for that message
have completed delivery.

13. What is the RPC Client Access Service?

In Microsoft Exchange Server 2007, the Client Access server role was introduced to
handle incoming client connections to Exchange mailboxes. Although the majority of
types of client connections were made to the Client Access server, Microsoft
Office Outlook still connected directly to the Mailbox server when it was running internally
with the MAPI protocol.
A new service was introduced with Exchange Server 2010 to allow these MAPI
connections to be handled by the Client Access server. The RPC Client Access service
provides data access through a single, common path of the Client Access server, with the
exception of public folder requests, which are still made directly to the Mailbox server.
This change applies business logic to clients more consistently, and provides a better
client experience when failover occurs.

14. What is circular Logging?

Circular logging allows Exchange to overwrite transaction log files after the data that the
log files contain is committed to the database. However, if circular logging is enabled, you
can recover data only up until the last full backup. For example, you can enable circular
logging when using Exchange native data protection, in which you don't make backups.
To prevent log buildup, you need to enable circular logging.

15. What is federated sharing in Exchange 2010?

Federated delegation uses the Microsoft Federation Gateway, a cloud-based service
offered by Microsoft, as the trust broker between your on-premises Exchange 2010
organization and other federated Exchange 2010 organizations.

Using federated delegation, users in your on-premises Exchange organization can share
information with recipients in other Exchange organizations that are also configured for
federated delegation. This connection is established by creating organization
relationships between the two organizations or by using a sharing policy, which allows
users to create sharing relationships on an individual basis.