While GitHub Enterprise Server is in maintenance mode, which user-facing capability remains available for troubleshooting?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Maintenance mode is the 'closed for renovations' sign on your GHES instance. Regular users can't browse, push, or hit the API the way they usually do — that's the point. Admins still get into the site admin area and Management Console so they can finish upgrades, backups, or repairs. When you're done, take maintenance mode off and double-check that replication and jobs look healthy before declaring the outage over.
Full explanation below image
Full Explanation
The correct answer is site admin and Management Console administrative access. Maintenance mode is intended for planned work such as upgrades, restores, or major configuration changes. It blocks ordinary end-user web, Git, and API traffic so the instance is not modified during the window. Administrators retain access to the Management Console and site admin interfaces so they can complete operational tasks. Option A is wrong because normal Git operations are disabled for users during maintenance. Option C is wrong because Actions and other application workloads are not treated as available production features while the appliance is in maintenance. Option D is wrong because public and member API access is restricted. Operationally, communicate the window, enable maintenance mode, perform the change, verify services (including any replica), then disable maintenance mode and monitor error rates.