Free Practice Questions for Cisco 500-710 Exam

 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 on1. 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 TMS2. 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 endpoint3.

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

Call bridges can connect to databases in full mesh. This is true because the call bridge cluster uses a distributed database architecture that allows each call bridge to connect to any other call bridge in the cluster, and synchronize the data across all nodes12.

Call bridges only connect to the master database. This is false because the call bridge cluster does not have a fixed master database, but rather elects one dynamically based on the availability and connectivity of the nodes12.

Only one call bridge should be configured per domain in a database cluster. This is false because the call bridge cluster can support multiple domains, and each domain can have multiple call bridges associated with it13.

Call bridges can read/write to any database in a cluster at anytime. This is false because the call bridge cluster uses a leader-follower model, where only one call bridge (the leader) can write to the database at a time, and the others (the followers) can only read from the database12. References := 1: Cisco Meeting Server Scalability and Resilience Deployment Guide (3.8) - Database Clustering 2: Cisco Meeting Server Configuration Guides - Configure Cisco Meeting Server Call Bridge Database Cluster 3: Cisco Meeting Server Scalability and Resilience Deployment Guide (3.8) - Call Bridge Clustering

= OAuth is an open standard for authorization that allows applications and services to access resources on behalf of a user, without sharing the user’s credentials. OAuth uses access tokens to grant permissions to applications and services to access the user’s resources1. Cisco Spark supports OAuth 2.0, which is the latest version of OAuth2.

To use OAuth access tokens with Cisco Spark, you need to follow these steps2:

Register your application or service to Cisco Spark as an integration. You will receive a client ID and a client secret, which are used to identify your application or service to Cisco Spark.

Redirect the user to the Cisco Spark authorization URL, where the user can login with their Cisco Spark credentials and grant permissions to your application or service. The permissions are defined by the scopes that you specify in the authorization URL. For example, if you want to access the user’s messages and rooms, you need to request the spark:messages_read and spark:rooms_read scopes.

Receive an authorization code from Cisco Spark, which is sent to the redirect URI that you specify in the authorization URL. The redirect URI must match the one that you registered with Cisco Spark.

Exchange the authorization code for an access token and a refresh token from Cisco Spark, using your client ID and client secret. The access token is used to access the user’s resources on Cisco Spark, such as messages, rooms, people, etc. The refresh token is used to obtain a new access token when the current one expires.

Use the access token to make API requests to Cisco Spark on behalf of the user. You need to include the access token in the Authorization header of your HTTP requests, such as Authorization: Bearer .

Therefore, the two options that are requirements to use OAuth access tokens with Cisco Spark are:

C. Applications can only request the access token when the authenticated user grants permissions to this service. This is true because the user needs to authorize the application or service to access their resources on Cisco Spark, by logging in and consenting to the scopes that the application or service requests.

E. Services can request the access token only when the authenticated user grants permissions to this service. This is also true because the service needs to obtain the user’s consent to access their resources on Cisco Spark, by redirecting the user to the Cisco Spark authorization URL and receiving an authorization code.

The other options are not requirements to use OAuth access tokens with Cisco Spark, because:

A. Tokens must request access to servers before applications register to Cisco Spark. This is false because tokens are not entities that can request access to servers. Tokens are strings that represent the permissions that the user grants to the applications or services. Applications or services need to register to Cisco Spark before they can request tokens, not the other way around.

B. Servers must register to Cisco Spark as an application to request access tokens. This is false because servers are not the same as applications. Servers are physical or virtual machines that host applications or services. Applications or services are software programs that interact with Cisco Spark. Servers do not need to register to Cisco Spark, but applications or services do.

D. Applications must register to Cisco Spark as a server to request access tokens. This is also false because applications are not the same as servers. Applications are software programs that interact with Cisco Spark. Servers are physical or virtual machines that host applications or services. Applications do not need to register to Cisco Spark as servers, but as integrations.

References := OAuth 2.0, Cisco Spark for Developers - Authentication

= Call-control devices are responsible for establishing, maintaining, and terminating calls in a Cisco Collaboration environment. They provide features such as endpoint registration, call routing, call admission control, codec negotiation, and trunk protocol translation. According to the Cisco Expressway Basic Configuration Deployment Guide, Cisco Expressway is a call-control device that enables secure communication between endpoints inside and outside the enterprise network. According to the Call Control with CUCM for Cisco CICD (210-060) course, Cisco Unified Communications Manager is a call-control device that provides centralized call processing and management for Cisco IP phones, video endpoints, and gateways.

The other options are not call-control devices, but rather collaboration devices that provide different functions. Cisco Telepresence Endpoint is a video device that enables face-to-face communication with high-quality audio and video. Cisco Meeting Server is a conferencing device that enables multiparty audio, video, and web collaboration. Cisco Content Server is a recording and streaming device that enables live and on-demand video content creation and distribution.

References := Cisco Expressway Basic Configuration Deployment Guide, Call Control with CUCM for Cisco CICD (210-060), [Cisco Collaboration Devices At-a-Glance]

