A Solution Architecture Diagram shows the high-level view of the solution components and how they relate to each other. It also shows the key business capabilities and objectives that the solution supports. It does not go into too much detail about the technical implementation or configuration of each component.
A Solution Architecture Diagram can help you communicate the vision and strategy of your multi-cloud solution to the business executives and stakeholders at a high level without overwhelming them with too much technical information.

Option B is a solution that can help AC Computers avoid hitting governor limits when processing large orders because asynchronous Apex can run in a separate thread and use higher limits than synchronous Apex1. For example, asynchronous Apex can process up to 50 million records per transaction, while synchronous Apex can only process up to 50 thousand records per transaction2. By moving some of their automation processes to asynchronous Apex, AC Computers can reduce the load on their Salesforce environment and improve performance.
A Solution Architect should evaluate moving automation to asynchronous Apex to resolve the issue of hitting governor limits when trying to create and activate orders in Salesforce. By moving the automation to asynchronous Apex, the automation processes can be run in a separate thread and will not affect the transaction limit for the current thread. This will prevent governor limits from being hit and ensure that the order creation and activation processes can be completed successfully.

Fast-track Service Cloud followed by Sales Cloud, Revenue Cloud, and, later, Experience Cloud. Service Cloud should be implemented first in order to quickly improve the customer experience. This should be followed by Sales Cloud and Revenue Cloud, which will allow the company to better manage customer relationships and revenue. Finally, Experience Cloud should be implemented to provide additional channels of communication and digital self-service offerings.
https://admin.salesforce.com/blog/2021/new-ideas-on-the-product-roadmap-admins-will-love

the B2B Solution Architect views more on the overall solution architecture in pure B2B scenarios. The certificate covers different aspects of the duties of an enterprise solution architect, such as understanding business requirements in the whole customer journey and understanding best practices to implement multi-cloud solutions. Therefore, it is important to conduct discovery meetings with key stakeholders to understand their needs and pain points before proposing a solution.

Plot the map of the current system landscape and identify key areas where the B2B multi-cloud solution will fit in. This is an important step to understand the existing technical dependencies within the organisation, such as data sources, integrations, applications, and platforms. It also helps to identify the gaps and opportunities for improvement that can be addressed by the B2B multi-cloud solution.