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

A required Lookup relationship ensures that the Shipment record must have a value for each of the three parent records, and also prevents the deletion of those parent records if they are referenced by a Shipment record. A Master-Detail relationship would not allow separate sharing models for each custom object, and a VLOOKUP formula field would not enforce the relationship or prevent deletion

Creating customers as Contacts and relating them to Business and Residential Accounts using the Account Contact Relationships (option A) is the best option to recommend for a single view of these customers without creating multiple customer records, as it allows the data architect to model complex relationships between customers and accounts using native Salesforce features and tools. Creating customers as Person Accounts and relating them to Business and Residential Accounts using the Account Contact relationship (option B) is not a good option, as it may create data redundancy and inconsistency, and it does not leverage the existing Contact object. Creating customers as individual objects and relating them with Accounts for Business and Residence accounts (option C) is also not a good option, as it may require more customization and maintenance effort, and it does not leverage the existing Account and Contact objects. Creating customers as Accounts for Residence Account and using Parent Account to relate Business Account (option D) is also not a good option, as it may create confusion and complexity with the account hierarchy, and it does not leverage the existing Contact object.

According to Trailhead2, record types are a feature that allows administrators to create different business processes, page layouts, and picklist values for different types of records within an object. Record types can be used to maintain different dealer types in Salesforce by creating record types for each of the dealer types and assigning them appropriate attributes, processes, and rules. Option A is the correct answer because it suggests using Accounts for dealers, and creating record types for each of the dealer types. Option B is incorrect because creating dealers as Accounts, and building custom views for each of the dealer types does not allow CRM users to enter only attributes related to the customer types, nor does it enable different processes and business rules for each of the customer types. Option C is incorrect because using Accounts for dealers and custom picklist field for each of the dealer types does not allow CRM users to enter only attributes related to the customer types, nor does it enable different processes and business rules for each of the customer types. Option D is incorrect because creating Custom objects for each dealer types and custom fields for dealer attributes can be unnecessary and complex, as it requires creating multiple objects and relationships instead of using the standard Account object.

Storing the data in a staging database and de-duplicating identical records (option D) is the best solution for a successful migration to mitigate the pain point, as it allows the data architect to identify and merge duplicate customers before they are imported into Salesforce. Hiring an intern manually de-duplicate the records after migrating to Salesforce (option A) is not a good solution, as it may be time-consuming and error-prone, and it does not prevent duplicate records from being created in Salesforce. Migrating the data as is and using Salesforce’s de-duplicating feature (option B) is also not a good solution, as it may cause data quality issues and conflicts, and it does not address the root cause of the duplication. Having the users manually clean the data in the old system prior to migration (option C) is also not a good solution, as it may be unrealistic and impractical, and it does not leverage any automated tools or processes.

 According to the Salesforce documentation1, the “UNABLE _TO_LOCK_ROW” error occurs when a record is being updated or created, and another operation tries to access or update the same record at the same time. This can cause lock contention and timeout issues. To resolve the error, some of the recommended solutions are:

Perform a batch job in serial mode and reduce the batch size (option B). This means running the batch job one at a time and processing fewer records per batch. This can reduce the chances of concurrent updates and lock contention on the same records.

Use the FOR UPDATE keyword to lock records in Apex code or API calls. This means explicitly locking the records that are being accessed or updated by a transaction, and preventing other transactions from modifying them until the lock is released. This can avoid conflicts and errors between concurrent operations on the same records2.

Defer rollup summary field calculation during data migration (option A). This means disabling the automatic calculation of rollup summary fields on the parent object when child records are inserted or updated. This can improve performance and avoid locking issues on the parent records. However, this option is only available for custom objects, not standard objects3.

Performing a batch job in parallel mode and reducing the batch size (option C) is not a good solution, as it can still cause lock contention and errors if multiple batches try to access or update the same records at the same time. Leveraging Data Loader’s platform API to load data (option D) is also not a good solution, as it can still encounter locking issues if other operations are modifying the same records at the same time.

The best data archiving strategies for UC are to use Big objects and Heroku with external objects. Big objects allow storing large amounts of data on the Salesforce platform without affecting performance or storage limits. They also support point-and-click tools, triggers, and Apex code. Heroku is a cloud platform that can host external databases and integrate with Salesforce using external objects. External objects enable on-demand access to external data sources via standard Salesforce APIs and user interfaces. Using bulk API to hard delete cases from Salesforce will free up storage space and improve performance.

Whether the system of record changes for different tables and the number of systems that are integrating with each other are two factors that the architect should take into consideration when deciding whether or not to use a Master Data Management system to achieve the solution of integrating data and resolving duplicates and discrepancies between Salesforce and one or more external systems. The system of record is the authoritative source of truth for a given entity or field in a given context. If different systems have different systems of record for different tables, then a Master Data Management system can help to manage and synchronize the data across systems and ensure data quality and consistency. The number of systems that are integrating with each other is another factor that affects the complexity and scalability of the integration solution. If there are many systems that need to integrate with each other, then a Master Data Management system can provide a centralized and standardized way of integrating data and resolving duplicates and discrepancies across systems. The other factors are not relevant or important for deciding whether or not to use a Master Data Management system, as they do not affect the data quality or integration challenges that a Master Data Management system can address.

 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.

A master-detail field on VTOTime__c to Project__c is the data relationship that the data architect should use to support the requirement when creating the custom VTOTime__c object. A master-detail relationship creates a parent-child relationship between two objects, where the master record controls certain behaviors of the detail record, such as security, ownership, deletion, and roll-up summary fields. By using a master-detail field on VTOTime__c to Project__c, you can ensure that the ability to view or edit the VTOTime__c object is the same as the Project__c record, and that managers can see the total hours volunteered while viewing the Project__c record using a roll-up summary field.

 Skinny tables are custom tables that contain frequently used fields from a standard or custom object. They are used to improve performance by reducing the number of database joins required for queries. Skinny tables have the following characteristics1:

They do not include soft-deleted records, which means they only contain active records and save space.

They avoid resource intensive joins by storing data from multiple objects in one table, which reduces the query time and complexity.

Their tables are kept in sync with their source tables when the source tables are modified, which ensures data consistency and accuracy.