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

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.

 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.

Using external objects to maintain Sales Order in Salesforce is the best recommendation for maintaining Sales Orders in Salesforce, as it allows users to access large volumes of data stored outside Salesforce without copying or synchronizing it. Using custom objects, custom big objects, or standard order object may not be feasible or optimal for storing more than 150 million records that will not be updated in Salesforce.

The best license to provide these features to the franchisees is the Partner Community license. Partner Community licenses are designed for external users who collaborate with your sales team on deals, such as resellers, distributors, or brokers. Partner Community users can access standard CRM objects, such as accounts, contacts, leads, opportunities, campaigns, and reports. They can also access custom objects and run dashboards12. Salesforce Sales Cloud license is not a good option because it is intended for internal users who need full access to standard CRM and custom apps. Lightning Platform license is not a good option because it is intended for users who need access to custom apps but not to standard CRM functionality. Customer Community license is not a good option because it is intended for external users who need access to customer support features, such as cases and knowledge articles, but not to sales features

A data dictionary is a document that describes the structure, format, and meaning of data entities and attributes. A common technique to build a data dictionary is to use an entity relationship diagram (ERD), which shows the logical relationships between objects and fields in a graphical way. Another technique is to use the Salesforce Metadata API, which allows you to retrieve and deploy the metadata that defines your Salesforce org

Determining if any integration points create records in Salesforce, running key reports to determine what fields should be required, and reviewing the sharing model to determine impact on duplicate records are three areas of Salesforce that the architect should review before proposing any design recommendation. These areas will help to identify the sources and quality of data, the business rules and validations for data entry, and the access and visibility of data across users and roles. Reviewing the metadata xml files for redundant fields to consolidate, and exporting the setup audit trail to review what fields are being used are not necessary steps for optimizing a data stewardship engagement, as they are more related to metadata management and audit tracking.

According to the Salesforce documentation2, duplicate leads are leads that have the same or similar information as other leads in Salesforce. Duplicate leads can cause poor customer experience, higher costs, and inaccurate reporting. To mitigate the issues caused by duplicate leads, some of the recommended practices are:

Standardize lead information across all channels (option B). This means using consistent formats, values, and fields for capturing lead data from different sources, such as web forms, email campaigns, or third-party vendors. This can help reduce data quality issues and make it easier to identify and prevent duplicate leads.

Implement a third-party solution to clean and enrich lead data (option D). This means using an external service or tool that can validate, correct, update, and enhance lead data before or after importing it into Salesforce. This can help improve data quality and accuracy, and reduce duplicate leads.

Implement a de-duplication strategy to prevent duplicate leads (option E). This means using Salesforce features or custom solutions that can detect and block duplicate leads from being created or imported into Salesforce. For example, using Data.com Duplicate Management3, which allows defining matching rules and duplicate rules for leads and other objects.

Building a process to manually search and merge duplicates (option A) is not a good practice, as it can be time-consuming, error-prone, and inefficient. Building a custom solution to identify and merge duplicate leads (option C) is also not a good practice, as it can be complex, costly, and difficult to maintain. It is better to use existing Salesforce features or third-party solutions that can handle duplicate leads more effectively.

Having each system pull the record changes from Salesforce using change data capture (option D) is the correct solution for ensuring all systems using customer data are kept up to date, as it allows the systems to subscribe to real-time events from Salesforce and receive notifications when customer records are created, updated, deleted, or undeleted. Sending customer data nightly to the system of truth in a scheduled batch job (option A) or sending customer record changes from Salesforce to each system in a nightly batch job (option B) are not good solutions, as they may cause data latency and inconsistency, and they do not provide real-time updates. Sending customer record changes from Salesforce to the system of truth in real time (option C) is also not a good solution, as it does not address how the other systems will receive the updates from the system of truth.

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.

The three questions that should be considered when designing an appropriate archiving strategy are: If reporting is necessary, can the information be aggregated into fewer, summary records? Will the data being archived need to be reported on or accessed in any way in the future? Are there any regulatory restrictions that will influence the archiving and purging plans? These questions are important because they help determine the scope, frequency, and method of archiving and purging data from Salesforce. For example, if reporting is necessary, then summary records or analytics snapshots can be used to store aggregated data and reduce the number of records that need to be archived1. If the data being archived needs to be accessed in the future, then offsite storage or external objects can be used to retain the data and make it available on demand2. If there are any regulatory restrictions, such as GDPR or HIPAA, then the archiving and purging plans need to comply with them and ensure data security and privacy