Northern Trail Outfitters (NTO) has outgrown its current Salesforce org and will be migrating to a new org shortly. As part of this process, NTO will be migrating all of its metadata and data. NTO's data model in the source org has a complex relationship hierarchy with several master-detail and lookup relationships across objects, which should be maintained in the target org.
Which three things should a data architect do to maintain the relationship hierarchy during migration? (Choose three.)

• A.Keep the relationship fields populated with the source record IDs in the import file.
• B.Redefine the master-detail relationship fields to lookup relationship fields in the target org.
• C.Create an external ID field for each object in the target org and map source record IDs to this field.
• D.Replace source record IDs with new record IDs from the target org in the import file.
• E.Use data loader to export the data from the source org and then import/upsert into the target org in sequential order.

Comment: *

Name: *

Email: *

Verification: *

Universal Containers is migrating 100,000 accounts from an enterprise resource planning (ERP) to Salesforce and is concerned about ownership skew and performances.
Which three recommendations should a data architect provide to prevent ownership skew? (Choose three.)

• A.Assign a default user as owner of accounts, and assign role in hierarchy
• B.Assign a default user as owner of accounts and assign top most role in hierarchy
• C.Keep users out of public groups that can be used as the source for sharing rules
• D.Assign a default user as owner of accounts and do not assign any role to default user
• E.Assign view all permissions on profile to give access to account

Comment: *

Name: *

Email: *

Verification: *

Universal Containers (UC) has a data model as shown in the image. The Project object has a private sharing model, and it has Roll -Up summary fields to calculate the number of resources assigned to the project, total hours for the project, and the number of work items associated to the project. What should the architect consider, knowing there will be a large amount of time entry records to be loaded regularly from an external system into Salesforce.com?

• A.Use workflow to calculate summary values instead of Roll -Up.
• B.Load all data after deferring sharing calculations.
• C.Use triggers to calculate summary values instead of Roll -Up.
• D.Load all data using external IDs to link to parent records.

Comment: *

Name: *

Email: *

Verification: *

NTO would like to retrieve their SF orgs meta data programmatically for backup within a various external. Which API is the best fit for accomplishing this task?

• A.Bulk API in serial mode
• B.SOAP API
• C.Tooling API
• D.Metadata API

Comment: *

Name: *

Email: *

Verification: *

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?

• A.Create a mashup page that will present the billing system records within Salesforce.
• B.Create a custom object and migrate the last 12 months of invoice data into Salesforce so it can be displayed on the Account layout.
• C.Write an Apex callout and populate a related list to display on the account record.
• D.Create a visual force tab with the billing system encapsulated within an iframe.

Comment: *

Name: *

Email: *

Verification: *