Free Plat-Admn-301 Practice Test Questions and Answers (2026)

A permission set is the standard and most appropriate tool for granting additional permissions to specific users without changing their base profile. The administrator should create a permission set that grants "Read" object permission for Leads and the "View All" system permission for the Lead object. Assigning this permission set to the contractor will grant the required access to all lead records while leaving their existing profile and app access intact. This adheres to the principle of least privilege and is a scalable solution.

B. Adding an app or tab only controls visibility in the user interface; it does not grant the underlying object permissions or record access required.

C. A public group is a collection of users for sharing purposes; it does not grant permissions itself. It is used as a target for sharing rules.

D. Creating a new profile is inefficient. A user can only have one profile, and changing it could remove their necessary access to the project management app.

1. Salesforce Help, Permission Sets. "A permission set is a collection of settings and permissions that give users access to various tools and functions. Use a permission set to grant additional permissions to users without changing their profiles."

2. Salesforce Help, Object Permissions. This document lists "View All" as a specific object permission that can be enabled in a profile or permission set to grant a user read access to all records of that object, regardless of sharing settings.

The best practice for declaratively controlling Apex logic execution for specific users is to use a custom permission. The Apex trigger code would be written to check if the running user has this specific custom permission before executing its logic. An administrator can then create a permission set that includes this custom permission and assign it to the required users or profiles. This approach allows for flexible, declarative control without modifying the Apex code.

A. Process Automation Settings are org-wide configurations, such as setting a default workflow user, not for controlling trigger execution for specific users.

B. While a standard system permission could be checked, a custom permission is the correct, scalable, and purpose-built solution for custom application logic.

C. Apex Class Access controls whether a user can invoke methods from a class (e.g., via a custom button), not whether a trigger fires during their DML operations.

1. Salesforce Developer Documentation, Apex Developer Guide. "Custom Permissions". The guide states, "Custom permissions let you define access checks that can be assigned to users via permission sets or profiles... For example, you can define access logic in Apex that makes a button on a Visualforce page available only if a user has the appropriate custom permission." This principle applies directly to controlling trigger logic.

2. Trailhead, Salesforce Developer. "Apex Triggers" module, "Trigger Context Variables" unit. This module explains that triggers run in system context, but best practices often involve checking the running user's permissions for conditional execution.

3. Salesforce Help. "Custom Permissions". "You can use custom permissions to provide a way for administrators to grant access to custom processes or apps declaratively."

Flows deployed with change sets are inactive by default and need to be manually activated in the

destination org before they can run. Deploying or redeploying a flow with change sets creates a new

version of the flow in the destination org, which preserves the previous versions and allows for

rollback if needed. All flow dependencies, such as custom fields, objects, or variables, are

automatically added to the change set when a flow is added

Roll-up Summary field calculations occur after record-triggered flows, processes, and workflows in Salesforce's order of execution. When a new appointment record is created, the Flow will fire immediately upon record creation, but at that moment, the Roll-up Summary field on the parent record hasn't been updated yet. This means the Flow would send outdated appointment count information to the agent unless specifically designed to account for this timing issue.

A. Roll-up Summary fields work with both standard and custom objects when master-detail relationships exist.

B. Flows can be triggered from both standard and custom object records without restriction.

C. Roll-up Summary calculations do not prevent Flows from being triggered; they execute in sequence.

1. Salesforce Developer Documentation: "Triggers and Order of Execution" - Section on System Validations and Roll-up Summary calculations

2. Salesforce Help: "Considerations for Time-Dependent Actions and Triggers" - Process automation timing

3. Salesforce Architect Documentation: "Platform Events and Process Automation" - Execution order details

4. Salesforce Administrator Guide: "Roll-up Summary Fields" - Chapter on calculation timing

5. Salesforce Developer Guide: "Flow Builder" - Record-triggered flow execution context

Field-Level Security (FLS) controls whether a user can see, edit, and delete the value for a particular field on an object. This is managed through Profiles and Permission Sets. The administrator should configure the sales reps' profile to have 'Visible' access to the 'Profit' field and the partner consultants' profile to have 'Hidden' access. Alternatively, a permission set granting visibility to the field could be created and assigned only to the sales reps, providing a more granular and additive approach to permissions.

B. Record types control page layouts and picklist values. Hiding a field on a page layout does not prevent access via reports or the API.

C. Organization-Wide Defaults (OWDs) control record-level access (which records a user can see), not field-level access (which fields they can see).

