This sample scenario demonstrates how the Cloud Pod Architecture feature can solve a real-world problem. It includes step-by-step instructions that you can follow to complete a Cloud Pod Architecture configuration.

In this scenario, a health insurance company has a mobile sales force that operates across two regions, the Central region and the Eastern region. Sales agents use mobile devices to present insurance policy quotes to customers and customers view and sign digital documents.

Rather than store customer data on their mobile devices, sales agents use standardized View floating desktops. Access to customer data is kept secure in the health insurance company's datacenters.

The health insurance company has two datacenters, one in each region. Occasional capacity problems cause sales agents to look for available desktops in a non-local datacenter, and WAN latency problems sometimes occur. If sales agents disconnect from desktops but leave their sessions logged in, they must remember which datacenter hosted their sessions to reconnect to their desktops.

To solve these problems, the health insurance company designs a Cloud Pod Architecture topology, initializes the Cloud Pod Architecture feature, joins its existing pods to the pod federation, creates sites for each of its datacenters, entitles its sales agents to all of its desktop pools, and implements a single View URL.