B2C-Solution-Architect Salesforce Certified B2C Solution Architect Arch-302 Exam Questions and Answers

Heroku is a cloud platform that allows developers to build, run, and scale applications using various languages and frameworks. Postgres is a relational database that can store large amounts of structured data. A custom solution using Heroku and Postgres can handle the high volume and frequency of data points generated by the “Track-My-Hike” feature, as well as provide scalability and flexibility for futur e enhancements. References: https://www.heroku.com/home https://www.postgresql.org/

B2C Commerce Governance and Quotas are a set of rules and limits that apply to B2C Commerce instances to ensure the efficiency and stability of solutions built on the platform. The following considerations should be kept in mind when considering B2C Commerce Governance and Quotas:

Object quotas status is updated with an up to 20-minute delay. Therefore, a Solution Architect must consider this delay when performing calculations related to traffic and limits. Object quotas are limits on the number of objects that can be created or stored in B2C Commerce, such as products, categories, customers, orders, etc. The object quotas status shows the current usage and remaining capacity of each object quota. However, the status is not updated in real time, but with an up to 20-minute delay. This means that the Solution Architect should account for this delay when estimating the traffic and limits for each object quota.

If an enforced quota is exceeded, an exception is thrown, which prevents the current operation from completing. The Solution Architect should design the solution so that the exception can be caught within a customization. Enforced quotas are quotas that are strictly enforced by B2C Commerce and cannot be exceeded or changed by customers. Examples of enforced quotas are API calls per hour, script execution time, cache size, etc. If an enforced quota is exceeded, B2C Commerce throws an exception that stops the current operation from completing. This can result in errors or failures in the storefront or backend processes. The Solution Architect should design the solution so that the exception can be caught within a customization and handled gracefully.

Option B is incorrect because sandbox quotas cannot be softened by exporting them from a production instance and importing them onto a sandbox instance. Sandbox quotas are fixed and cannot be changed by customers. Option C is incorrect because the Solution Architect cannot assume that quota violations have not occurred unless a site is experiencing performance issues. Quota violations can occur without affecting the site performance, but they can still cause errors or failures in certain operations or processes. References:

https://documentation.b2c.commercecloud.salesforce.com/DOC1/topic/com.demandware.dochelp/Governance/GovernanceOverview.html

https://documentation.b2c.commercecloud.salesforce.com/DOC1/topic/com.demandware.dochelp/Governance/ObjectQuotas.html

https://documentation.b2c.commercecloud.salesforce.com/DOC1/topic/com.demandware.dochelp/Governance/EnforcedQuotas.html

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. References:

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

Change Data Capture is an event-driven integration mechanism that allows near-real-time synchronization of Salesforce data changes with ex ternal systems. It does not impact the system performance as it uses asynchronous processing and does not require triggers or code. References: https://developer.salesforce.com/docs/atlas.en-us.change_data_capture.meta/change_data_capture/cdc_intro.htm

Marketing Cloud and B2C Commerce are the two products that a Solution Architect should include in the architecture to meet UC’s needs. Marketing Cloud allows UC to create customer group segments using its e-commerce data and send personalized messages across channels, while adhering to the current customer’s compliance preferences for previous campaigns. B2C Commerce enables UC to cross-sell its new product categories on its online storefront and provi de a seamless shopping experience for its customers.

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.

References:

: 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

Salesforce Connect is a feature that allows accessing and integrating external data from various sources without copying or storing it in Salesforce. Salesforce Connect uses external objects and external data sources to create a virtual data model that can be used in Salesforce applications and tools. The justifications for using Salesforce Connect in this solution are:

Need access to all external data in near real-time. Salesforce Connect allows accessing external data from ERP or other systems in near real-time, without any delays or synchronization issues. This ensures that the data is always up-to-date and consistent across systems.

The external data is changing frequently. Salesforce Connect allows reflecting any changes or updates made to the external data in ERP or other systems immediately in Salesforce, without requiring any manual intervention or batch processes. This ensures that the data is always accurate and reliable across systems.

Need real-time access to a small fraction of external data. Salesforce Connect allows accessing only a small fraction of external data that is relevant and needed for a specific use case, such as displaying customer order history or details. This reduces network overhead and improves performance.

Option A is incorrect because accessing external data using workflows and triggers is not possible or supported with Salesforce Connect. Option C is incorrect because integrating external data without writing custom code is not a justification for using Salesforce Connect, as it may require some custom code or configuration depending on the data source and use case. References:

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

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