1. Salesforce Help. (2024). Set Field-Level Security for a Single Field on All Profiles. "Field-level security settings let you restrict what fields users can view and edit based on their profile."

2. Salesforce Help. (2024). Permission Sets. "You can also use permission sets to grant access to... field-level security."

3. Trailhead. (2024). Data Security Module, Control Access to Fields Unit. "You can control the visibility of fields in any part of the app, including... reports... You can set field-level security through profiles or permission sets."

Roll-up summary fields have specific characteristics. They must be created on the master object in a master-detail relationship to aggregate data from detail records (B). Furthermore, the existence of a roll-up summary field on the master object creates a dependency that prevents the master-detail relationship from being converted to a lookup relationship until the field is deleted (C). These are fundamental considerations for data modeling in Salesforce.

A. The available roll-up types are COUNT, SUM, MIN, and MAX. AVG (Average) is not a standard function for roll-up summary fields.

D. Roll-up summary fields are calculated and updated asynchronously after a record on the detail side of the relationship is saved, deleted, or undeleted.

- Salesforce Help, "Roll-Up Summary Field". This document explicitly states, "You can create roll-up summary fields on any master object in a master-detail relationship." It also lists the available functions as COUNT, SUM, MIN, and MAX.

- Salesforce Help, "Considerations for Relationships". Under the section for converting relationships, it notes, "You can’t convert a master-detail relationship to a lookup relationship if the master object has a roll-up summary field that summarizes a field on the detail object."

- Salesforce Object Model and Customization, Trailhead Module "Data Modeling". Unit on "Create Object Relationships" covers the properties and limitations of roll-up summary fields.

The standard Salesforce solution for selling the same products at different prices is to use Price Books. The administrator should create a new "Retail" Price Book and add the products to it with their specific retail prices. When sales reps create an Opportunity for a retail deal, they will select this new Price Book. This ensures that when they add Opportunity Products (line items), the correct retail prices are used, leading to accurate sales data tracking for the new business channel without creating duplicate product records.

A. Creating new Product records for each price point is inefficient, creates duplicate data, and complicates inventory management and reporting.

B. An Order Process defines the stages for an Order. This is irrelevant to setting the correct price on the preceding Opportunity record.

D. Linking an Order to an Opportunity is good practice but does not solve the fundamental problem of ensuring accurate pricing on the Opportunity itself.

Salesforce Help, "Products, Price Books, and Schedules": This documentation states, "Price books let you create a custom collection of products with associated list prices for specific uses."

Trailhead, "Products, Quotes, and Contracts" module, "Set Up Products" unit: This module explains, "To sell a product, you have to add it to a price book with a price... You can have a standard price book and any number of custom price books."

Delegated administration allows administrators to assign limited administrative privileges to non-administrator users, enabling them to manage users within specific roles and subordinates. This feature is specifically designed for scenarios where certain users need to create, edit, and manage other users within their organizational scope without having full system administrator access. Division leaders can be granted the ability to manage users only within their division's role hierarchy, perfectly addressing Cloud Kicks' requirement for divisional user management autonomy.

B. Territory hierarchies are for organizing sales territories and account assignments, not for user management delegation.

C. Permission set groups bundle permissions for functional access but don't provide user management capabilities for specific divisions.

D. Profiles control object and field permissions but cannot grant selective user management rights limited to specific divisions.

1. Salesforce Help Documentation: "Delegated Administration" - Setup section, User Management subsection

2. Salesforce Administrator Guide: "Managing Users" - Chapter on Delegated Administration Groups

3. Trailhead Module: "User Management" - Unit on Delegated Administration

4. Salesforce Platform Administration Study Guide - Section 2.3: User Setup and Management

5. Official Salesforce Release Notes - Delegated Administration Enhancement Features

Salesforce Flow is the only declarative automation tool that can be triggered when a record is deleted. The administrator can create a record-triggered flow that initiates when a star record is deleted. This flow can then be configured to perform actions, such as sending a custom email notification to the relevant scientists. The notification can include details from the deleted record and identify the user who performed the deletion, fulfilling all aspects of the requirement.

A. Heroku is an external platform for building custom applications and is not a standard, declarative automation tool within Salesforce for this type of task.

B. Process Builder cannot be triggered by a record deletion event; it only works on record creation and updates.

C. Workflow Rules, like Process Builder, do not support triggers on record deletion. They are limited to record creation and update events.

1. Salesforce Help, Record-Triggered Flow. "A record-triggered flow starts when a record is created, updated, or deleted. The flow runs in the background."

