Vce Salesforce-Certified-Administrator Questions Latest

Creating a dashboard with the running user set as someone who can see all opportunities is a way to create an enterprise-wide dashboard of all open opportunities in the pipeline without changing any sharing settings. The running user determines what data is displayed on the dashboard based on their access level and permissions; if the running user can see all opportunities, then the dashboard will show all opportunities regardless of who views it. Updating the dashboard folder settings to manager for the sales reps role does not create an enterprise-wide dashboard; it only controls who can access the dashboard folder, not what data is displayed on the dashboard. Adding a filter to the dashboard to filter the opportunities by owner role does not create an enterprise-wide dashboard either; it only shows opportunities owned by users in certain roles, not all opportunities. Building individual dashboards for profiles that need to see the enterprise results is not a feasible solution; it would require creating multiple dashboards for different profiles and maintaining them separately, which is inefficient and redundant. References: &type=5

The contact hierarchy is a feature that allows users to view contacts related to an account in a hierarchical tree structure based on their role or position within the account. The contact hierarchy respects record-level access by user, meaning that users can see only those contacts that they have access to based on their profile permissions and sharing settings. The other options are incorrect because contact hierarchy is not limited to 3,000 contacts at one time (it can display up to 5,000 contacts), customizing hierarchy columns does not change the recently viewed contacts list view (it only affects how contacts are displayed in the hierarchy), and sharing settings are not ignored by contacts displayed in the contact hierarchy (they determine which contacts are visible to users). References: &type=5

Assignment rules are tools that allow administrators to automatically route records to users or queues based on certain criteria. For example, an assignment rule can assign cases to different queues based on case priority, origin, type, or other fields. Assignment rules can be triggered when records are created manually, via email, web, or API. Assignment rules consist of multiple rule entries that define the criteria and actions for each assignment scenario. References: &type=5 &type=5

To transfer data from a lead custom field to an opportunity field upon lead conversion, an administrator needs to create a custom field on the opportunity object that matches the data type and length of the lead custom field, and then map the two fields using the lead field mapping tool under setup. This will ensure that the value of the product category field on the lead is copied to the corresponding field on the opportunity when the lead is converted. References: &type=5