This approach allows the company to have a separate business unit for each B2C Commerce storefront, which provides data segreg ation and customization for each market. Each business unit can have its own Marketing Cloud product catalog, which is a data extension that contains product information for generating product recommendations using Einstein. D. This approach allows the com pany to implement abandoned cart using Marketing Cloud’s Behavioral Trigger feature, which can track customer behavior on the B2C Commerce storefront and trigger an email journey based on predefined rules. The abandonment journey can include product recomm endations based on the products left in the cart. The B2C Commerce storefront must also be extended to re-create the customer’s shopping cart with abandoned products using a link or button in the email. References: https://help.salesforce.com/s/articleView ? id=sf.mc_pb_product_catalog.htm & type=5 https://help.salesforce.com/s/articleView?id=sf.mc_pb_behavioral_triggers.htm & type=5 https://developer.salesforce.co m/docs/commerce/sfra/marketing-cloud/abandoned-cart

B. Email tracking for messages sent from the ecommerce si te will not be replicated via Marketing Cloud Connect and therefore will not be visible to the Service Agents. Marketing Cloud Connect can only track email sends that are initiated from Marketing Cloud or Salesforce CRM, not from an external ecommerce site . This means that the Service Agents will not have a complete view of the customer’s email interactions or preferences. D. Contacts may be duplicated in Marketing Cloud during the transition phase, and additional work may be required to merge identities at a later date. Marketing Cloud Connect uses the Salesforce Contact ID or Lead ID as the contact key in Marketing Cloud, which is a unique identifier for each contact or lead. If the existing ecommerce site integration uses a different identifier, such as e mail address or customer ID, then it may create duplicate contacts in Marketing Cloud when syncing with Service Cloud. This can affect the contact count, billing, and personalization in Marketing Cloud. References: https://help.salesforce.com/s/articleView ?id=sf.mc_co_sync_leads_and_contacts.htm & type=5 https://help.salesforce.com/s/articleView?id=sf.mc_co_subscriber_key_migration.htm & type=5

Marketi ng Cloud should be the system of record for lifetime engagement tracking and history, as well as other data for personalization or segmentation, as it is the system that collects and analyzes the customer’s interactions and behaviors across multiple channe ls and touchpoints.  Marketing Cloud can also use features like Audience Builder and Contact Builder to create unified customer profiles and segments based on various data sources 3  . Service Cloud should be the system of record for storing primary attributes (name, address, birthday, phone, and email) about the customer, as it is the system that represents a person across multiple Salesforce clouds and can store and manage the customer’s consent and compliance preferences using features like Individual object, Data Protection and Privacy, and Consent Management .

This answer is correct because it is a way to reduce the storage size in Salesforce and still be able to access the ERP Invoice records in Salesforce. Salesforce Connect/External Objects can be used to display external data in Salesforce without copying or storing it. Custom Apex adapters can be used to connect to any external system that has a web se rvice API, such as an ERP system. References: https://help.salesforce.com/s/articleView?id=sf.datacloud_connect.htm & type=5 https://developer. salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_connector_intro.htm

B2C Commerce can trigger a Marketing Cloud post-purchase journey using the Transactional Messaging API. Journey Builder can use a Wait activity to delay the email delivery based on a fixed duration or a date attribute. Einstein Engagem ent Split can use AI to determine the optimal path for each customer based on their engagement behavior, such as open rate. References: https://developer.salesforce.com/docs/commerce/sfra/marketing-cloud/transactional-messaging-api https://help.salesforce. com/s/articleView?id=sf.mc_jb_wait_activity.htm & type=5 https://help.salesforce.com/s/articleView?id=sf.mc_jb_einstein_engagement_split.htm & type=5

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. References:

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

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

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

A. The Contact Data Portability report in Marketing Cloud is a feature that allows creating a report containing subscriber data related to a single contact, such as email address, name, phone number, preferences, etc. This report can be used to provide customers access to their own data or comply with data privacy regulations, such as GDPR or CCPA. B. The Customer Data Snapshots report in Commerce Cloud is a feature that allows creating a report containing purchaser data related to a single customer, such as order history, payment methods, addresses, etc. This report can be used to provide customers access to their own data or comply with data privacy regulations, such as GDPR or CCPA. References: https://help.salesforce.com/s/articleView?id=sf.mc_overview_contact_data_portability.htm & type=5 https://documentation.b2c.commercecloud.salesforce.com/DOC1/topic/com.demandware.doch elp/content/b2c_commerce/topics/admin/b2c_customer_data_snapshots.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.

References:

: 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