2. Salesforce Architects, Record-Triggered Automation Decision Guide. "Use a record-triggered flow when you need to... perform actions after a record is deleted." The guide explicitly contrasts this with Workflow Rules and Process Builder, which cannot trigger on delete.

A Cross-Filter allows a report to be filtered based on the child records of the primary object without displaying the child records themselves. The administrator can create an Account report and add two cross-filters: one for "Accounts with Opportunities" (filtered by this year's close date) and another for "Accounts with Activities" (filtered for completed tasks in the last 30 days). This configuration will produce a list of only the Account records that meet both criteria, fulfilling the request precisely.

A. Joined Report: This would show blocks for Accounts, Opportunities, and Activities, which is explicitly what the request wants to avoid (no opportunity details).

C. Summary Report: This report type groups rows of data but does not provide the "with/without" filtering capability needed to check for related records.

D. Filter Logic: This applies to standard filters on the primary object's fields, not for filtering based on the existence of related child records.

1. Salesforce Help. (2023). Filter Reports by Child Objects with Cross Filters. Salesforce. Retrieved from https://help.salesforce.com/s/articleView?id=sf.reportscrossfilters.htm&type=5. (This article explains the use case for cross-filters, stating, "Use a cross filter to fine-tune your results by including or excluding records from related objects and their children, without having to write formulas or code.")

2. Salesforce Help. (2023). Report and Dashboard Objects. Reports and Dashboards REST API Developer Guide. Retrieved from https://developer.salesforce.com/docs/atlas.en-us.apianalytics.meta/apianalytics/analyticsapireportanddashboardobjects.htm. (The documentation on report metadata describes crossFilters as a component for filtering by related objects.)

Record Types are the ideal solution for this scenario. They allow an administrator to define different sets of business processes, page layouts, and picklist values for various categories of records within a single object. This directly addresses the need to display different fields for customer versus competitor accounts (via different page layouts) and to offer different picklist values in the Industry field for partner accounts. This approach segments the user experience based on the type of account being viewed or created.

A. Business Processes control the lifecycle stages for specific standard objects (like Opportunities or Cases), not the visibility of various fields or picklist values on a general field like 'Industry'.

B. Required Fields enforce data entry for all users on a layout but do not allow for showing different fields or picklist values based on the type of account.

C. Flow Builder is an automation tool for complex processes. Using it for UI variations is overly complex when standard features like Record Types are designed for this exact purpose.

1. Salesforce Help. (n.d.). Create Record Types. Retrieved from https://help.salesforce.com/s/articleView?id=sf.creatingrecordtypes.htm&type=5. (This document explains that record types "determine the business processes, page layouts, and picklist values users have access to.")

2. Salesforce Help. (n.d.). Record Types. Retrieved from https://help.salesforce.com/s/articleView?id=sf.recordtypesoverview.htm&type=5. (This overview states, "Record types let you offer different business processes, picklist values, and page layouts to different users.")

For a product to be selectable on an opportunity, two primary conditions must be met. First, the product must have an active price book entry within an active price book. Second, that specific price book must be selected on the opportunity record itself. If the sales representative is using an opportunity with a different price book (e.g., a standard price book instead of a custom one for the new keyboard), the product will not appear in the selection list. Therefore, the administrator must check both the product's association with the correct price book and the price book selected on the opportunity.

B. Make sure the price book Is in the company currency: While currency mismatch can cause issues, it doesn't prevent the product from being available for selection if the price book is otherwise valid.

D. Verify the product has a start date entered: A start date is not a required field on a product or price book entry, and its absence would not prevent the product from being available.

1. Salesforce Help. (2023). Considerations for Using Products and Price Books. Salesforce. Retrieved from https://help.salesforce.com/s/articleView?id=sf.productsconsiderations.htm&type=5. (This document states, "To add a product to an opportunity...the opportunity’s price book must contain the product.")

2. Salesforce Help. (2023). Add and Remove Products from Opportunities. Salesforce. Retrieved from https://help.salesforce.com/s/articleView?id=sf.opportunityproducts.htm&type=5. (This guide outlines the process, which implicitly requires the product to exist in the opportunity's selected price book.)

3. Trailhead by Salesforce. (2023). Products, Price Books, and Schedules. Retrieved from https://trailhead.salesforce.com/content/learn/modules/products-price-books-and-schedules. (This module explains the relationship: "An opportunity has one price book. A price book has many products.")

An entitlement is a record that represents a customer’s right to receive support or service based on

the terms of a contract or agreement. An asset is a record that represents a product that a customer

has purchased. To automatically provide phone support to customers who purchase photo editing

software, the administrator can create a flow that attaches an entitlement to the asset upon

purchase. The entitlement can have a term of 365 days and a service contract that specifies the

phone support details. Reference:

https://help.salesforce.com/s/articleView?id=sf.entitlements_overview.htm&type=5

https://help.salesforce.com/s/articleView?id=sf.assets_overview.htm&type=5

Salesforce Connect allows for the creation of external objects, which provide a seamless way to view, search, and report on data stored in an external system in real-time. By creating an external object that maps to the inventory application's data tables, Cloud Kicks can make the inventory information available within the Salesforce UI and for standard reporting without duplicating or synchronizing the data. This directly addresses the need to view and report on data from a legacy application.

B. Import the data into a custom object when needed; delete after it is used. This creates data silos, requires manual effort, and does not provide real-time information from the legacy system.

C. Build a Lightning component and use SFDX to connect to the inventory app. While a component can display external data, it does not make the data natively available for standard Salesforce reporting.

D. Upload an Excel spreadsheet with the data into the Files tab. This is a static, manual solution that would be immediately outdated and is not suitable for reporting on live inventory data.

1. Salesforce Help, Salesforce Connect. "Salesforce Connect lets your users view, search, and modify data that’s stored outside your Salesforce org... Instead of copying the data into your org, external objects let you access the data in real time via web service callouts."

2. Salesforce Help, Considerations for Salesforce Connect—All Adapters. This document details reporting capabilities: "External objects are available with Salesforce reports. External object reports are included in the Other Reports report type category."

Dynamic Actions are configured on the Highlights Panel component in the Lightning App Builder. This feature allows an administrator to control the visibility of each action button on the panel based on filter criteria, such as the value of a field on the record. By adding filters to actions on the Highlights Panel, the administrator can ensure that specific buttons only appear when the defined conditions, like a planet being "gaseous," are met.

A. The Record Detail component displays the fields from the page layout and does not control the action buttons at the top of the page.

C. The Activities component is used for managing tasks, events, and emails related to the record, not for configuring the primary record action buttons.

D. Related Lists components display lists of child records and have their own set of actions, which are separate from the main record's dynamic actions.

1. Salesforce Help. (2023). Dynamic Actions. Salesforce, Inc. Retrieved from https://help.salesforce.com/s/articleView?id=sf.dynamicactions.htm&type=5. (This document states, "Add the Highlights Panel component to your Lightning record page... In the Highlights Panel properties pane... you can add, reorder, and remove actions.")

2. Trailhead by Salesforce. (2023). Lightning App Builder Module, Create Dynamic Pages with Dynamic Actions Unit. Salesforce, Inc. Retrieved from https://trailhead.salesforce.com/content/learn/modules/lightning-app-builder/create-dynamic-pages-with-dynamic-actions. (This unit provides a step-by-step guide on configuring Dynamic Actions on the Highlights Panel.)

This scenario requires modeling a one-to-many relationship and tracking changes. A custom object (C) is the best solution to store multiple form submissions related to a single parent record (e.g., Opportunity). Each time a client fills out the form, a new record is created on this custom object. This is a scalable and reportable data model. To meet the requirement to "see what changed from one submission to the next," Field History Tracking (D) should be enabled on the fields of this new custom object. This creates a related list that logs the date, time, user, and nature of any changes made to tracked fields on each submission record.

A. Add forms as attachments: Attachments are unstructured files (like PDFs or images). You cannot report on the data within them or easily compare field-level changes between versions.

B. Make custom fields: Adding over 30 fields directly to the parent object is not scalable for multiple submissions. It would require creating duplicate sets of fields, making reporting and management difficult.

1. Salesforce Help. (2024). Create a Custom Object. "Custom objects are the heart of any application. Custom objects let you store data that’s unique to your organization." This is used to model relationships like one-to-many.

2. Trailhead by Salesforce. (2024). Data Modeling module, Create Object Relationships unit. Explains how to use custom objects and lookup/master-detail relationships to model business processes where one record can be related to many other records.

3. Salesforce Help. (2024). Track Field History for Standard and Custom Objects. "You can select certain fields to track and display the field history in the History related list of an object... For each field, the history includes the date and time of the change, the user who made it, and the old and new values."

For importing a large volume of data (over 100,000 records), the recommended tool is Data Loader with the Bulk API feature enabled. Data Loader is a client application designed for bulk data operations and can handle up to 5 million records. Enabling the Bulk API optimizes the process for large datasets by processing records in batches asynchronously, which is faster and more efficient in consuming API limits compared to the standard SOAP API used for smaller loads.

A. The Developer Console is a development and debugging tool, not a data import tool for large volumes of records.

C. An AppExchange package is a potential solution but not the standard, out-of-the-box tool. The question implies using native Salesforce functionality.

D. The Data Import Wizard is a user-friendly, web-based tool, but its processing limit is 50,000 records per job, making it unsuitable for this scenario.

1. Salesforce Help. (2024). Data Loader. "Use it to insert, update, delete, or export Salesforce records. When importing data, Data Loader reads, extracts, and loads data... For large numbers of records, we recommend you use Data Loader."

2. Salesforce Help. (2024). When to Use the Data Import Wizard. "Import up to 50,000 records at a time."

3. Salesforce Developer Documentation. (2024). Bulk API Developer Guide. "Bulk API is based on REST principles and is optimized for loading or deleting large sets of data." Section: Introduction to Bulk API.

To expedite record update time, a before-save Flow Trigger is the most efficient declarative alternative to Process Builder. Before-save flows update fields on a new or changed record before it is saved to the database. This is significantly faster than Process Builder, which runs after the record is saved, as it avoids an additional database manipulation language (DML) operation and bypasses the recursion checks that Process Builder and after-save flows must perform. The option "Before save How Trigger" is interpreted as a typo for "Before save Flow Trigger".

B. Batch Update: This is for processing a large number of records asynchronously, not for optimizing the performance of a single, real-time record save operation.

C. Workflow Rule Field Change: While often faster than Process Builder, Workflow Rules are also after-save automation and are being retired. Before-save flows are demonstrably faster.

D. Screen Row: This is not a recognized Salesforce automation tool or concept for record-triggered updates. It is likely a distractor option.

- Salesforce Architects, "Record-Triggered Automation Decision Guide". This guide states, "Before-save record-triggered flows are the fastest-performing record-triggered automation." It explicitly compares them to Process Builder and after-save flows.

- Salesforce Help, "Record-Triggered Flows". The documentation notes, "Before a record is saved, a before-save flow can update fields on the record... Because it runs before the record is saved, a before-save flow is much faster than a record-change process built in Process Builder."

Before enabling Advanced Currency Management (ACM), it is critical to understand its permanent implications. Once enabled, ACM cannot be disabled, making it an irreversible change to the organization's data architecture. This is a primary consideration for any administrator. Additionally, while currencies can be deactivated, any currency added to the organization's list of supported currencies cannot be permanently deleted. This means careful planning is required for which currencies to add, as they will permanently exist in the org's metadata. These two factors represent significant, irreversible changes that must be considered.

B. Opportunities display amounts in the record's currency, the user's personal currency, and the corporate currency, not just the customer's localized currency.

C. Advanced Currency Management uses dated exchange rates, meaning historical reports use the exchange rate effective on the opportunity's close date, not the last dated rate.

1. Salesforce Help, Considerations for Enabling Advanced Currency Management. Document ID: 000385023. This document explicitly states, "After it’s enabled, advanced currency management can’t be disabled."

2. Salesforce Help, Manage Currencies. Document ID: 000384999. This document notes, "After you add a currency, you can’t delete it. However, you can deactivate currencies that you no longer use."

To investigate a user's multi-factor authentication (MFA) login failure, an administrator should primarily review the Login History and Identity Verification History. The Login History page shows all login attempts for the organization and includes a "Status" column that provides the specific reason for any failure. The Identity Verification History page provides a detailed log of all verification attempts, including the method used (e.g., Salesforce Authenticator, SMS) and whether it was successful, which is crucial for diagnosing if the MFA challenge itself is the point of failure.

C. Debug Logs: These are used for troubleshooting code and automation (like Apex or Flows) execution, not for tracking or diagnosing user login attempts.

D. Setup Audit Trail: This tracks administrative changes to the org's configuration. While it could show a change that caused the issue (e.g., a profile change), it does not show the login attempt itself.

- Salesforce Help, "Monitor Login History". This document states, "Review all attempts to log in to your organization... The Status column tells you whether the login succeeded or failed, with a reason for the failure."

- Salesforce Help, "Monitor Identity Verification History". This page explains, "Monitor and audit your org’s identity verification attempts... For each attempt, you can see information such as the user who tried to verify and the status." This is directly applicable to MFA troubleshooting.