SC500-DISKENC-001SC-500Study guide skill: Implement and configure disk encryptionReviewed

Contoso plans to deploy new Azure VMs from a custom Linux image. The security requirements are to encrypt the temp disk and disk caches, to encrypt data flows between compute and storage, and to keep the encryption work off the VM's CPU. Which encryption option should you use?

  1. A. Azure Disk Storage server-side encryption (SSE) with customer-managed keys through a disk encryption set (DES)Incorrect
  2. B. Azure Disk Encryption (ADE)Incorrect
  3. C. Encryption at hostCorrect
  4. D. Confidential disk encryptionIncorrect
Show answer and explanation

Answer: C

Explanation

Encryption at host encrypts the temp disk, caches, and data flows between compute and storage, does not use the VM’s CPU, and works for custom images.[1] Encryption starts on the host server that the VM is allocated to, so it does not affect VM performance.[2] Note that temp disk encryption is supported only with platform-managed keys.[1]

Server-side encryption (SSE) does not encrypt the temp disk, caches, or data flows even with customer-managed keys, and Microsoft Defender for Cloud shows its disk encryption status as Unhealthy.[1] Azure Disk Encryption (ADE) uses the VM’s CPU and doesn’t work for custom Linux images, and it is scheduled for retirement on September 15, 2028, so encryption at host is recommended for new VMs.[1] Confidential disk encryption applies to the OS disk only and uses the VM’s CPU.[1]


Sources

  1. Overview of managed disk encryption optionsMicrosoft Learn · Location: Comparison · Checked
  2. Server-side encryption of Azure Disk StorageMicrosoft Learn · Location: Encryption at host - End-to-end encryption for your VM data · Checked