= To restrict the registration of endpoints based on their aliases, you can use the restriction policy feature on the Cisco Expressway. The restriction policy can be set to “Allow”, “Deny”, or “None”. If you set it to “Allow”, you can specify a list of regular expressions that match the aliases of the endpoints that you want to allow. Any endpoint that does not match any of the expressions in the allow list will be rejected. If you set it to “Deny”, you can specify a list of regular expressions that match the aliases of the endpoints that you want to deny. Any endpoint that matches any of the expressions in the deny list will be rejected. If you set it to “None”, you can disable the restriction policy feature and allow all endpoints to register.

In this question, the engineer wants to only allow the registration of endpoints with aliases containing cisco.com as the domain. Therefore, the best option is to set the restriction policy to “Allow” and include the expression. *@cisco. com in the allow list. This expression will match any alias that ends with @cisco.com, such as user1@cisco.com, user2@cisco.com, etc. Any other alias that does not end with @cisco.com, such as user3@gmail.com, user4@company.com, etc., will not match the expression and will be rejected.

References := Cisco Expressway Basic Configuration Deployment Guide, Cisco Expressway Administrator Guide

 To initially log in to the Cisco Spark Management Portal, an engineer needs to follow these steps:

From your web browser, navigate to http://admin.ciscospark.com.  This is the URL for the Cisco Spark Management Portal, where you can manage your Cisco Spark services, users, devices, and settings1.

Enter your username and click Sign In. Your username is the email address that you used to sign up for Cisco Spark1. You will be redirected to the Cisco Webex login page2.

On the next page, enter the password and click Sign In again. Your password is the one that you created when you activated your Cisco Spark account1. You will be logged in to the Cisco Spark Management Portal2. References := https://www.cisco.com/c/en/us/about/help/login-account-help.html

https://www.cisco.com/c/en/us/about/account.html

= Transforms are a way of modifying the destination alias or address of a call before it is routed to the appropriate zone or service. Transforms can be applied at different stages of the call routing process, such as pre-search, search rules, or call policy. The Cisco recommended method to add a domain to a numeric E.164 alias dialed by an H.323 endpoint is to use a pre-search transform. A pre-search transform is applied to the destination alias before any searches are sent to external zones. This allows the Expressway to standardize the destination aliases originating from both H.323 and SIP devices. For example, if the called address is an H.323 E.164 alias “01234”, the Expressway can automatically append the configured domain name (in this case example.com) to the called address (that is, 01234@example.com making it into a URI), before attempting to set up the call. This way, the Expressway can route the call to the correct destination zone or service based on the full URI. References := Cisco Expressway-E and Expressway-C Basic Configuration Deployment Guide (X14.0) - Routing ConfigurationCisco Expressway Administrator Guide (X14.0) - Dial Plan and Call Processing

Hybrid Services are a set of features that allow you to connect your on-premises or partner-hosted Cisco collaboration components to the cloud-based Cisco Spark capabilities1.

Connectors are software modules that run on Expressway-C or Expressway-E and provide secure communication between your premises environment and the cloud1.

To enable Hybrid Services with Cisco Spark, you need to establish four connectors in your premises environment123:

Calendar Connector: This connector integrates your on-premises Microsoft Exchange or Office 365 calendar with Cisco Spark, enabling users to schedule and join meetings from their calendar applications or devices1.

Call Service Connector: This connector enables Cisco Spark to use your on-premises call control (Cisco Unified Communications Manager or Cisco Business Edition) for PSTN calling, extension dialing, and desk phone control1.

Directory Connector: This connector synchronizes your on-premises Active Directory or LDAP directory with Cisco Spark, allowing users to search and communicate with their colleagues using their corporate email addresses1.

Serviceability Connector: This connector collects diagnostic data and logs from your on-premises devices and components and uploads them to the cloud for troubleshooting and analysis1.

The other options are incorrect because:

A. 2 is too few for Hybrid Services to be fully enabled with Cisco Spark. You need at least three connectors (Calendar, Call Service, and Directory) to enable the core features of Hybrid Services1. The Serviceability Connector is optional but recommended for support and maintenance1.

C. 3 is also too few for Hybrid Services to be fully enabled with Cisco Spark. You need all four connectors (Calendar, Call Service, Directory, and Serviceability) to enable the full functionality and benefits of Hybrid Services1.

D. 1 is not enough for Hybrid Services to be fully enabled with Cisco Spark. You need four different connectors (Calendar, Call Service, Directory, and Serviceability) to enable different aspects of Hybrid Services1.

References := 1: The best of both worlds – Cisco Spark Hybrid Services 2: Deployment guide for Hybrid Calendar - Deploy Expressway … - Cisco 3: Deployment guide for Hybrid Message - Deploy Cisco Webex Hybrid Message … : Deployment guide for Serviceability Connector - Deploy … - Cisco : Deployment guide for Hybrid Calling for Webex Devices (Device … - Cisco

 The minimum number of databases that can exist within a cluster when deploying a resilient and scalable Cisco Meeting Server deployment is 3. This is because a database cluster of 3 nodes can tolerate the failure of one node and still maintain a quorum, which is the majority of nodes that are online and can agree on the state of the data. A database cluster of 2 nodes cannot tolerate any failure, as it would lose the quorum and become unavailable. A database cluster of more than 3 nodes can also work, but it would consume more resources and increase the complexity of the deployment1.

References := 1: Frequently Asked Questions - Why do I need a database cluster with at least 3 nodes rather than 2 for my Meeting Server deployment?