Video Infrastructure Implementation Free Sample Questions

For active calls to be preserved during an Expressway peer failure, the 'Call preservation' feature must be explicitly enabled on the zones involved in the call path. This feature allows signaling to be re-established through an alternate peer without dropping the media session. While NTP sync is critical for cluster health and manual replication is a valid mode, neither directly addresses the preservation of active calls during a failover event. The failover license is for MRA, not general call preservation.

The correct regex pattern is (\d{10})@cisco\.com. (\d{10}) captures a group of exactly 10 digits. The . in cisco.com must be escaped with a backslash (\.) to be treated as a literal dot. The replace string \1 refers to the first captured group (the 10-digit number), effectively stripping the domain. The other options are incorrect: \0 refers to the entire matched string, (.*) is too broad, and \2 would refer to a second captured group which doesn't exist in that pattern.

For database redundancy in a large-scale CMS deployment, a three-node (or five-node) database cluster is required to maintain quorum and handle failover. A single database is a single point of failure. A load balancer is essential for distributing traffic across the Call Bridges.

To achieve scalability for 2,000 calls, multiple Call Bridge nodes are necessary. An external load balancer (like F5 or Citrix ADC) is required to distribute the incoming call load efficiently and evenly across these nodes.

Cisco TMS provides granular, role-based access control (RBAC). To restrict a user's permissions to a specific folder, you must create a user group, assign the necessary permissions (like 'Booking'), and set the scope of those permissions to 'Folder'. The administrator would then be granted access only to the specific folder(s) assigned to that group. Default groups have global scope, and user-level permissions override group settings but are harder to manage.

The Cisco Hybrid Calendar Service is responsible for integrating on-premises Microsoft Exchange (or Office 365) with the Webex cloud to enable features like @webex scheduling. This service is enabled by deploying the Calendar Connector software on the Expressway-C, which then communicates with the Exchange environment and the Webex cloud. The Directory Connector is for user synchronization, TMSXE is for TMS scheduling, and Expressway-E provides traversal but does not host the connector.

This classic one-way video scenario in a hybrid deployment points to a firewall issue. The on-premises endpoint can send its media (outbound UDP) to the Webex cloud, so cloud participants can see it. However, the media from the cloud participants (inbound UDP) is being blocked by the external firewall before it can reach the Expressway-E and be relayed to the on-premises endpoint. Ensuring the Webex cloud's IP address ranges are allowed for inbound UDP traffic to the Expressway-E is the correct solution.

In Expressway's Call Admission Control (CAC) model, a 'pipe' represents a network link and is used to define the total amount of bandwidth available between two locations (subzones or zones). When a call is placed between these locations, Expressway checks if there is sufficient bandwidth remaining in the pipe. If not, the call is rejected. This prevents oversubscription of the physical network link and ensures call quality.

This statement is true. The Web Bridge component of Cisco Meeting Server is stateless and can be deployed behind a standard load balancer for high availability and scalability. Its clustering is independent of the stateful Call Bridge cluster, which requires more complex peering and database replication for resilience.

The most efficient and scalable method is to use Configuration Templates in TMS. An administrator can define all the required security settings in a single template and then apply it to individual systems, folders, or the entire system tree. TMS will then automatically provision the endpoints with these settings and can be configured to periodically check for and correct any configuration drift, ensuring compliance.

To interact with Webex APIs, every application, including a bot, must be registered in the Webex for Developers portal (developer.webex.com). This registration process generates a unique Bot Access Token. This token must be included in the authorization header of every API request the bot makes, authenticating it to the Webex cloud and granting it permissions based on its defined scopes.