Examkin

All practice questions

1784 questions

All types1,784Multiple choice918Multiple select587Matching142Ordering137
Question 221Question →

An administrator at Apex Renewable Solutions is tasked with setting up a dedicated sales pipeline for government contracts, which requires a distinct sequence of opportunity stages compared to the standard commercial sales pipeline. The administrator has already created the new opportunity stage picklist values in the Opportunity object. Which administrative step must be performed next before these new stages can be selected by sales representatives on Opportunity records?

Show answer & explanation

Answer: Create a new Sales Process to select the government opportunity stages, then assign that Sales Process to an Opportunity Record Type.

Answer

Create a new Sales Process to select the government opportunity stages, then assign that Sales Process to an Opportunity Record Type.
In Salesforce Core Administration, the Opportunity object's Stage picklist field relies on a Sales Process to determine which stages appear for specific business processes. When custom stages are created, an administrator must create a Sales Process containing those specific stages, and then assign that Sales Process to an Opportunity Record Type. Once assigned to a record type, users with access to that record type can view and select those stages.

Step-by-Step Solution

1
Identify the relationship between Opportunity Stages, Sales Processes, and Record Types in Salesforce.
Recognize that Opportunity Stage picklist values cannot be filtered directly by Page Layouts or Record Types alone.
Salesforce uses Sales Processes to define custom lifecycles and stage picklist subsets for Opportunities.
2
Determine the required configuration order.
Create stage values in the Stage picklist field -> Create a Sales Process selecting the appropriate stages -> Associate the Sales Process with an Opportunity Record Type.
An Opportunity Record Type requires a Sales Process to determine its valid stage lifecycle.
3
Select the correct administrative action.
The next required step is creating the Sales Process and linking it to the Opportunity Record Type.
This makes the government-specific stages available to users assigned to that record type.

Key Concept

Sales Process and Record Type Linkage for Opportunity Stages
Question 222Question →

An Administrator at Northern Trail Outfitters is building an Opportunity report to evaluate deal velocity across sales regions. The sales leadership team specifies the following requirements for the report:
1. The report must include Opportunities where the Stage is either 'Proposal/Price Quote' or 'Negotiation/Review'.
2. The Opportunity Amount must exceed $100,000, OR the deal Probability must be greater than 75%.
3. The report must exclusively include Opportunities associated with Accounts that have at least one active Support Contract child record.
4. Deals must be categorized into custom market tiers ('Enterprise', 'Mid-Market', 'SMB') based on a custom currency formula field, `Calculated_Annual_Revenue__c`.

When attempting to build the report, the administrator notices that `Calculated_Annual_Revenue__c` is unavailable when creating a Bucket Field, and is unsure how to structure the filters. Which set of actions will successfully fulfill all reporting requirements?

Show answer & explanation

Answer: Set field filter logic to (1 OR 2) AND (3 OR 4) for the stage, amount, and probability filters; add a Cross Filter for Accounts WITH Support Contracts filtered by Status equals Active; and create a Row-Level Formula field on the report to group records into market tiers based on Calculated_Annual_Revenue__c.

Answer

Configure filter logic as (1 OR 2) AND (3 OR 4), apply a Cross Filter of Accounts WITH Support Contracts (Status = Active), and use a Row-Level Formula to categorize the custom formula field.
The correct solution accurately pairs parenthesized filter logic ((1 OR 2) AND (3 OR 4)) with a Cross Filter (Accounts WITH Support Contracts where Status = Active) and leverages a Row-Level Formula because Salesforce Bucket Fields cannot be created directly on formula fields.

Step-by-Step Solution

1
Evaluate Boolean Filter Logic requirement
Filters 1 (Stage = Proposal) and 2 (Stage = Negotiation) must be grouped with OR: (1 OR 2). Filters 3 (Amount > 100k) and 4 (Probability > 75%) must be grouped with OR: (3 OR 4). Combining them requires AND: (1 OR 2) AND (3 OR 4).
Without explicit parentheses, Salesforce evaluates AND operators before OR operators, which alters the intended logic.
2
Evaluate Child Object Filtering requirement
Add a Cross Filter on the Opportunity report: 'Accounts WITH Support Contracts' and add a secondary sub-filter 'Status equals Active'.
Cross Filters allow filtering a primary object based on the presence or absence of related child records and child record attributes.
3
Evaluate Bucketing vs Row-Level Formula requirement
Use a Row-Level Formula field instead of a Bucket Field.
Salesforce Bucket Fields support Picklist, Text, and Number fields, but CANNOT be created on Formula fields. A Row-Level Formula must be created to evaluate `Calculated_Annual_Revenue__c` row by row.

