Knowledge + Practice

CCNA Cloud And Hybrid Services Questions

63 questions · Cloud And Hybrid Services · All types, answers revealed

Practice these questions Domain overview All questions

1

MCQeasy

What is the first step to enable Webex Hybrid Services in a new organization?

A.Register the organization in Control Hub.

B.Purchase a PSTN plan.

C.Install the Expressway-C software.

D.Assign licenses to all users.

AnswerA

Control Hub is the management portal for Webex services, and an organisation must first be registered there before any Hybrid Services connector or resource can be provisioned. Registration establishes the org identity and licensing context required for subsequent hybrid configuration.

Why this answer

The first step to enable Webex Hybrid Services is to register the organization in Control Hub (A), because Control Hub is the management portal where the organization's Webex identity, licenses, and hybrid service configuration live. Without an organization registered in Control Hub, there is no anchor point for connecting on-premises components like Expressway-C or Expressway-E. Only after registration can you download the connector software, generate certificates, and configure hybrid services such as Hybrid Calendar, Hybrid Call Service, or Hybrid Message Service.

Exam trap

CLCOR often tests ordering of operations — candidates jump to installing Expressway-C because it is the visible on-premises component, forgetting that Control Hub organization registration must happen first to generate the connector and token.

How to eliminate wrong answers

Option B (Purchase a PSTN plan) is wrong because PSTN connectivity is a calling feature unrelated to enabling hybrid services; hybrid services connect on-premises infrastructure to Webex cloud, not to the PSTN. Option C (Install the Expressway-C software) is wrong because Expressway-C cannot be registered to Webex until the organization exists in Control Hub and the connector has been downloaded and configured from there — installation is a later step. Option D (Assign licenses to all users) is wrong because user licensing is a post-registration administrative task and is not required to enable hybrid services at the organizational level.

Practice this question →

2

MCQmedium

Which deployment model should be chosen for Cloud Connected PSTN (CCP) if the organization wants to leverage their existing carrier contracts?

A.Local Gateway PSTN

B.Webex Calling PSTN via Cisco

C.Cloud Connected PSTN (CCP)

D.Webex Calling Dedicated Instance

AnswerC

Cloud Connected PSTN (CCP) lets an organisation pair Webex Calling with its existing PSTN carrier contracts and numbers, rather than mandating a Cisco-provided calling plan. This directly satisfies the requirement to leverage current carrier agreements.

Why this answer

Cloud Connected PSTN (CCP) lets an organization bring its own PSTN carrier into Webex Calling by peering the carrier's network with the Webex Calling cloud, so existing carrier contracts, rates, and DIDs are preserved. This is the deployment model explicitly designed for 'use my existing carrier' scenarios, as opposed to Cisco-provided PSTN or on-premises gateways. The carrier must be a Webex Calling CCP partner.

Exam trap

CLCOR often tests the confusion between 'bring your own carrier' (CCP) and 'Cisco-provided PSTN' or 'Local Gateway,' so candidates who pick Local Gateway miss that CCP is the cloud-peered, contract-preserving option.

How to eliminate wrong answers

Option A is wrong because Local Gateway PSTN requires an on-premises Cisco gateway (e.g., CUBE) to connect to the PSTN, which does not leverage a cloud-peered carrier contract and adds on-prem hardware. Option B is wrong because Webex Calling PSTN via Cisco means Cisco provides the PSTN connectivity and DIDs, which replaces rather than leverages the customer's existing carrier contract. Option D is wrong because Webex Calling Dedicated Instance is a deployment topology for dedicated (non-shared) Webex Calling infrastructure, not a PSTN connectivity model, and does not by itself address carrier contract reuse.

Practice this question →

3

Multi-Selectmedium

Which TWO of the following are valid deployment models for the Webex Calling PSTN connectivity? (Choose two)

Select 2 answers

A.Webex Calling dedicated ISP.

B.Hybrid Cloud PSTN.

C.Local Gateway.

D.Peer-to-Peer PSTN.

E.Cloud Connected PSTN (CCP).

AnswersC, E

Local Gateway is a valid on-premises deployment model, connecting Webex Calling to your existing PSTN provider through a registered gateway at your site. It satisfies the scenario's requirement for a supported PSTN connectivity option, alongside Cloud Connected PSTN and Cisco PSTN, giving organisations direct control over voice trunks.

Why this answer

Webex Calling supports two valid PSTN connectivity deployment models: Local Gateway (C) and Cloud Connected PSTN (E). Local Gateway is correct because it uses an on-premises gateway (such as a Cisco IOS XE router or CUBE) registered to Webex Calling via the Local Gateway registration process, allowing the enterprise to connect its own PSTN trunks to the Webex Calling cloud. Cloud Connected PSTN (CCP) is correct because it lets a certified CCP provider deliver PSTN service directly to Webex Calling through the Cisco Cloud Connectivity platform, with no on-premises gateway required.

The remaining options are not valid Webex Calling PSTN deployment models: 'Webex Calling dedicated ISP' (A) is not a recognized model, 'Hybrid Cloud PSTN' (B) is not a Webex Calling PSTN option (hybrid refers to other deployment aspects), and 'Peer-to-Peer PSTN' (D) is not a supported architecture for Webex Calling PSTN connectivity.

Exam trap

CLCOR often tests the valid PSTN connectivity options, and candidates may be misled by plausible-sounding but non-existent models like 'Hybrid Cloud PSTN' or 'Peer-to-Peer PSTN'. The trap is selecting options that sound technical but are not official Webex Calling deployment models.

Practice this question →

4

MCQeasy

An administrator needs to verify that the Webex Hybrid Calendar Service connector is running and healthy. Where in Webex Control Hub should the administrator check the status of the connector?

A.Users > Manage Users

B.Organization Settings > Hybrid

C.Services > Hybrid Services > Calendar

D.Devices > List Devices

AnswerC

In Webex Control Hub, the status of hybrid service connectors is found under Services > Hybrid Services. Selecting Calendar shows the connector status, including whether it is running, stopped, or in error. This is the central place to monitor and manage all hybrid services, including Calendar, Call, and Message.

Why this answer

The correct location to verify the health of the Webex Hybrid Calendar Service connector is Services > Hybrid Services > Calendar in Webex Control Hub. This page provides the connector status, version, and any alerts. Administrators can also restart or troubleshoot connectors from here, making it the central monitoring point.

Exam trap

The trap here is assuming connector status is under Organization Settings or Devices, but it is specifically under Services > Hybrid Services.

Practice this question →

5

MCQmedium

What is the primary function of the Cisco Webex Edge Audio service?

A.To allow calling into Webex meetings via the corporate PSTN network.

B.To allow users to join meetings without an internet connection.

C.To encrypt all meeting audio traffic.

D.To provide high-definition video conferencing.

AnswerA

Webex Edge Audio routes meeting call-ins through the organisation's existing corporate PSTN infrastructure rather than Cisco's cloud telephony. This satisfies the requirement to leverage on-premises voice gateways for dial-in, reducing toll charges and keeping call traffic within the enterprise network.

Why this answer

Webex Edge Audio is a service that lets organizations route Webex meeting audio through their existing corporate PSTN/telephony infrastructure instead of the Webex cloud PSTN. This allows participants to dial into meetings using corporate phone lines, reducing toll costs and leveraging existing carrier contracts. It bridges on-premises voice gateways (CUBE/Expressway) with the Webex cloud for inbound and outbound audio.

Exam trap

CLCOR often tests the misconception that Edge Audio is about encryption or offline access — it is specifically about routing meeting audio through the corporate PSTN via SIP trunking.

How to eliminate wrong answers

Option B is wrong because joining without an internet connection is not the purpose of Edge Audio — participants still need connectivity to the Webex cloud or corporate network; Edge Audio is about PSTN routing, not offline access. Option C is wrong because encrypting meeting audio is handled by Webex's standard media encryption (SRTP/TLS), not by Edge Audio, which is a PSTN routing feature. Option D is wrong because high-definition video conferencing is a general Webex Meetings capability unrelated to Edge Audio, which specifically addresses audio PSTN integration.

Practice this question →

6

MCQmedium

What happens to a user's Webex account if they are removed from the synchronized Active Directory group?

A.The account remains active indefinitely.

B.The account is moved to a guest group.

C.The account becomes a free account.

D.The account is deactivated in Webex.

AnswerD

Directory synchronisation treats the Active Directory group as the source of truth, so removing a user from the synchronised group removes them from the Webex directory sync, and Control Hub deactivates the associated Webex account rather than deleting it outright.

Why this answer

When Webex Directory Synchronization is configured with Active Directory, the sync engine continuously reconciles Webex Control Hub users against the AD source of truth. If a user is removed from the synchronized AD group, the next sync cycle detects that the user is no longer in scope and deactivates the corresponding Webex account. Deactivation preserves the user's data (messages, files, settings) but blocks sign-in and license consumption until the account is either re-synced or manually reactivated.

Exam trap

CLCOR often tests the distinction between deactivation and deletion in Webex directory sync — candidates assume removal from AD either does nothing or fully deletes the account, when the actual behavior is a reversible deactivation that preserves data.

How to eliminate wrong answers

Option A is wrong because Webex directory sync is authoritative — leaving the account active indefinitely would defeat the purpose of AD-driven lifecycle management and would keep consuming licenses for users who no longer exist in the source group. Option B is wrong because guest accounts in Webex are created through a separate invitation workflow (or via specific guest-related sync rules), not as an automatic fallback when a synced user drops out of the AD group. Option C is wrong because Webex does not convert a deactivated enterprise user into a free consumer account; free accounts are a distinct account type tied to a personal sign-up, and enterprise-managed identities cannot silently downgrade to that state.

Practice this question →

7

MCQhard

You need to ensure that the Webex App can perform 'Click-to-Call' from a browser. What must be installed on the user's machine?

A.The Hybrid Calendar connector.

B.A local PSTN gateway.

C.Cisco Jabber for Windows.

D.Webex browser extension.

AnswerD

Click-to-Call from a browser requires the Webex browser extension, which integrates the Webex App with the browser to parse telephone numbers on web pages and hand them to the client. Without this extension, the browser cannot invoke the Webex App's calling functions.

Why this answer

Click-to-Call from a browser requires the Webex browser extension, which registers a URI handler (such as tel: or webex:) so the browser can hand off the click to the Webex App for call initiation. Without the extension, the browser has no mechanism to invoke the Webex App's dialer from a web page. The extension is available for Chrome, Edge, and Firefox and must be installed and enabled per user profile.

Exam trap

CLCOR often tests whether candidates confuse client-side browser integration (the Webex extension) with server-side services (Hybrid Calendar connector) or alternate clients (Jabber) — the extension is the only component that enables browser click-to-call.

How to eliminate wrong answers

Option A is wrong because the Hybrid Calendar connector is a server-side service on Expressway-C that syncs calendar data with Webex — it has nothing to do with browser click-to-call. Option B is wrong because a local PSTN gateway provides voice trunking to the PSTN and is unrelated to browser integration. Option C is wrong because Cisco Jabber is a separate softphone client; installing Jabber does not enable click-to-call within the Webex App and is not the required component.

Practice this question →

8

MCQeasy

Where in Webex Control Hub do you verify the health status of Hybrid Service connectors?

A.Troubleshooting tab

B.Devices tab

C.Services tab

D.Users tab

AnswerC

