I85PREP
⌘ K
Cisco CLCEI 300-820 study materials
Cisco CLCEI 300-820 study resources

Cisco CLCEI 300-820: Hybrid and Cloud Collaboration Architecture and Deployment Models

Cisco CLCEI 300-820 · Work through your exam, one topic at a time.

All guide sections

Hybrid and Cloud Collaboration Architecture and Deployment Models

This domain tests whether you can look at a customer scenario and choose the right Cisco collaboration deployment, then name the hybrid service and connector that makes it work. Expect questions that contrast on-premises, cloud, and hybrid, and that ask which component sits where.

The deployment spectrum

  • On-premises: Cisco UCM, IM and Presence, gateways, and Expressway are owned and operated by the customer. Maximum control, maximum operations burden.
  • Cisco-hosted cloud: Webex Meetings, Webex App messaging, Webex Calling, and UCM Cloud. UCM Cloud is a dedicated Cisco-hosted UCM cluster, not the same product as multi-tenant Webex Calling.
  • Hybrid: call control and data stay on-premises while Webex cloud supplies meetings, calendar, messaging, management, or analytics.

Hybrid service families

  • Hybrid Calendar Service - calendar connector on Expressway-C.
  • Directory Connector - Active Directory sync to Control Hub.
  • Hybrid Call Service Connect - call connector tying Webex App to on-premises UCM.
  • Hybrid Message Service - legacy, not offered for new deployments.
  • Hybrid Data Security - customer-hosted key management for messaging.
  • Webex Cloud-Connected UC - UCM telemetry and management into Webex.

The connector pattern

Every hybrid connector is outbound-only from Expressway-C to Webex over TCP 443. No inbound pinhole into the corporate network is required. Expressway-C registers to Control Hub, then each service is enabled and authorized per organization.

Worked example

A retailer runs UCM 14 on-premises and Exchange on-premises, and wants Webex App users to see meetings and join with one button. The answer is Hybrid Calendar Service plus Directory Connector, both hosted on the existing Expressway-C. Reasoning: the calendar connector talks to Exchange Web Services and outbound to Webex, and the directory connector reads LDAP. No Expressway-E is needed because neither service traverses the public internet inward. Expressway-E would only be required for mobile and remote access or business-to-business calling.

Traps that cost marks

  • Assuming every hybrid service needs an Expressway-E in the DMZ.
  • Treating Hybrid Message Service as still orderable.
  • Confusing UCM Cloud with Webex Calling; they have different dial plans and PSTN models.
  • Believing Directory Connector needs inbound LDAP from the cloud.