B2C-Solution-Architect Exam Questions & Answers

A) Enabling customer service agents to enroll customers in an Abandoned Cart Journey in Marketing Cloud if an interaction does not result in the processing of an order can help increase checkouts and decrease the time from adding items to completing a checkout by sending targeted and personalized messages to customers who have left items in their carts without purchasing them. This can help re-engage customers, remind them of their cart contents, and encourage them to complete their orders. D. Monitoring the cart items and time since it has been active in B2C Commerce and sending a reminder and checkout incentive 18 hours after the cart was last modified can help increase checkouts and decrease the time from adding items to completing a checkout by leveraging customer behavior data, timing, and urgency to motivate customers to buy their items before they are out of stock or unavailable. This can help reduce cart abandonment, increase conversion rates, and boost customer loyalty. Reference:

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

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

These answers are correct because they are actions that a Solution Architect should take to accurately capture the requirements for a multi-cloud solution design. Including functional and technical experts across discovery workshops can help ensure that the requirements and priorities are captured from different perspectives and domains. Drafting a requirements and process document can help document the business needs, expectations, and constraints for the solution design. Inviting key business and technical/design team stakeholders to review and approve the document can help validate the requirements and ensure alignment. Reference: https://trailhead.salesforce.com/en/content/learn/modules/solution-design/solution-design-process

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

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

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

A support case is a record that tracks a customer's question, problem, feedback, or request for service. A support case can be created manually by a user or automatically by an email, web form, chat, etc. A support case can be assigned to a user or a queue for further action or resolution. To automatically route incoming support cases to the correct team based on their tier level, a Solution Architect should configure the following:

Assignment Rules: Assignment rules are rules that define how to assign cases to users or queues based on certain criteria or conditions. Assignment rules can help automate the case assignment process and ensure that cases are routed to the right people or teams based on their skills, availability, workload, etc.

Queues: Queues are lists of records that need to be worked on by multiple users or teams. Queues can help organize and prioritize workloads and distribute cases among users or teams based on their capacity or expertise.

Option C is incorrect because support processes are processes that define the stages or statuses that a case goes through from creation to closure. Support processes do not affect how cases are assigned to users or queues based on tier level. Option D is incorrect because auto response rules are rules that define how to send automatic email responses to customers when cases are created or updated based on certain criteria or conditions. Auto response rules do not affect how cases are assigned to users or queues based on tier level. Reference:

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

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

https://help.salesforce.com/s/articleView?id=sf.queues_overview.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. 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