The Services tab in Webex Control Hub provides the dedicated health view for Hybrid Service connectors, showing connector status, alerts and connectivity to on-premises resources. This directly satisfies the stem's requirement to verify connector health, since connector monitoring lives under Services rather than general organisation or user settings.

Why this answer

In Webex Control Hub, the health status of Hybrid Service connectors is verified under the Services tab. Navigating to Services > Hybrid Services (or the specific service like Call/Calendar) shows connector status, registration state, and any alerts for each Expressway-C node running the connector.

Exam trap

CLCOR often tests the location of Hybrid Service connector status in Control Hub — candidates pick Troubleshooting because it sounds diagnostic, but connector health lives under Services.

How to eliminate wrong answers

Option A is wrong because the Troubleshooting tab focuses on call-quality diagnostics, meeting issues, and user-level troubleshooting — not connector health. Option B is wrong because the Devices tab lists Webex devices (phones, room systems) and their status, not Hybrid Service connectors. Option D is wrong because the Users tab manages user accounts, licenses, and assignments, not connector health.

Practice this question →

9

Multi-Selecthard

A company is deploying Webex Hybrid Data Security (HDS) to enhance privacy for Webex messages and files. Which two components must be deployed on-premises to support this service? (Choose two.)

Select 2 answers

A.Hybrid Data Security management connector

B.Hybrid Data Security node

C.Cisco Unified Communications Manager IM and Presence Service

D.Webex Meetings Server

E.Expressway-C and Expressway-E pair

AnswersA, B

The Hybrid Data Security management connector is an on-premises component that provides management and monitoring capabilities for the HDS nodes. It communicates with the Webex cloud to synchronize configuration and status. It is required in addition to the HDS node to fully deploy the service.

Why this answer

Hybrid Data Security requires two on-premises components: the HDS node, which stores encryption keys and performs cryptographic operations, and the HDS management connector, which handles management and communication with the Webex cloud. Together, they ensure that encryption keys remain on-premises while enabling secure messaging and file sharing in Webex.

Exam trap

The trap here is confusing Hybrid Data Security with other hybrid services that use Expressway or IM&P, leading to selection of components that are not part of HDS.

Practice this question →

10

MCQeasy

Which of the following is a key advantage of utilizing Cloud Connected PSTN (CCP)?

A.It allows for legacy analog phone support without an ATA.

B.It provides free long-distance calling globally.

C.It requires no internet connection.

D.It eliminates the need for on-premises PSTN gateways.

AnswerD

Cloud Connected PSTN delivers PSTN connectivity through the Cisco cloud, so calls route over the internet to the provider rather than through local gateways. This removes the requirement to deploy and maintain on-premises PSTN gateways at each site.

Why this answer

Cloud Connected PSTN (CCP) is a Cisco Webex Calling feature that connects your cloud phone system directly to a service provider's PSTN network in the cloud, bypassing the need for local gateways. This eliminates the hardware, maintenance, and configuration overhead of on-premises PSTN gateways, allowing calls to be routed entirely over the internet. It simplifies deployment and scales easily, which is the key advantage.

Exam trap

CLCOR often tests the misconception that CCP provides free calling or requires no internet, when in fact it still depends on an internet connection and incurs PSTN charges.

How to eliminate wrong answers

Option A is wrong because CCP does not inherently support legacy analog phones without an ATA; analog devices still require an ATA to convert signals to IP, regardless of PSTN connection type. Option B is wrong because CCP does not provide free long-distance calling; PSTN usage charges still apply based on the service provider's rates. Option C is wrong because CCP relies on an internet connection to reach the cloud PSTN service; without internet, calls cannot be made.

Practice this question →

11

MCQmedium

When using Webex Calling with the Local Gateway, which protocol is used for the SIP trunk between the CUBE and the Webex Calling cloud?

A.H.323

B.SCCP

C.MGCP

D.SIP

AnswerD

SIP is the signalling protocol carried over the trunk between the CUBE and Webex Calling cloud, satisfying the stem's requirement for the Local Gateway trunk protocol. Webex Calling registers the CUBE as a local gateway using SIP, not a proprietary alternative, so the trunk transports SIP messages directly.

Why this answer

The SIP trunk between the CUBE (Cisco Unified Border Element) and the Webex Calling cloud uses SIP (Session Initiation Protocol) for signaling. Webex Calling's Local Gateway architecture relies on SIP over TLS to establish and manage calls between on-premises CUBE and the Webex cloud. This is the standard protocol for Webex Calling PSTN connectivity.

Exam trap

CLCOR often tests protocol confusion — candidates pick H.323 or MGCP because they associate Cisco voice with those protocols, but Webex Calling cloud trunking is strictly SIP.

How to eliminate wrong answers

Option A is wrong because H.323 is a legacy ITU protocol used in older Cisco voice deployments; Webex Calling Local Gateway does not use H.323 for its cloud trunk. Option B is wrong because SCCP (Skinny Client Control Protocol) is a Cisco proprietary protocol for phone-to-call-manager signaling, not for cloud SIP trunking. Option C is wrong because MGCP is a gateway control protocol used between a call agent and media gateways, not for the CUBE-to-Webex cloud trunk.

Practice this question →

12

MCQmedium

You need to ensure that the Webex Hybrid Calendar service can access an Exchange 2019 environment. Which authentication method is recommended by Cisco for this deployment?

A.Digest Authentication

B.OAuth 2.0

C.Basic Authentication

D.Kerberos Constrained Delegation

AnswerB

OAuth 2.0 satisfies Cisco's requirement for Webex Hybrid Calendar against Exchange 2019, since on-premises deployments must use the Modern Authentication path rather than basic authentication, which Microsoft has deprecated. OAuth 2.0 delegates access via tokens issued by Microsoft Entra ID, enabling the calendar connector to read and write mailboxes without storing user credentials.

Why this answer

Cisco recommends OAuth 2.0 for Hybrid Calendar with Exchange 2019 because Microsoft has deprecated Basic Authentication for EWS and modern security baselines require token-based auth. OAuth 2.0 allows the Calendar Connector to authenticate via Azure AD app registration without storing user credentials. This is the supported and future-proof method for Exchange 2019 deployments.

Exam trap

CLCOR often tests authentication method recommendations, and candidates pick Basic or Kerberos because they are familiar with legacy Exchange setups, missing that Cisco explicitly recommends OAuth 2.0 for Exchange 2019.

How to eliminate wrong answers

Option A is wrong because Digest Authentication is a legacy HTTP auth mechanism not supported by Cisco for Hybrid Calendar and is not used with EWS in modern Exchange. Option C is wrong because Basic Authentication is deprecated by Microsoft for Exchange Online and strongly discouraged for Exchange 2019; Cisco no longer recommends it. Option D is wrong because Kerberos Constrained Delegation is an on-premises Windows auth model, not the method Cisco recommends for the Calendar Connector's cloud-mediated access to Exchange.

Practice this question →

13

MCQmedium

Which configuration in Control Hub allows you to define the emergency address for a user in a Webex Calling environment?

A.User Profile Settings.

B.Device Settings.

C.Organization Settings.

D.Location Settings.

AnswerD

Location Settings in Control Hub define the civic address and emergency (E911) details assigned to users and numbers. Configuring the location satisfies the requirement by binding each Webex Calling user to a validated emergency address.

Why this answer

In Webex Calling, emergency addresses are defined at the Location level in Control Hub. Each location has an associated emergency address that is used for emergency calls (e.g., 911). User profiles, device settings, and organization settings do not directly define emergency addresses; they inherit from the location.

The correct answer is D.

Exam trap

CLCOR often tests the hierarchy of settings in Control Hub, and candidates may incorrectly assume that emergency addresses are set at the user or device level. The trap is forgetting that emergency addresses are tied to locations, not individual users or devices.

How to eliminate wrong answers

Option A is wrong because user profile settings do not contain emergency address configuration; emergency addresses are assigned based on the user's location. Option B is wrong because device settings do not define emergency addresses; devices inherit the location's emergency address. Option C is wrong because organization settings are too broad and do not specify emergency addresses per user or location.

Practice this question →

14

MCQhard

A company has deployed Cisco Webex Hybrid Calendar Service with Exchange 2019 on-premises. Users report that scheduled Webex meetings are not appearing on their calendars, and the connector shows a 'Connected' status but no calendar events are being processed. Which action should be taken to resolve this issue?

A.Reinstall the Hybrid Calendar Service connector on the Expressway-C because the certificate may have expired.

B.Verify that the impersonation account has the required permissions to access user mailboxes and that the Exchange Web Services (EWS) URL is correctly configured.

C.Restart the Cisco Webex Hybrid Calendar Service connector service on the Expressway-C.

D.Change the Webex site URL in Control Hub to match the on-premises Exchange domain.

AnswerB

For Hybrid Calendar Service to process calendar events, the impersonation account must have the 'ApplicationImpersonation' role in Exchange and the EWS URL must be reachable and correctly configured in Control Hub. If these are misconfigured, the connector may show connected but fail to read or write calendar events. Checking these is the first step.

Why this answer

Hybrid Calendar Service relies on an impersonation account with ApplicationImpersonation rights and a correctly configured EWS URL. Even if the connector shows 'Connected', missing permissions or an incorrect EWS URL can prevent calendar processing. Verifying these settings ensures the connector can access mailboxes and process meeting invitations.

Exam trap

The trap here is assuming that a 'Connected' status means the service is fully functional, overlooking that underlying permissions or URL misconfigurations can cause silent failures.

Practice this question →

15

MCQeasy

Which component is required to synchronize users from an on-premises Active Directory to the Webex Cloud?

A.Cisco Directory Connector

B.Webex Calling Admin Console

C.Expressway-C

D.Cisco Webex HDS

AnswerA

Cisco Directory Connector runs on-premises, reads the Active Directory forest, and pushes user and group objects to Webex Control Hub via secure synchronisation. No other component bridges on-premises AD to the Webex Cloud, satisfying the stem's synchronisation requirement.

Why this answer

Cisco Directory Connector is the on-premises application that synchronizes users from Active Directory to Webex Cloud. It is specifically designed for directory synchronization in Webex Hybrid Services, ensuring user accounts are consistent between on-premises AD and the cloud.

Exam trap

CLCOR often tests the specific component names for hybrid services, and candidates may confuse Directory Connector with Expressway or other management consoles.

How to eliminate wrong answers

Option B is wrong because the Webex Calling Admin Console is for managing Webex Calling configurations, not for directory synchronization. Option C is wrong because Expressway-C is used for hybrid services connectivity (e.g., Calendar, Call, Message), not for AD user synchronization. Option D is wrong because Cisco Webex HDS (Hybrid Data Security) is for message encryption and compliance, not directory sync.

Practice this question →

16

MCQhard

A company is deploying Webex Hybrid Video Mesh to optimize media traversal for internal meetings. The administrator has deployed two Video Mesh nodes in a cluster. During testing, users on the internal network report poor video quality when joining meetings hosted by the Video Mesh nodes, while external users have good quality. What is the most likely cause?

A.The internal clients cannot reach the Video Mesh nodes due to firewall or routing issues.

B.The Video Mesh nodes are not configured with public IP addresses.

C.The Video Mesh cluster is not configured for high availability.

D.The Video Mesh nodes are not registered with Cisco Unified Communications Manager.

AnswerA

Internal clients need to be able to reach the Video Mesh nodes directly on the internal network. If firewall rules or routing configurations prevent this, clients will fall back to the Webex cloud for media, which can cause poor quality due to suboptimal paths or additional latency. This is a common misconfiguration when deploying Video Mesh, as internal clients must have direct IP connectivity to the Video Mesh nodes.

