A client is running a project with a 626 multi-cloud setup involving Marketing Cloud, Sales Cloud, ServiceCloud, Experience Cloud, and MuleSoft. Currently, MuleSoft is primarily used to integrate with third-party systems. Marketing Cloud is connected to Sales/Service using the standard connector. A recent requirement-gathering session, involving all functional streams, brought up the question of where consolidated reporting mil happen. So far, reporting has only been looked at individually per stream.
There is a steering committee meeting 1 week from now. The Solution Architect was asked to provide different solutions to fix the problem. The expectation is that a high-level evaluation will be done prior the steering committee meeting so that an indication of options can be given and additional funding can be requested.
Which three critical steps should the Solution Architect take first?
Choose 3 answers
For a multi-cloud setup involving various Salesforce clouds and MuleSoft, understanding the current data architecture and the need behind consolidated reporting is crucial. Reviewing established and planned data flows provides insight into the existing data landscape, identifying systems of record and current data integrations. Identifying the key drivers and high-level data scope for consolidated reporting helps in aligning reporting solutions with business needs. Drafting a high-level solution using CRM Analytics (formerly known as Einstein Analytics) showcases the potential for unified reporting across multiple Salesforce clouds, leveraging its powerful data integration, transformation, and visualization capabilities. This approach aligns with Salesforce's best practices for data management and analytics, providing a foundation for informed decision-making in the steering committee meeting.
Currently there are no comments in this discussion, be the first to comment!