Q: 8
Cloud Kicks (CK) acquired a shoe distribution partner. The marketing and sales directors want to
migrate the existing sales and marketing data into CK's Sales Cloud instance.
Which aspect should the consultant consider first before proceeding with the data migration?
Options
Discussion
C . B distracts but you have to know what and how much data before setting up access.
C . B is tempting but if you don't first know how much data and what kind, can't plan anything else. Scoping the data volume is key before worrying about sharing rules.
C . You have to figure out what and how much data you're actually moving before worrying about roles or licenses. B trips people up, but access controls don't matter until you know what needs controlling. Seen similar in practice questions-identify the data scope first, every time.
Maybe B. Role hierarchy and sharing usually comes up early in migration planning since permissions can break if they're not set, so I think that's important before moving data.
Option B similar question seen in a practice exam.
C , unless you know how much and what kind of data is moving over, you can’t even size the project or prep the tools needed. B matters later but always start by identifying scope. Anyone see a weird edge case with custom objects?
C. that's what I'd pick. You need to know how much and what type of data before any real planning or technical steps. Without that, can't predict effort, tool choice, or risks. Pretty sure that's what Salesforce wants here.
Option C but I get why B is tempting. You really need to know the data size before anything else.
I’d say B for role hierarchy, since data access can get messy if you don't map out sharing before bringing in new records.
C , figuring out the data volume is key before anything else. Can't really plan the migration process or estimate effort without knowing what you're dealing with. Role hierarchy stuff is important but comes after.
Be respectful. No spam.
