Skip to content Salesforce
(Plat-Arch-201)
105 Minutes
257
Salesforce Certified Platform Data Architect
A: Use triggers to populate denormalized related fields on the Account.
B: Use an indexed data field with bounded data filters.
C: Use Formula fields to surface information I related entities on the report.
D: Use unbounded date ranges to filter the report.
A: Ensure validation rules, triggers and other automation tools are disabled.
B: Ensure duplication and matching rules and defined.
C: Import the data in smaller batches over a 24-hour period.
D: Bulkily the trigger to handle import leads.
A: Review the metadata xml files for redundant fields to consolidate.
B: Determine if any integration points create records in Salesforce.
C: Run key reports to determine what fields should be required.
D: Export the setup audit trail to review what fields are being used.
E: Review the sharing model to determine impact on duplicate records.
A: Leverage real-time integration to pull records into Salesforce.
B: Bring all data Salesforce, and delete it after a year.
C: Leverage mashup to display historical records in Salesforce.
D: Build a chair solution to go the legacy system and display records.
A: Master Data Management systems determine system of record, and the Architect doesn't have to think about what data is controlled by what system.
B: Key stakeholders should review any fields that share the same purpose between systems to see how they will be used in Salesforce.
C: The database schema for each external system should be reviewed, and fields with different names should always be separate fields in Salesforce.
D: Any field that is an input field in either external system will be overwritten by the last record integrated and can never have a system of record.
