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

A correct technique UC should use to solve the data inconsistency is to define a data taxonomy for product data and apply the taxonomy to the product data in the data warehouse. A data taxonomy is a hierarchical classification of data entities and attributes that defines their meaning, format, and relationships. A data taxonomy can help ensure consistency, accuracy, and completeness of product data across different systems and channels

 Option C is the best answer because reviewing projected data storage needs is an important step in designing a field-level audit and recovery plan1. You need to estimate how much data storage you will need in the future and plan accordingly. Option A is not correct because reducing data storage by purging old data may not be sufficient or desirable for backup purposes. Option B is not correct because implementing an AppExchange package may not be customized or compatible with your org’s requirements. Option D is not correct because scheduling a weekly export file may not be frequent or granular enough for field-level audit and recovery.

Enabling field history tracking on the Case object is the first step to implement a reporting solution to measure the support reps case closure rates. Field history tracking allows you to track changes to certain fields on the Case object, such as Status, Owner, or Priority. You can then create reports based on the field history data to analyze how long it took to close a case, how many times the case owner changed, or how many cases were escalated.

  IP restrictions can be used to prevent users from accessing Salesforce from outside the company network or VPN. According to this article, sharing settings can be used to control access to customer information based on record ownership. According to this article, custom Apex can be used to support customer requests for removal of their information from Salesforce.

Cleaning data before importing to Salesforce and using Salesforce matching and duplicate rules are two design considerations that an architect should take to minimize data duplication when migrating legacy account data from two aging systems into Salesforce. Cleaning data before importing involves removing or correcting any inaccurate, incomplete, or inconsistent data from the source systems, as well as identifying and resolving any potential duplicates. This ensures that only high-quality and unique data is imported to Salesforce. Using Salesforce matching and duplicate rules allows the architect to define how Salesforce identifies duplicate records during import and how users can handle them. This prevents or reduces the creation of duplicate records in Salesforce and improves data quality. The other options are not effective or recommended for minimizing data duplication.

Running a report that shows the last time the key fields were updated can help Get Cloudy Consulting identify stale or outdated data and prioritize data cleansing activities. Running a report that shows the percentage of blanks for the important fields can help Get Cloudy Consulting measure the completeness of their data and identify gaps or missing value

According to the Using Mashups article on Salesforce Developers, one of the techniques for deploying large data volumes is to use mashups to display historical records in Salesforce. The article states that “Mashups are a way to display data from an external system within a Salesforce page without copying or synchronizing the data. Mashups use a combination of Visualforce, Apex callouts, and JavaScript code that runs in the browser. Mashups are useful when you want to display large amounts of read-only data that is stored outside of Salesforce.” Therefore, a data architect should recommend this solution to meet the business requirement of UC.

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.

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.

Using an AppExchange package for Data Quality is a good way to match Salesforce data against a trusted source, such as an MDM system. You can use tools like Cloudingo, DupeCatcher, or DemandTools to identify and merge duplicate records, standardize data formats, and enrich data with external sources