QUESTION: 53

A company plans to build a new B2C Commerce storefront for a popular segment of products that generate high-volume sales. Their team is evaluating whether B2C Commerce is the right platform to build this storefront, and they are specifically concerned about how quotas and limits directly impact the efficiency and stability of solutions built on the platform.

Which two considerations should a Solution Architect keep in mind when considering B2C Commerce Governance and Quotas?

Choose 2 answers

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.
For sandbox instances, quotas can be softened by exporting them from a production instance and importing them onto a sandbox instance. This approach lets Solution Architects match the development environment to the production environment.
Unless a site :s experiencing performance issues, the Solution Architect car assume that quota violations have not occurred.
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.

Answer(s): A,D

Explanation:

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.

Reference:

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

Reveal Solution Next Question

QUESTION: 54

An organization wants to add Service Cloud to their existing Salesforce Org currently hosting Sales Cloud. They know that an integrated customer service experience is a key component of a successful long-term relationship with their customers. After doing some research they learned that the Service Cloud connector can help start their implementation and they are now ready to proceed.

Which two functionality considerations should they be aware of when introducing the B2C Commerce to Service Cloud Connector into an existing Salesforce Org?

Choose 2 answers

In order to implement the Service Cloud Connector it is necessary to enable Person Accounts, a change which cannot be reverted once implemented.
The Service Cloud Connector is distributed as a managed package that can be extended to meet client-specific needs but with core functionality that cannot be altered.
The Service Cloud Connector natively supports accounts and contacts, households, and multi- brand customer models.
The Service Cloud Connector provides a collection of Lightning and Visualforce components that display customer and order information within Service Cloud, which needs to be customized and deployed by a developer.

Answer(s): A,B

Explanation:

The B2C Commerce to Service Cloud Connector is a solution that enables integration between B2C Commerce and Service Cloud. It allows displaying customer and order information in Service Cloud, creating orders on behalf of customers, and synchronizing customer data between the two systems.
When introducing the Service Cloud Connector into an existing Salesforce Org, the following functionality considerations should be aware of:

In order to implement the Service Cloud Connector it is necessary to enable Person Accounts, a change which cannot be reverted once implemented. Person Accounts are a type of account in Salesforce that combines an account and a contact into a single record. The Service Cloud Connector requires Person Accounts to store customer information from B2C Commerce. Enabling Person Accounts is an irreversible change that affects the entire Salesforce Org and may have implications for other features or customizations.

The Service Cloud Connector is distributed as a managed package that can be extended to meet client-specific needs but with core functionality that cannot be altered. A managed package is a collection of application components that can be installed from AppExchange or other sources. The Service Cloud Connector is a managed package that provides core functionality for integrating B2C Commerce and Service Cloud. The core functionality cannot be modified or deleted, but it can be extended or customized using Apex code, Visualforce pages, or Lightning components.

Option C is incorrect because the Service Cloud Connector does not natively support accounts and contacts, households, and multi-brand customer models. It only supports person accounts as a customer model by default. Option D is incorrect because the Service Cloud Connector provides a collection of Lightning components that display customer and order information within Service Cloud, which do not need to be customized or deployed by a developer.

Reference:

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

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

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

Reveal Solution Next Question

QUESTION: 55

A financial services company wants to implement Service Cloud and Marketing Cloud. A number of profile attributes required for personalization in Marketing Cloud were identified as personally identifiable information (PII) and are too sensitive to be stored in Salesforce.

Tokenized Sending was presented as a way to address these concerns.

Which two implications should a Solution Architect consider if Marketing Cloud Connect is to be used for cloud integration?

Choose 2 answers

The synchronized data extensions will include the token and all PII attributes
All emails will need to be sent through Marketing Cloud or Marketing Cloud Connect to avoid disruptions
The standard email address field for contacts and leads needs to be populated with a token
The token with all supporting attributes will need to be stored in Service Cloud

Answer(s): A,C

Explanation:

Tokenized Sending is a feature in Marketing Cloud that allows sending messages with data that is too sensitive to store in Salesforce due to laws, regulations, or security policies. Tokenized Sending uses an API call to exchange data from an external system with Marketing Cloud at send time, without storing the data in Salesforce. Marketing Cloud Connect is a feature that enables integration between Marketing Cloud and other Salesforce clouds such as Service Cloud.
When using Tokenized Sending with Marketing Cloud Connect, the following implications should be considered:

The synchronized data extensions will include the token and all PII attributes. Synchronized data extensions are tables in Marketing Cloud that store data from other Salesforce clouds using data synchronization in Marketing Cloud Connect.
When using Tokenized Sending, the synchronized data extensions will include the token as well as all personally identifiable information (PII) attributes such as name, email, phone, etc. The token will serve as the subscriber key and contact key in Marketing Cloud, while the PII attributes will be used for personalization and segmentation.

The standard email address field for contacts and leads needs to be populated with a token.
When using Tokenized Sending, the standard email address field for contacts and leads in other Salesforce clouds needs to be populated with a token instead of an actual email address. The token resembles a standard email address but contains encrypted information about the subscriber. The token is used to exchange data with the external system at send time and send messages to the actual email address.

Option B is incorrect because not all emails need to be sent through Marketing Cloud or Marketing Cloud Connect to avoid disruptions when using Tokenized Sending. However, it is recommended to do so to ensure consistent tracking and deliverability data across clouds. Option D is incorrect because the token with all supporting attributes does not need to be stored in Service Cloud when using Tokenized Sending. The token and the attributes are stored in the external system and only exchanged with Marketing Cloud at send time.

Reference:

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

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

Reveal Solution Next Question

QUESTION: 56

A company recently launched their ecommerce sites for three countries: Australia, New Zealand, and Singapore. The company is now looking to set up marketing automations using Marketing Cloud.

Their B2C Commerce is configured with two realms: ANZ and SE Asi

Each country has a site within their respective realm: Australia and New Zealand sites are within ANZ and Singapore is within SE Asia.
Which account hierarchy should a Solution Architect recommend for the Marketing Cloud set up?
Use a separate Marketing Cloud tenant for each site
Use a separate Marketing Cloud tenant for each realm and map business units to sites within each realm
Use a single Marketing Cloud tenant and map business units to each site irrespective of the realm
Use a single Marketing cloud tenant and map business units to each realm

Answer(s): C

Explanation:

Marketing Cloud account hierarchy is the way of organizing Marketing Cloud accounts and business units to support different business needs and use cases. A Marketing Cloud tenant is a top-level account that contains one or more business units. A business unit is a sub-account that can have its own data, content, users, and permissions. To set up Marketing Cloud account hierarchy for a company that has ecommerce sites for three countries: Australia, New Zealand, and Singapore, a Solution Architect should recommend the following:

Use a single Marketing Cloud tenant and map business units to each site irrespective of the realm. This option allows the company to have a centralized account that can manage all the sites across different countries and regions. It also allows the company to have separate business units for each site that can have their own data, content, users, and permissions. This way, the company can maintain consistency and compliance across all the sites, while also enabling personalization and segmentation for each site.

Option A is incorrect because using a separate Marketing Cloud tenant for each site is not necessary or advisable. It would create complexity and inefficiency in managing multiple accounts and duplicating data and content across them. It would also increase the cost and maintenance of the solution. Option B is incorrect because using a separate Marketing Cloud tenant for each realm and mapping business units to sites within each realm is not optimal or scalable. It would create inconsistency and fragmentation between the realms and limit the ability to share data and content across them. It would also increase the cost and maintenance of the solution. Option D is incorrect because using a single Marketing Cloud tenant and mapping business units to each realm is not sufficient or flexible. It would not allow the company to have separate data, content, users, and permissions for each site within a realm. It would also limit the ability to personalize and segment for each site.

Reference:

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

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

Reveal Solution Next Question

Free B2C-SOLUTION-ARCHITECT Exam Braindumps (page: 15)

QUESTION: 53

Explanation:

Reference:

QUESTION: 54

Explanation:

Reference:

QUESTION: 55

Explanation:

Reference:

QUESTION: 56

Explanation:

Reference:

B2C-SOLUTION-ARCHITECT Exam Discussions & Posts