Why this answer

For Video Mesh to improve media quality, internal clients must have direct IP connectivity to the Video Mesh nodes. If firewall rules or routing prevent this, clients will use the Webex cloud for media, which may result in poor quality. Ensuring that internal clients can reach the Video Mesh nodes on the required ports is essential for optimal performance.

Exam trap

The trap here is assuming that Video Mesh nodes need public IP addresses or CUCM registration, when in fact they are internal components that require direct client connectivity.

Practice this question →

17

MCQeasy

A collaboration administrator needs to provide users with the ability to make and receive PSTN calls through Webex Calling without deploying any on-premises gateways or maintaining a separate carrier contract. Which Webex Calling PSTN option should the administrator choose?

A.Webex Edge for Calling

B.Cisco PSTN

C.Local Gateway

D.Cloud Connected PSTN (CCP)

AnswerB

Cisco PSTN is a cloud-delivered PSTN service from Cisco that provides local, long-distance, and emergency calling directly through the Webex Calling cloud. It requires no on-premises gateway and no separate carrier contract, so it perfectly matches the administrator's need for a completely cloud-based PSTN option.

Why this answer

Cisco PSTN is the only Webex Calling PSTN option that is entirely cloud-delivered by Cisco, with no on-premises gateway and no separate carrier contract needed. It provides dial tone, emergency calling, and number management directly through the Webex Calling cloud, making it the correct choice for an organization that wants to avoid on-premises PSTN infrastructure and additional carrier agreements.

Exam trap

The trap here is confusing Cloud Connected PSTN with Cisco PSTN, assuming that any cloud-based PSTN option eliminates the need for a separate carrier contract, when only Cisco PSTN is fully delivered by Cisco without a third-party carrier.

Practice this question →

18

Multi-Selectmedium

Which TWO of the following describe the purpose of the Webex Edge for Devices service?

Select 2 answers

A.Automatically provisions local gateways

B.Provides a SIP trunking gateway

C.Replaces the need for a web proxy

D.Enables hybrid registration (CUCM + Cloud)

E.Allows cloud-based management of on-premises registered devices

AnswersD, E

Webex Edge for Devices enables hybrid registration, letting on-premises CUCM-registered endpoints connect to Webex cloud services for calling, meetings and messaging without full cloud migration. This satisfies the stem's requirement by describing a genuine purpose: bridging existing CUCM infrastructure with cloud-delivered capabilities while preserving the on-premises call control deployment.

Why this answer

Option D is correct because Webex Edge for Devices enables hybrid registration, allowing endpoints to register to on-premises Cisco Unified Communications Manager (CUCM) while still consuming Webex cloud services such as Webex Meetings and Webex Calling. Option E is correct because the service provides cloud-based management and control of devices that remain registered on-premises, letting administrators manage them through Control Hub. Options A and B are incorrect because Webex Edge for Devices is not a local gateway provisioning tool nor a SIP trunking gateway; those functions belong to services like Cisco Unified Border Element (CUBE) or Webex Edge Connect.

Option C is incorrect because Webex Edge for Devices does not replace a web proxy; proxy requirements are handled separately by the organization's network and Webex Edge Connect design.

Exam trap

CLCOR often tests the two core purposes of Webex Edge for Devices (hybrid registration + cloud management), and candidates confuse it with gateway, proxy, or SIP trunking functions that belong to other services.

Practice this question →

19

Multi-Selecthard

Which THREE items are required to successfully register a room device to Webex?

Select 3 answers

A.A valid Webex Device license

B.A local SIP trunk

C.An existing CUCM registration

D.A valid activation code from Control Hub

E.An active internet connection

AnswersA, D, E

A valid Webex Device license is mandatory because Webex cloud enforces licensing at registration: the device's MAC address must be associated with a paid device entitlement before the RoomOS device can activate against Webex. Without it, registration fails authorisation, satisfying the stem's licensing constraint.

Why this answer

Option A is correct because registering a room device to Webex requires a valid Webex Device license assigned to the device in Control Hub, which authorizes the device to use Webex cloud services. Option D is correct because the device must be onboarded using a valid activation code generated from Control Hub, which the device uses to authenticate and complete registration. Option E is correct because the device needs an active internet connection to reach Webex cloud endpoints and complete the cloud registration process.

Options B and C are not required: a local SIP trunk and an existing CUCM registration are on-premises telephony concepts and are not prerequisites for Webex cloud device registration.

Exam trap

CLCOR often tests the misconception that a SIP trunk or CUCM registration is needed for Webex cloud registration — candidates confuse on-premises calling prerequisites with cloud onboarding requirements.

Practice this question →

20

MCQhard

A company uses Webex Hybrid Calendar Service. Users report that the 'Join' button is missing from their Webex Room devices for scheduled meetings. What is the most likely cause?

A.The Webex site is not integrated with the Control Hub

B.The Room device has not been registered to Webex

C.The Expressway-C does not have a public certificate

D.The user's Exchange mailbox is not assigned to the Hybrid Calendar service

AnswerD

Hybrid Calendar injects the Join button by pairing the user's Exchange mailbox with the service; if that mailbox is not assigned, meeting data never reaches Webex and the button is absent. This is the specific provisioning prerequisite the symptom points to.

Why this answer

The 'Join' button on Webex Room devices for scheduled meetings is provided by the Hybrid Calendar Service, which requires the user's Exchange mailbox to be assigned to the service. If the mailbox is not assigned, the device cannot retrieve calendar information, and the Join button will not appear.

Exam trap

The trap is assuming that the issue is with device registration or certificate problems, when the most common cause is a per-user configuration in Control Hub. Candidates must remember that Hybrid Calendar requires explicit assignment of mailboxes.

How to eliminate wrong answers

Option A is wrong because if the Webex site were not integrated with Control Hub, the device would not be registered or managed at all, but the issue is specific to the Join button. Option B is wrong because if the Room device were not registered to Webex, it would not function as a Webex device, but the question implies it is otherwise working. Option C is wrong because an Expressway-C public certificate issue would affect call signaling or registration, not specifically the calendar Join button.

Practice this question →

21

MCQmedium

You need to migrate users from an on-premises Cisco Unified Communications Manager (CUCM) to Webex Calling. Which tool allows for the bulk onboarding of users while maintaining existing directory synchronization?

A.Webex Edge for Devices

B.CUCM AXL API bulk exporter

C.CSV Template upload in Control Hub

D.Webex Migration Tool

AnswerC

Control Hub's CSV template bulk-adds users and maps them to existing directory-synchronised identities, satisfying the requirement to preserve directory synchronisation. It avoids manual per-user creation, letting large CUCM populations be onboarded efficiently into Webex Calling.

Why this answer

The CSV template upload in Control Hub is the supported bulk onboarding method for migrating users to Webex Calling while preserving directory synchronization. You export user data (often from Active Directory or CUCM), populate the Webex-provided CSV template with required fields, and upload it to Control Hub, which provisions users and links them to the existing directory sync (e.g., via Azure AD or Cisco Directory Connector). This maintains identity consistency across the migration.

Exam trap

CLCOR often tests the confusion between extraction tools (AXL/BAT) and onboarding tools (Control Hub CSV) — candidates pick the exporter thinking it also provisions, but extraction and onboarding are separate steps.

How to eliminate wrong answers

Option A is wrong because Webex Edge for Devices is a hybrid calling feature that lets on-premises registered devices connect to Webex services — it is not a user migration/onboarding tool. Option B is wrong because the CUCM AXL API bulk exporter extracts configuration data from CUCM but does not onboard users into Webex Calling or maintain directory sync. Option D is wrong because there is no product called 'Webex Migration Tool' in the Webex Calling migration path — the actual tools are Control Hub CSV templates, Directory Connector, and Webex Calling migration utilities, not a single branded 'Migration Tool'.

Practice this question →

22

MCQmedium

A company is deploying Webex Hybrid Directory Service to synchronize on-premises Active Directory users to Webex Control Hub. The administrator has installed the connector on a Windows Server 2019 machine and configured the required DNS SRV record. During the connector setup, the administrator is prompted to provide credentials for a service account. Which of the following must be true about this service account?

A.It must have read access to the Active Directory partitions containing the users to be synchronized.

B.It must be a member of the Enterprise Admins group to synchronize users across all domains in the forest.

C.It must be a member of the Domain Admins group in Active Directory.

D.It must be a Microsoft Exchange mailbox-enabled account with a valid SMTP address.

AnswerA

The Hybrid Directory Service connector uses the service account to read user objects from Active Directory and replicate them to the Webex cloud. Only read permissions on the relevant directory partitions are needed. Write permissions, Domain Admin rights, or Exchange-specific roles are unnecessary and would introduce unnecessary security risk.

Why this answer

The Hybrid Directory Service connector authenticates to Active Directory using a service account that must be able to read the directory partitions containing the users to be synchronized. No administrative write privileges or special group memberships are required. This least-privilege model ensures the connector can perform its synchronization task without exposing the environment to unnecessary risk.

Exam trap

The trap here is assuming that a directory synchronization service account requires elevated domain administrative rights, when in fact only read access to the relevant partitions is necessary.

Practice this question →

23

MCQhard

A collaboration engineer is configuring Webex Hybrid Call Service Connect to integrate an on-premises Cisco Unified Communications Manager (CUCM) cluster with Webex. The engineer has deployed Expressway-C and Expressway-E in the enterprise and has enabled the Hybrid Call Service Connector on the Expressway-C. After configuration, users in Webex Teams cannot place calls to on-premises CUCM-registered endpoints. Which of the following is the most likely cause?

A.The Expressway-C does not have a valid certificate trusted by CUCM for the SIP TLS connection.

B.The Webex Teams users have not been assigned the Webex Calling license.

C.The CUCM cluster is not configured with a SIP trunk to the Expressway-C.

D.The Expressway-E is not configured with a public IP address and cannot reach the Webex cloud.

AnswerA

Hybrid Call Service Connect uses SIP TLS between the Expressway-C and CUCM. If the Expressway-C certificate is not trusted by CUCM (or vice versa), the TLS handshake fails, and calls cannot be established. This is a common misconfiguration when certificates are self-signed or from an untrusted CA. Ensuring mutual certificate trust is essential for the SIP trunk to come up.

Why this answer

Hybrid Call Service Connect relies on a SIP TLS connection between Expressway-C and CUCM. For this connection to work, both sides must trust each other's certificates. If the Expressway-C certificate is not trusted by CUCM, the TLS handshake fails, and calls between Webex Teams and on-premises endpoints cannot be established.

Verifying and importing the correct certificates is a critical troubleshooting step.

Exam trap

The trap here is assuming that Webex Calling licenses are needed for Hybrid Call Service Connect, when in fact the service uses a different entitlement model and the issue is more likely a certificate trust problem.

Practice this question →

24

MCQeasy

Which license type is required to manage Webex Calling services in Control Hub?

A.Webex Meetings License

B.Webex Calling License

C.Webex Room Device License

D.Webex Messaging License

AnswerB

A Webex Calling licence is mandatory because Control Hub only exposes calling configuration—users, numbers, and PSTN settings—when that entitlement is assigned. Without it, the organisation appears as a Webex Meetings or Messaging customer, so the Calling tab and its management controls remain unavailable.

Why this answer

Managing Webex Calling services in Control Hub — configuring users, numbers, dial plans, and PSTN — requires a Webex Calling license assigned to the administrator and to the users being managed. The Webex Calling license is what entitles the organization to the calling service and unlocks the Calling configuration sections in Control Hub. Without it, the Calling tabs are unavailable or read-only.

