Free Salesforce Data-Architect Practice Exam with Questions & Answers | Set: 7

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.

saving Apex errors in a custom object can be a way to report errors from an Apex job. The article provides an example of how to create a custom object called AsyncApexError__c and use a trigger to insert error records into it. The custom object can then be used for reporting or notification purposes.

The correct answer is B, use data classification metadata fields available in field definition. Data classification metadata fields are standard fields that allow you to classify the sensitivity level of your data based on your organization’s policies. You can use these fields to indicate whether a field contains confidential, restricted, or general data. These fields are available for both standard and custom objects in Salesforce. Using app exchange products, creating a custom picklist field, or building reports would not be as effective or consistent as using data classification metadata fields.

According to the Data Modeling unit on Trailhead, some of the key actions that should be done when data modeling in Salesforce are identifying data elements, mapping legacy data, and implementing legacy data model. The unit states that “Before you start creating objects and fields in Salesforce, you need to identify the data elements that you want to store and work with. … Next, you need to map your legacy data to Salesforce objects and fields. … Finally, you need to implement your data model in Salesforce by creating custom objects and fields using declarative tools or Metadata API.” Therefore, these are the correct actions for migrating a legacy client server app to Salesforce.

 Salesforce allows up to four objects in a single report type. This means that if an architect wants to create a report that compiles data from Accounts, Contacts, Opportunities, Orders, and Order Line Items, they will run into a difficulty because that would require five objects in a single report type. To overcome this limitation, the architect can either create two separate report types and join them in a joined report, or use an external reporting tool that can access data from multiple objects.

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.

 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

According to the Salesforce documentation, a relationship field is a field that allows linking one object to another object in Salesforce. There are different types of relationship fields that have different characteristics and behaviors, such as master-detail, lookup, indirect lookup, external lookup, etc.

To recommend a type of relationship field for this scenario, where legacy inventory data will be stored in a custom child object called Inventory__c, inventory data should be related to the standard Account object, the Inventory__c object should inherit the same sharing rules as the Account object, and anytime an Account record is deleted in Salesforce, the related Inventory__c record(s) should be deleted as well, a data architect should recommend:

Master-detail relationship field on Inventory__c, related to Account (option B). This means creating a field on the Inventory__c object that references the Account object as its parent. A master-detail relationship field establishes a parent-child relationship between two objects, where the parent object controls certain behaviors of the child object. For example, a master-detail relationship field can:

Inherit the sharing and security settings from the parent object to the child object. This means that the users who can access and edit the parent record can also access and edit the related child records.

Cascade delete from the parent object to the child object. This means that when a parent record is deleted, all the related child records are also deleted.

Roll up summary fields from the child object to the parent object. This means that the parent object can display aggregated information from the child records, such as count, sum, min, max, or average.

Master-detail relationship field on Account, related to Inventory__c (option A) is not a good solution, as it reverses the direction of the relationship. This means creating a field on the Account object that references the Inventory__c object as its parent. This is not possible, as a standard object cannot be on the detail side of a master-detail relationship. Indirect lookup relationship field on Account, related to Inventory__c (option C) is also not a good solution, as it is a special type of relationship field that allows linking a custom object to a standard object on an external system using an indirect reference. This is not applicable for this scenario, as both objects are in Salesforce and do not need an external reference. Lookup relationship field on Inventory__c related to Account (option D) is also not a good solution, as it establishes a looser relationship between two objects than a master-detail relationship. A lookup relationship field does not inherit sharing and security settings from the parent object to the child object, does not cascade delete from the parent object to the child object, and does not roll up summary fields from the child object to the parent object.

 Integrate SAP with Salesforce, SAP to legacy CRM but not legacy CRM to Salesforce. This is a good recommendation because it allows both Salesforce and the legacy CRM to interact with the ERP system, which can be the source of truth for some data entities. However, it avoids creating a direct connection between Salesforce and the legacy CRM, which can cause data duplication and synchronization issues. Suggest MDM solution and link MDM to salesforce and SAP. This is another good recommendation because it can help manage the data lifecycle and quality across multiple systems, as well as provide a single view of the customer data

Creating an external object Invoice_x with a Lookup relationship with Opportunity is the best option for modeling invoices, considering performance and data storage space. An external object allows the data to be stored in the ERP system and accessed via OData in Salesforce. This reduces the data storage consumption in Salesforce and improves the performance of queries and reports. A Lookup relationship allows the sales reps to view the invoice status and amount from the opportunity page. The other options would either consume more data storage space, require additional customization, or not provide real-time data access