AirWatch Cloud Connector is down in the civic data center. What should the associate expect?
Select an answer to reveal the explanation.
Short Explanation
Cloud Connector is the bridge to the directory, not the entire highway to SaaS. New AD names may not appear and CA-style jobs can stall, but phones that already enrolled can still check in to the cloud. It is not the Blast gateway and not NSX.
Full Explanation
When AirWatch Cloud Connector is down in the civic data center, the associate should expect that new Active Directory users and some on-premises UEM integrations may fail, while enrolled-device SaaS check-ins can still occur against the cloud tenant. Cloud Connector is the bridge to directory and enterprise systems, not the entire path every enrolled phone uses for routine SaaS communication. It is incorrect that every already-enrolled device immediately loses all SaaS UEM check-in solely because Cloud Connector is down. Horizon Blast sessions do not fail because Cloud Connector is the VDI gateway—that gateway role belongs to Unified Access Gateway for remote Horizon. NSX overlay segments for phones do not collapse when Cloud Connector returns offline; NSX is not dependent on ACC for underlay or overlay existence. Exam caveat: “some check-ins continue” does not mean certificate renewals, new AD-based assignments, or other ACC-dependent jobs still succeed—scope the outage precisely for civic stakeholders. Operational check: stop Cloud Connector in a maintenance window, confirm an already-enrolled test tablet still checks into SaaS UEM, attempt to sync a brand-new AD user, and document which integrations fail until ACC is restored.