A DevOps Engineer configures a delay in the out of the box online backup. What is the result of a delay that is too large?

A DevOps Engineer configures a delay in the out of the box online backup. What is the result of a delay that is too large?

• A. The backup takes more than 24 hours.
• B. Excessive reads of the repository occur.
• C. Too many file writes occur.
• D. The CPU usage is reduced too much.

Answer: (A)

Delaying an online backup throttles how quickly data is copied. If that delay is set too large, the backup process cannot finish within its expected time window, so the entire operation stretches beyond the planned duration and can take more than 24 hours. The main consequence is extended backup time, which is why this option best matches the scenario. The other effects aren’t a direct result of a larger delay: reads aren’t inherently excessive just because delay exists, writes aren’t increased by delaying (throttling would typically space them out), and CPU usage isn’t necessarily reduced to a problematic degree by a delay—the primary issue is the extended backup window.

Delaying an online backup throttles how quickly data is copied. If that delay is set too large, the backup process cannot finish within its expected time window, so the entire operation stretches beyond the planned duration and can take more than 24 hours. The main consequence is extended backup time, which is why this option best matches the scenario.

The other effects aren’t a direct result of a larger delay: reads aren’t inherently excessive just because delay exists, writes aren’t increased by delaying (throttling would typically space them out), and CPU usage isn’t necessarily reduced to a problematic degree by a delay—the primary issue is the extended backup window.