The correct option is Adopting open source style collaboration and transparency within the company.

This approach describes InnerSource because it brings open source practices into a private organization. Work is visible by default and repositories are discoverable across teams. Contribution guidelines invite participation from colleagues in other groups and code review and discussion happen in the open within the company. This fosters reuse and reduces silos as anyone can propose improvements and consume shared components.

Using a private hosted Git platform describes an infrastructure choice rather than a collaborative practice. You can host code privately and still work in isolation, which does not achieve InnerSource goals.

Implementing Scrum or Kanban practices to manage sprints is about agile delivery cadence and workflow. InnerSource is about cross team transparency and contribution norms rather than sprint management.

Running closed development that keeps code limited to the originating team is the opposite of InnerSource because it restricts visibility and prevents broad contribution and reuse.

Full AWS Practitioner Certification Question