Cisco Spark is a cloud-based collaboration platform that allows users to create, share, and communicate with each other through messaging, calling, and meeting features. Cisco Spark can be integrated with an on-premises solution using hybrid connectors, which are software applications that securely connect Cisco Spark to the organization’s premises or to the Cisco Hosted Collaboration Solution (HCS) in a partner cloud. The hybrid connectors enable integration with Cisco Spark for various services, such as calendar, call, directory, media, and serviceability.  1 2 3 4 5 , three hybrid connectors that allow Cisco Spark to be integrated with an on-premises solution are:

Calendar Connector: This connector allows users to schedule and join Webex meetings from their Microsoft Exchange or Google Calendar. It also enables features such as One Button to Push (OBTP) and Personal Meeting Room (PMR) for Cisco video devices. The Calendar Connector runs as an application within Cisco Expressway or Enterprise Compute Platform (ECP).

Call Connector: This connector allows users to make and receive calls from their Cisco Spark app using their existing phone system, such as Cisco Unified Communications Manager or Cisco HCS. It also enables features such as single number reach, call control, and call history. The Call Connector runs as an application within Cisco Expressway or ECP.

Directory Connect: This connector allows users to synchronize their user directory from their on-premises Active Directory or LDAP server to Cisco Spark. It also enables features such as user search, user profile, and user activation. The Directory Connect runs as an application within Cisco Expressway or ECP.

The other options, such as Calendar Aware, Directory Service, and Calendar Service, are not hybrid connectors for Cisco Spark. Calendar Aware is a feature that allows users to see the availability of other users based on their calendar status. Directory Service is a feature that allows users to search and view the contact details of other users. Calendar Service is a feature that allows users to schedule and join meetings from their Cisco Spark app. These features are enabled by the hybrid connectors, but they are not connectors themselves.  References  :=  Cisco Spark Hybrid Services Data Sheet Cisco Spark Hybrid Services - Cisco Deployment guide for Hybrid Calendar - Deploy Expressway-based Hybrid Calendar for Microsoft Exchange Deployment guide for Hybrid Call Service - Deploy Expressway-based Hybrid Call Service Deployment guide for Hybrid Directory Service - Deploy Expressway-based Hybrid Directory Service

= The scaled and resilient server deployment model is the best solution to accommodate fail-over for Cisco Meeting Server. This model involves deploying multiple Meeting Servers clustered together to provide greater scale and resilience in the deployment. The cluster can span across different locations and support up to 2500 HD ports. The cluster can also handle the failure of one or more servers without affecting the ongoing conferences or the user experience.  The cluster uses a load balancer to distribute the incoming calls among the available servers, and uses a database replication mechanism to synchronize the conference state and configuration across the servers 1 2 3   References  :=  1 Cisco Meeting Server - Configuration Guides   2 Cisco Meeting Server 3.8, Scaled and Resilient Server Deployment Guide   3 Cisco Meeting Server 3.8, White Paper on Load Balancing Calls Across Cisco Meeting Servers

= The Cisco Meeting Server uses a RESTful API to interact with the server. The API commands are sent via HTTP requests to the web admin service, which processes them and returns the response. The four basic API commands are GET, POST, PUT, and DELETE.  Each command has a different function and syntax, as explained below 1 2 :

GET: Retrieves existing information from the server. The syntax is  GET /api/v1/ < object > / < id >  where  < object >  is the type of object to retrieve, such as call, participant, space, etc., and  < id >  is the unique identifier of the object, such as a UUID or a name. For example,  GET /api/v1/calls/12345678-1234-1234-1234-123456789012  will return the information about the call with the specified UUID.

POST: Creates new information on the server. The syntax is  POST /api/v1/ < object >  where  < object >  is the type of object to create, such as call, participant, space, etc. The request body contains the attributes and values of the object to create, in JSON format. For example,  POST /api/v1/spaces  with the request body  {"name": "Test Space", "uri": "test@domain.com"}  will create a new space with the specified name and URI.

PUT: Modifies existing information on the server. The syntax is  PUT /api/v1/ < object > / < id >  where  < object >  is the type of object to modify, such as call, participant, space, etc., and  < id >  is the unique identifier of the object, such as a UUID or a name. The request body contains the attributes and values of the object to modify, in JSON format. For example,  PUT /api/v1/spaces/12345678-1234-1234-1234-123456789012  with the request body  {"name": "New Name"}  will change the name of the space with the specified UUID to “New Name”.

DELETE: Deletes existing information from the server. The syntax is  DELETE /api/v1/ < object > / < id >  where  < object >  is the type of object to delete, such as call, participant, space, etc., and  < id >  is the unique identifier of the object, such as a UUID or a name. For example,  DELETE /api/v1/spaces/12345678-1234-1234-1234-123456789012  will delete the space with the specified UUID.

