500-710 Sample Questions & Answers

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.

Cisco TelePresence Conductor uses Service Preferences to control which bridge pool is selected for a conference. By creating two bridge pools (one for each site) and a Service Preference that lists the primary site's pool with a lower priority number (e.g., Priority 10) and the DR site's pool with a higher number (e.g., Priority 20), the Conductor will always attempt to use the primary server first. It will only use the DR server if the primary is unavailable or has no capacity.

A publicly trusted CA-signed certificate is mandatory for Expressway-E to establish secure TLS connections with external clients (MRA, B2B). The certificate's SAN must include all FQDNs that clients will use to connect, including the collaboration edge domain(s). A default traversal zone using TLS is the standard mechanism for secure communication between Expressway-E and Expressway-C.

The traversal zone between Expressway-E and Expressway-C is the secure tunnel for all internal communications. Configuring this as a TLS-verified zone ensures that the signaling and media proxying between the DMZ and the internal network are encrypted and authenticated.

The coSpaceUri is the local part of the URI used to dial into the coSpace. The value 'boardroom' is a valid string for this parameter. The CMS will create the coSpace and assign it this URI. The full dialable address would then be 'boardroom@ ', where is configured on the CMS call settings. The API does not automatically generate a numeric ID in this field if a valid string is provided.

While co-locating the SQL database and TMS application is supported for smaller deployments, it is not a best practice for production environments. Both the TMS application (specifically IIS) and SQL Server are resource-intensive. Running them on the same OS can lead to contention for CPU, memory, and I/O, resulting in slow performance, application instability, and potential data corruption. Separating them onto dedicated servers is the recommended approach for scalability and reliability.

Once a user manually edits their own profile information (like their name) via the Webex profile portal, that information takes precedence over data synchronized from Active Directory. The Directory Connector will no longer be able to overwrite the user-modified fields. To resolve this, an administrator must use a CSV import in Control Hub to force the name change or the user must revert their changes, which is often not possible. This is a common operational issue in managed environments.