What does uploading an SSH certificate authority (CA) to a GitHub organization enable administrators to do?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Org SSH CAs let you hand out short-lived SSH certs signed by your authority — great for central key lifecycle — instead of every human uploading long-lived personal keys forever. It is not related to GHES appliance TLS certs and does not turn off audit. Pair it with short TTLs and automated issuance from your identity platform.
Full explanation below image
Full Explanation
The correct answer is issuing short-lived SSH certificates for member Git access instead of relying solely on user-uploaded SSH public keys. Organization SSH certificate authorities allow enterprises to integrate with internal certificate issuance so Git SSH auth uses managed, expiring credentials. Option A is unrelated. Option C confuses user Git SSH CAs with appliance TLS certificates in the Management Console. Option D is false; SSH CA usage does not disable auditing. Operationally, protect the CA private key offline or in HSM-backed systems, monitor issuance, and revoke by rotating CAs when compromise is suspected.