Universal Containers has a Sales Cloud implementation for a sales team and an enterprise resource planning (ERP) as a customer master. Sales teams are complaining about duplicate account records and data quality issues with account data.
Which two solutions should a data architect recommend to resolve the complaints? (Choose two.)
To resolve the complaints about duplicate account records and data quality issues, integrating Salesforce with the ERP and making the ERP the system of truth ensures that the data in Salesforce remains consistent and up-to-date. Additionally, implementing a de-dupe solution within Salesforce addresses the issue of existing duplicate records by merging them and establishes clear account ownership rules to prevent future duplicates. These combined actions ensure both immediate resolution of the duplicate issue and maintain data quality over time.
Universal Containers (UC) has adopted Salesforce as its primary sales automation tool. UC has 100,000 customers with a growth rate of 10% a year. UC uses an on-premise web-based billing and invoice system that generates over 1 million invoices a year supporting a monthly billing cycle.
The UC sales team needs to be able to pull up a customer record and view their account status, invoice history, and open opportunities without navigating outside of Salesforce.
What should a data architect use to provide the sales team with the required functionality?
To allow the UC sales team to view customer account status, invoice history, and open opportunities without navigating outside of Salesforce, creating a mashup page is the best solution. A mashup page can integrate data from the on-premise web-based billing and invoice system into Salesforce in a seamless way. This approach ensures that the sales team can access all needed information directly within Salesforce without the need to migrate extensive data or create complex custom objects and Apex callouts.
Universal Containers (UC) is in the process of migrating legacy inventory data from an enterprise resource planning (ERP) system into Sales Cloud with the following requirements:
1. Legacy inventory data will be stored in a custom child object called Inventory__c.
2. Inventory data should be related to the standard Account object.
3. The Inventory__c object should inherit the same sharing rules as the Account object.
4. Anytime an Account record is deleted in Salesforce. the related Inventory__c record(s) should be deleted as well.
What type of relationship field should a data architect recommend in this scenario?
The requirements indicate that legacy inventory data will be stored in a custom child object (Inventory__c) and needs to inherit the same sharing rules as the standard Account object. Additionally, related Inventory__c records should be deleted when an Account record is deleted. The proper relationship for these requirements is a Master-Detail relationship on Inventory__c related to Account. This ensures that Inventory__c records follow the sharing rules of the Account and are automatically deleted when the related Account is deleted.
Northern Trail Outfitters has implemented Salesforce for its sales associates nationwide. Senior management is concerned that the executive dashboards are not reliable for their real-time decision-making. On analysis, the team found the following issues with data entered in
Salesforce:
1. Information in certain records is incomplete.
2. Incorrect entry in certain fields causes records to be excluded in report filters.
3. Duplicate entries cause incorrect counts.
Which three steps should a data architect recommend to address the issues? (Choose three.)
To address the issues with data quality and reliability in Salesforce, it is essential to first enrich and augment the data with complete and accurate information, which can be achieved by exploring third-party data providers. Implementing a data-quality dashboard would be crucial to actively monitor and correct incomplete or incorrect records. Additionally, leveraging Salesforce features such as validation rules can prevent the entry of incomplete and incorrect records, maintaining data integrity from the outset. These steps will collectively ensure the data in Salesforce is reliable for real-time decision-making and reporting.
Northern Trail Outfitters (NTO) has been using Salesforce for Sales and Service for 10 years. For the past two years, the marketing group has noticed a rise from 0% to 35% in returned mail when sending mail using the contact information stored in Salesforce.
Which solution should the data architect use to reduce the amount of returned mail?
To reduce the amount of returned mail, leveraging a third-party data source to update the contact information in Salesforce is the most appropriate solution. This method ensures that the contact information is accurate and up-to-date without placing additional burdens on the sales team or customers. It is a more efficient and reliable approach compared to manually verifying information or deleting contacts, which could result in loss of potentially valuable customer data.