Exam trap

CLCOR often tests the confusion between Webex service licenses (Meetings, Messaging, Calling, Room Devices), so candidates who pick Meetings or Messaging miss that only a Webex Calling license unlocks Calling management in Control Hub.

How to eliminate wrong answers

Option A is wrong because a Webex Meetings license grants meeting capabilities (scheduling, hosting) but does not entitle the user or admin to Webex Calling configuration in Control Hub. Option C is wrong because a Webex Room Device license is for registering room devices (Room Kit, Board) and does not grant calling service management rights. Option D is wrong because a Webex Messaging license covers messaging and spaces, not PSTN calling configuration.

Practice this question →

25

MCQmedium

You are configuring a Webex Calling environment for a customer that requires integration with an existing on-premises PBX using a Cisco Unified Border Element (CUBE). Which gateway type should you register to Webex Control Hub to enable this connectivity?

A.Cloud Connected PSTN Gateway

B.Local Gateway

C.Webex Edge Connect Gateway

D.Virtual Gateway

AnswerB

Registering a Local Gateway in Webex Control Hub provisions a premises-based gateway that connects Webex Calling to your on-premises PBX through the CUBE, satisfying the requirement for local PSTN or PBX integration rather than cloud-delivered connectivity.

Why this answer

Local Gateway is the correct answer because in Webex Calling, a Local Gateway is an on-premises CUBE (Cisco Unified Border Element) registered to Webex Control Hub that provides connectivity between Webex Calling and an existing on-premises PBX or PSTN. It is the specific gateway type designed for premises-based PSTN or PBX integration via CUBE. Registering the CUBE as a Local Gateway in Control Hub enables call routing between Webex Calling users and the on-premises PBX.

Exam trap

CLCOR often tests the confusion between Local Gateway (on-premises CUBE for PBX/PSTN integration) and Cloud Connected PSTN (service provider-hosted PSTN), causing candidates to pick the cloud option when the scenario explicitly mentions an on-premises CUBE.

How to eliminate wrong answers

Option A is wrong because Cloud Connected PSTN Gateway refers to a service provider-hosted PSTN connection delivered through the Cisco Cloud Connected PSTN program, not an on-premises CUBE integration with a PBX. Option C is wrong because Webex Edge Connect Gateway is a dedicated network connection (via Equinix Fabric or similar) for optimizing Webex traffic, not a gateway type for PBX integration. Option D is wrong because 'Virtual Gateway' is not a valid Webex Calling gateway type in Control Hub — the valid types are Local Gateway, Cloud Connected PSTN, and Webex Calling PSTN.

Practice this question →

26

MCQmedium

You are deploying Webex Calling with Local Gateway. Which component must be configured to allow PSTN connectivity for users who have migrated from on-premises CUCM to the cloud?

A.Webex Edge Connect

B.SIP Trunk via Local Gateway

C.Webex Calling Cloud Connected PSTN

D.Unified Border Element (CUBE) API

AnswerB

The Local Gateway registers to Webex Calling and connects to the PSTN through a SIP trunk, providing the required voice path for migrated users. Without that trunk configuration, the gateway has no carrier connectivity, so cloud-registered endpoints cannot place or receive external calls.

Why this answer

A SIP Trunk via Local Gateway must be configured because the Local Gateway (LGW) is the on-premises component that connects Webex Calling to the PSTN through a local SIP trunk, allowing migrated users to make and receive external calls. The LGW registers with Webex Calling and bridges cloud-registered endpoints to the on-premises PSTN provider. This is the required component for PSTN connectivity when using Local Gateway.

Exam trap

CLCOR often tests the distinction between cloud-connected PSTN (provider handles PSTN in the cloud) and Local Gateway (on-premises SIP trunk to local PSTN), so candidates pick the cloud option when the scenario specifies Local Gateway.

How to eliminate wrong answers

Option A is wrong because Webex Edge Connect is a dedicated private network connection between Webex and the customer's data center for quality and security, not the PSTN connectivity mechanism itself. Option C is wrong because Webex Calling Cloud Connected PSTN is a cloud-based PSTN option where Cisco or a partner provides the PSTN connection directly in the cloud — it does not use the on-premises Local Gateway. Option D is wrong because Unified Border Element (CUBE) API is not a Webex Calling PSTN connectivity component; CUBE is a Cisco IOS XE session border controller used in on-premises SIP trunking, and the API reference is a distractor.

Practice this question →

27

MCQmedium

A collaboration engineer is configuring a Webex Calling PSTN option where the enterprise wants to keep its existing Cisco Unified Border Element (CUBE) and SIP trunk contract with the incumbent carrier, while still using Webex Calling for call control and user features. Which Webex Calling PSTN connection type should the engineer select in Webex Control Hub?

A.Webex Edge for Calling

B.Cloud Connected PSTN (CCP)

C.Local Gateway

D.Cisco PSTN

AnswerC

Local Gateway is the Webex Calling PSTN option that registers an on-premises Cisco Unified Border Element (CUBE) or IOS-XE gateway to Webex Calling, allowing the enterprise to keep its existing SIP trunk contract and carrier while Webex Calling handles call control and features. This matches the scenario exactly, because the CUBE remains the PSTN demarcation point and only signaling is extended to the Webex cloud.

Why this answer

Local Gateway is designed for organizations that want to retain their own on-premises PSTN connectivity, including the existing CUBE and carrier SIP trunk, while adopting Webex Calling for users and features. The CUBE registers to Webex Calling and acts as the local PSTN gateway, so the enterprise keeps its carrier contract and gateway investment without deploying a cloud-connected provider or Cisco PSTN service.

Exam trap

The trap here is assuming that any Webex Calling PSTN option that involves a carrier automatically preserves the existing on-premises CUBE and SIP trunk contract, when only Local Gateway keeps that on-premises gateway in the call path.

Practice this question →

28

MCQmedium

Which service allows Webex users to see the presence status of an on-premises Jabber user?

A.Hybrid Presence Service.

B.Hybrid Calendar Service.

C.Webex Calling.

D.Directory Connector.

AnswerA

Hybrid Presence Service federates presence between Webex and on-premises Jabber deployments, allowing Webex users to view the presence status of Jabber users registered on-premises. It is the specific service providing this cross-deployment presence visibility, unlike messaging or directory connectors.

Why this answer

Hybrid Presence Service (also known as Webex Hybrid Presence) allows Webex users to see the presence status of on-premises Jabber users by connecting the on-premises IM and Presence Service to Webex. The service synchronizes presence between the on-premises Cisco IM and Presence cluster and Webex, so a Webex user can see whether a Jabber user is available, busy, or away. This is the specific service designed for cross-presence visibility.

Exam trap

CLCOR often tests the distinction between Hybrid Services — candidates confuse Hybrid Calendar (meetings), Directory Connector (user sync), and Hybrid Presence (status) — and pick the wrong service for presence visibility.

How to eliminate wrong answers

Option B is wrong because Hybrid Calendar Service connects calendars (Microsoft 365 or Google) to Webex for meeting scheduling and Join buttons — it does not handle presence. Option C is wrong because Webex Calling is a cloud calling service for PSTN and internal calls, not a presence federation service. Option D is wrong because Directory Connector synchronizes user directories between on-premises and Webex, but it does not provide presence status — it only ensures users exist in both systems.

Practice this question →

29

MCQmedium

A collaboration engineer is designing a Webex Hybrid Services deployment for an organization that requires all media to be processed on-premises while still using Webex Control Hub for user management and analytics. The organization has an existing Expressway-C and Expressway-E pair. Which Webex Hybrid service must be deployed to meet the requirement that all call signaling and media remain on-premises?

A.Webex Hybrid Data Security

B.Webex Hybrid Message Service

C.Webex Hybrid Call Service

D.Webex Hybrid Calendar Service

AnswerC

Hybrid Call Service keeps call signaling and media on-premises by using Expressway-C and Expressway-E to connect Webex App to the on-premises CUCM. It provides a cloud-based user experience while preserving on-premises call control and media handling, which directly satisfies the requirement that all media be processed locally.

Why this answer

Webex Hybrid Call Service is designed to connect Webex App users to on-premises CUCM for call control while keeping media on-premises through Expressway-C and Expressway-E. It enables a hybrid experience where users get cloud-based convenience but calls are processed locally. The other hybrid services address calendaring, messaging, or data security, not call signaling and media processing.

Exam trap

The trap here is confusing Hybrid Call Service with Hybrid Message Service or Hybrid Calendar Service, assuming that any hybrid service keeps all communication on-premises.

Practice this question →

30

MCQmedium

A collaboration engineer is designing a Webex Calling deployment for a company that requires all PSTN calls to egress through their existing on-premises Cisco Unified Border Element (CUBE) with a PRI circuit. The company wants to keep the PSTN gateway on-premises and use Webex Calling for internal and external calling. Which deployment option should the engineer choose?

A.Webex Calling with Cisco PSTN

B.Cloud Connected PSTN (CCP)

C.Local Gateway

D.Webex Edge Audio

AnswerC

Local Gateway is the correct choice because it allows Webex Calling to route PSTN calls through an on-premises CUBE or gateway, leveraging the existing PRI circuit. This option is designed for customers who want to retain their on-premises PSTN connectivity while using Webex Calling for call control. It supports the required egress through the local CUBE.

Why this answer

Local Gateway is the correct deployment option because it enables Webex Calling to route PSTN calls through an on-premises Cisco Unified Border Element (CUBE) or gateway, preserving the existing PRI circuit. This option is specifically designed for organizations that want to retain their on-premises PSTN connectivity while adopting Webex Calling for cloud-based call control and features.

Exam trap

The trap here is confusing Local Gateway with Cloud Connected PSTN, assuming that any PSTN option allows on-premises egress when only Local Gateway does.

Practice this question →

31

MCQmedium

When deploying Webex Hybrid Services, what is the purpose of the Expressway-C cluster?

A.To act as a firewall for all enterprise traffic.

B.To store all user messages on-premises.

C.To host the connectors that communicate with the Webex cloud.

D.To manage public DNS records for the organization.

AnswerC

The Expressway-C cluster sits inside the enterprise network and hosts the connectors (such as Calendar, Management, and Call Connector) that establish outbound connections to the Webex cloud, satisfying the hybrid services requirement for secure connector hosting.

Why this answer

The Expressway-C (Concentrator) cluster sits inside the enterprise network and hosts the various connectors (e.g., Calendar Connector, Call Connector, Management Connector, and the edge traversal pair) that establish secure outbound connections to the Webex cloud. It acts as the trusted on-premises endpoint that brokers hybrid service traffic between internal resources like CUCM, Exchange, and the Webex cloud.

Exam trap

CLCOR often tests the confusion between Expressway-C and Expressway-E roles, where candidates incorrectly assume Expressway-C is the internet-facing edge or a firewall component rather than the internal connector host.

How to eliminate wrong answers

Option A is wrong because Expressway-C is not a firewall; it is a traversal/connector server that works with Expressway-E to traverse the DMZ, and firewalls remain separate security appliances. Option B is wrong because user messages are stored in the Webex cloud (or on the messaging platform), not on the Expressway-C cluster, which handles signaling/connector functions rather than message storage. Option D is wrong because public DNS records are managed by the organization's DNS provider or Cisco's cloud infrastructure, not by Expressway-C, which handles internal-to-cloud connector communication.

