Download Cisco.PracticeTest.210-060.v2017-10-18.by.Ian.109q.vcex

User passwords cannot be automatically synchronized when a Lightweight Directory Access Protocol (LDAP) directory is integrated with Cisco Unified Communications Manager (UCM). When UCM is configured to synchronize with an LDAP directory, such as OpenLDAP or Microsoft Active Directory, the user ID and all user personal and organizational data that is stored in the LDAP directory, except for passwords, are replicated to the UCM database. It is important to note that the Cisco Directory Synchronization (DirSync) service must be activated before LDAP synchronization can take place. 
When LDAP synchronization is configured, UCM configures the synchronized data as read-only data and acknowledges the LDAP directory as the central authority for creating and deleting user accounts. Therefore, UCM prevents administrators from using the UCM graphical user interface (GUI) to add and delete users. None of the data that was replicated to the UCM database can be modified by using the GUI. However, UCM user data that is not managed by the LDAP directory, such as the user's password and personal identification number (PIN), can be modified in the UCM administrative GUI. 
User lookups can be automatically synchronized when the LDAP directory of an organization has been integrated with UCM. When LDAP directory lookups are enabled, not only can UCM applications users, such as a Cisco Unified Personal Communicator client, search for and view information in the LDAP directory, but they can also add to their contact lists from the LDAP directory. Administrators can configure a limitless number of LDAP custom filters in UCM Administration to filter the results of LDAP searches. 
User authentication can be automatically synchronized when the LDAP directory of an organization has been integrated with UCM. When a user attempts to authenticate with UCM, the user's credentials are passed to the LDAP directory authentication service. If the credentials are correct, the user is authenticated and permitted to log in to the UCM GUI. 
User provisioning can be automatically synchronized when the LDAP directory of an organization has been integrated with UCM. When UCM is integrated with LDAP, provisioning a user in LDAP will automatically add that same user account to UCM. Having this integration prevents the administrator from having to make manual adjustments in two locations in the event that an account needs to be modified, created, or removed. 
Reference:
Cisco: LDAP Directory Integration: LDAP Authentication
Cisco: LDAP Directory Integration: LDAP Synchronization

