Which two uses of repository custom properties are valuable for enterprise administrators? (Choose two)
Select all correct answers, then click Submit.
Short Explanation and Infographic
Custom properties are structured labels on repos — think PCI=true or criticality=high — so you can find them and aim rulesets at the right population. They do not rewrite Git objects or turn off HTTPS per repo. Get a property taxonomy agreed with security/compliance before you invent fifty free-text fields nobody maintains.
Full explanation below image
Full Explanation
The correct answers are metadata tagging (classification/compliance tier) and ruleset targeting by property values. Custom properties provide governed metadata on repositories that scales better than ad-hoc topics alone for policy engines. Option B is false; Git object identity remains commit SHAs. Option D is false; HTTPS access is not toggled per repo via custom properties. Define allowed property values centrally, require properties on new repos where possible, and align security configurations and rulesets to those values.