Browse Certification Practice Tests by Exam Family

CompTIA DataSys+ DS0-002: Business Continuity

Try 10 focused CompTIA DataSys+ DS0-002 questions on Business Continuity, with explanations, then continue with IT Mastery.

Open the matching IT Mastery practice page for timed mocks, topic drills, progress tracking, explanations, and full practice.

Try CompTIA DataSys+ DS0-002 on Web View full CompTIA DataSys+ DS0-002 practice page

Topic snapshot

FieldDetail
Exam routeCompTIA DataSys+ DS0-002
Topic areaBusiness Continuity
Blueprint weight14%
Page purposeFocused sample questions before returning to mixed practice

How to use this topic drill

Use this page to isolate Business Continuity for CompTIA DataSys+ DS0-002. Work through the 10 questions first, then review the explanations and return to mixed practice in IT Mastery.

PassWhat to doWhat to record
First attemptAnswer without checking the explanation first.The fact, rule, calculation, or judgment point that controlled your answer.
ReviewRead the explanation even when you were correct.Why the best answer is stronger than the closest distractor.
RepairRepeat only missed or uncertain items after a short break.The pattern behind misses, not the answer letter.
TransferReturn to mixed practice once the topic feels stable.Whether the same skill holds up when the topic is no longer obvious.

Blueprint context: 14% of the practice outline. A focused topic score can overstate readiness if you recognize the pattern too quickly, so use it as repair work before timed mixed sets.

Sample questions

These original IT Mastery practice questions are aligned to this topic area. Use them for self-assessment, scope review, and deciding what to drill next.

Question 1

Topic: Business Continuity

A DBA is reviewing the backup strategy for an order-processing database. Requirements are: maximum data loss of 15 minutes, database available within 60 minutes after a failure, hash validation for backup integrity, and one off-site copy.

Exhibit: Backup and restore evidence

ItemEvidence
Full backupNightly at 12:00 a.m.
Transaction logsShipped every 5 minutes
Hash validationPassed on last 14 backup sets
StorageLocal disk and off-site object storage
Restore testLast full restore plus logs took 82 minutes

Which interpretation is best supported by the exhibit?

Options:

  • A. The strategy meets all stated requirements

  • B. The strategy meets data protection but misses operational recovery

  • C. The strategy is invalid because hashes were not retained off-site

  • D. The strategy misses data-loss requirements due to nightly full backups

Best answer: B

Explanation: The strategy should be evaluated against both data protection and operational recovery constraints. Data protection is supported because transaction logs are shipped every 5 minutes, which is within the 15-minute maximum data loss target, and the backup sets passed hash validation. Off-site object storage also satisfies the off-site copy requirement. Operational recovery is different: the restore test shows the database took 82 minutes to restore, which exceeds the required 60-minute availability target. A backup plan can protect data and still fail the recovery objective if restoration takes too long. The next improvement would focus on reducing restore time, such as using more frequent restore points, faster storage, snapshots, or standby recovery design.

  • Fully compliant fails because the measured restore time is longer than the required 60 minutes.
  • Nightly full backup concern fails because 5-minute transaction log shipping addresses the 15-minute data-loss target.
  • Hash retention issue fails because the stated requirement is hash validation, and the exhibit shows validation passed.

Question 2

Topic: Business Continuity

A DBA manages a 1 TB OLTP database. The business requires recovery to the previous night’s backup and a restore time under 2 hours. The weekly Sunday maintenance window can support a full backup, but weeknight backup windows are short. Restore testing shows that applying a long chain of nightly incremental backups exceeds the restore-time target by Friday. Which backup schedule is the best professional decision?

Options:

  • A. Weekly full backup only

  • B. Weekly full backup plus nightly incremental backups

  • C. Weekly full backup plus nightly differential backups

  • D. Daily full backups retained off-site

Best answer: C