Key Concept

Report Filter Logic, Cross Filters, and Bucket Field Limitations
Question 223Question →

Northern Trail Outfitters uses an executive dashboard to display quarterly sales pipeline metrics. The Salesforce administrator must ensure that regional directors can view the dashboard, but each director must see only the record data they are allowed to access based on their own role and sharing settings. Which two steps should the administrator take to achieve this access model? Select 2 options.

Select all that apply

Show answer & explanation

Answer: Set the dashboard running user setting to run as 'The logged-in user'.; Store the dashboard in a dedicated report and dashboard folder shared with the regional directors with View access.

Answer

To allow regional directors to access the dashboard while ensuring each user only sees data they have permission to view, the administrator must set the dashboard running user to 'The logged-in user' (Dynamic Dashboard) and place the dashboard in a folder accessible to the regional directors with View access.
Configuring the running user as 'The logged-in user' turns the dashboard into a Dynamic Dashboard, ensuring viewers see only data they own or have permission to view via role hierarchy and sharing rules. Additionally, users must be granted folder access to view the dashboard file itself.

Step-by-Step Solution

1
Determine data visibility behavior requirement
Dynamic data filtering per viewer is needed, which requires setting the dashboard running user to 'The logged-in user'.
When a dashboard runs as the logged-in user, each viewer sees data based strictly on their own security settings and record access.
2
Determine dashboard component access requirement
Grant View permissions to the target audience on the containing dashboard folder.
Users must have access to the dashboard folder in order to view the dashboard item in Salesforce.

Key Concept

Dynamic Dashboards and Dashboard Folder Visibility
Question 224Question →

A Salesforce Administrator is building an autolaunched flow to process a collection of Account records. Within a Loop element, the administrator needs to set specific field values on the current loop record variable before adding it to a separate record collection for a bulk update. Which Flow Builder element should be used inside the loop to update the field values of the variable without performing a database transaction?

Show answer & explanation

Answer: Assignment

Answer

The Assignment element should be used inside the loop to update variable field values in memory.
The Assignment element is the correct choice because it alters values of variables in flow memory without making a call to the database. This allows administrators to set field values on loop items safely before accumulating them into a collection variable for a single bulk update outside the loop.

Step-by-Step Solution

1
Identify the requirement to modify variable field values in memory inside a loop.
Recognize that variable manipulation must happen without triggering database transactions (DML).
Executing database operations like Update Records inside a loop violates Salesforce governor limits.
2
Select the appropriate Flow Builder logic element for updating variables.
Choose the Assignment element.
The Assignment element changes the values of flow variables in memory.

Key Concept

Flow Builder Logic Elements and Governor Limits inside Loops
Question 225Question →

A Salesforce Administrator at a renewable energy firm is troubleshooting a Sales Operations Lightning Dashboard designed for regional executives. The dashboard features an interactive filter for "Sales Territory" and a stacked bar chart intended to show opportunity volume by stage across regions. During testing, the administrator notices that the stacked bar chart component displays an error and fails to render, while selecting a territory value in the dashboard filter has no effect on two metric components. Which two underlying configuration issues explain these component and filter failures? (Select 2)

Select all that apply

Show answer & explanation

Answer: The source report powering the stacked bar chart is formatted as a tabular report without any row or column groupings.; The custom field used for the Sales Territory filter is missing from the report types of the two source reports powering the metric components.

Answer

The failures are caused by the source report for the stacked bar chart being a tabular report lacking required groupings, and the Sales Territory filter field being missing from the report types of the source reports powering the unaffected metric components.
The failure of the stacked bar chart is caused by its underlying source report being formatted as a tabular report without groupings; stacked bar charts require a summary or matrix report with at least two groupings. The failure of the dashboard filter to update specific metric components occurs because the field used in the filter is not present in the underlying report types for those reports, preventing the administrator from establishing valid field mapping.

