Explanation: These answers are correct because they are ways to model a customer across all three systems using the Marketing Cloud Subscriber Key andService Cloud as sources of truth. The Marketing Cloud Subscriber Key can be sent to Service Cloud and B2C Commerce to be held for reference, which can help link customer records across systems and enable cross-channel marketing and service. Service Cloudcan be used as system of record for customer data and consent preferences across all channels, which can help comply with data privacy laws and provide a consistent customer experience.

Explanation: Salesforce Shield Encryption is a feature that allows encrypting sensitive data at rest in Salesforce without compromising functionality or performance. Shield Encryption uses probabilistic encryption to protect data while preserving its format and length. Field-Level Encryption is a feature in Marketing Cloud that allows encrypting sensitive data at rest in Marketing Cloud using customer-managed keys. Field-Level Encryption uses deterministic encryption to protect data while preserving its format and length. When determining an appropriate solution for encrypting specific fields in Service Cloud as well as in data extensions in Marketing Cloud, the following considerations are relevant:
With Shield, encrypted fields cannot be used to filter or sort in Process Builder and Flow Builder. Process Builder and Flow Builder are tools in Salesforce that allow creating automated workflows and processes based on certain criteria or conditions. However, Shield Encryption does not support filtering or sorting on encrypted fields in these tools, because probabilistic encryption does not allow exact matching or comparison of values.
Shield encryption can be done on any standard or custom field on all field types, but cannot be set to encrypt those fields in Marketing Cloud. Shield Encryption supports encrypting any standard or custom field on any field type in Salesforce, such as text, email, phone, date, etc. However, Shield Encryption does not apply to Marketing Cloud fields or data extensions, because they are stored in a separate database from Salesforce. To encrypt fields in Marketing Cloud, Field-Level Encryption must be used.
Option A is incorrect because with Shield, encrypted fields are visible to the user if they have the View Encrypted Data permission, but there are other feature impacts such as filtering, sorting, searching, etc. Option C is incorrect because Field-Level Encryption is not required on Marketing Cloud to encrypt the custom fields if they are already encrypted by Shield Encryption in Service Cloud. However, Field-Level Encryption can be used on Marketing Cloud if additional encryption or customer-managed keys are needed.

Explanation: A multi-cloud integration is a solution that allows connecting and integrating data and applications across different cloud platforms and systems. A multi-cloud integration can provide various benefits, such as scalability, flexibility, resilience, and innovation. To design and implement a robust and scalable multi-cloud integration, a Solution Architect should recommend the following:
Build an application network by adopting an API-led connectivity approach that packages underlying connectivity and orchestration services as easily discoverable and reusable API building blocks. An application network is a way of organizing applications, data, and devices into a network of reusable services that can be composed and recomposed to meet changing business needs. An API-led connectivity approach is a methodical way to connect data and applications through reusable and purposeful APIs that are developed to play a specific role:
unlocking data from systems, composing data into processes, or delivering an experience. By building an application network using an API-led connectivity approach, the Solution Architect can enable a composable, connected, and automated solution that can leverage the capabilities of different cloud platforms and systems in a flexible and agile way.
Option A is incorrect because implementing an integration solution using an outbound messaging design pattern and Salesforce Connect as the integration approach is not suitable or scalable for a multi-cloud integration. An outbound messaging design pattern is a way of sending notifications from Salesforce to external systems when a record is created or updated. Salesforce Connect is a feature that allows accessing and integrating external data from various sources without copying or storing it in Salesforce. These approaches are limited in functionality, performance, security, and reliability for a complex multi-cloud integration scenario. Option B is incorrect because implementing a custom integration solution using lightweight middleware tools like Jitterbit or Talend is not optimal or sustainable for a multi-cloud integration. Lightweight middleware tools are software applications that provide basic integration capabilities, such as data transformation, routing, orchestration, etc. However, these tools are not designed for building an application network or supporting an API-led connectivity approach. They also require custom code or configuration that can increase the cost and complexity of the solution.
Option D is incorrect because building multiple point-to-point application integrations connecting the multi-cloud and on-premises applications using SOA (Service-Oriented Architecture) and SOAP web services is not advisable or scalable for a multi-cloud integration. Point-to-point integrations are direct connections between two applications or systems that are tightly coupled and hard to maintain. SOA is an architectural style that organizes applications into loosely coupled services that communicate through standardized interfaces. SOAP web services are protocols that allow exchanging structured data between applications using XML messages. However, these approaches are outdated and inefficient for a modern multi-cloud integration scenario. They also create complexity and fragility in the solution.

Explanation: Marketing Cloud provides both REST and SOAP APIs for integrating with other systems, includingService Cloud. Both APIs can be used to perform various operations such as creating, updating, or deleting data objects, triggering messages, retrieving tracking data, and more. The REST API uses JSON request and response bodies, while the SOAP API uses XML request and response bodies. The choice of API depends on the use case, preference, and compatibility of the systems involved.

Explanation: This option ensures that the Marketing Cloud Contact is linked to the correct Salesforce record after the Lead is converted to a Contact, and that the contact utilization is not affected by duplicate records. The other options can result in data loss, inconsistent reporting, or unnecessary complexity.