Practice this question →

32

MCQmedium

You are configuring Webex Hybrid Message Service. What is the primary purpose of this service?

A.To provide external federation for IM users.

B.To enable messaging between on-premises IM&P users and Webex App users.

C.To archive all Webex messages to an on-premises server.

D.To synchronize user passwords with Active Directory.

AnswerB

Webex Hybrid Message Service connects the on-premises IM and Presence deployment with the Webex App cloud, letting users exchange messages across both environments. It satisfies the requirement to federate messaging rather than replace the existing IM&P infrastructure.

Why this answer

Webex Hybrid Message Service (Hybrid Message) connects an on-premises Cisco IM and Presence (IM&P) deployment with Webex App so users on both sides can exchange instant messages. It is a hybrid connector-based service that federates the on-prem XMPP infrastructure with the Webex cloud messaging fabric, allowing a phased migration where some users remain on-prem while others move to the cloud.

Exam trap

CLCOR often tests the confusion between Hybrid Message (on-prem to cloud IM bridging) and federation or archiving features, so candidates who pick 'external federation' miss the on-prem-to-cloud scope.

How to eliminate wrong answers

Option A is wrong because external federation for IM users is handled by Expressway or Webex federation features, not by Hybrid Message Service. Option C is wrong because message archiving to an on-premises server is a compliance/eDiscovery function typically handled by Webex Compliance or a third-party archiver, not Hybrid Message. Option D is wrong because password synchronization with Active Directory is handled by Cisco Directory Connector or SSO integration, not Hybrid Message Service.

Practice this question →

33

Multi-Selecthard

When troubleshooting Webex Calling, which THREE factors are critical for maintaining call quality over a hybrid network?

Select 3 answers

A.Quality of Service (QoS) tagging

B.Local database replication speed

C.Low round-trip time (latency)

D.Sufficient upload/download bandwidth

E.Hardware firewall bypass

AnswersA, C, D

Quality of Service tagging marks voice packets with DSCP values so routers and switches can prioritise them over bulk data across the WAN. This directly satisfies the hybrid network constraint, where traffic traverses both on-premises and cloud paths, keeping jitter and packet loss within acceptable bounds for Webex Calling media.

Why this answer

Option A (QoS tagging) is correct because marking voice RTP packets with DSCP values such as EF (46) lets routers and switches prioritize real-time media over bulk data, preventing jitter and packet loss during congestion. Option C (low round-trip time/latency) is correct because Webex Calling uses RTP over UDP, and excessive latency (generally above 150 ms one-way) causes talk-over and degraded interactivity that no amount of bandwidth can fix. Option D (sufficient upload/download bandwidth) is correct because each concurrent call consumes roughly 100 kbps per direction plus overhead, and insufficient throughput leads to dropped packets, choppy audio, and failed call setup.

Option B (local database replication speed) is not relevant because Webex Calling is a cloud service and does not depend on on-premises directory replication for media quality. Option E (hardware firewall bypass) is not a valid practice; firewalls should be properly configured with the correct ports and media traversal rather than bypassed, which would create security risks without guaranteeing call quality.

Exam trap

CLCOR often tests the factors affecting call quality, and candidates may select irrelevant options like database replication or firewall bypass due to misunderstanding of voice transport requirements.

Practice this question →

34

MCQeasy

Which dashboard in Control Hub provides insights into the quality and usage of hybrid services?

A.Device Dashboard

B.Troubleshooting Dashboard

C.Analytics Dashboard

D.Management Dashboard

AnswerC

The Analytics Dashboard in Control Hub aggregates hybrid service telemetry, showing call quality metrics and adoption trends across registered nodes. It satisfies the requirement for both quality and usage insight, which the troubleshooting and configuration views do not provide.

Why this answer

The Analytics Dashboard in Control Hub provides insights into quality and usage of hybrid services, including call quality, media statistics, and service adoption. It aggregates data from hybrid connectors and services to show trends and performance. This is the designated dashboard for hybrid service analytics.

Exam trap

CLCOR often tests whether candidates confuse the Analytics Dashboard with the Troubleshooting Dashboard, picking the latter for hybrid service insights when the question asks about quality and usage trends rather than live diagnostics.

How to eliminate wrong answers

Option A is wrong because the Device Dashboard focuses on device inventory, status, and management, not hybrid service quality and usage analytics. Option B is wrong because the Troubleshooting Dashboard is for diagnosing specific call issues, not for broad hybrid service insights. Option D is wrong because there is no 'Management Dashboard' in Control Hub that serves this purpose; management functions are spread across other sections.

Practice this question →

35

MCQeasy

A collaboration administrator needs to verify that the Webex Hybrid Services connectors are healthy and operational. Where in Cisco Webex Control Hub can the administrator check the status of the connectors?

A.Monitoring > Hybrid Services

B.Troubleshooting > Hybrid Services

C.Services > Hybrid Services

D.Users > Hybrid Services

AnswerA

In Control Hub, the Monitoring section includes Hybrid Services, where you can view the health and status of each deployed hybrid service connector. This page shows whether connectors are up, down, or in an error state. It is the central place to monitor the operational status of Hybrid Calendar, Message, Calling, and other services. This is the correct answer.

Why this answer

The health status of Webex Hybrid Services connectors is found under Monitoring > Hybrid Services in Control Hub. This dashboard provides a comprehensive view of each connector's status, including connectivity and any reported errors. Administrators use this page to quickly assess whether hybrid services are functioning correctly and to identify any components that require attention.

Exam trap

The trap here is confusing the configuration page (Services > Hybrid Services) with the monitoring page (Monitoring > Hybrid Services); the former is for setup, the latter for health status.

Practice this question →

36

MCQhard

An administrator is troubleshooting a failed Hybrid Calendar setup. The 'Connector' shows as 'Down' in Control Hub. What is the most likely reason?

A.The calendar integration license is invalid.

B.The Expressway-C host cannot reach the cloud over port 443.

C.The user's password expired.

D.The user is not in the correct group in Active Directory.

AnswerB

The Connector status reflects the Expressway-C's connection to the Cisco cloud. If outbound TCP 443 is blocked, the connector cannot register and shows Down, making this the most likely cause of the failed Hybrid Calendar setup.

Why this answer

The Hybrid Calendar Connector in Control Hub relies on the on-premises Expressway-C (or Cisco Webex Hybrid Services connector) maintaining an outbound TLS connection to Webex cloud endpoints over TCP 443. When that outbound path is blocked by a firewall, proxy, or DNS failure, Control Hub reports the connector status as 'Down' because the heartbeat to the cloud cannot be established. License, user password, and AD group issues would not cause the connector itself to show Down — they would affect calendar processing for individual users, not the connector health state.

Exam trap

CLCOR often tests whether candidates confuse connector health (cloud reachability over 443) with user-level provisioning issues like licensing, passwords, or AD group membership — the connector status reflects the tunnel, not the user.

How to eliminate wrong answers

Option A is wrong because an invalid calendar integration license would prevent specific users from being provisioned for Hybrid Calendar, but the connector's health status in Control Hub is driven by cloud reachability, not licensing. Option C is wrong because an expired user password affects that user's calendar authorization (OAuth token refresh), not the connector's up/down state in Control Hub. Option D is wrong because AD group membership determines which users are synced for calendar services, but a misconfigured group would not cause the connector itself to report Down.

Practice this question →

37

MCQeasy

An administrator is configuring Cisco Webex Hybrid Directory Service to synchronize users from an on-premises Active Directory to Webex Control Hub. The synchronization is not working, and the connector status in Control Hub shows 'Not Connected'. What is the most likely cause?

A.The Cisco Directory Connector service is not running or is not properly registered with Webex.

B.The Expressway-C certificate has expired.

C.The Active Directory domain controller is not reachable from the Expressway-C.

D.The Webex Control Hub administrator account does not have the 'Directory Synchronization' role.

AnswerA

The Cisco Directory Connector is a Windows service that synchronizes users from Active Directory to Webex. If the service is stopped or not registered correctly, the connector status in Control Hub will show 'Not Connected'. Ensuring the service is running and registered with the correct credentials is essential for synchronization.

Why this answer

Hybrid Directory Service uses the Cisco Directory Connector installed on a Windows server to synchronize Active Directory users to Webex. If the connector service is stopped or not registered, Control Hub will show 'Not Connected'. Checking the service status and registration is the first step to resolve synchronization issues.

Exam trap

The trap here is assuming that the Expressway-C is involved in directory synchronization, when in fact it is not used for Hybrid Directory Service.

Practice this question →

38

MCQmedium

A collaboration engineer is deploying Webex Hybrid Calling with Cisco Unified Communications Manager (CUCM) as the call control. The engineer wants to provide PSTN access to Webex Calling users by leveraging the existing on-premises Cisco IOS Voice Gateway. Which solution should be implemented?

A.Cisco Unified Communications Manager (CUCM) SIP trunk directly to Webex Calling

B.Cisco Expressway-E and Expressway-C pair for Mobile and Remote Access (MRA)

C.Cisco Unified Border Element (CUBE) with Local Gateway

D.Webex Calling PSTN calling plan from Cisco

AnswerC

Local Gateway (LGW) allows Webex Calling to route PSTN calls to an on-premises CUBE registered to Webex. This is the recommended hybrid PSTN option when an enterprise wants to retain its existing voice gateway and PSTN circuits. The CUBE acts as the Local Gateway, providing a secure SIP trunk between Webex Calling and the on-premises PSTN. It is a supported and common deployment for hybrid calling.

Why this answer

Local Gateway is the correct hybrid PSTN solution when an organization wants to use its own on-premises CUBE for PSTN connectivity while using Webex Calling for call control. It enables Webex Calling to send PSTN-bound calls to the on-premises CUBE, which then routes them to the PSTN. This preserves existing gateway investments and is a supported deployment option in Webex Control Hub.

Exam trap

The trap here is confusing Mobile and Remote Access (MRA) with hybrid PSTN connectivity; MRA is for endpoint registration, not for routing PSTN calls from Webex to an on-premises gateway.

Practice this question →

39

MCQmedium

What is the impact of removing a node from a Hybrid Video Mesh cluster that is currently hosting active meetings?

A.The node remains active until the last call ends

B.Active calls are dropped or experience disruption

C.The cloud takes over the media immediately

D.The meetings are automatically migrated to another node

AnswerB

Removing a node from a Hybrid Video Mesh cluster forces its hosted conferences to be redistributed or torn down. Because the node is actively serving media, those meetings drop or suffer disruption until participants reconnect via remaining nodes or the cloud.

Why this answer

Removing a node from a Hybrid Video Mesh cluster that is actively hosting meetings will cause active calls to be dropped or experience disruption. The node is immediately removed from the cluster, and any meetings hosted on it are not gracefully migrated, leading to service interruption. This is a known behavior in Cisco Webex Hybrid Video Mesh.

Exam trap

The trap is assuming that the system provides high availability with seamless failover for active meetings; candidates often think the cloud or another node will take over, but removal causes immediate disruption.

How to eliminate wrong answers

Option A is wrong because the node does not remain active until the last call ends; removal is immediate and does not wait for calls to finish. Option C is wrong because the cloud does not take over the media immediately; there is no seamless failover for active meetings. Option D is wrong because meetings are not automatically migrated to another node; they are disrupted and must be re-established.

Practice this question →

40

MCQmedium

You are deploying a Webex Room device in a hybrid environment. What is the benefit of registering it to Webex instead of on-premises CUCM?