Explanation: Backup type selection balances restore speed, storage use, and operating windows. A full backup provides the baseline, but daily full backups usually consume the most storage and backup-window time. Incremental backups usually use the least storage and shortest daily window, but restores require the last full backup plus every incremental in sequence. Differential backups grow during the week, but restore needs only the last full backup plus the latest differential, making recovery faster than a long incremental chain while avoiding daily full backups. In this scenario, the failed restore test makes the incremental chain a poor fit for the RTO.

  • Incremental chain fails because restore testing already showed the growing sequence of incrementals exceeds the 2-hour target.
  • Daily full backups may restore quickly, but they ignore the short weeknight window and constrained storage.
  • Weekly full only fails the previous-night recovery requirement because it can lose several days of changes.

Question 3

Topic: Business Continuity

A company runs an order database in one region. The disaster recovery requirement states that if the entire region becomes unavailable, the application team must redirect users to a synchronized database in a distant region with data loss measured in minutes. Local server and disk failures are handled separately. Which implementation concept best meets this requirement?

Options:

  • A. Geo-replication

  • B. Local replication

  • C. Database mirroring

  • D. Component redundancy

Best answer: A

Explanation: Geo-replication is the best fit when the recovery target must survive a site or regional outage. The key requirement is not just another copy of the database, but another copy far enough away that the same regional failure is unlikely to affect both locations. Because the stem also gives an acceptable data loss window measured in minutes, asynchronous replication to another region is a realistic continuity design. Local high availability still matters, but it addresses smaller failures such as a server, disk, or zone issue rather than loss of the entire region. The main takeaway is to match the scope of the failure to the scope of the copy.

  • Mirroring is usually aimed at a closely paired database copy and does not by itself imply geographic separation.
  • Component redundancy protects against hardware or path failures, but it does not create a recoverable database in another region.
  • Local replication can improve availability within a site or region, but it does not satisfy the regional outage requirement.

Question 4

Topic: Business Continuity

A DBA supports an on-premises OLTP database that stores customer orders. The business requires a 15-minute RPO, 7-year retention for audit evidence, and proof that backup copies have not been altered. Recent backup jobs show “successful,” but no restore test has been performed. Which action is the BEST professional decision?

Options:

  • A. Store full and log backups off-site immutably, validate hashes, and schedule restore tests.

  • B. Encrypt backup files and delete older copies after each full backup.

  • C. Retain backup software success alerts as the primary audit evidence.

  • D. Keep local storage snapshots on the database array for fast rollback.

Best answer: A

Explanation: Backup assurance is not just confirming that a job completed. For this database, the DBA must preserve recoverability, integrity, and retention evidence. Off-site immutable storage reduces the risk that the same site failure, storage failure, or ransomware event destroys the usable backup set. Full and log backups support the short RPO, while hash validation provides evidence that stored backup files have not changed. Scheduled restore tests prove that the backup chain can actually be used to recover the database. Encryption may still be required for confidentiality, but it does not replace integrity validation or restore testing.

  • Local snapshots help with fast rollback but can share the same failure domain and do not prove long-term retention or restore viability.
  • Success alerts show that a backup job reported completion, not that the backup is unaltered or restorable.
  • Encryption only protects confidentiality, and deleting older copies conflicts with the 7-year retention requirement.

Question 5

Topic: Business Continuity

A company is designing continuity for an order-processing OLTP database. The database must continue operating if one availability zone fails, must not lose committed transactions during that failure, and must prevent two nodes from accepting writes at the same time. Which design best meets these requirements?

Options:

  • A. Multi-zone synchronous replication with quorum-based failover

  • B. Nightly full backups stored in a second zone

  • C. Active-active writes in two zones with asynchronous replication

  • D. Application servers in two zones using one database node

Best answer: A

Explanation: The design must address two continuity concerns at the same time: infrastructure failure and database consistency. Placing database nodes in more than one zone handles the infrastructure-failure requirement. Synchronous replication addresses the consistency requirement because a transaction is not considered committed until it is protected on the replica according to the design. Quorum-based failover or a witness mechanism helps ensure only one node becomes writable, reducing split-brain risk. Backups and application-tier redundancy are useful, but they do not provide immediate database failover with near-zero committed transaction loss.

  • Backups only support recovery after a failure, but they do not keep the OLTP database continuously available.
  • Asynchronous active-active can lose recent commits and may create conflicting writes during a failure.
  • App-tier redundancy does not remove the single database node as a point of failure.

Question 6

Topic: Business Continuity

A quarterly restore test for a customer database restores the data successfully in 12 minutes. The application remains unavailable for 45 minutes because the team did not validate DNS cutover and firewall rules for the DR site. The RTO is 30 minutes. Which improvement should the DBA implement for the next DR test?

Options:

  • A. Add end-to-end connectivity validation to the DR runbook

  • B. Increase the database backup frequency

  • C. Add another off-site archive copy

  • D. Replace the next restore test with a tabletop review

Best answer: A

Explanation: A DR test should be improved based on the specific gap it reveals. In this case, the database restore met the time need, but the service still missed the RTO because dependent recovery steps were not tested. The best improvement is to make the next exercise end-to-end: include DNS cutover, firewall validation, application login or health checks, owners, and timing in the DR runbook. That tests whether the restored database can actually support the application within the recovery window. Backup frequency and extra archive copies address recoverability, but they do not fix a failed cutover dependency.

  • Backup frequency targets RPO and data loss, but the restore already completed quickly enough.
  • Off-site archive improves backup resilience, but it does not validate DNS, firewall, or application access.
  • Tabletop only may improve discussion, but it reduces technical validation after a hands-on readiness gap was found.

Question 7

Topic: Business Continuity

A DBA supports a 1.8 TB on-premises OLTP database that receives transactions all day. The business requires an RPO of 15 minutes or less and an RTO of 2 hours or less. The overnight backup window is 4 hours, and finance policy requires encrypted off-site storage, hash validation, and monthly restore testing. Which backup strategy is the best professional decision?

Options:

  • A. Weekly full and nightly differential backups with encrypted off-site copies

  • B. Synchronous replication to a secondary server with no separate backup validation process

  • C. Weekly full, nightly differential, and 15-minute transaction log backups with encrypted off-site copies, hash checks, and monthly restore tests

  • D. Nightly full backups to local storage with weekly manual restore testing

Best answer: C

Explanation: A backup strategy must satisfy both data protection and operational recovery constraints. The 15-minute RPO requires a recoverable copy of changes at least every 15 minutes, so transaction log backups are needed for this transactional workload. Weekly full backups plus nightly differential backups reduce the daily backup window and shorten restore work compared with restoring a full backup and many days of logs. Encrypted off-site copies address storage and protection requirements, while hash validation and monthly restore testing prove that backups are usable, not just completed. Replication can improve availability, but it does not replace validated backups for corruption, deletion, or ransomware recovery.

  • Nightly full only misses the 15-minute RPO because a full backup once per day can lose up to a day of transactions.
  • No log backups fails because full and differential backups alone do not capture changes within the required 15-minute window.
  • Replication alone is not enough because it can replicate corruption or deletion and does not satisfy hash validation or restore testing.

Question 8

Topic: Business Continuity

A payment database must be recovered after the primary server fails. The recovery plan requires the service to return within 15 minutes and prohibits losing any committed payment transactions.

Exhibit: Replica status

TargetStatus
Sync replicaHealthy; all commits hardened; failover not automatic
Async replicaHealthy; approximately 8 minutes behind
Last full backupCompleted 6 hours ago

Which recovery recommendation best protects availability without compromising data integrity?

Options:

  • A. Manually fail over to the synchronous replica after validation

  • B. Restore the last full backup to a new server

  • C. Force the failed primary online and repair damaged pages

  • D. Promote the asynchronous replica immediately

