Salesforce DATA-ARCHITECT Online Practice Questions and Exam Preparation

Salesforce DATA-ARCHITECT Online Questions & Answers

• Question 201:

  UC is building a salesforce application to track contacts and their respective conferences that they have attended with the following requirements:

  1.Contacts will be stored in the standard contact object.

  2.Conferences will be stored in a custom conference_ c object.

  3.Each contact may attend multiple conferences and each conference may be related to multiple contacts.

  How should a data architect model the relationship between the contact and conference objects?

  A. Implement a Contact Conference junction object with master detail relationship to both contact and conference_c
  B. Create a master detail relationship field on the Contact object.
  C. Create a master detail relationship field on the Conference object.
  D. Create a lookup relationship field on contact object.
  A. Implement a Contact Conference junction object with master detail relationship to both contact and conference_c

  ---

  Explanation

  Implementing a Contact Conference junction object with master detail relationship to both contact and conference_c is the correct way to model the relationship between the contact and conference objects, as it allows a many-to-many relationship between them. This means that each contact can attend multiple conferences, and each conference can be related to multiple contacts. Creating a master detail relationship field on either the contact or the conference object would create a one-to-many relationship, which does not meet the requirements. Creating a lookup relationship field on contact object would also create a one-to-many relationship, and would not enforce referential integrity.

• Question 202:

  Universal Containers (UC) plans to implement consent management for its customers to be compliant with General Data Protection Regulation (GDPR). UC has the following requirements:

  UC uses Person Accounts and Contacts in Salesforce for its customers.

  Data Protection and Privacy is enabled in Salesforce.

  Consent should be maintained in both these objects.

  UC plans to verify the consent provided by customers before contacting them through email or phone.

  Which option should the data architect recommend to implement these requirements?

  A. Configure custom fields in Person Account and Contact to store consent provided by customers, and validate consent against the fields.
  B. Build Custom object to store consent information in Person Account and Contact, validate against this object before contacting customers.
  C. Use the Consent Management Feature to validate consent provide under the person Account and Contact that is provided by the customer.
  D. Delete contact information from customers who have declined consent to be contacted.
  C. Use the Consent Management Feature to validate consent provide under the person Account and Contact that is provided by the customer.

  ---

  Explanation

  Using the Consent Management Feature to validate consent provided under the person Account and Contact that is provided by the customer (option C) is the best option to implement these requirements, as it allows UC to store and manage consent preferences for Person Accounts and Contacts using native Salesforce features and tools. Configuring custom fields in Person Account and Contact to store consent provided by customers and validate consent against the fields (option A) or building Custom object to store consent information in Person Account and Contact and validate against this object before contacting customers (option B) are not good options, as they may require more customization and maintenance effort, and they do not leverage the existing Data Protection and Privacy feature. Deleting contact information from customers who have declined consent to be contacted (option D) is also not a good option, as it may cause data loss or compliance issues, and it does not allow UC to track or update consent preferences.

• Question 203:

  The data architect for UC has written a SOQL query that will return all records from the Task object that do not have a value in the WhatID field:

  Select id, description, Subject from Task where WhatId!= NULL

  When the data architect usages the query to select values for a process a time out error occurs.

  What does the data architect need to change to make this query more performant?

  A. Remove description from the requested field set.
  B. Change query to SOSL.
  C. Add limit 100 to the query.
  D. Change the where clause to filter by a deterministic defined value.
  D. Change the where clause to filter by a deterministic defined value.

  ---

  Explanation

  According to the Salesforce documentation, SOQL is a query language that allows querying data from Salesforce objects and fields. SOQL queries have various clauses and operators that can be used to filter and sort the results. However, some clauses and operators can affect the performance of SOQL queries by increasing the cost or complexity of executing them.

  To make this query more performant, a data architect should change the where clause to filter by a deterministic defined value (option D). This means using a filter condition that specifies a concrete value or range of values for a field, such as WhatId = `001xx000003DGg3' or WhatId IN (`001xx000003DGg3', `001xx000003DGg4'). This can improve the performance of the query by reducing the number of records that need to be scanned and returned. A deterministic defined value can also leverage an index on the field, which can speed up the query execution.

  Removing description from the requested field set (option A) is not a good solution, as it can affect the functionality or usability of the query. The description field may contain important or relevant information that is needed for the process.

  Changing the query to SOSL (option B) is also not a good solution, as SOSL is a different query language that allows searching text fields across multiple objects. SOSL queries have different syntax and limitations than SOQL queries, and may not return the same results or performance. Adding limit 100 to the query (option C) is also not a good solution, as it can affect the completeness or accuracy of the query. The limit clause specifies the maximum number of records that can be returned by the query, which may not include all the records that match the filter condition.