Step-by-Step Solution

1
Analyze why the stacked bar chart component fails to render.
Identify that visual chart components require source reports with groupings (Summary or Matrix formats). Stacked charts specifically require two groupings (X-axis and stacked segment). Tabular reports cannot power charts.
Salesforce dashboard charts derive their axes and groupings directly from report summary rows.
2
Analyze why the Sales Territory dashboard filter fails to update specific metric components.
Determine that dashboard filters must map to a valid field available within each component's source report type.
If a source report type does not contain the filtered field or an equivalent compatible field, the filter cannot be mapped or applied to that specific component.
3
Evaluate the incorrect options regarding limits and user permissions.
Confirm that Lightning dashboards support up to 3 dashboard filters (not 5) and that filtering does not require Modify All Data permissions.
Understanding system governor limits and object-level security prevents misdiagnosing configuration issues.

Key Concept

Dashboard Component Grouping Requirements and Dashboard Filter Field Mapping
Question 226Question →

A Salesforce Administrator is configuring a customer success dashboard containing six components fed by three distinct report types: Accounts with Contracts, Opportunities with Products, and Cases with Assets. The administrator adds a dynamic dashboard filter based on the Account Region field. During testing, four chart components update when a regional filter is applied, but two table components ignore the selection and continue displaying global records. What is the root cause of this behavior, and how should the administrator resolve it?

Show answer & explanation

Answer: The source reports for the two table components do not automatically map to the filter field, requiring the administrator to edit the filter settings and select the equivalent field for those specific components.

Answer

The source reports for the two table components do not automatically map to the filter field, requiring the administrator to edit the filter settings and select the equivalent field for those specific components.
When adding dynamic filters to a dashboard built on multiple report types, Salesforce attempts to auto-map the filter field to equivalent fields in each source report. If an equivalent field is not automatically recognized for a component's source report, the administrator must edit the dashboard filter settings and manually assign the matching field for that component.

Step-by-Step Solution

1
Analyze why dynamic dashboard filters apply to some components while ignoring others.
Dynamic dashboard filters rely on mapping a chosen filter field (e.g., Account Region) to a corresponding field in each component's underlying source report.
When components use different report types, field names or relationships may differ across reports.
2
Identify the configuration steps required when report types differ.
The administrator must open the dashboard filter properties and select the equivalent field for the components that did not automatically map.
If no equivalent field is mapped for a component, that specific component ignores the dashboard filter selection.

Key Concept

Dashboard Dynamic Filter Field Mapping across Multiple Source Report Types
Estimated Time:2m 0s
Question 227Question →

An administrator needs to ensure that a validation rule evaluates only when a user modifies the existing value of the Account Status field on an Account record. Which formula function should the administrator include in the validation rule formula to check whether the field value was updated during the save operation?

Show answer & explanation

Answer: ISCHANGED(Account_Status__c)

Answer

The ISCHANGED function evaluates whether a field's value has changed during the record update transaction.
The formula function ISCHANGED returns true if the field value being evaluated has changed compared to the value currently stored in the database.

Step-by-Step Solution

1
Identify the business requirement
The validation rule must trigger specifically when a user modifies a field value.
Validation rules should only execute when relevant target fields are changed during record editing.
2
Evaluate available formula functions
ISCHANGED returns true if a field's current value differs from its prior saved value.
This function directly checks for record changes in single-field contexts.

Key Concept

Detecting field value modifications in validation rules
Question 228Question →

Northern Trail Outfitters provides SLA-driven customer support with defined resolution target times using Milestones. Support management notices that when support agents change a Case status to 'Waiting on Customer', the milestone target countdown continues to elapse, resulting in false SLA breaches while waiting for customer feedback. What feature should the Salesforce Administrator configure to pause the milestone target timer when a case enters this status?

Show answer & explanation

Answer: Enable Stopped Time on the Entitlement Process and designate 'Waiting on Customer' as a Stopped status on the Case object.

Answer

Enable Stopped Time on the Entitlement Process and designate 'Waiting on Customer' as a Stopped status on the Case object.
Salesforce Entitlement Management includes a 'Stopped Time' feature. When enabled on an Entitlement Process, administrators can flag specific Case status values (like 'Waiting on Customer') as 'Stopped'. When a case enters that status, the countdown clock on active milestones pauses until the case exits the stopped status.

