Universal Containers (UC) has multiple development teams that work on separate streams of work, with different timelines. Each stream has different releases of code and config, and the delivery dates differ between them.
What is a suitable branching policy to recommend?

Universal Containers (UC) has a large user base (>300 users) and was originally implemented eight years ago by a Salesforce Systems Integration Partner. Since then, UC has made a number of changes to their Visual force pages and Apex classes in response to customer requirements, made by a variety of Vendors and internal teams. Which three issues would a new Technical Architect expect to see when evaluating the code in the Salesforce org? Choose 3 answers

A team has completed a sprint and intends to deploy these changes after business approval, but they will immediately begin the next sprint.
What strategy should an architect recommend?

An Architect is working on a Universal Containers project, and due to security concerns they cannot provide the Architect with production access. Instead, a central release management team will be responsible for performing production deployments for all development teams. How should an Architect leverage the Metadata API to ensure any metadata components necessary to deploy the project's functionality are properly communicated to the release management team?

Universal Containers has developed teams working on multiple projects. They are exploring a source control tool to track and manage their code/config. What two benefits does a source control tool provide? Choose 2 ans