Universal Containers (UC) currently has Sales Cloud, Revenue Cloud, and Marketing Cloud Account
Engagement within its existing Salesforce environment and is utilizing a standard Lead to Cash solution across those clouds. UC is 2 years into its Salesforce implementation, and the CIO is getting concerned with the sheer amount of data affecting its environment's data limits. IT is doing upkeep on older records that may no longer be relevant. They have decided to start looking at data archival strategies and what to archive correctly. Given that this solution involves Leads from Marketing Cloud Account Engagement, Opportunities from Sales Cloud, and Quotes from Revenue Cloud, they are concerned about archiving related data on active sales pipelines. They also want to keep a historical snapshot of all of their Quotes, Opportunities, and Leads for future pipeline performance purposes and are open to options.
Choose 2 answers
- Propose Skinny Tables to the CIO before doing anything else.
- Understand the organization's regulatory requirements around right to retain or delete data.
- Recommend AppExchange solutions that provide capabilities around data archiving to the CIO.
- Segment the data in terms of data needed for daily operations, data that is used occasionally at demand, and data that is used purely for historical purposes.
Answer(s): B,D
Explanation:
Before proposing any solutions to the CIO, it is important to understand the organization's regulatory requirements around right to retain or delete data. It is also important to segment the data into different categories based on the purpose of the data, such as data needed for daily operations, data that is used occasionally at demand, and data that is used purely for historical purposes. This will help the organization plan their data archival strategy more effectively. Additionally, the CIO can look into AppExchange solutions that provide capabilities around data archiving.
Option B is important because different industries and regions may have different laws and regulations regarding how long they need to keep certain types of data or when they need to delete them. For example, some financial records may need to be retained for a minimum of seven years, while some personal data may need to be deleted upon request.
Understanding these requirements can help UC decide what data can be archived and what data must be kept in Salesforce.
Option D is helpful because it can help UC prioritize and categorize their data based on how frequently and urgently they need to access it. For example, data that is needed for daily operations should be kept in Salesforce for optimal performance and availability, while data that is used occasionally at demand can be archived in an external system and accessed via Salesforce Connect.
Data that is used purely for historical purposes can be backed up in a secure storage system and deleted from Salesforce.