Step-by-Step Solution

1
Identify the standard Service Cloud feature for pausing milestone SLA clocks.
Determine that 'Stopped Time' functionality natively supports pausing milestone countdowns based on Case status.
Standard Entitlement Processes include a built-in mechanism to stop the SLA clock without altering case data manually.
2
Configure the Case object status settings and Entitlement Process.
Mark the 'Stopped' checkbox on the Case Status picklist value and check 'Enable Stopped Time' in the Entitlement Process settings.
This links the specific status to the entitlement process execution so the milestone timer automatically pauses when the status is applied.

Key Concept

Entitlement Process Stopped Time Configuration
Question 229Question →

A Salesforce administrator needs to update 3500035{}000 Account records with new custom category fields. The data operation requires matching existing records by Account Name and Site to prevent duplicate creation, while also suppressing active Workflow Rules from executing during the import. Which data utility should the administrator select to meet these requirements?

Show answer & explanation

Answer: Data Import Wizard, because it supports record matching by Account Name and Site, handles up to 5000050{}000 records, and provides an option to disable workflow rule execution.

Answer

Data Import Wizard, because it supports record matching by Account Name and Site, handles up to 5000050{}000 records, and provides an option to disable workflow rule execution.
The correct answer identifies that the Data Import Wizard is the appropriate tool for this scenario. The job volume of 3500035{}000 records is below the wizard's 5000050{}000 limit. Additionally, the Data Import Wizard supports Account matching by Name and Site to avoid duplicate record creation and includes an explicit configuration option to enable or disable workflow rules during the import process.

Step-by-Step Solution

1
Evaluate record volume requirement
The requirement is 3500035{}000 records, which is within the 5000050{}000 record capacity limit of the Data Import Wizard.
Data Import Wizard supports up to 5000050{}000 records per import job, whereas Data Loader is required for up to 50000005{}000{}000 records.
2
Evaluate object and matching requirements
Accounts are supported by the Data Import Wizard with built-in deduplication matching on Account Name and Site.
Data Import Wizard provides native duplicate matching options for standard objects like Accounts and Contacts based on Name, Site, or Email.
3
Evaluate workflow suppression capability
The Data Import Wizard features a checkbox to enable or disable triggering workflow rules and processes.
Unlike Data Loader, which executes active automation unless manually deactivated in Setup, the Data Import Wizard allows admins to uncheck workflow rule execution during the import process.

Key Concept

Data Import Wizard vs Data Loader capabilities for Account deduplication, volume limits, and workflow suppression
Estimated Time:1m 30s
Question 230Question →

An administrator at a consulting firm needs to secure sensitive files stored within Salesforce Content Libraries. The administrator must ensure that team members can view existing library documents, but are prevented from uploading new file versions into the library and from generating public links to share files with external clients. Which two actions should the administrator perform to enforce these restrictions? (Choose 2 answers)

Select all that apply

Show answer & explanation

Answer: Assign a Library Role that omits the 'Add Content' permission to team members for the specific content library.; Disable the 'Create Public Links' user permission on the profiles or permission sets assigned to team members.

Answer

The administrator should assign a Library Role that omits the 'Add Content' permission to team members for the specific library, and disable the 'Create Public Links' permission on the profiles or permission sets assigned to those users.
Content Library privileges are managed through Library Roles, where removing 'Add Content' stops users from uploading files to the library. System-wide permissions like 'Create Public Links' assigned via profiles or permission sets restrict users from generating external download links.

Step-by-Step Solution

1
Determine how content uploading is restricted within Salesforce Content Libraries.
Library access privileges (such as adding content or managing library settings) are controlled by Library Roles assigned to users or groups within that specific library.
Omitting the 'Add Content' permission from the assigned Library Role prevents users from contributing new files or file versions to that library.
2
Determine how public link generation is restricted across Salesforce Files.
The ability to generate public shareable URLs for files is controlled via user profile and permission set system permissions, specifically 'Create Public Links'.
Disabling 'Create Public Links' on the user's profile or assigned permission sets removes their functional permission to share files externally.

Key Concept

