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

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

An abandoned cart solution is a solution that allows sending personalized and timely email reminders to customers who have added items to their shopping cart but have not completed the purchase. An abandoned cart solution can help increase conversion rates, revenue, and customer loyalty. To implement an abandoned cart solution for their ecommerce storefront in Marketing Cloud, a Solution Architect should follow the following process:

Implement collect.js in the ecommerce storefront. Collect.js is a JavaScript code that allows tracking customer behavior and interactions on the ecommerce website, such as browsing products, adding items to cart, etc. Collect.js sends this behavioral data to Marketing Cloud for further analysis and action.

Create a behavioral trigger. A behavioral trigger is a rule that defines how to map behavioral data to a target data extension when a customer takes a particular action, such as abandoning a cart or browser session. A behavioral trigger can help automate the data flow and segmentation process based on customer behavior.

Create an email in Marketing Cloud. An email is a message that contains text, images, links, and other content that can be sent to customers via email. An email can be created using Content Builder, a tool that allows designing and managing email content in Marketing Cloud.

Create a journey. A journey is a sequence of messages and actions that are triggered by customer events or attributes. A journey can be created using Journey Builder, a tool that allows designing and managing customer journeys in Marketing Cloud.

Option A is incorrect because exporting the purchase data from B2C Commerce, importing the data into Marketing Cloud, and creating an email in Content Builder is not a sufficient or efficient process for implementing an abandoned cart solution. This process does not involve creating a behavioral trigger or a journey, which are essential for sending timely and personalized email reminders based on customer behavior. Option B is incorrect because setting up Marketing Cloud Connector, creating an email in Marketing Cloud, and creating a send trigger is not a suitable or scalable process for implementing an abandoned cart solution. Marketing Cloud Connector is a feature that allows integrating Marketing Cloud with other Salesforce products, such as Sales Cloud or Service Cloud. It is not necessary or relevant for integrating Marketing Cloud with B2C Commerce. A send trigger is a rule that defines how to send an email to customers based on certain criteria or conditions. However, a send trigger does not capture or leverage the behavioral data collected by collect.js, which is crucial for creating an effective abandoned cart solution. Option D is incorrect because setting up Einstein Recommenda tions, setting up Marketing Cloud Connector, and creating an email in Marketing Cloud is not a relevant or optimal process for implementing an abandoned cart solution. Einstein Recommendations is a feature that allows generating personalized product recommendations based on customer behavior and preferences. It is not directly related to creating an abandoned cart solution, although it can be used to enhance the email content with relevant recommendations. As mentioned before, Marketing Cloud Connector is not necessary or relevant for integrating Marketing Cloud with B2C Commerce. This process also does not involve creating a behavioral trigger or a journey, which are essential for sending timely and personalized email reminders based on customer behavior. References:

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

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

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

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

This answer is correct because it is a way to store payment information while still maintaining security and compliance. A tokenized payment card is a method that replaces sensitive card data with a unique identifier or token that cannot be mathematically reversed. The actual card data is stored in a secure vault by a payment processor or gateway. This way, the company can facilitate one-click ordering and automatic payment without exposing or storing the actual card data. References: https://help.salesforce.com/s/articleView?id=sf.b2c_commerce_payment_processing.htm & type=5

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

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

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

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

To enable the scenario of sending promotional emails with coupon offers generated in B2C Commerce, the following elements are required:

A B2C Commerce cartridge to call Marketing Cloud APIs, such as the Transactional Messaging API, to trigger the email journey and pass the coupon code as a data attribute.

A Marketing Cloud Installed Package to create an API integration between B2C Commerce and Marketing Cloud and provide authentication credentials and permissions.

A B2C Commerce storefront to generate and manage the coupon codes and redemption logic. References: https://developer.salesforce.com/docs/commerce/sfra/marketing-cloud/transactional-messaging-api https://developer.salesforce.com/docs/commerce/sfra/marketing-cloud/marketing-cloud-integration https://documentation.b2c.commercecloud.salesforce.com/DOC1/topic/com.demandware.dochelp/content/b2c_commerce/topics/promotions/b2c_coupon_codes.html

This answer is correct because it is a way to respond to the management team’s request to help formula te a roadmap for these new capabilities using the relationship design process. The relationship design process is a method that centers relationships as the building blocks of business and social value. It is based on four mindsets that can help design pro ducts and services from a place of compassion: compassion, intention, courage, and reciprocity. By facilitating a workshop with the management team, applying the relationship design process, a Solution Architect can help create a roadmap that aligns with b usiness objectives and builds customer trust. References: https://www.salesforce.com/blog/how-relationship-design-works/

A. Additional infrastructure (for example Heroku servers) may be required to host the application when using a headless approach. This can increase the complexity, cost, and maintenance of the solution. A Solution Architect should consider the trade-offs between flexibility and simplicity when choosing a headless approach. B. Features that are available by default in the Storefront Reference Architecture (SFRA) app will need to be custom built in custom frameworks when using a headless approach. This can increase the development time, effort, and risk of the solution. A Solution Architect should consider the benefits and drawbacks of using SFRA versus custom frameworks when choosing a headless approach. D. Available Service, Marketing, and LINK accelerators may not work without modifications when using a headless approach. This can limit the integration capabilities and functionality of the solution. A Solution Architect should consider the compatibility and extensibility of the accelerators when choosing a headless approach. References:

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

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

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

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

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

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