NTO uses salesforce to manage relationships and track sales opportunities. It has 10 million customers and 100 million opportunities. The CEO has been complaining 10 minutes to run and sometimes failed to load, throwing a time out error. Which 3 options should help improve the dashboard performance? Choose 3 answers:
A.
Use selective queries to reduce the amount of data being returned.
B.
De-normalize the data by reducing the number of joins.
C.
Remove widgets from the dashboard to reduce the number of graphics loaded.
D.
Run the dashboard for CEO and send it via email.
E.
Reduce the amount of data queried by archiving unused opportunity records.
Use selective queries to reduce the amount of data being returned.
De-normalize the data by reducing the number of joins.
Reduce the amount of data queried by archiving unused opportunity records.
All accounts and opportunities are created in Salesforce. Salesforce is integrated with three systems:
• An ERP system feeds order data into Salesforce and updates both Account and Opportunity records.
• An accounting system feeds invoice data into Salesforce and updates both Account and Opportunity records.
• A commission system feeds commission data into Salesforce and updates both Account and Opportunity records.
How should the architect determine which of these systems is the system of record?
A.
Account and opportunity data originates in Salesforce, and therefore Salesforce is the system of record.
B.
Whatever system updates the attribute or object should be the system of record for that field or object.
C.
Whatever integration data flow runs last will, by default, determine which system is the system of record.
D.
Data flows should be reviewed with the business users to determine the system of record per object or field.
Data flows should be reviewed with the business users to determine the system of record per object or field.
Get Cloud Consulting needs to integrate two different systems with customer records into the Salesforce Account object. So that no duplicate records are created in Salesforce, Master Data Management will be used. An Architect needs to determine which system is the system of record on a field level. What should the Architect do to achieve this goal?
A.
Master Data Management systems determine system of record, and the Architect doesn't have to think about what data is controlled by what system.
B.
Key stakeholders should review any fields that share the same purpose between systems to see how they will be used in Salesforce.
C.
The database schema for each external system should be reviewed, and fields with different names should always be separate fields in Salesforce.
D.
Any field that is an input field in either external system will be overwritten by the last record integrated and can never have a system of record.
The database schema for each external system should be reviewed, and fields with different names should always be separate fields in Salesforce.
Universal Containers is integrating a new Opportunity engagement system with Salesforce. According to their Master Data Management strategy, Salesforce is the system of record for Account, Contact, and Opportunity data. However, there does seem to be valuable Opportunity data in the new system that potentially conflicts with what is stored in Salesforce. What is the recommended course of action to appropriately integrate this new system?
A.
The MDM strategy defines Salesforce as the system of record, so Salesforce Opportunity values prevail in all conflicts.
B.
A policy should be adopted so that the system whose record was most recently updated should prevail in conflicts.
C.
The Opportunity engagement system should become the system of record for Opportunity records.
D.
Stakeholders should be brought together to discuss the appropriate data strategy moving forward.
Stakeholders should be brought together to discuss the appropriate data strategy moving forward.
Universal Containers is planning out their archiving and purging plans going forward for their custom objects Topic__c and Comment__c. Several options are being considered, including analytics snapshots, offsite storage, scheduled purges, etc. Which three questions should be considered when designing an appropriate archiving strategy?
A.
How many fields are defined on the custom objects that need to be archived?
B.
Which profiles and users currently have access to these custom object records?
C.
If reporting is necessary, can the information be aggregated into fewer, summary records?
D.
Will the data being archived need to be reported on or accessed in any way in the future?
E.
Are there any regulatory restrictions that will influence the archiving and purging plans?
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?
Universal Containers has 30 million case records. The Case object has 80 fields. Agents are reporting reports in the Salesforce org. Which solution should a data architect recommend to improve reporting performance?
A.
Create a custom object to store aggregate data and run reports.
B.
Contact Salesforce support to enable skinny table for cases.
C.
Move data off of the platform and run reporting outside Salesforce, and give access to reports.
D.
Build reports using custom Lightning components.
Move data off of the platform and run reporting outside Salesforce, and give access to reports.
Universals Containers’ system administrators have been complaining that they are not able to make changes to its users’ record, including moving them to new territories without getting “unable to lock row” errors. This is causing the system admins to spend hours updating user records every day. What should the data architect do to prevent the error?
A.
Reduce number of users updated concurrently.
B.
Enable granular locking.
C.
Analyze Splunk query to spot offending records.
D.
Increase CPU for the Salesforce org.
Enable granular locking.
Northern Trail Outfitters (NTO) wants to implement backup and restore for Salesforce data, Currently, it has data backup processes that runs weekly, which back up all Salesforce data to an enterprise data warehouse (EDW). NTO wants to move to daily backups and provide restore capability to avoid any data loss in case of outage. What should a data architect recommend for a daily backup and restore solution?
A.
Use AppExchange package for backup and restore.
B.
Use ETL for backup and restore from EDW.
C.
Use Bulk API to extract data on daily basis to EDW and REST API for restore.
D.
Change weekly backup process to daily backup, and implement a custom restore solution.
Use AppExchange package for backup and restore.
How can an architect find information about who is creating, changing, or deleting certain fields within the past two months?
A.
Remove "customize application" permissions from everyone else.
B.
Export the metadata and search it for the fields in question.
C.
Create a field history report for the fields in question.
D.
Export the setup audit trail and find the fields in question.
Export the setup audit trail and find the fields in question.
Every year, Ursa Major Solar has more than 1 million orders. Each order contains an average of 10 line items. The Chief Executive Officer (CEO) needs the Sales Reps to see how much money each customer generates year-over-year. However, data storage is running low in Salesforce. Which approach for data archiving is appropriate for this scenario?
A.
1. Annually export and delete order line items. 2. Store them in a zip file in case the data is needed later.
B.
1. Annually aggregate order amount data to store in a custom object. 2. Delete those orders and order line items.
C.
1. Annually export and delete orders and order line items. 2. Store them in a zip file in case the data is needed later.
D.
1. Annually delete orders and order line items. 2. Ensure the customer has order information in another system.
1. Annually aggregate order amount data to store in a custom object. 2. Delete those orders and order line items.
Universal Containers (UC) is launching an RFP to acquire a new accounting product available on AppExchange. UC is expecting to issue 5 million invoices per year, with each invoice containing an average of 10 line items. What should UC's Data Architect recommend to ensure scalability?
A.
Ensure invoice line items simply reference existing Opportunity line items.
B.
Ensure the account product vendor includes Wave Analytics in their offering.
C.
Ensure the account product vendor provides a sound data archiving strategy.
D.
Ensure the accounting product runs 100% natively on the Salesforce platform.
Ensure the account product vendor provides a sound data archiving strategy.
Universal Containers (UC) is building a Service Cloud call center application and has a multi-system support solution. UC would like or ensure that all systems have access to the same customer information. What solution should a data architect recommend?
A.
Make Salesforce the system of record for all data.
B.
Implement a master data management (MDM) strategy for customer data.
C.
Load customer data in all systems.
D.
Let each system be an owner of data it generates.
Implement a master data management (MDM) strategy for customer data.
Page 3 out of 22 Pages |
Previous |