For a production cutover, a large number of Account records will be loaded into Salesforce from a legacy system. The legacy system does not have enough information to determine the Ownership for these Accounts upon initial load. Which two recommended options assign Account ownership to mitigate potential performance problems?

• A.Let a "system user" own all the Account records and make this user part of the highest-level role in the Role Hierarchy.
• B.Let a "system user" own the Account records and assign this user to the lowest-level role in the Role Hierarchy.
• C.Let a "system user" own all the Account records without assigning any role to this user in Role Hierarchy.
• D.Let the VP of the Sales department, who will report directly to the senior VP, own all the Account records.

Comment: *

Name: *

Email: *

Verification: *

Universal Containers (UC) requires 2 years of customer related cases to be available on SF for operational reporting. Any cases older than 2 years and upto 7 years need to be available on demand to the Service agents. UC creates 5 million cases per yr.
Which 2 data archiving strategies should a data architect recommend? Choose 2 options:

• A.Use custom objects for cases older than 2 years and use nightly batch to move them.
• B.Sync cases older than 2 years to an external database, and provide access to Service agents to the database
• C.Use Big objects for cases older than 2 years, and use nightly batch to move them.
• D.Use Heroku and external objects to display cases older than 2 years and bulk API to hard delete from Salesforce.

Comment: *

Name: *

Email: *

Verification: *

Universal Containers has millions of rows of data in Salesforce that are being used in reports to evaluate historical trends. Performance has become an issue, as well as data storage limits. Which two strategies should be recommended when talking with stakeholders?

• A.Use scheduled batch Apex to copy aggregate information into a custom object and delete the original records.
• B.Combine Analytics Snapshots with a purging plan by reporting on the snapshot data and deleting the original records.
• C.Use Data Loader to extract data, aggregate it, and write it back to a custom object, then delete the original records.
• D.Configure the Salesforce Archiving feature to archive older records and remove them from the data storage limits.

Comment: *

Name: *

Email: *

Verification: *

Northern Trail Outfitters <NTO> is streaming IoT data from connected devices to a cloud database. Every 24 hours. 100,000 records are generated.
NIO employees will need to see these lol records within Salesforce and generate weekly reports on it. Developers may also need to write programmatic logic to aggregate the records and incorporate them into workflows.
Which data pattern will allow a data architect to satisfy these requirements, while also keeping limits in mind?

• A.Persistence
• B.Bidirectional integration
• C.Virtualization
• D.Unidirectional integration

Comment: *

Name: *

Email: *

Verification: *

UC has millions of case records with case history and SLA dat
a. UC's compliance team would like historical cases to be accessible for 10 years for Audit purpose.
What solution should a data architect recommend?

• A.Archive Case data using Salesforce Archiving process
• B.Purchase more data storage to support case object
• C.Use a custom object to store archived case data.
• D.Use a custom Big object to store archived case data.

Comment: *

Name: *

Email: *

Verification: *