Free Cisco 500-710 Practice Exam with Questions & Answers | Set: 3

Branding on the Cisco Meeting Server refers to the customization of prompts and backgrounds for the web app, SIP calls, and IVR messages. With a single branding license, you can customize the following aspects of the Cisco Meeting Server1:

• The sign-in page background image, icon, and logo for the web app
• The text strings for the web app
• The audio messages and background image for the SIP calls
• The audio messages and background image for the IVR messages
• The invitation text for the web app

You can apply branding to the Cisco Meeting Server in two ways: web server hosted branding or locally hosted branding1. Web server hosted branding requires a web server that hosts the branding files and provides the URLs to the Cisco Meeting Server API. Locally hosted branding requires uploading the branding files to the Cisco Meeting Server using the API1.

With web server hosted branding, you can use a single branding license to customize multiple logos and multiple backgrounds on multiple web bridges. This means that you can have different branding for different web bridges, depending on the web bridge profile that you associate with the web bridge1. For example, you can have a web bridge with a blue logo and background for one web bridge profile, and another web bridge with a red logo and background for another web bridge profile.

With locally hosted branding, you can use a single branding license to customize a single logo and single background on a single web bridge. This means that you can only have one branding for one web bridge, regardless of the web bridge profile that you associate with the web bridge1. For example, you can only have a web bridge with a green logo and background for any web bridge profile.

Therefore, the correct answer is B and E, as they describe the capabilities of web server hosted branding and locally hosted branding, respectively. References := 1: Cisco Meeting Server 3.5 Customization Guidelines,

According to the Cisco documentation1, the engineer can look on the Conductor web interface under Status > Calls > In Progress to view information about a call currently in progress. This page shows the details of each call, such as the call ID, the conference alias, the call type, the call state, the call duration, the call rate, the call protocol, the encryption status, and the call participants. The other options, such as Status > Calls > Calls, Logs > Event Log, and Status > Conferences > In Progress, do not show the information about a call currently in progress, but rather show the information about all calls, the event log messages, and the conferences in progress, respectively. References: 1: Cisco TelePresence Conductor Administrator Guide (XC4.3), Chapter 5: Monitoring Conferences and Calls, https://www.cisco.com/c/dam/en/us/td/docs/telepresence/infrastructure/conductor/admin_guide/Cisco-TelePresence-Conductor-Administrator-Guide-XC4-3.pdf

A user policy is a set of rules that defines how a user can access and use the video services. A user policy can include the following options1:

• Authentication: This option determines whether a user needs to provide credentials to access the video services, and what type of credentials are required (such as username and password, certificate, or token).
• Admin policy: This option determines whether a user has administrative privileges to manage the video services, such as creating and deleting spaces, adding and removing participants, and configuring settings.
• Call policy: This option determines whether a user can make and receive calls, and what type of calls are allowed (such as audio only, video only, or both).
• Find Me: This option determines whether a user can be reached by other users through a single address, and how the calls are routed to the user’s devices (such as desk phone, mobile phone, or video endpoint).

The correct answer is D, Find Me, because it is one of the options that can be configured in a user policy. The other options are not correct because:

• Authentication: This is not a user policy, but a security feature that can be enabled or disabled for the video services.
• Admin policy: This is not a user policy, but a role-based access control feature that can be assigned to different users or groups.
• Call policy: This is not a user policy, but a service policy that can be applied to different domains or zones.

References := 1: Cisco Meeting Server 3.5 Configuration Guides - User Policy Configuration

= When adding a Cisco Meeting Server to TMS, you need to configure the following items before the server can be used in scheduled conferences12:

