All practice questions

1784 questions

Question 701Question

A Salesforce administrator at a global logistics company is configuring Lead Custom Field Mapping to support lead conversion into Account and Contact records. Which two statements correctly describe the rules and system behavior for mapping custom Lead fields during lead conversion?

Select all that apply

Show answer & explanation

Answer: Custom Lead picklist fields can only be mapped to custom picklist fields on the target Account, Contact, or Opportunity objects.; Changing the data type of a custom Lead field that is currently mapped for conversion deletes the existing mapping configuration.

Answer

The correct statements are that custom Lead picklist fields must be mapped to custom picklist fields on target objects, and changing the data type of a mapped custom Lead field deletes its existing conversion mapping configuration.
Custom Lead fields can only map to custom fields on Account, Contact, or Opportunity records, requiring matching data types such as picklist-to-picklist. Additionally, changing a custom Lead field's data type deletes its conversion field mapping in setup.

Step-by-Step Solution

1
Evaluate target field mapping restrictions for custom Lead fields.
Salesforce enforces that custom Lead fields can only be mapped to custom fields (not standard fields) on Account, Contact, or Opportunity, and the data types must align (e.g., picklist to picklist).
This maintains structural integrity across objects during conversion.
2
Evaluate the impact of changing custom Lead field data types on existing mappings.
Altering a mapped field's data type clears its mapping entry in Lead Custom Field Mapping.
Data type alterations invalidate pre-existing type compatibility rules in the conversion setup.

Key Concept

Rules governing Salesforce Lead Custom Field Mapping and data type changes.
Question 702Question

A Salesforce administrator at a commercial aviation maintenance company is updating field configurations across custom objects and setting up lead management processes. The administrator needs to convert existing field data types and configure field mappings for lead conversion. Which two statements describe correct considerations for custom field data type conversions and lead field mapping? (Choose 2)

Select all that apply

Show answer & explanation

Answer: Custom Lead fields can only be mapped to custom fields on the Account, Contact, or Opportunity objects with compatible data types.; Changing a custom field type from Multi-Select Picklist to a single-select Picklist can result in data loss if existing records contain multiple selected values.

Answer

Custom Lead fields can only be mapped to custom fields on target records (Account, Contact, Opportunity) with matching data types, and converting a field from Multi-Select Picklist to single-select Picklist risks losing data when records have multiple selected values.
Custom Lead fields can only be mapped to custom fields on Account, Contact, or Opportunity records during lead conversion. Furthermore, converting a Multi-Select Picklist field to a single-select Picklist truncates extra values on records that contain multiple selections, resulting in data loss.

Step-by-Step Solution

1
Analyze lead conversion mapping constraints.
Determine that custom lead fields can only map to custom fields on target objects.
Standard fields are not valid mapping targets for custom lead fields during lead conversion.
2
Evaluate data type conversion behavior for picklist fields.
Identify that changing from Multi-Select Picklist to Picklist truncates all but the first selected value.
Data conversion rules specify data loss risks when multi-value fields are changed to single-value formats.

Key Concept

Custom field mapping restrictions during lead conversion and data loss rules for field type conversions.
Question 703Question

A Salesforce Administrator is customizing a custom object record page using Dynamic Forms in Lightning App Builder. The administrator needs to display a field named 'Special Handling Notes' only when the 'Priority' field on the record is set to 'High'. Which configuration should the administrator use to fulfill this requirement?

Show answer & explanation

Answer: Set component visibility filter rules on the field within the Lightning App Builder.

Answer

Set component visibility filter rules on the field within the Lightning App Builder.
Dynamic Forms in Lightning App Builder provides component visibility filters that allow administrators to show or hide individual fields dynamically based on record values, user fields, or device type.

Step-by-Step Solution

1
Open the record page in Lightning App Builder.
The page canvas with Dynamic Forms components is accessible.
Dynamic Forms allows field level customization directly on the Lightning page layout.
2
Select the 'Special Handling Notes' field component.
The component properties panel opens on the right.
Visibility rules are applied directly to individual field components.
3
Add a Filter under Component Visibility set to 'Priority equals High'.
The field will only appear on the record detail page when the condition is met.
Component visibility rules dynamically evaluate record data to show or hide components.

Key Concept

Conditional field visibility using Dynamic Forms component filters
Question 704Question