The Journey Membership Lightning component is a pre-built component that displays the journeys that a contact is in and their status in each journey. It can be added to the Contact Page Layout in Service Cloud using the Marketing Cloud Connect Managed Package, which enables integration be tween Service Cloud and Marketing Cloud. References: https://help.salesforce.com/s/articleView?id=sf.mc_co_journey_membership_lightning_component.htm & type=5 https://help.salesforce.com/s/articleView?id=sf.mc_co_marketing_cloud_connect.htm & type=5

These answers are correct because they are ways to model a customer across all three systems using the Marketing Cloud Subscriber Key and Service 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 Cloud can 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. References: https://help.salesforce.com/s/articleView? id=sf.mc_co_mark eting_cloud_connect_best_practices.htm & type=5 https://help.salesforce.com/s/articleView?id=sf.b2c_commerce_service_cloud_integration.htm & type =5

B2C Commerce should be defined as the data s ource authority for the customer attributes collected from the sweepstakes page, as it is the system that captures the customer data directly from the web form and validates the customer consent and compliance preferences. The other systems can consume or sync the customer data from B2C Commerce, but they should not overwrite or modify the data without the customer’s consent.

To adhere to global data privacy acts and respect customers’ privacy, the retailer should enable terms and conditions functionality within Marketing Cloud, which will allow them to display a custom message and a checkbox for customers to agree before they can submit a form or join a list. The retailer should also use profile and preference center functionality for Marketing Cloud Email Studio, which will allow them to capture consent and opt-in confirmation from customers, as well as provide them with options to manage their email preferences and unsubscribe.

References:

[Terms and Conditions]

[Profile and Preference Centers]

This answer is correct because it is the primary system that should be used for all authentication between B2C Commerce site and Experience Cloud site. Salesforce Identity can act as an identity provider (IDP) for both B2C Commerce and Experience Cloud, and it can provide a single login and data experience between the two sites. Salesforce Identity can also store customer profile data in a single pl ace and sync it across systems. References: https://help.salesforce.com/s/articleView?id=sf.b2c_commerce_service_cloud_integration.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. References:

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

This answer is correct because managing inventory data inside of B2C Comm erce makes it easier to parse by store and enable buy online pick up in store (BOPIS) functionality. B2C Commerce can store inventory information for multiple locations and provide real-time availability information to customers and service agents. B2C Com merce can also integrate with Salesforce OMS to manage order fulfillment and payment processing for BOPIS orders. References: https://help.salesforce.c om/s/articleView?id=sf.b2c_commerce_oms_integration.htm & type=5

Both options A and B are valid ways to implement an Abandoned Cart Solution Workflow using B2C Commerce and Marketing Cloud. Option A uses streaming updates for catalog importing, which allows for near real-time updates of product information in Marketing Cloud. Option B uses data feeds that are transferred via SFTP and imported via Automation Studio, which allows for more control over the data format and frequency. Both options use collect.js or Collect Tracking Code to monitor shopper behavior on the B2C Commerce site and share it with Marketing Cloud. Both options also use Journey Builder to trigger personalized messages based on abandoned cart events. Option C is not valid because Google Analytics tracking is not part of the solution. Option D is not valid because inventory data is not required for the solution. References:

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

https://trailhead.salesforce.com/content/learn/modules/salesforce-solution-kits-quick-look/c360-sk1

A is correct because Salesforce Order Management does not have native support for multiple distribution centers and requires either an AppExchange package or custom Apex triggers to implement fulfillment rules based on cus tom attributes 1 .

Customer 360 Data Manager is a platform service that enables companies to connect customer data across Salesforce apps and create a unified customer profile. It uses advanced matching algorithms to identify and link customer r ecords from different systems based on common attributes such as name, email, phone, address, etc. It also assigns a consistent Global Party ID to each customer record, which serves as a unique identifier across systems. Customer 360 Data Manager can be us ed across multiple brands within a single merchant environment by creating separate data spaces for each brand. Option B is incorrect because Customer 360 Data Manager can relate the IDs between systems without additional custom development. Option C is in correct because Customer 360 Data Manager supports multiple brands within a single merchant environment. Option D is incorrect because B2C Commerce, Service Cloud, and Marketing Cloud do not automatically use a common core Customer Profile managed by Custo mer 360 Data Manager; they need to be connected and configured via Customer 360 Data Manager. References:

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

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

