Salesforce Certified B2C Solution Architect (Arch-302): B2C-SOLUTION-ARCHITECT

Correct Answer: AD

API-led connectivity is a method of connecting data to applications through reusable and purposeful APIs. MuleSoft Accelerator for Salesforce B2C Commerce Cloud is a solution that uses API-led connectivity to integrate B2C Commerce with

other systems such as PIM, ERP, or Service Cloud. The benefits of API-led connectivity while implementing the MuleSoft accelerator for B2C Commerce are:

It enables self-service and an increase in productivity through reusable microservices and APIs. API-led connectivity allows developers to create modular and reusable microservices and APIs that can be easily discovered, accessed, and

composed by other developers or business users. This reduces duplication of effort, increases agility, and accelerates time to market. It enforces a distributed approach and allows for the creation of Experience APIs, Data APIs, and System

APIs. API-led connectivity follows a distributed approach that decouples data sources from data consumers, enabling greater scalability, flexibility, and security. It also allows for the creation of three layers of APIs:

Experience APIs that tailor data to specific channels or devices, Data APIs that orchestrate data from multiple sources, and System APIs that connect to core systems of record.

Option B is incorrect because API-led connectivity does not let the business quickly integrate different systems without involving IT. It requires IT to design, build, and manage the APIs that enable integration. Option C is incorrect because

API-led connectivity does not offer a template-driven approach for development. It offers a methodology and a framework for developing APIs based on best practices.

References:

https://www.mulesoft.com/resources/api/what-is-api-led-connectivity

https://www.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-salesforce-b2c-commerce-cloud/

Correct Answer: AD

Introducing a leads-management process and a web-to-lead form can have implications for consent, preferences, and compliance for converted leads in Marketing Cloud. For example, if a lead opts out of email communication in Sales Cloud, this preference should be reflected in Marketing Cloud as well. Similarly, if a lead is converted to a contact in Sales Cloud, the corresponding subscriber record in Marketing Cloud should be updated with the new ID and status. Leads can also have a detrimental impact on the quality of contact records in Sales Cloud if they are not properly deduplicated, validated, and enriched. For example, if a lead is created with an invalid or duplicate email address, this can affect the deliverability and personalization of email messages in Marketing Cloud.

References: https://help.salesforce.com/s/articleView?id=sf.mc_co_data_integration_best_practices.htmandtype=5 https://help.salesforce.com/s/articleView?id=sf.mc_co_subscriber_key.htmandtype=5 https://help.salesforce.com/s/articleView?id=sf.mc_co_web_to_lead.htmandtype=5

Correct Answer: BD

Service Cloud and Marketing Cloud are considered authoritative systems for consent and compliance preferences, as well as primary person attributes such as name, address, birthday, phone, and email. Service Cloud is the system of record for customer service interactions and case management, and it can store customer consent and preferences for different channels and purposes. Marketing Cloud is the system of record for customer engagement and marketing campaigns, and it can store customer consent and preferences for email, SMS, push notifications, and other channels. B2C Commerce is not an authoritative system for consent and compliance preferences, as it does not store them natively. It can store some primary person attributes such as name, address, phone, and email, but they may not be the most up-to-date or accurate. Experience Cloud is not an authoritative system for consent and compliance preferences, as it relies on other systems to store them. It can store some primary person attributes such as name, email, and birthday, but they may not be the most up-to-date or accurate.

References: https://help.salesforce.com/s/articleView?id=sf.mc_co_data_integration_best_pract ices.htmandtype=5 https://help.salesforce.com/s/articleView?id=sf.mc_co_data_integration_considerat ions.htmandtype=5