ADM-201 Salesforce Certified Platform Administrator (Plat-Admn-201) Question and Answers

An Approval Process is the dedicated Salesforce feature for managing workflows that require human " review and decision-making. " Unlike Assignment Rules (Option A), which simply change the owner of a record, an Approval Process locks the record to prevent further changes and routes a formal request to an " Approver. " This approver can then choose to Approve, Reject, or Reassign the request. The process can include multiple steps, entry criteria (e.g., " only if discount > 10% " ), and specific automated actions that occur once the final decision is made. Validation Rules (Option B) are used to prevent saving bad data, not for routing. Schema Builder (Option D) is a visualization tool for the data model. Therefore, when a business process requires an official " sign-off " or " decision, " the Approval Process engine is the correct architectural choice.

Case Escalation Rules are used in Service Cloud to ensure that cases are handled within specific timeframes, helping organizations meet their Service Level Agreements (SLAs) 23232323232323 . When a case meets the criteria defined in an escalation rule and remains unresolved for a specified period, the system can perform two primary automated actions:

Reassign the Case: The rule can automatically transfer ownership of the case to another user or a specific queue (e.g., a " Tier 2 Support " queue) to ensure it gets specialized attention 242424242424242424 .

Send Email Notifications: The system can send alerts to the new owner, the current owner, or up to five additional email addresses to notify management that a case has escalated .

While administrators often use other tools like Flow Builder to change the " Case Priority " (Option B) or " Reopen " a case (Option C), these are not standard features within the Escalation Rule interface26. Escalation rules focus specifically on the routing and notification aspects of case management to prevent tickets from " sitting " too long without a response .

To make a Screen Flow available to users on a specific record, such as a Case, the Platform Administrator should add the Flow component to the Lightning Record Page. Using the Lightning App Builder, the admin can drag the Flow component onto the page and select the specific " Service Question " flow from the list8888. This allows the flow to be embedded directly into the workspace where the service reps are already looking at case details9. While flows can be placed on a Home Page (Option B), that would not provide the case-specific context needed for the reps10. Page Layouts (Option A) are used for standard fields and related lists but do not natively host dynamic screen flow components11. Component Filters (Option D) are used to show or hide the flow based on certain criteria, but the distribution itself is handled by placing it on the Lightning Page12.

A common cause of errors in an Approval Process is a breakdown in the " Approver " chain. If an approval step is configured to route to a specific user or a manager who has been deactivated, Salesforce will throw an error when the current step tries to advance. The Platform Administrator should check the " Next Approver " field on the record or the step definition in Setup to ensure the target user is active and has a valid Salesforce license. While field visibility (Options B and C) is important for the user experience, missing field access typically doesn ' t " error out " the approval engine itself; it just prevents the user from seeing the data. Checking for inactive users is the first step in troubleshooting runtime errors in automated routing processes.

According to Agentforce best practices, action instructions must be highly specific regarding the action ' s purpose, the expected goal, and the conditions under which it should be triggered. Option D is the strongest set of instructions because it defines the Action (Update shipping address), the Goal (Modify address on a record), and a clear Constraint/Guardrail (Only use when the user explicitly requests it). This prevents the AI from accidentally triggering a data change based on a vague inquiry. Option B is also good but more restrictive than necessary unless the business logic specifically forbids updates during active orders. Option D provides the best balance of context and intent, ensuring the Large Language Model (LLM) understands the " why " and " when " of the action.

When a single object like Campaigns needs to support different " types " of marketing initiatives that require different fields or picklist values, the correct architectural solution is to use Record Types and Page Layouts. By creating distinct record types for " Email, " " Trade Show, " and " Webinar, " the Platform Administrator can assign a unique Page Layout to each. For example, the Trade Show layout might include fields for " Booth Number " and " Travel Costs, " while the Webinar layout might include " Webinar URL " and " Platform Provider. " This ensures that users only see the fields that are relevant to the specific type of campaign they are running, improving data quality and the user experience. While adding a custom field (Option B) would allow for categorization, it wouldn ' t hide irrelevant fields for different initiatives. Campaign Hierarchies (Option D) are used for relating parent and child campaigns but do not manage the specific data entry requirements for different initiative types.

