You support a Microsoft Lync Server 2013 Enterprise pool deployed in a high availability configuration for Back End Servers named Backend1 and Backend2. You execute the Get-CSDatabaseMirrorState cmdlet and discover the following errors. WARNING: Cannot connect to database server "BackEnd2.contoso.com".Message: A network- related or instance-specific error occurred whileestablishing a connection to SQL Server. The server was not found or was notaccessible. Verify that the instance name is correct and that SQL Server isconfigured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)DatabaseName : rtcabStateOnPrimary : PrincipalStateOnMirror : StatusUnavailableMirroringStatusOnPrimary :synchronizedMirroringStatusOnMirror :DatabaseName : rtcxdsStateOnPrimary : PrincipalStateOnMirror : StatusUnavailableMirroringStatusOnPrimary :synchronizedMirroringStatusOnMirror You need to resolve the connectivity issue and bring up the mirror databases to the synchronized state between the Back End Servers. What should you do?

• A. From the mirror Back End Server, create the inbound rule on the firewall.
• B. From the Front End Server, create the inbound rule on the firewall.
• C. Run the Invoke-CsPoolFailOver cmdlet.
• D. Run the Test-CsDatabase cmdlet.

You support Microsoft Lync Server 2013 servers in your customer's company network. Lync is configured as a federated partner with several business partners. The partners use Lync deployed with hosting providers. Your Lync servers are configured as an open federation. Lync users inform you that they are unable to communicate with a partner domain named fabrikam.com. You contact the partner and discover that they have recently changed their proxy server name. You need to restore communication with the federated partner. Which two cmdlets should you run? (Each correct answer presents part of the solution. Choose two.)

• A. Remove-CsHostingProvider -Identity "Fabrikam.com"
• B. Get-CsProxyConfiguration -Filter "service:*" | Remove-CsProxyConfiguration
• C. Set-CsHostingProvider -Identity "Fabrikam.com" -VerificationLevel "AlwaysUnverifiable"
• D. New-CsHostingProvider -Identity Fabrikam.com -ProxyFqdn "server1.fabrikam.com" -Enabled $True

You support a Microsoft Lync Server 2013 environment that includes:
-Two Enterprise consolidated Lync servers in a single pool,
-Two Edge consolidated Lync servers in a single pool,
-One Microsoft Office Web Apps server, and
-One reverse HTTP(S) proxy server. Microsoft Exchange 2010/Microsoft Outlook 2013 are used for internal email and Unified Messaging. The email solution has been used within the company for an extended time without any issues. Unified Messaging has been configured and set
up as part of the Lync 2013 implementation project. You plan to deploy Enterprise Voice for all users, including users who have Lync Phone Edition (LPE) devices that are connected by using a LAN cable and a USB cable. You begin migrating test accounts. When a test user signs into Outlook 2013 and Lync 2013, all communications appear to be working as expected. Outlook creates the user profile as expected and logs into the test user mailbox. The test user signs into Lync as expected and is able to communicate with Exchange by using Exchange Web Services (EWS).
After the test user signs into Lync, a prompt is displayed requesting user credentials for the Lync Phone Edition device. The test user enters his credentials and the phone signs into Lync; however, after a short period of time, a yellow warning triangle appears on every test LPE device. In reviewing the LPE device for errors, you discover that Exchange integration is failing with the following error: "Connection to Microsoft Exchange is unavailable. Please contact your support team." Logs from the LPE Device are displayed in the Exhibit 1. (Click the Exhibit button.)

Internet Information Services (IIS) logs on the Exchange Client Access server (CAS) are displayed in Exhibit 2. (Click the Exhibit button.)

You need to ensure that the LPE device can authenticate to EWS. What should you do?

• A. Update the certificate chain on the Exchange CAS.
• B. Remove the Lync Client certificates for the test user from the Lync server.
• C. Reissue the current Exchange CAS server certificate and bind to the IIS service.
• D. Update the Lync server internal web services certificate on each front-end pool server.

You support a customer whose network environment includes Microsoft Lync 2013 deployed in a datacenter that has two pools, named PoolA and PoolB. Both PoolA and PoolB have Microsoft Lync Server 2013 installed. You use the Lync Management Shell for all administrative actions. You run the Invoke-CsPoolFailover
PowerShell cmdlet and you receive the following message: Invoke-CsPoolFailOver: This Front-end pool "poolA.contoso.com" is specified in topology as the next hop for the Edge server. Failing over this pool may cause External access/Federation/Split- domain/XMPP features to stop working. Please use Topology Builder to change the Edge internal next hop setting to point to a different Front-end pool, before you proceed. You need to fail over PoolA only. What should you do?

• A. Run the Set-CsEdgeServer PowerShell cmdlet.
• B. Run the Get-CsDatabaseMirrorState cmdlet, and then run the Invoke-CSManagementServerFailover PowerShell cmdlet.
• C. Run the Set-CsAccessEdgeConfiguration cmdlet.
• D. Run the Set- CsAVEdgeConfiguration cmdlet

You support a customer whose network environment includes Microsoft Lync Server 2013. All users are members of an Active Directory Domain Services (AD DS) domain. All users are using the Global client policy. AddressBookAvailability is set to WebSearchOnly. For some users in Active Directory, you change the attributes that relate to title and department. You discover that these attributes are not reflected in the users' contact cards in Lync 2013. You need to update the Lync address book immediately to reflect the changes you made. What should you do?

• A. Run the Update-CsAddressBook cmdlet.
• B. Run the Set-CsClientPolicy-Identity Global-EnableExchangeContactSync $true cmdlet.
• C. Change the Global Client Policy to use WebSeachandFileDownload.
• D. Run the Update-CsUserDatabase cmdlet.