Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Salesforce Data Architecture and Management

You're reading from   Salesforce Data Architecture and Management A pragmatic guide for aspiring Salesforce architects and developers to manage, govern, and secure their data effectively

Arrow left icon
Product type Paperback
Published in Jul 2021
Publisher Packt
ISBN-13 9781801073240
Length 376 pages
Edition 1st Edition
Concepts
Arrow right icon
Author (1):
Arrow left icon
Ahsan Zafar Ahsan Zafar
Author Profile Icon Ahsan Zafar
Ahsan Zafar
Arrow right icon
View More author details
Toc

Table of Contents (14) Chapters Close

Preface 1. Section 1: Data Architecture and Data Management Essentials
2. Chapter 1:Data Architect Roles and Responsibilities FREE CHAPTER 3. Chapter 2: Understanding Salesforce Objects and Data Modeling 4. Chapter 3: Understanding Data Management 5. Section 2: Salesforce Data Governance and Master Data Management
6. Chapter 4: Making Sense of Master Data Management 7. Chapter 5: Implementing Data Governance 8. Chapter 6: Managing Performance 9. Section 3: Large Data Volumes (LDVs) and Data Migrations
10. Chapter 7: Working with Large Volumes of Data 11. Chapter 8: Best Practices for General Data Migration 12. Assessments 13. Other Books You May Enjoy

Questions

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

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at £16.99/month. Cancel anytime