Salesforce Content Libraries permissions and Salesforce Files public sharing controls
Question 231Question →

A support director wants to review customer cases by analyzing total case volume across two dimensions simultaneously: Case Origin along the columns and Escalation Reason along the rows. Which report format should a Salesforce administrator select to organize the data into this grid structure?

Show answer & explanation

Answer: Matrix Report

Answer

The Matrix Report format is required because it supports grouping records simultaneously by both rows and columns.
The Matrix Report format allows grouping data by both rows and columns simultaneously. This creates a grid structure ideal for cross-tabulating metrics like Case Origin against Escalation Reason.

Step-by-Step Solution

1
Analyze the business requirement for data layout.
The requirement specifies grouping data across two distinct axes: Case Origin along columns and Escalation Reason along rows.
Determining the required axes of grouping dictates the appropriate report format.
2
Evaluate Salesforce report format capabilities.
Tabular provides no groupings; Summary provides row groupings only; Matrix provides row and column groupings; Joined provides multi-block reports.
Only Matrix reports support simultaneous row and column matrix summarizations.

Key Concept

Selecting appropriate Salesforce report formats based on grouping requirements.
Question 232Question →

A Salesforce Administrator at Universal Containers needs to categorize Account records into ranges based on Annual Revenue—specifically 'Small' (under 1M),′Medium′(1M), 'Medium' ( 1M to 5M),and′Large′(over5M), and 'Large' (over 5M)—directly inside a report without modifying the schema or creating custom fields. Which reporting feature should the administrator use?

Show answer & explanation

Answer: Bucket Fields

Answer

Bucket Fields allow administrators to quickly categorize report records into defined ranges directly within the report builder without creating custom fields.
Bucket fields allow users to group report rows into custom buckets by field values (such as numeric ranges for Annual Revenue) directly within the report builder, satisfying the requirement without altering object schema.

Step-by-Step Solution

1
Identify the reporting requirement
Categorize records into ranges ('Small', 'Medium', 'Large') directly within the report without creating schema fields.
Creating custom fields for purely ad-hoc reporting needs adds unnecessary administrative overhead.
2
Select the appropriate report builder feature
Choose Bucket Fields on the Annual Revenue column.
Bucket fields enable inline categorization based on defined numeric thresholds.

Key Concept

Report Bucketing
Estimated Time:1m 0s
Question 233Question →

A business operations manager requires a Salesforce analytics solution for reviewing Accounts and their associated Assets. The solution must satisfy three specific criteria:
1. Include all Accounts in the report, including those without any related Asset records.
2. Group the summarized data across two distinct axes: Asset Status along rows and Purchase Calendar Quarter along columns.
3. Ensure any new custom fields added to the Asset object in the future are automatically included in the report builder field palette without requiring manual administrator updates to the report design layout.

Which configuration of report type settings and report format should the administrator implement to meet these requirements?

Show answer & explanation

Answer: Create a Custom Report Type with Accounts as the primary object and Assets as a secondary object using 'with or without' relationship, select the setting to automatically add new custom fields to report layouts, and choose the Matrix report format.

Answer

Create a Custom Report Type with Accounts as the primary object and Assets as a secondary object using 'with or without' relationship, select the setting to automatically add new custom fields to report layouts, and choose the Matrix report format.
To satisfy all requirements: (1) Creating a Custom Report Type with Accounts 'with or without' related Assets performs an outer join, displaying Accounts regardless of Asset presence. (2) Selecting the 'Auto-add new custom fields' option ensures any new fields created on Assets in the future are automatically made available to report builders without manual CRT maintenance. (3) Selecting the Matrix format allows summarizing metrics across two dimensions simultaneously (rows for Asset Status and columns for Purchase Calendar Quarter).

Step-by-Step Solution

1
Determine object relationship requirement for missing child records
Standard report types for Accounts with Assets perform an inner join ('with' relationship), hiding parent Accounts that have no Assets. A Custom Report Type (CRT) must be created specifying 'Each record ("A") may or may not have related ("B") records' (with or without) to ensure all Accounts are included.
Only CRT outer joins retain primary object records when secondary child records do not exist.
2
Determine report layout maintenance settings for future custom fields
In Setup under Custom Report Type field layout settings, enable the option to auto-add new custom fields to existing report layouts.
By default, custom fields added to an object after CRT creation are excluded from the CRT layout unless this auto-add setting is enabled or fields are manually dragged onto the layout.
3
Select appropriate report format for two-dimensional grouping
Select the Matrix report format (or group by both rows and columns in Lightning Report Builder).
Matrix format allows grouping data by both row headers (Asset Status) and column headers (Purchase Calendar Quarter), fulfilling the two-axis summarization requirement.

