Pass the Cisco Field Engineer 500-710 Questions and answers with ExamsMirror

Cisco Expressway is a video gateway that enables interoperability between different video endpoints and protocols. It consists of two components: Expressway core and Expressway edge1.

Cisco Meeting Server is a video conferencing solution that supports scalable and resilient deployments with multiple servers and clusters. It can integrate with various call control systems, such as Cisco Unified Communications Manager, Cisco Expressway, or Microsoft Skype for Business2.

To integrate Cisco Expressway with Cisco Meeting Server, the following steps are required3:

Configure the Expressway edge as the traversal server for the Meeting Server, and enable SIP and H.323 protocols on the Expressway edge.

Configure the Expressway core as the traversal client for the Meeting Server, and enable SIP and H.323 protocols on the Expressway core.

Configure the Meeting Server as the traversal server for the Expressway core, and enable SIP and H.323 protocols on the Meeting Server.

Configure the call control system to route calls to the Expressway core, and configure the Expressway core to route calls to the Meeting Server.

Optionally, configure the Expressway core to provide IM&P and video integration with Microsoft Skype for Business, if deployed in the core network with the Meeting Server.

By integrating both Expressway core and Expressway edge with Cisco Meeting Server, the following benefits can be achieved3:

Support for various video endpoints and protocols, such as SIP, H.323, WebRTC, and BFCP.

Support for firewall traversal and NAT traversal for external participants.

Support for encryption and authentication for secure communication.

Support for load balancing and failover for high availability and scalability.

References := 1: Cisco Expressway Series - Data Sheets - Cisco 2: Cisco Meeting Server - Configuration Guides - Cisco 3: Cisco Meeting Server, Deployments with Expressway Planning and Preparation Guide

Cisco Spark is a cloud-based collaboration platform that offers messaging, calling, meeting, and video conferencing capabilities. There are two main deployment models for Cisco Spark implementation: Spark Cloud and Spark Hybrid.

Spark Cloud is the default deployment model, where all the services and features are provided by the Cisco Spark cloud. The users can access the Cisco Spark app on their devices (such as desktops, laptops, tablets, or smartphones) and communicate with other users or join meetings hosted on the cloud. The users can also use Cisco Spark-registered devices, such as IP phones, video endpoints, or room systems, to access the cloud services. The Spark Cloud deployment model is suitable for organizations that want a simple, scalable, and secure cloud solution without the need for any on-premises infrastructure or integration.

Spark Hybrid is an optional deployment model, where some of the services and features are provided by the Cisco Spark cloud, while others are provided by the existing on-premises infrastructure, such as Cisco Unified Communications Manager (CUCM), Cisco Expressway, or Cisco TelePresence Server. The Spark Hybrid deployment model allows the organizations to leverage their existing investments and integrate the Cisco Spark cloud with their on-premises systems. The Spark Hybrid deployment model offers several hybrid services, such as hybrid call service, hybrid calendar service, hybrid directory service, hybrid media service, and hybrid message service. The Spark Hybrid deployment model is suitable for organizations that want to extend the functionality and reach of their on-premises systems and enable seamless collaboration across different environments.

The other options are not valid deployment models for Cisco Spark implementation. CMR stands for Cisco Collaboration Meeting Room, which is a solution that enables users to join meetings from any device, whether it is registered to the Cisco Spark cloud or the on-premises infrastructure. CMR is not a deployment model, but a feature that can be used in both Spark Cloud and Spark Hybrid deployment models. Spark Premises is not a valid option, as Cisco Spark is a cloud-based platform and does not offer a fully on-premises deployment option. References: Cisco Spark Deployment Models, Cisco Spark Hybrid Services, Cisco Collaboration Meeting Rooms (CMR)

= 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 <access_token>.

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

