Free Salesforce Certified B2C Solution Architect B2C-Solution-Architect Exam Questions

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

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

Experience Cloud is a product that allows creating and managing digital experiences for customers, partners, employees, and communities. Experience Cloud can be integrated with external payment gateways and Pardot to offer secure and personalized experiences for members who want to set up recurring donations. To increase security for their existing users, a Solution Architect can recommend the following options:

Implement high-assurance requirements for Experience Cloud profiles. High-assurance requirements are settings that define the level of security and identity verification needed for users to access certain pages or features in Experience Cloud. High-assurance requirements can help prevent unauthorized or fraudulent access to sensitive or confidential data or transactions, such as recurring donations.

Add a login flow that defines the scope of user access authorized by authentication providers. A login flow is a process that allows customizing the user login experience in Experience Cloud using various actions, such as collecting information, displaying messages, updating records, etc. A login flow can help define the scope of user access authorized by authentication providers, such as social media accounts or SAML-based identity providers. This can help limit or restrict the access of users based on their authentication method or credentials.

Develop login flows to change the user's session security level to initiate third-party identity verification. A session security level is a setting that determines the level of security and identity verification required for a user's session in Experience Cloud. A session security level can be changed using login flows to initiate third-party identity verification, such as SMS verification, email verification, biometric verification, etc. This can help enhance the security and trust of the user's session and prevent unauthorized or fraudulent access to sensitive or confidential data or transactions, such as recurring donations.

Option C is incorrect because replacing Pardot with Marketing Cloud to implement SMS for multi-factor authentication is not a valid or feasible option to increase security for their existing users. Pardot is a product that allows creating and managing B2B marketing campaigns and activities, such as email marketing, lead generation, lead nurturing, etc. Marketing Cloud is a product that allows creating and managing B2C marketing campaigns and activities, such as email marketing, mobile marketing, social media marketing, etc. Replacing Pardot with Marketing Cloud would not only be costly and complex, but also unnecessary and irrelevant for their use case of setting up recurring donations. Moreover, implementing SMS for multi-factor authentication does not require replacing Pardot with Marketing Cloud, as it can be done using other methods or tools, such as login flows or third-party identity verification services. Option D is incorrect because maintaining GAuth tokens for existing Experience Cloud profiles is not an option or a way to increase security for their existing users. GAuth tokens are tokens that are used by Google Authenticator, an app that generates one-time passwords for two-factor authentication. GAuth tokens are not related to Experience Cloud profiles or their security settings. Reference:

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

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

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

The Secondary Instance Group is used for sandboxes in B2C Commerce. Adding new sandboxes to this group does not require creating a new realm or adding instances to the Primary Instance Group, which is used for production and staging instances. Reference: https://developer.salesforce.com/docs/commerce/b2c-commerce/guide/b2c-developer-sandboxes.html

API-led connectivity is a method of connecting data to applications through reusable and purposeful APIs. MuleSoft Accelerator for Salesforce B2C Commerce Cloud is a solution that uses API-led connectivity to integrate B2C Commerce with other systems such as PIM, ERP, or Service Cloud. The benefits of API-led connectivity while implementing the MuleSoft accelerator for B2C Commerce are:

It enables self-service and an increase in productivity through reusable microservices and APIs. API-led connectivity allows developers to create modular and reusable microservices and APIs that can be easily discovered, accessed, and composed by other developers or business users. This reduces duplication of effort, increases agility, and accelerates time to market.

It enforces a distributed approach and allows for the creation of Experience APIs, Data APIs, and System APIs. API-led connectivity follows a distributed approach that decouples data sources from data consumers, enabling greater scalability, flexibility, and security. It also allows for the creation of three layers of APIs: Experience APIs that tailor data to specific channels or devices, Data APIs that orchestrate data from multiple sources, and System APIs that connect to core systems of record.

Option B is incorrect because API-led connectivity does not let the business quickly integrate different systems without involving IT. It requires IT to design, build, and manage the APIs that enable integration. Option C is incorrect because API-led connectivity does not offer a template-driven approach for development. It offers a methodology and a framework for developing APIs based on best practices. Reference:

https://www.mulesoft.com/resources/api/what-is-api-led-connectivity

https://www.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-salesforce-b2c-commerce-cloud/

This solution allows the company to send the electronic receipt in near real time 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. Reference: 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