An administrator created a new Record Type called 'Consulting Services' on the Lead object. Although an outdated picklist value was deactivated at the object level, users still see that value when creating records using the 'Consulting Services' Record Type. Which administrative action should be taken to remove this value from the dropdown?

Show answer & explanation

Answer: Edit the available picklist values for the Lead Source field within the Consulting Services Record Type detail page.

Answer

Edit the available picklist values for the Lead Source field within the Consulting Services Record Type detail page.
When a Record Type is created or modified, available picklist values for each custom or standard picklist field must be explicitly configured under that specific Record Type's setup page in Object Manager. Deactivating or modifying values at the object level does not automatically update existing Record Type picklist assignments.

Step-by-Step Solution

1
Identify the cause of the picklist discrepancy.
Recognize that creating or editing a Record Type requires explicit configuration of available picklist values for each picklist field on that object.
Record types maintain their own independent list of active picklist values.
2
Navigate to the target Record Type in Object Manager.
Locate the Lead object, select Record Types, and choose 'Consulting Services'.
Picklist assignments per record type are configured directly under the Record Type configuration page.
3
Edit the Lead Source picklist field under the Record Type.
Remove the unwanted picklist value from the Selected Values list and save.
This updates the available dropdown options specifically for records assigned to the Consulting Services Record Type.

Key Concept

Record Type Picklist Value Assignment
Question 705Question

An administrator at an IT consulting firm is managing a custom object named Client_Project__c, which is currently connected to the standard Account object through a Lookup relationship. The executive team requests two functional changes: first, if an Account record is deleted, all associated Client_Project__c records must be automatically removed; second, account managers must be able to view a calculated total of all related project budgets directly on the Account record. Which action should the administrator take to accomplish both requirements?

Show answer & explanation

Answer: Convert the Lookup relationship on Client_Project__c to a Master-Detail relationship after ensuring all Client_Project__c records have an assigned Account, then create a Roll-Up Summary field on Account.

Answer

Convert the Lookup relationship on Client_Project__c to a Master-Detail relationship after ensuring all Client_Project__c records have an assigned Account, then create a Roll-Up Summary field on Account.
Converting the relationship from Lookup to Master-Detail satisfies both requirements: detail records are automatically deleted when the master Account is deleted, and Master-Detail relationships permit the creation of standard Roll-Up Summary fields on the parent object. To successfully perform the conversion, every existing child record must have a populated parent lookup field.

Step-by-Step Solution

1
Analyze relationship capabilities for data retention and rollups
Identify that automatic cascading deletion and native Roll-Up Summary fields both require a Master-Detail relationship.
Lookup relationships do not support native Roll-Up Summary fields and by default clear the lookup field rather than deleting child records upon parent deletion.
2
Prepare data for relationship conversion
Ensure every existing Client_Project__c record contains a valid populated Account lookup value.
A Lookup relationship can only be converted to a Master-Detail relationship if all existing child records have a value in the lookup field.
3
Change relationship type and create summary field
Convert the field to Master-Detail and build the Roll-Up Summary field on Account to sum the project budgets.
Master-Detail relationships enforce cascade delete automatically and enable Roll-Up Summary fields on the master object.

Key Concept

Master-Detail vs Lookup Relationship Capabilities and Conversion Requirements
Question 706Question

A Salesforce Administrator at a global logistics firm must configure security controls for various departmental requirements. Match each business requirement on the left with the appropriate security feature or configuration on the right.

Click a left item, then click its matching right item

Items

Completely prevent all users assigned to the Sales Rep profile from viewing a sensitive custom field across all page layouts, reports, and API integrations.
Remove a field from the record detail view for general users while still allowing them to report on and edit the field value.
Prevent users assigned to a custom Support profile from viewing or creating any records of a new custom object.
Grant view access to a restricted financial field for only two specific users who share a standard profile with non-authorized users.

Matches

Show answer & explanation

Answer

Each security requirement maps directly to its corresponding feature based on Salesforce's security hierarchy: Profile FLS restricts field access platform-wide; Page Layouts control UI display only; Object Permissions control object-level access; Permission Sets grant selective incremental permissions to specific users.
Each requirement correctly pairs with the appropriate Salesforce mechanism: Profile FLS for global field restriction, Page Layouts for UI display adjustments, Object Permissions on Profiles for object access, and Permission Sets for targeted access extensions to specific individuals.