• Question 204:

  UC has the following system:

  Billing system.

  Customer support system.

  CRM system.

  US has been having trouble with business intelligence across the different systems.

  Recently US implemented a master data management (MDM) solution that will be the system of truth for the customer records.

  Which MDM data element is needed to allow reporting across these systems?

  A. Global unique customer number.
  B. Email address.
  C. Phone number.
  D. Full name.
  A. Global unique customer number.

  ---

  Explanation

  The correct answer is A, global unique customer number. A global unique customer number is a data element that can uniquely identify each customer across different systems. It can be used as a key to link customer records from different sources and enable reporting across these systems. Email address, phone number, and full name are not reliable or consistent identifiers for customers, as they can change over time or be shared by multiple customers.

• Question 205:

  A Salesforce customer has plenty of data storage. Sales Reps are complaining that searches are bringing back old records that aren't relevant any longer. Sales Managers need the data for their historical reporting.

  What strategy should a data architect use to ensure a better user experience for the Sales Reps?

  A. Create a Permission Set to hide old data from Sales Reps.
  B. Use Batch Apex to archive old data on a rolling nightly basis.
  C. Archive and purge old data from Salesforce on a monthly basis.
  D. Set data access to Private to hide old data from Sales Reps.
  C. Archive and purge old data from Salesforce on a monthly basis.

  ---

  Explanation

  Archiving and purging old data from Salesforce on a monthly basis is a good strategy to improve the user experience for the Sales Reps, as it will reduce the clutter and improve the search performance. Creating a permission set or setting data access to private are not effective ways to hide old data from Sales Reps, as they will still consume data storage and affect search results. Using Batch Apex to archive old data on a rolling nightly basis is also not a good option, as it will consume API requests and processing time, and may not comply with the data retention policy.

• Question 206:

  Universal Containers (UC) has a Salesforce instance with over 10.000 Account records. They have noticed similar, but not identical. Account names and addresses.

  What should UC do to ensure proper data quality?

  A. Use a service to standardize Account addresses, then use a 3rd -party tool to merge Accounts based on rules.
  B. Run a report, find Accounts whose name starts with the same five characters, then merge those Accounts.
  C. Enable Account de -duplication by creating matching rules in Salesforce, which will mass merge duplicate Accounts.
  D. Make the Account Owner clean their Accounts' addresses, then merge Accounts with the same address.
  C. Enable Account de -duplication by creating matching rules in Salesforce, which will mass merge duplicate Accounts.

  ---

  Explanation

  Enabling Account de-duplication by creating matching rules in Salesforce, which will mass merge duplicate Accounts, is what UC should do to ensure proper data quality for their Account records. Matching rules allow UC to define how Salesforce identifies duplicate Accounts based on various criteria, such as name, address, phone number, etc. Mass merge allows UC to merge up to 200 duplicate Accounts at a time, based on the matching rules. This simplifies and automates the process of de-duplicating Accounts and improves data quality. The other options are either more time-consuming, costly, or error-prone for ensuring proper data quality.

