Salesforce Certified B2C Solution Architect Exam Guide.
Salesforce Certified B2C Solution Architect credential is designed for individuals who have the knowledge, skills, and experience architecting and driving multi-cloud solutions that deliver business value for the customer.
Salesforce Certified B2C Solution Architect exam covers multiple products/features such as Service Cloud, Sales Cloud, Experience Cloud, Tableau CRM, Identity, Marketing Cloud, Heroku, B2C Commerce, Order Management, Shield Encryption, Lightning Scheduler, Digital Engagement, Marketing Connector, Service Connector, Marketing Cloud Connect, Distributed Marketing, Salesforce Connect, Heroku Connect, Customer 360 Data Manager & MuleSoft.
1. About the Salesforce Certified B2C Solution Architect Exam
- Content: 60 multiple-choice/multiple-select questions and 4 non-scored items
- Time allotted to complete the exam: 105 minutes
- Passing score: 63% (38 out of 60 Questions)
- Registration fee: USD 400, plus applicable taxes as required per local law
- Retake fee: USD 200, plus applicable taxes as required per local law
- Salesforce Certified Platform App Builder
- Salesforce Certified Integration Architecture Designer
- Salesforce Certified Marketing Cloud Email Specialist
2. Exam Outline
Discovery and Customer Success: 18%
- Given a scenario, determine how to facilitate a successful customer engagement (agenda, plan, gather requirements, document, and design).
- Given a set of business requirements and the understanding of standard Salesforce product capabilities, explain the reasoning and considerations to use a certain product.
- Given a scenario with a B2C architecture, validate that the associated systems of record, key objects, and risks have been captured and explained.
- Given a set of requirements, recommend the implementation approach and associated relative effort.
- Given a scenario, describe the appropriate themes and development lifecycle, including CI/CD and DevOps, for a multi-cloud implementation to increase operational efficiency and quality.
Functional Capabilities and Business Value: 19%
- Given a set of customer requirements for a multi-cloud solution, demonstrate how the business processes of customer acquisition, loyalty, and re-purchase can be achieved by leveraging the Salesforce B2C products.
- Given a set of customer requirements for product browsing, add to cart, and check out experience requirements for a multi-cloud solution, demonstrate how the customer experience can be achieved by leveraging Salesforce B2C products.
- Given a set of customer requirements for post-purchase activities in a multi-cloud solution, demonstrate how the customer experience can be achieved by leveraging Salesforce B2C products.
Architecture Design: 23%
- Given the understanding of retail solution architecture and integrations, illustrate how Salesforce products interact with each other and third-party systems to support consumer commerce journeys.
- Given a use case, analyze business processes and propose a customer experience solution that generates business value that meets expectations.
- Given a complex brand and localization scenario, design a multi-cloud strategy and implementation approach to support business requirements.
- Given data security and residency requirements, recommend an appropriate solution and describe how the solution’s considerations can impact implementation.
- Given a scenario, determine the considerations that should be made as a customer is identified and how the products will support the customer through their journey.
Data Models and Management: 21%
- Given the Salesforce supported standard object definitions for Commerce objects (profile, orders, products), articulate how key business entities relate between systems of record and systems of engagement.
- Given a set of business objectives and priorities, recommend an appropriate sequence for system integration, data exchanges, and process updates to satisfy known requirements, with recommendations and potential impact to overall program delivery.
- Given a set of customer requirements, articulate the consent and profile management features across multiple clouds, how they interact out-of-the-box, and when to consider custom solutions.
- Given a scenario across multiple Salesforce products, define appropriate systems of record for various data types for high-volume processing, system limitations, and recommend preferred methods for data integration.
- Given a scenario that requires knowledge of common data migration strategies and standard Salesforce data migration tools, demonstrate best practices on how to transfer data between products and development environments.
- Given a set of customer requirements, recommend an appropriate design and approach for a multi-cloud integration, understanding the out-of-the-box features, system limitations, and when custom integration is required.
- Given business requirements and use cases, recommend appropriate integration patterns based on data volume, latency, and system limitations.
- Given a B2C use case, recommend features and approaches that ensure security for both customers and internal business users while complying with regional and local legal requirements.
- Understand the recommended methods on how to integrate systems to Service Cloud, B2C Commerce, and Marketing Cloud environments using APIs and protocols that support various integration design patterns.
3. Exam Guide
4. B2C Solution Architect Certification Trail
5. B2C Solution Architect Certification Trailmix
6. B2C Solution Architect Certification Quip Link
7. Important Topics for B2C Solution Architect Certification Exam
7.1 Discovery and Customer Success: 18% (11 Questions)
- Documentation for B2C Commerce Implementation
- Functional Project Plan —Outlines and tracks the functional aspect of the implementation.
- Operating on B2C Commerce Checklist —Documents key areas such as merchandising, operations, administration, and organizational roles within the client organization.
- Architecture Diagram —Documents the entire planned system, with an emphasis on data flows and formats.
- Client Data Model —Describes the merchant’s data architecture.
- Content Inventory and Control —Describes content assets and slots and assigns IDs to them in a logical fashion.
- Storefront Reference Architecture (SFRA) Wireframes —Describes the standard page functionality of the SFRA so that the merchant can add customizations.
- Integration Review ―Documents the planned third-party integrations.
- Functional Specification Document (FSD) —Documents in detail the planned storefront functionality, separating standard functionality from customizations.
- Key participants of Discovery sessions
- Discovery Deliverables
- HLD document
- Plan Deliverables
- Project SOW
- Project plan
- Project health dashboard
- Design Deliverables
- Visual designs
- Customization wireframes
- Build Deliverables
- Functional Specification Document
- Technical Specification Document
- SFRA annotated wireframes
- Data map
- Updated project plan
- Sample product data (customer supplied)
- Production-ready data (customer supplied)
- Test plan
- Load testing SOW
- Launch Deliverables
- Launch plan
- Communication plan
- Completed launch checklist
- Launch Gate approval
- RACI stands for responsible, accountable, consulted, and informed. A RACI chart is a matrix of the activities or decision-making authorities in an organization, relative to all the people or roles
- A content slot is a preconfigured place on the storefront where a merchant can showcase products, categories, content assets, static HTML, or product recommendations
- A content asset can be a flash graphic, product carousel, product search result set, or marketing graphic
- Salesforce B2C Commerce offers two reference architectures:
- SiteGenesis Reference Architecture
- Storefront Reference Architecture (SFRA)
- Roles in a B2C Implementation Project
- Project manager
- Functional architect with ecommerce experience
- B2C Commerce–certified technical solution designer
- B2C Commerce–certified developers
- B2C Commerce UX designers
- Recommend appropriate Salesforce product as per the provided use case
- Order Management Objects
- Credit Memo
- Fulfillment Order
- Fulfillment Order Product
- Order Summary
- Salesforce Order Management includes a sample distributed order management flow package. This package includes sample flows, Apex classes, custom objects, and custom fields that together demonstrate a flow-based system for routing order items to fulfillment locations.
- Identify systems of record
- System of Record for Engagement Data
- CI/CD and DevOps, for a multi-cloud implementation
- Recommended tools for ensuring quality of deliverables. E.g. Code Quality during development
- Salesforce V2MOM
- Service Excellence
- Commerce Excellence
- Marketing Excellence
7.2 Functional Capabilities and Business Value: 19% (11 Questions)
- Omni-channel Service
- Use Cases justifying need for Digital Engagement
- Use Cases justifying need for Distributed Marketing
- B2C Commerce Solution Kits
- Audience Studio
- Marketing Cloud Connect
- Impact of using Leads vs Contacts while implementing Marketing Cloud Connect
- Recommend appropriate Marketing Cloud feature (Social Studio, Audience Builder, Triggered Send, Mobil Connect) to be used based on a given Use Case
- When to use multiple Marketing Cloud Business units
- B2C Commerce Storefront
- Einstein for Marketing Cloud
- Configure B2C Commerce product listings
7.3 Architecture Design: 23% (14 Questions)
- As Solution Architect recommend products/features based on a given multi-cloud Use Case
- Retail solution architecture and integrations
- As Solution Architect recommend sequence of implementation of different products/features based on a given multi-cloud Use Case
- B2C Commerce Replication
- B2C Commerce Cartridges
- B2C Governance and Quotas
- Use Cases justifying multiple B2C Commerce realms
- Salesforce Order Management Benefits
- Pros & Cons of Headless Commerce
- Use Cases justifying need for Headless Commerce
- Reference Architecture for Retail
- Solution Architecture for Retail and key considerations for Salesforce, Commerce, Marketing and Connectors
- Business Scenarios for Retail (Recommended Products, Solutions & Business Capabilities)
- Solution Kits for Retail and B2C. (Required Products, Workflow, Flow of Data, Design Considerations, Connector & Configurations)
- Experience Cloud
- Customer 360 Data Manager role in a multi-cloud implementation
- Identify key identifiers to be used to identify records in multi-cloud implementation
- Change Data Capture
- Benefits and Limitations of Shield Encryption
7.4 Data Models and Management: 21% (12 Questions)
- System of Record in multi-cloud implementation
- Cross Cloud Engagement Data Models
- Cross Cloud Identity Management
- Marketing Cloud Data Management
- Marketing Cloud Contact Management
- Synchronized Data Sources in Contact Builder
- Use Cases justifying need for Tokenized Sending
- General Data Protection Regulation (GDPR)
- US Privacy Laws
- Large Data Volumes
- Recommended tools/methods for de-duplication in a multi-could implementation
- Recommendations for storing Personally Identifiable Information (PII)
- OOB Duplicate Management helps manage duplicates for:
- Business accounts
- Person accounts
- Records created from custom objects
- OOB Duplicate Management Consists of
- Matching rule – matching criteria to identify duplicate records
- Duplicate Rules – determines actions to take if a duplicate is found, depending on configuration users will be alerted or blocked from creating duplicates
- A report on Duplicate Record Items can be created to get a list of duplicates identified
7.5 Integration: 19% (12)
- Integrate Service Cloud, Marketing Cloud, and Commerce Cloud with Connectors
- Benefits of Connectors vs Custom Development
- Limitations of Connectors
- Customer 360 Platform Integration Tools (Tight vs Loose Coupling, Declarative vs Programmatic)
- Recommend Integration Pattern to be used for a given Use Case. E.g. Integration Pattern to be used when integrating B2C Commerce to Data Lake, B2B Commerce to External Order Management System, Service Cloud to ERP etc
- Benefits of API led Integration
- API-led Connectivity – A methodical way to connect applications, data, and devices through reusable and purposeful APIs; the opposite of point-to-point integration
- MuleSoft Anypoint Platform
- MuleSoft recommends building and organizing APIs into three broad categories
- System APIs – handle the minutiae of connecting to systems (think databases) such that users are insulated from any changes
- Process APIs – shape data across System APIs, with the intent of modeling business needs and processes, to break down technology silos and make data more consumable
- Experience APIs – reconfigure this data so that it is most easily consumed by its intended audience through apps and devices. APIs at this level are created with reusability in mind, without a dependence on the source systems from which that data originates
- Benefits of MuleSoft Accelerators vs Custom Development
- Recommend API (SOAP, REST, Tooling, Streaming) to be utilised based on a given Use Case
- B2C Commerce storefront development tools
- Salesforce & Heroku Integration
- Connectors for Data Integration
- Recommended tools/methods for Initial Data Load in a multi-cloud implementation
- Recommend use of Heroku depending on a given Use Case
- Apex REST Services
- Apex SOAP Services
8. Additional Resources
- B2C Solution Architecture – Miro Board by Mark Cane
- How to pass the Salesforce B2C Solution Architect certification – by Christopher Ramm