Step-by-Step Solution

1
Analyze the requirements for universal field restriction.
Field-Level Security (FLS) on the Profile must be set to Hidden because page layouts alone do not block API or report access.
FLS is the primary tool for securing field data globally across all access channels.
2
Analyze UI-only visibility changes.
Removing the field from the Page Layout hides it from the detail page while preserving backend access, editing, and reporting capability.
Page layout settings control display on record pages but do not enforce security.
3
Analyze object record creation and visibility rules.
Object Permissions on the Profile must have Read and Create cleared.
Object permissions regulate basic CRUD access to object records.
4
Analyze user-specific access extensions.
Create and assign a Permission Set with the required FLS granted to the two specific users.
Permission sets allow administrators to grant extra access to subset users without creating duplicate profiles.

Key Concept

Profiles, Permission Sets, Field-Level Security (FLS), and Page Layouts
Estimated Time:1m 30s
Question 707Question

A Salesforce Administrator at Quantum Dynamics is setting up a custom price book named 'Global Commercial' for a newly created hardware product. When sales representatives attempt to add this product to an opportunity using the 'Global Commercial' price book, the product is not available for selection. Which two administrative actions must be completed to enable sales representatives to add this product to opportunities using the custom price book? (Select 2)

Select all that apply

Show answer & explanation

Answer: Create an active price entry for the product in the Standard Price Book.; Add an active price book entry for the product in the 'Global Commercial' custom price book.

Answer

The administrator must create an active price entry for the product in the Standard Price Book and add an active price book entry for the product in the 'Global Commercial' custom price book.
For a product to be selectable on an opportunity using a custom price book, two essential requirements must be met: first, the product must have an active price entry in the Standard Price Book; second, an active price entry must be created for that product within the target custom price book.

Step-by-Step Solution

1
Verify Standard Price Book Entry
Ensure the product has an active entry in the Standard Price Book.
Salesforce architecture requires every product to have an active standard price before it can exist in any custom price book.
2
Add Product to Custom Price Book
Create a list price entry for the product inside the 'Global Commercial' price book and mark it active.
Sales representatives can only add products to an opportunity if the product is active in the specific price book selected for that opportunity.

Key Concept

Price Book Architecture and Entry Prerequisites
Estimated Time:1m 30s
Question 708Question

Vanguard Financial Technologies operates two distinct revenue channels: a Government Procurement division requiring a 7-stage compliance pipeline and a Commercial Licensing division using a streamlined 4-stage pipeline. Currently, sales representatives from both teams see all available stage picklist values when creating or updating Opportunity records. Which sequence of administrative actions should the Salesforce administrator execute to ensure each sales channel sees only its relevant stages?

Show answer & explanation

Answer: Create two distinct Sales Processes to select the appropriate stages for each pipeline, create two Opportunity Record Types and associate each with its respective Sales Process, and assign the Record Types to the corresponding user profiles.

Answer

Create two distinct Sales Processes to select the appropriate stages for each pipeline, create two Opportunity Record Types and associate each with its respective Sales Process, and assign the Record Types to the corresponding user profiles.
The correct answer outlines the mandatory sequence in Salesforce for customizing Opportunity Stages. Because Opportunity Stage is a special business process picklist, an administrator must first create a Sales Process to select which stages are included, then link that Sales Process to an Opportunity Record Type, and finally assign the Record Type to the appropriate profiles or permission sets.

Step-by-Step Solution

1
Define Sales Processes
Two custom Sales Processes are configured, isolating the 7 stages for Government Procurement and 4 stages for Commercial Licensing.
Opportunity Stage values are unique because their availability per record type is governed by a Sales Process rather than direct picklist editing.
2
Create and Link Record Types
Two Opportunity Record Types (Government Opportunity and Commercial Opportunity) are created and each is linked to its corresponding Sales Process.
Record Types tie page layouts, business processes (Sales Processes), and user profile access together.
3
Assign Record Types to User Profiles
Sales representatives assigned to Government or Commercial profiles automatically receive the correct Record Type and Stage picklist sequence upon Opportunity creation.
Profile/Permission Set assignment ensures users are restricted to the appropriate business process flow.

Key Concept

Sales Processes and Opportunity Stage Picklist Filtering
Estimated Time:2m 0s
Question 709Question

