Salesforce : Plat-Arch-201 Questions & Answers

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

UC has migrated its Back-office data into an on-premise database with REST API access. UC recently implemented Sales cloud for its sales organization. But users are complaining about a lack of order data inside SF. UC is concerned about SF storage limits but would still like Sales cloud to have access to the data. Which design patterns should a data architect select to satisfy the requirement?

• A. Build a UI for the on-premise system and iframe it in Salesforce
• B. Migrate and persist the data in SF to take advantage of native functionality.
• C. Use SF Connect to virtualize the data in SF and avoid storage limits.
• D. Develop a bidirectional integration between the on-premise system and Salesforce.

Universal Containers (UC) has a custom discount request object set as a detail object with a custom product object as the master. There is a requirement to allow the creation of generic discount requests without the custom product object as its master record. What solution should an Architect recommend to UC?

• A. Change the master-detail relationship to a lookup relationship.
• B. Create a placeholder product record for the generic discount request.
• C. Mandate the selection of a custom product for each discount request.
• D. Remove the master-detail relationship and keep the objects separate.

Universal Containers (UC) has a requirement to create an Account plan object that is related to the Account object. Each Account plan needs to have an Account object, but the accessibility requirement of the Account plan is different from the Account object. What should an Architect recommend?

• A. Create a custom account plan object as detail with Account as mater in a master-detail relationship.
• B. Create a custom account plan object as detail with Account as master with additional sharing rules to allow access.
• C. Create an account plan object with a lookup relationship to Account with validation rules to enforce the Account association.
• D. Create an account plan object with a lookup relations to Account without any validation rules to enforce the Account association.

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 option

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