Salesforce Certified Platform Data Architect (Plat-Arch-201)

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 archived 1. 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 demand 2. 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

The best object model to configure within SF for migrating individual customers (B2C) data from legacy systems is to leverage person account object in Salesforce. Person accounts are a special type of accounts that store information about individual people by combining certain account and contact fields into a single record 4. Person accounts are useful for B2C scenarios where there is no need to associate a company name with a contact. Person accounts also support standard Salesforce features and functionality, such as leads, campaigns, reports, dashboards, etc 5. Leverage custom person account object in SF is not a good option because there is no such thing as a custom person account object. Leverage custom account and contact object in SF is not a good option because it would require creating and maintaining additional objects and fields that may not be necessary or compatible with standard Salesforce features. Leverage standard account and contact object in SF is not a good option because it would require filling in dummy values for the account name field, which is mandatory for standard accounts.

Data integrity and data usability are two aspects of data that an Enterprise data governance program aims to improve. Data integrity refers to the accuracy, consistency, and validity of the data across the enterprise 2. Data usability refers to the ease of access, analysis, and interpretation of the data by the end users

Data skew occurs when a large number of child records are associated with a single parent record, or when a single user owns a large number of records. This can cause performance issues and lock contention. To avoid data skew, the data architect should limit assigning one user 10,000 records ownership, limit associating 10,000 opportunities to one account, and limit associating 10,000 records looking up to the same record

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.

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 data 1. 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.com 2.

To solve the issue of lack of governance in making changes to Salesforce, a data architect should recommend creating and managing a data dictionary and setting up a governance process for changes made to common objects. A data dictionary is a document that defines the metadata, structure, and relationship of each object and field in Salesforce. A governance process is a set of rules and procedures that govern how changes are proposed, reviewed, approved, and deployed in Salesforce. These measures will help NTO to maintain consistency, quality, and clarity of their data model and avoid confusion and errors among users.
Option A is incorrect because adding description fields to explain why the field is used, and marking the field as required will not prevent unauthorized or unnecessary changes to Salesforce.
Option C is incorrect because creating reports to identify which users are leaving blank, and using external data sources to augment the missing data will not address the root cause of the issue, which is the lack of governance in making changes to Salesforce.
Option D is incorrect because creating validation rules with error messages to explain why the fields are used will not stop users from seeing new fields on their page that they are unsure of.

Service Cloud License (option C) is the license type that UC users need to fulfill UC's requirements, as it allows them to track customer complaints, provide white papers on products, and provide subscription-based support. Sales Cloud License (option A) is mainly for managing sales processes and leads, Lightning Platform Starter License (option B) is for building custom apps and workflows, and Salesforce License (option D) is a generic term that does not specify a particular license type.

The number of joins used in report query and the number of records returned by report query are two key considerations to make sure the performance of the report is not degraded due to large data volume. The number of joins used in report query affects the complexity and execution time of the query, especially when joining multiple large objects 4. The number of records returned by report query affects the amount of data that needs to be processed and displayed by the report engine.

The best solution to make sure decrypted values are exported during data export is to create another field to copy data from encrypted field and use this field in export. This is because classic encryption does not support exporting decrypted values of encrypted fields. The view encrypted data permission only allows users to view decrypted values in the user interface, but not in reports or data exports. Therefore, a workaround is to create a formula field or a workflow field update that copies the value of the encrypted field to another field, and use that field for data export. However, this solution has some drawbacks, such as exposing sensitive data in plain text and consuming extra storage space. A better solution would be to use Shield Platform Encryption, which supports exporting decrypted values of encrypted fields with the Export Encrypted Data permission