Courseiva

CCNA Salesforce Data Management Questions

43 questions · Salesforce Data Management · All types, answers revealed

Practice these questionsDomain overviewAll questions
1
MCQmedium

A Data Architect is tasked with cleaning up duplicate records in a large Salesforce organization. The duplicates have been identified across multiple objects. What is the most effective approach to maintain data integrity during this process?

A.Use Data Loader to export all records, delete them from Salesforce, and re-import unique records.
B.Delete records using a hard-delete command to ensure they are permanently removed.
C.Merge duplicate records using the native Salesforce Merge feature.
D.Update the records to a dummy state and hide them from all user profiles.
AnswerC

The native Merge feature is the safest way to consolidate duplicates. It automatically handles the reparenting of child records, such as Opportunities or Cases, to the master record. This prevents data loss and ensures that the history of interactions remains linked to the correct, surviving record in the system.

Why this answer

Using Duplicate Management rules alongside the Data Import Wizard or API-based deletion is the standard approach. By identifying duplicates through native features and merging them, the architect preserves related records (like child objects) that would otherwise be deleted during a manual record deletion. This ensures that the parent-child relationships remain intact, preventing data orphans and maintaining the overall integrity of the relational database structure.

Exam trap

Candidates frequently suggest manual deletion or custom Apex deletion scripts, forgetting that native Merge features are specifically designed to re-parent related records automatically, preserving critical relational data integrity.

Practice this question →
2
MCQeasy

Universal Containers is classifying their data based on sensitivity levels (e.g., Public, Internal, Confidential, Restricted). Which Salesforce feature allows them to record this classification directly on the field definition?

A.Field-Level Security (FLS) settings.
B.Shield Platform Encryption.
C.Custom Metadata Types.
D.Data Classification Metadata fields.
AnswerD

Data Classification metadata (Data Sensitivity Level, Compliance Categorization, etc.) is a native feature in Salesforce. It allows admins to tag fields with specific values, making it easy to run reports on what data is sensitive and ensuring the Org meets various privacy and auditing standards.

Why this answer

Salesforce provides built-in Data Classification fields for every custom and standard field. This allows organizations to track the Data Owner, Field Usage, Data Sensitivity, and Compliance Categorization directly in the metadata, which is essential for data governance and regulatory compliance reporting.

Exam trap

Candidates often confuse field-level security or custom picklist fields with native governance tools, failing to recognize dedicated metadata features built specifically for data classification.

Practice this question →
3
MCQeasy

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?

A.Configure a workflow rule to send an email notification on field change.
B.Create a trigger on the Account object to write changes to a custom object.
C.Enable Field History Tracking on the Account object for the required fields.
D.Use Salesforce Shield Event Monitoring to track field changes.
AnswerC

Field History Tracking is a declarative feature that automatically tracks changes to specified fields and retains history for up to 18 months (or 24 months in some editions). It requires no code and is ideal for auditing field changes. It stores old and new values, the user who made the change, and the timestamp, meeting the requirement for configurable auditing.

Why this answer

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.

Exam trap

The trap here is confusing event monitoring or triggers with field history tracking, but only Field History Tracking provides declarative, long-term field-level auditing.

Practice this question →
4
MCQmedium

A Data Architect needs to implement a field-level security strategy where PII is visible only to the 'HR' profile. However, other profiles need to run reports on the account data without seeing the PII. What is the correct way to handle this?

A.Create two separate objects and use a lookup relationship to link them.
B.Apply field-level security to the PII field for all profiles except HR.
C.Implement a custom Lightning component to mask the field data.
D.Use an Apex trigger to clear the field value if the user is not in the HR profile.
AnswerB

Field-level security allows for granular control over who can see specific data fields. By restricting the visibility for all profiles except HR, the system ensures that sensitive information is properly protected in the UI, API, and all report types, meeting the data privacy requirement simply and effectively.

Why this answer

Field-level security (FLS) is the primary method for controlling access to specific fields. By defining FLS for the HR profile and restricting access for others, the architect ensures data privacy. When users without access run reports, Salesforce automatically hides the field, preventing unauthorized viewing while allowing them to report on other non-sensitive data.

This approach is the native, secure way to manage field visibility without complex custom components or data splitting strategies.

Exam trap

Candidates often propose complex sharing rules or record-type splitting, failing to realize that Field-Level Security is the most direct and secure way to handle visibility for sensitive fields.

Practice this question →
5
MCQhard

Refer to the exhibit. An architect is reviewing an error log from a high-volume data load. Which pattern should be implemented to resolve this limit violation?

A.Increase the batch size in the data loader settings.
B.Implement the Bulk DML Pattern using collections.
C.Convert the trigger to an asynchronous future method.
D.Increase the Apex CPU time limit in the Setup menu.
AnswerB

Moving DML operations outside of loops is the fundamental requirement for Salesforce Apex development. By collecting records in a List and performing a single DML call, you stay within the 150 limit per transaction. This is a critical architectural pattern for ensuring scalable code during heavy data ingestion processes.

Why this answer

The error indicates that DML operations are occurring inside a loop, exceeding the Salesforce governor limit of 150 DML statements per transaction. To resolve this, developers must use the Bulk Pattern, which involves collecting records in a collection (List or Map) and performing a single DML operation outside of the loop. This ensures efficient resource usage and prevents transactions from failing during high-volume data processing scenarios.

Exam trap

Candidates look for asynchronous processing solutions like Queueable Apex, missing that the fundamental error is simply performing individual DML statements inside a loop rather than processing collections.