• Question 207:

  Universal Containers (UC) is migrating from an on-premise homegrown customer relationship management (CRM) system- During analysis, UC users highlight a pain point that there are multiple versions of many customers.

  What should the data architect do for a successful migration to mitigate the pain point?

  A. Hire an intern manually de-duplicate the records after migrating to Salesforce.
  B. Migrate the data as is, and use Salesforce's de-duplicating feature.
  C. Have the users manually clean the data in the old system prior to migration.
  D. Store the data in a staging database, and de-duplicate identical records.
  D. Store the data in a staging database, and de-duplicate identical records.

  ---

  Explanation

  Storing the data in a staging database and de-duplicating identical records (option D) is the best solution for a successful migration to mitigate the pain point, as it allows the data architect to identify and merge duplicate customers before they are imported into Salesforce. Hiring an intern manually de-duplicate the records after migrating to Salesforce (option A) is not a good solution, as it may be time-consuming and error- prone, and it does not prevent duplicate records from being created in Salesforce. Migrating the data as is and using Salesforce's de-duplicating feature (option B) is also not a good solution, as it may cause data quality issues and conflicts, and it does not address the root cause of the duplication.

  Having the users manually clean the data in the old system prior to migration (option C) is also not a good solution, as it may be unrealistic and impractical, and it does not leverage any automated tools or processes.

• Question 208:

  Universal Containers (UC) is facing data quality issues where Sales Reps are creating duplicate customer accounts, contacts, and leads. UC wants to fix this issue immediately by prompting users about a record that possibly exists in Salesforce. UC wants a report regarding duplicate records.

  What would be the recommended approach to help UC start immediately?

  A. Create an after insert and update trigger on the account, contact and lead, and send an error if a duplicate is found using a custom matching criteria.
  B. Create a duplicate rule for account, lead, and contact, use standard matching rules for these objects, and set the action to report and alert for both creates and edits.
  C. Create a duplicate rule for account, lead, and contact, use standard matching rules for these objects, and set the action to block for both creates and edits.
  D. Create a before insert and update trigger on account, contact, and lead, and send an error if a duplicate is found using a custom matching criteria.
  B. Create a duplicate rule for account, lead, and contact, use standard matching rules for these objects, and set the action to report and alert for both creates and edits.

  ---

  Explanation

  Creating a duplicate rule for account, lead, and contact, using standard matching rules for these objects, and setting the action to report and alert for both creates and edits can help UC fix the issue immediately by prompting users about a record that possibly exists in Salesforce. This can also generate a report regarding duplicate records that can be used for further analysis and resolution

• Question 209:

  Northern Trail outfitters in migrating to salesforce from a legacy CRM system that identifies the agent relationships in a look-up table.

  What should the data architect do in order to migrate the data to Salesfoce?

  A. Create custom objects to store agent relationships.
  B. Migrate to Salesforce without a record owner.
  C. Assign record owner based on relationship.
  D. Migrate the data and assign to a non-person system user.
  A. Create custom objects to store agent relationships.

  ---

  Explanation

  The correct answer is A. To migrate the data to Salesforce, the data architect should create custom objects to store agent relationships. This will allow the data architect to replicate the look-up table structure from the legacy CRM system and maintain the relationship data in Salesforce. Option B is incorrect because migrating to Salesforce without a record owner will cause errors and prevent the data from being imported. Option C is incorrect because assigning record owner based on relationship will not preserve the agent relationships from the legacy CRM system. Option D is incorrect because migrating the data and assigning to a non-person system user will not allow the users to access and modify the data.

• Question 210:

  UC is planning a massive SF implementation with large volumes of data. As part of the org's implementation, several roles, territories, groups, and sharing rules have been configured. The data architect has been tasked with loading all of the required data, including user data, in a timely manner.

  What should a data architect do to minimize data load times due to system calculations?

  A. Enable defer sharing calculations, and suspend sharing rule calculations
  B. Load the data through data loader, and turn on parallel processing.
  C. Leverage the Bulk API and concurrent processing with multiple batches
  D. Enable granular locking to avoid "UNABLE _TO_LOCK_ROW" error.
  A. Enable defer sharing calculations, and suspend sharing rule calculations

  ---

  Explanation

  The correct answer is A, enable defer sharing calculations, and suspend sharing rule calculations. Defer sharing calculations and suspend sharing rule calculations are features that allow you to temporarily disable the automatic recalculation of sharing rules when you load large volumes of data. This can improve the performance and speed of your data load process by avoiding unnecessary system calculations. Loading the data through data loader, leveraging the bulk API, or enabling granular locking are also options that can help with data load times, but they do not directly address the system calculations issue.