To prevent data loss from a redeployment of an Azure VM, what should be saved on persistent storage?

To prevent data loss from a redeployment of an Azure VM, what should be saved on persistent storage?

• A. Display settings
• B. Files on drive C
• C. Files on drive D
• D. Screen saver settings

Answer: (B)

The correct choice emphasizes the importance of preserving critical data that resides on the operating system's primary drive. In the context of Azure Virtual Machines, the operating system typically resides on the C drive. When a VM is redeployed, there is a risk that any files not stored in persistent storage can be lost, as redeployments may reset or wipe out the ephemeral disk, which is effectively the temporary storage associated with the VM. By saving files on drive C to persistent storage, such as Azure Managed Disks or other durable storage solutions like Azure Blob Storage, you ensure that important operating system configurations, applications, and files remain intact even after redeployment. This approach safeguards against data loss and facilitates recovery or continuity following maintenance actions, such as resizing or redeploying the VM, which is why it is essential to always back up critical data from the primary operational drive when planning redeployment. In contrast, files on drive D, while they can indeed be important, do not represent the same level of criticality as those on drive C in terms of system stability and operation. Display settings and screen saver settings do not have a significant impact on data loss or recovery during redeployments, focusing instead on personalized configurations that can be easily restored post-deployment.

The correct choice emphasizes the importance of preserving critical data that resides on the operating system's primary drive. In the context of Azure Virtual Machines, the operating system typically resides on the C drive. When a VM is redeployed, there is a risk that any files not stored in persistent storage can be lost, as redeployments may reset or wipe out the ephemeral disk, which is effectively the temporary storage associated with the VM.

By saving files on drive C to persistent storage, such as Azure Managed Disks or other durable storage solutions like Azure Blob Storage, you ensure that important operating system configurations, applications, and files remain intact even after redeployment. This approach safeguards against data loss and facilitates recovery or continuity following maintenance actions, such as resizing or redeploying the VM, which is why it is essential to always back up critical data from the primary operational drive when planning redeployment.

In contrast, files on drive D, while they can indeed be important, do not represent the same level of criticality as those on drive C in terms of system stability and operation. Display settings and screen saver settings do not have a significant impact on data loss or recovery during redeployments, focusing instead on personalized configurations that can be easily restored post-deployment.