Practice this question →
6
MCQhard

A Data Architect is designing a strategy to manage 'soft-deleted' data in a Salesforce instance. The requirement is to maintain data for seven years, but only show active records in standard views. What is the most recommended approach?

A.Use the 'Archive' custom object to store all inactive records.
B.Use an 'Active' checkbox and filtered list views to hide inactive records.
C.Create a daily batch job that deletes records older than one year.
D.Change the sharing settings to 'Private' for all inactive records.
AnswerB

This approach is the standard Salesforce practice for managing record lifecycle without deleting data. By using a simple status flag, users see only what they need, while data remains in the main table for audit and reporting purposes. It maintains full relational integrity and keeps the data easily accessible for compliance.

Why this answer

Using a combination of a status field and optimized list views/reports provides a flexible, low-impact solution. By setting an 'IsActive' flag, data remains available for historical reporting and audits without cluttering the UI for operational users. This pattern is easily scalable and avoids the complexities of moving data to external systems or utilizing custom objects, while adhering to organizational data retention policies without compromising standard Salesforce object relationships.

Exam trap

Candidates often over-engineer by suggesting archiving to external databases or custom objects, ignoring that simple list view filtering on a boolean field is the most performant, native solution.

Practice this question →
7
MCQmedium

Which security feature should an architect use to restrict access to sensitive fields based on a user's role?

A.Organization-Wide Defaults (OWD).
B.Field-Level Security (FLS).
C.Sharing Rules.
D.Role Hierarchy.
AnswerB

Field-Level Security provides the precise control needed to restrict visibility to specific fields on an object based on a user's profile or permission set. It is the standard platform feature for ensuring that sensitive data is only accessed by users authorized to view it, maintaining robust security posture.

Why this answer

Field-Level Security (FLS) is the correct mechanism for controlling field access by profile or permission set. It ensures that users only see and interact with data relevant to their role. By applying FLS, architects can enforce strict data access policies, which is essential for compliance and maintaining the 'need-to-know' principle in complex, multi-departmental Salesforce environments where data privacy is paramount.

Exam trap

Candidates often confuse Field-Level Security with Page Layouts. While layouts hide fields from the UI, they do not restrict access at the API or report level, leading to potential data exposure.

Practice this question →
8
MCQmedium

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?

A.Create a custom index on the Invoice_Status__c field.
B.Convert the picklist to a text field and enable indexing.
C.Enable the 'Allow Reports' setting on the field.
D.Create a formula field that returns the picklist value and filter on that instead.
AnswerA

Salesforce allows a custom index on a custom field via the field definition, which can significantly improve query performance for filters and list views. For an 8 million record object, filtering on an unindexed picklist forces a full table scan, so adding a custom index is the appropriate optimization. This directly addresses the slow list views and reports without changing data model.

Why this answer

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.

Exam trap

The trap here is assuming that enabling a field for reports or converting its type will improve performance, when only an explicit custom index changes the query execution plan.

Practice this question →
9
MCQhard

A Salesforce architect is designing a data integration strategy to synchronize 5 million records daily from an external ERP system into Salesforce. The integration must handle upserts, minimize API calls, and avoid governor limits. The external system can provide data in CSV format and supports REST APIs. Which approach should the architect recommend?

A.Use the SOAP API with a batch size of 200 records per call.
B.Use the Streaming API to push records from the ERP system into Salesforce.
C.Use the REST API with composite requests to combine multiple records per call.
D.Use the Bulk API 2.0 with parallel processing and CSV data.
AnswerD

Bulk API 2.0 is designed for high-volume data loads and can process millions of records efficiently. It accepts CSV data, supports parallel processing to speed up ingestion, and automatically handles chunking and batching. It also supports upserts using external ID fields. This minimizes API calls because a single job can process large volumes, and it avoids governor limits by using asynchronous processing. This is the optimal solution for daily synchronization of 5 million records.

Why this answer

Bulk API 2.0 is specifically built for high-volume data operations, supporting CSV input and parallel processing. It minimizes API calls by handling large batches in a single job and is designed to avoid governor limits through asynchronous processing. SOAP and REST APIs are better for smaller, real-time integrations, and the Streaming API is for outbound messaging.

Therefore, Bulk API 2.0 is the correct choice for daily synchronization of millions of records.

Exam trap

The trap here is assuming that composite REST requests or SOAP batches can handle millions of records efficiently; in reality, only Bulk API is designed for such volume without hitting API limits.

Practice this question →
10
MCQmedium

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?

A.Create a unique External ID field on Account and use the upsert operation with that field as the external ID.
B.Schedule a nightly batch Apex job that deletes duplicates after the load completes.
C.Enable duplicate rules with a matching rule on the ERP identifier field and set the action to Block.
D.Use a before-insert trigger to query for existing records and update them if found, otherwise insert.
AnswerA

Using an External ID field marked as unique and performing an upsert allows Salesforce to match incoming records to existing ones based on the ERP's identifier. This prevents duplicates by updating existing records instead of inserting new ones when the external ID already exists. Bulk API 2.0 supports upsert with an external ID, making it the optimal solution for large-volume, recurring loads.

Why this answer

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.

Exam trap

The trap here is assuming that duplicate rules alone can prevent duplicates during bulk loads, but they are not designed for upsert matching and can cause failures instead of updates.

Practice this question →
11
MCQmedium

An organization needs to integrate Salesforce with a legacy system that does not support modern authentication. What is the most secure architectural approach?

