Universal Containers (UC) is working on a major project and has determined that its approach to a certain feature will no longer work with an upcoming Salesforce platform release (e.g., Winter to Spring).What should a Technical Architect recommend to address this issue?

Universal Containers is delivering many changes to its Salesforce system. Adoption reports are discovering that many features are unused. The steering committee wants this to change and is looking to the architect for advice.
What should an architect recommend to overcome this?

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 CUC) has multi-cloud architecture in a single org. The Sales Cloud dev team is working in a Dev Pro sandbox (DevProl) of delivering a release In three months. The business requirements from Service Cloud warrant a quicker release in four weeks, but need part of the Sales Cloud work that is completed in DevProl. The decision of using a separate Dev Pro sandbox (DevPro2) is still pending. The DevProl was upgraded to preview for next salesforce major release two weeks ago.
What should an Architect recommend?

Universal Containers (UC) has recently acquired other companies that have their own Salesforce orgs.These companies have been merged as new UC business units.
The CEO has requested an architect to review the org strategy, taking into consideration two main factors:
* The CEO wants business process standardization among all business units.
* Businessprocess integration is not required as the different business units have different customers and expertise.
Which org strategy should the architect recommend in this scenario, and why?