Universal Containers (UC) has an Application custom object, which has tens of millions of records created in the past 5 years. UC needs the last 5 years of data to exist in Salesforce at all times for reporting and queries.
UC is currently encountering performance issues when reporting and running queries on this Object using date ranges as filters. Which two options can be used to improve report performance?

• A.Add custom indexes to the Date fields used for filtering the report.
• B.Add custom indexes to all fields on Application without a standard index.
• C.Run multiple reports to get different pieces of the data and combine them.
• D.Ask support to create a skinny table for Application with the necessary reporting fields.

Comment: *

Name: *

Email: *

Verification: *

Universal Containers (UC) uses the following Salesforce products:
* Sales Cloud for customer management.
* Marketing Cloud for marketing.
* Einstein Analytics for business reporting.
UC occasionally gets a list of prospects from third-party sources as comma-separated values (CSV) files for marketing purposes. Historically, UC would load these contacts into Lead object in Salesforce and sync to Marketing Cloud to send marketing communications. The number of records in the Lead object has grown over time and has been consuming large amounts of storage in Sales Cloud. UC is looking for recommendations to reduce the storage and advice on how to optimize the marketing process.
What should a data architect recommend to UC in order to immediately avoid storage issues in the future?

• A.Load the contacts directly to Marketing Cloud and have a reconciliation process to track prospects that are converted to customers.
• B.Continue to use the existing process to use Lead object to sync with Marketing Cloud and delete Lead records from Sales Cloud after the sync is complete.
• C.Load the CSV files in Einstein Analytics and sync with Marketing Cloud prior to sending marketing communications.
• D.Load the CSV files in an external database and sync with Marketing Cloud prior to sending marketing communications.

Comment: *

Name: *

Email: *

Verification: *

Cloud Kicks has the following requirements:
* Their Shipment custom object must always relate to a Product, a Sender, and a Receiver (all separate custom objects).
* If a Shipment is currently associated with a Product, Sender, or Receiver, deletion of those records should not be allowed.
* Each custom object must have separate sharing models.
What should an Architect do to fulfill these requirements?

• A.Create a required Lookup relationship to each of the three parent records.
• B.Create two Master-Detail and one Lookup relationship to the parent records.
• C.Associate the Shipment to each parent record by using a VLOOKUP formula field.
• D.Create a Master-Detail relationship to each of the three parent records.

Comment: *

Name: *

Email: *

Verification: *

Ursa Major Solar has 4 million rows of data in Salesforce that are used in reports to assess historical trends.
Both performance and data storage limits have become an issue.
Which two strategies are appropriate when discussing the issue with stakeholders? (Choose two.)

• A.Utilize Data Loader to extract data, aggregate it, and write it back to a custom object, then delete the original records.
• B.Utilize scheduled batch Apex to copy aggregate information into a custom object and delete the original records.
• C.Combine Analytics Snapshots with a purging plan by reporting on the snapshot data and deleting 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: *

Universal Containers (UC) has a multi-level master-detail relationship for opportunities, a custom opportunity line item object, and a custom discount request. UC has opportunity as master and custom line item object as detail in master-detail relationship. UC also has a custom line item object as master and a custom discount request object as detail in another master-detail relationship. UC has a requirement to show all sums of discounts across line items at an opportunity level. What is the recommended solution to address these requirements?

• A.Update the master-detail relationships to lookup relationships in order to allow the discount amount to roll up.
• B.Roll-up discount request amount at the line-item-level and line-item-level summary discount at the opportunity level.
• C.Use roll-up for the line-item-level summary and a trigger for the opportunity amount summary, as only one level roll-up is allowed.
• D.Remove the master-detail relationships and rely completely on workflow/triggers to summarize the discount amount.

Comment: *

Name: *

Email: *

Verification: *