Pass the Salesforce Application Architect Data-Architect Questions and answers with ValidTests

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.

Importing Account records first followed by order records after sorting orders by AccountID is the recommended way to avoid locking issues during import. This can reduce the number of lock contention errors by minimizing the number of parent records that are concurrently processed by multiple batches. Sorting orders by AccountID can also group the child records by their parent records and avoid updating the same parent record in different batches3. Importing Account records first followed by order records after sorting order by OrderID will not help with avoiding locking issues because it does not group the child records by their parent records. Changing the relationship to Lookup and updating the relationship to master-detail after import will not work because changing a relationship from Lookup to master-detail requires that all child records have a parent record, which may not be the case after import. Importing Order records and Account records separately and populating AccountID in orders using batch Apex will not help with avoiding locking issues because it still requires updating the parent records in batches.

The correct answer is C, implement shield platform encryption to encrypt standard and custom fields. Shield platform encryption is a feature that allows you to encrypt sensitive data at rest in Salesforce without affecting its functionality. You can encrypt both standard and custom fields using shield platform encryption. Using Apex Crypto Class, implementing classic encryption, or exporting data out of Salesforce are not recommended solutions, as they will either limit your functionality, require custom code, or compromise your data security.

According to this article, person accounts are designed to store information about individual people by combining certain account and contact fields into a single record. This is suitable for a large B2C retailer that needs to model the consumer account structure in Salesforce.

 Using a third-party data source to update contact information in Salesforce is the best solution to reduce the amount of returned mails. This way, the data architect can ensure that the contact information is accurate and up-to-date without relying on manual verification or deletion of contacts

 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

According to the What is Master Data Management (MDM)? article, some of the data challenges that an MDM tool can solve are data duplication, data accuracy and quality, and data standardization. The article states that “MDM solutions comprise a broad range of data cleansing, transformation, and integration practices. As data sources are added to the system, MDM initiates processes to identify, collect, transform, and repair data. Once the data meets the quality thresholds, schemas and taxonomies are created to help maintain a high-quality master reference.” Therefore, an MDM tool can help NTO eliminate data duplication across different systems, improve data accuracy and quality by removing errors and inconsistencies, and standardize data formats and definitions for better integration and analysis.

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.

Einstein Analytics can provide more analytical insights than native reports and dashboards by allowing users to explore data from multiple sources, create interactive visualizations, and apply AI-powered features5. AppExchange Apps can also provide more analytical insights by offering pre-built solutions or integrations with external tools that can enhance the reporting and analytics capabilities of Salesforce6.

The data architect should recommend using AppExchange package for backup and restore. AppExchange is a marketplace for Salesforce apps and solutions that can be installed and configured in Salesforce orgs. There are several AppExchange packages that provide backup and restore functionality for Salesforce data, such as OwnBackup, Odaseva, or Spanning. These packages can perform daily backups of Salesforce data to a secure cloud storage, and provide restore capability to avoid any data loss in case of outage. Option B is incorrect because using ETL (Extract, Transform, Load) for backup and restore from EDW (Enterprise Data Warehouse) will require additional development effort and may not be reliable or secure. Option C is incorrect because using Bulk API to extract data on daily basis to EDW and REST API for restore will require additional integration effort and may not be scalable or performant. Option D is incorrect because changing weekly backup process to daily backup, and implementing a custom restore solution will require additional configuration effort and may not be robust or compliant.