How does PowerProtect Data Manager ensure data integrity during a file system backup?

Question

Options

• ABy locking the file system
• BThrough checksum verification
• CBy creating a file system snapshot
• DThrough differential backup techniques

• A
  4% (1)
• B
  86% (24)
• C
  4% (1)
• D
  7% (2)

Explanation

Checksum verification (B) is how PowerProtect Data Manager validates data integrity - it computes a mathematical hash of the data before and after backup, confirming the copy is bit-for-bit identical to the source. This is a direct, active mechanism for proving the backup data hasn't been corrupted or altered.

Why the distractors are wrong:

• A (Locking the file system) - Locking would freeze I/O to create consistency, but it doesn't verify integrity; it's a crash-consistency technique, not a validation mechanism.
• C (File system snapshot) - Snapshots capture a point-in-time consistent state (useful for backup consistency), but snapshots don't verify the data copied into the backup target is accurate.
• D (Differential backup) - Differentials track what changed since the last full backup to reduce backup size/time; this is an efficiency strategy, not an integrity mechanism.

Memory tip: Think "integrity = verification." The word checksum contains check - you're literally checking that the data is correct. Any time an exam question pairs "data integrity" with backup, point your mind toward hashing/checksums, not snapshot or scheduling strategies.

No community discussion yet for this question.