Before a major upgrade to the county permitting database, the team needs a quick restore point on the same host, while the disaster-recovery site must stay nearly current for day-to-day failover. Which pairing best matches those needs?
Select an answer to reveal the explanation.
Short Explanation
Think of a snapshot like a bookmark on the same book—you can flip back fast if the upgrade goes sideways. Replication is the overnight courier keeping a twin copy at the DR site almost current. Use both for different jobs: local rollback vs near-real-time DR.
Full Explanation
Snapshots capture a point-in-time image useful for rapid rollback on the primary system after a risky change such as a major database upgrade. Replication continuously or frequently copies data to another site so recovery objectives for near-real-time failover can be met. Yearly archives and log-only approaches do not deliver either a convenient local restore point or near-current DR readiness. Matching each mechanism to its purpose strengthens resilience architecture.