Mobile Home is a customizable landing page for the Salesforce mobile app that acts as the default " start page " for users. It allows administrators to add various " cards " or " widgets, " including reports, pinned records, and upcoming events. By enabling and configuring Mobile Home, a Platform Administrator can place a specific Report card (such as " Top Opportunities " ) at the very top of the screen, ensuring it is the first thing users see upon opening the app. While adding the Reports tab (Option A) or Dashboards tab (Option D) allows users to find the information, it does not automatically present specific report data on the home screen. The " Today " feature (Option B) focuses on calendar events and tasks rather than customized reporting data 17 .

In this scenario, the two teams are " peers " in the role hierarchy (both reporting to the same manager). In a private sharing model, peers cannot see each other ' s records by default. To grant lateral access between these specific groups, an Owner-based Sharing Rule is the most effective solution. The administrator can create a rule stating that any records owned by members of " Role: Sales Team A " should be shared with members of " Role: Sales Team B " with specific access levels (e.g., Read/Write). Hierarchical sharing (Option C) only grants upward visibility to the Manager role, not across to the other team34. Manual sharing (Option D) is inefficient for an entire team35. Criteria-based sharing (Option A) is used when record field values determine access, whereas this requirement is based specifically on who owns the records36.

To ensure a consistent, weekly " check-in " occurs, the Platform Administrator should enable the creation of recurring tasks. This feature allows a sales rep to create a single task (e.g., " Monday Check-in " ) and set a recurring frequency of " Weekly " on " Mondays. " Salesforce then automatically generates the next task in the series once the current one is completed. This is the most effective way to provide reps with a constant reminder in their task list. Additionally, because these are standard Task records, the administrator can easily build a report and a dashboard component to track the completion status of these check-ins for the VP. Time-based workflow (Option A) is typically for one-off alerts based on a date field, not for a permanent weekly habit. Email actions (Option C) and alerts (Option D) notify users but do not create the trackable task record required for the dashboard component.

The administrator ' s goal is to gain a better understanding of current data quality and record completeness issues in Accounts and Opportunities. Creating reports (or dashboards) that highlight blank or missing key fields—using filters like " Field equals (blank) " or formula fields to flag incompleteness—directly assesses the existing data by showing which records lack required information.

Why B is correct : Salesforce Trailhead modules on data quality emphasize using reports and dashboards (e.g., Account, Contact & Opportunity Data Quality Dashboard) to identify missing fields and measure completeness before implementing fixes.

Why not the others :

A : Exploring AppExchange apps is useful for advanced or ongoing solutions but skips the initial assessment step.

C : Subscribing reps to reports helps with awareness but doesn ' t provide the admin with an overview of data quality.

D : Making fields required prevents future issues but doesn ' t reveal current missing data or outdated records.

This approach aligns with Salesforce best practices: assess data quality first through reporting, then enforce improvements.

To automate the update of related records (Opportunity Products) based on a change to a parent record (the Opportunity), Flow Builder is the most powerful and app7ropriate tool. Specifically, a " Record-Triggered Flow " can be configured to fire whenever an Opportunity is updated to the " Closed Won " stage. The flow can then use a " Get Records " element to find all Opportunity Product records associated with that specific Opportunity and an " Update Records " element to apply the discount value from the parent to each line item. Formula Fields are insufficient here because they are " read-only " and cannot physically push data into other records for permanent storage. Approval Processes manage status changes but are not designed for bulk child-record updates. Flow Builder provides the logic necessary to handle this " one-to-many " update scenario, significantly reducing manual data entry for sales reps and ensuring that the financial data on the products accurately reflects the agreed-upon deal terms.

