A company is implementing a multi-locale solution that includes B2C Commerce, Service Cloud, and Marketing Cloud. Order confirmation emails are triggered from either B2C Commerce or Service Cloud and sent from Marketing Cloud.
What are two possible reasons why the shipping method name and description can be missing when these emails are triggered for languages other than US English, while other translated content appears correctly?
Choose 2 answers
The shipping method name and description can be missing when order confirmation emails are triggered for languages other than US English, while other translated content appears correctly, for the following possible reasons:
The name and description for the shipping method are not set up correctly in B2C Commerce or Service Cloud for the requested locale. The shipping method name and description are stored as attributes in B2C Commerce or Service Cloud, and they need to be translated and localized for each supported locale. If the translation or localization is missing or incorrect, the order confirmation email may not display them properly.
The ShippingMethods data extension is missing the label and description field for the corresponding locale. The ShippingMethods data extension is a table in Marketing Cloud that stores the shipping method information for each locale. It has fields for label and description that need to match the values in B2C Commerce or Service Cloud. If the fields are missing or mismatched for a certain locale, the order confirmation email may not display them properly.
Option B is incorrect because the subscriber in Marketing Cloud does not need to have a preferred locale set. The locale can be determined by the order data or the storefront language. Option C is incorrect because the locale can be set correctly in the email template using AMPscript or SSJS variables. Reference:
https://help.salesforce.com/s/articleView?id=sf.mc_co_transactional_messaging.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.mc_co_order_confirmation_email.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.mc_co_shipping_methods_data_extension.htm&type=5
Refer to the exhibit.

A company plans to adopt Salesforce for a number of their needs, including an internal CRM, a public B2C Commerce storefront with order management functionality, and an extensible API framework to integrate with other systems, as well as marketing automation. The overall system landscape of the proposed solution is shown above.
Which three considerations are important for this scenario? Choose 3 answers
Option A is correct because the Salesforce Platform can be used for customer master and consent management, or it can integrate with a third-party Master Data Management system. This is an important consideration for this scenario, as it affects the data quality, security, and governance of customer data across multiple Salesforce clouds and systems.
Option C is correct because Order Management System (OMS) is a B2C Commerce product but it does not run natively on the core Salesforce Platform. This is an important consideration for this scenario, as it affects the integration, performance, and scalability of OMS with other Salesforce clouds and systems.
Option D is correct because Marketing Cloud enables personalization, journey orchestration, and cross-channel messaging. This is an important consideration for this scenario, as it affects the marketing strategy, campaign design, and customer engagement of the company.
Option B is incorrect because Tableau does not require MuleSoft in order to access data outside of the Salesforce Platform. Tableau can connect to various data sources using native connectors or custom connectors without relying on MuleSoft.
[Get Started with B2C Solution Architect Cert Prep - Trailhead]
[Certification - B2C Solution Architect - Trailhead]
B2C Solution Architect Certification Guide | Salesforce Ben
A company is currently Implementing B2C Commerce and wants to use Marketing Cloud to send transactional emails like the Welcome Email, Order Confirmation, and Order Status Update Email.
Which three steps are required to configure the Marketing Cloud Connector for triggered emails?
Choose 3 answers
Option A is correct because configuring REST services in B2C Commerce is a necessary step to enable authentication and communication with Marketing Cloud via its API integration and to initiate transactional email delivery using Marketing Cloud's Transactional Messaging REST API.
Option C is correct because creating an API integration in Marketing Cloud using Installed Packages is a necessary step to provision access to Marketing Cloud APIs by external systems like B2C Commerce and to generate an API key and secret for authentication purposes.
Option D is correct because customizing the B2C Commerce storefront to trigger Marketing Cloud Transactional Messages at strategic points in the customer's experience is a necessary step to invoke Marketing Cloud's Transactional Messaging REST API with a payload that informs message contents and recipients.
Option B is incorrect because front-end development capabilities are not required to configure the Marketing Cloud Connector for triggered emails, but rather to customize the B2C Commerce storefront and the email templates in Marketing Cloud.
Option E is incorrect because integrating Marketing Cloud and B2C Commerce to provide Marketing Cloud with B2C Commerce order and customer information on a nightly basis via SFTP is not required to configure the Marketing Cloud Connector for triggered emails, but rather to enable data synchronization and segmentation for marketing campaigns.
Get Started with B2C Solution Architect Cert Prep - Trailhead
Certification - B2C Solution Architect - Trailhead
A company needs to have specific fields encrypted in the user interface on the contact record in Service Cloud as well as on some fields in data extensions that exist only in the Marketing Cloud. The merchant believes that Salesforce Shield Encryption is a suitable solution.
Which two considerations are relevant for the merchant when determining an appropriate solution?
Choose 2 answers
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. Reference:
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 holding company owns and operates a large number of brands internationally. They are interested in migrating from a home-grown solution to a Salesforce multi-cloud solution as part of a new digitalization initiative to optimize IT spending across the brands. The brand any would like to operate B2C Commerce sites supported by Service Cloud for their agents, and use Marketing Cloud to drive consumer engagement. Given that the company has operations and customers in Brazil Canada Europe Japan Russia and the United States, which two recommendations should a Solution Architect make to ensure that customer experiences are compliant with all domestic and international regulations related to data privacy and security?
Choose 2 answers
Shield is a set of security tools that can help protect sensitive data across Salesforce products, including encryption, auditing, and monitoring. Shield can help comply with data privacy and security regulations that require geo-fencing or data residency. Salesforce Connect is a feature that allows accessing data from external sources without storing it in Salesforce. Salesforce Connect can help comply with data privacy and security regulations that restrict cross-border data transfers or require data localization. Reference: https://www.salesforce.com/products/platform/products/shield/ https://help.salesforce.com/s/articleView?id=sf.data_source_connect.htm&type=5
Brian Carter
10 days agoDorothy Turner
12 days agoCharles Morgan
1 month agoMatthew Jones
1 month agoTiffany Baker
1 month agoJennifer Rogers
1 month agoWilliam Jones
1 month agoGeorge Scott
29 days agoLisa Nguyen
25 days agoBarbra
2 months agoJerlene
2 months agoLachelle
3 months agoHelene
3 months agoRosita
3 months agoBronwyn
3 months agoBarb
4 months agoLizette
4 months agoArlette
4 months agoHyun
4 months agoBoris
5 months agoCarmen
5 months agoGlory
5 months agoSean
5 months agoKrissy
6 months agoAntione
6 months agoTamie
6 months agoBernardo
6 months agoDallas
7 months agoFreeman
7 months agoLonny
7 months agoLeota
7 months agoSue
8 months agoDorcas
8 months agoBelen
8 months agoVeronica
8 months agoArlette
9 months agoHortencia
9 months agoReyes
9 months agoCorazon
9 months agoMaile
11 months agoShawnda
12 months agoGayla
1 year agoFletcher
1 year agoJoni
1 year agoLynelle
1 year agoCordelia
1 year agoCarolynn
1 year agoGianna
2 years agoFairy
2 years agoGail
2 years agoRosalind
2 years agoStanton
2 years agoShawnna
2 years agoGilma
2 years agoJaime
2 years agoFelton
2 years agoEveline
2 years agoAngelica
2 years agoPauline
2 years agoCarri
2 years agoMuriel
2 years agoDorinda
2 years agoKerrie
2 years agoArminda
2 years agoSarah
2 years agoMarg
2 years agoLashaun
2 years ago