Explanation:
Volume for the AD DS database: F
Caching configuration for the volume that hosts the database: NONE
Explanation :
The Administering Windows Server Hybrid Core Infrastructure guidance for deploying AD DS on Azure IaaS VMs is explicit about storage placement and disk caching. The study materials state that you must not use the temporary disk and should place the AD DS database and logs on a persistent data disk:
"Do not place the Active Directory database, logs, or SYSVOL on the temporary disk (typically D: in Azure).
Data on the temporary disk is not persistent and can be lost at any time." They also direct disabling host caching on the disk that holds the AD DS database and logs to maximize resiliency and avoid write-caching data loss:
"For disks that store NTDS.dit and the AD DS log files, configure Host caching = None to prevent stale or unflushed writes and to ensure directory integrity during failures." And, for drive layout:
"Install the operating system on C: and create a separate data disk/volume for AD DS database and logs to improve reliability and recoverability." Applying these verified practices:
* Selecting F: (the new persistent data disk) meets the requirement to avoid the non-persistent D: drive and to separate AD DS from the OS volume (C:).
* Setting host caching to NONE on that disk maximizes resiliency and prevents accidental data loss by disabling volatile write caching for critical AD DS data.