Question
You have a server named Server1 that runs Windows Server and has the Hyper-V server role installed.
You need to limit which Hyper-V module cmdlets helpdesk users can use when administering Server1 remotely.
You configure Just Enough Administration (JEA) and successfully build the role capabilities and session configuration files.
How should you complete the PowerShell command? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
Hot Area:
Explanation
[dropdown] -Path .\HyperVJeaConfig: Register-PSSessionConfiguration — The role capability (.psrc) and session configuration (.pssc) files have already been built, so the remaining step is to register the session configuration on Server1 so helpdesk users connecting remotely land in the constrained JEA endpoint; Register-PSSessionConfiguration takes the -Path to the .pssc file and the -Name of the endpoint to create. New-PSSessionConfigurationFile is wrong because that cmdlet only creates the .pssc file, which the scenario states is already done, and Enter-PSSession merely opens an interactive remote session against an endpoint that must already exist.
[dropdown] -Name 'HyperVJeaHelpDesk' -Force: .pssc — Register-PSSessionConfiguration must be pointed at a PowerShell session configuration file, and .pssc is the extension produced by New-PSSessionConfigurationFile; it defines the session type (RestrictedRemoteServer), the run-as virtual or group-managed service account, and the role definitions that map the helpdesk group to the role capability limiting them to specific Hyper-V module cmdlets. The .psrc extension belongs to the role capability file that the .pssc references rather than to the file you register, while .ps1 (script) and .psm1 (module) are not valid inputs for -Path here.
