What should administrators evaluate when adopting GitHub Enterprise Cloud features related to data residency?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Data residency is about where customer data lives at rest for regulatory comfort — EU vs US etc. when the product offers those choices. Evaluate contracts and which data classes are covered. It is not FTP-only Git, public audit logs, or dropping MFA for a region.
Full explanation below image
Full Explanation
The correct answer is assessing whether residency options meet regulatory and contractual requirements. GHEC data residency offerings constrain where certain enterprise data is stored; admins must verify scope (which data types, which features) against legal needs. Option B is false. Option C is false. Option D is false and weakens security. Involve legal/compliance early, document residual risks for data that may still process outside the region, and align integrations that copy data out to third-party SaaS so residency promises are not accidentally voided by uncontrolled exports.