To enable second-hop remoting, what command should be executed on Server3?

To enable second-hop remoting in a Windows PowerShell environment, specific configurations and commands must be employed. The primary requirement for second-hop remoting is that it allows a PowerShell session to authenticate to a remote destination from a second system after establishing a connection from the local system.

The most essential setup for enabling second-hop remoting involves the use of CredSSP (Credential Security Support Provider), which allows credentials to be delegated securely. This cannot be achieved through any of the commands listed in the options.

The choice of "None of these choices" accurately reflects that none of the presented commands directly serve the purpose of enabling second-hop remoting. Commands like Set-RemoteAccess or Configure-PSRemoting do not specifically configure the necessary Credential Security Support Provider settings required for this functionality.

To properly enable second-hop remoting, an administrator would typically use commands related to CredSSP, which are not listed here, further emphasizing that the available options do not fit the requirement.