An on-premises mediator has been deployed. When a pod is stretched and replicating, it is observed that the pod is utilizing the Pure1 Cloud Mediator…

The selection of a mediator for an ActiveCluster pod is a specific configuration choice made during the pod's creation or via a subsequent modification command. An environment can have both the Pure1 Cloud Mediator and an on-premises mediator available. However, each stretched pod must be explicitly configured to use one or the other. If an administrator creates a new pod and does not specify the on-premises mediator, the system will use the default setting, which is the Pure1 Cloud Mediator. The observed behavior is therefore the direct result of the pod's configuration not being set to use the on-premises mediator.

B. The on-premises mediator is a fully supported deployment option specifically designed for ActiveCluster to provide a third-site witness without requiring an internet connection.

C. A missing DNS A record would cause connection errors and alerts for the on-premises mediator, not a silent, automatic fallback to using the cloud mediator.

1. Pure Storage, "Purity//FA ActiveCluster Configuration and Best Practices," Page 12, Section: "Creating a Stretched Pod." The documentation shows the purepod create command with the optional --mediator parameter, demonstrating it is a configurable setting.

2. Pure Storage, "Purity//FA CLI User Guide," Section: purepod create. The command syntax purepod create [--mediator MEDIATORADDRESS] confirms that the mediator must be specified for the pod. If omitted, the default is used.