A.Hardcode credentials in the Apex integration code.
B.Use a Middleware/Integration layer.
C.Disable TLS 1.2 in Salesforce settings.
D.Send data via unencrypted email attachments.
AnswerB

Middleware acts as a secure intermediary, handling modern auth protocols like OAuth for Salesforce while securely communicating with legacy systems. This separation ensures that Salesforce remains secure and the legacy system is protected, providing a manageable and audited path for data exchange between the two disparate environments.

Why this answer

Using an intermediate middleware or Integration Hub allows the architect to encapsulate the modern authentication requirements of Salesforce while providing a secure proxy for the legacy system. This prevents the need to downgrade security settings within Salesforce and keeps sensitive credentials secure. It is the professional standard for bridging modern cloud platforms with older on-premises systems while maintaining strict security and compliance standards.

Exam trap

Candidates frequently suggest lowering Salesforce security settings, such as enabling weak authentication protocols, to accommodate legacy systems, which is a major security violation in architectural design exams.

Practice this question →
12
MCQhard

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?

A.Create a report using a custom report type with a cross filter on Order__c and summarize by Account.
B.Create a roll-up summary field on Account that sums Order__c amounts for the last fiscal year, and use it in a report.
C.Create a Lightning Web Component that queries Order__c using SOQL with GROUP BY Account and displays the results.
D.Create a custom object to store aggregated order totals per account, populate it nightly using Batch Apex, and build a report on that object.
AnswerD

Pre-aggregating data into a custom object using Batch Apex ensures fast report performance because the report queries a small, indexed dataset. This approach scales well for many users and large data volumes. It also allows the aggregation logic to be customized for fiscal year calculations, meeting the performance and business requirements.

Why this answer

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.

Exam trap

The trap here is assuming that standard reporting features like cross filters or roll-up summaries can handle millions of records efficiently, but they often hit limits or require master-detail relationships.

Practice this question →
13
MCQhard

A company requires real-time reporting on millions of records. Which architecture enables this while minimizing impact on production database performance?

A.Import all data into custom Salesforce objects.
B.Use Salesforce Connect for virtualized access.
C.Copy all data into the Salesforce Big Object.
D.Use platform events to stream data records.
AnswerB

Salesforce Connect allows users to view external data in real-time without physically storing it in Salesforce. This offloads the data footprint to the external system, maintaining Salesforce performance and avoiding storage limits. It is an excellent architectural pattern for large datasets that need to be queried but not necessarily updated.

Why this answer

Salesforce Connect with External Objects is the ideal solution for large-scale data that shouldn't live directly inside Salesforce. It fetches data in real-time from external sources without consuming Salesforce storage or affecting local database performance. This pattern is critical for architects managing massive datasets, as it keeps the core Salesforce CRM instance light and performant while still providing users with seamless access to historical or external financial data.

Exam trap

Candidates often suggest custom code or batch processing to move historical data into Salesforce, ignoring the performance impact on local storage and the efficiency of virtualized external data access.

Practice this question →
14
MCQhard

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?

A.Workflow Rules
B.Lightning Data Quality Dashboard
C.Validation Rules
D.Duplicate Rules
AnswerC

Validation Rules allow administrators to define data quality criteria that are enforced when a user saves a record. They can display error messages to alert users of violations. They are centrally managed and apply to all users, making them ideal for enforcing data governance rules across business units. They directly meet the requirement of alerting users upon save.

Why this answer

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.

Exam trap

The trap here is assuming that any automation tool like Workflow Rules can enforce data quality, when only Validation Rules can block saves and alert users at the point of entry.

Practice this question →
15
MCQmedium

When designing a large-scale data architecture, what is the primary consideration regarding the 'Skinny Table' feature in Salesforce?

A.They automatically update whenever a record is modified by a user.
B.They are best used to improve write performance for high-volume transactions.
C.They should be requested through Salesforce Support for specific performance needs.
D.They allow for unlimited columns and data types in the table structure.
AnswerC

Skinny tables are not configurable by administrators in the UI. They must be requested via a support case. This process ensures that Salesforce engineering can evaluate the impact on the database and ensure the table is optimized correctly for the specific reporting requirements of the organization's data model.

Why this answer

Skinny tables are used to optimize read-only performance for reports and list views by denormalizing data into a single table. They are highly effective for performance, but they are maintenance-intensive because they require Salesforce Support to enable and update. They are not a general-purpose solution for transactional data; rather, they are a performance-tuning tool meant for specific, high-volume reporting needs that cannot be satisfied by standard indexes alone.

Exam trap

Candidates mistakenly believe they can create 'Skinny Tables' themselves in the setup menu, failing to realize this feature is hidden and requires a specific request to Salesforce Support.

Practice this question →
16
MCQmedium

Universal Containers needs to provide a Full Sandbox for testing, but they must ensure that sensitive customer data like Social Security Numbers and Credit Card details are not visible to developers. Which solution is most appropriate?

A.Use a Partial Copy Sandbox and exclude the sensitive objects.
B.Implement Salesforce Data Mask to anonymize data during refresh.
C.Encrypt the fields in Production using Shield Platform Encryption.
D.Write a post-copy Apex script to delete sensitive field values.
AnswerB

Salesforce Data Mask is a powerful tool that automatically replaces sensitive information with random characters or mapped values during the sandbox creation or refresh. This allows developers to work with realistic data structures and volumes without being exposed to actual sensitive customer information.

Why this answer

Data Masking is a specific security process used to anonymize or pseudonymize sensitive data when it is copied from a production environment to a sandbox. Salesforce Data Mask allows administrators to mask sensitive data automatically during the sandbox refresh process, ensuring compliance with privacy regulations.

