Salesforce App Builder Practice Exam

What should you avoid doing in a production organization?

1. Creating reports.

2. Developing Apex triggers.

3. Changing custom settings.

4. Creating dashboards.

The correct answer is: Developing Apex triggers.

In a production organization, developing Apex triggers should be approached with caution due to the potential impact on system performance and operational stability. Apex triggers are pieces of code that execute before or after specific data manipulation language (DML) events occur on Salesforce records. Since triggers can modify data, run complex logic, and interact with multiple records, poorly written or untested triggers could affect data integrity, lead to failures in business processes, or even cause performance issues that affect all users in the organization. In a production environment, any changes to the system should be thoroughly tested in a sandbox or development environment beforehand and then deployed using proper change management practices. This includes conducting unit tests and ensuring that the triggers do not introduce unexpected behavior or system errors, which could disrupt ongoing operations. Given the high stakes of maintaining a smooth user experience and data reliability in a production setting, introducing new or modified triggers without adequate testing and validation can lead to significant issues. The other activities mentioned—creating reports, changing custom settings, and creating dashboards—are generally lower risk when conducted appropriately. For instance, reports and dashboards are primarily read-only and do not affect the underlying data unless they involve complex real-time calculations that could impact performance. Changes to custom settings can often be made safely and are