Key Concept

Custom Report Type outer join definitions, auto-add field layout behavior, and Matrix report format capabilities.
Question 234Question →

Zephyr Aerospace is introducing a dedicated sales pipeline for its Professional Services division that requires a distinct set of Opportunity stages and probability calculations compared to its hardware sales division. Which two administrative actions must the system administrator perform to implement this requirement? (Select 2)

Select all that apply

Show answer & explanation

Answer: Create a new Sales Process and select the specific stage picklist values required for the Professional Services pipeline.; Create a new Opportunity Record Type and associate it with the newly created Professional Services Sales Process.

Answer

The administrator must create a new Sales Process containing the specific stages needed for Professional Services, and then create a new Opportunity Record Type linked to that Sales Process.
To support distinct sales pipelines with unique stages, an administrator must create a custom Sales Process containing the desired stages and then associate that Sales Process with a new Opportunity Record Type.

Step-by-Step Solution

1
Create a custom Sales Process
Defines the specific stage picklist values, open/closed statuses, and probability percentages tailored to the Professional Services sales cycle.
Opportunity stages are master picklist values that must be mapped into a Sales Process to support customized sales lifecycles.
2
Create an Opportunity Record Type
Associates the newly created Sales Process with the Record Type assigned to Professional Services users.
Linking the Sales Process to an Opportunity Record Type exposes the exact stages selected in that process to users when creating or managing records.

Key Concept

Sales Processes and Opportunity Stage Record Type Assignment
Question 235Question →

A Salesforce Administrator at a telecommunications firm is optimizing user interface navigation and field workflows for service representatives. Match each business operational requirement on the left with the correct Salesforce customization tool or action type on the right.

Click a left item, then click its matching right item

Items

Create a new Work Order record directly from an Account record page while automatically populating parent Account field values.
Launch an external carrier diagnostic portal in a new browser tab using dynamic parameters from the current Case record.
Provide users a consistent way to launch a Screen Flow from the global navigation bar across any page in Lightning Experience.
Allow representatives to modify specific fields on the current Case record using a targeted, streamlined overlay window.

Matches

Show answer & explanation

Answer

Each business requirement maps to its optimal Salesforce user interface tool based on context and target functionality: creating a related record with parent default values requires an Object-Specific Create Record Action; launching parameterized external web URLs requires a Custom Detail Page Link; triggering a general Screen Flow across all pages requires a Global Quick Action; and editing fields on the current record via an overlay layout requires an Object-Specific Update Record Action.
The requirement to create related records with pre-populated parent fields maps to Object-Specific Quick Actions (Create a Record). Opening external websites with record tokens maps to Custom Detail Page Links. Invoking general flows without record context maps to Global Quick Actions (Flow). Updating fields on the active record via a streamlined pop-up window maps to Object-Specific Quick Actions (Update a Record).

Step-by-Step Solution

1
Analyze the record context and target outcome for creating related records with field inheritance.
Creating a Work Order from an Account using parent values requires an Object-Specific Quick Action because it maintains relational context and supports Predefined Field Values.
Global actions cannot automatically reference target record field context, making object-specific actions mandatory for parent-to-child data inheritance.
2
Determine the tool for navigating to external web resources with record data tokens.
Constructing dynamic URLs with record merge fields to open external sites points directly to Custom Links.
Custom Links are designed to execute URL navigation and pass merge fields seamlessly into query parameters.
3
Evaluate global versus object-specific scope for screen flows.
A action needed everywhere across Lightning Experience without requiring a specific record context requires a Global Quick Action.
Global Quick Actions can be made available globally via Publisher Layouts in the global header.
4
Select the action type for focused inline record edits via pop-up dialogs.
Editing fields on the record currently being viewed via a specific sub-layout uses an Object-Specific Quick Action of type Update a Record.
Update a Record quick actions provide customized mini-layouts to modify record values without navigating away.