Cisco WebEx Meeting Center is a cloud-based service that provides video conferencing, screen sharing, chat, and other collaboration features for online meetings. Cisco WebEx Meeting Center can support calls from end points and WebEx clients, as well as from other devices and applications. End points are devices that are registered to the Cisco WebEx cloud, such as Cisco IP Phones, Cisco video devices, and third-party devices that use SIP to connect to the WebEx Suite services. WebEx clients are applications that run on desktops, laptops, tablets, or smartphones, such as the WebEx app, the WebEx Meetings app, or the WebEx Teams app. Users can join WebEx meetings from end points or WebEx clients, and they can also dial in or dial outto other numbers using the WebEx cloud. The other options are not valid Cisco WebEx products that can support calls from end points and WebEx clients. Cisco WebEx Training Center, Cisco WebEx Support Center, and Cisco WebEx Event Center are specialized services that provide additional features for specific use cases, such as online training, remote support, and large-scale events. However, they do not support calls from end points or WebEx clients, and they require users to join the meetings using the WebEx Meetings app or a web browser. References: Network Requirements for Webex Services, Overview of Webex Calling, Webex Calling—Cloud Phone System

To enable the administrator to be notified remotely when certain events occur, such as system errors, booking failures, or alarms, the email settings must be properly configured in TMS. The email settings allow the administrator to specify the SMTP server, the sender address, the recipient addresses, and the notification frequency for different types of events. The email settings can be configured by going to Administrative Tools > Configuration > Email Settings12. References := 

https://www.cisco.com/c/dam/en/us/td/docs/telepresence/infrastructure/tms/admin_guide/Cisco_TMS_Admin_Guide_14-1.pdf

https://www.cisco.com/c/dam/en/us/td/docs/telepresence/infrastructure/tms/admin_guide/Cisco-TMS-Admin-Guide-15-13-2.pdf

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

Authentication credentials can be stored in the local database of the Expressway. This is true because the Expressway can use its local authentication database to verify the credentials of incoming requests from devices or external systems1. Alternatively, the Expressway can also use external authentication methods, such as LDAP, SAML, or OAuth1.

SIP endpoints always need authentication credentials. This is false because the Expressway’s authentication policy can be configured separately for each zone, and it can be set to “Do not check credentials” or “Treat as authenticated” for SIP messages from local or non-local domains1. This means that some SIP endpoints may not need authentication credentials to communicate with the Expressway, depending on the zone configuration.

The endpoint and Expressway must be configured and synchronized with an NTP server delivering an identical time stamp. This is false because the Expressway and the endpoint do not need to be synchronized with identical NTP timestamps for authentication purposes2. However, it is recommended to synchronize the Expressway and the endpoint with the same NTP server for other reasons, such as logging, troubleshooting, and certificate validation3.

Expressways and endpoints do not need to be synchronized with identical NTP timestamps. This is true because the Expressway and the endpoint do not need to be synchronized with identical NTP timestamps for authentication purposes2. However, it is recommended to synchronize the Expressway and the endpoint with the same NTP server for other reasons, such as logging, troubleshooting, and certificate validation3.

When a subzone is set for “Treat as Authenticated”, the endpoint must have the correct authentications configured. This is false because the “Treat as Authenticated” option means that the Expressway will not verify the credentials and will allow the message to be processed as if it has been authenticated1. This option can be used to cater for endpoints from third-party suppliers that do not support authentication within their registration mechanism1.

References := 1: Cisco Expressway Administrator Guide (X14.0) - Device Authentication 2: Cisco Expressway Administrator Guide (X14.0) - NTP Configuration 3: Cisco Expressway Administrator Guide (X14.0) - Time and Date

= The CMR Premise platform is a solution for on-premises video conferencing that works with Cisco Unified Communications Manager to bring multipoint video to Unified Communications networks1. The CMR Premise platform supports two products as multipoint conferencing options:

Telepresence Server: This is a scalable and flexible video conferencing bridge that provides high-quality video and audio for multiparty conferencing. It supports a variety of endpoints, protocols, and features, such as ActiveControl, ClearPath, and cascading. It can be deployed on dedicated hardware or in virtualized environments2.

Cisco Meeting Server: This is a software-based video conferencing solution that provides interoperability with other video platforms, such as Microsoft Skype for Business and WebRTC. It supports a range of features, such as personal meeting rooms, screen sharing, and recording. It can be deployed on Cisco Meeting Server hardware or on virtual machines3.

