Salesforce Certified Data Architect Practice Test - Questions Answers, Page 10

The recommended solution to address the requirements of Universal Containers (UC) is to roll-up discount request amount at the line-item-level and line-item-level summary discount at the opportunity level. This solution would allow UC to show all sums of discounts across line items at an opportunity level using standard roll-up summary fields. Since UC has a multi-level master-detail relationship for opportunities, a custom opportunity line item object, and a custom discount request object, they can use two levels of roll-up summary fields to aggregate the discount amounts from the child objects to the parent objects. For example, they can create a roll-up summary field on the custom line item object to sum up the discount request amounts from the custom discount request object. Then, they can create another roll-up summary field on the opportunity object to sum up the line-item-level summary discounts from the custom line item object.

The two best practices that should be followed when using SOSL for searching are: Keep searches specific and avoid wildcards where possible. Use Find in ''ALL FIELDS'' for faster searches. These best practices are helpful because they optimize the search performance and relevance. For example, keeping searches specific and avoiding wildcards where possible can reduce the number of results returned and improve the search accuracy. Using Find in ''ALL FIELDS'' for faster searches can leverage Salesforce's pre-defined indexes on common fields and return results more quickly than specifying individual fields.

Integrating with a third-party database or service for address validation and enrichment is a scalable strategy that can improve the quality of the Account addresses by comparing them with a reliable source of data1.Leveraging Data.com Clean to clean up Account address fields with the D&B database is another scalable strategy that can automatically update and enrich Account records with verified information from Data.com2.

Leveraging a ''tier''-based approach to classify the record storage need is a true statement with respect to a data archiving strategy for UC.This approach involves defining different tiers of data based on their usage, value, and retention policies, and then applying appropriate storage and archiving solutions for each tier.

Setting Customer-Reference_c as an External ID (unique) is the recommended solution to ensure that support agents using global search and reports can quickly find shipment records.This is because external ID fields are indexed and can be used as filters in reports and list views4. Making the field unique also ensures that there are no duplicate values that could confuse the search results.

Using leading % wildcards, performing large loads and deletions, and using NOT and != operators are three options that prevent a query from being selective.These options can cause the query to scan a large number of records or indexes, which can negatively impact the performance and scalability of the query5.Using a custom index on a deterministic formula field, on the other hand, can improve the query selectivity by allowing the query to use the index instead of scanning all the records6.

Creating a custom lookup field on the standard Product to reference the parent record in the hierarchy is the correct way to modify the standard Product object model to support a hierarchical data structure. This allows UC to create a self-relationship on the Product object and define parent-child relationships among products.

Exporting in multiple batches and using PK Chunking are two steps that can help correct the issues with exporting large volumes of Order records using Informatica Cloud Loader. Exporting in multiple batches can reduce the load on the system and avoid timeouts or errors. Using PK Chunking can split a large data set into smaller chunks based on the record IDs and enable parallel processing of each chunk.

Evaluating a third-party AppExchange app, such as OwnBackup or Spanning, etc., for backup and archival purposes is the best approach to address the requirement of having a one-day SLA for any data loss. These apps can provide automated backups, granular restores, and compliance features that can help UC recover from any data loss or corruption scenarios.