Courseiva
Secure Windows Server InfrastructuremediumMultiple ChoiceObjective-mapped

AZ-802 Secure Windows Server Infrastructure Practice Question

You need to ensure that only authorized administrative users can access the server via PowerShell Remoting. Which security control should you implement?

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

Modify the Session Configuration security descriptor.

Restricting access to PowerShell Remoting is vital to prevent unauthorized remote management. By modifying the Security Descriptor of the WinRM session configuration, you can explicitly define which users or groups have the 'Access' and 'Execute' permissions. This is a critical step in maintaining a secure administrative surface, ensuring that only those with the necessary authorization can establish remote sessions, thereby mitigating the risk of lateral movement by attackers using PowerShell.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • Modify the Session Configuration security descriptor.

    Why this is correct

    The PowerShell session configuration (WSMan) includes a security descriptor that acts as an access control list. By using 'Set-PSSessionConfiguration', you can replace the default permissions with a custom security descriptor, effectively restricting which identities are allowed to connect to the server's PowerShell remoting endpoint, thereby hardening the remote management interface.

  • Configure the local Administrators group only.

    Why it's wrong here

    While members of the local Administrators group have broad rights, relying solely on this membership is not sufficient for fine-grained control of remote management. PowerShell remoting allows for specific configuration sets, and managing access via the PSSession security descriptor is a more precise and secure method than relying on standard group memberships.

  • Enable Credential Guard for PowerShell.

    Why it's wrong here

    Credential Guard protects identity secrets from memory-based theft but does not control who is authorized to initiate a remote PowerShell session. The session authorization itself is governed by the WinRM security descriptor, not by the credential protection mechanisms provided by the VBS-based Credential Guard feature.

  • Disable the WinRM service entirely.

    Why it's wrong here

    Disabling the WinRM service would stop all remote management, which prevents legitimate administration. The requirement is to restrict access to authorized users, not to eliminate the capability entirely. Proper security management involves allowing access only for specific, vetted identities, not by shutting down the service, which would hinder operational efficiency.

About these practice questions

This AZ-802 question is part of Courseiva's 116-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written and reviewed by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

Last reviewed September 2026 · checked against the official Microsoft exam blueprint

This AZ-802 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-802 exam.