These answers are correct because they are systems that can meet the company's requirements for delivering a full list of all customer orders throughout their engagement lifetime, providing lifetime engagement tracking and history of the customer, and calculating the lifetime value of customers based on their orders. Salesforce Order Management can manage order lifecycle from capture to fulfillment across multiple channels. Service Cloud can provide a complete view of customer interactions across sales, service, marketing, and commerce. Marketing Cloud can track customer engagement across email, mobile, social, web, and more. CRM Analytics can provide insights into customer lifetime value based on order data and engagement history. Reference: https://help.salesforce.com/s/articleView?id=sf.b2c_commerce_oms_integration.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.b2c_commerce_service_cloud_integration.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.icx_b2c_crosscloudengagement_connectors.htm&language=en_US&type=5 https://www.salesforce.com/products/marketing-cloud/what-is-marketing-cloud/

B) Extending the B2C Commerce storefront to trigger emails via Marketing 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 personalization 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. The 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. Reference: https://developer.salesforce.com/docs/commerce/sfra/marketing-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

A real-time inventory service is a service that allows accessing and displaying the current inventory levels of products or SKUs across different locations or sources, such as warehouses or stores. A real-time inventory service can help provide accurate and consistent inventory information to customers and staff, avoid overselling or underselling products, and optimize order fulfillment and delivery processes. To define an architectural solution that both mitigates the risk of overselling and allows for a positive customer service experience in the event inventory falls short, a Solution Architect should include the following ways:

Call real-time inventory services directly throughout the product grid and checkout experience to ensure accurate inventory count for every available SKU is displayed to the shopper. By calling real-time inventory services directly throughout the product grid and checkout experience, the Solution Architect can provide up-to-date and reliable inventory information to shoppers on every page where they can view or select products or SKUs. This can help prevent shoppers from adding out-of-stock items to their cart or placing orders that cannot be fulfilled.

Use Order Management capabilities to support the redirection of orders placed to warehouses or stores showing inventory for all, or most, of the SKU-level products in the order. By using Order Management capabilities, such as Salesforce Order Management or B2C Commerce Order Management, the Solution Architect can support the redirection of orders placed to different locations or sources based on their inventory availability and other factors, such as cost, speed, or sustainability. This can help optimize order fulfillment and delivery processes, reduce shipping costs and delays, and increase customer satisfaction.

Call real-time inventory services on product and cart pages to confirm that inventory has not changed. By calling real-time inventory services on product and cart pages, the Solution Architect can confirm that inventory has not changed since the last page load or refresh. This can help detect any discrepancies or conflicts between the displayed inventory information and the actual inventory levels, such as when another shopper has purchased the same item in the meantime. This can help avoid overselling products or disappointing customers with inaccurate inventory information.

Option A is incorrect because using Service Cloud to text all registered customers when any product comes back in stock is not a way to mitigate the risk of overselling or allow for a positive customer service experience in the event inventory falls short. Service Cloud is a product that allows managing customer service interactions across different channels and systems. Service Cloud does not provide any functionality or capability related to real-time inventory services or order management. Option D is incorrect because using both B2C Commerce and Marketing Cloud to offer email notifications for products that are back in stock is not a way to mitigate the risk of overselling

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. Reference: https://help.salesforce.com/s/articleView?id=sf.mc_co_marketing_cloud_connect_best_practices.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.b2c_commerce_service_cloud_integration.htm&type=5

Contact, Order, and Product are the standard objects from Sales Cloud that a Solution Architect should map to B2C Commerce objects. Contact represents a person who is a customer or a potential customer of the company. Order represents an order placed by a customer for one or more products. Product represents an item or service that the company sells. These objects can be mapped to B2C Commerce objects such as Customer, Order, and Product using the B2C Commerce APIs or the Commerce Cloud Connector.

A Marketing Cloud 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 multiple Marketing Cloud instances or business units. Reference: 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

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

Queues and Assignment rules are features of Service Cloud that allow incoming support cases to be automatically routed to the correct team or agent based on predefined criteria, such as customer purchases, case origin, or case priority.

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

B) Using a Salesforce record ID as a single unique identifier to apply across channels and clouds can help ensure GDPR compliance by enabling data portability, deletion, and anonymization across systems. This can also reduce data duplication and improve data quality. D. Setting field-level encryption across B2C Commerce, Marketing Cloud, and Service Cloud can help ensure GDPR compliance by protecting sensitive data from unauthorized access or disclosure. This can also help meet the requirements of data minimization and pseudonymization. Reference:

https://trailhead.salesforce.com/en/content/learn/modules/gdpr_basics/gdpr_basics_principles

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

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

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