nerdexam
Microsoft

AZ-801 · Question #102

Your network contains an Active Directory Domain Services (AD DS) domain. All domain members have Microsoft Defender Credential Guard with UEFI lock configured. In the domain, you deploy a server name

The correct answer is B. Disable the Turn on Virtualization Based Security group policy setting.. Even if Credential Guard is disabled locally, it can be re-enabled by Group Policy, so the relevant Group Policy setting must be disabled to ensure Credential Guard restrictions are completely removed.

Secure Windows Server on-premises and hybrid infrastructures

Question

Your network contains an Active Directory Domain Services (AD DS) domain. All domain members have Microsoft Defender Credential Guard with UEFI lock configured. In the domain, you deploy a server named Server1 that runs Windows Server. You disable Credential Guard on Server1. You need to ensure that Server1 is NOT subject to Credential Guard restrictions. What should you do next?

Options

  • ARun the Device Guard and Credential Guard hardware readiness tool.
  • BDisable the Turn on Virtualization Based Security group policy setting.
  • CRun dism and specify the /Disable-Feature and /FeatureName:IsolatedUserMode parameters.

How the community answered

(28 responses)
  • A
    14% (4)
  • B
    79% (22)
  • C
    7% (2)

Why each option

Even if Credential Guard is disabled locally, it can be re-enabled by Group Policy, so the relevant Group Policy setting must be disabled to ensure Credential Guard restrictions are completely removed.

ARun the Device Guard and Credential Guard hardware readiness tool.

The Device Guard and Credential Guard hardware readiness tool is used to check compatibility and status, not to disable the feature or override Group Policy enforcement.

BDisable the Turn on Virtualization Based Security group policy setting.Correct

With Credential Guard enforced by Group Policy with UEFI lock, merely disabling it locally on Server1 is insufficient as the Group Policy will reapply it upon system restart or policy refresh. To truly ensure Server1 is not subject to Credential Guard restrictions, the "Turn on Virtualization Based Security" Group Policy setting, which enables Credential Guard, must be disabled for Server1 or the organizational unit it resides in. This prevents the policy from re-enabling the feature.

CRun dism and specify the /Disable-Feature and /FeatureName:IsolatedUserMode parameters.

Using `dism /Disable-Feature /FeatureName:IsolatedUserMode` might disable some components locally, but it does not override a Group Policy that enforces Credential Guard with UEFI lock. The Group Policy must be addressed directly to remove the enforcement.

Concept tested: Disabling Credential Guard enforced by Group Policy

Source: https://learn.microsoft.com/en-us/windows/security/identity-protection/credential-guard/manage-credential-guard#disable-credential-guard

Topics

#Credential Guard#Virtualization-Based Security#Group Policy#Windows Server Security

Community Discussion

No community discussion yet for this question.

Full AZ-801 Practice