City firewall engineers ask where AirWatch Cloud Connector should live for the civic Workspace ONE SaaS tenant. Which resource supports that placement argument?
Select an answer to reveal the explanation.
Short Explanation
Where ACC sits is a map question, and Tech Zone prints that map. Agent logs, Boxer DLP, and Citrix guides do not place Cloud Connector for Workspace ONE SaaS. Use the reference architecture when the firewall team asks.
Full Explanation
Tech Zone reference architecture for Workspace ONE SaaS and AirWatch Cloud Connector placement is the resource that supports where ACC should live for a civic Workspace ONE SaaS tenant when firewall engineers ask for a placement argument. That material covers control-plane connectivity patterns for SaaS UEM. Network change boards accept ACC placement requests more readily when the attachment includes the Tech Zone diagram showing required ports and trust boundaries. Horizon Agent logs on an instant clone diagnose desktop-session issues and say nothing about ACC placement for Workspace ONE SaaS. Boxer attachment DLP policy is an email control, not a connector architecture guide for firewall change requests. A Citrix ADC deployment guide documents a different vendor's edge and must not drive Workspace ONE ACC placement decisions. Exam caveat: SaaS Workspace ONE still requires customer-side connector placement decisions, and those come from Tech Zone reference architecture rather than Horizon session logs. Operational check: Open the Tech Zone SaaS and ACC reference design, note required outbound connectivity and recommended network location for ACC, and align the city firewall change request to that diagram.