Free Salesforce Data Architect Practice Questions with Answers

Correct answer: B. Create a required Lookup relationship to each of the three parent records.

Required Lookup relationships enforce that each Shipment must reference all three parent records and prevent parent deletion if child records exist. Unlike Master-Detail, Lookup relationships allow separate sharing models for each object.

Correct answer: D. Create an account plan object with a lookup relationship to Account with validation rules to enforce the Account association.

Lookup relationships allow different accessibility requirements and separate sharing settings for Account Plan versus Account. Validation rules ensure each account plan must have an associated account.

Correct answer: D. Person Accounts.

Person Accounts combine account and contact fields into a single record, designed to store information about individual people. This is the standard feature for B2C retailers to model consumer accounts in Salesforce.

Correct answer: A and B. Acquire an AppExchange Lead de-duplication application. / Implement Salesforce Matching and Duplicate Rules.

AppExchange de-duplication apps provide advanced matching features like fuzzy matching and mass merge. Salesforce Matching and Duplicate Rules define identification criteria and alert/block actions during import, both providing effective duplicate prevention.

Correct answer: B and C. Review data quality reports and dashboards. / Install and run data quality analysis dashboard app.

Data quality reports and dashboards provide insights into completeness, accuracy, and consistency of data. The data quality analysis dashboard app (a free AppExchange app) can help analyze and improve data quality by identifying duplicate, incomplete, or inaccurate records.

Correct answer: A and C and E. Use hard delete in Bulk API to permanently delete records from Salesforce. / Identify records in objects that have not been modified or used in last 3 years. / Archive the records in enterprise data warehouse (EDW) before deleting from Salesforce.

Using hard delete in Bulk API is more efficient and scalable than Batch Apex or REST API. Identifying unused records determines what to archive. Archiving in EDW before deletion preserves compliance data.

Correct answer: A and B and C. They do not include soft-deleted records. / They avoid resource intensive joins. / Their tables are kept in sync with their source tables when the source tables are modified.

Skinny tables exclude soft-deleted records, reducing space. They avoid joins by storing frequently used multi-object fields in one table. They auto-sync with source tables, ensuring data consistency.

Correct answer: B and C. Use Metadata API to create big object. / Go to Big Object in setup and select new to create big object.

Metadata API enables programmatic creation of big objects. Big Object in setup provides declarative UI for creating big objects without code. DX and Object Manager do not support big object creation.

Correct answer: B. Import Account records first followed by order records after sorting orders by AccountID.

Importing accounts first, then sorting orders by AccountID groups child records by their parent, minimizing lock contention. This prevents multiple batches from concurrently updating the same parent record, reducing UNABLE_TO_LOCK_ROW errors.

Correct answer: B. Inserting 1 million orders distributed across a variety of accounts with potential lock exceptions.

Using Bulk API in serial mode is recommended when inserting large numbers of child records across multiple parent records, as it prevents lock contention that would occur in parallel mode. Serial processing handles the lock exceptions inherent in many-to-many distribution.

Correct answer: B. Use data classification metadata fields available in field definition.

Data classification metadata fields are built into Salesforce field definitions and allow administrators to classify sensitive data (PII, confidential, etc.) directly on standard and custom object fields, meeting GDPR compliance requirements.

Correct answer: D. Implement an MDM solution as the customer master with centralized integrations to ensure consistency across all systems.

MDM acts as the customer master with centralized integrations to other systems, avoiding data duplication and inconsistency. This is better than point-to-point integrations or one-time cleansing.