In Flow Builder, the most efficient and user-friendly way to handle dynamic user interfaces is through Component Visibility. This feature allows an administrator to set logic on individual screen components (like a picklist) so they only appear when specific criteria are met. In this scenario, the administrator would select the " Specific Search Engine " picklist component within the Flow Screen and configure its visibility to show only when the " Lead Source " screen component equals " Search Engine. " This provides a " clean " user experience where the form adapts in real-time to the user ' s input without requiring the user to navigate to a new screen or trigger a validation error. Validation rules (Option D) are reactive and only tell the user they made a mistake after they try to save, whereas conditional visibility is proactive. Option B is inefficient as it would require multiple screens and complex branching logic, whereas component visibility handles everything within a single screen element.

The most efficient and descriptive way to troubleshoot a flow is to use the native Debug feature within the Flow Builder. This tool allows the Platform Administrator to " run " the flow in a safe environment, simulating the creation or update of a record. As the flow executes, the Debugger provides a step-by-step panel showing exactly how variables were assigned, which paths were taken in " Decision " elements, and whether any " Update " or " Create " elements failed. It explicitly highlights where an error occurred and provides a detailed error message. While general Debug Logs (Option D) can capture flow information, they are much harder to read and require setting specific trace flags. The Setup Audit Trail (Option A) only shows configuration changes, not runtime errors. Email logs (Option B) are only useful if the flow is failing to send an email. The Flow Debugger is the primary tool for administrators to refine logic and fix issues before activating automation.

The Company Information page in the Setup menu is the " source of truth " for an organization ' s high-level metadata and licensing. In the User Licenses related list on this page, the administrator can see every license type purchased (e.g., Salesforce, Salesforce Platform, Force.com), the total number of seats allocated, the number of seats currently in use, and the number of remaining available licenses. This is the first place an administrator should look for budgeting and capacity planning. " Usage-based entitlements " (Option A) tracks limited-resource features like Login minutes or Data Cloud credits, but not standard seat-based user licenses. Searching for license types (Option B) or checking user management settings (Option D) will not provide a consolidated summary of the total license pool.

Case Assignment Rules are the standard Salesforce tool for automatically routing cases to specific users or queues based on record criteria. A single assignment rule can contain multiple " Rule Entries " processed in a specific order. To meet this requirement, the Platform Administrator would create a rule with two entries: one that checks if the Account ' s " Level " field equals " Platinum " and routes it to the Priority Support Queue, and another that checks if the level is " Silver " or " Gold " and routes it to the Regular Support Queue. This automation happens the moment the case is created, ensuring that high-value customers receive immediate attention from the appropriate team. Escalation Rules (Option A) are used to move a case after it has been sitting for a period of time, not for initial routing. Workflow Rules (Option D) are a legacy tool that cannot natively assign cases to queues in the same direct manner as Assignment Rules.

2

When a Lead is converted into an Account, Contact, and Opportunity, standard fields are mapped automatically. However, custom fields require manual configuration to ensure d3ata flows through the conversion process. First, the Platform Administrator must create a corresponding custom picklist field on the Contact object (Option B) with the same values as the Lead field. Second, the administrator must go to the Lead Object Manager, select " Fields & Relationships, " and click Map Lead Fields (Option C). Here, the admin explicitly maps the Lead custom picklist to the newly created Contact custom picklist. Without this mapping, the data will be lost during conversion. Validation rules (Option A) and making the field required (Option D) ensure data exists on the Lead but do not facilitate the transfer of that data to the Contact.

In Salesforce, a flow must be Active for it to execute in a production environment. When an administrator builds or updates a flow, it is saved as a new version. Even if the logic is perfect and passes all debug tests, the flow will not run for end-users unless the administrator explicitly clicks the " Activate " button. If a flow is intended to create records but nothing is happening, the first troubleshooting step is always to verify the status in the Flow Builder or the Flows list in Setup. A flow version that is simply " Saved " but not " Active " will remain dormant. Option D is unlikely because the Flow Builder usually prevents saving a record-triggered flow without a trigger defined. Option C ( " Read Only " ) is not a state that would prevent a flow from running. Option B ( " Flow URL " ) only applies to specific types of screen flows launched via custom links, whereas the question implies a general failure of the automation to execute.

