Why might a GHES administrator configure external blob/object storage for the appliance?
Select an answer to reveal the explanation.
Short Explanation
You configure external blob/object storage to park bulky assets off the appliance's primary disk so you can scale storage more flexibly. It doesn't replace Git, remove local disks, or move you to GitHub Enterprise Cloud.
Full Explanation
The correct answer is to scale and separate large binary/asset storage from the primary data disk footprint. GHES can be configured to use external object storage for certain large data classes so the appliance's primary disks are not consumed entirely by bulky assets, improving operational flexibility for capacity planning. Replacing Git version control with object storage for all source code is incorrect because Git repository storage and object storage for assets are not the same; source control remains Git-based. Disabling the need for any local disk on the GHES virtual machine is incorrect because the VM still requires substantial local storage for Git data, databases, and services. Automatically migrating the instance to GitHub Enterprise Cloud is incorrect because external storage configuration is not an automatic migration path to GitHub Enterprise Cloud. Administrators must secure storage credentials, ensure private network access if required, include object storage in DR planning, and validate performance after changes.