Aerospace Avionics Corp manages high-security escalation cases where Organization-Wide Defaults (OWD) for the Case object are set to Private. A compliance mandate requires external tier-3 security auditors—who do not own the cases—to temporarily collaborate on specific privacy breach cases. The auditors require Read/Write record access to edit specific case resolution details, as well as the ability to share restricted internal posts on the Case Feed that must remain invisible to external portal users. Which administrative configuration fulfills these access and feed collaboration requirements without granting global record permissions?

Show answer & explanation

Answer: Configure a Predefined Case Team containing the tier-3 security auditors with a Case Team Role granting Read/Write access, and train auditors to set Feed Item Visibility to 'Internal Users' when posting on the Case Feed.

Answer

Configure a Predefined Case Team containing the tier-3 security auditors with a Case Team Role granting Read/Write access, and instruct auditors to select 'Internal Users' for Feed Item Visibility when posting on the Case Feed.
The correct solution uses Predefined Case Teams with a Case Team Role granting Read/Write access, fulfilling the requirement for targeted, non-global record access under a Private OWD. Furthermore, utilizing the 'Internal Users' setting on Case Feed items restricts feed post visibility so that external portal users cannot view internal collaboration details.

Step-by-Step Solution

1
Evaluate record access requirements under OWD Private conditions
Standard sharing or Case Teams must be used to grant record-level Read/Write access to non-owners on a per-case basis.
Case Teams provide granular access control without altering OWD or granting global Modify All privileges.
2
Define Case Team Roles and Predefined Case Teams
Security auditors are added to a predefined team with a designated role configured for Read/Write record access.
Predefined Case Teams allow administrators to quickly add a group of frequent collaborators to individual cases.
3
Configure Case Feed publisher security settings
Auditors select 'Internal Users' for Feed Item Visibility during post creation.
Feed Item Visibility prevents external community/portal users from seeing sensitive internal collaboration posts.

Key Concept

Case Teams Record Sharing and Case Feed Item Visibility
Estimated Time:2m 0s
Question 710Question

An administrator is deploying a customized Lightning Record Page for the standard Account object. The business requirement states that users assigned to the Sales Rep profile must see this tailored page layout only when viewing Account records of the Partner Account record type while working within the Sales Console app. All other users and applications must continue seeing their current record pages. Which activation assignment option in the Lightning App Builder must the administrator select to fulfill this requirement?

Show answer & explanation

Answer: Assign the page as App, Record Type, and Profile, selecting the Sales Console app, the Partner Account record type, and the Sales Rep profile.

Answer

The correct activation option is to assign the page as App, Record Type, and Profile, specifying the Sales Console app, the Partner Account record type, and the Sales Rep profile.
In Lightning App Builder, activating a record page using the 'App, Record Type, and Profile' combination allows administrators to specify an exact target context. This ensures the customized record page displays only when all three conditions (Sales Console app, Partner Account record type, and Sales Rep profile) are met.

Step-by-Step Solution

1
Identify the required granularity of page activation.
The requirement demands filtering by three distinct criteria: Application (Sales Console), Record Type (Partner Account), and Profile (Sales Rep).
Lightning App Builder supports three levels of record page activation: Org Default, App Default, and App, Record Type, and Profile.
2
Select the appropriate activation tier in Lightning App Builder.
Choose 'App, Record Type, and Profile' in the activation dialog.
This tier provides the exact combination filtering needed to deliver the custom layout specifically to Sales Reps viewing Partner Accounts inside the Sales Console.

Key Concept

Lightning Record Page Activation Levels and Precedence
Question 711Question

A Salesforce administrator at a boutique wealth management firm wants to ensure that a custom field capturing a prospect's primary investment interest on the Lead object is automatically transferred to a custom field on the Contact object whenever a lead is converted. Which Salesforce feature should the administrator use to accomplish this?

Show answer & explanation

Answer: Map Lead Fields in the Lead Object Manager settings to target custom fields on the Contact object.

Answer

Map Lead Fields under the Lead Object Manager configuration to target the corresponding custom field on the Contact object.
To transfer custom Lead field data to custom Contact, Account, or Opportunity records during lead conversion, administrators must configure 'Map Lead Fields' in the Lead Object Manager settings. This maps the source Lead field to a compatible target field on the converted object.

Step-by-Step Solution

