Data-Architect Exam Question 21
The architect is planning a large data migration for Universal Containers from their legacy CRM system to Salesforce. What three things should the architect consider to optimize performance of the data migration? Choose 3 answers
Data-Architect Exam Question 22
Universal Containers (UC) is planning to move away from legacy CRM to Salesforce. As part of one-time data migration, UC will need to keep the original date when a contact was created in the legacy system. How should an Architect design the data migration solution to meet this requirement?
Data-Architect Exam Question 23
UC has a variety of systems across its technology landscape, including SF, legacy enterprise resource planning (ERP) applications and homegrown CRM tools. UC has decided that they would like to consolidate all customer, opportunity and order data into Salesforce as part of its master data management (MDM) strategy.
What are the 3 key steps that a data architect should take when merging data from multiple systems into Salesforce? Choose 3 answers:
What are the 3 key steps that a data architect should take when merging data from multiple systems into Salesforce? Choose 3 answers:
Data-Architect Exam Question 24
A customer needs a sales model that allows the following:
Opportunities need to be assigned to sales people based on the zip code.
Each sales person can be assigned to multiple zip codes.
Each zip code is assigned to a sales area definition. Sales is aggregated by sales area for reporting.
What should a data architect recommend?
Opportunities need to be assigned to sales people based on the zip code.
Each sales person can be assigned to multiple zip codes.
Each zip code is assigned to a sales area definition. Sales is aggregated by sales area for reporting.
What should a data architect recommend?
Data-Architect Exam Question 25
Get Cloudy Consulting uses an invoicing system that has specific requirements. One requirement is that attachments associated with the Invoice_c custom object be classified by Types (i.e., ""Purchase Order"",
""Receipt"", etc.) so that reporting can be performed on invoices showing the number of attachments grouped by Type.
What should an Architect do to categorize the attachments to fulfill these requirements?
""Receipt"", etc.) so that reporting can be performed on invoices showing the number of attachments grouped by Type.
What should an Architect do to categorize the attachments to fulfill these requirements?