Exam trap

Candidates mistakenly suggest manual data scrubbing or writing custom Apex scripts to anonymize data after a sandbox refresh, ignoring automated platform native features.

Practice this question →
17
MCQmedium

A company is migrating 50 million records into Salesforce. They need to ensure data integrity while minimizing API consumption. Which strategy is most efficient for a one-time bulk data load?

A.Use the standard REST API with single-record inserts.
B.Utilize the SOAP API with synchronous processing.
C.Use the Bulk API 2.0 with CSV files.
D.Perform a manual data import via the UI.
AnswerC

Bulk API 2.0 is purpose-built for high-volume data movement, handling large batches asynchronously to maintain system stability. It provides significant performance gains by allowing Salesforce to manage job batching internally. This minimizes the risk of hitting governor limits and ensures successful large-scale data migrations for enterprise environments.

Why this answer

Bulk API 2.0 is the recommended approach for large datasets as it optimizes throughput by automatically breaking large jobs into smaller batches. It significantly reduces the number of API calls required compared to standard REST or SOAP APIs. Properly architecting for data loads involves choosing tools that leverage Bulk API 2.0 to maintain governor limits and ensure successful processing of high-volume data without impacting real-time integrations.

Exam trap

Candidates often choose standard REST or SOAP APIs for large migrations, forgetting that they consume thousands of individual API calls and hit governor limits quickly on high-volume datasets.

Practice this question →
18
MCQhard

A bank requires a full audit trail of all record changes for compliance. What is the most effective way to track changes to sensitive fields?

A.Enable standard Field History Tracking.
B.Create a custom 'Audit' object with triggers.
C.Use Field Audit Trail (Shield).
D.Schedule daily exports of all records.
AnswerC

Field Audit Trail provides the deep, long-term history tracking required for compliance. It supports up to 10 years of data and allows for tracking a significantly higher number of fields than standard history tracking. It is the architecturally correct choice for meeting stringent regulatory data retention and audit requirements.

Why this answer

Field Audit Trail is the most reliable way to meet regulatory compliance requirements for tracking data history. Unlike standard Field History Tracking, which is limited in retention and volume, Field Audit Trail allows for long-term retention and higher storage limits. This is essential for highly regulated industries like banking, where historical data accuracy and a permanent audit trail are mandatory for legal and security compliance.

Exam trap

Candidates select standard Field History Tracking, forgetting that it has strict retention limits and maximum tracked field constraints unsuitable for strict banking compliance.

Practice this question →
19
MCQmedium

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?

A.Enable 'Block' for both user-facing and integration-based duplicate rules.
B.Apply 'Report' to the record creation rule and ignore the API settings.
C.Set 'Report' for record creation and 'Block' for API insertion.
D.Use a third-party AppExchange solution exclusively for integration rules.
AnswerC

This configuration directly maps to the requirements. The 'Report' action allows users to proceed after an alert, facilitating manual data entry, while the 'Block' action on the API ensures that automated integration processes cannot bypass duplicate prevention, effectively maintaining high data quality across all system interaction types.

Why this answer

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.

Exam trap

Candidates often think duplicate rules apply globally, failing to recognize that they can configure different actions for manual UI entry versus automated API integrations within the same rule.

Practice this question →
20
MCQeasy

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?

A.Workflow Rule with a Field Update
B.Record-Triggered Flow with an Update Records element
C.Process Builder with an Update Records action
D.Apex Trigger with a future method
AnswerB

Record-Triggered Flows are the modern declarative automation tool in Salesforce. They can be triggered when a record is created or updated, and they can update related records regardless of whether the relationship is master-detail or lookup. This meets the requirement without code. Flows are more powerful and flexible than Workflow Rules or Process Builder, and they are the recommended approach for new automation.

Why this answer

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.

Exam trap

The trap here is assuming that Workflow Rules or Process Builder are still the primary declarative automation tools, when Flow is now the strategic direction.

Practice this question →
21
MCQmedium

A Data Architect is designing a disaster recovery plan. Which data elements must be explicitly backed up outside of Salesforce to ensure business continuity?

A.Standard Account and Contact records, as they are managed by Salesforce.
B.System Metadata, Custom Settings, and complex relational data.
C.Chatter posts and historical activity logs for all users.
D.All temporary batch job execution logs.
AnswerB

Metadata and custom settings are the 'brain' of the Salesforce organization. If these are lost or corrupted, the system's custom logic and configuration cease to function. Backing them up externally is critical because they represent the effort of years of development and are not easily restorable from standard platform backups.

Why this answer

While Salesforce provides high availability, it does not provide a point-in-time restore for individual records or deleted data if the retention period has passed. Metadata, custom settings, and high-value transactional data must be exported and stored off-platform. This strategy ensures that if a catastrophic deletion occurs or if there is a need to revert to a specific state, the organization can reconstruct its configuration and data without relying solely on the platform's standard capabilities.

Exam trap

Candidates assume Salesforce's standard backup capabilities cover everything, failing to realize that metadata and specific configuration elements (like Custom Settings) require dedicated, external backup strategies for full recovery.

Practice this question →
22
MCQhard

Refer to the exhibit. An architect is using the Salesforce CLI to perform a high-volume data upsert. What is the significance of the '-i Legacy_ID__c' parameter in this command?

A.It specifies the internal Salesforce ID field for the upsert.
B.It indicates the field that should be used as the primary index for PK Chunking.
C.It defines the custom External ID field used to match existing records.
D.It tells the CLI to ignore all records that have a null value in that field.
AnswerC

