Every year, Ursa Major Solar has more than 1 million orders. Each order contains an average of 10 line items. The Chief Executive Officer (CEO) needs the Sales Reps to see how much money each customer generates year-over-year. However, data storage is running low in Salesforce.
Which approach for data archiving is appropriate for this scenario?

• A.1. Annually export and delete order line items. 2. Store them in a zip file in case the data is needed later.
• B.1. Annually export and delete orders and order line items. 2. Store them in a zip file in case the data is needed later.
• C.1. Annually aggregate order amount data to store in a custom object. 2. Delete those orders and order line items.
• D.1. Annually delete orders and order line items. 2. Ensure the customer has order information in another system.

Comment: *

Name: *

Email: *

Verification: *

A manager at Cloud Kicks is importing Leads into Salesforce and needs to avoid creating duplicate records.
Which two approaches should the manager take to achieve this goal? (Choose two.)

• A.Acquire an AppExchange Lead de-duplication application.
• B.Run the Salesforce Lead Mass de-duplication tool.
• C.Implement Salesforce Matching and Duplicate Rules.
• D.Create a Workflow Rule to check for duplicate records.

Comment: *

Name: *

Email: *

Verification: *

UC has millions of Cases and are running out of storage. Some user groups need to have access to historical cases for up to 7 years.
Which 2 solutions should a data architect recommend in order to minimize performance and storage issues?
Choose 2 answers:

• A.Create a custom object to store case history and run reports on it.
• B.Leverage big object to archive case data and lightning components to show archived data.
• C.Export data out of salesforce and store in Flat files on external system.
• D.Leverage on premise data archival and build integration to view archived data.

Comment: *

Name: *

Email: *

Verification: *

Get Cloudy Consulting uses an invoicing system that has specific requirements. One requirement is that attachments associated with the Invoice_c custom object be classified by Types (i.e., ""Purchase Order"", ""Receipt"", etc.) so that reporting can be performed on invoices showing the number of attachments grouped by Type.
What should an Architect do to categorize the attachments to fulfill these requirements?

• A.Create a custom picklist field for the Type on the standard Attachment object with the values.
• B.Add additional options to the standard ContentType picklist field for the Attachment object.
• C.Create a custom object related to the Invoice object with a picklist field for the Type.
• D.Add a ContentType picklist field to the Attachment layout and create additional picklist options.

Comment: *

Name: *

Email: *

Verification: *

An Architect needs information about who is creating, changing, or deleting certain fields within the past four months.
How can the Architect access this information?

• A.Create a field history report for the fields in question.
• B.After exporting the metadata, search it for the fields in question.
• C.After exporting the setup audit trail, find the fields in question.
• D.Remove "customize application" permissions from everyone else.

Comment: *

Name: *

Email: *

Verification: *