Free Practice Questions for Salesforce Plat-Admn-301 Exam

The Delete permission is missing on the user for Accounts is what is preventing the user from completing the merge. Merging accounts is a way to combine up to three duplicate accounts into one master record and update the related records accordingly. Merging accounts requires the Delete permission on accounts because merging accounts involves deleting the duplicate records and keeping only the master record.

The Setup Audit Trail is a tool that allows you to view and download a log of changes made in your org’s Setup area. The log shows up to 20 fields of information for each change, such as who made it, when it was made, what type of change it was, and what values were changed. You can use the Setup Audit Trail to track configuration changes directly in production and identify any unauthorized or problematic changes. One of the changes that the Setup Audit Trail tracks is when a user grants login access to another user. This means that you can use the Setup Audit Trail to see if any other administrators or delegated administrators are using the Log In As a User feature. References: https://help.salesforce.com/s/articleView?id=sf.monitorsetup.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.remoteaccess_granting_login_access.htm &type=5

Chat must be routed with Omni-Channel in Lightning Experience because Omni-Channel is the only way to route chats to agents in Lightning Experience1. Chat can only be added to Console navigation Lightning apps because Chat is a console app feature and requires a console app with a console navigation style2. References: 1 https://help.salesforce.com/s/articleView?id=sf.live_agent_chat_omnichannel.htm &type=5 2 https://help.salesforce.com/s/articleView?id=sf.live_agent_chat_app.htm &type=5

Delegated Administration is a feature that allows administrators to delegate some administrative tasks to other users without giving them full access to Setup. Delegated administrators can manage users and assign permissions for specific custom objects, tabs, apps, and fields. This can help reduce the workload of the system administrator and empower power users to make configuration changes to a specific custom object

Dynamic actions are actions that appear on Lightning record pages based on criteria such as field values or user profiles. Dynamic actions allow administrators to customize which actions are available for users on different record types or page layouts without creating multiple page layouts for each scenario. By using dynamic actions and conditional visibility for accounts at AW Computing, administrators can show only relevant actions for customer service and sales users based on their situation. References: https://help.salesforce.com/s/articleView?id=sf.dynamic_actions_overview.htm &type=5

Lightning Object Creator is a tool that allows you to create custom objects and fields from a spreadsheet in a few clicks. Lightning Object Creator analyzes the spreadsheet data and suggests the best way to map it to Salesforce fields and relationships. You can also import the data from the spreadsheet into the new custom object and view it in a list view or a related list. In this case, you can use Lightning Object Creator to create a custom Project object from the spreadsheet that tracks installations and also import the data into the new object. References: https://help.salesforce.com/s/articleView?id=sf.object_creator_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.object_creator_create_object.htm &type=5

Time-based workflows are a type of workflow that execute actions based on a specific time trigger, such as a certain number of days before or after a date field on a record. Time-based workflows can cause delays in processing because they are added to a queue and processed in one-hour batches. If the queue is large or the system is busy, the actions may not execute at the exact time they are scheduled. Therefore, time-based workflows can contribute to reaching the hourly limit for processing workflow time triggers. References: https://help.salesforce.com/s/articleView? id=sf.workflow_time_action_considerations.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.workflow_limits.htm &type=5

Knowledge is a feature that allows administrators to create, manage, and share articles that provide information and solutions for common issues or questions. Knowledge articles can be searched by users using keywords or phrases.

To improve its customers’ ability to search for knowledge articles, UMS can use two options:

B) Create synonyms for specific search terms.

Synonyms are words or phrases that have the same or similar meanings, such as “TV” and “television” or “fix” and “repair”. By creating synonyms for specific search terms, administrators can ensure that customers can find relevant articles even if they use different words or spellings than the ones used in the articles. References: https://help.salesforce.com/s/articleView?id=sf.knowledge_search_synonyms.htm &type=5

D) Promote specific search terms for specific articles.

Promoted search terms are keywords or phrases that administrators can associate with specific articles to boost their relevance and ranking in search results. By promoting specific search terms for specific articles, administrators can ensure that customers can find the most helpful or popular articles for their queries. References: https://help.salesforce.com/s/articleView?id=sf.knowledge_search_promotion.htm &type=5

A dashboard is a visual display of key metrics and trends for records in your org. Dashboards allow users to quickly monitor performance and identify trends or issues at a glance. To make it easier for users to see a dashboard they use frequently, administrators can add it to their home page using Lightning App Builder. This way, users can see their dashboard every time they log in or go to their home tab without having to navigate elsewhere. References: https://help.salesforce.com/s/articleView?id=sf.dashboards_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.dashboards_add_to_home_page.htm &type=5

A sandbox is a copy of a production org that can be used for development, testing, or training purposes. Sandboxes allow administrators to make changes and test them without affecting the live production org. A shared sandbox is a type of sandbox that can be used by multiple users or teams to collaborate on development or testing projects. By testing changes in a shared sandbox, the AW Computing administrator team can avoid conflicts and errors when deploying changes to production. References: https://help.salesforce.com/s/articleView?id=sf.data_sandbox.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.data_sandbox_environments.htm &type=5