500-710 Video Infrastructure Implementation Practice Questions

The Network Log (also known as the searchrules log) provides the most granular detail about how Expressway processes incoming calls against its configured search rules and transforms. By setting the log level to DEBUG, the engineer can see the incoming alias, how it is processed by each rule in priority order, any regex matches and replacements that occur, and the final routing decision. This log is essential for diagnosing complex call routing problems, including why a '404 Not Found' is being returned.

This is a complex routing scenario that requires multiple, location-specific Service Preferences. The correct approach is to define Locations for the endpoints and bridge pools for the resources. Then, you create a distinct Service Preference for each originating location (EU and APAC) that defines the specific, ordered cascade of bridge pools to try. For EU callers, the preference would be EU -> HQ -> APAC. For APAC callers, it would be APAC -> HQ -> EU. This configuration provides the precise, tiered overflow logic required.

Membership Rules are used to dynamically place call sources into a specific subzone. These rules can be based on various criteria, such as the source IP address, the authenticated user, or the alias pattern. This allows administrators to automatically group devices or call types into different subzones to apply specific bandwidth management or call processing policies without manual assignment.

On the Cisco Meeting Server, after configuring a new Syslog server using the syslog add command via the MMP (Mainboard Management Processor), the configuration change does not take effect immediately. The logger service must be restarted for the CMS to begin sending logs to the newly defined destination. This is a common oversight during initial configuration.

External Jabber clients and other collaboration services (like Webex) need to establish a trusted TLS connection to the Expressway-E. To do this without manual certificate installation on every client, the Expressway-E must have a server certificate signed by a public Certificate Authority that is trusted by default by clients' operating systems.

The communication path between the Expressway-E in the DMZ and the Expressway-C in the internal network is secured via a traversal zone. This zone MUST be configured for mutual TLS, where each server presents a certificate and validates the certificate of the other, establishing a highly secure and trusted path for MRA traffic.

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.