Salesforce Certified B2C Solution Architect Practice Test - Questions Answers, Page 4

C is correct because Marketing Cloud Connect uses the SOAP API to integrate multiple business units in Marketing Cloud with Salesforce core orgs. The SOAP API enables data synchronization, triggered sends, journey builder integrations, and tracking data.

A is incorrect because the Tooling API is used to create and modify metadata in Salesforce core orgs, such as custom objects, fields, workflows, etc. It is not used for Marketing Cloud Connect integration.

B is incorrect because the REST API is used to access resources in Marketing Cloud, such as contacts, content, campaigns, etc. It is not used for Marketing Cloud Connect integration.

D is incorrect because the Streaming API is used to receive notifications of data changes in Salesforce core orgs, such as record updates, deletes, etc. It is not used for Marketing Cloud Connect integration.

: https://developer.salesforce.com/docs/atlas.en-us.mc-apis.meta/mc-apis/index-api.htm

: https://developer.salesforce.com/docs/atlas.en-us.api_tooling.meta/api_tooling/intro_api_tooling.htm

: https://developer.salesforce.com/docs/atlas.en-us.mc-apis.meta/mc-apis/index-api.htm

: https://developer.salesforce.com/docs/atlas.en-us.api_streaming.meta/api_streaming/intro_stream.htm

C is correct because Marketing Cloud Triggered Send is a feature that allows sending personalized emails based on events or actions in another system, such as B2C Commerce. Triggered Send can be used to send password reset emails when a new account is created or the email address is updated in B2C Commerce. Triggered Send also tracks email open and forward count in Marketing Cloud. To disable the coupon code after a single use, B2C Commerce can use coupon code restrictions based on redemption count.

A is incorrect because Service Cloud Email Service is a feature that allows receiving and processing inbound emails from customers in Service Cloud. It is not used to send password reset emails or track email open and forward count.

B is incorrect because Marketing Cloud Journey Event is a feature that allows triggering journeys based on events or actions in another system, such as B2C Commerce. Journey Event can be used to send password reset emails, but it is more suitable for complex or multi-step customer interactions, such as welcome series or re-engagement campaigns. Triggered Send is more efficient and simpler for single-step interactions, such as password reset.

D is incorrect because Commerce Cloud Email Service is a feature that allows sending transactional emails from B2C Commerce, such as order confirmation or shipping notification. It is not used to send password reset emails or track email open and forward count.

: https://help.salesforce.com/s/articleView?id=sf.mc_co_triggered_email_sends.htm&type=5

: https://help.salesforce.com/s/articleView?id=sf.mc_es_triggered_send_definition.htm&type=5

: https://documentation.b2c.commercecloud.salesforce.com/DOC1/topic/com.demandware.dochelp/content/b2c_commerce/topics/coupons/b2c_coupon_code_restrictions.html

: https://help.salesforce.com/s/articleView?id=sf.email_services.htm&type=5

: https://help.salesforce.com/s/articleView?id=sf.mc_jb_journey_events.htm&type=5

: https://documentation.b2c.commercecloud.salesforce.com/DOC1/topic/com.demandware.dochelp/OrderManagement/EmailService.html

B is correct because Marketing Cloud can be used for customer segmentation based on VIP status and cart abandonment behavior. B2C Commerce can be used for creation of coupon codes using promotion rules and coupon code restrictions. B2C Commerce and Marketing Cloud functionalities can be used to send abandoned cart emails using the Marketing Cloud Connector cartridge and the Abandoned Cart Journey template. Marketing Cloud can track email open and forward count using tracking metrics.

A is incorrect because Service Cloud is not used for customer segmentation or creation of coupon codes. Service Cloud is used for customer service and case management.

C is incorrect because B2C Commerce is not used for customer segmentation or creation of coupon codes. B2C Commerce is used for online shopping and order management.

D is incorrect because Tableau CRM is not used to track email open and forward count. Tableau CRM is used for data analysis and visualization.

: https://help.salesforce.com/s/articleView?id=sf.mc_co_create_audience_segment.htm&type=5

: https://documentation.b2c.commercecloud.salesforce.com/DOC1/topic/com.demandware.dochelp/content/b2c_commerce/topics/coupons/b2c_creating_coupon_codes.html

: https://help.salesforce.com/s/articleView?id=sf.mc_co_abandoned_cart_journey.htm&type=5

: https://help.salesforce.com/s/articleView?id=sf.mc_es_email_tracking_metrics.htm&type=5

