A recovery drill will use cloned hosts while production users remain active. The proposed test points the cloned hosts to the live read-write profile share. What should be corrected before the drill?

✓ Correct answer

• Use an isolated test profile/data copy and controlled test connectivity so the drill cannot write to live user state.

Recovery testing should validate a representative workload against controlled copies and paths. Protect production from conflicting writes while measuring the full recovery procedure. Option explanations: A. Disable test telemetry so no production operator sees the drill.: Monitoring visibility does not prevent live data writes and is needed to assess recovery. B. Use the live profile share and assume a test host cannot modify it.: A host with write permissions can alter live data regardless of its test label. C. Change only the test host names and retain the same live read-write containers.: Different host names do not isolate profile writes. D. Use an isolated test profile/data copy and controlled test connectivity so the drill cannot write to live user state.: Isolation lets the team test restoration without conflicting with production writers. Sources: Multiregion business continuity — https://learn.microsoft.com/en-us/azure/architecture/example-scenario/azure-virtual-desktop/azure-virtual-desktop-multi-region-bcdr; Disaster recovery concepts — https://learn.microsoft.com/en-us/azure/virtual-desktop/disaster-recovery-concepts

Read the source reference