The team can discover silent profile corruption up to 14 days after it occurs. The current backup policy keeps only seven days of healthy recovery points. A recent incident was noticed on day 12. Which policy change addresses the identified gap?

✓ Correct answer

• Retain recovery history beyond the possible detection delay with an appropriate safety margin, and test restoring a healthy point.

Set retention for detection and recovery needs as well as backup frequency for RPO. Frequent backups with too-short retention can still leave no healthy historical state. Option explanations: A. Keep seven-day retention but double the current live-share replicas.: Current-state redundancy does not extend historical backup retention. B. Keep seven-day retention but increase the desktop VM session limit.: Session allocation cannot preserve an older healthy profile version. C. Retain recovery history beyond the possible detection delay with an appropriate safety margin, and test restoring a healthy point.: A healthy point must still exist when corruption is detected; retention must cover that delay. D. Take more frequent backups while retaining them all for only seven days.: Higher frequency improves point granularity but does not solve a 12-day detection delay. Sources: Azure Files backup overview — https://learn.microsoft.com/en-us/azure/backup/azure-file-share-backup-overview

Read the source reference