An administrator is adding a new high-availability replica to an existing GitHub Enterprise Server primary. Which step is essential in the supported HA setup process?
Select an answer to reveal the explanation.
Short Explanation and Infographic
New HA replicas need the official repl setup and sync from primary first. You don't nuke the primary disk or bolt on MSSQL Always On.
Full explanation below image
Full Explanation
Adding a GitHub Enterprise Server HA replica requires following GitHub's replication setup process: prepare a compatible appliance, configure replication (commonly involving ghe-repl-setup and enabling replication services), allow the replica to catch up with the primary, and verify health with tools such as ghe-repl-status before relying on it for failover. Destroying the primary data disk to force a weekly backup restore is not the HA add-replica procedure and risks production outage. GitHub.com organization ownership is unrelated to GHES HA wiring. MSSQL Always On is not how GHES implements appliance replication. After setup, admins should document promotion steps, network paths, and DNS or load-balancer cutover for true recovery readiness.