A development team is building proprietary microservices and needs a central location to store the Git source code so that remote employees can clone, push, and open pull requests. The repository must remain inaccessible to the general Internet while still providing granular role-based permissions for selected developers and reviewers. Which storage option BEST meets these requirements?
A private repository on a version-control platform with access restricted to approved organization members
A public pastebin-style sharing site that automatically deletes files after 30 days
An FTP server placed in the company's DMZ with anonymous read permissions enabled
A public repository that allows read-only access to anyone on the Internet
A private repository on a modern version-control platform limits visibility to explicitly granted users while supporting standard collaboration features such as cloning, branching, and pull requests. A public repository, an anonymous FTP server, or a pastebin service would expose the source code to unauthorized parties and therefore do not satisfy the requirement to keep the code internal.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What are the benefits of using a private repository for source code management?
Open an interactive chat with Bash
What is role-based access control (RBAC) in version-control platforms?
Open an interactive chat with Bash
Why is hosting source code on public services like pastebins or anonymous FTP servers a bad idea?