- An administrator builds an Opportunities report and wants to show only records where Stage equals Closed Won OR Amount is greater than 100,000. Using the standard filter row interface, both conditions are currently combined with AND. What must the administrator configure to change this to an OR relationship?
- A cross filter between Opportunities and Accounts
- A bucket field grouping the two conditions
- A summary formula that evaluates both fields
- Custom filter logic specifying the conditions joined with OR
Correct answer: Custom filter logic specifying the conditions joined with OR
Custom filter logic is correct because by default standard report filters are joined with AND, and the administrator must add explicit filter logic such as '1 OR 2' to combine the numbered conditions with OR. A cross filter relates parent and child objects rather than joining field conditions, a bucket field categorizes values, and a summary formula calculates totals, so none of those change how filters are logically combined.
- A sales manager wants a report listing only Accounts that have at least one related Opportunity, while still reporting primarily on Account fields. Which report feature returns parent records based on the existence of related child records?
- Custom filter logic with OR
- A row-level formula
- A bucket field
- A cross filter
Correct answer: A cross filter
A cross filter is correct because it filters parent records by the presence or absence of related child records, such as showing only Accounts WITH Opportunities, without adding child fields as columns. Custom filter logic only combines field-level conditions on the same report, a row-level formula calculates a per-row value, and a bucket field groups values, so none of those filter by related-record existence.
- An administrator wants a report to show only Accounts that do NOT have any related Cases. Which configuration accomplishes this?
- A field filter set to Cases equals zero
- A cross filter using the WITHOUT condition on Cases
- Filter logic combining all Case fields with NOT
- A summary formula counting Cases
Correct answer: A cross filter using the WITHOUT condition on Cases
A cross filter using WITHOUT Cases is correct because cross filters let an administrator include or exclude parent records based on whether related child records exist, and the WITHOUT option returns only Accounts with no related Cases. A direct field filter cannot count related records, filter logic only joins same-report field conditions, and a summary formula computes totals rather than filtering which Accounts appear.
- An administrator needs a dashboard component that visually compares total Opportunity Amount across each Stage, with one bar per stage. Which chart type is most appropriate for this comparison?
- A gauge chart
- A metric component
- A bar (or column) chart
- A funnel chart
Correct answer: A bar (or column) chart
A bar or column chart is most appropriate because it compares a measured value across distinct categories, placing one bar per stage to compare amounts. A gauge shows a single value against a target range, a metric displays one summary number, and a funnel emphasizes sequential drop-off through ordered stages rather than a straightforward category comparison.
- A manager wants a dashboard component that displays a single number, total closed revenue this quarter, prominently with no chart. Which dashboard component type should the administrator choose?
- A line chart
- A table component with all columns
- A scatter chart
- A metric component
Correct answer: A metric component
A metric component is correct because it surfaces a single summarized value as a large prominent number, which is exactly what displaying total closed revenue requires. A line chart shows change over time, a table lists multiple rows and columns, and a scatter chart plots two measures against each other, none of which present one headline figure as cleanly.
- Every dashboard component in Salesforce gets its data from a particular underlying element. What must exist before a dashboard component can display data?
- A source report that the component is based on
- A validation rule on the source object
- A bucket field on the dashboard
- A permission set group for viewers
Correct answer: A source report that the component is based on
A source report is correct because each dashboard component is built from a report, and the report's data and groupings drive what the component can visualize. A validation rule enforces data entry standards, a bucket field categorizes values within a report rather than feeding a component directly, and a permission set group governs access rather than supplying component data.
- Sales leadership wants the morning pipeline dashboard delivered to their inboxes automatically every weekday at 7 a.m. without anyone opening Salesforce. Which dashboard capability meets this requirement?
- Subscribing to the dashboard on a schedule
- Setting a dynamic running user
- Adding a gauge component
- Exporting the dashboard with Data Loader
Correct answer: Subscribing to the dashboard on a schedule
Subscribing to the dashboard on a schedule is correct because dashboard subscriptions email a snapshot of the dashboard to recipients at a configured frequency and time, delivering it without manual action. A dynamic running user changes whose data appears, a gauge is a component type, and Data Loader handles record loading rather than emailing dashboards, so none of those automate scheduled delivery.
- An administrator wants a dashboard to show the most current data each time it is opened, but notices it displays figures from yesterday. What action updates the dashboard with the latest data from its source reports?
- Editing the dashboard folder sharing
- Changing the chart type to a gauge
- Adding a cross filter to the source report
- Refreshing the dashboard
Correct answer: Refreshing the dashboard
Refreshing the dashboard is correct because dashboards display data as of the last refresh, and refreshing re-runs the source reports to pull current values. Editing folder sharing changes access, switching to a gauge changes visualization style, and adding a cross filter alters which records the report returns, none of which by themselves update the displayed data to the latest values.
- A gauge component is added to an executive dashboard to track progress toward an annual sales target. What does a gauge chart best represent?
- A trend of values across many months
- A single value measured against defined breakpoints or a goal
- A list of individual records with their fields
- The percentage split of records across categories
Correct answer: A single value measured against defined breakpoints or a goal
A single value measured against defined breakpoints is correct because a gauge displays one number relative to ranges such as low, medium, and high or a goal, making it ideal for progress toward a target. A trend over months suits a line chart, a list of records suits a table, and a category split suits a pie or donut chart rather than a gauge.
- An administrator wants a report that is purely a flat list of contacts with their phone and email, no subtotals or groupings. Which report format should be selected?
- A matrix report
- A summary report
- A tabular report
- A joined report
Correct answer: A tabular report
A tabular report is correct because it presents a simple row-and-column list of records without groupings or subtotals, which matches a flat contact list. A summary report groups rows and provides subtotals, a matrix report groups by both rows and columns, and a joined report combines multiple report blocks, all of which add structure beyond a plain list.
- A manager needs a report that groups opportunities by Stage down the rows and by Lead Source across the columns to see amounts at each intersection. Which report format supports grouping in both directions?
- A tabular report
- A summary report
- A matrix report
- A bucket report
Correct answer: A matrix report
A matrix report is correct because it groups data by both rows and columns simultaneously, displaying summarized values at each row-and-column intersection. A tabular report has no grouping, a summary report groups only by rows, and a bucket report is not a report format, so none of those provide two-dimensional grouping.
- An administrator wants a single report that shows two related but separately grouped blocks, one of open cases and one of closed cases, side by side using different filters. Which report format is designed for this?
- A joined report
- A matrix report
- A tabular report
- A summary report
Correct answer: A joined report
A joined report is correct because it lets an administrator place multiple report blocks, each with its own filters and groupings, in a single report for side-by-side comparison. A matrix groups in two directions within one block, a tabular report is a flat list, and a summary report groups one block by rows, so none of those combine independently filtered blocks.
- Two users open the same Opportunities report, but one sees fewer records than the other even though they share the same role. What most likely explains why the second user sees fewer opportunity records?
- The report uses a tabular format
- The two users have different record-level access through the sharing model
- The report folder is shared as Viewer for one of them
- One user lacks a subscription to the report
Correct answer: The two users have different record-level access through the sharing model
Different record-level access through the sharing model is correct because reports only return records the running user can already see, so org-wide defaults, sharing rules, and ownership differences cause two users to see different row counts. The report format affects layout not visibility, folder sharing controls who can open the report rather than which records appear, and a subscription only schedules delivery.
- A field on the Opportunity object is hidden for a user through field-level security. When that user runs a report that includes the field as a column, what happens?
- The report fails to load entirely
- The user can see the column but not the records
- The field is automatically converted to a bucket field
- The hidden field's values are not visible to that user in the report
Correct answer: The hidden field's values are not visible to that user in the report
The hidden field's values not being visible is correct because field-level security carries into reports, so a user who cannot see a field cannot see its values even when it appears as a report column. The report still loads, the records themselves remain visible based on sharing, and field-level security never converts a field into a bucket field.
- An administrator places a sensitive dashboard in a folder and wants only the finance team to be able to open it. Which mechanism controls who can access that dashboard?
- The organization-wide default for the source object
- The dashboard folder's sharing settings
- The running user's profile
- A cross filter on the source report
Correct answer: The dashboard folder's sharing settings
The dashboard folder's sharing settings are correct because folder access determines which users or groups can open the dashboards stored inside, making it the control for limiting access to the finance team. The org-wide default governs record visibility within data, the running user determines whose data renders, and a cross filter narrows report records, none of which restrict who can open the dashboard.
- A duplicate rule is configured with the action set to Block when a matching Contact is found. A user attempts to save a new contact that matches an existing one. What is the result?
- The record saves and an admin is notified
- The record is prevented from being saved
- The record saves but is flagged for review
- The matching contact is automatically merged
Correct answer: The record is prevented from being saved
The record being prevented from saving is correct because a duplicate rule with a Block action stops the user from creating a record that matches per the matching rule. An Allow action would let it save with an optional alert, no standard duplicate rule action auto-merges records, and notifying an admin while saving is not the behavior of a Block action.
- An administrator wants to find and resolve duplicates that already exist across thousands of Account records in the database, rather than preventing new ones at entry. Which native capability addresses existing duplicates in bulk?
- A validation rule on Account
- A tabular report format
- A duplicate job using a duplicate rule
- A dashboard subscription
Correct answer: A duplicate job using a duplicate rule
A duplicate job is correct because it scans existing records in bulk against an active duplicate rule and surfaces duplicate record sets for review and merging, addressing duplicates already in the database. A validation rule blocks bad entries going forward, a tabular report only lists records, and a dashboard subscription schedules delivery, none of which detect and group existing duplicates at scale.
- An administrator must export all 250,000 Contact records, including the Salesforce record IDs, to a backup CSV file. Which native tool performs this export?
- The Data Import Wizard
- Data Loader
- A summary report emailed as a subscription
- Schema Builder
Correct answer: Data Loader
Data Loader is correct because it supports an export operation that pulls records, including IDs, out of Salesforce to a CSV at high volume. The Data Import Wizard only imports data and cannot export, a subscribed report delivers a snapshot rather than a full raw data export, and Schema Builder visualizes the data model rather than extracting records.
- An administrator needs to insert new records where they exist by an external ID, and update them where a matching external ID is already present, all in one operation. Which Data Loader operation does this?
Correct answer: Upsert
Upsert is correct because it combines insert and update by using an external ID field to update matching records and create those that do not yet exist in a single pass. Insert only creates new records and errors on existing ones, delete removes records, and export pulls data out, none of which conditionally insert-or-update based on an external ID.
- An administrator is told a report must only display this fiscal quarter's opportunities. Which part of the report should be configured to limit the records by Close Date to the current quarter?
- A date field filter on Close Date
- A bucket field on Close Date
- The dashboard running user
- Field-level security on Close Date
Correct answer: A date field filter on Close Date
A date field filter on Close Date is correct because report filters, including relative date ranges like THIS FISCAL QUARTER, restrict which records appear based on a field value. A bucket field only groups values into categories, the dashboard running user affects whose data is shown not the date range, and field-level security controls visibility of the field rather than filtering records by date.
- A dashboard built with a dynamic running user is requested to also be scheduled for automated email delivery. The administrator finds the subscription option is unavailable. What is the reason?
- Dynamic dashboards cannot be subscribed to or scheduled for refresh
- The dashboard folder is shared as Viewer
- The source report uses a cross filter
- The dashboard has too many components
Correct answer: Dynamic dashboards cannot be subscribed to or scheduled for refresh
Dynamic dashboards not supporting scheduling is correct because a dynamic dashboard renders per logged-in viewer and therefore cannot be set to a scheduled refresh or subscription. Folder sharing as Viewer affects edit rights not scheduling, a cross filter on the source report does not disable subscriptions, and the number of components does not remove the subscription option.
- An organization is limited in how many dynamic dashboards it can have based on its edition. What is the primary trade-off an administrator accepts when choosing a dynamic dashboard over a standard running-user dashboard?
- Dynamic dashboards cannot use bar charts
- Dynamic dashboards show each viewer data per their own access but cannot be scheduled to refresh
- Dynamic dashboards require Data Loader to populate
- Dynamic dashboards ignore the sharing model entirely
Correct answer: Dynamic dashboards show each viewer data per their own access but cannot be scheduled to refresh
Showing each viewer their own data while losing scheduled refresh is correct because a dynamic dashboard personalizes data to the logged-in user but cannot be subscribed to or scheduled, unlike a standard running-user dashboard. Dynamic dashboards still support standard chart types, do not rely on Data Loader, and respect rather than ignore the sharing model, so those options misstate the trade-off.
- An administrator needs a quarterly process that updates a custom Status field on roughly 120,000 records nightly, fully automated with no one logging in. Which native tool can be scheduled from a command line to perform this recurring update?
- The Data Import Wizard
- Schema Builder
- Data Loader run via its command-line interface
- A dashboard subscription
Correct answer: Data Loader run via its command-line interface
Data Loader's command-line interface is correct because it can be scheduled by the operating system to run unattended update operations on large record volumes on a recurring basis. The Data Import Wizard is an interactive browser tool that cannot be scheduled, Schema Builder designs objects rather than updating data, and a dashboard subscription emails dashboards rather than updating records.
- An administrator must give the entire org a common baseline of object access and tab visibility, then layer extra permissions onto only a few power users without changing what everyone else can do. Which combination follows Salesforce's recommended model for granting access?
- Use a profile for the additive power-user grants and permission sets for the baseline
- Use a profile for the common baseline and permission sets for the additive power-user grants
- Use organization-wide defaults for the baseline and sharing rules for the power users
- Use a role hierarchy for the baseline and manual sharing for the power users
Correct answer: Use a profile for the common baseline and permission sets for the additive power-user grants
Using a profile for the common baseline and permission sets for the extra grants is correct because the profile is assigned to every user as the foundational set of permissions, while permission sets add capabilities to selected users without altering the profile. Reversing the two misuses each tool, and organization-wide defaults, sharing rules, role hierarchy, and manual sharing govern record-level sharing rather than object and tab permissions.
- An administrator is debating whether to clone a profile to grant five users access to a new custom object, or to create a permission set. Which advantage of the permission set best explains why it is the preferred approach for this incremental access?
- A permission set lowers the organization-wide default automatically
- A permission set replaces the user's existing profile
- A permission set sets the org's fiscal year
- A permission set can be assigned to users across many different profiles without cloning
Correct answer: A permission set can be assigned to users across many different profiles without cloning
The key advantage is that a permission set can be assigned to users regardless of their profile, so one reusable permission set grants the new object access to users on different profiles without proliferating cloned profiles. A permission set does not lower the organization-wide default, does not replace a user's profile since it is additive, and does not set the fiscal year, which is an org-level company setting.
- A company's accounting team closes its books in a non-standard schedule that begins in February rather than January, and the periods do not align to standard calendar quarters. Which Company Information configuration lets the administrator define these custom periods for forecasting and reporting?
- Enabling a custom fiscal year
- Enabling multiple currencies
- Setting business hours
- Setting the default locale
Correct answer: Enabling a custom fiscal year
Enabling a custom fiscal year is correct because it lets the administrator define fiscal periods that do not follow the standard calendar structure, supporting an organization whose financial year starts in a different month or uses non-standard period lengths. Multiple currencies handles international amounts, business hours defines support schedules, and locale controls date and number formatting, none of which defines custom fiscal periods.
- An administrator needs to change the organization-wide default for the Contact object from Controlled by Parent to Private. In which area of Setup is the organization-wide default for an object configured?
- Object Manager page layouts
- Company Information
- Sharing Settings
- Session Settings
Correct answer: Sharing Settings
Sharing Settings is correct because the organization-wide defaults for each object, which set the baseline record access, are defined there alongside sharing rules. Object Manager page layouts control field arrangement on records, Company Information holds org defaults such as fiscal year and currency, and Session Settings governs session timeout and security, none of which is where organization-wide defaults are set.
- An administrator wants to restrict a specific profile's users so they can only log in from the corporate network's IP address range and are denied access from any other address. Which profile-level setting enforces this restriction?
- Login IP Ranges on the profile
- Trusted IP Ranges in Network Access
- A criteria-based sharing rule
- The role hierarchy
Correct answer: Login IP Ranges on the profile
Login IP Ranges on the profile is correct because it defines the addresses from which that profile's users are permitted to log in, blocking logins from outside the range entirely. Trusted IP Ranges in Network Access only exempts listed addresses from identity verification challenges but does not block other logins, while a criteria-based sharing rule and the role hierarchy govern record access rather than login locations.
- An administrator is told that field-level security can be applied through either a profile or a permission set. A field must remain hidden for most users but be made visible to a small reporting team without editing every profile. Which approach grants that field visibility most efficiently?
- Make the field visible on every profile, then hide it with a sharing rule
- Grant the field's visibility through a permission set assigned to the reporting team
- Set the field to universally required
- Change the organization-wide default for the object
Correct answer: Grant the field's visibility through a permission set assigned to the reporting team
Granting field visibility through a permission set is most efficient because field-level security is additive through permission sets, so assigning one to the reporting team reveals the field for just those users while it stays hidden for everyone else. Making it visible everywhere then hiding it with a sharing rule is invalid because sharing rules do not control field visibility, universally required forces data entry, and the organization-wide default governs record sharing.
- In a Private organization-wide default model, an administrator needs senior managers to automatically see records owned by their direct and indirect reports without writing any sharing rules. Which built-in mechanism provides this access up the management chain?
- Public groups
- Field-level security
- Permission set groups
- The role hierarchy
Correct answer: The role hierarchy
The role hierarchy is correct because users higher in the hierarchy automatically gain access to records owned by users below them, which delivers manager visibility to subordinates' records without any sharing rules. Public groups are sharing audiences that still require a rule or manual share, field-level security controls field visibility, and permission set groups bundle permissions rather than open record access up the management chain.
- An administrator must add several individual users, two roles, and another existing group into one collection that can then be used as the audience for multiple sharing rules. Which construct lets the administrator combine these different member types into a single reusable audience?
- A permission set group
- A public group
- A queue
- A muting permission set
Correct answer: A public group
A public group is correct because it can contain individual users, roles, roles and subordinates, and other public groups, forming a reusable collection that sharing rules and other features can target. A permission set group bundles permission sets for assignment, a queue holds records for shared ownership and assignment, and a muting permission set suppresses permissions, none of which assembles a mixed-member sharing audience.
- A user reports that even though their profile grants the 'Manage Users' permission, they still cannot see the option in Setup. The administrator suspects another permission is missing. Which permission is generally required for a user to access the Setup menu at all?
- Modify All Data
- Customize Application
- Manage Sharing
- View Setup and Configuration
Correct answer: View Setup and Configuration
View Setup and Configuration is correct because it is the permission that allows a user to view the Setup area, which is a prerequisite for using administrative pages found there. Modify All Data grants broad record access, Customize Application allows changing app and object configuration once in Setup, and Manage Sharing controls sharing administration, none of which is the baseline permission for reaching the Setup menu.
- An administrator wants certain elevated permissions to apply to a user only during the current browser session, automatically dropping when the session ends, rather than being granted persistently. Which feature supports this temporary, session-scoped activation of access?
- A standard profile
- An owner-based sharing rule
- A session-based permission set
- A validation rule
Correct answer: A session-based permission set
A session-based permission set is correct because it is activated only for the duration of a user's session, granting elevated access temporarily and removing it when the session ends, which suits just-in-time access scenarios. A standard profile grants persistent baseline access, an owner-based sharing rule governs record sharing, and a validation rule enforces data entry conditions, none of which provides session-scoped permission activation.
- An administrator sets the organization-wide default for Opportunity to Private and the role hierarchy is in place, yet a director still cannot see an opportunity owned by a peer in a different branch of the hierarchy. Why does the director lack access to that record?
- The role hierarchy only grants access downward to subordinates, not across to peers
- Private always blocks managers from all records
- Field-level security is hiding the record
- The opportunity has no page layout assigned
Correct answer: The role hierarchy only grants access downward to subordinates, not across to peers
The role hierarchy grants access downward to records owned by subordinates, so it does not give a director access to a peer in a separate branch who is not below them, which explains the missing access. Private does not block managers from their own subordinates' records, field-level security hides fields rather than whole records, and a missing page layout would not prevent record-level visibility through sharing.
- After setting an object's organization-wide default to Private, an administrator wants a rule that automatically shares all records owned by users in the Inside Sales role with users in the Field Sales role on an ongoing basis. Which sharing rule type bases the share on who owns the records?
- A criteria-based sharing rule
- An owner-based sharing rule
- A manual share
- A guest user sharing rule
Correct answer: An owner-based sharing rule
An owner-based sharing rule is correct because it shares records based on the record owner's role, group, or queue membership, which matches automatically sharing all records owned by the Inside Sales role with the Field Sales role. A criteria-based rule shares by field values rather than ownership, a manual share handles single records individually, and a guest user sharing rule targets unauthenticated visitors.
- An administrator needs to grant a contractor a full Salesforce license's worth of access for object permissions but realizes a specific feature requires an additional entitlement layered on top of the base license. Which statement correctly distinguishes a user license from a permission set license?
- A user license and a permission set license are the same thing
- A permission set license lowers the organization-wide default
- A user license is assigned through a sharing rule
- A user license sets the baseline of what a user can access; a permission set license enables specific additional features through an assigned permission set
Correct answer: A user license sets the baseline of what a user can access; a permission set license enables specific additional features through an assigned permission set
The correct distinction is that the user license defines the broad foundation of features a user can be granted, while a permission set license enables particular add-on features that are then delivered through an assigned permission set. The two are not the same, a permission set license does not change the organization-wide default, and user licenses are assigned on the user record rather than through a sharing rule.
- An administrator wants Salesforce to track the standard support coverage window of 8 a.m. to 6 p.m. Monday through Friday so that case escalation timing respects that schedule. Which Company-level configuration defines this operating window?
- Business hours
- Login hours
- Session timeout
- Fiscal year
Correct answer: Business hours
Business hours is correct because it defines the organization's operating schedule that features such as escalation rules and entitlement milestones use to calculate elapsed support time. Login hours restrict when users may sign in, session timeout controls inactivity expiration, and fiscal year defines financial reporting periods, none of which establishes the support coverage window used for escalation timing.
- An administrator wants to verify exactly which apps, objects, fields, and user permissions a particular permission set grants before assigning it widely. Where does the administrator review the contents of a permission set?
- In the organization-wide defaults
- In the role hierarchy
- In Company Information
- On the permission set's detail page in Setup
Correct answer: On the permission set's detail page in Setup
The permission set's detail page in Setup is correct because it lists the assigned apps, object and field permissions, system permissions, and other access the permission set grants, letting the administrator review its contents before assignment. Organization-wide defaults and the role hierarchy govern record sharing, and Company Information holds org-level settings such as fiscal year and currency rather than the contents of a permission set.
- A small team needs to read and edit all Lead records regardless of owner, but the administrator wants this capability tied to their job function so it can be granted or revoked easily as people join or leave the team. Which approach best supports easy, function-based management of this access?
- Manually share every Lead record with each team member
- Grant Modify All for Leads through a permission set assigned to team members
- Lower the organization-wide default for Leads to Public Read/Write
- Add each member to the role hierarchy at the top
Correct answer: Grant Modify All for Leads through a permission set assigned to team members
Granting Modify All for Leads through a permission set is best because the permission set ties the broad access to a job function and can be assigned or unassigned as team membership changes, while still bypassing the sharing model for that object. Manual sharing of every record is unmanageable, lowering the organization-wide default exposes leads to everyone, and placing members at the top of the role hierarchy over-grants access broadly.
- An administrator must promptly remove a departing employee's ability to log in while preserving their records, historical activity, and field history for audit purposes, and is willing to free the license. Which user-management action is the standard choice for a permanent departure?
- Freezing the user
- Deactivating the user
- Setting login hours to none
- Removing the user from all public groups
Correct answer: Deactivating the user
Deactivating the user is the standard choice for a permanent departure because it blocks login and frees the license while preserving the user's records, ownership history, and related data for audit. Freezing only temporarily blocks login without freeing the license, setting login hours to none is an awkward workaround, and removing the user from public groups affects sharing rather than disabling the account.
- An administrator notices that when an account is shared with a user, that user can also see the account's child contacts even though no contact sharing rule exists. Which Salesforce behavior explains this automatic visibility of related child records?
- A muting permission set
- Field-level security
- Implicit sharing between parent accounts and their child records
- The custom fiscal year
Correct answer: Implicit sharing between parent accounts and their child records
Implicit sharing explains the behavior because Salesforce automatically extends certain access between an account and its associated child records such as contacts, so seeing the account can grant visibility to its related contacts without an explicit rule. A muting permission set suppresses permissions, field-level security governs field visibility, and the custom fiscal year defines financial periods, none of which automatically links parent and child record access.
- An administrator wants the most reusable, scalable way to provision access for a brand-new job role so that future hires in that role can be set up consistently and the access can be audited as a single unit. Which design best meets these goals?
- Assign each new hire a unique cloned profile
- Add a manual share for every record the role needs
- Lower the organization-wide default for the objects the role uses
- Build a permission set group representing the job role and assign it to each new hire
Correct answer: Build a permission set group representing the job role and assign it to each new hire
Building a permission set group for the job role is best because it packages the needed permission sets into one assignable, auditable unit, making provisioning consistent and scalable for every future hire in that role. Cloning a unique profile per hire is unmanageable, manual shares per record do not scale, and lowering the organization-wide default over-exposes records to all users rather than provisioning role-based access.
- An administrator must change which page layout, record type, and field-level security a group of users receives, but the change should apply to everyone who shares a particular baseline assignment rather than to selected individuals. Which assignment is the appropriate place to define these defaults for the whole group at once?
- A public group
- A sharing rule
- The users' profile
- A queue
Correct answer: The users' profile
The profile is the appropriate place because page layout assignments, record type defaults, and field-level security can all be defined on the profile, applying uniformly to every user assigned that profile as their baseline. A public group and a queue are sharing and assignment constructs, and a sharing rule governs record access, none of which sets layout, record type, and field-level security defaults for the whole assigned group.
- An administrator wants new users in the org to be created efficiently with consistent role, profile, and locale settings, and asks whether multiple users can be set up at once rather than one at a time. Which built-in capability supports adding several standard users in a single operation?
- The Add Multiple Users option on the Users page in Setup
- A sharing rule
- Organization-wide defaults
- A muting permission set
Correct answer: The Add Multiple Users option on the Users page in Setup
The Add Multiple Users option on the Users page is correct because it lets an administrator create several users at once, entering details for each so they can be provisioned together with consistent settings. A sharing rule governs record access, organization-wide defaults set the sharing baseline, and a muting permission set suppresses permissions, none of which is a mechanism for creating multiple user accounts at once.
- Before assigning record types on the Lead object, an administrator must first define the underlying process that orders the Lead Status picklist values for each record type. Which configuration is required to associate a status sequence with a record type?
- A sales path on the opportunity
- A support process
- A lead process
- A validation rule on the status field
Correct answer: A lead process
A lead process is required because, on the Lead object, a record type must be tied to a lead process that defines which Lead Status values are available and their order, mirroring how opportunities use sales processes and cases use support processes. A support process governs Case Status, a sales path is a guidance UI rather than the process tied to a lead record type, and a validation rule only blocks invalid saves, so none of those supplies the status sequence a lead record type requires.
- An administrator wants to confirm whether record types control which users can edit a particular field on an Account. What is the accurate scope of what a record type controls?
- Record types control field-level edit and read access for users
- Record types control which records a user can view or own
- Record types control the org-wide default sharing level
- Record types control the page layout and available picklist values for a business process, not field-level security
Correct answer: Record types control the page layout and available picklist values for a business process, not field-level security
Record types control which page layout a user sees and which picklist values are available for a given business process, but they do not govern field-level security, record visibility, or sharing. Field edit and read access come from field-level security on profiles or permission sets, record visibility comes from the sharing model, and the org-wide default is a separate security setting, so attributing those to record types is incorrect.
- A company wants new opportunities created through a specific business process to automatically follow a tailored set of stages, while another business process uses a different stage set on the same Opportunity object. Which pairing must the administrator configure together to achieve this?
- A sharing rule paired with a permission set
- A compact layout paired with a list view
- A roll-up summary paired with a validation rule
- A record type paired with a sales process that defines the stage values
Correct answer: A record type paired with a sales process that defines the stage values
A record type paired with a sales process is correct because each opportunity record type is associated with a sales process that determines which Stage values are available and in what order, letting different business processes use different stage sets on the same object. A sharing rule and permission set govern access, a compact layout and list view affect display, and a roll-up summary with a validation rule address aggregation and data integrity, so none of those defines opportunity stages per business process.
- An administrator builds a formula field on the Contact object that should display the parent Account's industry, but the relationship from Contact to Account is a standard lookup, not master-detail. Can a cross-object formula still reference the Account field?
- Yes, cross-object formulas can traverse both lookup and master-detail relationships to reference parent fields
- No, cross-object formulas only work across master-detail relationships
- No, the lookup must be made required first
- Yes, but only if a roll-up summary already exists on the Account
Correct answer: Yes, cross-object formulas can traverse both lookup and master-detail relationships to reference parent fields
A cross-object formula can traverse either a lookup or a master-detail relationship to reference fields on a parent record, so the Contact formula can display the related Account's industry through the standard lookup. The traversal is not restricted to master-detail relationships, the lookup does not need to be required to be referenced, and no pre-existing roll-up summary is needed, since roll-up summaries aggregate child data rather than enable upward formula references.
- An administrator wants a formula field to render a colored status icon, such as a green or red image, instead of plain text on the record. Which formula function makes displaying an inline image possible?
- The IMAGE function returning a referenced image
- The TEXT function converting a picklist
- The VLOOKUP function
- The ISCHANGED function
Correct answer: The IMAGE function returning a referenced image
The IMAGE function is correct because it lets a formula field return and display an image, such as a colored status indicator, by referencing the image's URL and alternate text. The TEXT function converts values like picklists or dates to strings rather than rendering images, VLOOKUP looks up values in a related list of records for validation contexts, and ISCHANGED detects field changes within rules, so none of those displays an inline image.
- A roll-up summary field on a parent object stopped updating after a large data import, and the administrator suspects the totals are stale. Which action forces a roll-up summary field to recalculate across existing records?
- Convert the field to a formula field
- Add a new record type to the child object
- Use the option to force a mass recalculation of the roll-up summary field
- Disable field-level security on the parent
Correct answer: Use the option to force a mass recalculation of the roll-up summary field
Forcing a mass recalculation is correct because Salesforce provides an option to recalculate a roll-up summary across all existing parent records when totals appear stale after bulk operations. Converting to a formula field would change the field's behavior entirely, adding a record type to the child does not affect aggregation, and disabling field-level security only changes visibility, so none of those refreshes the roll-up totals.
- An administrator is planning the data model and needs to know how many master-detail relationships a single custom object can have as a child. What is the maximum number of master-detail relationships a custom object can act as the detail side of?
Correct answer: Two
Two is correct because a custom object can be the detail side of at most two master-detail relationships, which is exactly what makes the junction-object pattern for many-to-many relationships possible. It is not limited to one, which would prevent junction objects, and it is not five or unlimited, since allowing more than two masters would conflict with how detail records inherit ownership and sharing from their masters.
- An administrator creates a master-detail relationship and wants users to be able to move a child record to a different parent after creation. Which setting must be enabled on the master-detail relationship to permit this?
- Cascade delete protection
- Field history tracking
- Roll-up summary filtering
- Allow reparenting of the child record
Correct answer: Allow reparenting of the child record
Allowing reparenting is correct because master-detail child records cannot be moved to a new parent by default, and the administrator must enable the reparenting option on the relationship to let users reassign a detail record to a different master. Cascade delete protection, field history tracking, and roll-up summary filtering address deletion behavior, change auditing, and aggregation scope respectively, none of which permits changing a detail record's parent.
- An administrator wants to know whether Schema Builder can be used to set field-level security or assign page layouts while editing the data model. What is the accurate limitation of Schema Builder?
- Schema Builder can configure field-level security but not relationships
- Schema Builder visualizes and creates objects, fields, and relationships but does not manage field-level security or page layout assignments
- Schema Builder can assign page layouts but cannot create fields
- Schema Builder can do everything Object Manager can do
Correct answer: Schema Builder visualizes and creates objects, fields, and relationships but does not manage field-level security or page layout assignments
Schema Builder visualizes and lets an administrator create objects, fields, and relationships on a canvas, but it does not configure field-level security or assign page layouts, which remain Object Manager and profile or permission set tasks. It is not the case that it sets field-level security, nor that it can only assign layouts, and it is not a full replacement for Object Manager, so those statements overstate its capabilities.
- An administrator is migrating an Account record page from a single Record Detail component to Dynamic Forms and wants Salesforce to convert the existing layout automatically. Which Lightning App Builder feature assists with this conversion?
- The Schema Builder import tool
- The Data Import Wizard
- The compact layout converter
- The Dynamic Forms upgrade or migration wizard within the Lightning App Builder
Correct answer: The Dynamic Forms upgrade or migration wizard within the Lightning App Builder
The Dynamic Forms upgrade wizard within the Lightning App Builder is correct because it can take the fields from an existing page layout and convert them into Dynamic Forms field sections on the Lightning record page, streamlining the migration. Schema Builder edits the data model, the Data Import Wizard loads records, and there is no compact layout converter that performs this task, so none of those migrates a page to Dynamic Forms.
- An administrator wants to build a Lightning page that serves as a personalized starting screen showing assistant, recent items, and key components for users when they log in, not tied to a single object. Which Lightning page type fits this purpose?
- A record page
- A compact layout
- A list view
- A home page
Correct answer: A home page
A home page is correct because the Lightning App Builder lets an administrator build home pages that present components such as the assistant, recent records, and key metrics as a personalized landing experience independent of any specific record. A record page is bound to an object's records, a compact layout selects highlights-panel fields, and a list view displays filtered records, so none of those creates a login home screen.
- An administrator needs the Industry picklist to appear differently depending on a checkbox named 'Is Partner' on the Account. Can a checkbox be used to control a dependent picklist, and what is the dependent side limited to?
- No, only picklists can be controlling fields
- Yes, but the dependent field must be a text field
- No, checkboxes can only be dependent fields
- Yes, a checkbox can control a picklist, and the dependent field must be a picklist or multi-select picklist
Correct answer: Yes, a checkbox can control a picklist, and the dependent field must be a picklist or multi-select picklist
A checkbox can serve as a controlling field, with its checked and unchecked states driving which values appear, and the dependent field must be a standard or custom picklist or multi-select picklist. It is not true that only picklists can control dependencies, the dependent side cannot be a plain text field, and checkboxes are not restricted to being dependent fields, so those alternatives misstate the rules.
- An administrator opens a page layout in Object Manager and wants to add a section that shows child records, such as related Contacts, beneath the Account's fields. Which page layout element displays these child records?
- A related list
- A roll-up summary field
- A field dependency
- A compact layout
Correct answer: A related list
A related list is correct because page layouts include related lists that display records associated with the current record, such as Contacts shown on an Account, along with selected columns and buttons. A roll-up summary aggregates child values into a single field rather than listing the records, a field dependency filters picklists, and a compact layout selects highlights-panel fields, so none of those displays the child records themselves.
- An administrator wants a custom Lightning app to surface a particular set of objects and a custom home page, and to control its branding and navigation style. In which Setup area is an entire Lightning app, including its navigation items and assigned pages, defined?
- Schema Builder
- The sharing settings
- The App Manager
- The Data Loader
Correct answer: The App Manager
The App Manager is correct because it is where an administrator creates and edits Lightning apps, defining the app's navigation items, branding, and which Lightning pages, such as a custom home page, belong to the app. Schema Builder edits the data model, sharing settings control record access, and Data Loader moves data, so none of those defines a Lightning app's overall composition.
- An administrator must add a brand-new custom field to track a warranty expiration date on a custom 'Asset Record' object. From which area is a new custom field created on a custom object?
- The Fields and Relationships area for that object in Object Manager
- The report type editor
- The list view controls
- The org-wide default settings
Correct answer: The Fields and Relationships area for that object in Object Manager
The Fields and Relationships area within the object's entry in Object Manager is correct because that is where an administrator launches the new custom field wizard to choose a data type and define a field such as a warranty expiration date. The report type editor defines reportable fields for reporting, list view controls filter displayed records, and org-wide defaults set baseline access, so none of those is where a custom field is created.
- An administrator wants a percent-type custom field on Opportunity that captures a manually entered discount rate that users can edit at any time. Which characteristic distinguishes this standard custom field from a formula field of the same percent type?
- The custom field is read-only while the formula field is editable
- The custom field stores a user-entered, editable value while the formula field is read-only and auto-calculated
- Both fields aggregate child records
- Both fields require a master-detail relationship
Correct answer: The custom field stores a user-entered, editable value while the formula field is read-only and auto-calculated
The distinguishing characteristic is that a standard custom percent field stores a value that users can enter and edit, whereas a formula field of percent type is read-only and derived automatically from an expression. The custom field is editable rather than read-only, neither field aggregates child records, which is a roll-up summary's role, and neither requires a master-detail relationship, so those statements are inaccurate.
- An administrator wants the highlights panel on a custom object to remain consistent while still using Dynamic Forms for the body fields on the Lightning record page. Which element continues to define the fields shown in the highlights panel regardless of Dynamic Forms?
- The validation rule
- The org-wide default
- The compact layout
- The sharing rule
Correct answer: The compact layout
The compact layout is correct because it defines which fields appear in the highlights panel at the top of a record, and this remains governed by the compact layout even when Dynamic Forms controls the body field placement. A validation rule blocks invalid saves, an org-wide default sets baseline record access, and a sharing rule grants additional access, none of which selects the highlights-panel fields.
- An administrator wants to make sure a Lightning record page is only used for Account records of the 'Customer' record type, while a different page is used for the 'Partner' record type. How is this targeting accomplished in the Lightning App Builder?
- By creating a separate object for each record type
- By activating each Lightning record page with an assignment tied to its specific record type
- By adding a roll-up summary for each record type
- By setting an org-wide default per record type
Correct answer: By activating each Lightning record page with an assignment tied to its specific record type
Activating each Lightning record page with a record-type-specific assignment is correct because the Lightning App Builder lets an administrator assign different pages by record type, so Customer and Partner accounts each open their intended page. Creating separate objects is unnecessary and incorrect for one object, roll-up summaries aggregate data rather than assign pages, and org-wide defaults govern access not page assignment, so none of those targets a page by record type.
- An administrator is designing a relationship between a custom 'Project' object and the standard Account object and wants Project to be the child whose records are deleted when the Account is deleted. Which fact about master-detail relationships involving standard objects must the administrator account for?
- A standard object can be the detail side of a custom object's master-detail relationship
- A standard object cannot be the detail side of a master-detail relationship where a custom object is the master
- Standard objects cannot participate in any relationships
- Master-detail relationships are only allowed between two standard objects
Correct answer: A standard object cannot be the detail side of a master-detail relationship where a custom object is the master
The administrator must account for the fact that a standard object cannot be the detail side of a master-detail relationship controlled by a custom master, so the custom Project object must be the detail and Account the master. It is not the case that a standard object can be the custom-mastered detail, standard objects do participate in relationships, and master-detail relationships are not limited to two standard objects, so those statements are incorrect.
- An administrator wants a single Lightning component to appear on the record page only when a custom checkbox 'Escalated' is true, and the page is built with the Lightning App Builder. Which approach correctly drives this conditional display?
- A page layout field section
- A component visibility rule referencing the Escalated field
- A criteria-based sharing rule
- A dependent picklist on the component
Correct answer: A component visibility rule referencing the Escalated field
A component visibility rule referencing the Escalated field is correct because the Lightning App Builder lets an administrator set conditions on a component so it appears only when a record field, such as the Escalated checkbox, meets the criteria. A page layout field section governs classic layouts rather than Lightning component visibility, a sharing rule controls record access, and a dependent picklist filters picklist values, so none of those conditionally shows a Lightning component.
- An administrator needs a roll-up summary on an Account that sums the Amount of related Opportunities. The Account-to-Opportunity link is a standard relationship that already supports roll-up summaries. Which built-in behavior allows this specific roll-up summary on Account?
- Account and Opportunity are connected by a standard master-detail-style relationship that permits roll-up summaries
- A lookup relationship was converted automatically at runtime
- A formula field was promoted to a roll-up summary
- A field dependency enabled aggregation
Correct answer: Account and Opportunity are connected by a standard master-detail-style relationship that permits roll-up summaries
The roll-up summary is allowed because Account and Opportunity share a standard relationship that behaves like a master-detail relationship for this purpose, so the parent Account can aggregate child Opportunity amounts. No runtime conversion of a lookup occurs, a formula field is a separate field type that is not promoted into a roll-up summary, and a field dependency only filters picklist values rather than enabling aggregation, so those explanations are incorrect.
- An administrator has three separate record-triggered flows that all run after save on the Account object, and the order in which they execute matters for the result. Which Flow Builder feature lets the administrator view and set a numeric trigger order so the flows run in a predictable sequence?
- The organization-wide default for the Account object
- The field-level security on the triggering field
- The login IP range of the running user
- The flow trigger order setting (such as the priority value shown in Flow Trigger Explorer)
Correct answer: The flow trigger order setting (such as the priority value shown in Flow Trigger Explorer)
Setting the flow trigger order is correct because each record-triggered flow can be assigned a trigger order value, and Flow Trigger Explorer shows the sequence so an administrator can make multiple same-trigger flows run in a defined order. The organization-wide default governs record access, field-level security controls field visibility, and a login IP range restricts user access, so none of those determines the execution sequence of multiple flows on one object.
- An administrator wants to confirm a complex screen flow behaves correctly without manually clicking through every path on the live record page. Which Flow Builder capability lets the administrator step through the flow and inspect variable values before activating it?
- Schema Builder
- The organization-wide default preview
- The Debug feature in Flow Builder
- A sharing rule simulation
Correct answer: The Debug feature in Flow Builder
The Debug feature is correct because it runs the flow in a controlled mode that lets the administrator supply inputs, follow each element, and inspect the values of variables to validate behavior before activation. Schema Builder visualizes the data model, the organization-wide default controls record access, and there is no sharing rule simulation that walks through flow logic, so none of those tests a flow's execution path.
- In Flow Builder, an administrator needs a value that is calculated dynamically from other field or variable values and reused at several points in the flow, without storing it permanently. Which type of flow resource should the administrator create?
- A constant
- A formula resource
- A choice
- A stage
Correct answer: A formula resource
A formula resource is correct because it evaluates an expression based on other resources or record fields each time it is referenced, giving a dynamically calculated value the flow can reuse without persisting it. A constant holds a fixed unchanging value, a choice supplies selectable options on a screen, and a stage tracks progress through a flow, so none of those produces a recalculated value from other inputs.
- A record-triggered flow uses a Get Records element to retrieve open opportunities, and the administrator wants only the single most recently created one returned. Which configuration of the Get Records element accomplishes this?
- Set the object's organization-wide default to Private
- Add a validation rule to the Opportunity object
- Sort the results by created date descending and store only the first record
- Convert the flow to a screen flow
Correct answer: Sort the results by created date descending and store only the first record
Sorting by created date descending and storing only the first record is correct because the Get Records element can order matching records and be set to return just the first one, yielding the most recently created opportunity. Changing the organization-wide default affects access, adding a validation rule blocks invalid saves, and converting to a screen flow changes the trigger model, so none of those controls which single record a Get Records element returns.
- An administrator must deactivate a running flow to stop it temporarily but wants to preserve the ability to reactivate the exact same logic later. Which characteristic of Flow versioning supports this?
- Deactivating a flow permanently deletes all of its versions
- Only one version of a flow can be active at a time, and inactive versions are retained and can be reactivated
- A flow can have many active versions running simultaneously
- Deactivating a flow converts it into a workflow rule
Correct answer: Only one version of a flow can be active at a time, and inactive versions are retained and can be reactivated
The supporting characteristic is that a flow can have only one active version at a time while its other versions remain saved and inactive, so the administrator can deactivate the current version and reactivate a retained version later. Deactivating does not delete versions, multiple versions cannot be active at once, and deactivation never turns a flow into a workflow rule, so the other statements misdescribe flow versioning.
- An administrator wants a record-triggered flow to wait three days after a Case is created and then check whether it is still open before sending a reminder, all within the same flow. Which record-triggered flow feature provides this delayed execution?
- A Scheduled Path on the record-triggered flow
- An escalation rule on the Case object
- A before-save flow path
- A roll-up summary field
Correct answer: A Scheduled Path on the record-triggered flow
A Scheduled Path is correct because it lets a record-triggered flow run a set of actions at a defined time after the trigger, such as three days later, allowing the flow to re-check the case and send a reminder. An escalation rule is a separate case feature, a before-save path runs synchronously during the save with no delay, and a roll-up summary field only aggregates child records, so none of those adds a timed branch inside the flow.
- An administrator needs a flow to run automatically when a platform event message is received from an integration, rather than when a record changes or a user starts it. Which flow trigger type is designed for this?
- A screen flow
- A schedule-triggered flow
- A before-save record-triggered flow
- A platform event-triggered flow
Correct answer: A platform event-triggered flow
A platform event-triggered flow is designed for this because it starts when a specified platform event message is published, letting the flow react to integration events. A screen flow needs a user, a schedule-triggered flow runs on a timer, and a before-save record-triggered flow fires only when a record is saved, so none of those responds to an incoming platform event.
- An administrator wants a validation rule's error message to appear directly beneath the specific field a user entered incorrectly rather than at the top of the record. Which validation rule setting controls this placement?
- The organization-wide default for the object
- The page layout's related list order
- The field-level security on the field
- The error location, which can be set to the top of the page or to a specific field
Correct answer: The error location, which can be set to the top of the page or to a specific field
The error location setting controls placement because a validation rule lets the administrator choose whether the error message shows at the top of the page or next to a chosen field. The organization-wide default governs record access, the related list order changes layout display, and field-level security controls field visibility, so none of those determines where a validation error message appears.
- An administrator wrote a validation rule but wants to keep it in the org without it enforcing anything for now, planning to turn it back on after a data cleanup. What is the appropriate way to stop the rule from firing while keeping its definition?
- Delete the rule and rebuild it after the cleanup
- Uncheck the Active checkbox on the validation rule
- Lower the organization-wide default to Private
- Move the rule into an approval process
Correct answer: Uncheck the Active checkbox on the validation rule
Unchecking the Active checkbox is appropriate because a validation rule has an active flag that, when cleared, stops the rule from evaluating saves while preserving its definition for later reactivation. Deleting and rebuilding discards the work, lowering the org-wide default changes record access, and approval processes do not contain validation rules, so none of those cleanly disables a rule temporarily.
- An administrator must build a validation rule that blocks a save only when a Contact record is first being created, not on later edits. Which formula function detects that the record is new?
- The ISNEW function
- The PRIORVALUE function
- The VLOOKUP function
- The ISCHANGED function
Correct answer: The ISNEW function
The ISNEW function is correct because it returns true only when a record is being created, allowing the validation rule to enforce a condition on creation but not on subsequent edits. PRIORVALUE returns a field's previous value, VLOOKUP looks up a value in another object, and ISCHANGED detects a field modification during an edit, so none of those identifies a brand-new record the way ISNEW does.
- An administrator wants two managers to both approve a request in a single approval step, and the request should advance only if both approve. Which approval step configuration accomplishes this?
- Setting the organization-wide default to Public Read Only
- Adding a lead assignment rule entry for each manager
- Assigning the step to multiple approvers and requiring unanimous approval
- Creating a separate profile for each approver
Correct answer: Assigning the step to multiple approvers and requiring unanimous approval
Assigning multiple approvers and requiring unanimous approval is correct because an approval step can route to several approvers at once and be set so the request advances only when all of them approve. Changing the organization-wide default affects record access, lead assignment rules route leads, and creating profiles manages permissions, so none of those requires multiple approvers to all approve a single step.
- A company wants busy executives to be able to approve or reject requests by replying to an email from their phone instead of logging into Salesforce. Which approval process capability enables this?
- A schedule-triggered flow
- A roll-up summary field on the record
- Email approval response, which lets approvers reply to act on the request
- An auto-response rule on the object
Correct answer: Email approval response, which lets approvers reply to act on the request
Email approval response is correct because Salesforce can let approvers approve or reject a pending request by replying to the approval email, which is convenient for mobile approvers. A schedule-triggered flow runs on a timer, a roll-up summary field aggregates child data, and an auto-response rule sends acknowledgment email rather than processing approvals, so none of those lets an approver act by email reply.
- An administrator wants users to see who approved a record and read any comments approvers left during the approval process directly on the record. Which element should be added to the page layout to expose this information?
- A roll-up summary field
- A sharing rule
- The organization-wide default panel
- The Approval History related list
Correct answer: The Approval History related list
The Approval History related list is correct because adding it to the page layout displays each approval step, the approver, the action taken, and the comments, giving users full visibility into the approval trail. A roll-up summary field aggregates numeric child data, a sharing rule grants access, and there is no org-wide default panel that shows approval steps, so none of those surfaces approval history on the record.
- An administrator is building a screen flow and wants to validate that a user entered a phone number in the correct format before the flow advances to the next screen. Which screen flow capability enforces the entry before moving on?
- Input validation configured on the screen component
- A criteria-based sharing rule
- An escalation rule on the object
- The fiscal year setting
Correct answer: Input validation configured on the screen component
Input validation on the screen component is correct because a screen flow input field can include a validation formula and error message that must be satisfied before the user can proceed, enforcing the correct phone format. A sharing rule grants access, an escalation rule applies to case aging, and the fiscal year setting governs reporting periods, so none of those validates user input within a screen flow.
- A screen flow must present a picklist whose available options come from the values of an existing custom picklist field rather than a hand-typed list. Which screen flow resource provides these dynamically sourced options?
- A constant
- A stage
- A picklist choice set tied to the field's values
- A formula resource
Correct answer: A picklist choice set tied to the field's values
A picklist choice set is correct because it generates the selectable options for a screen choice component directly from a picklist field's defined values, so the screen reflects the field rather than a static list. A constant holds a fixed value, a stage tracks flow progress, and a formula resource calculates a value, so none of those populates a screen choice from a picklist field's options.
- An administrator wants a screen flow to display read-only instructional text and a clickable help link on a screen, alongside the input fields, to guide users. Which screen component type provides this non-input content?
- A Display Text component
- A Loop element
- A Get Records element
- An Update Records element
Correct answer: A Display Text component
A Display Text component is correct because it shows formatted, read-only text, including links and instructions, on a flow screen without collecting input. A Loop element iterates over a collection, a Get Records element retrieves data, and an Update Records element changes existing records, so none of those displays informational text to guide the user on a screen.
- An administrator is documenting the difference between Process Builder and Flow for the team. According to current Salesforce direction, what is the correct status of Process Builder for new automation?
- Process Builder remains the preferred tool and should be used for all new automation
- Salesforce no longer supports creating new Process Builder processes and directs new automation to Flow
- Process Builder can only be used after a validation rule is created
- Process Builder is required to run any record-triggered flow
Correct answer: Salesforce no longer supports creating new Process Builder processes and directs new automation to Flow
The correct status is that Salesforce no longer supports creating new Process Builder processes and steers new declarative automation into Flow, consolidating on a single tool. Process Builder is not the preferred go-forward tool, it has no dependency on validation rules, and record-triggered flows run on their own without Process Builder, so the other statements are inaccurate.
- An administrator is comparing a legacy Workflow Rule field update with a before-save record-triggered flow that updates the same field. Which advantage explains why Salesforce recommends the before-save flow for this same-record update?
- The workflow rule cannot update any field, while the flow can
- The before-save flow is generally faster because it updates the field during the initial save without a separate update operation
- The workflow rule runs only on a nightly schedule
- The before-save flow requires an approval process to update the field
Correct answer: The before-save flow is generally faster because it updates the field during the initial save without a separate update operation
The advantage is that a before-save flow updates the field during the original save transaction without issuing a separate update, which a workflow rule field update effectively triggers, so the flow is generally faster. Workflow rules can update fields, they do not run only on a schedule, and a before-save flow needs no approval process, so the other statements are inaccurate.
- An administrator wants reps to choose from a different set of opportunity stage values depending on whether the deal is a New Business sale or a Renewal. What configuration links each business scenario to its own subset of stage picklist values?
- A separate price book for each business scenario
- An owner-based sharing rule on the Opportunity object
- A campaign member status set for each scenario
- Opportunity record types, each with a sales process that controls which stages are available
Correct answer: Opportunity record types, each with a sales process that controls which stages are available
Opportunity record types are paired with sales processes, and each sales process defines the subset of stage picklist values available for that scenario, so New Business and Renewal deals can follow different stages. A price book governs product pricing, an owner-based sharing rule controls record access, and a campaign member status set tracks marketing responses, none of which limits which opportunity stages a given deal can use.
- A sales operations lead reports that some deals jump straight to Closed Won while skipping required mid-pipeline stages, and wants only valid forward progression allowed. Which approach lets the administrator enforce that opportunities follow the intended stage order?
- Increase the probability percentage on each stage
- Add a custom price book for closed deals
- Convert the opportunity into a lead before closing
- Create a validation rule that checks the prior and new Stage values to block invalid transitions
Correct answer: Create a validation rule that checks the prior and new Stage values to block invalid transitions
A validation rule comparing the prior stage to the new stage can block out-of-order jumps, enforcing intended forward progression through the sales process. Raising probability percentages only changes pipeline math, a price book governs product pricing, and converting an opportunity back into a lead is not a real action, so none of those enforces stage sequencing.
- When an administrator configures opportunity stages, each stage value can be mapped to a forecast category. What is the primary purpose of that forecast category mapping?
- It sets the organization-wide default for opportunities
- It determines which price book is used for the deal
- It groups opportunities into buckets like Pipeline, Best Case, and Commit for forecasting
- It assigns the opportunity to a campaign
Correct answer: It groups opportunities into buckets like Pipeline, Best Case, and Commit for forecasting
Mapping a stage to a forecast category groups its opportunities into forecasting buckets such as Pipeline, Best Case, Commit, Closed, and Omitted so managers can roll up expected revenue by category. Forecast category mapping does not set organization-wide defaults, choose a price book, or assign a campaign, since those are unrelated access, pricing, and marketing settings.
- A rep wants to convert a lead but also relate that lead to the marketing campaign that generated it so the resulting opportunity shows campaign influence. What should the rep populate before or during conversion to make this association?
- The Campaign Source (primary campaign) on the lead, which carries to the new opportunity
- A roll-up summary field on the account
- A login IP range for the lead owner
- The standard price book entry for the lead
Correct answer: The Campaign Source (primary campaign) on the lead, which carries to the new opportunity
Setting the lead's Campaign Source, the primary campaign, lets that campaign carry through conversion and become the primary campaign source on the resulting opportunity, supporting campaign influence reporting. A roll-up summary field aggregates child records, a login IP range is a security control, and a price book entry is pricing data, so none of those connects a converted lead to its originating campaign.
- After a lead is successfully converted, a new user searches the Leads tab and cannot find the original lead record. Which statement best explains the standard behavior of a converted lead?
- Converted leads are permanently deleted during conversion
- The lead is hidden until an escalation rule reopens it
- The lead becomes read-only and is filtered out of standard open-lead list views but still exists
- The lead is automatically merged into a price book
Correct answer: The lead becomes read-only and is filtered out of standard open-lead list views but still exists
A converted lead is not deleted; it is marked converted, becomes read-only, and drops out of standard open-lead list views, though it remains retrievable via reports or by filtering for converted leads. Conversion does not delete the record, escalation rules apply to cases, and price books hold pricing, so none of those describes what happens to a converted lead.
- An administrator maps a custom lead picklist to a custom opportunity picklist for conversion, but values are not transferring and conversions fail. Which requirement about lead field mapping is the most likely cause?
- The mapped fields must be of compatible data types for the values to transfer
- The lead must belong to a queue before mapping works
- A custom price book must exist for mapping to function
- The opportunity must have a campaign member before mapping applies
Correct answer: The mapped fields must be of compatible data types for the values to transfer
Lead field mapping requires the source and destination fields to be of compatible data types, so mapping a picklist to an incompatible field type prevents values from transferring and can break conversion. Queue membership, a custom price book, and an existing campaign member are unrelated to whether field data types are compatible for mapping at conversion.
- A marketing team runs a multi-touch program and wants the same lead to belong to several campaigns over time, each with its own response status. Which fact about campaign membership supports this?
- A lead can be a campaign member of many campaigns, with a distinct member status per campaign
- A lead can only belong to one campaign at a time
- Campaign membership is controlled by the role hierarchy
- Campaign members are stored as price book entries
Correct answer: A lead can be a campaign member of many campaigns, with a distinct member status per campaign
A single lead or contact can be a campaign member of many campaigns simultaneously, and each membership carries its own member status, which is what enables multi-touch tracking. Membership is not limited to one campaign, it is not governed by the role hierarchy, and campaign members are not stored as price book entries, so those statements do not hold.
- An administrator needs to bulk-add several thousand existing contacts to a campaign and set their member status in one operation. Which approach is most appropriate for adding campaign members at this scale?
- Manually open each contact and add the campaign one at a time
- Use a report or list view to add members, or import them via the campaign member import
- Create a validation rule that adds members automatically
- Change the organization-wide default to add members
Correct answer: Use a report or list view to add members, or import them via the campaign member import
Adding contacts to a campaign from a report or list view, or using the campaign member import, is the standard way to bulk-enroll many members and assign a status efficiently. Manually editing each record does not scale, a validation rule only blocks invalid saves, and organization-wide defaults govern record access, so none of those bulk-adds campaign members.
- When defining member status values for a specific campaign, an administrator marks one value as 'Responded.' What effect does flagging a status as Responded have on campaign statistics?
- It excludes those members from the campaign
- Members with that status are counted in the campaign's Responses total and response rate
- It changes the opportunity stage probability
- It locks the campaign to a single price book
Correct answer: Members with that status are counted in the campaign's Responses total and response rate
Marking a member status value as Responded causes members assigned that status to be tallied in the campaign's Responses statistic and to factor into the response rate, which is how marketers measure engagement. The flag does not remove members, alter opportunity probability, or tie the campaign to a price book, since those are unrelated functions.
- A web administrator sets up Web-to-Lead and wants to be confident a form submission was received even if processing is delayed. Which Web-to-Lead feature provides this assurance to the submitter or the company?
- A roll-up summary field on the lead
- An organization-wide default of Private
- A custom price book entry for the lead
- An auto-response rule that emails a confirmation when the lead is created
Correct answer: An auto-response rule that emails a confirmation when the lead is created
Auto-response rules can send a templated confirmation email when a Web-to-Lead record is created, assuring the submitter their request was received. A roll-up summary field aggregates child data, an organization-wide default sets baseline access, and a price book entry is pricing data, so none of those confirms receipt of a web form submission.
- An administrator is concerned that Web-to-Lead could be abused to flood the org with junk leads from automated bots. Which built-in safeguard helps limit and validate Web-to-Lead submissions?
- Setting a custom price book for inbound leads
- Enabling the reCAPTCHA (spam filtering) option and the daily Web-to-Lead request limit
- Adding the leads to a campaign member status
- Mapping the lead to an opportunity stage
Correct answer: Enabling the reCAPTCHA (spam filtering) option and the daily Web-to-Lead request limit
Web-to-Lead supports a reCAPTCHA spam-filtering option to verify human submitters, and Salesforce enforces a daily Web-to-Lead request limit, both of which curb bot-driven junk leads. A price book, campaign member status, and opportunity stage relate to pricing, marketing tracking, and pipeline configuration, so none of those protects a web form from spam.
- A rep adds a product to an opportunity, and the line item shows a Sales Price that the rep then changes to offer a discount. How does Salesforce treat the original price defined in the price book versus the edited line price?
- Editing the line price rewrites the price book entry for everyone
- The price book entry supplies the default List Price, while the editable Sales Price on the line item can differ for that opportunity
- The Sales Price cannot be edited once a product is added
- The change updates the standard price book only
Correct answer: The price book entry supplies the default List Price, while the editable Sales Price on the line item can differ for that opportunity
The price book entry provides the List Price that defaults onto the line item, but the Sales Price on that opportunity line item is editable, so a rep can apply a discount without affecting the catalog. Editing the line does not rewrite the price book entry for everyone, the Sales Price is not locked, and it does not change the standard price book, since the override is local to that line item.
- An administrator wants to limit which products certain sales teams can sell by giving each team access to only the relevant subset of products. Which price book capability supports this segmentation?
- Creating custom price books containing only the relevant products and sharing each to the appropriate users
- Adding a validation rule to the Product object
- Changing the opportunity stage probabilities
- Assigning campaign member statuses to products
Correct answer: Creating custom price books containing only the relevant products and sharing each to the appropriate users
Custom price books can each contain a curated subset of products, and sharing a given price book with the appropriate users restricts which products those teams can add to opportunities. A validation rule blocks invalid saves rather than scoping product access, stage probabilities are pipeline math, and campaign member statuses track marketing responses, so none of those segments product availability.
- A rep tries to add products to an opportunity but is prompted to choose a price book first and cannot proceed without one. What does this requirement reveal about how products relate to opportunities?
- Every opportunity must have a campaign before products can be added
- Products are added through price book entries, so an opportunity must be associated with a price book to add line items
- Products require an approval process before they appear
- Opportunities inherit products from the role hierarchy
Correct answer: Products are added through price book entries, so an opportunity must be associated with a price book to add line items
Because products reach an opportunity through price book entries, the opportunity must first be associated with a price book before any product line items can be added. A campaign is not a prerequisite, products do not require an approval process to appear, and the role hierarchy governs record access rather than supplying products, so none of those explains the price book prompt.
- A support team complains that when a case sits in the Tier 2 queue, nobody is officially responsible for it until someone manually accepts it. An administrator wants to confirm what happens to record ownership while a case waits in a queue before an agent takes it. Which statement is accurate?
- The case has no owner at all until an agent accepts it
- The administrator who created the queue automatically owns every case in it
- The most senior agent in the role hierarchy silently owns all queued cases
- The queue itself is the owner of the case until a queue member accepts it and becomes the new owner
Correct answer: The queue itself is the owner of the case until a queue member accepts it and becomes the new owner
The queue owning the case until a member accepts it is correct because a queue functions as a shared owner: the case's Owner is the queue while it waits, and ownership transfers to the individual agent the moment they accept it. A case always has an owner, so the no-owner option is wrong. Queue creation does not make the admin the owner. The role hierarchy governs visibility, not silent ownership of queued records.
- An administrator needs a single change so that whenever any case is closed, an email and a field update both fire automatically as part of finishing that case. Where in Setup does the administrator define these closing actions that are tied specifically to the case-close step?
- In Support Settings and the Closed case actions, including the case close page layout and close-related automation
- In a sharing rule for the Case object
- In the role hierarchy
- In data category visibility settings
Correct answer: In Support Settings and the Closed case actions, including the case close page layout and close-related automation
Support Settings combined with close-specific configuration is correct because Salesforce gives the Case object a dedicated close experience, including a close page layout and the ability to drive automation off the closed state, all managed through case support configuration rather than ad hoc. A sharing rule only grants record access. The role hierarchy controls visibility. Data category visibility governs which Knowledge articles users can browse, not case-close behavior.
- A help desk wants customers who post a question in an online community to be able to convert that community question into a formal case when no peer answer resolves it, so the issue is tracked through support. Which Service capability supports escalating an unanswered community question into a tracked case?
- Web-to-Lead
- A roll-up summary field on the case
- Question-to-Case
- A presence configuration
Correct answer: Question-to-Case
Question-to-Case is correct because it lets moderators or members turn an unresolved question raised in Chatter or an Experience Cloud site into a case so support can formally track and resolve it. Web-to-Lead captures marketing leads from web forms, not support questions. A roll-up summary aggregates numeric child values and cannot escalate a question. A presence configuration governs Omni-Channel agent availability, not question handling.
- An administrator has one active case assignment rule but needs different routing for cases created through the web form versus cases created by Email-to-Case, because each channel has its own rule entries. The administrator notices that when agents manually create a case, the assignment rule does not run unless a checkbox is selected. What governs whether the assignment rule fires on a manually created case?
- The Assign using active assignment rule checkbox on the case edit page, which the agent or the page layout must enable
- The role hierarchy depth of the creating agent
- Whether the case has an attached Knowledge article
- The org-wide default sharing setting for cases
Correct answer: The Assign using active assignment rule checkbox on the case edit page, which the agent or the page layout must enable
The assignment-rule checkbox is correct because manual case creation only triggers the active assignment rule when the Assign using active assignment rule option is selected, which an administrator can preset or default through the page layout. Role hierarchy depth has no bearing on whether the rule runs. An attached article does not control assignment. The org-wide default governs record visibility, not whether assignment rules execute.
- A company wants every case that mentions a billing dispute to be routed to the Finance Support queue, while cases mentioning shipping go to Logistics Support. The administrator is building a single assignment rule with multiple entries. Within one assignment rule entry, what determines which records that entry acts on and where it sends them?
- The agent's presence status at the time of creation
- The data category assigned to the related Knowledge article
- The case's milestone completion percentage
- The entry's criteria or formula plus the user or queue it assigns matching cases to
Correct answer: The entry's criteria or formula plus the user or queue it assigns matching cases to
Criteria or formula paired with a target user or queue is correct because each assignment rule entry is defined by the conditions a case must meet and the owner the matching case is routed to. An agent's presence status affects Omni-Channel routing, not assignment rule entries. The related article's data category controls article browsing. Milestone completion measures SLA progress and has no role in defining an assignment entry.
- An administrator sets up a case escalation rule with two entries: one for Platinum customers escalating after 2 hours and one for all other customers escalating after 8 hours. A Platinum customer's case also matches the second, broader entry. Which entry's escalation timing applies to that case?
- Both entries run and the case escalates twice
- The 8-hour entry applies because it is broader
- The first entry whose criteria the case matches applies, so the 2-hour Platinum entry governs it
- Neither applies because the case matches more than one entry
Correct answer: The first entry whose criteria the case matches applies, so the 2-hour Platinum entry governs it
The first matching entry governing is correct because escalation rule entries are evaluated top to bottom and the first entry whose criteria the case meets controls the escalation, so the order must place Platinum before the catch-all. Cases do not escalate under multiple entries simultaneously. The broader entry does not automatically win. Matching more than one entry does not cancel escalation; evaluation simply stops at the first match.
- After a case escalation rule reassigns an aging case to a senior queue, a support lead asks how the team is notified and what else the rule can do beyond changing the owner at the moment of escalation. Which set of actions can a single escalation rule entry perform when its age threshold is reached?
- Permanently delete the case from the org
- Rewrite the case description with AI-generated text
- Reassign the case and send notification emails to the new owner and other users
- Change the org-wide default sharing model for cases
Correct answer: Reassign the case and send notification emails to the new owner and other users
Reassigning the case and sending notification emails is correct because an escalation rule entry can change the case owner and notify the new owner and additional recipients when the age criteria are met. Escalation rules do not delete cases. They do not rewrite descriptions with generated text. Changing the org-wide default is an org security setting, not an action an escalation rule performs on a case.
- A knowledge manager wants frequently used solution articles to appear at the top of search results and on case pages, and wants to retire articles that are no longer accurate without permanently deleting them so they can be restored or referenced later. Which Knowledge lifecycle state should the manager move an outdated-but-not-disposable article into?
- Archived
- Published
- Draft
- Assigned
Correct answer: Archived
Archived is correct because archiving removes an article from active publication while preserving it so it can be restored or referenced rather than permanently deleted. Draft is the editing state before publication, not a retirement state. Published makes the article live to its channels, the opposite of retiring it. Assigned refers to handing an article to a user for review, not to retiring it from active use.
- An organization wants its public-facing customers to find help articles on their support website while keeping certain internal troubleshooting articles visible only to employees. Which Knowledge configuration controls which audience can see a given article?
- The case assignment rule entries
- The Omni-Channel routing configuration
- The article's roll-up summary field
- The channels the article is published to, such as Internal App, Customer, Partner, or Public Knowledge Base
Correct answer: The channels the article is published to, such as Internal App, Customer, Partner, or Public Knowledge Base
Publishing channels are correct because each Knowledge article is exposed to specific channels, such as Internal App for employees or Public Knowledge Base for anonymous website visitors, controlling which audience can see it. Case assignment rules route cases, not articles. The Omni-Channel routing configuration distributes work to agents. Articles do not have roll-up summary fields, so that option is not a real visibility control.
- A support administrator wants to measure which Knowledge articles agents rely on most and which ones resolve cases, so the content team can improve low-value articles. Which native Knowledge capability captures how often articles are viewed, rated, or linked to cases for this analysis?
- A presence configuration
- Knowledge reports built on article report types such as article views and ratings
- A case close page layout
- A web-to-case HTML form
Correct answer: Knowledge reports built on article report types such as article views and ratings
Knowledge reports using article-related report types are correct because Salesforce provides report types that surface article views, ratings, and case associations so administrators can evaluate which content performs well. A presence configuration manages Omni-Channel availability. A case close page layout controls the close screen, not article analytics. A web-to-case form captures support requests and has nothing to do with measuring article usage.
- An administrator is rolling out the Service Console and wants each agent to land on a workspace where the case list, the open case, and related contact details are visible together, and wants to control which components show in those side regions. Which tool does the administrator use to design the layout of the Service Console record pages?
- A sharing rule
- A duplicate rule
- The Lightning App Builder
- An entitlement process
Correct answer: The Lightning App Builder
The Lightning App Builder is correct because administrators use it to build and arrange the Lightning record pages, including the multi-region layouts and components, that agents see inside the Service Console. A sharing rule grants record access, not page design. A duplicate rule prevents duplicate records. An entitlement process tracks SLA milestones and does not design console pages.
- Agents in the Service Console handle live chat sessions and want a workspace tab to remain pinned with the customer's record open even after the chat ends, so they can finish wrap-up work. An administrator is reviewing how the console keeps an agent's place across work items. Which Service Console behavior allows an agent to keep several customer interactions open at once without reloading the page?
- A roll-up summary that combines the records into one
- Workspace tabs and subtabs that hold multiple records open within a single console session
- A sharing rule that merges the records
- A data category that groups the records
Correct answer: Workspace tabs and subtabs that hold multiple records open within a single console session
Workspace tabs and subtabs are correct because the Service Console keeps multiple records open simultaneously as primary tabs with related subtabs, letting an agent move between interactions without losing context or reloading. A roll-up summary aggregates numeric values and does not hold records open. A sharing rule grants access rather than keeping tabs open. A data category classifies Knowledge articles, unrelated to console tabbing.
- A contact center director wants Salesforce to evaluate every available agent's current open work and automatically hand the next chat to the agent carrying the lightest load rather than simply rotating through agents in order. Which Omni-Channel routing model meets this requirement?
- Most Available routing only, ignoring how many items each agent already holds
- External routing through a non-Salesforce system
- A case escalation rule based on business hours
- Least Active routing, which sends new work to the available agent with the fewest open work items
Correct answer: Least Active routing, which sends new work to the available agent with the fewest open work items
Least Active routing is correct because it compares agents' current open work and routes the next item to the one with the lightest active load, balancing the team. Most Available routing measures remaining capacity differently and is not described by lightest current load alone. External routing offloads decisions to a third-party system, which is not what the director wants. A business-hours escalation rule handles aging cases, not live workload balancing.
- A support supervisor wants a live view of which agents are online in Omni-Channel, how much work each is carrying, and what is waiting in the queue, so the supervisor can reassign work or coach agents in the moment. Which Service feature gives the supervisor this real-time operational view?
- A static report run nightly on case counts
- Omni Supervisor, the real-time dashboard of agent presence, workload, and queue backlog
- A validation rule on the Case object
- The case close page layout
Correct answer: Omni Supervisor, the real-time dashboard of agent presence, workload, and queue backlog
Omni Supervisor is correct because it gives supervisors a live monitoring view of agent presence statuses, current assigned work, and queue backlog, and lets them reassign or raise work in real time. A nightly static report is historical, not real-time. A validation rule blocks invalid saves and shows nothing about live workload. The case close page layout controls the close screen, not supervisor monitoring.
- An administrator wants sales reps to filter and view a saved set of records, such as all open opportunities closing this quarter that they own, directly from the Opportunities tab without running a report. Which Salesforce feature provides this saved, filterable display of records?
- A custom report type
- A list view
- A dashboard component
- A page layout
Correct answer: A list view
A list view is the correct feature. List views let users save a filtered, sortable display of records for an object directly on its tab, so reps can quickly see records matching criteria like open opportunities they own closing this quarter without building or running a report. A report is a separate analytics tool, a dashboard component visualizes summarized data, and a page layout controls a single record's detail screen rather than a list of records.
- An administrator creates a list view on the Account object and wants it available to all internal users but read-only so users cannot change its filters. When sharing the list view visibility, which option allows the administrator to expose the list view to everyone while keeping it under the administrator's control?
- Share the list view with a specific public group only
- Mark the list view as a personal list view
- Restrict the list view to the running user of a dashboard
- Set the visibility to 'Visible to all users' so it is shared org-wide but only the creator and admins can edit its definition
Correct answer: Set the visibility to 'Visible to all users' so it is shared org-wide but only the creator and admins can edit its definition
Setting the visibility to 'Visible to all users' is correct. List view sharing settings let a creator choose whether a list view is private, visible to all users, or shared with specific groups or roles; choosing 'Visible to all users' exposes it org-wide while the underlying filter definition stays editable only by the creator and administrators. Sharing with one public group would not reach everyone, a personal list view is visible only to its creator, and dashboard running-user settings are unrelated to list view sharing.
- A user wants to perform a quick inline edit on several records at once from a list view, such as updating the Stage on multiple opportunities. Which condition must be true for inline editing directly within a list view to work?
- The list view must be filtered to a single record type and the fields must be editable for that user
- The list view must be a dashboard source report
- The user must own every record displayed in the list view
- The fields must be formula fields so they recalculate automatically
Correct answer: The list view must be filtered to a single record type and the fields must be editable for that user
Requiring a single record type and user-editable fields is correct. Inline editing from a list view works when the list is filtered so all records share the same record type and when the user has edit access to the fields involved, allowing mass inline updates without opening each record. Owning every record is not required as long as the user has edit access through the sharing model, list views are not dashboard sources, and formula fields are read-only and cannot be edited at all.
- An administrator needs reps to send standardized branded emails to customers with consistent wording and merge fields that pull in the recipient's name and account details automatically. Which Salesforce feature should the administrator create so reps reuse this consistent content?
- An auto-response rule
- An email template
- A validation rule
- A Chatter post
Correct answer: An email template
An email template is the correct feature. Email templates store reusable, branded email content with merge fields that automatically insert record data such as the recipient's name and account, so reps send consistent messages without retyping them. Auto-response rules send automated replies to inbound leads or cases rather than letting a rep compose, validation rules enforce data quality at save, and Chatter is an internal collaboration feed, not customer email.
- An administrator is choosing an email template type that lets non-technical users design a rich, formatted layout by dragging in components and images without writing HTML. Which email template type best fits this requirement in Lightning Experience?
- A text-only template
- A Visualforce email template
- A Lightning email template built with the email template builder
- A custom HTML template requiring hand-coded markup
Correct answer: A Lightning email template built with the email template builder
A Lightning email template built with the email template builder is correct. The Lightning email template builder gives non-technical users a drag-and-drop canvas to add rich text, images, and components and to insert merge fields without writing code. Text-only templates have no formatting, Visualforce email templates require developer markup, and a custom HTML template requires hand-coding the markup, none of which meets the no-code drag-and-drop requirement.
- A rep wants the recipient's first name to appear automatically at the top of every email created from a template, populated from the contact's record. Which element of an email template makes this dynamic personalization possible?
- A roll-up summary field
- A sharing rule
- A list view filter
- A merge field
Correct answer: A merge field
A merge field is correct. Merge fields are placeholders in an email template that Salesforce replaces at send time with data from the related record, so inserting the contact's first-name merge field personalizes each email automatically. A roll-up summary aggregates child-record values on a parent, a sharing rule controls record access, and a list view filter narrows which records display, none of which inserts record values into email body text.
- An administrator wants employees to post updates, ask questions, and follow records and people in an internal social feed so teams collaborate inside Salesforce. Which Salesforce feature provides this collaboration capability?
- Chatter
- Web-to-Case
- Salesforce Knowledge
- Sales Path
Correct answer: Chatter
Chatter is correct. Chatter is Salesforce's internal collaboration tool, providing feeds, groups, posts, comments, and the ability to follow records and people so teams communicate and share updates inside the platform. Web-to-Case captures cases from web forms, Salesforce Knowledge is an article repository, and Sales Path guides reps through opportunity stages, none of which provides a social collaboration feed.
- An administrator creates a Chatter group intended only for a confidential project team, so that membership requires approval and posts are not visible to other employees. Which type of Chatter group should the administrator create?
- A public group
- An unlisted broadcast-only group with open membership
- A private group
- An archived group
Correct answer: A private group
A private group is correct. A private Chatter group restricts membership to approved members and hides its posts and files from non-members, which fits a confidential project team. A public Chatter group lets anyone join and see posts, an open-membership group would not restrict who joins, and archiving a group simply makes it read-only rather than controlling who can see or join it.
- A manager wants to be notified in their Chatter feed whenever a specific high-value opportunity record changes its Amount or Stage, without checking the record manually. What should the manager do to receive these record updates in their feed?
- Create a list view filtered to that opportunity
- Add the opportunity to a public group
- Follow the opportunity record in Chatter
- Assign themselves as the dashboard running user
Correct answer: Follow the opportunity record in Chatter
Following the opportunity record in Chatter is correct. When a user follows a record, tracked field changes and posts on that record appear automatically in the user's Chatter feed, so the manager sees Amount or Stage updates without revisiting the record. A list view shows records in a list but does not push feed notifications, adding a record to a group is not how record tracking works, and a dashboard running user controls dashboard data visibility, not feed follows.
- An administrator wants a sales rep to keep a to-do reminder with a due date to follow up with a prospect next week, and separately to schedule a meeting that has a specific start and end time. Which two activity types correspond to these needs?
- A task for the follow-up reminder and an event for the scheduled meeting
- An event for the follow-up reminder and a task for the scheduled meeting
- A Chatter post for both
- A case for the follow-up and an opportunity for the meeting
Correct answer: A task for the follow-up reminder and an event for the scheduled meeting
A task for the follow-up and an event for the meeting is correct. In Salesforce activity management, a task represents a to-do item with a due date such as a follow-up reminder, while an event represents a calendared item with a specific start and end time such as a scheduled meeting. Reversing the two mislabels the activity types, Chatter posts are collaboration messages rather than activities, and cases and opportunities are business objects, not activity records.
- An administrator notices that completed tasks and past events logged against a contact no longer appear in the open activity area but are still retained for history. Where do these completed activities appear on the record?
- In the Activity History related list
- In the Open Activities related list
- Only in a custom report and nowhere on the record
- In the record's page layout header
Correct answer: In the Activity History related list
The Activity History related list is correct. Once a task is completed or an event's date passes, the activity moves from Open Activities to the Activity History related list, which retains logged calls, completed tasks, and past events on the record. Open Activities holds only pending items, completed activities remain visible on the record rather than only in a report, and the page layout header shows record fields, not the activity timeline.
- A team wants newly created tasks to be assigned to a group of reps so any available rep can take ownership, similar to how unassigned work is pooled. Which configuration lets a task be owned by a shared pool of users rather than a single named user?
- Assign the task to a queue enabled for the Task object
- Assign the task to a public group used only for Chatter
- Assign the task to a role in the role hierarchy
- Assign the task to a dashboard folder
Correct answer: Assign the task to a queue enabled for the Task object
Assigning the task to a queue enabled for the Task object is correct. Queues can be enabled for tasks so a task is owned by the queue and any queue member can take ownership, pooling the work across reps rather than naming one owner. A Chatter public group is for collaboration and cannot own activity records, a role defines hierarchy access rather than ownership of a task, and a dashboard folder organizes dashboards, not tasks.
- A service organization wants to deploy an autonomous AI assistant that can independently reason over a customer's question, decide which actions to take, and resolve common support cases in a self-service channel without a human agent driving each step. Which Salesforce capability is designed for this use case?
- A record-triggered flow on the Case object
- Agentforce agents
- A case assignment rule routing to a queue
- An email template with merge fields
Correct answer: Agentforce agents
Agentforce agents are designed for this because an Agentforce agent autonomously reasons over a request, selects the appropriate actions, and completes tasks such as resolving support cases without a human directing every step. A record-triggered flow runs fixed, predefined logic rather than reasoning autonomously. A case assignment rule only routes a case to a queue or user, and an email template merely formats outbound email, so none of these provide the autonomous, reasoning-driven behavior of an agent.
- An administrator is configuring an Agentforce agent in Agent Builder and needs to define a distinct job the agent can handle, such as 'Process Order Returns,' along with the specific operations the agent can perform within that job. Which two building blocks in Agent Builder represent the job and its operations?
- Profiles and permission sets
- Validation rules and flows
- Topics and actions
- Report types and dashboards
Correct answer: Topics and actions
Topics and actions are correct because in Agent Builder a topic represents a category of work or job the agent can handle, such as processing returns, while actions are the specific operations the agent can execute within that topic, like looking up an order or initiating a refund. Profiles and permission sets govern user security, validation rules and flows are automation features, and report types and dashboards are analytics constructs, so none of those define an agent's jobs and operations.
- Within Agent Builder, what is the role of an action attached to a topic?
- It defines the baseline record access for the agent's data
- It specifies a discrete operation the agent can perform, such as querying a record or running a flow, to fulfill the topic
- It schedules when the agent is allowed to log in
- It groups several agents into a shared work pool
Correct answer: It specifies a discrete operation the agent can perform, such as querying a record or running a flow, to fulfill the topic
An action specifies a discrete operation the agent can perform, such as retrieving a record, invoking a flow, or calling an Apex method, to accomplish what a topic covers. Baseline record access is governed by the sharing model, login scheduling is a security profile control, and grouping work into shared pools describes queues, none of which is what an action does within Agent Builder.
- A marketing administrator wants to create and manage reusable, grounded generative-AI instructions that can be embedded in a Lightning record page to draft a personalized account summary from live Salesforce data. Which Agentforce-related tool should the administrator use to build and manage those instructions?
- Schema Builder
- Flow Builder
- Process Builder
- Prompt Builder
Correct answer: Prompt Builder
Prompt Builder is correct because it is the tool used to create, test, and manage reusable prompt templates that ground generative AI in Salesforce data and can be surfaced on record pages to produce outputs like a personalized account summary. Schema Builder designs the data model, Flow Builder creates automation logic, and Process Builder is a retired automation tool, none of which builds grounded generative-AI prompt templates.
- An administrator building a prompt template in Prompt Builder wants the generated text to reference specific values from the current record, such as the account name and recent cases, instead of generic placeholder content. What is this practice of supplying the prompt with trusted Salesforce data called?
- Grounding the prompt with merge fields and related data
- Escalating the prompt to a queue
- Setting field-level security on the prompt
- Deactivating the prompt template
Correct answer: Grounding the prompt with merge fields and related data
Grounding the prompt with merge fields and related data is correct because grounding supplies the large language model with trusted, record-specific Salesforce data, such as the account name and related cases, so the output is accurate and contextual rather than generic. Escalating to a queue is a case-routing concept, field-level security governs field visibility, and deactivating a template disables it, none of which describes feeding record data into a prompt.
- Leadership asks an administrator to distinguish Einstein generative features from Agentforce when planning their AI roadmap. Which statement most accurately captures the difference?
- Einstein and Agentforce are two names for the identical product with no functional difference
- Einstein only works for sales while Agentforce only works for service
- Einstein features assist a human user with predictions or generated content the user then acts on, while Agentforce provides autonomous agents that can take actions and complete tasks on their own
- Agentforce can only summarize records, while Einstein can take autonomous actions
Correct answer: Einstein features assist a human user with predictions or generated content the user then acts on, while Agentforce provides autonomous agents that can take actions and complete tasks on their own
The accurate distinction is that Einstein features assist a person by surfacing predictions or generated content that the human reviews and acts on, whereas Agentforce delivers autonomous agents that reason and take actions to complete tasks without a human driving each step. Einstein and Agentforce are not the same product, neither is limited to a single cloud, and it is Agentforce, not Einstein, that acts autonomously, so the other choices misstate the relationship.
- A retailer wants to deploy an Agentforce agent on its public help site so shoppers who are not logged in can ask product questions and get answers grounded in the company's knowledge articles. Which type of Agentforce agent fits an unauthenticated, customer-facing channel like this?
- An internal employee-only agent restricted to logged-in staff
- A sharing rule for the Knowledge object
- A dynamic dashboard for the storefront
- A service or customer-facing agent (such as an Agentforce Service Agent) configured for external users
Correct answer: A service or customer-facing agent (such as an Agentforce Service Agent) configured for external users
A service or customer-facing agent configured for external users is correct because Agentforce can deploy agents to public, unauthenticated channels such as a help site to answer customer questions using grounded knowledge. An internal employee-only agent is restricted to authenticated staff and would not serve anonymous shoppers. A sharing rule governs record access and a dynamic dashboard is an analytics feature, neither of which is a deployable customer-facing agent.
- An administrator wants an Agentforce agent to be able to answer customer questions using the company's existing support content, such as how-to articles and policies, so the agent's responses stay accurate and on-brand. Which Salesforce data source should the agent be grounded in to achieve this?
- The Setup Audit Trail
- Login IP ranges
- Salesforce Knowledge articles
- A report folder
Correct answer: Salesforce Knowledge articles
Salesforce Knowledge articles are correct because grounding an Agentforce agent in the Knowledge base lets it draw on the company's vetted support content to produce accurate, on-brand answers. The Setup Audit Trail logs configuration changes, login IP ranges restrict where users can log in, and a report folder organizes reports, none of which is a knowledge source an agent uses to answer customer questions.
- An Agentforce agent occasionally tries to handle requests outside the scope its business owners intended, and the administrator needs to constrain what the agent will and will not do. Where in Agent Builder does the administrator most directly shape this behavior?
- In the topic's instructions, which guide when and how the agent uses that topic
- In the organization-wide default for the related object
- In the company fiscal year setting
- In a public group definition
Correct answer: In the topic's instructions, which guide when and how the agent uses that topic
Topic instructions are correct because they tell the agent when a topic applies and how it should behave while handling that topic, directly shaping and constraining the agent's actions within scope. Organization-wide defaults govern record access, the fiscal year setting drives reporting periods, and a public group is a sharing audience, none of which controls how an agent decides to act on a topic.
- An administrator must decide between assigning a human-assist Einstein feature or building an autonomous Agentforce agent for a new requirement. The requirement is: 'When a rep opens a case, suggest a draft reply that the rep reviews and edits before sending.' Which choice best matches this requirement and why?
- An Agentforce agent, because the task must be completed end-to-end with no human involvement
- An Einstein generative feature, because it produces a suggested draft that a human reviews and acts on
- A validation rule, because it enforces the wording of the reply
- A sharing rule, because it grants the rep access to the case
Correct answer: An Einstein generative feature, because it produces a suggested draft that a human reviews and acts on
An Einstein generative feature best matches the requirement because the rep stays in control and reviews and edits the AI-suggested draft before sending, which is exactly the human-in-the-loop assistance Einstein provides. An autonomous Agentforce agent would be appropriate only if the task were completed without human involvement, which contradicts the requirement. A validation rule enforces data conditions and a sharing rule grants access, neither of which drafts a reply.
- An administrator is configuring an Agentforce agent and wants one of its actions to execute existing, tested business logic that already validates an order and creates a return record. Which approach lets the agent reuse that logic as an action rather than rebuilding it?
- Reference an existing flow as the action the topic invokes
- Add the agent to a sharing rule
- Create a bucket field on the Order object
- Set the agent as the running user of a dashboard
Correct answer: Reference an existing flow as the action the topic invokes
Referencing an existing flow as the action is correct because Agentforce actions can invoke flows, allowing the agent to reuse already-built and tested automation rather than recreating the logic. A sharing rule grants record access, a bucket field categorizes report data, and a dashboard running user controls whose data a dashboard shows, none of which lets an agent action execute existing business logic.
- A company is evaluating where Agentforce delivers the most value across its operation. Which scenario is the strongest fit for an autonomous Agentforce agent rather than a simple workflow automation?
- Automatically setting a field value to today's date whenever a record is created
- Conversing with a customer in natural language to understand an open-ended request, decide which steps to take, and resolve it
- Preventing a record from saving when a required field is blank
- Sending the same templated email to every new lead
Correct answer: Conversing with a customer in natural language to understand an open-ended request, decide which steps to take, and resolve it
Conversing in natural language to interpret an open-ended request, decide the steps, and resolve it is the strongest fit because an autonomous Agentforce agent's value is reasoning over ambiguous, conversational input and dynamically choosing actions. Setting a date field on create, blocking a save on a blank field, and sending a templated email are all deterministic tasks that fixed automation like flows, validation rules, and auto-response rules handle better, so they do not call for an agent.
- A sales operations team wants to compare the total open pipeline amount captured on the first of each month over the past year to analyze how the pipeline has grown. Standard reports only show current values. Which native feature should the administrator configure to capture and report on these point-in-time values over time?
- A dynamic dashboard with a gauge component
- A standard summary report grouped by Close Date
- A reporting snapshot that runs on a schedule and writes report results to a custom object
- A list view filtered to open opportunities
Correct answer: A reporting snapshot that runs on a schedule and writes report results to a custom object
A reporting snapshot is correct. A reporting snapshot lets an administrator capture report data on a scheduled basis and save those results as records in a custom object, so historical point-in-time values can be reported on later. A standard report only reflects current data, a dashboard merely visualizes a report, and a list view does not store historical trends.
- An administrator wants the Tuesday forecast report emailed automatically to themselves and three colleagues every week, with the email reflecting the data each recipient is allowed to see. Which reporting feature delivers a report on a recurring schedule directly to recipients?
- A reporting snapshot
- A report subscription
- A bucket column
- A joined report block
Correct answer: A report subscription
A report subscription is correct. A report subscription lets users schedule a report to be emailed to themselves and other recipients on a recurring frequency. A reporting snapshot writes results to a custom object rather than emailing them, a bucket column groups values, and a joined report combines blocks.
- In the Lightning report builder, an administrator has four filters and needs the logic to read: filter 1 AND (filter 2 OR filter 3) AND filter 4. Which report builder capability lets the administrator define this exact grouping of conditions?
- Filter logic, where the administrator types a custom expression referencing filter numbers and parentheses
- Conditional highlighting on the summary rows
- A bucket field combining the values
- Cross filters applied to each related object
Correct answer: Filter logic, where the administrator types a custom expression referencing filter numbers and parentheses
Filter logic is correct. Filter logic lets an administrator enter a custom expression using the numbered filters together with AND, OR, and parentheses to control precisely how conditions combine. Cross filters relate to child records, buckets categorize values, and conditional highlighting only colors cells.
- A regional manager needs to reassign ownership of 4,000 open Lead records from a departing rep to another rep all at once, without exporting and re-importing. Which native Salesforce capability lets an administrator change the owner of many records of the same type in one action?
- Data Import Wizard
- Mass Transfer Records
- A reporting snapshot
- A duplicate rule
Correct answer: Mass Transfer Records
Mass Transfer Records is correct. The Mass Transfer Records tool in Setup lets an administrator reassign ownership of many records, such as Leads or Accounts, from one user to another in a single operation. The Data Import Wizard loads data rather than transferring ownership, a snapshot stores results, and a duplicate rule manages matches.
- A manager wants a dashboard component that plots total Opportunity Amount by Close Date month so the trend across the year is visible as a continuous trend line. Which chart type best displays a value changing over time?
- Donut chart
- Funnel chart
- Metric component
- Line chart
Correct answer: Line chart
A line chart is correct. A line chart is best for showing how a value changes over a continuous dimension such as time, making month-over-month trends easy to read. A donut shows proportions of a whole, a funnel shows sequential drop-off, and a metric shows a single number.
- A sales director wants a dashboard component that visualizes how many opportunities remain at each successive stage of the pipeline, emphasizing the drop-off from one stage to the next. Which chart type is designed to show progressive reduction through stages?
- Bar chart
- Funnel chart
- Scatter chart
- Gauge chart
Correct answer: Funnel chart
A funnel chart is correct. A funnel chart displays values across ordered stages and is ideal for visualizing the progressive narrowing of records, such as opportunities moving through pipeline stages. A bar chart compares categories without implying sequence, a gauge tracks progress to a target, and a scatter shows correlation.
- An administrator builds a dashboard and wants viewers to be able to change a single control at the top so the same components instantly show data for only the Western region or only the Eastern region. Which dashboard feature provides this interactive narrowing across components?
- A bucket column on the source report
- Field-level security
- A dashboard filter
- A reporting snapshot
Correct answer: A dashboard filter
A dashboard filter is correct. A dashboard filter lets viewers select a value that simultaneously narrows the data shown across the dashboard's components without editing the underlying reports. A snapshot stores historical data, a bucket groups values within one report, and field-level security governs field visibility.
- An administrator needs the underlying row-level data of a report, including every column for thousands of records, delivered as a file for analysis in a spreadsheet. From the report, which action produces this output?
- Export the report's details to a file such as CSV or Excel
- Apply conditional highlighting
- Add a summary formula to the report
- Subscribe to the report
Correct answer: Export the report's details to a file such as CSV or Excel
Exporting the report's details is correct. The export action on a report generates a file, such as CSV or Excel, containing the report's row-level data for use elsewhere. Subscribing emails the report on a schedule, a summary formula adds a calculation, and conditional highlighting only colors cells.
- An administrator configures Data Loader to update 200,000 Account records and wants the job to process records in larger groups to finish faster while staying within governor handling. Which Data Loader setting controls how many records are sent to Salesforce in each chunk?
- The field mapping file
- The upsert operation
- The batch size setting
- The external ID field mapping
Correct answer: The batch size setting
The batch size setting is correct. Data Loader's batch size controls how many records are grouped into each batch sent to Salesforce during a load, affecting throughput and processing. The external ID mapping is for matching, upsert is an operation type, and the mapping file aligns columns to fields.
- A user reports that a Contacts report shows numbers slightly different from a colleague's, and the administrator wants the report's grouped subtotals updated to use the most recent saved data. After changing source records, which simple action refreshes a report's results to reflect current data?
- Create a new custom report type
- Click Run or Refresh on the report
- Add a cross filter
- Schedule a reporting snapshot
Correct answer: Click Run or Refresh on the report
Running or refreshing the report is correct. A report queries live data each time it is run, so clicking Run or Refresh updates its results to reflect current record values. Creating a report type changes available fields, a snapshot captures history, and a cross filter narrows by related records.
- An administrator must update existing Opportunity records and is choosing the Data Loader operation. They have the Salesforce record IDs in the file and want to change field values on those exact records, with no new records created. Which operation is appropriate?
Correct answer: Update
Update is correct. The Update operation in Data Loader modifies existing records matched by their Salesforce record ID and never creates new records. Insert only creates records, upsert both creates and updates based on a matching field, and export pulls data out.
- A manager wants a report listing Accounts that have related Cases but only those whose related Cases include at least one with Priority equal to High. Which report builder feature filters parent records based on conditions applied to their related child records?
- A summary formula
- A bucket column
- A cross filter with a subfilter on the related object
- A row-level formula
Correct answer: A cross filter with a subfilter on the related object
A cross filter with a subfilter is correct. A cross filter lets an administrator include or exclude parent records based on their related child records, and a subfilter adds conditions on those child records, such as Priority equals High. A bucket categorizes values, and the two formula types compute numbers rather than filter related records.
- An administrator wants a report that limits Opportunities to those closing within the next 30 days without hardcoding specific dates, so it stays accurate as time passes. Which approach should be used in the report filter?
- A bucket column on Close Date
- A reporting snapshot
- Conditional highlighting on Close Date
- A relative date filter such as NEXT N DAYS on Close Date
Correct answer: A relative date filter such as NEXT N DAYS on Close Date
A relative date filter is correct. Relative date values such as NEXT N DAYS let a report filter dynamically by a rolling window relative to today, so it remains accurate over time without editing fixed dates. A bucket groups values, a snapshot stores history, and conditional highlighting only colors output.
- An administrator wants to enable reporting on how a specific picklist field's value has changed over time, such as a sequence of Stage changes, using a dedicated history-tracking report. What must be enabled on the object first so this history becomes available to report on?
- Field history tracking on the object's fields
- A reporting snapshot
- A duplicate rule
- A dashboard filter
Correct answer: Field history tracking on the object's fields
Field history tracking is correct. Enabling field history tracking on an object records changes to selected fields, which then become reportable through a history report type. A reporting snapshot captures whole-report results, a duplicate rule manages matching, and a dashboard filter narrows dashboard views.
- An administrator notices a dashboard component shows stale numbers and learns the dashboard caches its last run. Leadership wants the figures recalculated automatically each morning before they arrive. Which capability recomputes a dashboard's data on a recurring schedule?
- A scheduled dashboard refresh
- A bucket field on the source report
- A row-level formula on the source report
- Field-level security on the components
Correct answer: A scheduled dashboard refresh
A scheduled dashboard refresh is correct. Scheduling a dashboard refresh causes Salesforce to rerun the dashboard's source reports and update its components automatically at the set time. A row-level formula and bucket field operate within a report, and field-level security governs field visibility.
- An administrator must load 90,000 records into a custom object that the Data Import Wizard does not support, mapping fields from a CSV and inserting them. Considering the wizard's record limit and object support, which native tool should the administrator use instead?
- Mass Transfer Records
- Data Import Wizard
- A reporting snapshot
- Data Loader
Correct answer: Data Loader
Data Loader is correct. Data Loader supports custom objects and large volumes well beyond the Data Import Wizard's lower record ceiling, making it the appropriate choice for inserting 90,000 records into a custom object. The wizard is limited in both volume and object coverage, Mass Transfer reassigns ownership, and a snapshot stores report results.
- An administrator wants to automatically share every Opportunity whose Stage equals 'Closed Won' with a public group, regardless of who owns the record. The org-wide default for Opportunity is Private. Which type of sharing rule should the administrator create?
- A permission set that grants View All on Opportunity
- An owner-based sharing rule that shares records owned by a role
- A manual share added by each record owner
- A criteria-based sharing rule that shares records matching the field value condition
Correct answer: A criteria-based sharing rule that shares records matching the field value condition
A criteria-based sharing rule is correct because it shares records based on field values, such as Stage equals Closed Won, rather than on record ownership. An owner-based rule shares by who owns the record, manual sharing is one record at a time, and View All would expose all opportunities, not just the matching ones.
- An administrator needs users in a specific profile to be able to log in to Salesforce only between 7 a.m. and 7 p.m. on weekdays, with logins blocked at all other times. Which profile-level setting enforces this time-based restriction?
- Session Settings in the profile
- Login IP Ranges on the profile
- Login Hours on the profile
- Business Hours under Company settings
Correct answer: Login Hours on the profile
Login Hours on the profile is correct because it defines the days and times during which the profile's users are allowed to log in, blocking access outside that window. Login IP Ranges restrict by network address, session settings govern timeout behavior, and Business Hours drive case escalation timing, not login restrictions.
- An administrator must group several support agents so that incoming cases can be routed to the whole team for any member to pick up and take ownership of records. Which Salesforce construct is designed to own records collectively until a member accepts them?
- A public group
- A queue
- A role
- A permission set group
Correct answer: A queue
A queue is correct because it can own records such as cases or leads collectively, holding them until a member accepts ownership. A public group is used as a sharing audience and does not own records, a role positions users in the hierarchy, and a permission set group bundles permissions.
- An administrator wants a single, branded login URL for the org such as mycompany.lightning.force.com so the company can customize the login page and enable certain single sign-on features. Which Setup feature provides this custom org subdomain?
- Communities sharing settings
- Sites
- My Domain
- Remote Site Settings
Correct answer: My Domain
My Domain is correct because it gives the org a custom, branded subdomain in login and application URLs and is a prerequisite for features like a customized login page and certain single sign-on options. Sites and Communities serve external pages, and Remote Site Settings authorize outbound callouts.
- An administrator needs to review a chronological list of recent configuration changes, including who modified profiles, security controls, and metadata, to investigate an unexpected setting change. Which tool provides this record of administrative changes?
- Debug Logs
- Field History Tracking
- Login History
- Setup Audit Trail
Correct answer: Setup Audit Trail
Setup Audit Trail is correct because it logs recent setup and configuration changes along with the user who made them and the date, making it the tool for investigating administrative changes. Field History Tracking records data field changes on records, Login History tracks authentication events, and Debug Logs capture code execution.
- An administrator wants to define org-wide network addresses from which users can log in without receiving an identity verification challenge, while still allowing logins from elsewhere after verification. Where is this configured at the org level?
- Login IP Ranges on each profile
- Trusted IP Ranges in Network Access under Session Settings
- Organization-Wide Defaults in Sharing Settings
- Login Hours on each profile
Correct answer: Trusted IP Ranges in Network Access under Session Settings
Trusted IP Ranges in Network Access is correct because it defines org-wide addresses from which users can log in without an identity verification challenge, while still permitting logins elsewhere after verification. Profile Login IP Ranges strictly block addresses outside the range, OWD governs record visibility, and Login Hours control timing.
- An administrator wants to assess the org's security posture by comparing its password policies, session settings, and other controls against Salesforce-recommended baselines, receiving a score and remediation guidance. Which Setup tool provides this assessment?
- Security Center licensing
- Optimizer
- Setup Audit Trail
- Health Check
Correct answer: Health Check
Health Check is correct because it compares the org's security settings against a Salesforce baseline, returning a percentage score and identifying high-risk settings to remediate. Optimizer reports on general org health and limits, Setup Audit Trail lists configuration changes, and it is not the security baseline scoring tool.
- After deactivating a user who has left the company, an administrator notices the deactivated user is still listed as the owner of dozens of open opportunities. What is the standard administrative step to keep those records actively managed?
- Reassign ownership of the records to an active user
- Reactivate the user so the records have an active owner
- Delete the records because a deactivated owner invalidates them
- Freeze the user to transfer ownership automatically
Correct answer: Reassign ownership of the records to an active user
Reassigning ownership to an active user is correct because deactivation does not remove a user as record owner, so open records should be transferred to keep them managed and visible through normal sharing. Reactivating consumes a license unnecessarily, records are not invalidated or deleted, and freezing only blocks login without moving ownership.
- An administrator must decide between freezing and deactivating a user who is suspected of a security issue but whose status is still under review. Why might the administrator freeze rather than deactivate the user?
- Freezing permanently removes the user and frees the license right away
- Freezing blocks login immediately even when deactivation is temporarily blocked by dependencies, and it does not free the license
- Freezing reassigns all of the user's records automatically
- Freezing deletes the user's login history for privacy
Correct answer: Freezing blocks login immediately even when deactivation is temporarily blocked by dependencies, and it does not free the license
Freezing is correct because it immediately blocks the user from logging in even when deactivation cannot complete due to dependencies such as workflow ownership, and it does not release the license. Freezing does not delete the user, reassign records, or remove login history.
- An administrator created a permission set granting access to a feature that requires a special license, but the assignment fails for some users. What must be true for those users to receive the permission set?
- Each user must have the required permission set license assigned before the permission set can be assigned
- Each user must have the System Administrator profile
- The org-wide default for the related object must be Public
- The permission set must be added to a public group
Correct answer: Each user must have the required permission set license assigned before the permission set can be assigned
Having the required permission set license assigned first is correct because some permission sets depend on a specific permission set license, which must be on the user before the permission set can be assigned. The admin profile is unrelated, OWD governs records not assignment, and permission sets are not added to public groups.
- An administrator needs to enforce that, after several failed login attempts, a user account is locked for fifteen minutes before another attempt is allowed. Where is this lockout behavior configured?
- In Session Settings under timeout values
- In Password Policies, which include the lockout threshold and lockout duration
- In Login Hours on the profile
- In Organization-Wide Defaults
Correct answer: In Password Policies, which include the lockout threshold and lockout duration
Password Policies is correct because the maximum invalid login attempts and the lockout effective period are defined there alongside complexity and expiration rules. Session Settings control timeouts and clickjack protection, Login Hours restrict timing, and OWD governs record sharing.
- An administrator wants every internal user across all profiles to see a particular custom Lightning app and a standard default landing experience without editing each profile individually for tab visibility. Which approach lets the administrator set tab visibility once and apply it broadly?
- Configure the app's assigned profiles and default tab settings through the Lightning App's profile assignments
- Create a public group containing all users and assign the app to it
- Set the org-wide default for the related object to Public Read/Write
- Use a sharing rule to share the app with all users
Correct answer: Configure the app's assigned profiles and default tab settings through the Lightning App's profile assignments
Managing the Lightning app's profile assignments is correct because tab visibility and app availability are controlled per profile, and assigning the app to the relevant profiles applies it across those users. Public groups and sharing rules govern record access, not app or tab visibility, and OWD is unrelated to apps.
- An administrator needs to restrict which users can see records they would otherwise have access to, tightening access for a specific group on a particular object without changing the org-wide default for everyone. Which newer access mechanism is designed to narrow rather than expand access?
- A public group
- A criteria-based sharing rule
- A restriction rule
- An owner-based sharing rule
Correct answer: A restriction rule
A restriction rule is correct because it narrows the records that specified users can access on an object, filtering down access they would otherwise have, rather than opening it up. Sharing rules and public groups only expand or grant access, so they cannot tighten visibility for a subset of users.
- An administrator needs a text field on a custom object that, once a record is saved, can never be changed by anyone, even an administrator with edit rights. Which standard custom field type behaves this way after the initial save?
- An Auto Number field, which is system generated and read-only once the record is created
- A Text field marked as Unique, which still allows manual edits afterward
- A Formula field, which can be recalculated by reopening the record
- A Picklist field set to Required, which only restricts blank values
Correct answer: An Auto Number field, which is system generated and read-only once the record is created
An Auto Number field is the answer because Salesforce assigns its sequential value automatically at record creation and the field is system generated and read-only, so it cannot be edited afterward. A unique Text field still accepts manual edits, a Formula field recalculates rather than locking, and a required Picklist only prevents blanks.
- An administrator wants to display, on a Lightning record page, a single component that shows the entire history of stage changes and field updates for the record in a chronological feed. Which standard Lightning App Builder component surfaces this running list of record activity and posts?
- The Activities component
- The Chatter (Feed) component
- The Path component
- The Related Lists component
Correct answer: The Chatter (Feed) component
The Chatter, or Feed, component is correct because it renders the chronological feed of posts, updates, and tracked field changes on the record page. The Activities component handles tasks and events, the Path component shows guided stage progress, and the Related Lists component displays child records.
- An administrator must let a custom field's value be visible to one profile but completely hidden from another, regardless of which page layout is in use. Which Object Manager setting controls whether a profile can see or edit a field at all?
- Page layout assignment
- Field-Level Security on the field
- Record type assignment
- The compact layout
Correct answer: Field-Level Security on the field
Field-Level Security is the answer because it determines, per profile or permission set, whether a field is visible and editable across all interfaces independent of any page layout. Page layouts only arrange visible fields, record types govern picklist values and processes, and compact layouts control highlight fields.
- An administrator wants a formula field on the Opportunity to return the number of complete years between the Created Date and today. Which built-in approach correctly calculates a whole-year difference in a formula?
- Subtract the two date values directly to get the year count
- Use a date-math expression that divides the day difference and floors the result, such as FLOOR((TODAY() - DATEVALUE(CreatedDate))/365)
- Use the YEAR() function alone on the Created Date
- Concatenate the two dates with the ampersand operator
Correct answer: Use a date-math expression that divides the day difference and floors the result, such as FLOOR((TODAY() - DATEVALUE(CreatedDate))/365)
Dividing the day difference by 365 and applying FLOOR is correct because subtracting two dates yields days, and flooring the quotient gives whole years. Directly subtracting returns days, YEAR() alone returns only the calendar year of one date, and concatenation produces text rather than a number.
- An administrator builds a custom 'Equipment' object and wants its records to appear with their own tab and to be searchable across the org. Which option must the administrator select during or after object creation to give the object a navigation tab?
- Enable 'Allow Reports' on the object
- Create a Custom Object Tab for the object in Setup
- Add the object to a roll-up summary field
- Assign the object a record type
Correct answer: Create a Custom Object Tab for the object in Setup
Creating a Custom Object Tab is correct because a custom object needs a tab defined in Setup before it appears in app navigation and gains a dedicated home. Allowing reports affects reporting only, roll-up summaries aggregate child data, and record types control processes rather than navigation.
- An administrator is editing a Lightning record page and wants a component to display only on phones and not on the desktop browser. Which Lightning App Builder capability lets the administrator restrict a component to a specific form factor?
- A component visibility filter using the Device form factor field
- A separate page layout for mobile in Object Manager
- A validation rule referencing the device type
- A compact layout assignment for phones
Correct answer: A component visibility filter using the Device form factor field
A component visibility filter on the Device form factor is correct because Lightning App Builder lets an administrator set conditions, including form factor, that show or hide a component on phone versus desktop. Page layouts do not target form factor this way, validation rules block saves rather than display, and compact layouts only define highlight fields.
- An administrator wants two custom objects linked so that each child relates to one parent, but the relationship requires no special sharing inheritance and the child should keep its own owner. The administrator also needs the lookup to be required on the child. Which fact about a required lookup relationship applies?
- A required lookup still lets the child keep its own owner and sharing while preventing the lookup field from being left blank
- Making a lookup required automatically converts it into a master-detail relationship
- A required lookup forces the child to inherit the parent's sharing like master-detail
- Lookups cannot be made required under any circumstances
Correct answer: A required lookup still lets the child keep its own owner and sharing while preventing the lookup field from being left blank
A required lookup keeping its own owner and sharing while disallowing a blank value is correct because marking a lookup required only enforces that the field is populated; it does not introduce master-detail sharing inheritance. It does not convert to master-detail, does not force inherited sharing, and lookups can indeed be made required.
- An administrator wants the Lightning App Builder canvas for a record page to show distinct tabbed sections, such as 'Details', 'Related', and 'News', each holding its own components. Which Lightning App Builder component creates these in-page tabs?
- The Tabs component
- The Accordion component used as tabs
- The Related Lists component
- The Record Detail component
Correct answer: The Tabs component
The Tabs component is correct because it lets an administrator add labeled tabs on the page, each containing its own set of components. The Accordion component creates collapsible sections rather than tabs, Related Lists shows child records, and Record Detail displays the record's fields.
- An administrator deactivates a custom field's picklist value that is no longer used. Existing records still hold that value. What happens to those existing records after the value is deactivated rather than deleted?
- The records retain the deactivated value, but it is no longer available for new selections
- The records are automatically cleared of the value immediately
- The records are deleted along with the picklist value
- The deactivated value still appears as a selectable option for all users
Correct answer: The records retain the deactivated value, but it is no longer available for new selections
Records retaining the deactivated value while it becomes unavailable for new selection is correct because deactivating a picklist value removes it from future choices but preserves it on records that already use it. The value is not cleared or deleted from records automatically, and it no longer appears as a new selectable option.
- An administrator needs a formula field that returns one of several text outputs based on which of multiple mutually exclusive conditions is true, evaluating them in order. Which formula function is best suited to handle several conditions and return the first matching result?
- The CASE function
- The ISBLANK function
- The VLOOKUP function
- The TRIM function
Correct answer: The CASE function
The CASE function is correct because it evaluates an expression against multiple values and returns the result for the first match, ideal for several mutually exclusive outcomes. ISBLANK only tests for empty values, VLOOKUP retrieves a value from custom object data, and TRIM removes spaces from text.
- An administrator wants a custom object's records to be shareable like top-level objects, with their own owner, sharing rules, and queues. The object currently is the detail side of a master-detail relationship. What must change for the object to gain its own ownership and sharing?
- The master-detail relationship must be converted to a lookup relationship
- A new compact layout must be assigned to the object
- The object's tab must be hidden from all profiles
- A roll-up summary field must be added to the parent
Correct answer: The master-detail relationship must be converted to a lookup relationship
Converting the master-detail relationship to a lookup is correct because detail records in master-detail relationships inherit the parent's ownership and sharing and lack their own; only a lookup lets the object hold its own owner, sharing rules, and queue eligibility. Compact layouts, tab visibility, and roll-up summaries do not affect ownership.
- An administrator opens the Fields & Relationships area of a custom object and wants to reorder where a field appears when users enter data. Which element actually controls the field's position on the data entry screen, rather than the Fields & Relationships list order?
- The page layout (or Dynamic Forms field arrangement)
- The order fields are listed in Fields & Relationships
- The field's API name
- The object's record type
Correct answer: The page layout (or Dynamic Forms field arrangement)
The page layout, or Dynamic Forms arrangement, is correct because field position on the record's data entry screen is determined by where the field is placed on the layout, not by the Fields & Relationships listing. The Fields & Relationships order is administrative only, the API name is an identifier, and record types govern picklist values and processes.
- An administrator wants users to launch a global action that creates a new Event from anywhere in the app via the navigation bar's plus menu, not tied to a specific record page. Which type of action provides this app-wide creation capability?
- A Global Action
- An Object-Specific Action on the Event object only
- A Quick Action limited to the highlights panel
- A roll-up summary action
Correct answer: A Global Action
A Global Action is correct because global actions appear in the navigation bar's quick-create menu and let users perform tasks like creating records from anywhere in the app, independent of a record context. Object-specific and highlights-panel actions live on a record page, and there is no roll-up summary action.
- An administrator creates a formula field that must combine a text field with a number field to produce a label. The save fails with a type mismatch. Which function converts the number so it can be joined with text using the concatenation operator?
- The TEXT function
- The VALUE function
- The ABS function
- The ROUND function
Correct answer: The TEXT function
The TEXT function is correct because concatenating requires both operands to be text, and TEXT converts a number into a string so it can join with the text field. VALUE does the reverse by turning text into a number, ABS returns absolute value, and ROUND adjusts decimal places without changing the data type to text.
- An administrator wants to grant users a button on the Account record page that, when clicked, sends them to an external URL pre-filled with the account's name. Which type of custom button or action allows directing users to a URL using merge fields?
- A URL custom button (or action) using merge fields
- A roll-up summary field
- A field dependency
- A compact layout
Correct answer: A URL custom button (or action) using merge fields
A URL custom button using merge fields is correct because URL-type buttons and actions can construct a destination link that incorporates record field values through merge syntax. Roll-up summaries aggregate data, field dependencies filter picklists, and compact layouts define highlight fields.
- An administrator must allow a custom object to support more than two parent relationships where each parent's deletion should cascade to the child. Given master-detail's two-relationship limit, which approach lets a record cascade-delete from additional parents beyond two?
- Use lookup relationships for the additional parents and rely on automation to delete children, since only two master-detail parents are allowed
- Create a third master-detail relationship, which Salesforce permits without limit
- Convert one master-detail relationship into a roll-up summary
- Add a hierarchical relationship for each extra parent
Correct answer: Use lookup relationships for the additional parents and rely on automation to delete children, since only two master-detail parents are allowed
Using lookups for the extra parents and automating the deletion is correct because an object can be the detail side of at most two master-detail relationships, so cascade behavior beyond two must be achieved with lookups plus automation. A third master-detail is not permitted, roll-up summaries are not relationships, and hierarchical relationships apply only to the User object.
- An administrator is building a record-triggered flow on the Opportunity and wants the flow to run only when records meeting the entry conditions are created or updated, but the org has many Opportunity updates per second. Which Flow optimization should the administrator set so the flow skips evaluation entirely for records that never meet the criteria?
- Add a Pause element at the beginning of the flow
- Define entry conditions on the Start element so the flow only runs for qualifying records
- Convert the flow to a screen flow so users trigger it manually
- Set the flow to run asynchronously for all records
Correct answer: Define entry conditions on the Start element so the flow only runs for qualifying records
Defining entry conditions on the Start element is correct. Entry conditions filter which records launch the flow, so records that never meet the criteria do not execute the flow logic at all, reducing unnecessary processing. A Pause element delays a running flow rather than preventing it from starting, a screen flow requires manual launch, and asynchronous execution changes timing, not whether the flow runs.
- An administrator wants a record-triggered flow to send an outbound message to an external endpoint using a configured Outbound Message action. Which legacy automation feature provides this outbound message capability that an administrator may still configure declaratively?
- A Decision element configured to call the endpoint
- A validation rule with a URL formula
- A report subscription pointing to the endpoint
- Outbound Messages defined in Workflow Actions, which can be invoked from Flow
Correct answer: Outbound Messages defined in Workflow Actions, which can be invoked from Flow
Outbound Messages defined in Workflow Actions are correct. Outbound messages are a declarative workflow action that sends a SOAP message to an external endpoint, and they can be referenced as actions from Flow. A Decision element only branches logic, validation rules block saves, and report subscriptions email reports rather than send integration messages.
- In a record-triggered flow, an administrator adds an Assignment element to set a variable's value before a later Update Records element runs. What is the primary purpose of the Assignment element in this flow?
- To set or change the values of variables and resources within the flow
- To commit changes directly to the Salesforce database
- To branch the flow down different paths
- To pause the flow until a future date
Correct answer: To set or change the values of variables and resources within the flow
Setting or changing the values of variables and resources is correct. The Assignment element manipulates in-memory variables and resources during the flow run. Committing to the database is done by Create or Update Records elements, branching is done by a Decision element, and pausing is done by a Pause element.
- An administrator wants a screen flow to look up an existing Account by name as the user types and let the user pick from matching results on the screen. Which standard screen component provides this type-ahead record selection?
- A Long Text Area input component
- The Lookup screen component bound to the Account object
- A Display Text component
- A Section component
Correct answer: The Lookup screen component bound to the Account object
The Lookup screen component is correct. The Lookup component lets users search for and select an existing record of a specified object directly on a flow screen with type-ahead matching. A Long Text Area captures free text, Display Text shows read-only content, and a Section only organizes other components into columns.
- An administrator must build automation that fires when several records are processed together, and wants the flow to operate efficiently on the whole set rather than once per record. Which characteristic of record-triggered flows helps Salesforce process multiple triggering records efficiently in one transaction?
- Each record must be processed in its own separate transaction manually
- The administrator must write Apex to enable bulk processing
- Record-triggered flows are bulkified automatically by the platform
- Bulk processing requires converting the flow to a scheduled flow
Correct answer: Record-triggered flows are bulkified automatically by the platform
Record-triggered flows being bulkified automatically is correct. Salesforce handles multiple triggering records together so the flow's queries and DML operate in bulk without the administrator coding for it. Records are not forced into separate transactions, no Apex is required for bulkification, and converting to a scheduled flow changes the trigger, not the bulk behavior.
- An administrator is creating a validation rule and wants the rule to block the save only when a custom checkbox field named Approved is unchecked and the Amount exceeds 50000. Which logical structure must the validation rule formula evaluate to in order to fire the error?
- The formula must evaluate to FALSE for the error to display
- The formula must evaluate to TRUE for the error to display and the save to be blocked
- The formula must return a numeric value greater than zero
- The formula must return the field name to highlight
Correct answer: The formula must evaluate to TRUE for the error to display and the save to be blocked
The formula evaluating to TRUE is correct. A validation rule blocks the save and shows its error message whenever its formula evaluates to TRUE. A FALSE result allows the save, validation formulas return Boolean rather than numeric values, and the error location is set separately, not by the formula return.
- An administrator wants a record-triggered flow to skip its scheduled path actions if the record no longer meets a condition by the time the scheduled path executes. Which configuration on the scheduled path lets the administrator re-check conditions before running the path's actions?
- Add a second Start element for the scheduled path
- Change the flow to a before-save flow
- Use a validation rule to cancel the scheduled path
- Set conditions on the scheduled path so it only executes for records still meeting them
Correct answer: Set conditions on the scheduled path so it only executes for records still meeting them
Setting conditions on the scheduled path is correct. Scheduled paths re-evaluate their own conditions when they run, so records that no longer qualify are skipped. A flow has a single Start element, before-save flows cannot have scheduled paths, and validation rules cannot cancel a scheduled flow path.
- An administrator needs an approval process to automatically reassign a pending request to a higher-level approver if the original approver does not respond within two days. Which is the appropriate way to implement this time-based escalation?
- Build a record-triggered flow with a scheduled path that checks whether the request is still pending and then reassigns or escalates it
- Add a validation rule that fires two days after submission
- Configure a standard approval step option that escalates by elapsed time
- Use a workflow field update scheduled for two days to change the approver
Correct answer: Build a record-triggered flow with a scheduled path that checks whether the request is still pending and then reassigns or escalates it
Building a record-triggered flow with a scheduled path is correct. Native approval processes do not provide built-in time-based escalation, so administrators use a flow with a scheduled path to detect a still-pending request and then act on it. Validation rules cannot reassign approvals, no standard approval step escalates by elapsed time, and a field update cannot reroute a pending approval request.
- An administrator is converting a Process Builder process that updates a related record into a flow. Which flow element reproduces the process's ability to update a different, related record rather than the triggering record?
- An Assignment element pointing at the related record
- A Decision element referencing the related record
- An Update Records element configured to find and update the related record
- A Display Text element showing the related record
Correct answer: An Update Records element configured to find and update the related record
An Update Records element configured to find and update the related record is correct. To change a related (non-triggering) record, the flow uses an Update Records element that specifies which records to update by criteria. An Assignment only changes variables in memory, a Decision branches logic, and Display Text only appears in screen flows.
- An administrator builds a screen flow that loops over a collection of selected Contacts and needs to add each processed Contact to a new collection to update them all at once afterward. Which element adds items to a collection variable inside the loop?
- A Create Records element inside the loop for each Contact
- A Decision element that stores the Contact
- A Get Records element that builds the collection
- An Assignment element using the Add operator to append items to the collection variable
Correct answer: An Assignment element using the Add operator to append items to the collection variable
An Assignment element using the Add operator is correct. Inside a loop, an Assignment element with the Add operator appends the current loop item to a collection variable, enabling a single bulk update after the loop. Creating records inside the loop causes per-iteration DML, a Decision only branches, and Get Records retrieves from the database rather than building a collection from loop items.
- An administrator wants to ensure that when a validation rule blocks a record, the user sees a clear, business-friendly explanation rather than a technical message. Where does the administrator define the text the user will see when the rule fires?
- In the field's Help Text property
- In the validation rule's Error Message field
- In the page layout's section header
- In the object's custom setting record
Correct answer: In the validation rule's Error Message field
The validation rule's Error Message field is correct. Each validation rule has an Error Message that displays to the user when the rule's formula evaluates to TRUE. Field Help Text appears as a tooltip regardless of validation, section headers only label layout regions, and custom settings store configuration data, not validation messages.
- An administrator is asked to automate sending a Slack message when a high-priority Case is created. Which type of action can a record-triggered flow invoke to post this message without custom code?
- A validation rule action
- A workflow outbound email alert
- A Slack-related core or invocable action available in Flow Builder's Action element
- A report subscription action
Correct answer: A Slack-related core or invocable action available in Flow Builder's Action element
A Slack-related core or invocable action in the Action element is correct. Flow's Action element can call available actions, including Slack actions, to post messages declaratively. Validation rules only block saves, an email alert sends email rather than a Slack message, and report subscriptions deliver reports on a schedule.
- An administrator must build a flow that runs nightly, but the flow needs to operate on a defined set of records returned by a filter rather than on a single triggering record. In a schedule-triggered flow, what determines which records the scheduled run processes?
- The record that the user is currently viewing
- The record that most recently changed in the org
- The object and filter conditions specified on the schedule-triggered flow's Start element
- A validation rule attached to the flow
Correct answer: The object and filter conditions specified on the schedule-triggered flow's Start element
The object and filter conditions on the Start element are correct. A schedule-triggered flow runs at the set time and processes each record returned by the object and filter conditions defined on its Start element. There is no current user record in a scheduled context, it does not key off the most recent change, and validation rules do not select records for a flow.
- An administrator wants a record-triggered flow's fault path to send an email to the admin team whenever any element in the flow encounters an unhandled error. Which connector should the administrator draw from the data element to route the flow when that element fails?
- A normal connector to the next element
- A loop connector back to the Start element
- A scheduled path connector
- A fault connector from the element to an error-handling path
Correct answer: A fault connector from the element to an error-handling path
A fault connector to an error-handling path is correct. Drawing a fault connector from a data element routes the flow to error-handling logic, such as sending an email, when that element fails. A normal connector handles the success path, there is no loop connector to Start, and scheduled path connectors apply to record-triggered scheduled paths, not fault handling.
- An administrator wants to prevent an infinite loop where a record-triggered flow updates a record, which re-triggers the same flow repeatedly. Which design practice most directly prevents the flow from re-triggering itself unnecessarily?
- Increase the flow's API version
- Add entry conditions or an ISCHANGED-style check so the flow only runs when the relevant field actually changes
- Set the flow to run asynchronously
- Add more screens to the flow
Correct answer: Add entry conditions or an ISCHANGED-style check so the flow only runs when the relevant field actually changes
Adding entry conditions or a change check is correct. Restricting the flow to run only when a relevant field actually changes prevents it from re-triggering itself after its own updates. Changing the API version, running asynchronously, or adding screens does not stop the recursive re-trigger condition.
- An administrator is comparing where to enforce a required-field rule: a validation rule versus making the field required on the page layout. Which statement correctly describes a difference relevant to automation and data integrity?
- Page layout required enforcement applies to API inserts but validation rules do not
- Validation rules only apply to the Salesforce mobile app
- A validation rule enforces the condition for all save paths including API and data loads, while page layout required only applies to that layout's UI
- Both apply identically and there is no difference
Correct answer: A validation rule enforces the condition for all save paths including API and data loads, while page layout required only applies to that layout's UI
The validation rule enforcing all save paths is correct. Validation rules fire regardless of how the record is saved, including API and Data Loader operations, whereas a field marked required on a page layout only enforces entry through that specific layout. The reversed claim is false, validation rules are not limited to mobile, and the two mechanisms differ in scope.
- An administrator needs a record-triggered flow to run additional actions only after the triggering record and its initial save are fully committed, such as creating related records and sending emails. Which run timing should the administrator select for the flow?
- Before the record is saved (before-save)
- After the record is saved (after-save)
- On a schedule unrelated to the save
- Only when launched from a screen
Correct answer: After the record is saved (after-save)
After the record is saved (after-save) is correct. After-save record-triggered flows run once the record is committed and are required for actions like creating related records and sending emails. Before-save flows run prior to commit and cannot perform these actions, a schedule decouples from the save event, and a screen launch is user-initiated rather than record-triggered.
- A knowledge team publishes articles in English but supports customers in French and German, and the administrator wants the same article maintained as language-specific versions that are translated and published separately while staying linked to the master article. Which Lightning Knowledge feature must the administrator enable and configure to support these language-specific versions of an article?
- Article record types, with one record type per language
- Data categories, with one category value per language
- Multiple languages for Knowledge, with a supported language list and assigned translators
- Knowledge promoted search terms, with one term per language
Correct answer: Multiple languages for Knowledge, with a supported language list and assigned translators
Enabling multiple languages for Knowledge is the answer: the administrator turns on Knowledge translation, defines the list of supported languages, and assigns translators or a translation queue so each article can have language-specific versions managed and published separately. Data categories classify content for browsing, record types define content structure, and promoted terms boost search ranking, none of which create translated versions.
- A support team receives duplicate cases when a customer phones in about an issue they already emailed about, and the administrator wants agents to combine the duplicate case records into a single case so the history and related items are consolidated under one record. Which native Service capability lets an agent combine duplicate case records this way?
- Merge Cases
- Case escalation rules
- Case auto-response rules
- Email-to-Case threading
Correct answer: Merge Cases
Merge Cases is the answer: the case merge feature lets an agent select duplicate case records, choose a master, and combine them so related lists and history roll up under the single surviving case. Escalation rules act on aging cases, auto-response rules send creation emails, and email threading keeps replies on one case, so none of those consolidate already-separate duplicate case records.
- An administrator wants sales reps to work in Outlook or Gmail while seeing relevant Salesforce records, and to log emails to Salesforce directly from their mailbox without switching applications. Which Salesforce capability connects the rep's email client to Salesforce for this purpose?
- The Outlook and Gmail integration (email client integration)
- A workflow rule on the EmailMessage object
- A dashboard subscription scheduled to email reps
- A sharing rule applied to the Task object
Correct answer: The Outlook and Gmail integration (email client integration)
The Outlook and Gmail integration is the correct capability. It embeds a Salesforce side panel inside the rep's email client so they can view related Salesforce records and log emails and events to Salesforce without leaving Outlook or Gmail. A workflow rule, dashboard subscription, and sharing rule do not link an external mailbox to Salesforce in this way.
- An administrator wants reps' emails and events to be added to related Salesforce records automatically in the background, so reps no longer have to manually log each interaction. Which Salesforce feature automates capturing this activity data from connected email and calendar accounts?
- Einstein Activity Capture
- Field history tracking
- A validation rule on the Activity object
- The Data Import Wizard
Correct answer: Einstein Activity Capture
Einstein Activity Capture is the correct feature. Once a rep connects their email and calendar, it automatically captures emails and events and associates them with related Salesforce records, removing the need for manual logging. Field history tracking records field changes, a validation rule enforces data entry, and the Data Import Wizard loads records in bulk; none of these auto-capture email and calendar activity.
- An administrator wants to give users a consolidated, prioritized to-do list that pulls together their open tasks across records into one place they can quickly review and reorder. Which Salesforce productivity feature surfaces a user's open tasks in this single prioritized list?
- The To Do List in the utility bar
- A report subscription on the Task object
- A custom report type joining Tasks and Contacts
- A Chatter group dedicated to tasks
Correct answer: The To Do List in the utility bar
The To Do List is the correct feature. It appears in the utility bar and gathers a user's open tasks into one prioritized list they can reorder and act on quickly. A report subscription emails report results, a custom report type defines report structure, and a Chatter group is for feed collaboration; none provide a personal consolidated task list in the utility bar.
- A rep wants to send an email from Salesforce and later see whether the recipient opened it and how many times, so they can time their follow-up. Which Salesforce email capability gives the rep these open insights?
- Email tracking, which records when and how often a sent email is opened
- Feed tracking enabled on the Contact object
- An approval process triggered when an email is sent
- A list view filter scoped to opened emails
Correct answer: Email tracking, which records when and how often a sent email is opened
Email tracking is the correct capability. When enabled, it records when a sent email is opened and how many times, giving the rep insight into engagement to time their follow-up. Feed tracking posts field changes to Chatter, an approval process routes records for sign-off, and a list view filter only displays records; none of these report email-open activity.
- An administrator needs to send the same email to a large group of contacts at once, such as 500 customers, for a one-time announcement. Which Salesforce feature is designed to send a single message to many recipients in one operation?
- List email (mass email to a list view or campaign)
- A single email composed from the Activity timeline
- An auto-response rule on Web-to-Case
- An organization-wide email address
Correct answer: List email (mass email to a list view or campaign)
List email is the correct feature. It sends a single message to all recipients in a selected list view or campaign in one operation, which suits a one-time bulk announcement. A single email from the timeline reaches one recipient, an auto-response rule replies to inbound cases, and an organization-wide email address only defines a shared From address; none send a bulk message to a list.
- An administrator wants to guide reps through the stages of an Opportunity by showing the steps along the top of the record and displaying key fields and guidance for success at each stage. Which Salesforce feature presents this visual stage-by-stage guidance on a record?
- Path
- Activity timeline
- List view chart
- Compact layout
Correct answer: Path
Path is the correct feature. It displays the stages of a record along the top and lets the administrator surface key fields and guidance for success at each stage, helping reps move records forward. The activity timeline shows activities, a list view chart visualizes filtered records, and a compact layout controls highlighted fields; none provide stage-based guidance across a picklist.
- A user wants to indicate they like a coworker's Chatter post and add a brief comment beneath it to continue the conversation in the same thread. Which two Chatter interactions let the user do this directly on an existing post?
- Liking the post and adding a comment to it
- Creating a new record and a validation rule
- Following the user and editing the post's owner
- Sharing a report and scheduling a dashboard
Correct answer: Liking the post and adding a comment to it
Liking the post and adding a comment are the correct interactions. A like signals approval and a comment continues the discussion in the same thread beneath the original post. Creating records, validation rules, following a user, editing ownership, sharing reports, and scheduling dashboards are unrelated to engaging with an existing Chatter post.
- An administrator wants users to be able to share documents inside Salesforce, organize them in libraries, and track different versions of the same file over time. Which Salesforce capability provides this document storage, sharing, and version management?
- Salesforce Files (Files and libraries)
- Field-level security settings
- The Schema Builder
- Record types on the Document object
Correct answer: Salesforce Files (Files and libraries)
Salesforce Files is the correct capability. It lets users upload, share, and organize documents in libraries and maintains version history so older versions are retained as new ones are uploaded. Field-level security controls field access, Schema Builder visualizes the data model, and record types vary page layouts and picklists; none manage shared files and their versions.
- A user wants their colleagues to be able to view their Salesforce calendar so teammates can see when they are available before scheduling meetings. Which Salesforce capability lets a user expose their calendar of events to other users?
- Calendar sharing
- A sharing set on the Account object
- A queue assigned to the Event object
- Field history tracking on Event
Correct answer: Calendar sharing
Calendar sharing is the correct capability. It lets a user share their calendar so other users can view their scheduled events and availability before booking time. A sharing set grants Experience Cloud users record access, a queue pools record ownership, and field history tracking logs field changes; none expose a user's calendar to teammates.
- An administrator wants reps using the Salesforce mobile app at customer sites with poor connectivity to view and edit certain records even when no network is available, syncing changes once they reconnect. Which mobile capability addresses working without a live connection?
- Mobile offline access, which caches records for use without connectivity
- A scheduled flow that runs nightly
- An outbound message to an external endpoint
- A list view filtered to mobile users
Correct answer: Mobile offline access, which caches records for use without connectivity
Mobile offline access is the correct capability. It caches records on the device so reps can view and edit them without a network connection, then syncs the changes once connectivity returns. A scheduled flow, an outbound message, and a list view filter do not enable disconnected use of records on a phone.
- An administrator wants to apply a branded color scheme and the company logo to the Salesforce mobile app so it reflects corporate identity for users on their phones. Where does the administrator configure this mobile visual branding?
- In the Salesforce mobile app branding settings in Setup
- In the compact layout assignment for each object
- In a permission set assigned to mobile users
- In the sharing settings for the Mobile object
Correct answer: In the Salesforce mobile app branding settings in Setup
The Salesforce mobile app branding settings in Setup are correct. There the administrator sets the brand colors and logo so the mobile app reflects corporate identity. A compact layout controls highlighted fields, a permission set grants access, and sharing settings govern record visibility; none control the mobile app's visual branding.
- A user wants their personal Chatter feed to show updates about a coworker's posts and a key account's changes, so those items appear without searching for them. What action should the user take to make these updates flow into their own feed?
- Follow the coworker and follow the account record
- Add the coworker and account to a public group
- Create a list view filtered to the coworker and account
- Assign the coworker and account to a queue
Correct answer: Follow the coworker and follow the account record
Following the coworker and following the account record is the correct action. Following a person or a record subscribes the user so that person's posts and that record's tracked changes appear in the user's Chatter feed automatically. Adding them to a public group affects sharing or membership, a list view only displays records, and a queue pools ownership; none route updates into a personal feed.
- A company already runs a menu-driven Einstein Bot but now wants to replace it with the newer Salesforce product that uses an autonomous agent to handle inbound customer service conversations on digital channels with grounded, reasoning-based responses. Which Agentforce product is purpose-built to serve customers in this service role?
- Agentforce Service Agent
- Einstein Bot Builder
- Service Cloud Voice
- Omni-Channel Supervisor
Correct answer: Agentforce Service Agent
Agentforce Service Agent is correct because it is the prebuilt Agentforce product designed to autonomously handle customer service conversations on digital channels, reasoning over requests and grounding responses, and it is the modern replacement for the menu-driven Einstein Bot. Einstein Bot Builder builds scripted bots, Service Cloud Voice handles telephony, and Omni-Channel Supervisor monitors live human queues rather than running an autonomous agent.
- An administrator wants their Agentforce agent to retrieve answers from a curated set of indexed structured records and unstructured files in Data Cloud, and learns they must first create the Data Cloud object that bundles those sources so the agent can search them at conversation time. Which Data Cloud construct should the administrator set up to package these grounding sources for the agent?
- A validation rule
- A Data Library
- A page layout
- A sharing rule
Correct answer: A Data Library
A Data Library is correct because in Data Cloud it bundles the indexed structured and unstructured sources an Agentforce agent searches for grounding, giving the agent a curated, retrievable knowledge set. A validation rule enforces data entry, a page layout arranges fields on a record, and a sharing rule grants record access, none of which package grounding sources.
- While configuring an Agentforce agent, an administrator wants the agent to pause and ask the customer a clarifying question when a request is ambiguous, rather than guessing which action to run. Where does the administrator most directly express that the agent should gather missing information before acting?
- In the company's password policy
- In the org-wide default sharing settings
- In the topic instructions that guide the agent's behavior
- In a report folder's access level
Correct answer: In the topic instructions that guide the agent's behavior
The topic instructions are correct because they are natural-language directions that shape how the agent behaves within a topic, so telling the agent to ask a clarifying question when information is missing is expressed there. Org-wide defaults govern record visibility, the password policy governs login security, and report folder access controls report sharing, none of which direct agent conversational behavior.
- An administrator building an Agentforce agent sees that Salesforce provides topics already defined for common service jobs out of the box, which can be added to an agent and then refined, instead of authoring every topic manually. What are these ready-made, refinable topics called?
- Record types
- Custom metadata types
- Permission set groups
- Standard topics
Correct answer: Standard topics
Standard topics are correct because Salesforce ships predefined topics for common jobs that an administrator can add to an agent and then customize, accelerating setup compared with authoring custom topics from scratch. Custom metadata types store configuration data, permission set groups bundle permissions, and record types differentiate business processes on an object, none of which are prebuilt agent topics.
- A sales organization wants a prebuilt Agentforce agent that reviews a rep's deals and pipeline and proactively coaches the rep with tailored guidance on how to advance opportunities, rather than engaging customers directly. Which Agentforce sales offering fits this rep-coaching purpose?
- Agentforce Sales Coach
- Agentforce Service Agent
- Einstein Activity Capture
- Salesforce Scheduler
Correct answer: Agentforce Sales Coach
Agentforce Sales Coach is correct because it is the prebuilt sales agent that analyzes a rep's deals and delivers tailored coaching to help advance opportunities, focused on guiding the rep rather than conversing with customers. Agentforce Service Agent handles customer service, Einstein Activity Capture syncs emails and events, and Salesforce Scheduler books appointments, none of which provide AI sales coaching.
- A security team approves Agentforce only if the platform can resist attempts by a customer to trick the agent through cleverly worded messages into ignoring its instructions and revealing restricted information. Which Einstein Trust Layer protection is specifically aimed at defending against these manipulation attempts in the prompt?
- Field history tracking
- Prompt defense
- Login IP ranges
- Duplicate management
Correct answer: Prompt defense
Prompt defense is correct because it is the Einstein Trust Layer protection that hardens prompts against manipulation, helping the agent resist instructions hidden in user input that try to make it ignore its guardrails. Field history tracking logs field changes, login IP ranges restrict where users can log in, and duplicate management prevents duplicate records, none of which defend the prompt from manipulation.
- An administrator is adding an action to an Agentforce agent and wants to control precisely when the agent decides to use that action during a conversation. Which part of the action's configuration tells the agent the circumstances under which it should invoke the action?
- The org's fiscal year settings
- The action's API version number
- The action's instructions describing when to use it
- The action's record-level rollup summary
Correct answer: The action's instructions describing when to use it
The action's instructions are correct because they describe to the agent the circumstances and intent for using the action, guiding the reasoning engine on when to invoke it during a conversation. An API version number governs metadata compatibility, fiscal year settings affect reporting periods, and a rollup summary aggregates child records, none of which tell the agent when to use an action.
- An administrator has built and tested an Agentforce service agent and now needs customers to reach it through the company's enhanced messaging experience, such as WhatsApp or web messaging. After activating the agent, what must the administrator do so customers can actually start conversations with it?
- Add the agent to a report dashboard
- Schedule a nightly data export
- Create a new fiscal period
- Connect the agent to a messaging channel and deployment
Correct answer: Connect the agent to a messaging channel and deployment
Connecting the agent to a messaging channel and deployment is correct because activation alone does not route customers to the agent; it must be wired to the enhanced messaging channel and deployment that customers use to start conversations. Scheduling a data export, creating a fiscal period, and adding it to a dashboard are unrelated to exposing the agent on a customer messaging channel.
- Leadership asks an administrator to forecast costs before scaling an Agentforce deployment, because every agent conversation draws on the org's consumable usage allotment. Which consideration should the administrator factor into capacity planning for Agentforce?
- That Agentforce consumes a usage-based allotment per conversation, so volume affects cost
- That each conversation requires a separate Salesforce org
- That agents only run during scheduled batch windows
- That conversations are free and unlimited regardless of volume
Correct answer: That Agentforce consumes a usage-based allotment per conversation, so volume affects cost
That Agentforce consumes a usage-based allotment per conversation is correct because Agentforce usage is metered, so the volume of agent conversations directly affects consumption and cost and must be planned for. A separate org per conversation is unnecessary, agents respond in real time rather than only in batch windows, and conversations are not free and unlimited, so the other options are inaccurate.
- A revenue team needs a single report that lists each Account alongside its related Opportunities and related Cases, with all three objects shown in separate blocks. Which report format should the administrator use?
- A joined report with multiple report blocks
- A summary report grouped by Account
- A matrix report with row and column groupings
- A tabular report exported to a spreadsheet
Correct answer: A joined report with multiple report blocks
A joined report is correct because it allows multiple report blocks from different report types to be combined in one view, displaying Accounts with their Opportunities and Cases side by side. Summary and matrix reports use a single report type, and a tabular report cannot show multiple object blocks.
- A sales manager wants to automatically receive a report by email every Monday at 7 a.m. without manually running it. What should the administrator configure?
- A report subscription with a Monday schedule
- A dashboard refresh schedule
- A scheduled flow that queries the report
- An email alert tied to a report record
Correct answer: A report subscription with a Monday schedule
A report subscription is correct because it lets a user schedule a report to run and be emailed on a recurring basis, such as every Monday at 7 a.m. Dashboard refreshes deliver dashboards rather than report rows, and flows and email alerts are not the supported mechanism for delivering report results on a schedule.
- In a matrix report grouped by Stage and Region, an administrator needs each Region column to show what percentage each Stage contributes to that Region's total. Which summary formula function should be used?
- PARENTGROUPVAL to reference the column grouping total
- PREVGROUPVAL to reference the prior row value
- ROUND applied to the record count
- A standard roll-up summary on the report
Correct answer: PARENTGROUPVAL to reference the column grouping total
PARENTGROUPVAL is correct because it lets a summary formula reference the value of a parent grouping, enabling a percentage-of-total calculation within each Region column. PREVGROUPVAL compares to a preceding peer grouping, ROUND only rounds a number, and roll-up summaries are object fields, not report functions.
- An administrator wants a report and dashboard to track how the total pipeline Amount changes day over day so trends can be analyzed over the past three months. Which capability should be enabled?
- Historical trend reporting on the Opportunity object
- A standard Opportunity Pipeline report type
- Field history tracking with a related list
- A dynamic dashboard set to the running user
Correct answer: Historical trend reporting on the Opportunity object
Historical trend reporting is correct because it captures daily snapshots of selected fields, allowing administrators to report on how values like pipeline Amount changed over time. A standard pipeline report shows only current values, field history tracking logs individual record changes for audit, and dynamic dashboards control viewing context rather than trending.
- A regional VP should see a dashboard reflecting only her region's data, while the same dashboard shown to other VPs reflects each of their own regions. Which dashboard setting achieves this with one dashboard?
- Set the dashboard to run as the logged-in user (dynamic dashboard)
- Set a fixed running user equal to the VP
- Add a dashboard filter on Region
- Create a separate dashboard for each VP
Correct answer: Set the dashboard to run as the logged-in user (dynamic dashboard)
Setting the dashboard to run as the logged-in user, a dynamic dashboard, is correct because each viewer sees data according to their own access, so each VP sees their own region. A fixed running user would show one person's data to everyone, a Region filter requires manual selection, and separate dashboards defeat the single-dashboard requirement.
- An administrator needs to export all Contact records nightly to an external backup system as CSV files with no manual intervention. Which native tool is best suited?
- Schedule the weekly or monthly Data Export Service
- Run the Data Import Wizard each night
- Use the Mass Transfer Records tool
- Create a list view and click Export
Correct answer: Schedule the weekly or monthly Data Export Service
The Data Export Service is correct because it provides scheduled, automated exports of org data as CSV files on a weekly or monthly basis. The Data Import Wizard loads data in, Mass Transfer Records reassigns ownership, and a list view export is a manual action.
- A report should display only Accounts that do NOT have any related Opportunities. Which report feature should the administrator apply?
- A cross filter set to Accounts without Opportunities
- A bucket field on the Opportunity count
- A row-limit filter set to zero
- A standard filter on Opportunity Amount equals 0
Correct answer: A cross filter set to Accounts without Opportunities
A cross filter set to Accounts without Opportunities is correct because cross filters evaluate the presence or absence of related records, returning Accounts that have no associated Opportunities. A bucket field categorizes existing values, a row limit caps displayed rows, and an Amount filter would still require related Opportunities to exist.
- An administrator wants the same dashboard to let viewers choose between North America, EMEA, or APAC and have all components update accordingly. What should be added?
- A dashboard filter with values for each region
- A separate dynamic dashboard per region
- A cross filter on each source report
- A bucket field grouping regions
Correct answer: A dashboard filter with values for each region
A dashboard filter is correct because it lets viewers select a value, such as a region, that simultaneously refines all compatible components on the dashboard. Multiple dashboards add maintenance, cross filters operate on related-record presence, and bucket fields only categorize values within a single report.
- After loading 50,000 leads, an administrator must update the Lead Source on the same records using a CSV that includes the Salesforce record IDs. Which Data Loader operation is appropriate?
- Update, matched on the Salesforce ID
- Insert, creating new records
- Upsert, matched on the Lead Source field
- Export, to retrieve the records
Correct answer: Update, matched on the Salesforce ID
Update matched on the Salesforce ID is correct because the records already exist and the CSV contains their IDs, so Update modifies them in place. Insert would create duplicates, Upsert is needed only when some records may be new and requires an external ID, and Export retrieves rather than modifies data.
- An administrator builds a report type that should also surface fields from a related child object even when no child records exist. How should the relationship be configured in the custom report type?
- Set the relationship to 'with or without' related records
- Set the relationship to 'each ... must have at least one related record'
- Mark the child object as the primary object
- Use a standard report type instead
Correct answer: Set the relationship to 'with or without' related records
Setting the relationship to 'with or without' related records is correct because it produces an outer-join behavior, returning primary records even when related child records are absent. Requiring at least one related record forces an inner join, making the child the primary object changes the report's focus, and a standard report type may not include the needed combination.
- An administrator wants a dashboard component to display a single Key Performance Indicator, such as total closed-won revenue, as one large number. Which component type is most appropriate?
- A metric (or gauge) component
- A stacked bar chart component
- A table component listing all records
- A funnel component
Correct answer: A metric (or gauge) component
A metric component is correct because it displays a single summarized value prominently, ideal for a KPI like total closed-won revenue. A stacked bar chart compares categories, a table lists multiple rows, and a funnel visualizes progression through stages.
- A user can run a report but sees fewer records than a colleague running the identical report. What is the most likely cause?
- Record-level access differs because of the sharing model
- The report uses a tabular format
- The report has a row limit applied
- The report type is a custom report type
Correct answer: Record-level access differs because of the sharing model
Differing record-level access from the sharing model is correct because reports respect each running user's access, so a user with narrower sharing sees fewer rows than a colleague with broader access. Report format, row limits, and report type affect all users equally rather than producing different counts per user.
- An administrator must reassign all Opportunities owned by a departing sales rep to a new owner in bulk through the user interface. Which native tool is designed for this?
- Mass Transfer Records
- The Data Export Service
- Duplicate Management rules
- A report subscription
Correct answer: Mass Transfer Records
Mass Transfer Records is correct because it is the standard Setup tool for changing ownership of many records, such as a departing rep's Opportunities, at once. The Data Export Service backs up data, Duplicate Management prevents duplicates, and report subscriptions schedule report delivery.
- An administrator needs to give a small group of support agents access to a set of Cases routed for shared handling, with the ability for any member to take ownership. Which construct should be used?
- A queue containing the Case object
- A public group used only in a sharing rule
- A role placed at the top of the hierarchy
- A permission set group
Correct answer: A queue containing the Case object
A queue is correct because it holds records like Cases for a group of users who can view and accept ownership of items from a shared pool. A public group is an audience for sharing but cannot own records, a role governs hierarchy access, and a permission set group bundles permissions rather than routing records.
- An administrator must allow sales reps to be added to specific Accounts with defined access levels so collaborators can edit those Accounts. Which feature provides this on a per-record basis?
- Account Teams
- Role hierarchy
- Organization-wide defaults
- Profiles
Correct answer: Account Teams
Account Teams are correct because they let users be added to individual Accounts with specified access levels for collaboration. The role hierarchy grants access by reporting structure, org-wide defaults set the baseline for all records, and profiles control object and field permissions rather than per-record team access.
- An administrator wants to track who changed the Stage field on Opportunities and when, retaining the old and new values. What should be enabled?
- Field history tracking on the Stage field
- A validation rule on Stage
- The Setup Audit Trail
- A duplicate rule on Opportunity
Correct answer: Field history tracking on the Stage field
Field history tracking is correct because it records old and new values, the user, and the timestamp for changes to selected fields like Stage. A validation rule blocks bad data, the Setup Audit Trail logs administrative configuration changes rather than record data, and duplicate rules prevent duplicate records.
- An administrator needs a clone of production data and metadata for end users to perform user-acceptance testing before a release. Which sandbox type is most appropriate, assuming the org has the necessary license?
- A Full sandbox
- A Developer sandbox
- A Developer Pro sandbox
- A scratch org
Correct answer: A Full sandbox
A Full sandbox is correct because it copies all production metadata and data, making it suitable for user-acceptance testing and performance testing at scale. Developer and Developer Pro sandboxes copy metadata with little or no data, and a scratch org is a source-driven ephemeral environment, not a production copy.
- After building new automation and fields in a sandbox, an administrator must move only those specific components to production. Which native tool moves selected metadata between related orgs?
- A change set
- The Data Loader
- Mass Transfer Records
- The Data Import Wizard
Correct answer: A change set
A change set is correct because it packages selected metadata components and deploys them between a sandbox and its connected production org. The Data Loader, Mass Transfer Records, and the Data Import Wizard all move record data, not metadata such as fields and automation.
- An administrator wants to see how many Salesforce user licenses are available versus used in the org. Where should the administrator look?
- The Company Information page in Setup
- The user's individual detail page
- The Login History report
- The permission set assignment list
Correct answer: The Company Information page in Setup
The Company Information page is correct because it displays the org's purchased and used license counts, including user licenses and feature licenses. A user detail page shows one user's settings, login history shows access events, and permission set assignments show feature grants rather than license totals.
- An administrator must ensure that every user is prompted for a second verification factor when logging in to Salesforce. Which security feature enforces this?
- Multi-factor authentication
- Login IP ranges
- Password complexity policies
- Field-level security
Correct answer: Multi-factor authentication
Multi-factor authentication is correct because it requires users to provide an additional verification factor beyond a password at login. Login IP ranges restrict source addresses, password policies govern password strength and expiration, and field-level security controls access to fields rather than authentication.
- An administrator wants newly created Accounts to be automatically shared with a regional sales team based on the Account's Region field. Which mechanism should be used?
- A criteria-based sharing rule on the Region field
- Manual sharing on each Account
- A queue for the Account object
- An owner-based role hierarchy change
Correct answer: A criteria-based sharing rule on the Region field
A criteria-based sharing rule is correct because it automatically extends access to a group when records meet field criteria such as a specific Region. Manual sharing is one record at a time, queues do not apply to Account ownership routing for sharing, and altering the role hierarchy is broad and not field-driven.
- An administrator needs to delegate the ability to manage users and reset passwords within a specific role's branch to a non-administrator. Which feature provides this scoped capability?
- Delegated administration
- A permission set with Modify All Data
- The System Administrator profile
- A public group
Correct answer: Delegated administration
Delegated administration is correct because it grants limited administrative tasks, such as managing users in specified roles and assigning chosen profiles, without full admin rights. Modify All Data grants org-wide data control, the System Administrator profile is full access, and a public group is a sharing audience.
- An administrator wants the org to use a custom fiscal year that starts in February and includes 4-4-5 week quarters. What must be enabled in Setup?
- Custom fiscal year settings
- Multiple currencies
- The standard fiscal year picklist
- State and country picklists
Correct answer: Custom fiscal year settings
Custom fiscal year settings are correct because they let the org define non-standard periods, such as a February start with 4-4-5 quarters. Multiple currencies handle currency conversion, the standard fiscal year supports only conventional calendars, and state and country picklists standardize address values.
- An administrator must temporarily prevent a user from logging in while preserving the user's record ownership and licenses pending an investigation. What is the best action?
- Freeze the user
- Deactivate the user
- Delete the user
- Reset the user's password
Correct answer: Freeze the user
Freezing the user is correct because it immediately blocks login without freeing the license or removing record ownership, which suits a temporary hold. Deactivation frees the license and ends sessions more permanently, users cannot be deleted in Salesforce, and resetting a password does not block access.
- An administrator wants reps to easily move Opportunities through stages and see guidance and key fields for each stage on the record page. Which feature should be configured?
- Path on the Opportunity object
- A validation rule per stage
- A roll-up summary on Stage
- A Web-to-Lead form
Correct answer: Path on the Opportunity object
Path is correct because it provides a guided, clickable representation of stages with key fields and guidance for success at each step. A validation rule enforces data quality, a roll-up summary aggregates child values, and Web-to-Lead captures leads from external forms.
- A sales leader wants forecast totals split into Pipeline, Best Case, and Commit. Which Salesforce concept maps opportunity stages into these rollups?
- Forecast categories tied to opportunity stages
- Opportunity record types
- Campaign member statuses
- Price book entries
Correct answer: Forecast categories tied to opportunity stages
Forecast categories are correct because each opportunity stage maps to a forecast category such as Pipeline, Best Case, Commit, or Closed, which drives forecast rollups. Record types segment business processes, campaign member statuses track marketing responses, and price book entries define product pricing.
- An administrator needs to record which contacts play which parts, such as Decision Maker or Economic Buyer, on a given Opportunity. Which feature supports this?
- Opportunity Contact Roles
- Account Teams
- Campaign Members
- Related list filters
Correct answer: Opportunity Contact Roles
Opportunity Contact Roles are correct because they associate contacts with an Opportunity and define each contact's role, such as Decision Maker. Account Teams add collaborating users to Accounts, Campaign Members track marketing responses, and related list filters only refine displayed records.
- An administrator wants new web-generated leads automatically assigned to the correct sales queue based on the lead's country. Which tool should be configured?
- Lead assignment rules
- Case escalation rules
- Opportunity contact roles
- Duplicate matching rules
Correct answer: Lead assignment rules
Lead assignment rules are correct because they automatically route incoming leads to users or queues based on criteria such as country. Case escalation rules apply to support cases, opportunity contact roles describe contacts on deals, and duplicate matching rules identify potential duplicates.
- A company sells the same product in both US dollars and euros at different prices for different regions. How should the administrator model this?
- Add separate price book entries with each currency in the appropriate price book
- Create a separate product record for each currency
- Use a formula field to convert prices on the opportunity
- Add a custom currency field on the product
Correct answer: Add separate price book entries with each currency in the appropriate price book
Separate price book entries per currency are correct because a product can have multiple price book entries, each specifying a price in a given currency within a price book. Duplicating products is unnecessary, a formula field cannot replace list pricing, and a custom field does not integrate with standard pricing.
- A sales rep needs to generate a formal, branded document listing products, quantities, and prices that can be sent to a customer for approval. Which Salesforce feature should the administrator enable?
- Quotes related to Opportunities
- Campaign hierarchies
- Web-to-Lead
- Lead conversion mapping
Correct answer: Quotes related to Opportunities
Quotes are correct because they let reps create branded, printable records of proposed products and pricing tied to an Opportunity and send them to customers. Campaign hierarchies organize marketing efforts, Web-to-Lead captures inbound leads, and lead conversion maps lead data into other objects.
- Marketing wants to measure how multiple campaigns contributed to a single closed Opportunity's revenue. Which feature provides this attribution?
- Campaign Influence
- Campaign member statuses
- Web-to-Lead
- Lead scoring
Correct answer: Campaign Influence
Campaign Influence is correct because it links multiple campaigns to an Opportunity and attributes revenue across them. Campaign member statuses track individual responses, Web-to-Lead captures leads, and lead scoring ranks lead quality rather than attributing closed revenue.
- During lead conversion, an administrator wants a custom lead field 'Budget' to populate a corresponding field on the new Opportunity. What must the administrator configure?
- Lead field mapping for conversion
- A validation rule on the Opportunity
- A duplicate rule on Leads
- A roll-up summary on the Account
Correct answer: Lead field mapping for conversion
Lead field mapping is correct because it defines which lead fields, including custom ones like Budget, transfer to the Account, Contact, or Opportunity during conversion. Validation rules enforce data quality, duplicate rules detect duplicates, and roll-up summaries aggregate child records.
- An administrator wants reps to be required to enter a Close Reason whenever an Opportunity is moved to Closed Lost. Which configuration enforces this only at that stage?
- A validation rule referencing the Stage and Close Reason fields
- Making Close Reason universally required on the page layout
- A path key field on every stage
- A duplicate rule on Opportunities
Correct answer: A validation rule referencing the Stage and Close Reason fields
A validation rule referencing Stage and Close Reason is correct because it can require the field only when the Stage equals Closed Lost, enforcing the condition precisely. A page-layout required field applies at all times, a path key field only displays guidance, and duplicate rules address duplicates rather than required entry.
- A support organization must guarantee that a first response is sent within four hours of a Case being created, with milestones tracked against the Case. Which feature supports defining and tracking these service commitments?
- Entitlements with milestones
- Case assignment rules
- Omni-Channel routing
- Web-to-Case
Correct answer: Entitlements with milestones
Entitlements with milestones are correct because they define service-level terms and track time-based milestones, such as a four-hour first response, on Cases. Assignment rules route cases, Omni-Channel distributes work to agents, and Web-to-Case captures cases from web forms.
- An administrator wants website visitors to submit support requests that automatically create Case records in Salesforce. Which feature should be configured?
- Web-to-Case
- Email-to-Case
- Web-to-Lead
- Omni-Channel
Correct answer: Web-to-Case
Web-to-Case is correct because it generates Case records from form submissions on a company website. Email-to-Case creates cases from inbound email, Web-to-Lead creates leads rather than cases, and Omni-Channel routes existing work items to agents.
- A support team wants incoming customer emails sent to support@company.com to automatically create or update Cases. Which feature should the administrator implement?
- Email-to-Case
- Web-to-Case
- A case assignment rule
- A macro
Correct answer: Email-to-Case
Email-to-Case is correct because it converts inbound emails to a designated address into Case records and threads replies onto the case. Web-to-Case uses web forms, an assignment rule only routes cases, and a macro automates repetitive agent actions rather than creating cases from email.
- Support agents repeatedly perform the same set of steps to update a Case status, add a comment, and send a templated email. Which tool lets the administrator package these actions for one-click execution?
- A macro
- A validation rule
- An escalation rule
- A data category
Correct answer: A macro
A macro is correct because it bundles repetitive agent actions, such as updating fields and sending an email, into a single reusable action in the console. A validation rule enforces data, an escalation rule raises priority over time, and a data category classifies Knowledge articles.
- An administrator wants a report that shows each sales rep's total Opportunity Amount as a percentage of the grand total across all reps, displayed directly in the report. Which summary feature provides this?
- A summary formula using the PARENTGROUPVAL function to compare each group's total to the grand total
- A row-level formula that multiplies Amount by Probability
- A bucket column grouping Amount into named tiers
- A cross filter limiting the report to top reps
Correct answer: A summary formula using the PARENTGROUPVAL function to compare each group's total to the grand total
A summary formula with the PARENTGROUPVAL function is correct because it references a summary value at a higher grouping level (the grand total) so each rep group can be expressed as a percentage of the whole. A row-level formula works only on individual rows and cannot reference group totals, a bucket column merely categorizes values, and a cross filter restricts which records appear rather than calculating proportions.
- An administrator needs a dashboard that always shows data filtered to the logged-in viewer's own region without building a separate dashboard per region. Which dashboard capability accomplishes this?
- A dynamic dashboard set to run as the logged-in user
- A dashboard with a single fixed running user set to an executive
- Scheduling the dashboard to refresh nightly
- Placing the dashboard in a private folder
Correct answer: A dynamic dashboard set to run as the logged-in user
A dynamic dashboard set to run as the logged-in user is correct because each person sees data according to their own access and ownership, so regional viewers automatically see only their region. A fixed running user shows everyone the same data through that one user's access, scheduling only controls refresh timing, and a private folder controls who can open the dashboard rather than personalizing its data.
- An administrator wants users in a profile to retain their normal access but additionally be able to manage cases only for the next two weeks during a coverage gap. What is the most appropriate way to grant this temporary access?
- Assign a permission set with an expiration date for the elevated case access
- Edit the base profile to add the case permissions permanently
- Change the organization-wide default for Case to Public Read/Write
- Add the users to a new role higher in the hierarchy
Correct answer: Assign a permission set with an expiration date for the elevated case access
Assigning a permission set with an expiration date is correct because permission set assignments support an expiration so the extra access is automatically removed when the coverage period ends, without altering everyone's baseline. Editing the profile would grant the access permanently to all profile users, changing the org-wide default affects record visibility for the entire org, and moving users up the role hierarchy alters record-sharing rather than feature permissions.
- An administrator wants a brand-new job function to receive a consistent bundle of several permission sets together, so future hires can be granted everything in one assignment. What should the administrator use?
- A permission set group that combines the related permission sets
- A sharing rule applied to the new hires
- A queue that the new hires are members of
- An organization-wide default change for each object
Correct answer: A permission set group that combines the related permission sets
A permission set group is correct because it bundles multiple permission sets so a single assignment grants all of their combined access, simplifying provisioning for a job function. A sharing rule only opens record access between groups of users, a queue is used to own and route records to a team, and an org-wide default sets baseline record visibility rather than packaging permissions.
- A sales team wants opportunities to be created in a specific currency for international deals while still rolling up to a common corporate currency for reporting. Which feature must be enabled?
- Multiple currencies with a designated corporate currency and conversion rates
- Advanced currency management on price books only
- A validation rule requiring a currency code
- A custom currency field on the Opportunity object
Correct answer: Multiple currencies with a designated corporate currency and conversion rates
Multiple currencies with a designated corporate currency is correct because it lets each opportunity store its own currency while Salesforce uses conversion rates to roll amounts up to the corporate currency for reporting. Advanced currency management governs dated exchange rates and does not by itself enable per-record currencies, a validation rule only enforces data entry, and a custom currency field would not convert amounts for reporting.