The '-i' flag (or --externalid) tells the Bulk API which field to use for matching the incoming data against existing Salesforce records. If a match is found based on this field, the record is updated; if no match is found, a new record is created.

Why this answer

When performing an upsert operation via the Bulk API (or CLI), the system needs a way to determine if a record already exists or if a new one should be created. The '-i' parameter specifies the External ID field that the system will use as the unique key for this matching process.

Exam trap

Candidates confuse the '-i' parameter with setting a primary key or auto-number generation, forgetting its primary purpose is matching existing records during an upsert operation.

Practice this question →
23
Multi-Selecthard

When evaluating external data integration, which THREE architectural patterns should a Data Architect consider to minimize the impact on Salesforce governor limits?

Select 3 answers
A.Use Salesforce Connect to access external data without importing it.
B.Perform all data transformations using Apex inside the Salesforce transaction.
C.Utilize Middleware to process and aggregate data before sending it to Salesforce.
D.Design for asynchronous processing using Platform Events or Queueable Apex.
E.Increase the batch size limit by contacting Salesforce Support.
AnswersA, C, D

Salesforce Connect allows the system to query external data as if it were natively stored in Salesforce, without actually importing or storing the records. This keeps the Salesforce storage footprint small and avoids hitting governor limits associated with record counts, as the data is retrieved on-demand from the remote source.

Why this answer

To keep Salesforce performant, architects must offload heavy processing. Integrating with an middleware, using asynchronous patterns, and leveraging external objects (Salesforce Connect) are all strategies to avoid hitting governor limits. These methods decouple the heavy lifting from the Salesforce transaction, allowing the platform to remain responsive while the external system handles the data processing, aggregation, or long-term storage, keeping the overall architecture lean and within prescribed operational constraints.

Exam trap

Candidates often suggest synchronous batching or bulk imports as a way to save limits, ignoring that these still consume transactional resources rather than offloading them via asynchronous patterns.

Practice this question →
24
MCQmedium

Refer to the exhibit. An integration user is encountering record locking errors during high-volume data updates. What is the most effective technical solution to resolve this contention?

A.Increase the number of threads in the integration to process records faster.
B.Group records by parent ID before processing to ensure serialization.
C.Change the record ownership to a generic user account to avoid user locks.
D.Disable the 'User Audit' tracking on the affected object.
AnswerB

Sorting or grouping records by parent ID ensures that all child records associated with a specific parent are handled in the same batch. This approach minimizes the number of competing processes that need to lock the same parent record, significantly reducing the likelihood of encountering row-locking errors during processing.

Why this answer

Record locking in Salesforce often occurs when multiple processes or threads attempt to update the same parent record or records with common children. To resolve this, the integration process should be serialized or partitioned to group related records together. By ensuring that transactions affecting the same parent record are processed sequentially in the same thread, the architecture prevents the 'Unable to lock row' errors, enhancing overall stability and throughput.

Exam trap

Candidates mistakenly suggest increasing batch sizes or running parallel threads to speed up updates, which actually exacerbates record locking contention on parent records.

Practice this question →
25
MCQmedium

Refer to the exhibit. An architect is reviewing a JSON configuration for a data load into a Big Object. Which statement correctly describes a requirement for successfully loading data into this specific object type?

A.The Bulk API 2.0 must be used as it is the only API supporting Big Objects.
B.All fields defined in the Big Object's index must be present in the CSV.
C.Triggers on the Big Object will execute for each record inserted.
D.The operation must be set to 'upsert' to avoid duplicate index entries.
AnswerB

Big Objects require a custom index to function, and this index is what defines the uniqueness of a record. During an insert operation, every field that makes up that index must be provided in the data source to ensure the record can be correctly placed and retrieved from storage.

Why this answer

Big Objects are designed for massive data storage but have unique requirements compared to standard objects. When inserting data into a Big Object, the CSV file must include all fields that are defined in the Big Object's custom index. This index is required for querying and uniquely identifying records within the Big Object store.

Exam trap

Candidates often assume Big Objects behave like standard objects and can be updated partially. They fail to realize that Big Objects have rigid index requirements for data insertion.

Practice this question →
26
Multi-Selectmedium

A healthcare company must retain patient interaction records for 10 years for regulatory compliance. However, records older than 2 years are rarely accessed and are causing performance issues in the live Org. Which TWO strategies should an architect recommend?

Select 2 answers
A.Archive records older than 2 years into a Big Object.
B.Use a Skinny Table to store records older than 2 years.
C.Off-load data to an external data warehouse and use Salesforce Connect for access.
D.Implement a nightly batch job to delete records older than 2 years.
E.Move historical records to a separate 'Archive' custom object within Salesforce.
AnswersA, C

Big Objects are ideal for archiving large volumes of historical data that must remain accessible within Salesforce. By moving older patient interactions to a Big Object, the company reduces the size of the standard object tables, which improves query performance and reduces overall storage costs.

Why this answer

Managing Large Data Volumes (LDV) requires moving infrequently accessed data out of the primary transactional tables. Moving data to Big Objects keeps it within the Salesforce ecosystem at a lower cost, while off-platform archiving to a data warehouse provides maximum performance and long-term storage flexibility.

Exam trap

Candidates incorrectly suggest archiving historical data using standard custom objects or standard reporting snapshots, which still consume primary Salesforce storage limits and degrade live performance.

Practice this question →
27
MCQeasy

