Salesforce Salesforce Certifications DATA-ARCHITECT Questions & Answers

• Question 81:

  Every year, Ursa Major Solar has more than 1 million orders. Each order contains an average of 10 line items. The Chief Executive Officer (CEO) needs the Sales Reps to see how much money each customer generates year-over-year. However, data storage is running low in Salesforce.

  Which approach for data archiving is appropriate for this scenario?

  A. 1. Annually export and delete order line items. 2. Store them in a zip file in case the data is needed later.

  B. 1. Annually aggregate order amount data to store in a custom object. 2. Delete those orders and order line items.

  C. 1. Annually export and delete orders and order line items. 2. Store them in a zip file in case the data is needed later.

  D. 1. Annually delete orders and order line items. 2. Ensure the customer has order information in another system.

  Correct Answer: B

  Explanation: Option B is the most appropriate approach for data archiving in this scenario1. By aggregating order amount data at a summary level and storing it in a custom object, you can reduce data storage and still provide visibility to the Sales Reps on how much money each customer generates year-over-year. Option A is not correct because storing data in a zip file does not make it available in Salesforce. Option C is not correct because exporting and deleting orders and order line items may lose important details that are needed for analysis or reporting. Option D is not correct because deleting orders and order line items without exporting them may cause data loss or inconsistency if the customer does not have order information in another system.

• Question 82:

  Universal Container (UC) has around 200,000 Customers (stored in Account object). They get 1 or 2 Orders every month from each Customer. Orders are stored in a custom object called "Order c"; this has about 50 fields. UC is expecting a growth of 10% year -over -year. What are two considerations an architect should consider to improve the performance of SOQL queries that retrieve data from the Order _c object? Choose 2 answers

  A. Use SOQL queries without WHERE conditions.

  B. Work with Salesforce Support to enable Skinny Tables.

  C. Reduce the number of triggers on Order _c object.

  D. Make the queries more selective using indexed fields.

  Correct Answer: BD

  Explanation: To improve the performance of SOQL queries that retrieve data from the Order_c object, the data architect should work with Salesforce Support to enable Skinny Tables and make the queries more selective using indexed fields. Skinny Tables are custom tables that contain frequently used fields and are kept in sync with the base tables3. They can improve performance by reducing the number of table joins and using indexes. Making the queries more selective using indexed fields can also improve performance by reducing the query execution time and avoiding query timeouts4. The other options are not effective or recommended for improving SOQL performance.

• Question 83:

  UC has a requirement to migrate 100 million order records from a legacy ERP application into the salesforce platform. UC does not have any requirements around reporting on the migrated data.

  What should a data architect recommend to reduce the performance degradation of the platform?

  A. Create a custom object to store the data.

  B. Use a standard big object defined by salesforce.

  C. Use the standard "Order" object to store the data.

  D. Implement a custom big object to store the data.

  Correct Answer: D

  Explanation: Implementing a custom big object to store the data is the best recommendation to reduce the performance degradation of the platform, as it allows storing large volumes of data that do not need real-time access or reporting. Custom big objects can be defined using metadata API or developer console, and support up to 1 billion records per object. Creating a custom object or using the standard order object would consume a lot of storage space and impact the performance of queries and reports. Using a standard big object defined by salesforce would not be applicable for order records, as standard big objects are predefined for specific use cases such as audit trails or field history.

• Question 84:

  NTO has a loyalty program to reward repeat customers. The following conditions exists:

  1.Reward levels are earned based on the amount spent during the previous 12 months.

  2.The program will track every item a customer has bought and grant them points for discount.

  3.The program generates 100 million records each month.

  NTO customer support would like to see a summary of a customer's recent transaction and reward level(s) they have attained.

  Which solution should the data architect use to provide the information within the salesforce for the customer support agents?

  A. Create a custom object in salesforce to capture and store all reward program. Populate nightly from the point-of-scale system, and present on the customer record.

  B. Capture the reward program data in an external data store and present the 12 months trailing summary in salesforce using salesforce connect and then external object.

  C. Provide a button so that the agent can quickly open the point of sales system displaying the customer history.

  D. Create a custom big object to capture the reward program data and display it on the contact record and update nightly from the point-of-scale system.

  Correct Answer: D

  Explanation: According to the Get Started with Big Objects unit on Trailhead, one of the use cases for custom big objects is to store and manage loyalty program data for customers. The unit states that "From loyalty programs to transactions, order, and billing information, use a custom big object to keep track of every detail." Therefore, a custom big object can be used to capture the reward program data and display it on the contact record. Additionally, according to the Big Objects Implementation Guide, big objects can handle massive amounts of data (up to billions of records) and can be updated nightly from external systems using Bulk API or batch Apex. Therefore, a custom big object can meet the requirements of NTO's loyalty program scenario.

• Question 85:

  Universal Containers (UC) has a custom discount request object set as a detail object with a custom product object as the master. There is a requirement to allow the creation of generic discount requests without the custom product object as its master record. What solution should an Architect recommend to UC?

  A. Mandate the selection of a custom product for each discount request.

  B. Create a placeholder product record for the generic discount request.

  C. Remove the master-detail relationship and keep the objects separate.

  D. Change the master-detail relationship to a lookup relationship.

  Correct Answer: D

  Explanation: Changing the master-detail relationship to a lookup relationship is the best solution for allowing the creation of generic discount requests without the custom product object as its master record. A lookup relationship allows you to create child records without requiring a parent record. It also gives you more flexibility in defining the sharing and security settings for each object

