An Architect needs to assist Get Cloudy Consulting to maintain Lead data, even after Lead records are deleted and the Recycle Bin emptied.
What should the Architect do to implement this solution?

• A.Use a Lead standard report and filter on the IsDeleted standard field.
• B.Send data to a Data Warehouse and mark Leads as deleted in that system.
• C.Use a Converted Lead report to display data on Leads that have been deleted.
• D.Query Salesforce with the queryAll API method or using the ALL ROWS SOQL keywords.

Comment: *

Name: *

Email: *

Verification: *

UC has a salesforce org with multiple automated processes defined for group membership process. UC also have multiple admins on staff that perform manual adjustments to the role hierarchy. The automated task and manual task overlap daily and UC is experiencing "Lock errors" consistently.
What should a data architect recommend mitigate these errors?

• A.Enable sharing recalculations
• B.Remove SOQL statements from APEX loops.
• C.Ask salesforce support for addition CPU power.
• D.Enable granular locking.

Comment: *

Name: *

Email: *

Verification: *

Universal Containers (UC) has several custom Visualforce applications have been developed in which users are able to edit Opportunity records. UC struggles with data completeness on their Opportunity records and has decided to make certain fields required that have not been in the past. The newly required fields are dependent on the Stage of the Opportunity, such that certain fields are only required once an Opportunity advances to later stages. There are two fields. What is the simplest approach to handle this new requirement?

• A.Use a validation rule for each field that takes the Stage into consideration.
• B.Write an Apex trigger that checks each field when records are saved.
• C.Update the Opportunity page layout to mark these fields as required.
• D.Update these Opportunity field definitions in Setup to be required.

Comment: *

Name: *

Email: *

Verification: *

Universal Containers (UC) loads bulk leads and campaigns from third-party lead aggregators on a weekly and monthly basis. The expected lead record volume is 500K records per week, and the expected campaign records volume is 10K campaigns per week. After the upload, Lead records are shared with various sales agents via sharing rules and added as Campaign members via Apex triggers on Lead creation. UC agents work on leads for 6 months, but want to keep the records in the system for at least 1 year for reference. Compliance requires them to be stored for a minimum of 3 years. After that, data can be deleted. What statement is true with respect to a data archiving strategy for UC?

• A.UC can leverage recycle bin capability, which guarantees record storage for 15 days after deletion.
• B.UC can store long-term lead records in custom storage objects to avoid counting against storage limits.
• C.UC can leverage a "tier"-based approach to classify the record storage need.
• D.UC can leverage the Salesforce Data Backup and Recovery feature for data archival needs.

Comment: *

Name: *

Email: *

Verification: *

Universal Containers (UC) is facing data quality issues where Sales Reps are creating duplicate customer accounts, contacts, and leads. UC wants to fix this issue immediately by prompting users about a record that possibly exists in Salesforce. UC wants a report regarding duplicate records. What would be the recommended approach to help UC start immediately?

• A.Create an after insert and update trigger on the account, contact and lead, and send an error if a duplicate is found using a custom matching criteria.
• B.Create a before insert and update trigger on account, contact, and lead, and send an error if a duplicate is found using a custom matching criteria.
• C.Create a duplicate rule for account, lead, and contact, use standard matching rules for these objects, and set the action to report and alert for both creates and edits.
• D.Create a duplicate rule for account, lead, and contact, use standard matching rules for these objects, and set the action to block for both creates and edits.

Comment: *

Name: *

Email: *

Verification: *