Option B is the correct approach as it leverages Azure DevOps or GitHub, which are designed for version control and collaboration. These platforms provide features like branching, merging, and history tracking, which are essential for managing pipeline artifacts. Option A lacks proper version control mechanisms, while Option C is not scalable and prone to errors. Option D is inefficient as it does not maintain a history of changes, making it difficult to track and revert to previous versions if needed.