Book Image

Salesforce Data Architect Certification Guide

By : Aaron Allport
Book Image

Salesforce Data Architect Certification Guide

By: Aaron Allport

Overview of this book

The Salesforce Data Architect is a prerequisite exam for the Application Architect half of the Salesforce Certified Technical Architect credential. This book offers complete, up-to-date coverage of the Salesforce Data Architect exam so you can take it with confidence. The book is written in a clear, succinct way with self-assessment and practice exam questions, covering all the topics necessary to help you pass the exam with ease. You’ll understand the theory around Salesforce data modeling, database design, master data management (MDM), Salesforce data management (SDM), and data governance. Additionally, performance considerations associated with large data volumes will be covered. You’ll also get to grips with data migration and understand the supporting theory needed to achieve Salesforce Data Architect certification. By the end of this Salesforce book, you'll have covered everything you need to know to pass the Salesforce Data Architect certification exam and have a handy, on-the-job desktop reference guide to re-visit the concepts.
Table of Contents (23 chapters)
1
Section 1: Salesforce Data Architect Theory
9
Section 2: Salesforce Data Architect Design
15
Section 3: Applying What We've Learned – Practice Questions and Revision Aids

Implementing MDM

As part of the fundamental design of an MDM strategy, consideration should be given to the system landscape, budget, and technical capabilities within an organization for implementing MDM. Several models for implementation exist and can be broadly bucketed into the following categories:

  • Source of record
  • Central registry
  • Consolidated golden record
  • Coexistence of the golden record

These different implementation methods are explained here.

Source of record

A single system can be identified as the source of record or definitive source of information. All data operations are performed in that one system or application. This implementation model is extremely simple, and therefore doesn't lend itself well to organizations of siloed departments or where data federation is necessary. Take my experience of the car dealership. I'm represented twice in the IT enterprise, as a prospect in one system and a qualified (and converted) sales...