Best answer: A

Explanation: The key trade-off is availability versus data integrity. The requirement allows up to 15 minutes to restore service, but it does not allow committed payment transactions to be lost. A healthy synchronous replica with all commits hardened is the safest recovery target because it should contain the committed transaction set from the primary. Manual validation before failover is appropriate when automatic failover is disabled and integrity must be protected. The asynchronous replica may improve speed, but being 8 minutes behind creates a data-loss risk. A 6-hour-old full backup would also lose later committed work unless additional logs are restored, which the stem does not provide.

  • Promoting the asynchronous replica is tempting for speed, but the lag violates the no-data-loss requirement.
  • Restoring only the full backup does not meet integrity needs because committed transactions after the backup are not included.
  • Forcing repair on the failed primary risks data loss or corruption and is not the safest availability-preserving recovery path.

Question 9

Topic: Business Continuity

A DBA manages a transactional payroll database with nightly full backups and 15-minute transaction log backups stored off-site. The business requires proof that backups can be restored without affecting production and that restored data is not corrupted. Which action is the BEST professional decision before a failure occurs?

Options:

  • A. Restore the latest backup over production during a maintenance window

  • B. Schedule isolated restore tests with hash validation and integrity checks

  • C. Keep additional off-site copies without performing restores

  • D. Review backup job success alerts each morning

Best answer: B

Explanation: Backup usability is confirmed by testing the restore process, not only by confirming that backup jobs completed. For a production payroll database, the safest approach is to restore backups into an isolated test or recovery environment, validate the backup files with hashes or checksums, and run database integrity checks after restore. This verifies that the files are readable, the restore procedure works, encryption or access requirements are handled, and the restored database is not corrupted. The test should be documented and repeated on a schedule aligned with recovery requirements. Extra copies and alerts are useful controls, but they do not prove that a backup can actually be restored.

  • Job success only fails because a completed backup job can still produce a file that is unreadable, incomplete, or unusable during restore.
  • Production overwrite creates unnecessary operational risk and violates the requirement to avoid affecting production.
  • Extra copies only improves storage resilience but does not validate restore steps or restored data integrity.

Question 10

Topic: Business Continuity

A DBA reviews the continuity design for an on-premises OLTP database that supports order processing. The database runs on two clustered servers in separate racks, and failover testing between the servers succeeds. However, both servers use the same storage array and the same storage controller path. The business requires minimizing downtime without moving the system to a new platform. What is the BEST professional decision?

Options:

  • A. Document the successful server failover test as sufficient

  • B. Remove the shared storage dependency from the HA design

  • C. Increase the frequency of full database backups

  • D. Add more CPU and memory to both database servers

Best answer: B

Explanation: Single-point-of-failure analysis looks past visible redundancy and checks whether redundant components still depend on one shared component. In this scenario, the two database servers can fail over, but both rely on the same storage array and controller path. A failure there can stop both nodes, so the continuity design does not meet the availability intent. The appropriate decision is to remove or mitigate that shared dependency, such as by using redundant storage paths/controllers, replicated storage, or another approved design that keeps storage failure from disabling both servers. Backups help recovery, but they do not provide high availability during a storage outage.

  • More backups improve recoverability, but they do not prevent downtime from the shared storage component.
  • More server resources address capacity or performance, not the single storage dependency.
  • Successful node failover proves server-level redundancy only; it does not validate the full continuity design.

Continue with full practice

Use the CompTIA DataSys+ DS0-002 Practice Test page for the full IT Mastery practice bank, mixed-topic practice, timed mock exams, explanations, and web/mobile app access.

Try CompTIA DataSys+ DS0-002 on Web View CompTIA DataSys+ DS0-002 Practice Test

Free review resource

Use the full IT Mastery practice page above for the latest review links and practice page.

Revised on Thursday, May 28, 2026