Key Concept

Quick Action Scoping, Action Types, and Custom Web Navigation Tools
Estimated Time:1m 30s
Question 236Question →

An administrator needs to deploy a customized mobile experience with specific navigation tabs for field representatives using the Salesforce Mobile App. Order the sequence of administrative steps required to build, configure, and expose this tailored Lightning App navigation experience to the targeted mobile users.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct administrative sequence begins with accessing App Manager to edit the custom Lightning App, configuring the Supported Form Factors to include 'Desktop and Phone', adding and ordering the desired items under Navigation Items, assigning the designated User Profiles under User Profiles settings, and finally directing users to select the Lightning App within the Salesforce Mobile App Launcher.
The proper administrative order requires modifying the Lightning App in App Manager, setting the form factor to include Phone, customizing navigation items, assigning user profiles, and having users select the app via the mobile App Launcher.

Step-by-Step Solution

1
Access App Manager in Setup
Opens configuration options for the Lightning App.
Customizing app-level mobile navigation begins in App Manager.
2
Set Supported Form Factors to include Phone
Enables the app for Salesforce Mobile App users.
Apps restricted to Desktop will not appear in the mobile App Launcher.
3
Select and sequence Navigation Items
Defines the exact navigation tabs available in the mobile app view.
Navigation Items dictate the mobile navigation bar content for that specific Lightning App.
4
Assign User Profiles
Grants app access to the designated target audience.
Users cannot view or switch to a Lightning App without profile assignment.
5
Select the Lightning App in Mobile App Launcher
Displays the custom tab navigation on the user's mobile device.
Users must actively switch to the configured app in the mobile app launcher to view its custom navigation layout.

Key Concept

Salesforce Mobile App Navigation and Custom Lightning App Deployment
Question 237Question →

An administrator needs to write a validation rule on the Account object. The business requirement states that whenever an existing Account record is updated and its Rating picklist is set to 'Hot', the AnnualRevenue field must be populated with a value greater than 00. If AnnualRevenue is left blank, the validation rule must trigger to prevent saving. Which formula criteria correctly enforces this logic while properly handling blank values?

Show answer & explanation

Answer: AND( NOT(ISNEW()), ISPICKVAL(Rating, "Hot"), OR(ISBLANK(AnnualRevenue), AnnualRevenue <= 0) )

Answer

The correct formula uses AND( NOT(ISNEW()), ISPICKVAL(Rating, "Hot"), OR(ISBLANK(AnnualRevenue), AnnualRevenue <= 0) ) to ensure that updates to existing records evaluate the Rating picklist and explicitly verify both blank state and numerical values for AnnualRevenue.
The formula stating 'AND( NOT(ISNEW()), ISPICKVAL(Rating, "Hot"), OR(ISBLANK(AnnualRevenue), AnnualRevenue <= 0) )' correctly enforces all business constraints: it filters out record creation via NOT(ISNEW()), verifies picklist status with ISPICKVAL(), and robustly catches both null/blank entries and values less than or equal to 0.

Step-by-Step Solution

1
Identify record lifecycle state requirement
Use NOT(ISNEW()) to ensure the rule triggers only during record updates, excluding record creation.
The requirement specifies that the validation rule applies when an existing Account record is updated.
2
Evaluate picklist field condition
Use ISPICKVAL(Rating, "Hot") to check if the Rating picklist field contains 'Hot'.
Validation rules require ISPICKVAL() or TEXT() functions to evaluate picklist values.
3
Construct proper null and value comparison logic
Combine ISBLANK(AnnualRevenue) with AnnualRevenue <= 0 inside an OR() statement.
Numerical comparisons alone do not reliably capture blank or null values; explicit ISBLANK checks prevent formula evaluation errors and bypasses.

Key Concept

Handling null values explicitly in validation rule formulas evaluating picklists and numeric fields
Question 238Question →

A financial services company recently implemented the Salesforce Gmail Integration for its client onboarding group. The team manager requests that three specific specialists be granted the ability to create and edit public Lightning Email Templates for the team, while maintaining read-only access for the rest of the specialists. Which administration approach allows these three specialists to perform these tasks without modifying standard user profiles?