• Question 86:

  Developers at Universal Containers need to build a report for the business which displays Accounts opened in the past year grouped by industry. This report will also include information from contacts, opportunities, and orders. There are several million Accounts in the system. Which two options should be recommended to make this report perform well and satisfy the business need?

  A. Use triggers to populate denormalized related fields on the Account.

  B. Use an indexed data field with bounded data filters.

  C. Use Formula fields to surface information I related entities on the report.

  D. Use unbounded date ranges to filter the report.

  Correct Answer: BC

  Explanation: Using an indexed data field with bounded data filters can improve the report performance by making the query more selective and reducing the number of records to scan. Using formula fields to surface information from related entities on the report can also enhance the report performance by avoiding joins and complex calculations

• Question 87:

  Universal Containers (UC) has a very large and complex Salesforce org with hundreds of validation rules and triggers. The triggers are responsible for system updates and data manipulation as records are created or updates by users. A majority of the automation tool within UC'' org were not designed to run during a data load. UC is importing 100,000 records into Salesforce across several objects over the weekend.

  What should a data architect do to mitigate any unwanted results during the import?

  A. Ensure validation rules, triggers and other automation tools are disabled.

  B. Ensure duplication and matching rules and defined.

  C. Import the data in smaller batches over a 24-hour period.

  D. Bulkily the trigger to handle import leads.

  Correct Answer: A

  Explanation: Ensuring validation rules, triggers and other automation tools are disabled is the best way to mitigate any unwanted results during the import, as it prevents any errors or conflicts that may occur due to the existing logic. Ensuring duplication and matching rules are defined may not be sufficient or relevant for preventing unwanted results. Importing the data in smaller batches over a 24-hour period may not be necessary or efficient. Bulkifying the trigger to handle import leads may not be possible or desirable if the triggers were not designed to run during a data load.

• Question 88:

  NTO has implemented salesforce for its sales users. The opportunity management in salesforce is implemented as follows:

  1.Sales users enter their opportunities in salesforce for forecasting and reporting purposes.

  2.NTO has a product pricing system (PPS) that is used to update opportunity amount field on opportunities on a daily basis.

  3.PPS is the trusted source within the NTO for opportunity amount.

  4.NTO uses opportunity forecast for its sales planning and management.

  Sales users have noticed that their updates to the opportunity amount field are overwritten when PPS updates their opportunities.

  How should a data architect address this overriding issue?

  A. Create a custom field for opportunity amount that sales users update separating the fields that PPS updates.

  B. Create a custom field for opportunity amount that PPS updates separating the field that sales user updates.

  C. Change opportunity amount field access to read only for sales users using field level security.

  D. Change PPS integration to update only opportunity amount fields when values is NULL.

  Correct Answer: C

  Explanation: Changing the opportunity amount field access to read only for sales users using field level security is the best way to address the overriding issue. This way, the sales users can still view the opportunity amount field but cannot edit it, and PPS can update it as the trusted source

• Question 89:

  Universal Containers (UC) is in the process of migrating legacy inventory data from an enterprise resources planning (ERP) system into Sales Cloud with the following requirements: Legacy inventory data will be stored in a custom child object called Inventory_c.

  Inventory data should be related to the standard Account object.

  The Inventory object should Invent the same sharing rules as the Account object.

  Anytime an Account record is deleted in Salesforce, the related Inventory_c record(s) should be deleted as well.

  What type of relationship field should a data architect recommend in this scenario?

  A. Master-detail relationship filed on Account, related to Inventory_c

  B. Master-detail relationship filed on Inventory_c, related to Account

  C. Indirect lookup relationship field on Account, related to Inventory_c

  D. Lookup relationship fields on Inventory related to Account

  Correct Answer: B

  Explanation: According to the Salesforce documentation, a relationship field is a field that allows linking one object to another object in Salesforce. There are different types of relationship fields that have different characteristics and behaviors,

  such as master-detail, lookup, indirect lookup, external lookup, etc.

  To recommend a type of relationship field for this scenario, where legacy inventory data will be stored in a custom child object called Inventory__c, inventory data should be related to the standard Account object, the Inventory__c object

  should inherit the same sharing rules as the Account object, and anytime an Account record is deleted in Salesforce, the related Inventory__c record(s) should be deleted as well, a data architect should recommend:

  Master-detail relationship field on Inventory__c, related to Account (option B). This means creating a field on the Inventory__c object that references the Account object as its parent. A master-detail relationship field establishes a parent-child

  relationship between two objects, where the parent object controls certain behaviors of the child object. For example, a master-detail relationship field can:

  Master-detail relationship field on Account, related to Inventory__c (option A) is not a good solution, as it reverses the direction of the relationship. This means creating a field on the Account object that references the Inventory__c object as its

  parent. This is not possible, as a standard object cannot be on the detail side of a master-detail relationship. Indirect lookup relationship field on Account, related to Inventory__c (option C) is also not a good solution, as it is a special type of

  relationship field that allows linking a custom object to a standard object on an external system using an indirect reference. This is not applicable for this scenario, as both objects are in Salesforce and do not need an external reference.

  Lookup relationship field on Inventory__c related to Account (option D) is also not a good solution, as it establishes a looser relationship between two objects than a master-detail relationship. A lookup relationship field does not inherit sharing

  and security settings from the parent object to the child object, does not cascade delete from the parent object to the child object, and does not roll up summary fields from the child object to the parent object.

• Question 90:

  Universal Containers (UC) has lead assignment rules to assign leads to owners. Leads not routed by assignment rules are assigned to a dummy user. Sales rep are complaining of high load times and issues with accessing leads assigned to the dummy user.

  What should a data architect recommend to solve these performance issues?

  A. Assign dummy user last role in role hierarchy

  B. Create multiple dummy user and assign leads to them

  C. Assign dummy user to highest role in role hierarchy

  D. Periodically delete leads to reduce number of leads

  Correct Answer: B

  Explanation: 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.