A.It allows the device to function without an internet connection.

B.It enables full access to Webex cloud features like whiteboarding and AI-driven metrics.

C.It reduces the bandwidth required for video calls.

D.It forces the device to use on-premises media routing.

AnswerB

Registering to Webex gives the Room device native access to cloud-only capabilities such as whiteboarding and AI-driven metrics, which on-premises CUCM registration cannot deliver. This satisfies the hybrid deployment's requirement for full cloud feature parity.

Why this answer

Registering a Webex Room device to Webex (cloud) rather than on-premises CUCM unlocks the full Webex cloud feature set, including Webex Assistant, whiteboarding, AI-driven meeting metrics, and cloud-based management through Control Hub. Cloud registration also simplifies updates and provides native Webex Meetings join experience. On-premises CUCM registration limits the device to CUCM call control features and requires expressway/Collaboration Edge for cloud service access.

Exam trap

CLCOR often tests the misconception that cloud registration is only about call control; the real differentiator is access to Webex cloud-only features like whiteboarding and AI metrics, not bandwidth or offline capability.

How to eliminate wrong answers

Option A is wrong because cloud registration requires internet connectivity to reach Webex; it does not enable offline operation. Option C is wrong because registration method does not change the underlying media bandwidth — video codec and resolution determine bandwidth, not whether the device is registered to Webex or CUCM. Option D is wrong because cloud registration actually enables Webex cloud media routing (Webex Meetings), not on-premises media routing; forcing on-premises media is a CUCM/Expressway design choice.

Practice this question →

41

MCQmedium

When managing Webex Calling using the 'Webex Calling' app versus the 'Webex' app, what determines the calling capabilities?

A.The user's assigned license in Control Hub.

B.The firmware version of the desk phone.

C.The location of the user's home network.

D.The operating system of the device.

AnswerA

Calling capabilities are governed by the licence assigned to each user in Control Hub, not by which app interface they open. The Webex Calling app and Webex app both surface whatever telephony features that entitlement grants, so the licence is the determining factor.

Why this answer

In Webex Control Hub, the calling capabilities a user receives are determined by the license assigned to that user. A Webex Calling license (e.g., Professional or Standard) enables PSTN calling, voicemail, and enterprise features, while a Webex Meetings-only license does not. The app used (Webex Calling app vs.

Webex app) is just a client; the backend entitlement comes from the license. Therefore, the assigned license in Control Hub is the determining factor.

Exam trap

CLCOR often tests the misconception that the app or device determines calling features — candidates may pick firmware or OS, but the license is the true entitlement gate.

How to eliminate wrong answers

Option B is wrong because desk phone firmware affects device features but does not grant calling entitlements — a phone without a calling license cannot make PSTN calls. Option C is wrong because the user's home network location does not determine calling capabilities; it may affect quality but not entitlement. Option D is wrong because the device OS (Windows, macOS, iOS) only affects which client can be installed, not the calling features available.

Practice this question →

42

MCQhard

You are deploying Webex Hybrid Data Security (HDS). After deploying the virtual machines for the HDS nodes, you find they are not appearing in Control Hub. What is the first step you should take to troubleshoot the registration?

A.Disable the firewall on the HDS node.

B.Restart the Cisco Webex Hybrid Services host.

C.Check the local log files in the HDS node using the CLI.

D.Re-download the management certificate.

AnswerC

HDS nodes log registration attempts locally, so the CLI log files on the node reveal why Control Hub registration fails, such as connectivity, certificate or configuration errors. Checking them first establishes the actual failure cause before altering network or platform settings.

Why this answer

When HDS nodes do not appear in Control Hub, the first troubleshooting step is to check the local log files on the HDS node via the CLI. The logs will show whether the node successfully reached the Webex cloud, whether the registration token was accepted, and whether there are certificate or connectivity errors. This is the fastest way to identify the root cause before making configuration changes.

Exam trap

CLCOR often tests the tendency to jump to configuration changes (restart, re-download certificate, disable firewall) instead of first gathering evidence from local logs, which is the correct first troubleshooting step.

How to eliminate wrong answers

Option A is wrong because disabling the firewall is a security risk and is not a diagnostic step; the firewall may be the cause, but you should first confirm via logs which ports or destinations are failing. Option B is wrong because restarting the Cisco Webex Hybrid Services host is a broad action that may not address the underlying registration issue and could disrupt other services. Option D is wrong because re-downloading the management certificate is a specific fix that should only be done after logs confirm a certificate problem; it is not the first step.

Practice this question →

43

MCQmedium

You are configuring a local gateway for Webex Calling. Which mechanism ensures that the Webex Cloud can communicate with your on-premises edge device without requiring inbound firewall ports?

A.Webex Calling Connector via port forwarding

B.Outbound TLS connection from CUBE to Webex Cloud

C.SIP Trunk over VPN

D.H.323 Gatekeeper registration

AnswerB

CUBE initiates an outbound TLS connection to the Webex Cloud, which is kept open and reused for signalling and media. Because the connection originates from on-premises, no inbound firewall ports are required, satisfying the stated constraint.

Why this answer

The correct answer is B because Webex Calling uses a persistent outbound TLS connection from the on-premises CUBE (Customer Edge) to the Webex Cloud. This connection is initiated from the enterprise side, typically over TCP port 8934 (or 443 for some services), and is kept alive with keepalives. Because the connection is outbound, no inbound firewall ports need to be opened, and the cloud can send messages back over the established TLS session.

This design is fundamental to Webex Calling's cloud-to-edge architecture, ensuring secure and NAT-friendly connectivity.

Exam trap

CLCOR often tests the misconception that cloud services require inbound firewall ports, but Webex Calling specifically uses outbound TLS to avoid that, so candidates might incorrectly choose options that involve port forwarding or VPNs.

How to eliminate wrong answers

Option A is wrong because a Webex Calling Connector via port forwarding would require inbound ports to be opened on the firewall, which contradicts the requirement. Option C is wrong because a SIP Trunk over VPN would still require an inbound connection or a VPN tunnel that typically needs inbound ports to be opened for the tunnel establishment, and it is not the mechanism used for Webex Calling local gateway. Option D is wrong because H.323 Gatekeeper registration is a legacy protocol not used by Webex Calling, and it would require inbound signaling ports, not an outbound TLS connection.

Practice this question →

44

MCQhard

You are configuring Webex Hybrid Data Security (HDS). What is the purpose of the 'Key Management Service' (KMS) in this architecture?

A.To authenticate users against local Active Directory

B.To facilitate the storage of encrypted meeting recordings

C.To manage SIP signaling encryption

D.To allow the enterprise to maintain control over encryption keys

AnswerD

The Key Management Service holds and manages the encryption keys used by the HDS nodes, keeping key custody within the enterprise rather than with Cisco. This satisfies the requirement that the organisation retains control over its encryption keys.

Why this answer

In Webex Hybrid Data Security (HDS), the Key Management Service (KMS) is a customer-deployed component that stores and manages the encryption keys used to encrypt Webex content (messages, files, whiteboards). Its core purpose is to give the enterprise sole control over those keys, so Cisco cannot decrypt the content — this is the 'hybrid' data security promise. Thus, the correct answer is that KMS allows the enterprise to maintain control over encryption keys.

Exam trap

The trap here is confusing KMS with general encryption services — candidates may pick 'storage of encrypted recordings' because KMS sounds like it stores data, but it only manages keys, not content.

How to eliminate wrong answers

Option A is wrong because user authentication against Active Directory is handled by the Expressway/Connector and Webex Identity, not by KMS. Option B is wrong because KMS manages keys for encryption, but the storage of encrypted meeting recordings is handled by Webex storage services, not KMS itself. Option C is wrong because SIP signaling encryption (TLS) is managed by CUCM/Expressway certificates, not by the HDS KMS.

Practice this question →

45

Multi-Selectmedium

A collaboration engineer is deploying Cisco Webex Hybrid Message Service with Cisco Unified Communications Manager (CUCM) and Expressway-C. The requirement is to enable secure instant messaging and presence between on-premises CUCM users and Webex. Which two components are required for this deployment? (Choose two.)

Select 2 answers

A.Cisco Webex Meetings Server

B.Cisco Unified Border Element (CUBE)

C.Cisco Unified Communications Manager IM and Presence Service

D.Cisco Expressway-C with Hybrid Message Service connector

E.Cisco TelePresence Video Communication Server (VCS)

AnswersC, D

The IM and Presence Service on-premises is required to provide instant messaging and presence for CUCM users. The Hybrid Message Service connector integrates this on-premises service with Webex, allowing users to communicate with Webex users. Without it, there is no on-premises IM and presence to extend to the cloud.

Why this answer

Hybrid Message Service requires the Expressway-C with the Hybrid Message Service connector and the on-premises IM and Presence Service. The connector bridges the on-premises IM and Presence with Webex, enabling secure instant messaging and presence federation. Other components like Webex Meetings Server, VCS, or CUBE are not part of this architecture.

Exam trap

The trap here is confusing components from other hybrid services, such as CUBE for Edge Audio or VCS for video, when the question specifically asks for Hybrid Message Service requirements.

Practice this question →

46

MCQhard

A user is unable to receive incoming PSTN calls via a Webex Calling Local Gateway. You observe that the INVITE from the provider reaches the CUBE, but the CUBE sends a 403 Forbidden. What is the most likely cause?

A.The PSTN provider is using an unsupported codec

B.The incoming dial peer is missing or misconfigured

C.The Webex cloud is unreachable

D.The user's directory number is not in the PSTN white list

AnswerB

The CUBE matches inbound calls against incoming dial peers; if none matches the provider's INVITE, or the peer lacks the correct destination pattern and voice translation rules, call admission fails and the CUBE returns 403 Forbidden rather than routing to the Local Gateway.

Why this answer

A 403 Forbidden response from the CUBE indicates that the incoming INVITE is being rejected due to a dial peer mismatch. The incoming dial peer is responsible for matching incoming calls and applying the correct configuration; if it is missing or misconfigured, the CUBE cannot route the call and returns 403.

Exam trap

The trap is assuming that a 403 Forbidden is related to authentication or permissions, when in CUBE it often indicates a dial peer mismatch. Candidates might also confuse it with codec issues, but the SIP response code is the key differentiator.

How to eliminate wrong answers

Option A is wrong because an unsupported codec would typically result in a 488 Not Acceptable Here or 415 Unsupported Media Type, not 403 Forbidden. Option C is wrong because if the Webex cloud were unreachable, the call would not reach the CUBE at all, or the CUBE would fail to route to Webex, but the 403 is generated by the CUBE itself. Option D is wrong because a PSTN white list issue would usually cause a 404 Not Found or 403 from the provider, not from the CUBE after the INVITE has reached it.

Practice this question →

47

MCQmedium

A company has deployed Webex Hybrid Call Service Connect to allow Webex App users to make calls using their on-premises Cisco Unified Communications Manager (CUCM) infrastructure. Users report that they can see presence but cannot make calls. Which component should be checked first to ensure that call signaling is working?

A.Cisco Expressway-E

B.Cisco Unified Communications Manager IM and Presence Service

C.Expressway-C connector

D.Webex Hybrid Data Security

AnswerC

The Expressway-C connector is critical for Hybrid Call Service Connect because it handles call signaling between Webex and CUCM. If users can see presence but cannot make calls, the Expressway-C may not be properly registered or the call connector may be down. Checking its status and logs is the first step to isolate signaling issues.

Why this answer

