Free Salesforce Plat-Admn-201 Exam Dumps July 2026

To 'undo' a mistaken import, the administrator must delete the incorrectly created records. Two standard tools facilitate this:

Mass Delete Records (Option D): This is a browser-based tool in Setup that allows administrators to delete up to 250 records at a time (standard) or use criteria to identify and remove larger sets of records. It is the quickest way for smaller mistakes.

Data Loader (Option B): For large-scale errors, the administrator can use the Success file generated during the original import (which contains the new record IDs) and perform a 'Delete' operation.

The Data Import Wizard (Option C) is for adding or updating data, but it does not have a 'Delete' function. Weekly Data Export (Option A) is a backup tool and cannot be used to remove existing data from the system.

For any business process that needs to run at a specific time interval (in this case, 'once a week'), a Scheduled flow is the standard tool. A scheduled flow allows the Platform Administrator to define a frequency (Daily, Weekly, or Once) and a start time57. The flow can then query all relevant Account records and perform the logic of counting open cases and updating the parent record autonomously58. Record-triggered flows (Option B) are inappropriate here because the count needs to happen on a schedule rather than being triggered by an individual record edit59. Autolaunched flows (Option C) must be called by another process, such as a button or Apex, and do not have their own timing mechanism60. 'Automation event triggered flow' (Option D) is not a standard type of flow used for recurring batch processing

Comprehensive and Detailed 150 to 200 words of Explanation From Salesforce Topics:

A master-detail relationship can be converted to a lookup relationship only when Salesforce dependency rules tied to the master-detail structure are removed first. The key blocker in this scenario is the presence of roll-up summary fields on the master object. Roll-up summary fields depend on a master-detail relationship because they aggregate values from child records to the parent. Once the relationship becomes a lookup, that roll-up behavior is no longer supported, so Salesforce prevents the conversion until those roll-up summary fields are deleted or otherwise replaced. This is why option B is the correct answer. The other options do not block the conversion in the same way. A lookup field can still contain values after conversion, and a required lookup can be configured separately. A junction object is used for many-to-many designs, but it is not required simply to change a master-detail relationship to lookup. Salesforce documentation consistently ties roll-up summary capability to master-detail relationships, which is the decisive rule here.

The Opportunity Sales Path (or simply Path) is a visual representation of the stages in a sales process. It is the best tool for this requirement because it not only shows the current stage prominently at the top of the record but also allows administrators to define Key Fields and Guidance for Success for every stage. This guidance can include specific steps, tips, and links to company resources that explain exactly what a rep needs to do to move the deal to the next phase. Reports (Option A), List Views (Option D), and Big Deal Alerts (Option C) provide data and notifications but do not offer the contextual, stage-by-stage guidance that the Path provides.

Agentforce is designed to handle sophisticated, multi-step business processes that traditionally require human intervention. In a sales organization, a primary use case is Automating Lead Qualification. Unlike basic web bots (Option C) that follow a rigid, pre-defined script, an Agentforce agent can engage in natural language conversations with prospects. It can ask relevant discovery questions, handle objections, and determine if a lead meets the company's 'Qualified' criteria based on the information provided. Once qualified, the agent can autonomously update the Salesforce record or even book a meeting for a human sales representative. While AI can assist with content, 'automating all marketing content' (Option B) is overly broad and typically handled by specialized marketing tools. Generating cold calls (Option A) involves voice technology and legal complexities that are not the core focus of the Agentforce platform's digital agent capabilities. Lead qualification represents a high-value, repeatable process that perfectly leverages the agent's ability to reason and interact with Salesforce data.

The Activity Timeline is a standard Lightning component that displays open tasks, upcoming events, and past activities (like logged calls or sent emails) in a chronological view. If this timeline is missing from an Account page, it is usually because the component has been removed from the Lightning Record Page layout. To fix this, the Platform Administrator should open the Account record in the Lightning App Builder. From the list of standard components on the left, the admin must drag the Activities component onto the page canvas---typically in the right-hand column or a dedicated tab. Once the page is saved and activated, the timeline will be visible to users. Visibility of the timeline is a layout configuration, not a specific 'Edit access' permission (Option B). Running a report (Option C) might confirm if data exists, but it won't fix the UI issue. There is no 'button' for the Activity Timeline in the Object Manager (Option D); it is managed strictly as a component within the App Builder.