1
Identify the administrative requirement
Custom field data captured on a Lead record must populate a custom field on the newly created Contact record upon lead conversion.
Standard field values convert automatically, but custom fields require explicit administrative configuration.
2
Locate the Lead Custom Field Mapping interface
Navigate to Setup > Object Manager > Lead > Fields & Relationships > Map Lead Fields.
This tool defines destination custom fields on Account, Contact, and Opportunity objects for custom Lead data.
3
Select the target object tab and select the matching destination field
Select the Contact tab and pair the custom investment interest Lead field with the corresponding custom Contact field.
Mapping guarantees seamless data transfer during the conversion process provided data types are compatible.

Key Concept

Lead Custom Field Mapping during Lead Conversion
Question 712Question

A Salesforce Administrator at Solaria Cloud Services is launching a new IoT sensor package named 'SkyTracker Pro'. The administrator creates the product record and attempts to add it immediately to a newly created custom price book called 'EMEA Partner Price Book'. However, Salesforce prevents the administrator from creating the price book entry for the custom price book. Which prerequisite step did the administrator fail to complete before attempting to add the product to the custom price book?

Show answer & explanation

Answer: Creating an active price entry for the product in the Standard Price Book.

Answer

Creating an active price entry for the product in the Standard Price Book is required before adding it to any custom price book.
In Salesforce, the Standard Price Book serves as the foundational price catalog for all products. A product must have an active standard price established in the Standard Price Book before it can be assigned a list price in any custom price book.

Step-by-Step Solution

1
Analyze the core Salesforce product architecture requirement.
Identify that every product must have a baseline standard price stored in the Standard Price Book.
The Standard Price Book acts as the master repository for all product prices across the enterprise.
2
Evaluate the custom price book entry prerequisites.
Confirm that an active Standard Price Book entry must exist prior to creating entries in custom price books.
Salesforce enforces this data model rule to ensure price consistency and relational integrity.
3
Determine why the administrator's action failed.
The product record was created, but no active standard price was assigned in the Standard Price Book before attempting custom price book assignment.
Without an active standard price entry, custom price book entries cannot be established.

Key Concept

Standard Price Book Entry Prerequisite
Estimated Time:2m 0s
Question 713Question

An administrator at Northern Trail Outfitters configures a multi-channel event campaign and creates two custom campaign member statuses: "Invited" and "Attended Booth". The marketing manager needs to evaluate campaign performance using the standard Campaign ROI and response metrics. After updating several campaign members to "Attended Booth", campaign summary reports continue to show zero responded members and a zero percent response rate. Which administrative action will resolve this issue?

Show answer & explanation

Answer: Edit the Campaign Member Statuses related list on the campaign to select the "Responded" checkbox for "Attended Booth".

Answer

Edit the Campaign Member Statuses related list on the campaign to select the "Responded" checkbox for "Attended Booth".
In Salesforce Campaign Management, response metrics such as 'Total Responded' and response percentages depend entirely on the 'Responded' checkbox setting for each Campaign Member Status value. When custom member statuses are added, Salesforce does not automatically treat them as responses. Enabling the 'Responded' option for 'Attended Booth' ensures that any Lead or Contact assigned this status is counted in campaign response totals and summary reports.

Step-by-Step Solution

1
Identify how Salesforce calculates campaign member responses.
Salesforce tracks responded members based on the 'Responded' flag associated with each Campaign Member Status value.
By default, custom member statuses are created with the 'Responded' box unchecked unless configured otherwise.
2
Locate the administrative setting for campaign member statuses.
Navigate to the Campaign record page and view the Campaign Member Statuses related list (or standard Advanced Setup).
Each campaign allows administrators and campaign owners to define custom statuses and designate which ones count as a valid response.
3
Update the custom status configuration.
Check the 'Responded' box next to 'Attended Booth'.
This updates the Campaign Member metrics instantly, ensuring reports accurately display total responses and calculate ROI.

Key Concept

Campaign Member Status Responded Tracking
Question 714Question

A Support Operations Manager at a global logistics firm requests a streamlined process for Tier 2 support agents working on Case records. When handling escalation cases, agents must quickly create a related custom escalation dispatch record. The solution must automatically populate target fields on the new record using parent Case data (including Account, Contact, and Subject), enforce specific predefined field values, automatically link the new record to the source Case, and function seamlessly across both the Salesforce Mobile App and Lightning Experience desktop pages without custom code. Which solution should the System Administrator implement to meet these requirements?

