Microsoft Lync 2013 Depth Support Engineer Sample Questions:

1. You support a customer who administers Microsoft Lync Server 2013 Enterprise servers in his company. The pool named lync.contoso.com is configured with the session initiation protocol (SIP) domain contoso.com. The internal split-DNS domain
contoso.com contains the following records: _gc._tcpSRV priority 0, weight 100, port 3268 dc1.contoso.com_ldap._tcpSRV priority 0, weight 100, port 389 dc1.contoso.com_kerberos._tcpSRV priority 0, weight 100, port 88 dc1.contoso.com_sipinternal._tcpSRV priority 0, weight 0, port 5061, lync.contoso.com _sip._tlsSRV priority 0, weight 0, port 5061, lync.contoso.com EnterpriseCA A 192.168.10.5Admin A 192.168.10.10Lync A 192.168.10.10Lyncdiscoverinternal A 192.168.10.10Exchange2010 A 192.168.10.4OWA A 192.168.10.4DC1 A 192.168.10.3Sip A
192.168.10.10 Users who are running Lync Mobile on their mobile devices report that when they attempt to retrieve calendar information, they receive an error that references a Microsoft Exchange Web Services connectivity issue. You need to ensure that users are able to receive calendar information from Lync Mobile devices. What should you do?

A) Create the following service record in DNS: _lyncdiscover._tcp.contoso.com SRV Priority 0, weight 0, port 5061, Lync.contoso.com
B) Reconfigure Dynamic Host Configuration Protocol (DHCP) option 43 to point to EnterpriseCA.contoso.local.
C) Reconfigure Dynamic Host Configuration Protocol (DHCP) option 120 to point to DC1.contoso.local.
D) Create the following host record in DNS: Autodiscover.contoso.com A 192.168.10.4

2. You support a customer whose company network includes Microsoft Lync Server 2013 with web conferencing deployed at a main site named Washington and a branch site named Redmond. All users have Lync 2013 and Microsoft Outlook 2013 installed. UserA and UserB are both Lync- enabled users at your customer's main site. UserA has the Global conferencing policy and the Washington meeting configuration assigned to his account. UserB has the Redmond conferencing policy and the Global meeting configuration assigned to his account. In online meetings that UserA schedules, users can collaborate using videoconferencing. In online meetings scheduled by UserB, videoconferencing is not available. You need to determine
why videoconferencing is unavailable in UserB's meetings.
Which cmdlet should you run from the Lync Server Management Shell?

A) Get-CSMeetingConfiguration -Identity Global
B) Get-CSConferencingPolicy -Identity Redmond
C) Get-CSConferencingPolicy -Identity Global
D) Get-CSMeetingConfiguration -Identity Redmond

3. You support a customer who is upgrading from Lync 2010 Group Chat to Lync 2013 Persistent Chat. Users are Session Initiation Protocol (SIP) enabled members of a single Active Directory Domain Services (AD DS) domain. Group Chat clients connect by using a well-known user named [email protected]. The Lookup service registers
with the Lync server to receive incoming requests.
Your customer's Persistent Chat pool fully qualified domain name (FQDN) is named pchatpool.litwareinc.com. When users sign out of Lync and then sign in again by using the Lync 2010 Group Chat client, they are able to access their data without needing to change any configuration. You need to configure Lync Server 2013 persistent chat to support legacy Group Chat clients. Which cmdlet should you run?

A) Set-CsPersistentChatRoom -Identity IT -Presenters
@{Add="sip:ocschat(g)litwareinc.com"}
B) New-CsTrustedApplicationEndpoint -Applicationld pchat -
TrustedApplicationPoolFqdn pchatpool.litware.com -SipAddress sip:
[email protected]
C) New-CsPersistentChatEndpoint
-SipAddress
sip:[email protected] -
PersistentChatPoolFqdn pchatpool.litware.com
D) $cred1 = Get-Credential "litwareinc\pilar" $cred2 = Get-Credential
"litwareinc\ocschat"
Test-CsPersistentChatMessage -TargetFqdn pchatpool.litwareinc.com -
SenderSipAddress "sip:[email protected]" -
SenderCredential
$cred1 -ReceiverSipAddress "sip:ocschat@)litwareinc.com" -
ReceiverCredential $cred2

4. HOTSPOT Your customer supports a Microsoft Lync Server 2013 environment. Users are unable to add a federated user to an AV conference. The affected users can view the federated user's presence, and the internal users' External Access Policy is configured to allow communication with federated users. You attempt to initiate a Telnet session to TCP port 5062 from your Lync Server 2013 Front End Server to your Lync Server 2013 Edge Server's internal interface, but you receive an error message that includes "Could not open a connection to the host, on port 5062: Connect failed." You decide to work with the network team to ensure that the Lync Server 2013 environment has the appropriate connectivity to ensure media path negotiation and media flow between the front end server and the Edge server. You need to ensure that users are able to add federated users to an AV conference. Which network ports should you confirm are open on the Lync Server 2013 Front End Server and on the Lync Server 2013 Edge Server? To answer, select the appropriate server or servers for each port in the answer area.

5. You administer a Microsoft Lync Server 2010 Standard Edition server in your network environment. You deploy a Microsoft Lync Server 2013 Standard Edition server. You want to migrate users from Lync Server 2010 to Lync Server 2013. You migrate a test account from Lync Server 2010 to Lync Server 2013. You start the Lync 2013 client on one of your test computers and start testing various modalities. During testing, you decide to test the Meet Now functionality in Lync 2013 client. Meet Now starts a conference
and fails to connect. You start Clslogging.exe. You generate a log that includes the following information:

You need to identify the cause of the issue. What should you do first?

A) Right-click the error message and select Go to nearest entry in trace viewer.
B) Start WireShark and perform the Meet Now test again.
C) Click Show Call Flow Window.
D) Open another log file from the Lync client in Snooper.

Solutions: