The design and deployment of a single, hierarchical access model is not a trivial undertaking. Neither is the task of maintaining this platform as new sites are added or capacity exhaustion causes the available sites within a zone to change over time. Because of the advantages to offering this resilient access model, it is worth considering as part of the deployment of vCloud Director or the upgrade to v9.0. However, this level of complex access capability is not necessary to realize the benefits of multisite access. A Cloud Service Provider might choose to deploy a more local version in which each site has its own direct access URLs. In addition, sites that are typically used in availability pairs or zones can have an access URL that distributes connections across those few sites, as shown in the following figure.

 

Customers might choose to take service in sites which the Service Provider does not consider part of a single zone or region, perhaps at opposite ends of a particular geography. Unless the provider chooses to offer a bespoke per-customer access model, there might not be the justification for a multilevel hierarchy of DNS names and URLs, and direct, per-site access might be the only sensible option.