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

To recommend a clean migration, the data architect should set up a staging database, and define external IDs to merge, clean duplicate data, and load into Salesforce. This will allow the data architect to consolidate and deduplicate the data from two legacy systems before importing it into Salesforce using external IDs as unique identifiers. Option A is incorrect because defining external IDs for an object, migrating second database to first database, and loading into Salesforce will not ensure that the data is clean and duplicate-free. Option B is incorrect because defining duplicate rules in Salesforce, and loading data into Salesforce from both databases will not prevent the duplicate data from being imported into Salesforce. Option D is incorrect because defining external IDs for an object, inserting data from one database, and using upsert for a second database will not handle the duplicate data from both databases.

The data architect should recommend Lighting platform plus license type for the finance team that best meets the requirements. This license type allows users to access custom objects and run reports and dashboards on them, without accessing any sales objects. Option A is incorrect because Service Cloud license type is more suitable for customer service users who need to access cases, knowledge, and other service objects. Option B is incorrect because Sales Cloud license type is more suitable for sales users who need to access accounts, contacts, opportunities, and other sales objects. Option C is incorrect because Light Platform Start license type does not allow users to run reports and dashboards on custom objects.

The data architect should recommend using field metadata attributes for compliance categorization, data owner, and data sensitivity level. This will allow the SF admins to generate reports to manage compliance based on the field metadata attributes that are defined for each data element in SF. Option A is incorrect because using metadata API to extract field attribute information and use the extract to classify and build reports will require additional development effort and may not be up-to-date with the latest changes in SF. Option C is incorrect because creating a custom object and field to capture necessary compliance information and build custom reports will require additional configuration effort and may not be consistent with the actual data elements in SF. Option D is incorrect because building reports for field information, then exporting the information to classify and report for audits will require additional manual effort and may not be accurate or timely.

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.

To provide the sales team with the required functionality, a data architect should use a mashup page that will present the billing system records within Salesforce. A mashup page is a web page that combines data from multiple sources into a single integrated view. A mashup page can be created using Visualforce or Lightning Web Components, and can use Salesforce Connect or custom integrations to access external data from the on-premise web-based billing and invoice system. This will allow the sales team to pull a customer record and view their account status, invoice history, and opportunities without navigating outside of Salesforce. Option A is incorrect because creating a custom object and migrating the last 12 months of invoice data into Salesforce so it can be displayed on the account layout will consume a lot of storage space and may not reflect the latest data from the billing system. Option B is incorrect because writing an Apex callout and populating a related list to display on the account record will require additional development effort and may not be scalable or performant for large volumes of data. Option D is incorrect because creating a visual force tab with the billing system encapsulated within an iframe will not allow the sales team to view the billing system records within the customer record, but rather in a separate tab.

To help uniquely identify customer across multiple systems, a data architect should recommend creating a custom field as external ID to maintain the customer ID from the MDM solution. An external ID is a custom field that has the ''External ID'' attribute enabled, which means that it contains unique record identifiers from a system outside of Salesforce. By using the customer ID from the MDM solution as an external ID in Salesforce CRM, Contract Management system, and Marketing solution, the data architect can ensure that each customer can be easily identified and integrated across these systems. Option A is incorrect because storing the Salesforce ID in all the solutions to identify the customer will not work if the customer records are created or updated in other systems besides Salesforce CRM. Option B is incorrect because creating a custom object that will serve as a cross reference for the customer ID will require additional configuration effort and may not be consistent with the actual customer records in each system. Option C is incorrect because creating a customer database and using this ID in all systems will require additional infrastructure cost and maintenance effort.

To build a custom big object to support storing more than 100 million records in Salesforce, a data architect should use Metadata API or Big Object in setup. Metadata API is an API that allows developers to create, retrieve, update, or delete metadata components in Salesforce programmatically. Big Object in setup is a user interface that allows admins to create big objects declaratively without writing code. Both tools can be used to define custom big objects and their fields, indexes, and relationships in Salesforce. Option A is incorrect because DX (Developer Experience) is a set of tools that allows developers to create and manage applications on Salesforce Platform, but it does not support creating big objects directly. Option D is incorrect because Object Manager in setup is a user interface that allows admins to create and manage standard and custom objects in Salesforce, but it does not support creating big objects declaratively.

To improve the dashboard performance, the data architect should use selective queries to reduce the amount of data being returned, de-normalize the data by reducing the number of joins, and reduce the amount of data queried by archiving unused opportunity records. These options will help optimize the query performance, reduce the query complexity, and free up storage space. Option C is incorrect because removing widgets from the dashboard to reduce the number of graphics loaded will not affect the dashboard performance significantly, and may reduce the usability and functionality of the dashboard. Option D is incorrect because running the dashboard for CEO and sending it via email will not improve the dashboard performance, but rather shift the burden to another user.

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.