You have two servers named Lync1 and Lync2 that have Lync Server 2013 Standard Edition deployed. The servers are located in different buildings. Lync1 hosts
response groups.
You need to ensure that Lync2 can host the response groups if Lync1 fails.
Which cmdlet should you run first?

A.
Export-CsConfiguration

B.
Export-CsRgsConfiguration

C.
Backup-CsPool

D.
Move-CsRgsConfiguration

Explanation:
http://technet.microsoft.com/en-us/library/jj205011.aspx Reference: Export-CsRgsConfiguration

Export-CsRgsConfiguration
Detailed Description
The Export-CsRgsConfiguration cmdlet and the Import-CsRgsConfiguration cmdlet enable you to export data about your current implementation of the Response
Group application (including such things as workflows, queues, agent groups, holiday sets and business hours, as well as audio files and service configuration
settings) and then later import (or re-import) that information. This can be extremely useful in a disaster recovery scenario (for example, in a case where the server
hosting the Response Group application has failed) or if you simply need to transfer the Response Group application to a different pool.
Note that the Export-CsRgsConfiguration cmdlet and the Import-CsRgsConfiguration cmdlet are designed to work only with Lync Server 2013. If you want to
migrate Response Group data from Microsoft Lync Server 2010 to Lync Server 2013, you should use the Move-CsRgsConfiguration cmdlet instead.
Export-CsRgsConfiguration -Source “ApplicationServer:atl-rgs-001.litwareinc.com” -FileName “C:\\Exports\\Rgs.zip”
To return a list of all the role-based access control (RBAC) roles this cmdlet has been assigned to (including any custom RBAC roles you have created yourself),
run the following command from the Windows PowerShell command-line interface prompt:
Get-CsAdminRole | Where-Object {$_.Cmdlets match “Export-CsRgsConfiguration”}
Lync Server Control Panel: The functions carried out by the Export-CsRgsConfiguration cmdlet are not available in the Lync Server Control Panel.