You could issue the following command set on Router1 so that calls are routed to Phone2:
dial-peer voice 1 pots 
destination-pattern ....... 
port 1/0/0 
The dial-peer voice tag [pots | voip] command is used to define how calls are routed to destination endpoints on either the public switched telephone network (PSTN) or a Voice over IP (VoIP) network. To define call routing for the PSTN, you should issue the dial-peer voice command with the pots keyword. The tag value is any number in the range from 1 through 2147483647 that you assign to the dial peer as an identifier. To define call routing for a VoIP network, you should issue the dial-peer voice command with the voip keyword. In this scenario, Phone2 is connected to the PSTN. Therefore, dial peer 1 should be configured as a pots dial peer. 
The destination-pattern command is used to match both inbound and outbound dial peers. The sequence of dialed digits that will be matched for a dial peer can contain the digits 0 through 9, the asterisk (*), and the pound sign (#). In addition, you can use a period (.) as a wildcard symbol to refine the dialing pattern or to match multiple dial strings for a single dial peer. In the command set above, dial peer 1 is configured to match destinations that contain seven digits. Each digit in the pattern is represented by a single .wildcard. Phone2 is addressed with a seven-digit telephone number; therefore, the dial peer's destination-pattern command should be configured to match a sevendigit pattern. 
The port command is used by a voice router to match inbound plain old telephone service (POTS) dial peers and to determine where to route outgoing POTS dial peers. In this scenario, the Cisco Unified Communications Manager Express (CME) router port connected to the PSTN is foreign exchange office (FXO) port 1/0/0. Therefore, the dial peer should be configured to send traffic from Router1 destined for Phone2 through port 1/0/0. 
Issuing the following command set on Router1 will not route calls to Phone2:
dial-peer voice 1 voip 
destination-pattern 555.... 
port 1/0/0 
Although the destination-pattern command will match the Phone2 telephone number and the port command is configured for the port on Router1 that is connected to the PSTN, the dial-peer voice command has been issued with the voip keyword. Phone2 is connected to the PSTN, not to the VoIP network. In addition, the session target command, not the port command, must be issued to route a voip dial peer. The session target command configures a dial peer with a network address for routing voice traffic over an IP network. The network address can be an IP address or a host name, depending on whether a Domain Name System (DNS) server is configured and available to resolve host names. 
Issuing the following command set on Router1 will not route calls to Phone2:
dial-peer voice 1 voip 
destination-pattern 555.... 
port 1/0/1 
Although the destination-pattern command will match the Phone2 telephone number, the port command is configured for the foreign exchange station (FXS) 1/0/1 port on Router1, not the outbound port that is connected to the PSTN. In addition, the dial-peer voice command has been issued with the voip keyword. Therefore, the previous command set is an invalid configuration. 
Issuing the following command set on Router1 will not route calls to Phone2:
dial-peer voice 1 pots 
destination-pattern 5550717 
port 1/0/1 
Although the dial-peer voice command is correctly configured and the destination-pattern command will explicitly match the telephone number for Phone2, an incorrect port has been specified for the outbound traffic. The command set above would work if the port 1/0/0 command were issued instead of the port 1/0/1 command. You cannot connect an FXS port to the PSTN. 
Reference:
Cisco: Understanding Inbound and Outbound Dial Peer Matching on IOS Platforms: Non DID Case

Of the available choices, you are most likely configuring a customer administrator if you click Administrator’s Login Account in the Configure System Parameters menu. A Cisco Unified Communications Manager Express (CME) environment supports three types of users: system administrator, customer administrator, and phone user. A customer administrator account enables a reseller to give customers administrative control over some of the CME features that are available to those customers. In order for a customer administrator to log on to the graphical user interface (GUI), the system administrator must first create a customer administrator account for that user. After clicking Administrator’s Login Account in the GUI, you should enter appropriate values in the Admin User Name (username) field, the Admin User Type (Customer) field, and both password fields. Finally, click the Change button to create the user.
You can also create a customer administrator by using the command-line interface (CLI). Customer administrator accounts are configured in the CLI by issuing the web admin customer name user-name password string command in telephony service configuration mode, where username is the user name you want to assign to the customer administrator and string is the password you want to associate with the user name. 
You are not configuring a phone administrator. Phone users, not phone administrators, can manage IP phone settings either by using the telephone keypad or by logging on to the CME browser-based GUI. To create a phone user by using the CLI, you should issue the username user-name password password command in ephone configuration mode, where username is the user name you want to assign to the user and password is the password you want to assign to the user. You should issue the username user-name password password command only in ephone configuration mode of the device that you want to assign to the user you are creating. For example, if you want user John to be able to manage the device settings of ephone 5 by using the CME GUI, you should issue the following commands on the CME router:
ephone 5 
username john password b0s0n 
To create a phone user account in the CME GUI, you should click Configure > Phones > Add Phone in the GUI, which opens the Add Phone window. In the Login Account area of the Add Phone window, you should assign the phone user a user name and password and then associate the phone user with either an existing device or a new device. Finally, click the Change button to create the user. You can also change an existing user’s password by clicking Configure > Phones in the GUI. Scroll through the list of Media Access Control (MAC) addresses in the Phone Physical ID (MAC Address) column until you find the phone you want to modify. Click on the phone you want to modify, change the password, and then click the Change button. 
You are not configuring a system administrator. The system administrator account must be configured from the CLI before the system administrator account can access the GUI. You can enable GUI access for a system administrator by issuing the web admin system name admin password string command in telephony service configuration mode. 
You are not configuring a Lightweight Directory Access Protocol (LDAP) administrator. You cannot directly synchronize users in an LDAP directory, such as Microsoft Active Directory, with CME. However, you can synchronize users in an LDAP directory with other Cisco Unified Communications products, such as Cisco Unity Connection. 
Reference:
Cisco: Enabling the GUI: Enabling GUI Access for Customer Administrators

The end user cannot log in to a temporary IP phone as if it were a permanent workstation, because Extension Mobility has not been configured for this user. Extension Mobility enables a user who works at a shared workstation to log in to and use an IP phone as if the phone were at a permanent workstation. For example, if the user programmed speed-dial options on an IP phone, those options would be stored in the user's device profile and made available to the user at any IP phone that is subscribed to Extension Mobility, as long as the user is able to log in to that IP phone. 
In order for an Extension Mobility user to properly log in to and log out of an IP phone, both the IP phone and the device profile that stores the user's preferences must be subscribed to the Extension Mobility service. In this scenario, no device profile has been associated with the end user. In addition, if the IP phone is not subscribed to Extension Mobility, the user will not be able to log in to Extension Mobility from the IP phone and an error message will appear on the IP phone's display. In addition, if the Extension Mobility Uniform Resource Locator (URL) is not correctly configured in UCM, the user will not be able to log in to Extension Mobility from the IP phone and an error message will appear on the IP phone's display. 
The end user cannot currently use Cisco Jabber for IM and Presence information. Cisco Jabber relies on Cisco Unified Presence (CUPS) and the Extensible Messaging and Presence Protocol (XMPP) for instant messaging (IM) and Presence functionality. However, in this scenario, Cisco Jabber is unable to connect to a CUPS server. 
There is not enough information in this scenario to determine whether the end user has been configured to control a desk phone from Cisco Jabber. Based on the Connection Status window, you can determine only that the Cisco Jabber client is not currently connected to a desk phone. 
The end user's primary extension is 65501. The 65501 value has been configured in the Primary Extension field. 
Reference:
Cisco: Extension Mobility and Phone Login Features

Most likely, the reason the user named Joe Cambers is not able to use Cisco Jabber's voice mail functionality is because the Cisco Unity Connection server either is down or is not installed. Cisco Unity Connection is a voice mail platform that integrates with a Cisco Unified Communications Manager (UCM) system. The Cisco Jabber client connects to Cisco Unity Connection by using a Representational State Transfer (REST) interface. 
You can display and verify the backend systems to which the Cisco Jabber client is connected by clicking the gear icon and Show Connection Status in the Cisco Jabber home window. Clicking Show Connection Status displays the Connection Status window, which provides the connectivity status of every service to which Jabber is connected or is configured to connect. Services that are preceded by a green check mark have connected successfully. Services that display Not Connected or a caution icon have not connected successfully. 
Although the user cannot use Cisco Jabber's IM and Presence functionality in this scenario, it is because the Session Initiation Protocol (SIP) trunk from UCM to the Cisco Unified Presence (CUPS) server either is down or is not installed. Cisco Jabber relies on CUPS and the Extensible Messaging and Presence Protocol (XMPP) for instant messaging (IM) and Presence functionality. Cisco Unity Connection is not required for IM and Presence functionality. 
The softphone has a SIP profile. Based on the value displayed in the SIP Profile field of the UCM Administration page in this scenario, you can determine that the softphone is configured to use the Standard SIP Profile, which is the default UCM SIP profile. 
The softphone's profile does allow Computer Telephony Integration (CTI) control. Based on the value displayed in the Allow Control of Device from CTI field, you can determine that CTI control has been enabled for the softphone. However, disabling this option would not disable Jabber's IM functionality. CTI enables the Cisco Jabber client to control aspects of a connected hardware phone, or desk phone. However, the Cisco Jabber client does not require a desk phone. Both Jabber and Cisco Unified Personal Communicator communicate with a desk phone by using the CTI Quick Buffer Encoding (CTIQBE) protocol. 
Reference:
Cisco: Feature Comparison Cisco Messaging Products (Unity Express, Unity Connection, Unity)

Most likely, the Cisco Unified Communications Manager (UCM) server's host name is cucm862. Based on the information in the browser's location bar, you can determine that the administrator in this scenario connected to the UCM Administration page by using the Uniform Resource Locator (URL) https:// cucm862:8443/ccmadmin. If the workstation were not able to resolve the host name cucm862 to an IP address, the administrator would not be able to connect to the UCM Administration page.
Although UCM can be deployed with a Domain Name System (DNS) configuration, Cisco recommends that administrators who are deploying UCM in a high availability environment not rely on DNS to connect endpoints to UCM, because doing so could create a single point of failure. Even if DNS is required for systems management purposes, Cisco recommends not using host names to configure endpoints, gateways, and UCM servers. 
There is not enough information in the scenario to determine whether the workstation is using a hosts file, or whether the UCM server is configured to use DNS name resolution. Even though the Cisco Jabber client is connecting to the UCM server by using the IP address of 192.168.51.10, the administrator's workstation has been able to resolve the UCM server's host name. The workstation could have resolved the host name of cucm862 by using either a DNS server or a local hosts file. 
When Cisco Jabber cannot connect to a server by using either DNS or an IP address, the Cannot communicate with the server message will appear on the Cisco Jabber client's login screen. The same message will appear if the server to which Cisco Jabber is configured to connect is down. In this scenario, the Cisco Jabber client has successfully connected to the UCM device at 192.168.51.10. 
The end user's user name is not Jabberwocky. In this scenario, the user's login information has not been provided. Jabberwocky is the name of the Cisco Jabber client endpoint in UCM. 
There is not enough information to determine whether a DNS server is down, because the Cisco Jabber client is not relying on DNS to connect to the UCM server. If the Cisco Jabber user logged in with a fully qualified domain name (FQDN), you could surmise that the DNS server is still functional because Cisco Jabber was able to resolve the login credential. However, you do not know what credentials were used to log in. 
Reference:
Cisco: Network Infrastructure: Domain Name System (DNS)

Of the available choices, it is most likely that the user has not been configured with an extension mobility profile, because the Default Profile dropdown field is configured to Not Selected. Extension Mobility enables a user who works at a shared workstation to log in to and use an IP phone as if the phone were at a permanent workstation. For example, if the user programmed speed-dial options on an IP phone, those options would be stored in the user's device profile and made available to the user at any IP phone that is subscribed to Extension Mobility, as long as the user is able to log in to that IP phone. When the user logs out of the IP phone, the user's specific preferences are no longer available on the IP phone. Therefore, multiple users can have different preferences associated with the same IP phone. 
In order for an Extension Mobility user to properly log in to and log out of an IP phone, both the IP phone and the device profile that stores the user's preferences must be subscribed to the Extension Mobility service. If the device profile is not subscribed to the Extension Mobility service, the user will still be able to log in to the IP phone and download the device profile. However, the user will not see the logout option on the IP phone and will not be able to log out of Extension Mobility. 
There is not enough information to determine whether the user is enabled for Cisco Unified Presence (CUPS). To enable a user for CUPS, you should first navigate to User Management > User Settings > UC Service in Cisco Unified Communications Manager (UCM) Administration. Next, click Add New. Finally, select IM and Presence from the UC Service Type dropdown field and configure the appropriate information. 
The user can monitor Presence destinations. In this scenario, the Presence Group field has been configured to use the default Standard Presence group. A presence group defines which destinations the user is allowed to monitor for presence information. The Standard Presence group is configured automatically when UCM is installed. 
The user can control associated devices by using Computer Telephony Interface (CTI). Based on the value displayed in the Allow Control of Device from CTI field, you can determine that CTI control has been enabled for the user. This field overrides the Allow Control of Device from CTI field in an associated endpoint's configuration. CTI enables a softphone, such as the Cisco Jabber client, to control aspects of a connected hardware phone, or desk phone. Both Jabber and Cisco Unified Personal Communicator communicate with a desk phone by using the CTI Quick Buffer Encoding (CTIQBE) protocol. 
Reference:
Cisco: End User Configuration

You could issue the no digit-strip command or the forward-digits all command instead of the forward-digits 3 command to enable the router to forward N11 service calls to the public switched telephone network (PSTN). N11 numbers are a group of short telephone numbers that are reserved in the North American Numbering Plan (NANP) for special services, such as emergency calls, telephone directory information, and traffic reports. 
The destination-pattern command is used to match both inbound and outbound dial peers. The sequence of dialed digits that will be matched for a dial peer can contain the digits 0 through 9, the asterisk (*), and the pound sign (#). In addition, you can use a period (.) as a wildcard symbol to refine the dialing pattern or to match multiple dial strings for a single dial peer. The command set in this scenario configures a dial peer on a Cisco Unified Communications Manager Express (CME) router to match three-digit patterns ending in 11. By default, CME only forwards digits matched by wildcards in a destination pattern, not digits that are explicitly defined in the destination pattern. Therefore, the destination-pattern .11 command configures CME to forward only the first digit in the destination pattern when a user dials an N11 service code. The no digit-strip, forward digits 3, and forward-digits all commands would modify the digits that are forwarded to the PSTN. 
The no digit-strip command configures CME to forward every digit that is matched in a destination pattern, even if the digits are explicitly matched. In this scenario, the no digit strip command would configure CME to forward all three digits of the dialed N11 code, even if the digits are explicitly matched. Therefore, issuing the no-digit strip command would complete the configuration. 
Conversely, the digit-strip command enables the default dial peer configuration behavior of stripping digits that are explicitly defined in the destination pattern. Therefore, issuing the digit-strip command would not change the behavior of CME; only the first digit in the destination pattern would be forwarded to the PSTN when a user dials an N11 service code. 
The forward-digits command configures a dial peer to forward the rightmost number of digits matched by the destination pattern, even if the digits are explicitly matched. The number of digits forwarded by CME depends on the value configured in the forward-digits command. In this scenario, the forward-digits 3 command would configure CME to forward all three digits of the dialed N11 code, even if the digits are explicitly matched. Therefore, issuing the forward-digits 3 command would complete the configuration. 
Issuing the forward-digits all command configures a dial peer to forward every digit that matches the destination pattern, even if the digits are explicitly matched. Conversely, issuing the forward-digits implicit command or the no forward-digits command configures a dial peer to perform the default behavior of stripping digits that are explicitly matched in the destination pattern. In this scenario, the forward-digits all command would configure CME to forward all three digits of the dialed N11 code, even if the digits are explicitly matched. Therefore, issuing the forward-digits all command would complete the configuration. 
The forward-digits .11 command contains invalid syntax. Wildcard patterns containing periods can be used with the destination-pattern command to match dialed strings, but they cannot be used with the forward-digits command. Therefore, issuing the forward digits .11 command would not complete the configuration. 
The prefix [2-9] command contains invalid syntax. The prefix command is used to add one or more digits to the front of the dial string before the dial string is forwarded to the destination network. You can issue the destination-pattern [2-9] command to match any single digit from 2 through 9, but you cannot issue a digit range with the prefix command. Therefore, issuing the prefix [2-9] command would not complete the configuration. 
Reference:
Cisco: Cisco IOS Voice Command Reference: forward-digits

The call will fail because the forward-digits 3 command is missing from the configuration. The forward-digits 3 command would enable the router to forward N11 service calls to the public switched telephone network (PSTN). N11 numbers are a group of short telephone numbers that are reserved in the North American Numbering Plan (NANP) for special services, such as emergency calls, telephone directory information, and traffic reports. By default, Cisco Unified Communications Manager Express (CME) only forwards digits matched by wildcards in a destination pattern, not digits that are explicitly defined in the destination pattern. Therefore, the destination-pattern .11 command configures CME to forward only the first digit in the destination pattern when a user dials an N11 service code. 
The destination pattern in this configuration is valid. The destination-pattern command is used to match both inbound and outbound dial peers. The sequence of dialed digits that will be matched for a dial peer can contain the digits 0 through 9, the asterisk (*), and the pound sign (#). In addition, you can use a period (.) as a wildcard symbol to refine the dialing pattern or to match multiple dial strings for a single dial peer. The command set in this scenario configures a dial peer on a CME router to match three-digit patterns ending in 11. 
The call will not connect to either the 911 service or the 411 service, because the CME router will forward only the first digit of the number. However, if the forward digits 3 command had been issued on the router, the call would connect to the 411 service only if the user dialed 411. Destination pattern matching on the. wildcard matches digits one-by-one as the user dials them; it does not match digits to wildcards in a given sort order. 
Reference:
Cisco: Cisco IOS Voice Command Reference: forward-digits

Of the available choices, only the destination-pattern .T command could be issued in place of the destination-pattern .11 command to enable users to dial N11 numbers without any other configuration. The destination-pattern command is used to match both inbound and outbound dial peers. The sequence of dialed digits that will be matched for a dial peer can contain the digits 0 through 9, the asterisk (*), and the pound sign (#). In addition, you can use a period (.) as a wildcard symbol to refine the dialing pattern or to match multiple dial strings for a single dial peer. The .T wildcard pattern configures the Cisco Unified Communications Manager Express (CME) router to match every digit the user dials regardless of the length of the string of digits. The router will wait until the user stops dialing before attempting to route the call. By default, CME only forwards digits matched by wildcards in a destination pattern, not digits that are explicitly defined in the destination pattern. 
None of the other destination patterns will enable users to dial all N11 numbers without additional configuration, because all of the remaining choices contain explicit matches. The command set in this scenario configures a dial peer on a CME router to match the pattern .11. In order to ensure that the N11 digits are forwarded by CME, you would additionally need to issue the forward-digits 3 command, the forward-digits all command, or the no digit-strip command on the CME router. 
Reference:
Cisco: Cisco IOS Voice Command Reference: destination-pattern