Explain the Use Cases and Considerations for Data Migration in Sales Cloud. AGENTFORCE-SALES-CONSULTANT Practice Questions (Page 1)

Questions 1–5

1. 1expert · hard

   A company is migrating from a legacy CRM to Sales Cloud. They have a large number of records with parent-child relationships, such as accounts with multiple contacts and opportunities. The migration team is concerned about maintaining these relationships. What is the most important consideration?

   • AUse a third-party tool that automatically handles relationships without any configuration.
   • BMigrate child records first, then parent records, and use a lookup field to link them.
   • CMigrate parent records first, then child records, using the Salesforce record IDs.
   • DEnsure that external IDs are used to maintain relationships between parent and child records during the migration.
   Reveal Solution Discussion Select an answer first
2. 2application · medium

   A company is migrating from a legacy CRM to Sales Cloud. They have a large volume of historical data, but the sales team only needs the last two years of data for active use. The company wants to keep the older data for compliance purposes. What should the migration plan include?

   • AMigrate the last two years of data to Sales Cloud and archive the older data in a separate system or data warehouse.
   • BMigrate all historical data to Sales Cloud to ensure nothing is lost.
   • CDelete the older data because it is not needed for daily operations.
   • DMigrate only the older data and leave the recent data in the legacy system.
   Reveal Solution Discussion Select an answer first
4. 3application · medium

   A company is implementing Sales Cloud for the first time and needs to migrate historical opportunity data from spreadsheets. The data includes closed won, closed lost, and open opportunities. The sales manager wants to ensure that the historical data is available for reporting but does not want to clutter the sales team's active pipeline. What should the migration plan include?

   • AMigrate only closed opportunities and start the open opportunities from scratch in Sales Cloud.
   • BMigrate all opportunities but change closed opportunities to a custom status that does not appear in reports.
   • CMigrate only open opportunities and store closed opportunities in an external data warehouse for reporting.
   • DMigrate all opportunities with their original statuses and use filters in reports to exclude closed opportunities from the pipeline view.
   Reveal Solution Discussion Select an answer first
5. 4application · medium

   A sales operations team is planning a data migration to Sales Cloud. They have a tight deadline and need to minimize downtime for the sales team. Which approach is most effective?

   • APerform a big-bang migration, moving all data at once to complete the process quickly.
   • BMigrate data only after business hours to avoid any impact on the sales team.
   • CUse a test environment to validate the migration, but do not perform a full validation in production.
   • DPerform a phased migration, moving data in batches and validating each batch before moving to the next.
   Reveal Solution Discussion Select an answer first
6. 5application · medium

   A company is migrating from a legacy CRM to Sales Cloud. The legacy system has a field for 'Lead Source' that contains values like 'Web', 'Referral', and 'Trade Show'. In Sales Cloud, the picklist values are 'Website', 'Referral', and 'Event'. What is the best way to handle this discrepancy during migration?

   • AMap the legacy values to the Sales Cloud picklist values using a data transformation during the migration.
   • BAdd the legacy values as additional picklist values in Sales Cloud.
   • CUse a free-text field instead of a picklist to store the legacy values.
   • DLeave the field blank for records that do not match the Sales Cloud picklist.
   Reveal Solution Discussion Select an answer first