The Lightning App Builder includes a built-in Analysis tool (often referred to as Page Analysis or Analytics) that provides administrators with a performance score for a record page. This tool evaluates the page ' s metadata and components to identify factors that contribute to slow load times, such as having too many fields in a single section, using complex related lists, or including multiple heavy Lightning Web Components. It provides specific suggestions, such as using " Dynamic Forms " to break up the page or moving less-used components into separate tabs to improve the " time to interact " for the user. The Lightning Usage App (Option B) provides broad metrics on adoption and browser usage across the whole org but does not offer granular, component-level performance analysis for a single record page. Visibility Rules (Option C) are for showing/hiding content, not for technical performance auditing.

Effective Agentforce instructions must be explicit about the data format, the source of the data, and the requirements for the input. Option D is the best choice because it provides the most detail for the Large Language Model (LLM). It specifies the format (18 character ID / three-digit code), the source (conversation history or user input), and the logic/dependency (required only when the product ID is present). This level of detail prevents the agent from guessing or providing incomplete data to the underlying Salesforce action. Options A and C are too vague and could lead to errors. Option B is better but lacks the explicit " Required " tag and format details found in Option D. High-quality instructions act as a contract between the agent ' s natural language understanding and the structured data requirements of the Salesforce system.

Profiles in Salesforce serve as the foundation for what a user can " do " with records, specifically defining Object-Level Security (Create, Read, Edit, Delete permissions). The standard Marketing User profile typically does not include full " Edit " access to the Opportunity object by default, as marketing roles are traditionally focused on Leads and Campaigns. To fulfill the requirement of allowing marketers to maintain campaign relationships on Opportunities, the administrator must ensure the profile has the necessary object permissions. If the organization is using a custom profile based on the Marketing User template, the admin should edit the object permissions directly on that profile to include " Read " and " Edit " for Opportunities. This allows the marketers to view the records and update the " Primary Campaign Source " field. While a Permission Set could also grant this access, the question implies the admin is currently configuring the profile itself. Adjusting the profile ' s object permissions is the direct way to align the user ' s capabilities with the business ' s functional requirements.

A Dynamic Dashboard is a specific type of dashboard where the data displayed changes based on which user is currently viewing it. By setting the " View Dashboard As " property to " The logged-in user, " the dashboard components will respect each individual user ' s sharing settings, role hierarchy, and record ownership. For example, if a sales rep views a dynamic dashboard, they might only see their own $100k pipeline, while their manager viewing the same dashboard would see the team ' s combined $1M pipeline. This eliminates the need for an administrator to create and maintain dozens of identical dashboards for different individuals. Dashboard Filters (Option A) allow users to narrow down data but do not change the fundamental " running user " security context. Setting the dashboard to run as " Me " (the admin) or " Another person " (Options C and D) creates a static view where everyone sees the same data, which is the opposite of providing an individualized view.

To organize related marketing initiatives and simplify reporting, Salesforce utilizes Campaign Hierarchies. A hierarchy allows an administrator to link multiple campaigns together using the " Parent Campaign " field. In this scenario, the admin should create a " Parent " campaign to represent the entire networking series and then create individual " Child " campaigns for each monthly event. This structure provides two major benefits: it allows the sales rep to see the specific performance (ROI, members, responses) of a single monthly event, and it uses " Hierarchy Total " fields to automatically roll up all those metrics to the parent level. This provides a holistic view of the entire series ' success without requiring complex manual calculations. Using the same name for campaigns (Option A) leads to data confusion, and while member statuses (Option B) are useful, they do not provide the structural " series vs. month " reporting required here. Campaign Hierarchy is the standard architectural approach for multi-touch or recurring marketing efforts.

When an administrator needs to extract a specific subset of records (e.g., Opportunities filtered by stage and date) with specific fields, the Data Loader is the most appropriate tool . Data Loader is a client application that allows for bulk operations, including " Export " and " Export All " 43. It allows the administrator to write a SOQL (Salesforce Object Query Language) query or use the built-in query builder to apply filters, such as StageName = ' Closed Won ' and CloseDate = LAST_90_DAYS44. The Data Import Wizard (Option B) is primarily used for importing data and has very limited export capabilities, usually confined to simple CSV samples45454545. The Data Export Service (Option D), also known as " Weekly Export, " is designed for full backup purposes; it exports the entire database into zip files and does not allow for specific filtering of records or fields for a quick ad-hoc report . Data Cloud (Option C) is a large-scale data platform and is overkill for a simple file export task47. Thus, for targeted, field-specific exports of 90 days of data, Data Loader is the standard choice .

