500-710 Cisco Video Infrastructure Implementation (VII) Free Practice Exam Questions (2025 Updated)

According to the Cisco documentation1, the Expressway stores the username and password of the local database users in its local database. These users can be used for authentication and authorization purposes when accessing the Expressway web interface or API. The other elements, such as user authority, CA authority, and crypto hash key, are not stored in the local database of the Expressway, but are either derived from other sources or generated dynamically. References: 1: Cisco Expressway Basic Configuration Deployment Guide, Chapter 3: Configuring Local Database Users, https://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/expressway/config_guide/X8-11/Cisco-Expressway-Basic-Configuration-Deployment-Guide-X8-11.pdf

= Call Service Connect is a hybrid service that allows integration between Cisco Spark and Cisco Unified Communications Manager (CUCM). Call Service Connect enables the Cisco Spark app to be used as a softphone for voice and video calling, and to share an extension with the CUCM desk phone. Call Service Connect also provides a unified call history and caller ID across Cisco Spark and CUCM devices123

Call Service Connect requires media traversal capabilities and licenses to be installed on the Expressway-C and Expressway-E pair that connects the CUCM and the Cisco Collaboration Cloud. Call Service Connect also requires mutual TLS (mTLS) authentication between the Expressway-E and the cloud, and between the Expressway-C and the CUCM. Call Service Connect depends on Call Service Aware, which is another hybrid service that synchronizes the user and device information from the CUCM to the cloud. Call Service Aware must be deployed before Call Service Connect124

References := 1Cisco Spark Hybrid Services Data Sheet 2Cisco Spark Hybrid Services Deployment Guide 3Cisco Spark Hybrid Services At-a-Glance 4Deployment guide for Hybrid Calling for Webex Devices (Device Connector)

system network directory is a phone book source that imports contacts from a directory server that uses the H.350 protocol. TMS can connect to multiple system network directories and synchronize the contacts with the TMS database. The system network directory can be used to create phone books for endpoints that are managed by TMS. The other options are not valid phone book sources for TMS. References: Cisco TelePresence Management Suite Phone Book Configuration Guide, TMS Phone Books Troubleshoot Guide

= TMS permissions are assigned to groups, and users are added to the groups. This is because TMS uses a role-based access control model, where different groups have different levels of access and privileges to the TMS functions and resources. Users can belong to one or more groups, and inherit the permissions of those groups. TMS provides some predefined groups, such as Administrators, Booking, Users, and Read Only, and also allows creating custom groups with specific permissions1.

The other options are not correct because:

TMS permissions are directly assigned to individual users: This is not true, as TMS does not allow assigning permissions to individual users. Users can only have permissions through the groups they belong to1.

TMS permissions can be imported from the Expressway or Cisco Unified Communications Manager: This is not true, as TMS does not support importing permissions from other systems. TMS permissions are configured and managed within the TMS application1.

TMS permissions are configured in Active Directory, which is then synched to TMS: This is partially true, as TMS can integrate with Active Directory to authenticate users and import user accounts and groups. However, the permissions are not configured in Active Directory, but in TMS. The Active Directory groups are mapped to the TMS groups, and the permissions are applied accordingly2.

References := 1: Cisco TelePresence Management Suite Administrator Guide (15.16) - User Administration [Cisco TelePresence Management Suite] - Cisco 2: Cisco TelePresence Management Suite Administrator Guide (15.16) - Active Directory Integration [Cisco TelePresence Management Suite] - Cisco

A subzone is a logical grouping of endpoints within a zone that allows the Expressway to apply different policies and bandwidth controls to different sets of endpoints1.

An endpoint is a device that can make or receive calls, such as a video conferencing system, a phone, or a soft client2.

When an endpoint registers with the Expressway, it is assigned to a subzone based on the following criteria3:

If the endpoint is making a traversal call (a call that crosses a firewall or a network boundary), it is assigned to the traversal subzone. A traversal call requires a traversal client zone on the Expressway that initiates the call and a traversal server zone on the Expressway that receives the call.

If the endpoint is not making a traversal call, it is assigned to a subzone based on the subzone membership rules. These rules specify the range of IP addresses or alias pattern matches for each subzone. If an endpoint’s IP address or alias does not match any of the membership rules, it is assigned to the default subzone.

