SF-Data-Arch Data Migration Practice Question
During a large data migration, a developer notices that existing Apex triggers are causing severe performance degradation. What is the most effective way to prevent trigger execution without deleting the code?
⚠ Common exam trap
Candidates often select architectural solutions like permanently deleting or rewriting trigger logic, failing to recognize that configuration-based bypass mechanisms using custom settings are much safer and more efficient.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use a Custom Setting to control trigger execution.
The most effective method to mitigate trigger-related performance issues during high-volume loads is to implement a 'Bypass' or 'Switch' pattern using Custom Settings or Custom Metadata. By checking this flag at the start of the trigger, logic can be conditionally skipped. This preserves code integrity while allowing the migration to proceed at maximum speed without the overhead of complex validation or automated process logic.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Comment out the trigger logic and redeploy the code.
Why it's wrong here
Commenting out code is a risky, manual process that is prone to deployment errors and requires multiple deployments to enable and disable. It is not considered a professional practice, as it disrupts the development lifecycle and lacks the agility of a configuration-based toggle approach.
- ✗
Disable the triggers in the Setup menu under 'Manage Triggers'.
Why it's wrong here
Salesforce does not provide a global 'Manage Triggers' interface to disable Apex code. Triggers are compiled into the organization and always execute unless handled programmatically within the code using custom settings or metadata to bypass the execution logic during high-volume data operations.
- ✓
Use a Custom Setting to control trigger execution.
Why this is correct
A Custom Setting (or Custom Metadata) provides a clean, highly performant way to toggle Apex execution logic. This allows developers to disable resource-intensive triggers temporarily for the duration of the data load and reactivate them immediately afterward without needing a full code deployment cycle.
- ✗
Remove user permissions for the integration user.
Why it's wrong here
Removing permissions is an ineffective and imprecise way to stop trigger logic, as triggers run in system mode. Removing field access may cause the migration to fail entirely, and it does not stop the underlying Apex processing, which continues to execute as long as the record meets conditions.
About these practice questions
Courseiva writes every SF-Data-Arch question from scratch — 222 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Salesforce exam blueprint
This SF-Data-Arch practice question is part of Courseiva's free Salesforce certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SF-Data-Arch exam.