To manage different business requirements for a single object like Opportunities, Salesforce utilizes a combination of Record Types and Sales Processes. A Sales Process is a specific feature for the Opportunity object that allows an administrator to select which " Stage " picklist values are visible. In this scenario, the admin would create one Sales Process for " Business " (4 stages) and another for " Partner " (8 stages). Once these processes are defined, they are linked to Record Types. Record Types are the engine that allows different users to see different Page Layouts and picklist options based on the " type " of record they are creating. This architecture ensures that users working on Partner deals are guided through the appropriate eight stages and see the relevant fields on their layout, while Business users have a streamlined four-stage experience. This separation is critical for maintaining data integrity and ensuring that the reporting for each pipeline is accurate. It prevents confusion by only showing users the options that are relevant to the specific context of the deal they are managing.

When a report contains many rows where the same Account name appears multiple times (due to having several opportunities), a simple count of rows will not accurately represent the number of distinct accounts. To find the specific number of individual accounts, the Platform Administrator should use the Unique Count feature on the Account Name or Account ID column in the report builder. Selecting " Show Unique Count " provides a total at the bottom of the report (and in summary groupings) that counts each unique value only once, regardless of how many times it appears in the list. Bucket Columns (Option A) group data into categories46. Report Filters (Option B) exclude records47. Grouping Rows (Option D) visually organizes the report by Account but does not inherently provide a single summary number for the count of distinct accounts in the way that Unique Count does.

For an AI agent to provide " complete and accurate " support, it needs access to a unified, 360-degree view of the customer data. Data Cloud is the critical prerequisite because it ingests, harmonizes, and unifies data from multiple sources (Salesforce, external databases, legacy systems) into a single " Unified Profile. " When Agentforce is " grounded " in Data Cloud, it can reference real-time customer interactions, purchase history, and cross-channel behavior that might not exist in a single Case or Contact record. Without Data Cloud, the agent ' s knowledge is limited to siloed data, which increases the risk of providing incomplete or irrelevant answers. While Console layouts (Option B) and intake methods (Option A) are important for the UI, they do not provide the data foundation necessary for advanced AI reasoning.

In Salesforce, a dashboard’s running user determines which data is displayed to anyone viewing the dashboard. If a dashboard is configured with a " Static " running user (e.g., a Support Manager who has " View All " permissions), every user who views that dashboard will see the manager ' s level of data, regardless of their own personal sharing permissions. This bypasses the Organization-Wide Default (OWD) of " Private " for the Case object. When the support manager observes that reps can see all cases on a group dashboard, it is almost certainly because the dashboard is " running " as a user with high-level access. To correct this and ensure users only see data they are entitled to, the Platform Administrator should convert it into a Dynamic Dashboard. A dynamic dashboard is set to " Run as the logged-in user, " meaning the data reflected in the components will automatically filter based on the individual viewer ' s specific sharing rules and record ownership. This ensures that the dashboard remains a useful tool for the team while strictly adhering to the company ' s data privacy and security requirements.

Case Escalation Rules are the dedicated tool for time-based notifications and reassignments in Service Cloud. The Platform Administrator can set an escalation rule entry that triggers when a case is " Older than 2 hours " and meets specific status criteria (e.g., Status = New). The rule can then be configured to send an Email Notification to a manager or a specific distribution list. This ensures that management is alerted to potential SLA breaches. Assignment Rules (Option A) only run when a case is first created. Formula fields (Option C) can calculate time but cannot send notifications. Omni-Channel Supervisor (Option D) allows for real-time monitoring but does not provide automated email alerting based on specific time-elapsed thresholds.