In this question, the API command that is used to modify a configuration setting on the Cisco Meeting Server is PUT, as it allows changing the attributes and values of an existing object on the server.

References  :=  Cisco Meeting Server Basic API Functions ,  Cisco Meeting Server - Programming Guides

The Expressway solution can be peered with a Cisco Unified Communications Manager to allow for greater capabilities.  This is true because the Expressway-C can connect to the Unified CM via a SIP trunk or a line-side connection, and the Expressway-E can enable firewall traversal and business-to-business communications for the Unified CM endpoints 1 2 .

The Expressway series can never operate as a standalone call-control solution.  This is false because the Expressway series can act as a standalone call-control solution for SIP and H.323 endpoints, and can provide interworking between them 1 3 .

The Expressway series requires the peering with a Cisco Unified Communications Manager to act as a call-control device.  This is false because the Expressway series does not depend on the Unified CM for call-control functionality, although it can enhance the Unified CM capabilities when peered with it 1 3 .

The Expressway series may operate as a standalone call-control solution.  This is true because the Expressway series can support SIP and H.323 endpoints without requiring the Unified CM, and can also provide session management and interworking features 1 3 .

The Expressway series only supports SIP-based communications.  This is false because the Expressway series supports both SIP and H.323 protocols, and can interwork between them 1 3 .  References  :=  1 :  Cisco Expressway Administrator Guide (X14.0) - Introduction   2 :  Cisco Expressway Administrator Guide (X15.0) - Unified Communications   3 :  Concept of Zones Demystified On Cisco Expressway Series

A  cluster  is a group of servers or nodes that work together to provide high availability, scalability, and load balancing for applications and services 1 .

Network latency  is the time it takes for a packet of data to travel from one point to another on a network 2 .  It is usually measured in milliseconds (ms) and can be affected by various factors, such as distance, bandwidth, congestion, and routing 2 .

The  maximum network latency allowed between peers in a cluster  depends on the type and configuration of the cluster, as well as the application and service requirements.  Different cluster solutions may have different latency thresholds and recommendations for optimal performance and stability 3 4 5 .

one of the common cluster solutions that has a maximum network latency requirement is the  Windows Server Failover Clustering (WSFC) 3 .  WSFC is a feature of Windows Server that enables servers to work together to provide continuous service for applications and services, such as SQL Server, Exchange Server, and Hyper-V 3 .

According to the Microsoft documentation, the maximum network latency allowed between peers in a WSFC cluster is  100 ms one way 3 . This means that the round-trip latency between any two nodes in the cluster should not exceed 200 ms.  This requirement applies to both the private and public network connections between cluster nodes, and is based on the assumption that the network is reliable and stable 3 .

The other options are incorrect because:

A. 30 ms total is too low for a realistic network latency requirement between peers in a cluster.  It is unlikely that any network can consistently provide such a low latency across different locations and conditions 2 .

B. 300 ms total is too high for a network latency requirement between peers in a cluster.  It is likely that such a high latency would cause performance degradation, timeouts, and failures for applications and services that rely on the cluster 2 .

D. 150 ms one-way is also too high for a network latency requirement between peers in a cluster.  It would imply a round-trip latency of 300 ms, which is above the threshold for WSFC and other cluster solutions 3 4 5 .

References  :=  1 : What is a Cluster?  2 : What is Network Latency?  3 :  Windows clustering and geographically separate sites   4 :  Cluster Network Latency - Troubleshooting Guide   5 :  Support Policies for RHEL High Availability Clusters - Cluster …

An endpoint registration request message that is sent to a SIP Server contains the following two options 1 :

E.164 address: This is the telephone number of the endpoint, which is used to identify the endpoint in the SIP domain. The E.164 address is also known as the Address of Record (AOR), which is a high-level name that is assigned to a SIP entity without regard to the device or devices that name might use. The format for an AOR is sip:user@domain (e.g.  2025551234@sip.plivo.com) 2 .

SIP URI: This is the location of the endpoint, which is identified by an IP address, port number and protocol. The SIP URI is used to reach the endpoint for establishing a media session. The format for a SIP URI is sip:user@host:port;transport (e.g.  sip:2025551234@192.168.1.120:5060;udp) 1 .

The other options are not correct because:

SIP Server IP address: This is not included in the endpoint registration request message, as the endpoint already knows the IP address of the SIP Server to which it is sending the message.  The SIP Server IP address is usually configured in the endpoint settings as the Registration Domain or the Outbound Proxy 3 .

Endpoint IP address: This is not included in the endpoint registration request message, as it is already part of the SIP URI.  The endpoint IP address is the host part of the SIP URI, which indicates the location of the endpoint 1 .

