Which two outcomes does a correctly configured github/backup-utils snapshot of GitHub Enterprise Server provide for disaster recovery? (Choose two.)
Select all correct answers, then click Submit.
Short Explanation and Infographic
Backup-utils gives you restorable Git plus app data and a path to restore onto a target appliance—not magic multi-region writes or Actions job teleportation.
Full explanation below image
Full Explanation
The GitHub Enterprise backup utilities (github/backup-utils) capture Git repository data and critical application data so administrators can restore a GHES instance after failure or corruption. A successful backup supports restoring onto a prepared target appliance following GitHub's restore procedures. It does not create automatic multi-region active-active write routing; that is an architectural capability outside of backup snapshots. It also does not live-migrate in-flight Actions jobs to GitHub.com. Administrators should schedule regular backups, verify restore drills, and store backup hosts with network access and disk capacity appropriate for full instance size. Treating backups as a substitute for HA or clustering is a common design error.