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

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.

A Sales KPI Dashboard is one reporting option that Get Cloudy Consulting should consider to understand key relevant performance figures and help managers take corrective actions where appropriate. A Sales KPI Dashboard can display various metrics that indicate the health and effectiveness of the sales team, such as quota attainment, pipeline value, win rate, average deal size, sales cycle length, and more. A Sales KPI Dashboard can also help identify trends, patterns, and areas for improvement.

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.

Creating a report in an external system combining Salesforce Account data and Invoice data from the ERP, and creating a Visualforce page combining Salesforce Account data and Invoice external object data are two approaches that an architect can suggest for achieving this solution. Both of these approaches can display data from both Accounts and Invoices in one place, using either an external reporting tool or a custom web page. Creating a report combining data from the Account standard object and the Invoices external object is not possible because Salesforce does not support reporting on external objects. Creating a separate Salesforce report for Accounts and Invoices and combining them in a dashboard is not ideal because it will not show the data in one report, but rather in two separate components.

According to the exam guide, one of the objectives is to 'describe how to use queryAll() or ALL ROWS keywords to access deleted records in Apex and SOQL'1. This implies that option C is the correct way to access deleted records in Salesforce. Option D is not correct because sending data to a data warehouse does not maintain the data in Salesforce.Options A and B are not correct because they do not apply to deleted records2.

According to the exam guide, one of the objectives is to 'describe the use cases and considerations for using AppExchange apps and Wave Analytics'1. This implies that options A and B are both valid approaches to provide more analytical insights.Option C is not correct because weekly snapshots are used to track changes over time, not to provide advanced analytics3. Option D is not correct because setup audit trails are used to monitor changes in the setup menu, not to provide analytical insights.

According to the exam guide, one of the objectives is to 'describe the use cases and considerations for using various tools and techniques for data migration (for example, Data Loader, Bulk API)'1. This implies that option B is the correct way to extract large volumes of data from Salesforce. The Bulk API is designed to handle large-scale data operations and avoid timeouts. Option A is not correct because the SOAP API is not optimized for large data sets and may encounter limits. Option C is not correct because GZIP compression does not prevent timeouts, but rather reduces the size of the data transferred. Option D is not correct because Batch Apex is used to process records asynchronously in Salesforce, not to export data to an external system.

According to the exam guide, one of the objectives is to 'describe best practices for implementing a single-org strategy in a B2C scenario'1. This implies that option D is the best practice for loading individual consumers as contacts in Salesforce. This approach avoids creating unnecessary accounts and reduces data duplication. Option C is not correct because it creates one account per contact, which increases data volume and complexity. Options A and B are not correct because they do not leverage the standard contact object, which provides native functionality and integration with other Salesforce features.

According to the exam guide, one of the objectives is to 'describe the use cases and considerations for deferring sharing calculations'1. This implies that option A is the correct way to load large amounts of data into Salesforce without affecting performance and data integrity.Deferring sharing calculations allows the data to be loaded first and then the sharing rules to be applied later2.Option B is not correct because workflows are not recommended for calculating summary values, as they can cause performance issues and data skew3. Option C is not correct because triggers are also not recommended for calculating summary values, as they can cause governor limit errors and data inconsistency. Option D is not correct because external IDs are used to link records from different systems, not to improve data loading performance.