The Expressway-C connector is the correct component to check first because it is responsible for call signaling between Webex and CUCM in Hybrid Call Service Connect. If it is not functioning, users may experience presence but cannot make calls. Verifying its status and logs will help identify signaling problems.

Exam trap

The trap here is assuming that presence and call signaling use the same path, but presence may work through a different service, so checking IM and Presence is misleading.

Practice this question →

48

MCQmedium

Which option allows a customer to keep their existing PSTN numbers while moving to Webex Calling?

A.Number aliasing.

B.Number forwarding.

C.Number porting.

D.Number provisioning.

AnswerC

Number porting transfers existing PSTN numbers from the current carrier to Webex Calling, preserving the digits users already know. This directly satisfies the requirement to keep existing numbers, unlike provisioning new numbers or forwarding, which would change them.

Why this answer

Number porting is the regulated process (governed by FCC/local authorities) that transfers an existing PSTN number from one carrier to another while preserving the number itself. When migrating to Webex Calling, the customer submits a port request with a Letter of Authorization (LOA) and recent bill so Cisco's carrier partner can pull the DIDs from the incumbent provider. This is the only option that actually moves ownership of the number rather than just redirecting or labeling it.

Exam trap

CLCOR often tests the distinction between moving a number (porting) versus redirecting or relabeling it (forwarding/aliasing), so candidates who pick 'forwarding' miss that ownership must transfer.

How to eliminate wrong answers

Option A is wrong because number aliasing only creates an additional label or alternate dial string that maps to an existing number — it does not transfer ownership from the current carrier. Option B is wrong because number forwarding simply redirects incoming calls to another destination while the original carrier still owns and bills the number, so the customer has not truly 'kept' it on Webex. Option D is wrong because number provisioning is the act of assigning new numbers from Webex's inventory, not migrating existing ones from an external carrier.

Practice this question →

49

MCQmedium

When troubleshooting a Hybrid Media Service node, which log file is most critical for determining if the media is being routed correctly to the cloud?

A.Hybrid Media Service logs

B.Cisco Discovery Protocol logs

C.System event logs

D.Call processing logs

AnswerA

Hybrid Media Service logs record call routing decisions between on-premises and cloud media paths, showing whether media is delivered to the correct cloud node. They directly satisfy the need to verify correct cloud routing during troubleshooting.

Why this answer

The Hybrid Media Service logs are the most critical for troubleshooting media routing issues because they contain detailed information about how the Hybrid Media Service node handles media streams, including routing decisions and errors. The correct answer is A.

Exam trap

CLCOR often tests the specific log files for different troubleshooting scenarios, and candidates may choose general logs like system event logs or call processing logs instead of the specialized Hybrid Media Service logs. The trap is not knowing which log provides the necessary media routing details.

How to eliminate wrong answers

Option B is wrong because Cisco Discovery Protocol logs are used for Layer 2 neighbor discovery and do not provide media routing details. Option C is wrong because system event logs are general OS logs and do not contain specific media routing information. Option D is wrong because call processing logs focus on call signaling, not media routing; they may show call setup but not the media path.

Practice this question →

50

MCQhard

A company is implementing Webex Edge Connect. They require a dedicated circuit. Who must they coordinate with to set up the physical connection?

A.The local Internet Service Provider only.

B.The Webex Control Hub automated provisioning tool.

C.Cisco Technical Support

D.A certified Cisco Webex Edge Connect partner.

AnswerD

Webex Edge Connect requires a dedicated circuit provisioned through a certified Cisco Webex Edge Connect partner, who coordinates the physical cross-connect into Cisco's peering fabric. Cisco does not order the circuit directly, so partner involvement satisfies the dedicated-connection requirement.

Why this answer

Webex Edge Connect is a dedicated, private connectivity option between a customer's network and the Webex cloud, delivered via a Cisco-certified partner that has direct peering into Cisco's Edge Connect locations. The physical cross-connect, BGP peering, and circuit turn-up must be coordinated with that certified partner because they own the interconnection into Cisco's data centers. Cisco does not sell the circuit directly, and the customer's local ISP alone cannot provision the private handoff into Webex.

Exam trap

CLCOR often tests the misconception that Cisco or the local ISP provisions the Edge Connect circuit, when in reality only a certified Webex Edge Connect partner can coordinate the physical connection.

How to eliminate wrong answers

Option A is wrong because a local ISP only provides internet transit — it cannot provision the private cross-connect into Cisco's Edge Connect peering fabric. Option B is wrong because Control Hub is a management plane for configuring services and does not perform physical circuit provisioning or BGP peering. Option C is wrong because Cisco TAC supports the Webex service itself, not the physical circuit installation or partner-side cross-connect.

Practice this question →

51

MCQeasy

Where in Webex Control Hub do you go to view the health status of all deployed Hybrid Services connectors?

A.Devices > Management

B.Analytics > Reports

C.Services > Hybrid

D.Users > Settings

AnswerC

The health status of all deployed Hybrid Services connectors is viewed under Services > Hybrid in Webex Control Hub. That page lists each connector, its cluster and its current state, letting administrators confirm whether on-premises components are running or degraded.

Why this answer

In Webex Control Hub, Hybrid Services connector health is monitored under Services > Hybrid. This section lists each connector (e.g., Calendar, Message, Directory, Call) and shows its status, version, and any alerts. Administrators use this page to verify connector registration, connectivity, and health.

Exam trap

CLCOR often tests Control Hub navigation by mixing up device management, analytics, and hybrid services; the trap is assuming connector health is under Devices or Analytics instead of Services > Hybrid.

How to eliminate wrong answers

Option A is wrong because Devices > Management is for device inventory and configuration, not hybrid connector health. Option B is wrong because Analytics > Reports provides usage and quality reports, not connector status. Option D is wrong because Users > Settings is for user account settings, not hybrid service monitoring.

Practice this question →

52

MCQeasy

What is the primary benefit of the 'Webex Edge' strategy?

A.It allows you to use your own cloud hosting.

B.It removes the need for user authentication.

C.It optimizes the quality and reliability of Webex traffic.

D.It eliminates the need for internet access.

AnswerC

Webex Edge connects your organisation's Webex services through dedicated peering into the Webex backbone, bypassing the public internet for media. This optimises quality and reliability of Webex traffic, which is the primary benefit the question asks for.

Why this answer

Webex Edge is a set of hybrid options that let enterprises leverage their existing on-premises infrastructure and network to improve the quality, reliability, and manageability of Webex traffic. By peering Webex traffic through the customer's own network or dedicated connections rather than the public internet, latency and jitter are reduced, and the customer gains visibility and control. It does not replace the Webex cloud — it optimizes how traffic reaches it.

Exam trap

CLCOR often tests the misconception that Webex Edge means hosting Webex yourself or removing authentication, when it actually means optimizing connectivity and hybrid integration with the Cisco cloud.

How to eliminate wrong answers

Option A is wrong because Webex Edge does not let customers host the Webex cloud themselves; the service still runs in Cisco's cloud. Option B is wrong because user authentication is still required and is typically handled via SSO or Control Hub identity management. Option D is wrong because Webex Edge still requires internet or private connectivity to reach the Webex cloud — it does not eliminate the need for connectivity.

Practice this question →

53

MCQeasy

A collaboration administrator is troubleshooting a Webex Hybrid Services deployment. The connector for Hybrid Calendar Service shows as 'Down' in Control Hub. The administrator has verified that the connector server has network connectivity to the internet. Which additional check should be performed first to resolve the connector status?

A.Reinstall the Webex App on all user devices.

B.Verify that the connector's service account credentials have not expired.

C.Check the Expressway-E certificate expiration date.

D.Restart the Cisco Unified Communications Manager service.

AnswerB

The connector uses a service account to authenticate with the Webex cloud. If the credentials expire or are changed, the connector cannot authenticate and will show as 'Down'. Checking and updating the service account credentials is a primary troubleshooting step for a down connector, especially when network connectivity is confirmed.

Why this answer

When a Hybrid Services connector shows as 'Down' and network connectivity is confirmed, the most common cause is an authentication issue. The connector uses a service account to connect to the Webex cloud; if those credentials expire or are incorrect, the connector cannot establish a session. Verifying and updating the credentials is the logical first step before investigating other potential causes.

Exam trap

The trap here is assuming that network connectivity is the only requirement and overlooking that the connector also depends on valid service account credentials.

Practice this question →

54

Multi-Selectmedium

Which TWO tasks must be performed when setting up Webex Hybrid Calendar service with Microsoft Exchange?

Select 2 answers

A.Create a dedicated DNS zone for Exchange

B.Configure a SIP trunk between Exchange and Webex

C.Install an H.323 gateway in the DMZ

D.Grant the service account ApplicationImpersonation rights

E.Enable the Hybrid Calendar service in Control Hub

AnswersD, E

ApplicationImpersonation lets the service account act on behalf of users to read and write their calendars, which the Hybrid Calendar connector requires for meeting scheduling. Without this Exchange role assignment, calendar operations fail despite correct Control Hub configuration.

Why this answer

Option D is correct because the Webex Hybrid Calendar service connects to Microsoft Exchange on-premises via Exchange Web Services (EWS) using a dedicated service account, and that account must be granted the ApplicationImpersonation management role so it can act on behalf of users to read and manage their calendar data. Option E is correct because the Hybrid Calendar service must be activated and configured in Control Hub (the Webex administrative portal), where you enable the service and supply the Exchange environment details and service account credentials that tie the on-premises deployment to the cloud service. Options A, B, and C are incorrect: no dedicated DNS zone for Exchange is required, Hybrid Calendar does not use a SIP trunk between Exchange and Webex, and no H.323 gateway in the DMZ is involved since the integration relies on HTTPS/EWS rather than telephony signaling.

Exam trap

CLCOR often tests the confusion between Hybrid Calendar (EWS/impersonation) and Hybrid Calling (SIP trunk), causing candidates to select SIP-related options for calendar questions.

Practice this question →

55

MCQeasy

Which protocol is required for the Webex Hybrid Directory Connector to communicate with on-premises Active Directory?

A.LDAP

B.XML

C.SIP

D.SNMP

AnswerA

The Webex Hybrid Directory Connector queries on-premises Active Directory using LDAP to synchronise user and group objects into the Webex cloud. LDAP is the native directory access protocol Active Directory exposes, satisfying the connector's requirement to read directory data from the on-premises domain controllers.

Why this answer

The Webex Hybrid Directory Connector synchronizes user data from on-premises Active Directory to the Webex cloud, and it uses LDAP (Lightweight Directory Access Protocol) to query and read directory information from Active Directory. LDAP is the standard protocol for accessing and maintaining distributed directory information services.

Exam trap

CLCOR often tests the protocol used for directory synchronization, and candidates may confuse LDAP with other protocols like SIP or XML due to the hybrid context.

How to eliminate wrong answers

Option B is wrong because XML is a markup language used for data representation, not a directory access protocol, and while it may be used in some API payloads, it is not the protocol for AD communication. Option C is wrong because SIP is a signaling protocol for VoIP and real-time communication, not for directory synchronization. Option D is wrong because SNMP is used for network management and monitoring, not for querying Active Directory.

Practice this question →

56

MCQhard

You notice high latency on calls placed through a Local Gateway. Which metric should you inspect in the Webex Control Hub to confirm the issue is with the network path?

A.Network latency and jitter.

B.Calling license usage.

C.User status.

D.Device firmware version.

AnswerA

