Your supervisor has asked you to configure a Cisco TelePresence Conductor with 50 registered MCUs in order
to provide dynamic cascading of ad hoc conferences.
Why will your supervisor’s plan not work?

A.
A Conductor cluster is required to support 50 MCUs.

B.
A Conductor or Conductor cluster supports a maximum of 30 MCUs.

C.
Conductor does not support dynamic cascading.

D.
Conductor does not support ad hoc conferences.

Explanation:
A Conductor or Conductor cluster supports a maximum of 30 multipoint control units (MCUs). Cisco
TelePresence Conductor manages conference functions for TelePresence Servers that operate in remotely
managed mode. An MCU is used primarily to connect Session Initiation Protocol (SIP) or H.323 single-screen
endpoints into virtual meeting rooms. Optimally, all participants in a conference will be connected to a single
MCU. However, when there are not enough ports on an MCU for all of the participants, the MCU can cascade
to another MCU in order to handle the load.
Conductor supports only ad hoc conferences; it does not support scheduled conferences. Ad hoc conferences
include auto attendant conferences, rendezvous conferences, and Multiway conferences; however, only
rendezvous conferences and Multiway conferences are supported on Conductor.
Conductor supports dynamic cascading. With dynamic cascading, MCUs are added as they are needed.
Statically configured cascading is available only with Cisco TelePresence Video Communication Server (VCS).
Cisco: Cisco TelePresence MCU 45X0, 53X0 and MCU MSE 8510, Cisco TelePresence Deployment Guide:
Deploying an MCU with Cisco TelePresence Conductor (PDF)