A is correct because integrating product, order, and customer data feeds into Marketing Cloud Data Extensions is a prerequisite for enabling an Abandoned Cart Journey. Data Extensions are tables that store data in Marketing Cloud and can be used to define audience segments and personalize messages.

D is correct because implementing the Marketing Cloud collect.js through the storefront by using the Connector's reference implementation is a prerequisite for enabling an Abandoned Cart Journey. The collect.js script tracks customer behavior on the storefront and sends data to Marketing Cloud using the Connector cartridge.

B is incorrect because integrating product, order, and customer data feeds into Service Cloud objects is not needed for enabling an Abandoned Cart Journey. Service Cloud objects are used to store data in Service Cloud and can be used to manage customer service cases and interactions.

C is incorrect because using Mulesoft to bring order and customer data feeds from B2C Commerce to Marketing Cloud is not needed for enabling an Abandoned Cart Journey. Mulesoft is a platform that provides integration solutions for various systems and applications.

: https://help.salesforce.com/s/articleView?id=sf.mc_co_data_integration.htm&type=5

: https://help.salesforce.com/s/articleView?id=sf.mc_co_web_and_mobile_analytics_tracking.htm&type=5

A custom solution in Service Cloud can use Apex or Lightning Web Components to call the B2C Commerce APIs and update the customer records in B2C Commerce. This option provides the most flexibility and control over the integration logic and error handling. Platform events, outbound messages, and change data capture are not supported by B2C Commerce out of the box, so they would require additional development or middleware to handle them.

Reference:

https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_rest_code_sample_basic.htm

https://developer.salesforce.com/docs/component-library/documentation/en/lwc/lwc.data_wire_example

https://documentation.b2c.commercecloud.salesforce.com/DOC1/index.jsp?topic=%2Fcom.demandware.dochelp%2FOCAPI%2Fcurrent%2Fusage%2FRESTAPIs.html

Request and reply is an integration pattern that allows a system to send a message to another system and wait for a response. This pattern is suitable for scenarios where the sender needs to receive an immediate confirmation or acknowledgment from the receiver. In this case, B2C Commerce needs to receive the order number and status from the ERP system after sending the order details.

Reference:

https://architect.salesforce.com/design/integration-patterns-and-practices/request-and-reply/

https://documentation.b2c.commercecloud.salesforce.com/DOC1/topic/com.demandware.dochelp/OrderManagement/OrderManagementOverview.html

Marketing Cloud provides both REST and SOAP APIs for integrating with other systems, including Service 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.

Reference:

https://developer.salesforce.com/docs/atlas.en-us.mc-apis.meta/mc-apis/index-api.htm

https://developer.salesforce.com/docs/atlas.en-us.noversion.mc-getting-started.meta/mc-getting-started/get-started-with-marketing-cloud-apis.htm

A Marketing Cloud sandbox is a separate instance of Marketing Cloud that can be used for development, testing, and training purposes. A Marketing Cloud sandbox can be connected to a Service Cloud sandbox using Marketing Cloud Connect, which allows data synchronization and cross-cloud functionality. This option supports the CI/CO processes and data segregation for each Service Cloud sandbox. The other options are either not feasible or not cost-effective.

Reference:

https://help.salesforce.com/s/articleView?id=sf.mc_co_marketing_cloud_sandbox.htm&type=5

https://help.salesforce.com/s/articleView?id=sf.mc_co_marketing_cloud_connect.htm&type=5

Migrating the Subscriber Key in Marketing Cloud to be the Service Cloud Contact or Person Account ID allows for a consistent identification of customers across both systems. This also enables data synchronization and cross-cloud features via Marketing Cloud Connect. Using Service Cloud as a central point to hold unique identifiers from all systems, including B2C Commerce CustomerNo and Customer ID, allows for a single source of truth for customer data and facilitates data integration and reporting across systems. Customer 360 Data Manager is not yet available for B2C Commerce, so option B is not possible. Sending the Marketing Cloud Subscriber Key to Service Cloud and B2C Commerce is not necessary if option A is implemented, so option D is not optimal.

Reference:

https://help.salesforce.com/s/articleView?id=sf.mc_co_subscriber_key.htm&type=5

https://help.salesforce.com/s/articleView?id=sf.mc_co_data_integration_best_practices.htm&type=5

https://www.salesforce.com/in/blog/2020/04/what-is-salesforce-customer-360.html