Which tool should an architect select to perform a one-time migration of complex, relational data while maintaining parent-child relationships?

A.Data Import Wizard.
B.Salesforce Data Loader.
C.Salesforce Inspector Chrome extension.
D.Change Sets.
AnswerB

Data Loader is the robust industry standard for handling large, complex data imports and exports. It supports relational mapping, allowing architects to preserve parent-child hierarchies during migration. Its logging and error handling capabilities are essential for auditing and ensuring that data is correctly inserted into the Salesforce environment.

Why this answer

Salesforce Data Loader is the standard tool for managing complex data migrations. Its ability to map CSV files to objects and maintain relationships via External IDs or record IDs makes it the primary choice for data architects. Using a mature, supported tool minimizes errors during migration and ensures that data integrity is preserved across relational structures, which is critical for successful implementation projects and long-term data reliability.

Exam trap

Candidates choose API-based custom scripts or third-party middleware for simple one-time relational loads, overlooking the built-in capabilities of native data loading tools.

Practice this question →
28
MCQhard

Refer to the exhibit. What is the primary benefit of configuring a field with these settings for data integration?

A.It enables faster reporting on the Account object.
B.It allows for deduplication in the UI.
C.It enables efficient Upsert operations.
D.It increases the maximum number of records.
AnswerC

The Upsert operation relies on External IDs to identify if a record exists. By making the field unique and an External ID, the system can determine whether to create a new record or update an existing one. This is the foundation of efficient, idempotent data synchronization in enterprise integrations.

Why this answer

The configuration allows the field to serve as a key for 'Upsert' operations. By marking the field as an External ID and unique, Salesforce can automatically match records from an external system to existing Salesforce records. This prevents duplicates and allows for automated, incremental data updates without needing to know the internal Salesforce record ID, which is critical for robust, scalable integration architectures.

Exam trap

Candidates assume the unique External ID configuration is merely for reporting or display purposes, overlooking its core integration function for record matching.

Practice this question →
29
MCQmedium

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?

A.Store the source system ID in the standard Name field.
B.Create a custom field marked as an External ID to store legacy identifiers.
C.Use the Salesforce ID as the source record identifier in legacy systems.
D.Append the source system name to the record's description field.
AnswerB

External ID fields are specifically designed for data integration and lineage. Marking them as an index ensures fast queries when upserting records. This satisfies the requirement to maintain a persistent link between Salesforce and legacy systems, which is essential for ongoing data governance and audit reporting requirements.

Why this answer

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.

Exam trap

Test-takers often choose standard name fields or formula fields for data lineage, ignoring the need for indexing and unique upsert capabilities provided by External IDs.

Practice this question →
30
MCQhard

A financial services firm needs to load 20 million records into an object with a complex sharing model involving many Sharing Rules and Role Hierarchy levels. To minimize the time taken for the data load and avoid performance degradation, which feature should the architect utilize?

A.Granting 'Ignore Hierarchy' permissions to the integration user profile.
B.Utilizing the 'Granular Locking' feature to allow concurrent sharing updates.
C.Utilizing 'Deferred Sharing Maintenance' to pause sharing rule recalculations.
D.Setting the Organization-Wide Defaults (OWD) to Public Read/Write for the load.
AnswerC

Deferred Sharing Maintenance allows administrators to suspend the automatic recalculation of sharing rules. This is essential for large data volumes because it prevents the system from performing redundant calculations after every batch, allowing the admin to trigger a single comprehensive recalculation after the total data load is finished.

Why this answer

Loading massive datasets into objects with complex sharing logic triggers significant overhead as Salesforce recalculates sharing access for every record. Deferring sharing calculations allows the data load to proceed without immediate recalculation, which is then performed in a single, optimized background process once the load is complete, saving hours of processing time.

Exam trap

Candidates often attempt to load data without adjusting sharing settings, leading to 'lock contention' as Salesforce tries to recalculate sharing rules for every single record during the load.

Practice this question →
31
Multi-Selecthard

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.)

Select 2 answers
A.Schedule nightly full data exports to a data warehouse for backup purposes.
B.Configure field-level security to restrict access to sensitive fields.
C.Define a master data management (MDM) strategy to establish a single source of truth.
D.Use Salesforce Data Loader to manually reconcile data discrepancies on a weekly basis.
E.Implement validation rules and duplicate rules to enforce data quality at the point of entry.
AnswersC, E

An MDM strategy ensures that critical data entities have a single, authoritative source. It defines data ownership, stewardship, and synchronization rules. This reduces data duplication and inconsistency across systems. By implementing MDM, the architect can enforce data quality and consistency, which is essential for integrated environments.

Why this answer

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.

Exam trap

The trap here is thinking that manual reconciliation or data exports are sufficient for data governance, but they do not prevent data quality issues at the source.

Practice this question →
32
MCQmedium

A company is experiencing slow performance on reports that join multiple objects with millions of records. What architectural change should the Data Architect propose first to improve report performance?

A.Switch to an external reporting tool like Tableau or Power BI.
B.Request custom indexes for the fields used in report filters.
C.Force all users to use the Reporting Snapshot feature instead of live reports.
D.Convert all report types to be 'Joined Reports' to reduce data loads.
AnswerB

Custom indexes significantly speed up database queries by allowing the query optimizer to quickly find records matching filter criteria. This is the recommended first step when standard reports slow down due to large data volumes, as it directly addresses the inefficiency of full table scans during the reporting process.

Why this answer

