
Explanation/Reference:
Explanation:
From scenario:
The site resilience solution must follow the bound namespace model.

The forest contains a site in Houston and a site in London.

Litware plans to implement a site resilience solution ensuring that outbound email messages can be

delivered if one of the sites fails. The site resilience solution must allow all users to access their mailbox if a server fails in each site.
Box 1: Four
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 Box 2: Two 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.
Incorrect Answers:
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.