Book Image

Salesforce Data Architecture and Management

By : Ahsan Zafar
Book Image

Salesforce Data Architecture and Management

By: Ahsan Zafar

Overview of this book

As Salesforce orgs mature over time, data management and integrations are becoming more challenging than ever. Salesforce Data Architecture and Management follows a hands-on approach to managing data and tracking the performance of your Salesforce org. You’ll start by understanding the role and skills required to become a successful data architect. The book focuses on data modeling concepts, how to apply them in Salesforce, and how they relate to objects and fields in Salesforce. You’ll learn the intricacies of managing data in Salesforce, starting from understanding why Salesforce has chosen to optimize for read rather than write operations. After developing a solid foundation, you’ll explore examples and best practices for managing your data. You’ll understand how to manage your master data and discover what the Golden Record is and why it is important for organizations. Next, you'll learn how to align your MDM and CRM strategy with a discussion on Salesforce’s Customer 360 and its key components. You’ll also cover data governance, its multiple facets, and how GDPR compliance can be achieved with Salesforce. Finally, you'll discover Large Data Volumes (LDVs) and best practices for migrating data using APIs. By the end of this book, you’ll be well-versed with data management, data backup, storage, and archiving in Salesforce.
Table of Contents (14 chapters)
Section 1: Data Architecture and Data Management Essentials
Section 2: Salesforce Data Governance and Master Data Management
Section 3: Large Data Volumes (LDVs) and Data Migrations


  1. Precision Printing (PP) has been using Salesforce for 15 years and has a very mature DevOps process. They developed a custom quoting solution on the Salesforce Platform that has served them well over the years, but it's showing signs of aging and requires significant maintenance efforts.

PP's management has decided to implement the Salesforce CPQ solution. What options should the architect propose for the legacy solution when Salesforce CPQ is live in production?

a) Remove all users' access and keep the legacy solution running. Users will just forget about it.

b) When the Salesforce CPQ-managed package is installed, it will automatically remove the legacy application from the organization.

c) Migrate or archive any data from the legacy solution. Then, proceed to remove all legacy objects, Apex code, Visualforce pages, and other metadata associated with the legacy solution.

d) Run both solutions at the same time and give users the option...