You need to manage Server2 remotely from Server1

Answer C is correct.

Yes.. Answer Should be “D”

This is a difficult question and many people are posting different answers. So I am still searching for the right answer.

On this article it says:
http://blogs.technet.com/b/poshchap/archive/2014/07/04/powershell-remoting-considerations.aspx

Windows Server 2012 R2

PS Remoting enabled by default.

The Enable-PSRemoting cmdlet performs the following operations:

— Runs the Set-WSManQuickConfig cmdlet, which performs the following tasks:

—– Starts the WinRM service.

—– Sets the startup type on the WinRM service to Automatic.

—– Creates a listener to accept requests on any IP address.

—– Enables a firewall exception for WS-Management communications.

—– Registers the Microsoft.PowerShell and Microsoft.PowerShell.Workflow session
configurations, if it they are not already registered.

—– Registers the Microsoft.PowerShell32 session configuration on 64-bit
computers, if it is not already registered.

—– Enables all session configurations.

—– Changes the security descriptor of all session configurations to allow
remote access.

—– Restarts the WinRM service to make the preceding changes effective.

To run this cmdlet, start Windows PowerShell with the “Run as administrator”
option.

Answer D: looks correct in the domain to workgroup scenario too.

Note: In Windows Workgroup environment, there is a need to add a trust for the server that the client initiate a connection to it.
winrm set winrm/config/client @{TrustedHosts=”%servername1%,”%servername2%”}
Verity the new settings by using the command:
“winrm enumerate winrm/config/listener”

https://support.microsoft.com/kb/555966/en-us

Another source: https://technet.microsoft.com/en-us/library/dd759202.aspx

If you are managing a remote computer from a computer that is running Windows 7, start the Windows Remote Management (WinRM) service to allow for the addition of trusted hosts. Open a Command Prompt session with elevated user rights by clicking Start , clicking All Programs , clicking Accessories , right-clicking Command Prompt , and then clicking Run as administrator . Type the following, and then press Enter : net start winrm
For remote connections in a Workgroup to Workgroup/Domain scenario, the remote computer must be added to the trusted hosts list on the source computer. To do this, run the following command on the source computer in a Command Prompt window that is opened with elevated user rights.
winrm set winrm/config/client @{TrustedHosts=”RemoteComputerName”}
For remote connections in a Workgroup to Workgroup/Domain scenario, if a user is not logged on by using the source computer’s built-in administrator account, the following WinRM registry key must be configured to allow remote access from the source computer. This change is required because of a User Account Control (UAC) limitation on non-administrator accounts that are members of the Administrators group. To change this registry key, run the following command on the source computer at a command prompt that is opened with elevated user rights.
reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v LocalAccountTokenFilterPolicy /t REG_DWORD /d 1 /f
By default, WinRM allows for a maximum of five connections to a remote computer to be active per user. To increase the limit, run the following command on the source computer, in which X represents the number of connections that you want to allow, at a command prompt that is opened with elevated user rights.
winrm s winrm/config/winrs @{MaxShellsPerUser=”X”}

By the way,
Winrs is a client, but there is still a “-machine:” key for winrm (and was “-r:” in the past). I can run winrm from server1 and the answer is the same ;-).