Omni-Channel is a comprehensive service tool designed to route work items (like Cases, Leads, or custom objects) to the most available and qualified support agents in real-time. Unlike Case Assignment Rules, which are often static and require administrative intervention to update complex logic, Omni-Channel allows for more dynamic management through the use of Queues and Presence Statuses. By using Omni-Channel, a support manager or " Supervisor " can monitor agent workloads and adjust capacity or move people between service channels without needing to modify the underlying system configuration or involve the Platform Administrator. It supports various routing models, such as " Least Active " or " Most Available, " ensuring that work is distributed fairly and efficiently. This flexibility is vital for growing organizations that need to scale their support operations quickly while maintaining high service levels. Furthermore, it provides the business with the autonomy to manage its workforce effectively, as managers can see who is logged in and what they are working on, allowing for immediate adjustments to handle spikes in case volume.

Tasks and Events are both part of the Activity object, but they often require different picklist values for the standard Subject field. To achieve this, the Platform Administrator must manage the picklist values for the Subject field specifically for each record type or activity type. In the Object Manager, under the Activity object (or Task/Event objects individually in some setups), the admin should edit the Subject field. Because Task and Event are distinct entities with their own picklist value sets for the Subject field, the admin can add " Schedule Site Visit " and " Send Contract " to the Task Subject list and " Site Visit " and " Ride Along " to the Event Subject list. This ensures that when a user creates a Task, they only see task-related subjects, and when they create an Event, they see event-related subjects. Option D is incorrect because it would mix all values together, causing confusion for the users. Option A (Predefined Field Values) is used to set a single default value for a field when an action is clicked, but it does not manage the available list of options in a picklist.

When users click the " New Report " button, they are presented with a list of Report Types, which act as templates determining which objects and fields are available for the report. Often, an org has many standard report types that are irrelevant or confusing to the average user. To " limit the kinds of reports " and simplify the user experience, a Platform Administrator can use the Select Report Types to Hide feature in the Report and Dashboard Settings. By hiding unnecessary or redundant report types, the admin ensures that users only see the specific templates that align with company reporting standards. This reduces the risk of users creating inaccurate reports using the wrong data models. Report Folder Sharing (Option B) controls who can view or edit existing reports, but it does not restrict the creation of new ones from specific templates. While creating Custom Report Types is a way to define what data is available, the specific act of " limiting " the visible list is handled by the " Hide " functionality.

An Approval Process consists of several stages, each with its own set of automated actions. When a record is first submitted, it is typically locked to prevent further edits. If a user needs to " reverse " that submission—perhaps because they realized they made a mistake or the deal terms changed—the administrator must configure Recall Actions12. A recall action is specifically designed to allow the submitter or an administrator to pull the record back out of the approval queue. Common recall actions include a Field Update to change the status back to " Draft " and, most importantly, an action to unlock the record so it can be edited again. Final Rejection Actions (Option A) occur when an approver denies the request, and Final Approval Actions (Option C) occur when the request is fully granted. Initial Submission Actions (Option D) are what lock the record and start the process in the first place.

The requirement to have a record " signed off " by a specific individual (the CFO) based on a dollar threshold is a classic use case for an Approval Process . While the " Submit for Approval " button (Option A) allows a user to manually start the process, the prompt specifies that the process should happen " automatically " 50. To achieve this automation, the Platform Administrator should use Flow Builder to trigger the approval process . A Record-Triggered Flow can be set to run when an Opportunity is created or updated and meets the criteria (Amount > $100,000) . The flow would then use the " Submit for Approval " action to launch the record into the predefined approval process without requiring the sales rep to click a button . Einstein Next Best Action (Option B) is a recommendation tool, not a workflow enforcement tool54. Apex Triggers (Option C) could perform this task, but Salesforce best practices recommend using " clicks not code " (Flow) whenever possible for such requirements . Using Flow to launch an Approval Process provides the necessary automation, routing, and audit trail the CFO requires

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.