Indexing is the most fundamental way to improve database performance for filtering and joining large datasets. In Salesforce, ensuring that fields used in report filters and custom indexes are properly configured is the first step. If standard indexing is insufficient, the architect may consider custom indexes or denormalizing the data model.

This approach is far less intrusive and more cost-effective than re-architecting the entire data model or moving data to an external warehouse.

Exam trap

Candidates often jump to complex solutions like data warehousing or changing the data model, ignoring that simple custom indexing on report filter fields is the most effective initial step.

Practice this question →
33
MCQhard

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?

A.Enable field history tracking on all fields and rely on it for archival.
B.Move records to a custom object with a lookup to the original record and use standard reports.
C.Create a scheduled batch job that deletes records older than 2 years.
D.Use Salesforce Big Objects to store archived records and query them via Async SOQL.
AnswerD

Big Objects are designed for massive data volumes and provide cost-effective storage with asynchronous query capabilities via Async SOQL. They allow the organization to retain records beyond the standard object limits while keeping them accessible for occasional reporting. This approach aligns with data archiving best practices for high-volume, low-access data.

Why this answer

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.

Exam trap

The trap here is assuming that deleting or moving records to another standard object solves archival needs, when only Big Objects provide the scale and query capability required for massive historical data.

Practice this question →
34
MCQhard

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?

A.Configure a time-based workflow rule to delete records after 7 years.
B.Create a formula field that flags records older than 7 years and use a sharing rule to hide them.
C.Use a scheduled batch Apex job that exports records to an external system and then deletes them from Salesforce.
D.Use the Data Loader to manually export and delete records every quarter.
AnswerC

A scheduled batch Apex job can query records older than 7 years, export them to an external archive via callouts or middleware, and then delete them. This meets the archiving and deletion requirements. It is a scalable solution for large data volumes and can be scheduled to run during off-peak hours.

Why this answer

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.

Exam trap

The trap here is thinking that declarative tools like workflow rules can delete records, but they cannot perform deletions.

Practice this question →
35
MCQeasy

Universal Containers needs to access real-time order data stored in an external legacy ERP system within Salesforce without storing the data locally. Which Salesforce feature is most appropriate for this data management requirement?

A.Bulk API 2.0 with a scheduled middleware sync.
B.Change Data Capture (CDC) to monitor ERP updates.
C.Apex Callouts to a REST endpoint on the ERP.
D.Salesforce Connect using an OData adapter.
AnswerD

Salesforce Connect is the ideal solution for real-time access to external data without replication. By using the OData adapter, the external ERP data appears as External Objects in Salesforce, allowing for seamless integration into the UI and reporting while the data remains in the legacy system.

Why this answer

Salesforce Connect allows for the integration of external data sources via OData or custom adapters, exposing external data as External Objects. This allows users to view and interact with the data in real-time within Salesforce without the storage costs or synchronization issues associated with physically importing the data.

Exam trap

Candidates mistakenly suggest custom batch integrations or ETL tools to copy external data locally, missing the core requirement that the data must be accessed in real-time without local storage.

Practice this question →
36
MCQmedium

Universal Containers is importing 5 million child records into a custom object using the Bulk API in parallel mode. The load frequently fails due to UNABLE_TO_LOCK_ROW errors because many child records share the same parent account. Which strategy should the architect recommend to resolve this failure?

A.Sort the CSV file by ParentId and process the data load in serial mode.
B.Disable all triggers and validation rules on the child object during the import.
C.Increase the batch size to 10,000 records per batch in the Bulk API settings.
D.Enable PK Chunking to split the data load into smaller, manageable pieces.
AnswerA

Sorting the CSV by ParentId and switching to serial mode effectively eliminates lock contention. While serial mode is slower than parallel, it prevents the failures caused by concurrent batches trying to update the same parent record, ensuring that the entire multi-million record data load completes successfully without manual intervention.

Why this answer

Bulk API parallel processing often triggers lock contention when multiple batches attempt to update different child records that roll up to the same parent record simultaneously. By organizing the CSV file such that records with the same parent are grouped together and then processing the load in serial mode, the system ensures that only one batch accesses a parent at a time.

Exam trap

Candidates often try to increase batch sizes to speed up loads, which actually exacerbates row-locking issues when many records share the same parent account ID.

Practice this question →
37
Multi-Selectmedium

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.)

Select 2 answers
A.Enable field history tracking on all fields to audit changes.
B.Use Data Loader to perform a nightly update to correct inconsistencies.
C.Schedule a weekly report to identify records with missing values.
D.Implement duplicate rules to block or alert on duplicate records.
E.Define validation rules on critical fields to prevent invalid data from being saved.
AnswersD, E

Duplicate rules help maintain data quality by identifying potential duplicate records during creation or editing. They can be configured to block saves or allow with an alert, depending on business requirements. This prevents duplicate data from entering the system, which is essential for a single source of truth and data governance across business units.

Why this answer

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.

Exam trap

The trap here is choosing reactive measures like reports or nightly corrections instead of proactive point-of-entry controls.

Practice this question →
38
MCQmedium

Universal Containers uses a Big Object named 'Log__b' to store audit trails. They need to generate a report that aggregates this data weekly for compliance. Standard SOQL queries are failing due to the volume of records. What should the architect recommend?

A.Use a Skinny Table on the Big Object to improve query performance.
B.Use CRM Analytics (formerly Tableau CRM) to ingest and aggregate the data.
C.Create a Summary Report in Salesforce and schedule it for weekly delivery.
D.Write an Apex batch job to query the Big Object using the 'GROUP BY' clause.
AnswerB