Show answer & explanation

Answer: Create an Object-Specific Quick Action on the Case object of type 'Create a Record' targeting the escalation dispatch object, set predefined field values, and place the action on the Case page layout.

Answer

Create an Object-Specific Quick Action on the Case object of type 'Create a Record' targeting the escalation dispatch object, set predefined field values, and place the action on the Case page layout.
Object-Specific Quick Actions created on the Case object automatically pass the host Case record ID into the relationship field of the target object. They allow administrators to configure predefined field values using formulas referencing the parent Case fields, seamlessly support Salesforce Mobile and Lightning Experience, and enforce declarative best practices.

Step-by-Step Solution

1
Analyze the requirements for context sensitivity, cross-platform availability, and declarative capabilities.
Identified that the action must inherit parent record data (Case) and be available in both Lightning Experience and Mobile.
Object-specific actions inherit the context of the record page from which they are launched.
2
Evaluate Object-Specific Quick Actions versus Global Quick Actions and Custom Buttons.
Global actions lack record context; JavaScript custom buttons are unsupported in Lightning Experience.
Only Object-Specific Quick Actions meet all declarative, context-aware, and Lightning/Mobile compatibility requirements.
3
Configure the action with predefined field values.
Target fields are automatically populated from the source Case fields (Account, Contact, Subject).
Predefined field values in Quick Actions enable dynamic field populating without custom URL hacking or code.

Key Concept

Object-Specific Quick Actions vs. Global Quick Actions and Custom Buttons in Lightning Experience
Estimated Time:2m 0s
Question 715Question

A Salesforce Administrator at Quantum Edge Systems needs to launch a new hardware offering named 'EdgeNode Matrix'. The product must be configured so sales representatives can add it as an Opportunity Line Item using a new regional custom price book called 'EMEA Enterprise'.

