How many namespaces and DAGs should you recommend adding?

HOTSPOT

You need to recommend how many database availability groups (DAGs) and how many namespaces must be added to the site resilience solution to meet the availability requirements.

How many namespaces and DAGs should you recommend adding? To answer, select the appropriate options in the answer area. NOTE: Each correct selection is worth one point.

View Answer

Answer:

Explanation:

Box 1: Number of namespaces: Four

Box 2: Number of Dags: Two Depending on your architecture and infrastructure you have two choices: These choices are tied to the DAG architecture.

• Deploy a unified namespace for the site resilient datacenter pair (unbound model).

• In an unbound model, you have a single DAG deployed across the datacenter pair.

• Deploy a dedicated namespace for each datacenter in the site resilient pair (bound model). In a bound model, multiple namespaces are preferred, two per datacenter (primary and failback namespaces), to prevent clients trying to connect to the datacenter where they may have no connectivity.

As its name implies, in a bound model, users are associated (or bound) to a specific datacenter. In other words, there is preference to have the users operate out of one datacenter during normal operations and only have the users operate out of the second datacenter during failure events. There is also a possibility that users do not have equal connectivity to both datacenters. Typically, in a bound model, there are two DAGs deployed in the datacenter pair. Each DAG contains a set of mailbox databases for a particular datacenter; by controlling where the databases are mounted, you control connectivity.

From scenario:

The servers in the New York and London offices are members of a database availability group (DAG).

Fabrikam identifies the following high-availability requirements for the planned deployment: Mailbox databases that contain mailboxes for the New York office users must only be activated on the servers in the London office manually. All client access connections to the London and New York offices must use load-balanced namespaces. The load balancing mechanism must perform health checks.

References: https://blogs.technet.microsoft.com/exchange/2015/10/06/namespace-planning-in-exchange­2016/