E.164URI: This is not a valid option, as there is no such thing as an E.164URI.  The E.164 address is not a URI, but a telephone number that is used to identify the endpoint in the SIP domain 2 .

References  :=  1 : Cisco Unified Communications System 9.0 SRND - SIP Infrastructure  2 : SIP signalling- the registration process and setting up a SIP call  3 : Programmable Voice - SIP Registration | Twilio

 Microsoft Skype for Business (S4B) interoperability with Cisco Meeting Server (CMS) allows S4B users to join CMS meetings and vice versa. Chat can be used between S4B and Cisco Meeting App (CMA) users, as both support the SIP SIMPLE protocol for instant messaging. However, chat cannot be used between S4B and Cisco Meeting Server Spaces, as Spaces do not support chat functionality. Calls can be placed between S4B and CMA users, as both support the H.264 video codec and the Opus audio codec. Local directories can be used between S4B users and CMA, but only if the CMA is configured to use the same domain as the S4B server.  References :  Configure Cisco Meeting Server and Skype for Business ,  Plan for Video Interop Server in Skype for Business Server ,  Deploy Video Interop Server in Skype for Business Server

 A template is being persistently pushed to the endpoint from TMS. This is because TMS, or Cisco TelePresence Management Suite, is a software application that enables centralized management of Cisco video conferencing and collaboration devices and systems.  TMS can use templates to configure and update multiple endpoints with the same settings, such as alias information, network settings, security settings, and so on 1 .  If a template is applied to an endpoint, any manual changes made to the endpoint will be overwritten by the template settings the next time the template is pushed by TMS 2 . Therefore, if an administrator notices that the alias information changes revert back to their original state the following day, it is most likely that a template is being persistently pushed to the endpoint from TMS.

The other options are not correct because:

The changes are not being saved properly on the endpoint: This is not likely, as the changes are successful and visible on the endpoint until the next day.  If the changes were not saved properly on the endpoint, they would not take effect at all or would be lost after a reboot or power cycle of the endpoint 3 .

A template is being pushed persistently to the endpoint from the Expressway: This is not possible, as the Expressway does not support pushing templates to endpoints. The Expressway is a network device that provides firewall traversal, NAT, and encryption services for video communications. The Expressway does not have the capability to configure or update endpoints with templates.

The alias information of the endpoint is duplicated on another endpoint: This is not relevant, as the alias information of the endpoint is not affected by the alias information of another endpoint. The alias information is a unique identifier for the endpoint that is used for registration and dialing purposes. The alias information of another endpoint does not overwrite or interfere with the alias information of the endpoint in question.

References  :=  1 : Cisco TelePresence Management Suite Administrator Guide (15.16) - Templates [Cisco TelePresence Management Suite] - Cisco  2 : Cisco TelePresence Management Suite Administrator Guide (15.16) - Applying Templates [Cisco TelePresence Management Suite] - Cisco  3 : Cisco TelePresence Management Suite Administrator Guide (15.16) - Configuring Endpoints [Cisco TelePresence Management Suite] - Cisco : Cisco Expressway Basic Configuration Deployment Guide (X12.6) - Introduction [Cisco Expressway Series] - Cisco : Cisco Expressway Basic Configuration Deployment Guide (X12.6) - Registering Aliases [Cisco Expressway Series] - Cisco

 TMS, or Cisco TelePresence Management Suite, is a software application that enables centralized management of Cisco video conferencing and collaboration devices and systems.  TMS relies on the following two operating systems and database applications 1 :

Windows Server: TMS requires a Windows Server operating system to run.  The supported versions are Windows Server 2019, 2016, and 2012 R2 2 .

SQL: TMS requires a SQL database application to store and manage data.  The supported versions are SQL Server 2019, 2017, 2016, and 2014 2 .

The other options are not correct because:

Oracle: TMS does not support Oracle as a database application.  TMS only supports SQL Server as a database application 2 .

MS Access: TMS does not support MS Access as a database application.  TMS only supports SQL Server as a database application 2 .

Linux Ubuntu: TMS does not support Linux Ubuntu as an operating system.  TMS only supports Windows Server as an operating system 2 .

References  :=  1 : Cisco TelePresence Management Suite (TMS) - Cisco  2 : Cisco TelePresence Management Suite Installation and Upgrade Guide (15.16) - System Requirements [Cisco TelePresence Management Suite] - Cisco

When a source endpoint dials a destination endpoint, the first thing to occur is that an invite is sent to the SIP Server. The SIP Server is a logical entity that handles the signaling and call setup between SIP endpoints. The invite message contains the source endpoint’s identity, capabilities, and session parameters, as well as the destination endpoint’s address.  The SIP Server then routes the invite message to the destination endpoint or to another SIP Server if the destination endpoint is in a different domain 1 2 .  References  :=  1 2