Master Salesforce Data Architect Exam with Reliable Practice Questions

Correct : A

Creating customers as Contacts and relating them to Business and Residential Accounts using the Account Contact Relationships (option A) is the best option to recommend for a single view of these customers without creating multiple customer records, as it allows the data architect to model complex relationships between customers and accounts using native Salesforce features and tools. Creating customers as Person Accounts and relating them to Business and Residential Accounts using the Account Contact relationship (option B) is not a good option, as it may create data redundancy and inconsistency, and it does not leverage the existing Contact object. Creating customers as individual objects and relating them with Accounts for Business and Residence accounts (option C) is also not a good option, as it may require more customization and maintenance effort, and it does not leverage the existing Account and Contact objects. Creating customers as Accounts for Residence Account and using Parent Account to relate Business Account (option D) is also not a good option, as it may create confusion and complexity with the account hierarchy, and it does not leverage the existing Contact object.

Correct : B

Enabling granular locking (option B) is the best option to prevent the error, as it allows finer control over how records are locked during automated or manual processes, and reduces the chances of lock contention or deadlock. Reducing number of users updated concurrently (option A) is not a good option, as it may limit the productivity and efficiency of the system admins, and it does not address the root cause of the error. Analyzing Splunk query to spot offending records (option C) is also not a good option, as it may require more time and effort, and it does not provide a permanent solution for the error. Increasing CPU for the Salesforce org (option D) is also not a good option, as it may introduce additional cost and complexity, and it does not solve the root cause of the error.

Correct : A

According to the official Salesforce guide1, big objects are designed to store and manage massive data volumes within Salesforce without affecting performance. They can be queried by using Async SOQL or standard SOQL, and they can be accessed by using Apex, Visualforce, Lightning components, or APIs. Big objects are ideal for storing data that is used for analytics or reporting purposes, such as the reward program data. Option A is the correct answer because it allows NTO to create a custom big object in Salesforce that can store the reward program data and make it available for consumption by Einstein Analytics and Discovery. Option B is incorrect because Einstein cannot connect directly to the point of sales system to capture the reward program data. Option C is incorrect because Einstein Analytics does not support creating big objects. Option D is incorrect because custom objects are not suitable for storing large volumes of data.

Correct : B

: According to the official Salesforce guide1, assigning leads to a single dummy user can cause performance issues and data skew, especially if the dummy user owns more than 10,000 records. Data skew occurs when a single user or a small number of users own a disproportionately large number of records, which can affect query performance and sharing calculations. Option B is the correct answer because it suggests creating multiple dummy users and assigning leads to them, which can distribute the load and reduce data skew. Option A is incorrect because assigning the dummy user to the last role in the role hierarchy does not affect the performance or data skew issues. Option C is incorrect because assigning the dummy user to the highest role in the role hierarchy can worsen the performance and data skew issues, as it will grant access to more users and records. Option D is incorrect because periodically deleting leads can cause data loss and does not address the root cause of the problem.

Correct : D

According to the official Salesforce guide1, data classification metadata is a feature that allows administrators to classify data fields based on their sensitivity level, such as confidential, restricted, or general. Data classification metadata can be used to filter and identify sensitive data fields and apply appropriate security measures, such as encryption, masking, or auditing. Option D is the correct answer because it suggests using data classification metadata to provide ways to filter and identify sensitive data. Option A is incorrect because data grouping metadata is not a feature in Salesforce. Option B is incorrect because field-level security is a feature that controls the visibility and editability of fields based on user profiles or permission sets, but it does not provide ways to filter and identify sensitive data. Option C is incorrect because creating a custom checkbox denoting sensitive data is not a scalable or reliable solution, as it requires manual maintenance and does not enforce any security measures.