CRM Analytics is designed to handle and aggregate massive datasets that exceed standard Salesforce limits. It can ingest data from Big Objects and perform complex aggregations and visualizations, making it the preferred architectural choice for reporting on high-volume audit logs or historical data.

Why this answer

Big Objects are optimized for massive scale but do not support standard SOQL features like aggregate functions or complex filtering over large sets. Async SOQL was the historical solution, but it has been retired. The modern recommendation is to use CRM Analytics or external reporting tools to process Big Object data.

Exam trap

Candidates often suggest using standard SOQL or Async SOQL, forgetting that Async SOQL has been retired and standard SOQL cannot perform aggregations on massive Big Object datasets.

Practice this question →
39
MCQmedium

An enterprise organization is experiencing frequent data skew issues on the Account object, leading to severe record locking and performance degradation during parallel batch updates. What is the primary architectural cause of Account data skew in Salesforce?

A.Having more than 10,000 custom fields defined across multiple page layouts within the Account object schema.
B.Assigning more than 50 active workflow rules that evaluate every record modification synchronously.
C.Associating over 10,000 child records, such as Contacts or Cases, with a single parent Account record in the database.
D.Utilizing person accounts alongside standard business accounts in a high-volume multi-region Salesforce implementation.
AnswerC

Exceeding 10,000 child records linked to one parent record creates severe account data skew. Salesforce locks the parent record during child updates, creating contention bottlenecks when multiple asynchronous threads attempt to modify associated children simultaneously.

Why this answer

Data skew occurs when an exceptionally high volume of child records are associated with a single parent record. During DML operations, Salesforce locks the parent record to maintain referential integrity, blocking concurrent threads attempting to update related children and causing transaction timeouts.

Exam trap

Candidates often confuse data skew with 'ownership skew.' While both cause performance issues, data skew specifically refers to the concentration of child records under a single parent.

Practice this question →
40
Multi-Selecthard

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.)

Select 2 answers
A.Big Objects with a custom index and asynchronous SOQL queries
B.Salesforce Connect to expose external archived data via an external object
C.Standard Salesforce Recycle Bin retention policies
D.Field Audit Trail and Data Retention policies for standard objects
E.Salesforce Data Loader with a scheduled export to a local database
AnswersA, B

Big Objects are designed to store massive data volumes on the Salesforce platform and can be queried asynchronously using SOQL with the ASYNC keyword. By defining a custom index on the timestamp and other filter fields, the architect can archive older Invoice__c records into a Big Object, keeping them queryable for audit purposes without affecting the performance of the transactional object. This meets both retention and queryability requirements while staying within Salesforce.

Why this answer

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.

Exam trap

The trap here is assuming that standard backup or export utilities like Data Loader can serve as a compliant, queryable archive without impacting performance or requiring external infrastructure.

Practice this question →
41
Multi-Selecthard

When designing a master data management (MDM) strategy for Salesforce, which THREE factors are critical to preventing duplicate data across the enterprise? (Select THREE)

Select 3 answers
A.Implementing standard and custom Matching Rules.
B.Enforcing data entry through API-only integrations.
C.Establishing a Unique Identifier (External ID) strategy.
D.Deploying a centralized Data Governance policy.
E.Regularly increasing the Data Storage capacity.
AnswersA, C, D

Matching rules are essential for identifying potential duplicates during record creation. By defining specific criteria based on business logic, Salesforce can flag or block duplicates automatically, ensuring that records remain unique and that the database integrity is maintained across different user input sources and automated integration processes.

Why this answer

Effective MDM strategies require a combination of automated matching rules, robust integration standards, and consistent data governance. These factors ensure that data entered through various channels is normalized and deduped at the point of entry. By implementing these controls, organizations maintain a single source of truth, improve data quality, and reduce the operational costs associated with manual data cleansing and conflicting records within their Salesforce environment.

Exam trap

Candidates focus exclusively on technical deduplication rules while forgetting that enterprise master data management requires broader governance policies and unique identifiers.

Practice this question →
42
MCQhard

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?

A.Implement a scheduled batch process that exports records older than two years to an external data warehouse and then deletes them from Salesforce.
B.Enable field history tracking on Event_Log__c to retain old values for two years.
C.Create a report filter to hide records older than two years from users.
D.Use Salesforce Big Objects to store all Event_Log__c records indefinitely.
AnswerA

This approach aligns with a data retention policy: it moves old records to a cost-effective external system, deletes them from Salesforce to free storage, and maintains audit accessibility via the external system. A scheduled batch job can handle large volumes efficiently using the Bulk API or Batch Apex. It is the most appropriate way to meet the two-year retention requirement while minimizing storage costs.

Why this answer

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.

Exam trap

The trap here is confusing data visibility with data archival; hiding records via reports or field history does not remove them from storage.

Practice this question →
43
MCQeasy

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?

A.Organization-wide defaults
B.Permission sets
C.Field-level security
D.Sharing rules
AnswerC

Field-level security (FLS) allows administrators to control which profiles can view or edit specific fields. By setting the sensitive fields to hidden for unauthorized profiles, the architect ensures that only authorized users can see the patient information. FLS is the standard mechanism for field-level access control in Salesforce and works in conjunction with page layouts and permission sets.

Why this answer

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.

Exam trap

The trap here is confusing record-level security features like organization-wide defaults and sharing rules with field-level security, which is specifically designed to control field visibility.

Practice this question →

Ready to test yourself?

Try a timed practice session using only Salesforce Data Management questions.

Start 20-question session