If the endpoint is not allowed to register with the Expressway, it is rejected based on the registration restriction rules. These rules specify the IP addresses or aliases of the endpoints that are denied or allowed to register with the Expressway.

Therefore, the two statements that are true about the assignment of endpoints to a subzone are:

A. A registration restriction rule must be configured that matches the endpoint’s alias or IP subnet. This statement is true because the registration restriction rules are used to filter out the endpoints that are not allowed to register with the Expressway based on their alias or IP subnet3.

E. A subzone membership rule must be configured that matches the endpoint’s alias or IP subnet. This statement is true because the subzone membership rules are used to assign the endpoints that are allowed to register with the Expressway to the appropriate subzone based on their alias or IP subnet3.

The other options are incorrect because:

B. Endpoints making a traversal call must be registered to the traversal subzone. This statement is false because the traversal subzone is not a subzone that endpoints can register to, but a subzone that endpoints are assigned to when they make a traversal call3.

C. By default, all endpoints are registered to the default subzone. This statement is false because not all endpoints are registered to the default subzone, only those that do not match any subzone membership rules or make a traversal call3.

D. By default, all endpoints are registered to the neighbor subzone. This statement is false because the neighbor subzone is not a subzone that endpoints can register to, but a subzone that represents a neighbor zone (a logical connection to another Expressway or a third-party device) on the Expressway.

References := 1: Cisco Expressway Administrator Guide (X14.0) 2: Cisco Expressway Basic Configuration Deployment Guide (X8.11) 3: Cisco Expressway Administrator Guide (X14.0) : Cisco Expressway Administrator Guide (X14.0) : Cisco Expressway Administrator Guide (X14.0)

 The Cisco Meeting Server uses port 5060 for SIP signaling from the call bridge to the H.323 gateway. This is because port 5060 is the default port for SIP signaling over UDP or TCP, and the Cisco Meeting Server supports both protocols for SIP signaling1. The call bridge communicates with the H.323 gateway using SIP signaling to establish and manage calls between SIP and H.323 endpoints2.

The other options are not correct because:

4999: This is not a port used for SIP signaling, but for H.323 signaling over TCP. The Cisco Meeting Server uses port 4999 for H.323 signaling from the call bridge to the H.323 gateway1.

5222: This is not a port used for SIP signaling, but for XMPP signaling over TCP. The Cisco Meeting Server uses port 5222 for XMPP signaling from the call bridge to the XMPP server1.

6061: This is not a port used for SIP signaling, but for SIP signaling over TLS. The Cisco Meeting Server uses port 6061 for SIP signaling over TLS from the call bridge to the Expressway-C or the SIP proxy1.

References := 1: Cisco Meeting Server 3.5 Configuration Guides - Port Reference 2: Cisco Meeting Server 3.5 Configuration Guides - H.323 Gateway Configuration

The engineer needs to navigate to Systems > Configuration Templates to create this setting. 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 configuration templates to configure and update multiple endpoints with the same settings, such as registration configurations, network settings, security settings, and so on1. The engineer can create a configuration template with the desired registration configurations for the group of endpoints in the remote office, and then schedule the template to be applied automatically every Sunday at 3:00 a.m. using the TMS Tools application2.

The other options are not correct because:

Systems > Manage Dial Plan: This is not the correct navigation, as this option is used to manage the dial plan for the video network, such as creating prefixes, aliases, and zones. This option does not allow creating or applying configuration templates3.

Systems > Provisioning: This is not the correct navigation, as this option is used to manage the provisioning of endpoints that are registered to Cisco Unified Communications Manager or Cisco VCS. This option does not allow creating or applying configuration templates4.

Systems > Navigator: This is not the correct navigation, as this option is used to manage the Navigator clusters that aggregate multiple Cisco VCS or Expressway devices into a single entity. This option does not allow creating or applying configuration templates.

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) - Dial Plan [Cisco TelePresence Management Suite] - Cisco 4: Cisco TelePresence Management Suite Administrator Guide (15.16) - Provisioning [CiscoTelePresence Management Suite] - Cisco : Cisco TelePresence Management Suite Administrator Guide (15.16) - Navigator [Cisco TelePresence Management Suite] - Cisco