Show answer & explanation

Answer: Create a permission set containing the 'Manage Public Lightning Email Templates' system permission and assign it to the three specialists.

Answer

Create a permission set containing the 'Manage Public Lightning Email Templates' system permission and assign it to the three specialists.
The system permission 'Manage Public Lightning Email Templates' grants users the ability to create, edit, and delete public templates. Using a permission set to assign this permission allows administrators to grant additive capabilities to selected specialists without altering their underlying profile or affecting other users.

Step-by-Step Solution

1
Identify the functional requirement
Three specific users require additive capabilities to create and manage public Lightning Email Templates used within Gmail integration.
Only a subset of users with the same baseline role/profile need extended administrative abilities.
2
Determine the appropriate security component for additive permissions
Use a Permission Set rather than modifying baseline Profiles.
Permission sets allow targeted assignment of system permissions without causing profile proliferation.
3
Select the required system permission
Enable 'Manage Public Lightning Email Templates' in the permission set and assign it.
This specific system permission grants users the authority to create, edit, and delete public Lightning Email Templates.

Key Concept

Selective Permission Assignment via Permission Sets for Lightning Email Templates
Estimated Time:1m 30s
Question 239Question →

An administrator at a renewable energy company builds an executive dashboard containing components based on both Account reports and Opportunity reports. The administrator configures a dashboard filter using the Account Industry field. During testing, selecting an industry value filters the Account-based components, but the Opportunity-based components continue displaying unfiltered data. What action should the administrator take to resolve this issue?

Show answer & explanation

Answer: Edit the dashboard filter properties and manually map the filter to the Account Industry field for the Opportunity source report.

Answer

The administrator must edit the dashboard filter properties and manually map the filter to the Account Industry field for the Opportunity source report.
Dashboard filters apply criteria to components based on mapped fields. When dashboard components rely on reports built from different objects (such as Accounts and Opportunities), Salesforce may not automatically detect which field in the Opportunity report corresponds to the Account Industry filter. Manually editing the dashboard filter settings to map the filter to the Account Industry field available on the Opportunity object ensures all components update correctly when the filter is applied.

Step-by-Step Solution

1
Identify the cause of unfiltered components on a dashboard.
Recognize that dashboard filters require each source report to specify which field corresponds to the dashboard filter.
When source reports use different primary objects (e.g., Accounts vs. Opportunities), automatic mapping may fail if the field relationship is not automatically detected.
2
Navigate to the dashboard filter settings in the Lightning Dashboard Builder.
Access the field mapping configuration for each component using a source report.
Each dashboard filter allows explicit selection of equivalent fields across all underlying source reports.
3
Select the Account Industry field (via the related Account object) for the Opportunity source report component.
All components dynamically update when a user selects an industry filter value.
Manual field mapping ensures the filter criteria are passed correctly to all report types.

Key Concept

Dashboard Filter Field Mapping Across Multiple Source Reports
Estimated Time:1m 30s
Question 240Question →

Cloud Kicks created a customer support analytics dashboard and set the static running user to the VP of Customer Support, who has organization-wide access to all Case records. The dashboard is stored in a public folder shared with Support Representatives who have Read-only access restricted to cases they own. When a Support Representative views this dashboard, which data will be displayed on the dashboard components?

Show answer & explanation

Answer: All case data accessible to the VP of Customer Support, regardless of the viewing agent's record-level sharing permissions.

Answer

All case data accessible to the VP of Customer Support, regardless of the viewing agent's record-level sharing permissions.
In Salesforce, setting a static running user for a dashboard causes all components to display data according to that running user's field- and record-level access settings. Because the VP of Customer Support has access to all cases, any user who can access the dashboard folder will see data based on the VP's access level.

Step-by-Step Solution

1
Identify the dashboard running user configuration.
The dashboard uses a static running user (the VP of Customer Support).
The security context of a static dashboard is determined by the specified running user account.
2
Determine data visibility rules for static running users.
Data is rendered according to the VP's broad access permissions.
Dashboard components execute queries under the security clearance of the running user, bypassing the viewing user's OWD and sharing rules.

Key Concept

Dashboard Static Running User Security Context
PreviousPage 12 / 90Next
All practice questions — Salesforce Certified Administrator | Examkin