A. A service definition in B2C Commerce is a configuration that defines how B2C Commerce communicates with an external system, such as Marketing Cloud. By creating a service definition that points to Marketing Cloud’s REST API, the company can enable B2C Commerce to call Marketing Cloud’s endpoints for various purposes, such as triggering journeys or updating contact data. D. After purchase, the company can use the B2C Commerce service definition to send redemption data to Marketing Cloud using the REST API. This data can include the coupon code, the journey ID, and the contact key. Marketing Cloud can use this data to update the contact’s journey status and stop sending reminder emails. References: https://developer.salesforce.com/docs/commerce/sfra/marketing-cloud/marketing-cloud-integration https://developer.salesforce.com/docs/commerce/sfra/marketing-cloud/transactional-messaging-api

This solution allows the company to send the electronic receipt in near real ti me using the Marketing Cloud Transactional Messaging API, which can handle high-volume and time-sensitive messages. The POS system already has the Service Cloud Contact ID for the customer, so there is no need to make an extra API call to Service Cloud to fetch it. The Service Cloud Contact ID can be passed as the Marketing Cloud Contact Key to ensure data consistency across the systems. References: https://developer.salesforce.com/docs/commerce/sfra/marketing-cloud/transactional-messaging-api https://help.salesforce.com/s/articleView?id=sf.mc_co_subscriber_key_migration.htm & type=5

A. Fixing the data quality issues in Service Cloud before migrating to Marketing Cloud can help avoid duplicate or incomplete contacts in Marketing Cloud, which can affect the contact count, billing, and personalization. Data quality issues can be fixed by using tools such as Data Loader, Duplicate Management, or ETL tools. C. Mapping Contact, Lead, and Ac count objects within Marketing Cloud can help enable personalization by using data from Service Cloud in email content or journeys. Mapping can be done by using Marketing Cloud Connect or Customer 360 Data Manager. References: https://help.salesforce.com/s /articleView?id=sf.mc_co_sync_leads_and_contacts.htm & type=5 https://help.salesforce.com/s/articleView?id=sf.mc_co_subscriber_key_migration.htm & type=5 h ttps://help.salesforce.com/s/articleView?id=sf.mc_co_map_salesforce_objects.htm & type=5

A Technical Design Specification is a document that describes the technical architecture and design of a solution, including the data mapping/model and systems integration. This document c an help the company understand the solution that is needed and how it will meet their requirements. References: https://trailhead.salesforce.com/content/learn/modules/solution-design-for-technical-architects/define-the-technical-architecture

B. Extending the B2C Commerce storefront to trigger emails via Marketi ng Cloud’s journey REST APIs allows the customer to send triggered emails based on customer behavior on the storefront, such as signing up, placing an order, or abandoning a cart. The REST APIs can also pass data attributes, such as order details or person alization information, to Marketing Cloud. D. Copying and pasting the Collect Script within the head or body in the website template allows the customer to track customer behavior on the storefront using Marketing Cloud’s Web & Mobile Analytics feature. Th e Collect Script can also capture customer attributes, such as email address or contact key, and send them to Marketing Cloud. E. Updating order.export custom object in B2C Commerce with the Marketing Cloud object data extension allows the customer to map order data from B2C Commerce to Marketing Cloud using a point-and-click configuration in Business Manager. This enables order data synchronization between B2C Commerce and Marketing Cloud. References: https://developer.salesforce.com/docs/commerce/sfra/mar keting-cloud/marketing-cloud-integration https://developer.salesforce.com/docs/commerce/sfra/marketing-cloud/transactional-messaging-api https://help.salesforce.com/s/articleView?id=sf.mc_pb_web_and_mobile_analytics.htm & type=5 https://help.salesforce.com/s/articleView?id=sf.mc_co_data_integration_with_commerce_cloud.htm & type=5

Shield Platform Encryption is a feature that allows you to encrypt sensitive data at rest in Service Cloud and B2C Commerce, while preserving platform functionality. Encrypted Data Sending (EDS) is a feature that allows you to send encrypted data from Service Cloud to Marketing Cloud using an encryption key that only you control. B2C Commerce’s crypto API is a set of methods that allow you to encrypt and decrypt data using symmetric or asymmetric keys in your code.

References:

[Salesforce Shield Platform Encryption Implementation Guide]

[Encrypted Data Sending (EDS) for Marketing Cloud]

[B2C Commerce Crypto API]

Option A is correct because authentication credentials should be stored and managed by Experience Cloud as the system of record for this customer data. Experience Cloud acts as an identity provider (IDP) for commerce, meaning that it verifies the identity of customers who log in to ecommerce sites using their communities credentials. Experience Cloud can also leverage Salesforce Identity features to provide secure and seamless authentication across multiple Salesforce clouds and external systems.

Option B is incorrect because address book should not be stored and managed by Experience Cloud as the system of record for this customer data. Address book is mainly used for ecommerce purposes, such as shipping and billing addresses, and it should be stored and managed by B2C Commerce as the system of record. B2C Commerce can also integrate with Experience Cloud to provide a consistent user experience across ecommerce sites and communities.

