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

Comment: *

Name: *

Email: *

Verification: *

UC needs to load a large volume of leads into salesforce on a weekly basis. During this process the validation rules are disabled.
What should a data architect recommend to ensure data quality is maintained in salesforce.

• A.Activate validation rules once the leads are loaded into salesforce to maintain quality.
• B.Allow validation rules to be activated during the load of leads into salesforce.
• C.Ensure the lead data is preprocessed for quality before loading into salesforce.
• D.Develop custom APEX batch process to improve quality once the load is completed.

Comment: *

Name: *

Email: *

Verification: *

Northern Trail Outfitters (NTO) has implemented Salesforce for its sales users. The opportunity management in Saiesforce Is implemented as follows:
1. Sales users enter their opportunities in Salesforce for forecasting and reporting purposes.
2. NTO has a product pricing system (PPS) that is used to update the Opportunity Amount field on opportunities on a daily basis.
3. PPS is the trusted source within NTO for Opportunity Amount.
4. NTO uses Opportunity Forecast for its sales planning and management.
Sales users have noticed that their updates to the Opportunity Amount field are overwritten when PPS updates their opportunities.
How should a data architect address this overwriting issue?

• A.Change Opportunity Amount field access to Read Only for sales users field-level security.
• B.Change PSS integration to update only Opportunity Amount field when the value is null.
• C.Create a custom field for Opportunity amount that sales users update separating the field that PPS updates.
• D.Create a custom field for Opportunity amount that PSS updates separating the field sales user updates.

Comment: *

Name: *

Email: *

Verification: *

Universal Containers has a large number of Opportunity fields (100) that they want to track field history on.
Which two actions should an architect perform in order to meet this requirement? Choose 2 answers

• A.Create a custom object to store the previous and new field values.
• B.Create a custom object to store a copy of the record when changed.
• C.Select the 100 fields in the Opportunity Set History Tracking page.
• D.Use Analytic Snapshots to store a copy of the record when changed.

Comment: *

Name: *

Email: *

Verification: *

Universal Containers (UC) uses Salesforce for tracking opportunities (Opportunity). UC uses an internal ERP system for tracking deliveries and invoicing. The ERP system supports SOAP API and OData for bi-directional integration between Salesforce and the ERP system. UC has about one million opportunities. For each opportunity, UC sends 12 invoices, one per month. UC sales reps have requirements to view current invoice status and invoice amount from the opportunity page. When creating an object to model invoices, what should the architect recommend, considering performance and data storage space?

• A.Use Streaming API to get the current status from the ERP and display on the Opportunity page.
• B.Create a custom object Invoice _c with a master -detail relationship with Opportunity.
• C.Create an external object Invoice _x with a Lookup relationship with Opportunity.
• D.Create a custom object Invoice _c with a Lookup relationship with Opportunity.

Comment: *

Name: *

Email: *

Verification: *