Free Salesforce Certified B2C Solution Architect (Arch-302) Exam Dumps July 2026

This answer is correct because it is the primary system that should be used for all authentication between B2C Commerce site and Experience Cloud site. Salesforce Identity can act as an identity provider (IDP) for both B2C Commerce and Experience Cloud, and it can provide a single login and data experience between the two sites. Salesforce Identity can also store customer profile data in a single place and sync it across systems. Reference: https://help.salesforce.com/s/articleView?id=sf.b2c_commerce_service_cloud_integration.htm&type=5

Marketing Cloud should be the single source of truth for customer journey flow, which is the sequence of interactions that a customer has with a brand across different channels and touchpoints. Marketing Cloud can help design, execute, and optimize customer journeys using Journey Builder, which can leverage data from other systems, such as B2C Commerce or Service Cloud, to trigger or personalize journeys. Reference: https://help.salesforce.com/s/articleView?id=sf.mc_jb_journey_builder.htm&type=5

CDP is a feature that allows creating a unified and holistic view of the customer across different systems and channels. CDP can use various identifiers, such as email, phone, or social media, to recognize customers as humans and extend existing records related to that human across connected systems, such as B2C Commerce, Service Cloud, and Marketing Cloud. CDP can also assign a consistent Global Party ID to each human, which can be used as a unique identifier across the systems. Reference: https://www.salesforceben.com/the-drip/complete-guide-to-customer-data-platforms-and-salesforce-cdp/

Syncing Person Account object can help map subscriber data in Marketing Cloud when the company has Person Account set up on their Sales Cloud. This can enable bi-directional data integration between Sales Cloud and Marketing Cloud for Person Accounts, which are records that combine both Account and Contact information for individuals. Reference:

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

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

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

This answer is correct because it is the primary system that should be used for all authentication between B2C Commerce site and Experience Cloud site. Salesforce Identity can act as an identity provider (IDP) for both B2C Commerce and Experience Cloud, and it can provide a single login and data experience between the two sites. Salesforce Identity can also store customer profile data in a single place and sync it across systems. Reference: https://help.salesforce.com/s/articleView?id=sf.b2c_commerce_service_cloud_integration.htm&type=5