Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Salesforce B2C Solution Architect's Handbook
  • Toc
  • feedback
Salesforce B2C Solution Architect's Handbook

Salesforce B2C Solution Architect's Handbook

By : Mike King
4.7 (13)
close
Salesforce B2C Solution Architect's Handbook

Salesforce B2C Solution Architect's Handbook

4.7 (13)
By: Mike King

Overview of this book

There’s a huge demand on the market for Salesforce professionals who can create a single view of the customer across the Salesforce Customer 360 platform and leverage data into actionable insights. With Salesforce B2C Solution Architect's Handbook, you’ll gain a deeper understanding of the integration options and products that help you deliver value for organizations. While this book will help you prepare for the B2C Solution Architect exam, its true value lies in setting you up for success afterwards. The first few chapters will help you develop a solid understanding of the capabilities of each component in the Customer 360 ecosystem, their data models, and governance. As you progress, you'll explore the role of a B2C solution architect in planning critical requirements and implementation sequences to avoid costly reworks and unnecessary delays. You’ll learn about the available options for integrating products with the Salesforce ecosystem and demonstrate best practices for data modeling across Salesforce products and beyond. Once you’ve mastered the core knowledge, you'll also learn about tools, techniques, and certification scenarios in preparation for the B2C Solution Architect exam. By the end of this book, you’ll have the skills to design scalable, secure, and future-proof solutions supporting critical business demands.
Table of Contents (20 chapters)
close
1
Section 1 Customer 360 Component Products
7
Section 2 Architecture of Customer 360 Solutions
13
Section 3 Salesforce-Certified B2C Solution Architect

Architecture deliverables

As a B2C solution architect, your primary role in a project is to design the overall technical solution to support business needs regardless of the component products. The way that you'll distill and communicate that design is through a set of architectural deliverables.

Creating the architectural documentation, based on the foundational decisions and requirements gathered, is the last phase of the discovery process before moving into implementation:

Figure 6.6 – Documentation

Architectural deliverables are any work product that is intended to document and communicate the design of the solution to other stakeholders, including the implementation team. These can be documents, presentations, diagrams, spreadsheets, wiki pages, or anything else that helps to take the solution from the theoretical to the concrete. Your role is to take those business needs, such as the ability to pull up a customer's order history when...

bookmark search playlist font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete