Salesforce Business Analyst Certification Practice Exam

Which type of metadata changes must be tracked manually in the package development model?

1. All metadata changes need to be tracked.

2. Changes made through the Setup UI.

3. Components that do not support source tracking.

4. Only major release changes.

The correct answer is: Components that do not support source tracking.

In the context of Salesforce development and the package development model, components that do not support source tracking must be tracked manually because they lack built-in mechanisms to automatically record changes. This means that if any alterations are made to these components—such as page layouts, workflows, or certain standard objects—developers cannot rely on Salesforce's version control features to document these changes. Instead, they are required to keep a manual record of such adjustments to ensure that all updates are accounted for when deploying or maintaining the package. Other choices do not align with the specificity of manual tracking requirements. For instance, asserting that all metadata changes need to be tracked is overly broad, as many metadata changes can be tracked automatically in the context of source tracking capabilities. Changes made through the Setup UI may also fall under automatic tracking for certain components, thus not necessitating manual documentation. Lastly, stating only major release changes need tracking does not encompass the range of component updates that require manual intervention, as even minor changes in unsupported components also need to be logged. Thus, the focus on components that do not support source tracking accurately reflects the manual effort required.