A team redeploys pooled session hosts monthly. Its profile storage and shared network have a much longer lifecycle. The team wants to reduce accidental deletion during host cleanup. Which grouping best supports this requirement?

✓ Correct answer

• Place replaceable hosts and durable shared dependencies in separate resource groups.

Resource groups should reflect shared lifecycle and ownership. Durable profiles and networking need protection beyond the replaceable session-host lifecycle. Option explanations: A. Place replaceable hosts and durable shared dependencies in separate resource groups.: Separating lifecycle boundaries lets host resources be cleaned up without deleting the durable dependencies with them. B. Place all resources in one resource group so deleting the pool also deletes its profiles.: A single deletion boundary increases the precise risk the team wants to reduce. C. Create a management group for each VM and put the VM directly inside it.: Management groups organize subscriptions; VMs are Azure resources inside resource groups. D. Put every resource in the same region and rely on the region to prevent deletion.: Region placement does not define resource deletion boundaries. Sources: Azure resource management fundamentals — https://learn.microsoft.com/en-us/entra/architecture/secure-resource-management

Read the source reference