A database outage with different connection outcomes

A fictional on-premises Citrix site has two zones. Each zone has Controllers and VDAs, and the design includes Local Host Cache. During an authorized test, connectivity to the site database is interrupted. Existing sessions continue to run, and some new launches to eligible local resources succeed. A requested launch requiring a resource in another zone does not succeed during the outage. The project sponsor concludes that Local Host Cache is broken because its name sounds like a complete copy of the normal control plane. The operations team has recorded the relevant component events and test timestamps but has not compared the requested launch with the documented outage restrictions. No one has authorization to make broad production configuration changes. The architect needs to distinguish an expected design boundary from evidence of a separate fault.