In what sequential order should the administrator execute the configuration steps to successfully make the product available on opportunities?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequential setup order is: 1) Create and activate the 'EdgeNode Matrix' Product record, 2) Create an active Standard Price Book Entry in the Standard Price Book, 3) Create and activate the 'EMEA Enterprise' Custom Price Book, 4) Create a Custom Price Book Entry in the 'EMEA Enterprise' Price Book, and 5) Select the 'EMEA Enterprise' Price Book on an Opportunity and add 'EdgeNode Matrix' as an Opportunity Line Item.
In Salesforce Core Administration, setting up products for opportunity line items follows a strict architectural sequence. First, the base Product record must be created and activated. Second, an active Standard Price Book Entry must be created in the Standard Price Book—this is a mandatory prerequisite enforced by Salesforce before any custom price entries can exist. Third, the custom price book container must be created and activated. Fourth, the custom price book entry (listing the product's custom price in that custom price book) is added. Finally, end users can select the custom price book on an Opportunity record and add the product as an Opportunity Line Item.

Step-by-Step Solution

1
Create and activate the base Product record.
The core product object exists in Salesforce and is available for catalog configuration.
Price book entries cannot be attached to a non-existent product.
2
Establish an active Standard Price Book Entry in the Standard Price Book.
The product receives its foundational baseline price.
Salesforce enforces a strict data dependency requiring an active standard price book entry before any custom price book entries can be created for a product.
3
Create and activate the custom price book ('EMEA Enterprise').
A custom price book container is ready to accept product price entries.
Custom price entries require an active parent Custom Price Book record.
4
Create a Custom Price Book Entry for the product in the custom price book.
The product receives its regional negotiated price within the custom price book.
This links the product to the custom price book with its specific list price.
5
Associate the custom price book with an Opportunity and add the Opportunity Line Item.
The product is successfully added to the opportunity schedule.
Opportunity line items require both an active opportunity price book assignment and active line item pricing in that specific price book.

Key Concept

Products, Price Books, and Price Book Entry Prerequisites
Question 716Question

An administrator created a new Record Type named 'Partner Account' on the Account object to support a new channel sales initiative. The administrator assigned the corresponding 'Partner Account Layout' to the Custom Sales Representative profile for this record type. However, during user testing, representatives assigned to the profile report two issues when creating a 'Partner Account' record: the standard 'Type' picklist field displays values that should only apply to direct customers, and a newly created custom picklist field 'Partner Tier' displays no values at all. Upon checking, both picklists have active values defined in Fields & Relationships. Which administrative action should be taken to resolve the picklist display issues for the 'Partner Account' Record Type?

Show answer & explanation

Answer: Navigate to the 'Partner Account' Record Type detail page in Object Manager, edit the picklist settings for 'Type' and 'Partner Tier', and specify which values are selected and available for this specific record type.

Answer

The administrator must navigate to the 'Partner Account' Record Type detail page in Object Manager, edit the picklist settings for both 'Type' and 'Partner Tier', and specify the available values for each picklist under that record type.
In Salesforce, when a new Record Type is created on an object, the administrator must explicitly configure which picklist values are available for each picklist field on that Record Type. Editing the picklist options under Object Manager > [Object] > Record Types > [Record Type Name] allows the administrator to add, remove, or set defaults for picklist values specifically for records of that Record Type.

Step-by-Step Solution

1
Identify the root cause of record type picklist value discrepancies.
Recognize that creating a record type does not automatically filter or populate picklist choices unless the picklists are explicitly configured under the Record Type setup.
Record Types control available picklist values independently for each picklist field on the object.
2
Navigate to Object Manager > Account > Record Types > Partner Account.
Access the list of Picklists Available for Editing for the 'Partner Account' record type.
This section displays all standard and custom picklists for the object and their current value assignments for this specific record type.
3
Edit the 'Type' and 'Partner Tier' picklist fields under the Record Type configuration.
Remove invalid direct customer values from 'Type' and move valid values into the Available/Selected list for 'Partner Tier'.
Saving these changes ensures users creating or editing records assigned to the 'Partner Account' Record Type only see the appropriate picklist options.

Key Concept

Picklist Value Assignment per Record Type
Question 717Question

A Salesforce Administrator is tasked with manually provisioning a new team member who requires specific operational access beyond standard system capabilities. What is the correct sequence of steps the administrator should follow to provision this user according to Salesforce security best practices?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct order to provision the user is: First, select the User License and assign a minimal baseline profile. Second, populate mandatory user record attributes like Username, Email, Alias, and Role. Third, save the User record to create the user account. Fourth, assign relevant Permission Sets to extend permissions. Fifth, add the user to designated Queues and Public Groups.
User provisioning in Salesforce begins by setting fundamental license and profile limits (least privilege), populating required fields, saving the record to generate the user ID, layering specific access via Permission Sets, and finally adding the user to sharing groups and queues.

Step-by-Step Solution

1
Select User License and minimal Profile
Defines core functional boundaries and license availability.
Salesforce requires a license and profile to establish base capabilities following the principle of least privilege.
2
Fill required identity and organizational fields
Prepares mandatory user details such as Username, Email, and Role.
A user record cannot be saved without mandatory fields and role placement.
3
Save the User record
Creates the user record and generates a unique User ID.
Subsequent assignments require an active User ID to attach permission sets and group memberships.
4
Attach Permission Sets
Grants additional object and field permissions tailored to the job function.
Permission sets layer access onto existing users without granting overly broad profile access.
5
Configure Queue and Public Group memberships
Integrates the user into automated routing and record sharing rules.
Group and queue assignments finalise functional access and record visibility.

Key Concept

User Provisioning Workflow and Least Privilege Access
Estimated Time:1m 30s
Question 718Question

A Salesforce administrator at a cloud telephony provider is configuring lead conversion settings. The sales team requires that a custom picklist field on the Lead object, named Service Tier, populates a custom field on the Contact record upon lead conversion. During testing, the administrator observes that the field value on newly converted Contact records remains blank. Which configuration setting should the administrator check to resolve this issue?

Show answer & explanation

Answer: Verify that the custom Lead field Service Tier is explicitly mapped to a custom Contact field of a compatible data type in Lead Custom Field Mapping.

Answer

The administrator must verify that the custom Lead field Service Tier is explicitly mapped to a custom Contact field of a compatible data type within Lead Custom Field Mapping.
When converting leads in Salesforce, standard lead fields map automatically to their standard counterparts on Accounts, Contacts, and Opportunities. However, custom fields on the Lead object require explicit setup under Lead Custom Field Mapping in order to pass their values over to converted records. Additionally, custom lead fields can only be mapped to custom target fields of compatible data types.

Step-by-Step Solution

1
Identify the data flow requirement during lead conversion.
Recognize that custom Lead fields require explicit mapping rules to transfer data to converted records.
Salesforce does not automatically copy custom Lead field values to standard or custom target object fields upon conversion.
2
Evaluate Salesforce platform capabilities and restrictions for Lead Custom Field Mapping.
Determine that custom fields on the Lead object must be mapped specifically to custom fields on the Account, Contact, or Opportunity objects with compatible data types.
Mapping custom Lead fields to standard fields is prohibited by the platform, and missing mapping definitions results in blank fields on converted records.
3
Select the correct administrative action.
Navigate to Object Manager > Lead > Fields & Relationships > Map Lead Fields and configure the mapping from the custom Lead field to the custom Contact field.
This establishes the necessary field mapping so values correctly populate when leads are converted.

Key Concept

Lead Custom Field Mapping
Question 719Question

A Salesforce administrator is configuring a Lightning record page for a Support team working on Case records. The team needs a streamlined way to create child Task records to log customer calls and update the status of the current Case record directly from the publisher area. Which TWO action types should the administrator configure on the Case object? (Select 2 answers)

Select all that apply

Show answer & explanation

Answer: An Object-Specific Create Record Quick Action to create related Task records; An Object-Specific Update a Record Quick Action to modify Case fields

Answer

The administrator should configure an Object-Specific Create Record Quick Action to create related Task records and an Object-Specific Update a Record Quick Action to modify Case fields.
Object-specific actions are ideal for record pages because they operate within the context of the current record. A Create Record object-specific action creates related records like Tasks tied directly to the Case, while an Update a Record object-specific action modifies fields on the current Case record using an optimized action layout.

Step-by-Step Solution

1
Identify the requirement to create a related record (Task) from a Case record page.
Determine that an Object-Specific Create Record action automatically links the new child record to the current Case.
Object-specific create actions maintain parent-child record context.
2
Identify the requirement to update fields on the active Case record from the page publisher.
Determine that an Object-Specific Update a Record action allows editing record fields using a targeted action layout.
Update record actions provide dedicated fields for quick editing on Lightning pages.

Key Concept

Object-Specific Quick Actions
Question 720Question

An administrator at a logistics company manages a custom data model where individual Package__c records are linked to a parent Delivery_Manifest__c object via a standard Lookup relationship. Management requests a field on Delivery_Manifest__c that automatically calculates the cumulative weight of all associated packages. When attempting to create a field on Delivery_Manifest__c, the Roll-Up Summary field type is disabled. Which configuration change must the administrator make to fulfill this requirement?

Show answer & explanation

Answer: Convert the existing Lookup field on Package__c into a Master-Detail relationship after ensuring all existing Package__c records have the Delivery_Manifest__c lookup field populated.

Answer

Convert the existing Lookup field on Package__c into a Master-Detail relationship after ensuring all existing Package__c records have the Delivery_Manifest__c lookup field populated.
Declarative Roll-Up Summary fields require a Master-Detail relationship where the summarizing object acts as the master. Converting the Lookup relationship on the child object to a Master-Detail relationship enables Roll-Up Summary fields on the parent object, provided all existing child records contain populated parent lookup values prior to conversion.

Step-by-Step Solution

1
Identify relationship requirements for declarative Roll-Up Summary fields in Salesforce.
Declarative Roll-Up Summary fields are only available on the parent object of a Master-Detail relationship, not on a standard Lookup relationship.
Salesforce platform rules strictly restrict declarative Roll-Up Summary field types to Master-Detail parent objects.
2
Evaluate the prerequisite for converting a Lookup relationship to a Master-Detail relationship.
All child records (Package__c) must have a value in the parent lookup field (Delivery_Manifest__c) before conversion.
Master-Detail relationships enforce mandatory parentage; null values are prohibited on detail records.
3
Convert the relationship field type and create the requested Roll-Up Summary field.
The field type on Package__c is converted to Master-Detail, allowing the administrator to create a SUM Roll-Up Summary field on Delivery_Manifest__c.
Once the Master-Detail relationship is established, the Roll-Up Summary field type becomes enabled on the parent object.

Key Concept

Roll-Up Summary Field Capabilities and Relationship Conversion Prerequisites
PreviousPage 36 / 90Next
All practice questions — Salesforce Certified Administrator | Examkin