Universal Containers (UC) is implementing a new customer categorization process where customers should be assigned to a Gold, Silver, or Bronze category if they've purchased UC's new support service. Customers are expected to be evenly distributed across all three categories. Currently, UC has around 500,000 customers, and is expecting 1% of existing non-categorized customers to purchase UC's new support service every month over the next five years. What is the recommended solution to ensure long-term performance, bearing in mind the above requirements?

• A.Implement a new Categories custom object and a master-detail relationship from Account to Category.
• B.Implement a new Categories custom object and create a lookup field from Account to Category.
• C.Implement a new picklist custom field in the Account object with Gold, Silver, and Bronze values.
• D.Implement a new global picklist custom field with Gold, Silver, and Bronze values and enable it in Account.

Comment: *

Name: *

Email: *

Verification: *

Universal Containers (UC) is migrating from an on-premise homegrown customer relationship management (CRM) system- During analysis, UC users highlight a pain point that there are multiple versions of many customers.
What should the data architect do for a successful migration to mitigate the pain point?

• A.Migrate the data as is, and use Salesforce's de-duplicating feature.
• B.Have the users manually clean the data in the old system prior to migration.
• C.Hire an intern manually de-duplicate the records after migrating to Salesforce.
• D.Store the data in a staging database, and de-duplicate identical records.

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 a Master-Detail relationship to each of the three parent records.
• C.Associate the Shipment to each parent record by using a VLOOKUP formula field.
• D.Create two Master-Detail and one Lookup relationship to the parent records.

Comment: *

Name: *

Email: *

Verification: *

Universal Containers (UC) has 1,000 accounts and 50,000 opportunities. UC has an enterprise security requirement to export all sales data outside of Salesforce on a weekly basis. The security requirement also calls for exporting key operational data that includes events such as file downloads, logins, logouts, etc. Which two recommended approaches would address the above requirement?

• A.Use Weekly Export to extract transactional data to on-premise systems.
• B.Use Event Monitoring to extract event data to on-premise systems.
• C.Use Field Audit History to capture operational data and extract it to on-premise systems.
• D.Use a custom built extract job to extract operational data to on-premise systems.

Comment: *

Name: *

Email: *

Verification: *

Universal Containers (UC) is planning to launch its Customer Community. The community will allow user to register shipment requests which are then processed by UC employees.
Shipment requests contain header information, and then a list of no more than 5 items being shipped. UC will initially roll out its community to 5,000 customers in Europe, and will ultimately roll out to 20,000 customers worldwide within the next two years. UC expects an average of 10 shipment requests per week per customer. UC wants customers to be able to view up to three years of shipment requests and use Saleforce reports. What is the recommended solution for UC's Data Architect to address the requirements?

• A.Create a custom object to track shipment requests with five lookup custom fields for each item being shipped Implement an archiving process that moves data off-platform after three years.
• B.Create an external custom object to track shipment requests and a child external object to track shipment items. External objects are stored off-platform in Heroku's Postgres database.
• C.Create an external custom object to track shipment requests with five lookup custom fields for each item being shipped. External objects are stored off-platform in Heroku's Postgres database.
• D.Create a custom object to track shipment requests and a child custom object to track shipment items. Implement an archiving process that moves data off-platform after three years.

Comment: *

Name: *

Email: *

Verification: *