Why might a GHES administrator configure external blob/object storage for the appliance?
Select an answer to reveal the explanation.
Short Explanation and Infographic
External object storage is about parking bulky assets — think large blobs and attachments — off the main appliance disks so you can grow storage more flexibly. It does not turn Git into S3-only, remove the need for local disks, or magically move you to GHEC. Plan credentials, network paths, and backup coverage for that external store just like any other critical dependency.
Full explanation below image
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. Option A is incorrect: Git repository storage and object storage for assets are not the same; source control remains Git-based. Option B is incorrect: the VM still requires substantial local storage for Git data, databases, and services. Option D is incorrect: 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.