Network latency and jitter metrics in Control Hub isolate the transport path between endpoints and the Local Gateway, distinguishing path degradation from application or media-processing faults, which is exactly what the stem asks you to confirm.

Why this answer

Network latency and jitter are key metrics that measure the quality of the network path. High latency indicates delay in packet delivery, while jitter measures variation in delay, both of which directly affect voice quality. Inspecting these metrics in Webex Control Hub can confirm if the issue is with the network path.

Exam trap

The trap is selecting metrics that seem related to call quality but are not network-related, such as license usage or firmware version. Candidates must focus on the specific symptom: high latency on calls, which points directly to network metrics.

How to eliminate wrong answers

Option B is wrong because calling license usage relates to licensing consumption, not network performance. Option C is wrong because user status indicates whether a user is available or busy, not network latency. Option D is wrong because device firmware version is about software compatibility, not real-time network conditions.

Practice this question →

57

MCQeasy

What is the purpose of the 'Webex Service' account in Active Directory when using Directory Connector?

A.To encrypt the synchronization traffic.

B.To read directory objects for synchronization.

C.To manage the user's email password.

D.To bypass the firewall.

AnswerB

The Webex Service account is granted read access to directory objects so Directory Connector can synchronise users and groups into Webex. This read-only permission satisfies the stem's synchronisation purpose, without granting write or administrative rights in Active Directory.

Why this answer

The Webex Service account in Active Directory is used by Directory Connector to read (bind and query) directory objects such as users, groups, and attributes for synchronization to Webex. It requires read permissions on the directory partitions being synced. This service account is the identity Directory Connector uses to authenticate to AD and pull the data needed for user provisioning.

Exam trap

CLCOR often tests the purpose of the AD service account — candidates confuse it with encryption or password management, missing that its sole role is read access for directory synchronization.

How to eliminate wrong answers

Option A is wrong because encrypting synchronization traffic is handled by TLS/SSL between Directory Connector and Webex, not by the service account, which is an AD identity. Option C is wrong because managing a user's email password is not the service account's role — Directory Connector does not manage passwords; it reads directory attributes. Option D is wrong because bypassing the firewall is a network configuration concern (ports/proxies), not something an AD service account can do.

Practice this question →

58

MCQmedium

A company has deployed Webex Hybrid Message Service to integrate its on-premises Cisco Unified Communications Manager IM and Presence Service with Webex. Users complain that their presence status is not updating in Webex when they change it in the on-premises Jabber client. The administrator confirms that the Expressway-C and Expressway-E are registered and that the Hybrid Message Service connector is running. Which component should the administrator verify next to ensure presence federation is working?

A.Cisco Unity Connection voicemail ports

B.Webex Control Hub user account license assignment

C.Cisco Unified Communications Manager IM and Presence Service SIP federation configuration

D.Cisco Expressway-C certificate trust store for HTTPS

AnswerC

Hybrid Message Service relies on SIP federation between the on-premises IM and Presence Service and the Webex cloud. If the SIP federation is misconfigured or the federation routing is not properly set up, presence updates will not be exchanged even though the connectors are healthy. Verifying the SIP federation configuration on IM and Presence is the logical next step to isolate the presence synchronization issue.

Why this answer

Hybrid Message Service uses SIP federation to connect the on-premises IM and Presence Service with the Webex cloud. Presence information flows over this federation, so if presence updates are not appearing, the SIP federation configuration on IM and Presence is the most likely culprit. The Expressway connectors and Hybrid Message Service connector only provide the transport and service registration; they do not replace the need for correct SIP federation settings.

Exam trap

The trap here is focusing on the hybrid connector health and overlooking that presence federation specifically requires SIP federation to be configured and operational on the on-premises IM and Presence Service.

Practice this question →

59

Multi-Selecteasy

Which TWO of the following are required components of a Cisco Local Gateway deployment? (Choose two)

Select 2 answers

A.An on-premises Active Directory server.

B.A Cisco Unified Border Element (CUBE).

C.A SIP trunk connecting to Webex Calling.

D.A dedicated fiber-optic internet connection.

E.A cloud-based PSTN provider.

AnswersB, C

A Cisco Unified Border Element provides the session border controller function that a Cisco Local Gateway deployment requires, interworking SIP signalling and media between the enterprise collaboration environment and the external PSTN or ITSP trunk. Without this demarcation and protocol-normalisation role, the Local Gateway cannot terminate or secure the external voice connection.

Why this answer

In a Cisco Local Gateway (LGW) deployment for Webex Calling, the Local Gateway itself is implemented on a Cisco Unified Border Element (CUBE), which provides the SIP normalization, media handling, and session border control between the enterprise voice network and Webex Calling — so option B is required. The Local Gateway must also be reachable over a SIP trunk that connects it to Webex Calling, since the LGW registers with and routes calls to the Webex Calling cloud via that SIP trunk, making option C required. Option A is not required because the Local Gateway does not depend on an on-premises Active Directory server; identity and user management reside in Webex Control Hub.

Option D is not required because any supported internet connection with adequate bandwidth and QoS can carry the SIP trunk, not specifically dedicated fiber. Option E is not required because the Local Gateway connects to Webex Calling for PSTN, not to a separate cloud-based PSTN provider.

Exam trap

CLCOR often tests component roles — candidates pick Active Directory or a cloud PSTN provider because they sound like 'required' enterprise components, missing that CUBE and the Webex Calling SIP trunk are the two mandatory LGW building blocks.

Practice this question →

60

Multi-Selecthard

Which THREE of the following items are verified during the Webex Hybrid Service connector installation? (Choose three)

Select 3 answers

A.The local PBX manufacturer.

B.Active Directory service account privileges.

C.User's home network speed.

D.Outbound HTTPS connection to the cloud.

E.SSL/TLS certificate trust chain.

AnswersB, D, E

The installer confirms the specified Active Directory service account holds the required privileges to read and synchronise directory objects for the hybrid service. Insufficient rights cause verification failure, satisfying the directory-access prerequisite checked during connector setup.

Why this answer

During the Webex Hybrid Service connector installation, the installer validates the Active Directory service account privileges (B) because the connector needs a properly privileged AD account to sync users and groups to the Webex cloud. It also verifies the outbound HTTPS connection to the cloud (D), since the connector must reach Webex services over TCP 443 for registration and ongoing communication. The SSL/TLS certificate trust chain (E) is checked as well, ensuring the connector trusts the cloud endpoint's certificate and can establish secure TLS sessions.

The local PBX manufacturer (A) is not verified by the connector installer, as it is irrelevant to connector prerequisites, and the user's home network speed (C) is not tested because the connector is a server-side component whose bandwidth requirements are not validated during installation.

Exam trap

The trap is selecting plausible-sounding but irrelevant items like PBX manufacturer or home network speed — the exam expects candidates to know that the connector validates AD privileges, cloud HTTPS reachability, and certificate trust, not physical PBX or user-side factors.

Practice this question →

61

MCQhard

When configuring Hybrid Call Service for Cisco Unified Communications Manager, which specific requirement must be met for the Expressway-C and Expressway-E pair?

A.They must be configured with a Unified Communications traversal zone.

B.They must use the same certificate authority as the CUCM nodes.

C.They must use a public IP address on the Expressway-C.

D.They must be in the same subnet.

AnswerA

The 'Unified Communications' traversal zone is mandatory for Hybrid Call Service interworking.

Why this answer

For Hybrid Call Service with Cisco Unified Communications Manager, the Expressway-C and Expressway-E pair must be configured with a Unified Communications traversal zone. This zone enables Mobile and Remote Access (MRA) by allowing signaling and media to traverse the firewall securely between the internal CUCM and external endpoints.

Exam trap

CLCOR often tests the misconception that Expressway-C needs a public IP or that both nodes must be in the same subnet, when in fact Expressway-C is internal and Expressway-E is in the DMZ with a public IP.

How to eliminate wrong answers

Option B is wrong because while certificates are important for trust, the Expressway pair does not need to use the same certificate authority as CUCM nodes; they can use different CAs as long as trust is established. Option C is wrong because Expressway-C is deployed in the internal network and does not require a public IP address; only Expressway-E needs a public IP for external connectivity. Option D is wrong because Expressway-C and Expressway-E are typically deployed in different network segments (internal vs.

DMZ), not the same subnet.

Practice this question →

62

MCQhard

An administrator is deploying Webex Hybrid Calendar Service with an on-premises Microsoft Exchange 2019 environment. Users report that their Webex meetings are not being automatically added to their Outlook calendars. The administrator has already verified that the Expressway-C and Expressway-E connectors are registered and healthy in Control Hub. Which additional component must be installed and configured to enable the calendar integration?

A.Webex Hybrid Calendar Service connector (Calendar Connector) on a Windows server

B.Webex Hybrid Media Service node on the Expressway-C

C.Cisco Directory Connector on a domain-joined Windows server

D.Cisco Expressway-E with a public TLS certificate

AnswerA

The Calendar Connector is a separate on-premises component that communicates with the Exchange environment to read and write calendar items, and it registers with the Webex cloud to enable Hybrid Calendar Service. Even when Expressway connectors are healthy, the Calendar Connector is required for Exchange integration, so its absence explains why meetings are not appearing in Outlook calendars.

Why this answer

Hybrid Calendar Service requires a dedicated Calendar Connector to integrate with the on-premises Exchange environment. The Expressway pair handles secure connectivity to the Webex cloud, but the Calendar Connector is the component that actually reads and writes Exchange calendar data to insert Webex meeting details. Without it, meetings will not appear on users' Outlook calendars even if the Expressway connectors are healthy.

Exam trap

The trap here is assuming that healthy Expressway connectors are sufficient for all hybrid services, when each hybrid service such as Calendar requires its own dedicated on-premises connector.

Practice this question →

63

MCQmedium

In a Webex hybrid environment, what is the primary role of the Expressway-C?

A.To manage public DNS records

B.To act as a SIP proxy for internal phones

C.To provide a secure connector for Hybrid Services

D.To replace the CUCM server

AnswerC

Expressway-C establishes outbound-only connections to Webex cloud services, so no inbound firewall ports are opened. This satisfies the hybrid constraint: it registers and proxies on-premises resources—call connectors, calendar connectors, messaging—through a secure tunnel, with Expressway-E handling external traversal. That connector role is its primary function in hybrid deployments.

Why this answer

Expressway-C is deployed inside the enterprise network and acts as the secure connector that initiates outbound-only connections to Expressway-E, which then relays traffic to Webex cloud services. This connector role is what enables Hybrid Services (Calendar, Message, Directory, Management, Call) to traverse the firewall without inbound pinholes. It does not manage DNS or replace CUCM; it is purely a traversal/connector component in the hybrid architecture.

Exam trap

CLCOR often tests the distinction between Expressway-C (internal secure connector) and Expressway-E (DMZ traversal server), causing candidates to confuse the two roles or assume Expressway-C handles DNS/SIP duties it does not own.

How to eliminate wrong answers

Option A is wrong because public DNS records are managed by the organization's DNS provider or Cisco Webex's cloud DNS, not by Expressway-C. Option B is wrong because while Expressway-C can proxy SIP for Mobile and Remote Access (MRA) registrations, its primary role in the Hybrid Services context is the secure connector, not a generic SIP proxy for internal phones. Option D is wrong because CUCM remains the on-premises call control; Expressway-C never replaces CUCM—it complements it by brokering hybrid service traffic.

Practice this question →

Ready to test yourself?

Try a timed practice session using only Cloud And Hybrid Services questions.

Start 20-question session