The other products, such as Cisco Expressway, Cisco Telepresence Multipoint Switch, and Cisco VCS, are not multipoint conferencing options in the CMR Premise platform. Cisco Expressway is a gateway that provides firewall traversal, edge services, and interworking for video calls. Cisco Telepresence Multipoint Switch is a legacy product that provides multipoint conferencing for Cisco Telepresence endpoints only. Cisco VCS is a call control and management solution that provides SIP and H.323 interworking, registration, and routing for video endpoints4 . References := 1: Cisco Collaboration Meeting Rooms Premises - Cisco 2: Cisco TelePresence Server Data Sheet - Cisco 3: Cisco MeetingServer Data Sheet - Cisco 4: Cisco Expressway Series - Cisco : Cisco TelePresence Multipoint Switch Data Sheet - Cisco : Cisco TelePresence Video Communication Server (VCS) - Cisco

According to the Cisco documentation1, the Conductor uses the source IP addresses of the incoming calls to determine which subzone they belong to, and then applies the appropriate search rules to route them to the appropriate conference bridge. The conference IP addresses, location IP addresses, and management IP addresses are not used by the Conductor for this purpose. References: 1: Cisco Video Infrastructure Design Guide, Chapter 4: Cisco Conductor, https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/uc_system/design/guides/videodg/vidguide/conductor.html#pgfId-1060629

= To match any incoming call to the Expressway that is searching for an E.164 address of only 6 digits and append the domain cisco.com to the end, you need to use a pattern match and a replace string using regular expressions. Regular expressions are a way of describing patterns of text using special characters and symbols1. The Expressway supports the use of regular expressions in several features, such as search rules, transforms, and dial plan2.

A pattern match is a regular expression that defines the criteria for matching the incoming call. A replace string is a regular expression that defines how to modify the matched call and add the desired domain. The Expressway uses the following syntax for pattern match and replace string2:

The pattern match is enclosed in parentheses, such as (pattern).

The replace string is preceded by a colon, such as :replace.

The replace string can use backreferences to refer to the matched groups in the pattern match, such as \1, \2, etc.

For example, the pattern match and replace string (pattern):replace means that the Expressway will match the incoming call with the pattern and replace it with the replace string.

In this question, the pattern match should match an E.164 address of only 6 digits. An E.164 address is a global phone number that can have up to 15 digits, starting with a plus sign (+)3. To match only 6 digits, we can use the following regular expression:

({6}\d) : This means that the Expressway will match any 6 consecutive digits (\d) and capture them as a group ({6}). The curly braces indicate the number of repetitions of the preceding character. The parentheses indicate the grouping of the characters.

The replace string should append the domain cisco.com to the end of the matched E.164 address. To do this, we can use the following regular expression:

:\1@cisco.com : This means that the Expressway will replace the matched E.164 address with the first captured group (\1) followed by an at sign (@) and the domain cisco.com.

Therefore, the correct pattern match and replace string using regular expressions are:

pattern match: ({6}\d)

replace string: \1@cisco.com

The other options are incorrect because:

A. pattern match: ({6}) : This means that the Expressway will match any 6 consecutive characters () and capture them as a group. The asterisk means that the preceding character can be repeated zero or more times. This is too broad and can match non-digit characters as well.

C. pattern match: ({5}\d) : This means that the Expressway will match any 5 consecutive digits (\d) and capture them as a group. This is too short and will not match an E.164 address of 6 digits.

D. replace string: \6@cisco.com : This means that the Expressway will replace the matched E.164 address with the sixth captured group (\6) followed by an at sign (@) and the domain cisco.com. This is incorrect because there is only one captured group in the pattern match, so \6 will not refer to anything.

F. replace string: $@cisco.com : This means that the Expressway will replace the matched E.164 address with a dollar sign ($) followed by an at sign (@) and the domain cisco.com. This is incorrect because the dollar sign is a special character in regular expressions that means the end of the string. To use it literally, it needs to be escaped with a backslash ().

References := Regular Expressions, Cisco Expressway Basic Configuration Deployment Guide, E.164 : The international public telecommunication numbering plan