Salesforce Certified Platform Data Architect Practice Questions

Salesforce Certified Platform Data Architect exam preparation

Salesforce Certified Platform Data Architect practice questions in English: 177 questions with explanations. The mock exam has 60 questions and 105 minutes.

Salesforce Certified Platform Data Architect free question 8 / 10 · Domain 5: Large Data Volume Considerations

An org with customers around the world has tens of millions of accounts. The customers fall into the Americas, Europe, and Asia, with few relationships across regions. To reduce the number of records that queries and reports return, you want to split the data with divisions. Which approach matches the large data volume best practices?

  1. Contact Salesforce Customer Support to enable the special support for partitioning data by divisions
  2. An administrator defines the regions in Setup, and from that day on queries return fewer records
  3. Divisions control who can see data like sharing, so use sharing rules instead if the goal is fewer records
  4. Divisions suit data with many links between regions, so link the regions through the account hierarchy
Show the answer and explanation

Answer: A

Why this is correct
The large data volume best practices describe divisions as a means of partitioning the data of large deployments to reduce the number of records returned by queries and reports. Their example is a deployment with many customers that creates divisions such as US, EMEA, and APAC and groups customers into smaller sets that are unlikely to have relationships with each other. It adds that Salesforce provides special support for partitioning data by divisions, which you can enable by contacting Salesforce Customer Support.

Why the other options are wrong
"Divisions control who can see data like sharing, so use sharing rules instead if the goal is fewer records" … The guide describes divisions as a means of partitioning data to reduce the number of records that queries and reports return. It does not describe them as a way of controlling who sees data.
"Divisions suit data with many links between regions, so link the regions through the account hierarchy" … The guide's example groups customers into smaller sets that are unlikely to have relationships with each other, such as US, EMEA, and APAC. It is not an example of splitting data that has many relationships.
"An administrator defines the regions in Setup, and from that day on queries return fewer records" … The guide says the special support for partitioning data by divisions is enabled by contacting Salesforce Customer Support. It does not describe starting with a Setup step alone.

Where people trip
Divisions work when the groups have few relationships with each other. If data is linked across regions all the time, a query still reads several groups and the number of records does not drop.

Go to the Salesforce Certified Platform Data Architect practice app (10 free questions; purchase unlocks all questions)

See the full practice set