A Marketing Clo ud sandbox is a separate instance that can be used for testing and development purposes. It can be connected to multiple Service Cloud sandboxes using Marketing Cloud Connect. This setup allows data segregation and cost efficiency, as opposed to creating m ultiple Marketing Cloud instances or business units. References: 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_connect_multiple_salesforce_orgs.htm & type=5

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 recor ds. The other options can result in data loss, inconsistent reporting, or unnecessary complexity.

Syncing Person Account object can help map subscriber data in Marketing Cloud when the company has Person Account set up on their Sales Cloud. This can enable bi-directional data integration between Sales Cloud and Marketing Cloud for Person Accounts, which are records that combine both Account and Contact information for individuals. References:

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

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.

References:

: 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

Product Catalogs are a type of data extension that contain product information for generating product recommendations using Einstein in Marketing Cloud. Product Catalogs can be configured natively to sync from B2C Commerce to Marketing Cloud using a point and click configuration in the Marketing Cloud Business Manager. References: h ttps://help.salesforce.com/s/articleView?id=sf.mc_pb_product_catalog.htm & type=5 https://developer.salesforce.com/docs/commerce/sfra/marketing-c loud/marketing-cloud-integration

Identity is a feature that allows managing user authentication and access across different applications and systems. Identity can be either internal or external to Salesforce, depending on where the user credentials are stored and verified. To cover NTOs identity needs, a Solution Architect should recommend the following:

Define a user registration handler to support user provisioning and authentication via social services like Google and Facebook. A user registration handler is a class in Apex code that defines the logic for creating and updating user accounts based on information from an external identity provider. A user registration handler can support user provisioning and authentication via social services like Google and Facebook, by using OAuth 2.0 protocols and OpenID Connect standards to exchange user information and tokens between Salesforce and the social services.

Leverage Salesforce Identity as the identity provider to centralize authentication for both Experience Cloud and B2C Commerce in one place. Salesforce Identity is a product that allows using Salesforce as an identity provider for other applications and systems. Salesforce Identity can centralize authentication for both Experience Cloud and B2C Commerce in one place, by using single sign-on (SSO) protocols and standards to enable users to log in to both applications with the same credentials.

Option C is incorrect because leveraging B2C Commerce as the identity provider for both Storefront and the Service Portal is not possible or advisable. B2C Commerce does not support acting as an identity provider for other applications or systems, as it does not support SSO protocols or standards. Option D is incorrect because using Salesforce CDP, which automatically syncs profiles and authentication information across systems, is not a valid or available option. Salesforce CDP is a product that allows creating unified customer profiles from various data sources, but it does not sync or manage authentication information across systems. References:

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

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

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

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

This answer is correct because it is a next step that a Solution Architect should suggest to provide UC the kind of understanding they are looking for regarding how to manage or work with health related data while still keeping their users trust. A Consequence Scanning Workshop is a method that helps identify potential positive and negative consequences of a product or service on people, society, and environment. It can help UC anticipate the impact of their work on their users’ trust and privacy, and design solutions that mitigate risks and maximize benefits. References : https://www.salesforce.com/blog/how-relationship-design-works/

These answers are correct because they are recommendations that can improve the success of the automated re-en gagement campaign. Using SMS as a channel can increase the engagement rate as compared to email, as SMS messages have higher open and response rates. Configuring Einstein Recommendations in Marketing Cloud can automate segment generation for Journey Builde r, which can help create personalized and relevant messages based on customer data and behavior. References: https://www.salesforce.com/products/marketing-cloud/best-practices/sms-marketing-statistics/ https://help.salesforce.com/s/articleView?id=sf.mc_pb_einstein_recommendations.htm & type=5

This answer is correct because the consent data model in Marketing Cloud allows for multiple contacts per individual customer, each with their own consent preferences for differ ent brands. This enables consent-based marketing campaigns across multiple brands in a single org. References: https://help.salesforce.com/s/articleView?id=sf.mc_ca b_consents.htm & type=5

This answer is correct because it is a recommended time to refresh the full copy sandbox. Refreshing the full copy sandbox after each major release to production can h elp ensure that the sandbox has the most updated data and metadata from production, which can facilitate testing and development activities. Refreshing the full copy sandbox too frequently can be costly and time-consuming, as it consumes a lot of storage s pace and requires data masking or anonymization. References: https://help.salesforce.com/s/articleView?id=sf.data_sandbox_implementation_tips.htm & type=5