Free Certified-Data-Architecture-and-Management-Designer – Certified Data Architecture and Management Designer Practice Test Question

Select all that apply, then click Submit answer.

• ○

  Use picklist fields rather than lookup to custom object.

• ○

  Limit assigning one user 10000 records ownership.

• ○

  Assign 10000 opportunities to one account.

• ○

  Limit associating 10000 opportunities to one account.

• ○

  Limit associating 10000 records looking up to same records.
  
  
  

Select all that apply, then click Submit answer.

• ○

  Data completeness

• ○

  Data loss and recovery

• ○

  Data duplication

• ○

  Data accuracy and quality

• ○

  Data standardization
  
  
  

Select all that apply, then click Submit answer.

• ○

  Create the users, upload all data, and then deploy the sharing rules.

• ○

  Contact Salesforce to activate indexing before uploading the data.

• ○

  First, load all account records, and then load all user records.

• ○

  Defer sharing calculations until the data has finished uploading.
  
  
  

Select all that apply, then click Submit answer.

• ○

  Create a unique global customer ID for each customer and store that in all system for referential identity.

• ○

  Use Salesforce CDC to sync customer data cross all systems to keep customer record in sync.

• ○

  Invest in data duplicate tool to de-dupe and merge duplicate records across all systems.

• ○

  Duplicate customer records across the system and provide a two-way sync of data between the systems.
  

• ○

  Create a customer master database external to Salesforce as a system of truth and sync the customer data with all systems.
  
  

Select all that apply, then click Submit answer.

• ○

  Acquire an AppExchange Lead de-duplication application.

• ○

  Implement Salesforce Matching and Duplicate Rules.

• ○

  Run the Salesforce Lead Mass de-duplication tool.

• ○

  Create a Workflow Rule to check for duplicate records.
  
  
  

Select all that apply, then click Submit answer.

• ○

  Schedule a weekly dashboard displaying records that are missing information to be sent to managers for review.

• ○

  Use Workflow, Validation Rules, and Force.com code (Apex) to enforce critical business processes.

• ○

  Schedule reports that will automatically catch duplicates and merge or delete the records every week.

• ○

  Store all data in an external system and set up an integration to Salesforce for view only access.
  
  
  

Select all that apply, then click Submit answer.

• ○

  Log a case with SF to update these fields

• ○

  Enable update records with Inactive Owners Permission

• ○

  Enable Set Audit fields upon Record Creation Permission
  

• ○

  Enable modify all and view all permission.
  
  
  

Select an option, then click Submit answer.

• ○

  use as ETL tool to orchestrate the migration.
  

• ○

  Use Data Loader for export and Data Import Wizard for import
  

• ○

  Write a script to use the Bulk API
  

• ○

  Use the Salesforces CLI to query, export, and import

Select an option, then click Submit answer.

• ○

  A middleware solution that extracts and distributes data across both the hub and spokes.

• ○

  Develop custom APIs to poll the hub org for change data and push into the spoke orgs.

• ○

  Develop custom APIs to poll the spoke for change data and push into the org.

• ○

  A backup and archive solution that extracts and restores data across orgs.
  
  
  

Select an option, then click Submit answer.

• ○

  Load all data using external IDs to link to parent records.

• ○

  Use workflow to calculate summary values instead of Roll -Up.

• ○

  Use triggers to calculate summary values instead of Roll -Up.

• ○

  Load all data after deferring sharing calculations.
  
  
  

Select an option, then click Submit answer.

• ○

  Load all data after deferring sharing calculations.

• ○

  Calculate summary values instead of Roll-Up by using workflow.

• ○

  Calculate summary values instead of Roll-Up by using triggers.

• ○

  Load all data using external IDs to link to parent records.
  
  
  

Select an option, then click Submit answer.

• ○

  Implement a Master Data Management system to determine system of record.

• ○

  Implement a workflow rule that sends Opportunity data through Outbound Messaging.

• ○

  Have the ERP poll Salesforce nightly and bring in the desired Opportunities.

• ○

  Implement an hourly integration to send Salesforce Opportunities to the ERP system.
  
  
  

Select an option, then click Submit answer.

• ○

  Master-detail relationship filed on Account, related to Inventory_c

• ○

  Master-detail relationship filed on Inventory_c, related to Account

• ○

  Indirect lookup relationship field on Account, related to Inventory_c

• ○

  Lookup relationship fields on Inventory related to Account
  
  
  

Select an option, then click Submit answer.

• ○

  Update the Opportunity page layout to mark these fields as required.

• ○

  Use a validation rule for each field that takes the Stage into consideration.

• ○

  Update these Opportunity field definitions in Setup to be required.

• ○

  Write an Apex trigger that checks each field when records are saved.
  
  
  

Select an option, then click Submit answer.

• ○

  Use Streaming API to get the current status from the ERP and display on the Opportunity page.

• ○

  Create an external object Invoice _x with a Lookup relationship with Opportunity.

• ○

  Create a custom object Invoice _c with a master -detail relationship with Opportunity.

• ○

  Create a custom object Invoice _c with a Lookup relationship with Opportunity.