During the Lead Conversion process, Salesforce automatically transfers the history and interaction data associated with the Lead to the newly created Account, Contact, and Opportunity. This includes all activities, meaning both Open Activities (like upcoming tasks or events) and Activity History (like past emails or logged calls) are attached to the resulting records to maintain a complete customer timeline. Campaign history is also typically associated with the resulting Contact, but the question specifically asks about " related records " in a broader sense, and the transfer of all activities is a primary mechanical function of the conversion. Option A is incorrect because custom object records do not automatically move unless specific custom mapping or code is in place. Option B is incorrect because the system does not limit the transfer to only open activities.

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

In the Salesforce Lightning Experience, the fields displayed in the " header " of a record and on the cards in the Kanban view are controlled by the Compact Layout. Each object has a System Default compact layout, but a Platform Administrator can create custom ones to prioritize the most important information, such as " Account Name " and " Close Date. " By editing the primary compact layout for the Opportunity object, the admin directly controls which fields the sales team sees as they drag and drop deals through the Kanban stages. While Page Layouts (Option C) control the main record detail page and Kanban Settings (Option D) control which field is used for columns and summaries, the individual " card " content is always driven by the Compact Layout. This ensures that users can quickly gather key context without needing to open every individual record.

Agentforce is built to be dynamic, meaning it doesn ' t just follow a static script but rather " reasons " through a problem using an agentic loop. The feature that directly allows an agent to adapt its behavior and take specific, real-time steps based on customer input is Custom Actions 3 . When a customer provides information—such as a specific order number or a request to change an address—the agent identifies the user ' s intent and selects the most relevant action to execute 4 . These actions can be powered by Flows, Apex, or Prompt Templates, giving the agent the ability to interact with Salesforce data in real-time. While Data Cloud (Option A) provides the data foundation for grounding, it is the actions themselves that define the agent ' s behavioral capabilities 6 . Screen flows (Option C) provide a guided UI for humans, but custom actions are what allow the agent to function autonomously 7 . Tableau (Option D) is an analytics tool and does not drive real-time agent behavior 8 .

To help sales reps prioritize their pipeline and identify which deals are most likely to close, Einstein Opportunity Scoring is the most effective tool. Part of Salesforce ' s AI suite, Opportunity Scoring uses machine learning to analyze past won and lost opportunities to assign a score from 1 to 99 to every open deal. The score is accompanied by " Key Factors " —both positive and negative—that explain why the score was given (e.g., " The deal has progressed quickly through stages " or " The close date has been pushed three times " ). This allows reps to focus their time on high-scoring deals or take corrective action on deals with low scores. Einstein Lead Scoring (Option B) helps with the intake of new prospects but not with existing deals. Einstein Activity Capture (Option D) automates the logging of emails and events but does not provide prioritization logic. Einstein Search (Option A) improves search results but does not assist in deal management strategy.

The Mass Transfer Records tool is a built-in Salesforce feature designed specifically for the scenario of a person leaving the company or changing roles. It allows a Platform Administrator to select a " From " user and a " To " user and then choose specific record types to transfer, such as Accounts and Opportunities. A major advantage of this tool is that it gives the administrator the option to transfer related records (like open opportunities or cases) and keep existing teams (like Account Teams) intact during the move. While Data Loader (Option A) or Dataloader.io (Option B) could technically perform a bulk update of the " OwnerId " field, they require several steps, including exporting data, manipulating CSV files, and re-uploading. The Data Import Wizard (Option D) is primarily for creating or updating records from an external file and does not have a dedicated " transfer " function. Mass Transfer is the fastest and safest standard way to reassign ownership within the Setup menu.

When an administrator needs to perform a " cleanup " of existing data in bulk, a Schedule-triggered flow is the most efficient choice. This type of flow can be configured to run once (or on a recurring schedule) and process all Lead records that meet the " inconsistent " criteria (e.g., Lead Source equals ' Website ' or ' Online ' )46. The flow can then automatically update those records to the standard " Web " value. A Record-triggered flow (Option B) only works on records as they are being created or updated, so it would not fix historical data unless every record was manually touched Screen flows (Option D) require manual user interaction for each record. 53Segment-triggered flows (Option A) are used in Data Cloud marketing conte54xts rather than standard core record cleanup.

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.