Contoso connected an on-premises Active Directory domain controller as an Azure Arc-enabled server. Only the Azure Monitor Agent and the Microsoft Defender for Servers extension may run on this server, and the Custom Script Extension must not be usable for remote commands even if a subscription administrator disables Azure policies. What should you do?
Show answer and explanation
Answer: A
Explanation
The Azure Connected Machine agent has security controls of its own that take precedence over any restrictions set in the cloud.[1] For Tier 0 assets such as domain controllers, the guidance is to use these local controls to restrict unused functionality: set an extension allowlist, disable the machine configuration agent, and disable remote access.[1] The documented example allowlists only the Azure Monitor Agent and the Defender for Servers extension and sets guestconfiguration.enabled and incomingconnections.enabled to false.[1] The Custom Script Extension, which isn’t on the allowlist, can’t be installed.[1]
Cloud-based restrictions like Azure Policy are good for applying controls at scale, but they don’t protect against a privileged account circumventing security measures by disabling policies.[1] Disabling the extension manager entirely is meant for when you don’t use extensions, so the Azure Monitor Agent and Defender for Servers extension couldn’t be installed either.[1] Machine enrollment is a preview feature, and it configures servers with a curated set of features rather than restricting functionality.[2]