SC500-TL-001SC-500Study guide skill: Configure security features on a VM, including secure boot, virtual Trusted Platform Module (vTPM), integrity monitoring, and security typeReviewed

An administrator changed the security type of an existing Gen2 VM to Trusted launch with the default settings and installed the Guest Attestation extension. The VM uses only signed OS components. However, remote attestation for this VM keeps failing in Microsoft Defender for Cloud, so boot integrity monitoring doesn't work. What should you do?

  1. A. Enable Secure Boot on the VMCorrect
  2. B. Remove and reinstall the Guest Attestation extensionIncorrect
  3. C. Roll the security type back to Standard and then enable Trusted launch againIncorrect
  4. D. Register the Trusted Launch as default (TLaD) feature on the subscriptionIncorrect
Show answer and explanation

Answer: A

Explanation

When you enable Trusted launch on an existing VM, vTPM is enabled by default but Secure Boot isn’t.[2] For boot integrity monitoring, Defender for Cloud can remotely validate the boot only when Secure Boot and vTPM are enabled and the Attestation extension is installed, and attestation fails if Secure Boot is disabled.[1] Because the VM doesn’t use unsigned kernels or drivers, enabling Secure Boot is recommended.[2]

The extension is already installed and the cause is the disabled Secure Boot, so reinstalling the extension won’t stop attestation from failing.[1] Rolling back to Standard is a one-way operation, and you can’t re-enable Trusted launch on the same VM afterward.[2] Trusted Launch as default (TLaD) applies to new Gen2 VMs and scale sets, so it doesn’t change an existing VM.[1]


Sources

  1. Trusted Launch for Azure virtual machinesMicrosoft Learn · Location: Microsoft Defender for Cloud integration / (General Availability) Trusted Launch as default · Checked
  2. Enable Trusted launch on existing Azure Gen2 VMsMicrosoft Learn · Location: Enable Trusted launch on an existing VM / Roll back · Checked