SF-Data-Arch Practice Test 10 — 10 Questions

Question 1

A data architect needs to migrate 500,000 Account records from a legacy system into Salesforce. The legacy system uses a 15-digit alphanumeric string as the unique identifier. The architect must ensure that future updates can match existing Accounts without creating duplicates. Which field configuration should be used on the Account object to support this requirement?

Choose an answer to begin — your selection is scored in the full session.

Accepted Answer

Create a custom Text field of length 15 and make it an External ID.. To support upsert and prevent duplicates, the legacy identifier must be stored in a field marked as an External ID. A custom Text field of sufficient length, designated as External ID, allows the Data Loader or Bulk API to match existing records based on that field. This is the standard pattern for integrating external systems and maintaining data integrity.

Answer

Create a custom Text field of length 15 and use it as the Salesforce Record ID.

Answer

Use the standard Account Number field and set it as an External ID.

Answer

Create a custom Text field of length 15 and mark it as Unique.

Question 2

Universal Containers is building a Data Governance program for its Salesforce org. The governance lead wants a single authoritative reference that defines every custom object and field, its business definition, data owner, allowed values, and system of record. Which artifact should the architect recommend as the foundation?

Accepted Answer

A Data Dictionary maintained as a versioned document and published to all stakeholders. The requirement is one authoritative reference covering field definitions, ownership, allowed values, and system of record. A Data Dictionary is precisely that artifact and is the standard foundation for a Data Governance program. ERDs, audit retention policies, and migration mappings each serve narrower technical purposes and cannot substitute for a maintained catalog of business and technical metadata.

Answer

A Data Loader field-mapping spreadsheet used for the most recent migration

Answer

An Entity Relationship Diagram showing all object relationships and cardinalities

Answer

A Field Audit Trail retention policy configured on all custom objects

Question 3

A financial services company is migrating 5 million Account records from a legacy CRM to Salesforce. The legacy system has a field 'AnnualRevenue' stored as a string with currency symbols and commas (e.g., '$1,234,567.89'). The target Salesforce field is a Currency field with 2 decimal places. During a test load of 100,000 records using the Bulk API, the architect receives errors indicating 'Invalid currency format'. What is the most efficient way to resolve this before the full migration?

Accepted Answer

Pre-process the source data using an ETL tool or script to remove non-numeric characters and convert the string to a decimal number before loading.. The Bulk API rejects records with non-numeric characters in Currency fields. Pre-processing the source data to remove symbols and commas and convert to decimal is the most efficient solution. It ensures data conforms to Salesforce's expected format, preventing load errors and maintaining data integrity without compromising field types or requiring post-load fixes.

Answer

Modify the Salesforce field type to Text to accept the legacy format, then create a formula field to display the numeric value.

Answer

Use Data Loader's 'Transform' feature to strip currency symbols and commas before loading.

Answer

Load the data as-is and then use a scheduled Apex job to clean up the values after import.

Question 4

A data architect is implementing a data governance strategy for a Salesforce org with multiple business units. The requirement is to ensure that data stewards can define and enforce data quality rules centrally, and that users are alerted when they attempt to save records that violate these rules. Which feature should be used?

Accepted Answer

Validation Rules. Validation Rules are the standard Salesforce feature to enforce data quality at the point of record save. They can be defined centrally and apply to all users, ensuring consistent data governance. They alert users with custom error messages when rules are violated. Duplicate Rules are for duplicates only, Workflow Rules do not block saves, and the Data Quality Dashboard is not a real-time enforcement tool.

Answer

Workflow Rules

Answer

Lightning Data Quality Dashboard

Answer

Duplicate Rules

Question 5

A healthcare company needs to store patient consent records that must be retained for ten years and are rarely accessed after the first year. The records include sensitive data and must be queryable by compliance officers using standard reports. Which storage strategy should the architect recommend?

Accepted Answer

Create a Big Object to store consent records and use Async SOQL or a custom index to query them for compliance reporting.. Big Objects are the Salesforce-native option for retaining large volumes of rarely accessed data for long periods while keeping it queryable. They do not consume standard data storage and support indexes for compliance queries. Standard custom objects, external warehouses, and field history tracking cannot simultaneously satisfy long-term retention and native reporting requirements.

Answer

Archive consent records to an external data warehouse and delete them from Salesforce after one year.

Answer

Store all consent records as standard custom object records and rely on Salesforce's default data retention.

Answer

Store consent records in a custom object with field history tracking enabled and purge old records annually.

Question 6

