nerdexam
Microsoft

70-465 · Question #66

You need to recommend a disaster recovery solution for the Dev database. What should you include in the recommendation?

The correct answer is A. The simple recovery model and full backups. For a Dev (development) database, minimal recovery overhead is acceptable, making the simple recovery model with full backups the appropriate disaster recovery choice.

Submitted by khalil_dz· Mar 5, 2026Design and implement database solutions for SQL Server

Question

You need to recommend a disaster recovery solution for the Dev database. What should you include in the recommendation?

Options

  • AThe simple recovery model and full backups
  • BThe full recovery model, full backups, and transaction log backups
  • CThe full recovery model, full backups, and differential backups
  • DThe bulk-logged recovery model and full backups

How the community answered

(34 responses)
  • A
    74% (25)
  • B
    9% (3)
  • C
    3% (1)
  • D
    15% (5)

Why each option

For a Dev (development) database, minimal recovery overhead is acceptable, making the simple recovery model with full backups the appropriate disaster recovery choice.

AThe simple recovery model and full backupsCorrect

The simple recovery model is ideal for development databases because they do not require point-in-time recovery; data loss to the last full backup is acceptable in a dev environment. The simple recovery model automatically reclaims log space, reducing administrative overhead, and full backups provide a sufficient restore point without the complexity of managing transaction log chains.

BThe full recovery model, full backups, and transaction log backups

The full recovery model with transaction log backups is designed for production databases requiring point-in-time recovery, which is unnecessary overhead for a development database.

CThe full recovery model, full backups, and differential backups

The full recovery model with differential backups still introduces unnecessary complexity and log management requirements that are not justified for a non-production development database.

DThe bulk-logged recovery model and full backups

The bulk-logged recovery model is intended to minimize log space usage during bulk operations in production scenarios, and does not provide point-in-time recovery, making it inappropriate as a standard DR strategy even for dev databases when simple recovery suffices.

Concept tested: SQL Server recovery model selection for database tiers

Source: https://learn.microsoft.com/en-us/sql/relational-databases/backup-restore/recovery-models-sql-server

Topics

#SQL Server recovery models#Backup strategy#Disaster recovery

Community Discussion

No community discussion yet for this question.

Full 70-465 Practice