• domain: This is the domain name of the Cisco Meeting Server, which is used to generate the conference aliases and URIs. For example, if the domain is cisco.com, the conference alias will be something like 123456@cisco.com. The domain name must match the domain name configured on the Cisco Meeting Server and the certificates used for secure communication.
• numeric ID base: This is the starting number for the numeric conference IDs that TMS assigns to the conferences scheduled on the Cisco Meeting Server. For example, if the numeric ID base is 1000, the first conference will have the numeric ID 1000, the second conference will have the numeric ID 1001, and so on. The numeric ID base must be unique for each Cisco Meeting Server in TMS and must not overlap with any existing conference IDs in TMS.
• numeric ID quantity: This is the number of numeric conference IDs that TMS can assign to the conferences scheduled on the Cisco Meeting Server. For example, if the numeric ID quantity is 100, TMS can assign numeric IDs from 1000 to 1099 to the conferences on the Cisco Meeting Server. The numeric ID quantity must be sufficient to accommodate the expected number of conferences on the Cisco Meeting Server.

The other options are not required or relevant for adding a Cisco Meeting Server to TMS. The DNS address and MAC address are not used by TMS to identify or communicate with the Cisco Meeting Server. The conference ID range is not a valid parameter for TMS.

References := Connect to TMS, Cisco Meeting Server - Configuration Guides

 TURN servers must be configured in a resilient and scalable Cisco Meeting Servers solution on the CMS edge only. The CMS edge is the component that provides firewall traversal and NAT traversal for external participants using WebRTC or SIP. The CMS edge acts as a TURN server that relays the media traffic between the external participants and the CMS core, which hosts the conferences. The CMS edge also performs media demultiplexing and encryption/decryption for the media streams. The CMS core does not need to have TURN servers configured, as it communicates directly with the internal endpoints and the CMS edge. The Cisco Unified Communications Manager does not need to have TURN servers configured either, as it is not involved in the media path for the CMS conferences123 References := 1Cisco Meeting Server - Configuration Guides 2Cisco Meeting Server 3.8, Scaled and Resilient Server Deployment Guide 3TURN Server and WebRTC

The Expressway uses subzones and pipes to control the bandwidth used by endpoints on the network. Subzones are logical groups of endpoints that share the same bandwidth policies and settings. Pipes are logical connections between subzones or zones that limit the total or per-call bandwidth available for calls. The Expressway allows the administrator to configure the bandwidth limits for each subzone and pipe, as well as the behavior when the bandwidth is insufficient or not specified. The other options are not valid methods for bandwidth control on the Expressway. References: Cisco Expressway Administrator Guide (X14.0) - Bandwidth Control, Cisco Expressway Basic Configuration Deployment Guide (X14.0) - Configuring Bandwidth Management

 The priority number governs the order in which the search rules query the local zone versus neighbored Expressways. The priority number is a value between 1 and 1000 that is assigned to each search rule. The lower the priority number, the higher the precedence of the search rule. The Expressway evaluates the search rules in ascending order of priority numbers, and stops when it finds a match. The priority number determines which zone (local or neighbor) is searched first for a given destination alias123 References := 1Cisco Expressway Administrator Guide (X14.0) - Search Rules 2Cisco Expressway-E and Expressway-C Basic Configuration Deployment Guide (X14.0) - Routing Configuration 3Concept of Zones Demystified On Cisco Expressway Series

• The engineer should navigate to System > Provisioning in TMS to resolve this issue. This is because the provisioning feature allows the engineer to centrally manage and configure the endpoints in remote offices, and prevent users from changing the settings locally12.
• System > Configuration Backup is not the correct option because this feature allows the engineer to backup and restore the configuration of TMS itself, not the endpoints3.
• Booking > Conference Templates is not the correct option because this feature allows the engineer to create and apply templates for scheduling conferences, not for configuring endpoints4.
• Monitoring > Conference Control Center is not the correct option because this feature allows the engineer to monitor and control the ongoing conferences, not the endpoint settings5. References := 1: Cisco TelePresence Management Suite Provisioning Extension Deployment Guide (TMSPE 1.8) - Introduction 2: Cisco TelePresence Management Suite Provisioning Extension Deployment Guide (TMSPE 1.8) - Configuring Endpoints 3: Cisco TelePresence Management Suite Administrator Guide (15.13) - Configuration Backup 4: Cisco TelePresence Management Suite Administrator Guide (15.13) - Conference Templates 5: Cisco TelePresence Management Suite Administrator Guide (15.13) - Conference Control Center