SF-Data-Arch Salesforce Data Management Practice Test 5 — 15 Questions

Question 1

Universal Containers wants to ensure data quality by preventing the creation of duplicate Leads from various sources. The architect recommends matching rules and duplicate rules. Which action should the architect take to ensure that users are alerted to potential duplicates during manual entry while blocking automated integrations?

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

Accepted Answer

Set 'Report' for record creation and 'Block' for API insertion.. To achieve this, the architect must configure duplicate rules with distinct settings for user-based versus integration-based scenarios. By setting the 'Report' action for user-facing rules, the UI displays an alert, while selecting 'Block' for API-based rules prevents duplicates from being inserted via integration tools. This tiered approach maintains data integrity across different entry points without hindering necessary manual workflows during prospect record creation.

Answer

Enable 'Block' for both user-facing and integration-based duplicate rules.

Answer

Apply 'Report' to the record creation rule and ignore the API settings.

Answer

Use a third-party AppExchange solution exclusively for integration rules.

Question 2

An organization is consolidating multiple legacy systems into Salesforce. They need to track the lineage of data records back to their source systems for audit purposes. What is the recommended strategy for maintaining data lineage?

Accepted Answer

Create a custom field marked as an External ID to store legacy identifiers.. The recommended approach is to create a dedicated 'External ID' custom field on relevant objects to store the source system's unique identifier. This field should be marked as an External ID and indexed. This allows for easy upsert operations, prevents duplicates during ongoing synchronization, and provides a clear audit trail for compliance teams to trace records back to their original source systems during data lifecycle management.

Answer

Store the source system ID in the standard Name field.

Answer

Use the Salesforce ID as the source record identifier in legacy systems.

Answer

Append the source system name to the record's description field.

Question 3

Universal Containers has a custom object Invoice__c with 8 million records. Users report that list views and reports filtering on the Invoice_Status__c picklist field are slow. The field is not indexed. What should the data architect do to improve query performance?

Accepted Answer

Create a custom index on the Invoice_Status__c field.. Custom indexes are the standard mechanism to improve query performance on large custom objects when filtering on a custom field. Because Invoice_Status__c is not indexed, queries perform full table scans across 8 million records. Requesting a custom index on that field allows the database to quickly locate matching rows, improving list view and report responsiveness without altering the data model or field type.

Answer

Convert the picklist to a text field and enable indexing.

Answer

Enable the 'Allow Reports' setting on the field.

Answer

Create a formula field that returns the picklist value and filter on that instead.

Question 4

A Data Architect is designing a data retention policy for a custom object that stores transaction records. The object has a master-detail relationship to Account and contains over 50 million records. The business requires that records older than 7 years be automatically deleted, but they must be archived first for compliance. Which approach should the architect recommend?

Accepted Answer

Use a scheduled batch Apex job that exports records to an external system and then deletes them from Salesforce.. A scheduled batch Apex job is the most appropriate solution because it can automate the export of old records to an external archive and then delete them from Salesforce. Batch Apex is designed for processing large data volumes and can be scheduled to run regularly. This approach ensures compliance with the retention policy and offloads data to reduce storage costs.

Answer

Configure a time-based workflow rule to delete records after 7 years.

Answer

Create a formula field that flags records older than 7 years and use a sharing rule to hide them.

Answer

Use the Data Loader to manually export and delete records every quarter.

Question 5

A data architect is designing a data retention policy for a custom object Event_Log__c that stores 20 million records per year. The business requires that records older than 2 years be archived but still accessible for occasional reporting. What is the most appropriate approach?

Accepted Answer

Use Salesforce Big Objects to store archived records and query them via Async SOQL.. For high-volume, low-access data that must be retained and occasionally queried, Big Objects with Async SOQL provide a scalable, cost-effective archival solution. They allow storage of billions of records without impacting standard object performance. Deletion or moving to another custom object does not address the scale and accessibility requirements. Field history tracking is not a full archival mechanism.

Answer

Enable field history tracking on all fields and rely on it for archival.

Answer

Move records to a custom object with a lookup to the original record and use standard reports.

Answer

Create a scheduled batch job that deletes records older than 2 years.

Question 6

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 7

A Data Architect is designing a data governance strategy for a Salesforce org that integrates with multiple external systems. The architect needs to ensure data quality and consistency across systems. Which two practices should be implemented? (Choose two.)

Accepted Answer

Define a master data management (MDM) strategy to establish a single source of truth.. The two correct practices are defining an MDM strategy and implementing validation and duplicate rules. MDM establishes a single source of truth, while validation and duplicate rules enforce data quality at the point of entry. Together, they ensure data consistency and accuracy across integrated systems, which is essential for effective data governance.

Answer

Schedule nightly full data exports to a data warehouse for backup purposes.

Answer

Configure field-level security to restrict access to sensitive fields.

Answer

Use Salesforce Data Loader to manually reconcile data discrepancies on a weekly basis.

Question 8

Cloud Kicks is ingesting 20 million Account records nightly from an external ERP into Salesforce using the Bulk API 2.0. The ERP also updates existing records. During testing, the data architect observes that some records are duplicated because the external system's unique identifier is not enforced in Salesforce. Which solution should the architect implement to prevent duplicates during the nightly load?

Accepted Answer

Create a unique External ID field on Account and use the upsert operation with that field as the external ID.. An External ID field with the unique attribute allows Salesforce to reliably match incoming records to existing ones during an upsert. This prevents duplicates by updating matched records and inserting only new ones. Bulk API 2.0 supports upsert with an external ID, making it the most efficient and scalable solution for nightly loads of millions of records while maintaining data integrity.

Answer

