A data architect is working with a large B2C retailer and needs to model the consumer account structure in Salesforce.
What standard feature should be selected in this scenario?

• A.Contacts
• B.Account Contact
• C.Person Accounts
• D.Individual Accounts

Comment: *

Name: *

Email: *

Verification: *

Universal Containers (UC) has an open sharing model for its Salesforce users to allow all its Salesforce internal users to edit all contacts, regardless of who owns the contact. However, UC management wants to allow only the owner of a contact record to delete that contact. If a user does not own the contact, then the user should not be allowed to delete the record. How should the architect approach the project so that the requirements are met?

• A.Create a "before delete" trigger to check if the current user is not the owner.
• B.Set the Sharing settings as Public Read Only for the Contact object.
• C.Set the profile of the users to remove delete permission from the Contact object.
• D.Create a validation rule on the Contact object to check if the current user is not the owner.

Comment: *

Name: *

Email: *

Verification: *

Universal Containers has a rollup summary field on account to calculate the number of contacts associated with an account. During the account load, Salesforce is throwing an "UNABLE _TO_LOCK_ROW" error.
Which solution should a data architect recommend to resolve the error?

• A.Defer rollup summary field calculation during data migration.
• B.Leverage Data Loader's platform API to load data.
• C.Perform a batch job in parallel mode and reduce the batch size.
• D.Perform a batch job in serial mode and reduce the batch size.

Comment: *

Name: *

Email: *

Verification: *

Which two best practices should be followed when using SOSL for searching?

• A.Use searches against single Objects for greater speed and accuracy.
• B.Keep searches specific and avoid wildcards where possible.
• C.Use SOSL option to ignore custom indexes as search fields are pre-indexed.
• D.Use Find in "ALL FIELDS" for faster searches.

Comment: *

Name: *

Email: *

Verification: *

NTO has implemented salesforce for its sales users. The opportunity management in salesforce 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 opportunity amount field on opportunities on a daily basis.
3. PPS is the trusted source within the 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 overriding issue?

• A.Create a custom field for opportunity amount that sales users update separating the fields that PPS updates.
• B.Create a custom field for opportunity amount that PPS updates separating the field that sales user updates.
• C.Change opportunity amount field access to read only for sales users using field level security.
• D.Change PPS integration to update only opportunity amount fields when values is NULL.

Comment: *

Name: *

Email: *

Verification: *