Northern Trail Outfitters is preparing for a GDPR-driven data subject deletion request affecting a Contact and its related Cases, Email Messages, and custom child records. The architect must ensure the deletion is complete and evidenced. Which approach best satisfies the governance requirement?

Accepted Answer

Use the native Data Subject Request (DSR) tooling to locate, and then erase the individual's data across related objects, capturing the action for evidence. A GDPR erasure request spans every object holding the individual's data, and governance requires proof the action occurred. The native Data Subject Request tooling locates data across related objects, supports erasure, and records the activity, satisfying both completeness and evidence. Manual deletes, field nulling, and off-platform exports each leave residual data or create ungoverned copies.

Answer

Export the individual's data to a CSV, delete the Contact, and archive the CSV in a shared drive

Answer

Overwrite the Contact fields with null values using Data Loader and leave related records intact

Answer

Delete the Contact record and rely on the recycle bin to remove related records

Question 7

A data architect is migrating 30 million Opportunity records into Salesforce. The legacy system has a 'Close_Date__c' field that is a date, but some records have invalid dates such as '0000-00-00' or future dates beyond 2099. The Salesforce Opportunity Close Date field is a standard Date field. The architect must ensure the migration does not fail due to these invalid dates. Which approach should be used?

Accepted Answer

Load the invalid dates as NULL and log the affected records for manual review after the migration.. The architect should set invalid dates to NULL and log the affected records for post-migration review. Salesforce Date fields accept NULL values, so this prevents load failures. Logging allows for manual correction later, ensuring data quality without blocking the migration. This approach is scalable for 30 million records and maintains the integrity of the standard Close Date field.

Answer

Convert the invalid dates to a default date such as '1900-01-01' to maintain a non-null value.

Answer

Create a custom text field to store the original date string and load it alongside the standard Close Date field, leaving Close Date blank for invalid records.

Answer

Use the Data Loader's 'Allow Field Truncation' option to bypass date validation and load the invalid dates as-is.

Question 8

A data architect is migrating 500,000 records into a custom object that has a validation rule requiring the 'Status__c' field to be either 'Active' or 'Inactive'. The legacy data contains some records with a blank Status__c. The architect needs to ensure the migration succeeds without modifying the validation rule. What should be done?

Accepted Answer

Transform the legacy data by setting a default value of 'Inactive' for any records with a blank Status__c before loading.. The validation rule requires Status__c to be 'Active' or 'Inactive'. The most straightforward solution is to transform the legacy data by setting a default value of 'Inactive' for blank entries. This ensures all records pass validation without altering the validation rule or adding custom code. Data transformation during migration is a best practice to meet target system requirements and maintain data integrity.

Answer

Temporarily deactivate the validation rule during the data load, then reactivate it afterward.

Answer

Load the records with blank Status__c using the Data Loader's 'Bulk' mode, which bypasses validation rules.

Answer

Create a before insert trigger to set a default value for Status__c when it is blank.

Question 9

A Salesforce data architect at a global manufacturer is defining the master data domain for 'Customer'. The company has separate business units that each maintain their own customer records. The architect must ensure that a single, authoritative Customer record exists and is referenced by all transactional systems. Which approach best achieves this?

Accepted Answer

Define a master data domain with a golden record, survivorship rules, and a data stewardship process.. A master data domain is defined by a golden record, survivorship rules, and data stewardship. The golden record is the single authoritative version of a Customer, and survivorship rules determine which source system's data prevails when attributes conflict. Data stewardship ensures ongoing quality. This combination ensures all transactional systems reference the same authoritative Customer record, which is the goal.

Answer

Use Salesforce Connect to virtualize customer data from each business unit system in real time.

Answer

Create a single Account record type and enforce a unique external ID on the Account object.

Answer

Implement Salesforce Duplicate Management with matching rules and duplicate rules.

Question 10

A Salesforce org has a data governance policy that requires all new custom objects to have a description and a data owner assigned before deployment to production. The architect needs to enforce this policy automatically during the development lifecycle. Which approach should the architect take?

Accepted Answer

Use a Salesforce CLI plugin or a script in the CI/CD pipeline to check metadata for description and owner before deployment.. Enforcing metadata standards like requiring a description and data owner on custom objects requires checking metadata before deployment. A CI/CD pipeline with Salesforce CLI or scripts can automate these checks, preventing non-compliant metadata from being deployed. Validation rules, permission sets, and workflow rules operate on data or user access, not metadata, so they cannot enforce this policy.

Answer

Configure a permission set that only allows users to create custom objects if they include a description.

Answer

Create a validation rule on the custom object that requires the description field to be populated.

Answer

Set up a workflow rule that sends an email to the data governance team when a new custom object is created without a description.