Schedule a nightly batch Apex job that deletes duplicates after the load completes.

Answer

Enable duplicate rules with a matching rule on the ERP identifier field and set the action to Block.

Answer

Use a before-insert trigger to query for existing records and update them if found, otherwise insert.

Question 9

Universal Containers has a custom object Order__c with 10 million records. The object has a lookup relationship to Account. A data architect needs to create a report that shows the total order amount per account for the last fiscal year. The report must be accessible to 500 users and should load in under 10 seconds. Which solution should the architect recommend?

Accepted Answer

Create a custom object to store aggregated order totals per account, populate it nightly using Batch Apex, and build a report on that object.. Pre-aggregating data into a custom object via Batch Apex provides a performant and scalable solution for reporting on large data volumes. The report then queries a small, indexed dataset, ensuring fast load times for many users. This pattern is commonly recommended for large-scale aggregations that cannot be efficiently handled by standard reports or real-time queries.

Answer

Create a report using a custom report type with a cross filter on Order__c and summarize by Account.

Answer

Create a roll-up summary field on Account that sums Order__c amounts for the last fiscal year, and use it in a report.

Answer

Create a Lightning Web Component that queries Order__c using SOQL with GROUP BY Account and displays the results.

Question 10

A data architect is designing a data retention policy for a custom object Event_Log__c that stores 20 million records per year. The business requires that records older than two years be archived to an external system but remain accessible for audit purposes. What is the most appropriate approach to meet these requirements while minimizing storage costs?

Accepted Answer

Implement a scheduled batch process that exports records older than two years to an external data warehouse and then deletes them from Salesforce.. A data retention policy requires physically moving data out of Salesforce to reduce storage and cost. A scheduled batch export followed by deletion is a standard pattern for archiving large volumes. It ensures records older than the retention period are removed from Salesforce while remaining available externally for audit. This approach is scalable and can be automated, aligning with data management best practices.

Answer

Enable field history tracking on Event_Log__c to retain old values for two years.

Answer

Create a report filter to hide records older than two years from users.

Answer

Use Salesforce Big Objects to store all Event_Log__c records indefinitely.

Question 11

Universal Containers is implementing a data retention strategy for a custom object called Invoice__c that stores 120 million records. They need to archive records older than seven years to an external system while keeping the most recent records immediately accessible in Salesforce. Compliance requires that archived records remain queryable for audit purposes without impacting Salesforce performance. Which two Salesforce features should the architect recommend to meet these requirements? (Choose two.)

Accepted Answer

Big Objects with a custom index and asynchronous SOQL queries. Big Objects provide native, scalable storage for massive data volumes and support asynchronous queries, making them ideal for long-term archival within Salesforce. Salesforce Connect allows real-time access to external data without replication, so archived records remain queryable for audits. Together, they satisfy retention, performance, and compliance requirements without overloading the transactional object.

Answer

Standard Salesforce Recycle Bin retention policies

Answer

Field Audit Trail and Data Retention policies for standard objects

Answer

Salesforce Data Loader with a scheduled export to a local database

Question 12

Universal Containers is implementing a data governance framework. They need to ensure that data quality is maintained across multiple business units. Which two practices should the data architect recommend to enforce data quality at the point of entry? (Choose two.)

Accepted Answer

Implement duplicate rules to block or alert on duplicate records.. To enforce data quality at the point of entry, the architect should implement validation rules to reject invalid data and duplicate rules to prevent duplicates. These are proactive controls that operate when records are created or updated. They are standard Salesforce features that can be configured declaratively and apply across all entry points, including UI, API, and integrations, ensuring consistent data governance.

Answer

Enable field history tracking on all fields to audit changes.

Answer

Use Data Loader to perform a nightly update to correct inconsistencies.

Answer

Schedule a weekly report to identify records with missing values.

Question 13

A data architect needs to ensure that when a user updates a field on a custom object, a related record on another object is automatically updated to reflect the change. The architect wants to avoid writing code. Which declarative feature should be used?

Accepted Answer

Record-Triggered Flow with an Update Records element. Record-Triggered Flows are the declarative tool of choice for automating updates to related records. They can be configured to run before or after a record is saved, and they can update records on the same object or related objects. They support both master-detail and lookup relationships, and they do not require code. This makes them ideal for the scenario where a related record needs to be updated when a field changes.

Answer

Workflow Rule with a Field Update

Answer

Process Builder with an Update Records action

Answer

Apex Trigger with a future method

Question 14

Universal Containers wants to ensure that when a user updates a field on an Account record, the change is captured and stored for auditing purposes. The solution must be configurable without writing code and must retain field history for up to 18 months. What should a data architect implement?

Accepted Answer

Enable Field History Tracking on the Account object for the required fields.. Field History Tracking is the standard declarative feature for auditing field changes. It automatically records changes, retains them for up to 18 months, and requires no code. Other options either involve code, track the wrong type of activity, or do not store historical data, making them unsuitable for this requirement.

Answer

Configure a workflow rule to send an email notification on field change.

Answer

Create a trigger on the Account object to write changes to a custom object.

Answer

Use Salesforce Shield Event Monitoring to track field changes.

Question 15

A data architect at a healthcare company needs to ensure that only authorized users can view sensitive patient information stored in custom fields on the Patient__c object. The organization uses a role hierarchy and profiles. Which feature should the architect use to restrict access to these fields?

Accepted Answer

Field-level security. Field-level security is the correct feature to restrict access to sensitive fields based on profiles. It allows administrators to hide fields from users who should not see them, regardless of record access. This ensures compliance with privacy regulations by limiting field visibility to authorized personnel only.

Answer

Organization-wide defaults

Answer

Permission sets

Answer

Sharing rules