Operational recovery refers to routine, day-to-day recovery activity handling the everyday, relatively small-scale incidents that occur in any environment, such as an individual user accidentally deleting a file or a small set of files becoming corrupted, and restoring just that small number of affected items back to a working state, typically from the most recent backup, with minimal disruption to the broader system or business. This kind of frequent, low-impact restore activity is explicitly what distinguishes operational recovery from broader, catastrophic recovery scenarios, making it the correct classification for the scenario described. Full VM recovery (B) refers to restoring an entire virtual machine, operating system, applications, and all associated data as a single unit, a far larger-scale operation than restoring 'small numbers of files,' and is used when the whole machine, not just individual files, has been lost or corrupted. Disaster recovery (C) addresses recovery from major, often site-wide or system-wide disruptive events, such as natural disasters or catastrophic infrastructure failures, a fundamentally different scale and scope of impact than a handful of accidentally deleted files. Cloud disaster recovery (D) similarly describes a large-scale recovery strategy leveraging cloud infrastructure specifically for major outage scenarios, not routine, small-scale file-level restores. Operational recovery is correct.
Reference topic: Data Backup and Deduplication - Operational Recovery vs. Disaster Recovery.
