Sharing the dashboard folder with roles and subordinates of the US Sales Director and sharing the report folder with the role of US Sales Director will ensure that only the US sales directors can see the data in the component and view its source report, while all US sales reps can view the US Team dashboard. Making the US Sales Director the running user will show only his or her data in the component, not the whole team's data. Making the dashboard dynamic will show different data depending on who is viewing it, not based on their role. Sharing the dashboard with the public group US Sales Reps and sharing the dashboard source reports folder with the US Sales Director profile will not prevent other profiles from accessing the reports if they have access to the report folder.

The best actions to take to avoid creating duplicate leads when uploading a list of 400 leads are to utilize a Lead Matching Rule and corresponding Duplicate Rule to block newly created duplicate leads, and to upload the lead list using the import wizard and select a Matching type to prevent duplicate lead creation. The Lead Matching Rule defines the criteria for identifying duplicate leads, and the Duplicate Rule defines the actions to take when a duplicate is detected. The import wizard allows users to choose a Matching type based on the Lead Matching Rule and block or allow duplicates. Using Data Loader's update function or enabling Duplicate Matching in the Data Management section will not prevent duplicate lead creation.

A custom action on Account can be used to create additional accounts from a parent account record. A custom action can have predefined values for certain fields based on the parent record. A custom global action can be used to create records that do not have any relationship with other objects. A custom link on Account can be used to execute JavaScript or link to an external URL.

The app builder should recommend a workflow rule to automate this process. A workflow rule is a type of automation tool that can execute actions based on certain criteria. In this case, the workflow rule can have a criterion that evaluates if the DoNotCall checkbox is checked on a Contact record, and then execute a field update action that sets the Phone field to null. Option A, B, and C are not automation tools that can perform this task.

The app builder needs to have NOT(ISBLANK([Lead].OwnerId)) in the criteria to ensure the process runs without error. This formula checks if the OwnerId field on the Lead object is not blank, which means that the lead is owned by a user or a queue. This will prevent the process from running on leads that are not owned by anyone, which could cause an error. Option A, B, and C are not formulas that can ensure the process runs without error.