All practice questions

1784 questions

Question 601Question

An administrator at Cloud Kicks creates a new product and needs to add it to a newly created custom price book. However, when attempting to add the product to the custom price book, the product is not available for selection. What must the administrator do first to resolve this issue?

Show answer & explanation

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

Answer

Create an active price entry for the product in the Standard Price Book.
Before a product can be added to any custom price book, it must first have an active price entry in the Standard Price Book. Once the standard price entry is created and marked active, the product will become available for assignment to custom price books.

Step-by-Step Solution

1
Identify the prerequisite requirement for adding products to custom price books in Salesforce.
Salesforce mandates that every product must have an active standard price entry in the Standard Price Book before it can be added to a custom price book.
The standard price serves as the base price entry for product management across all price books.
2
Add an active price to the Standard Price Book for the new product.
The product becomes available to be selected and added to custom price books.
Fulfilling this dependency enables custom price book entries for that product.

Key Concept

Standard Price Book prerequisite for Custom Price Book Entries
Estimated Time:45s
Question 602Question

An administrator configures three distinct custom Lightning Record Pages for the Opportunity object with the following activation settings:

- Page 1 is activated as the Org Default across desktop and phone channels.
- Page 2 is activated as the App Default for the Global Sales Console application.
- Page 3 is activated for the Global Sales Console application, specifically assigned to the Enterprise Deal Record Type and the Enterprise Sales Rep Profile.

A sales user assigned the Enterprise Sales Rep Profile opens an Opportunity record that has the Commercial Deal Record Type while working inside the Global Sales Console application on a desktop. Which Lightning Record Page will be displayed to the user?

Show answer & explanation

Answer: Page 2

Answer

Page 2 will be displayed to the user.
Salesforce evaluates Lightning Record Page assignments in a strict hierarchy: 1) App, Record Type, and Profile combination, 2) App Default, and 3) Org Default. In this scenario, Page 3 requires the Enterprise Deal record type, but the record being viewed is a Commercial Deal. Because all three assignment dimensions must match for Page 3, Salesforce moves down the hierarchy to check for an App Default assignment for the Global Sales Console application. Since Page 2 is assigned as the App Default for that app, it is selected and displayed.

Step-by-Step Solution

1
Evaluate the most specific activation level (App + Record Type + Profile)
Page 3 is configured for Global Sales Console + Enterprise Deal + Enterprise Sales Rep. The target record has the Commercial Deal Record Type, failing the match condition.
Lightning Record Page evaluation requires all three parameters to match exactly at this level.
2
Evaluate the next precedence level (App Default)
Page 2 is activated as the App Default for the Global Sales Console application.
When no specific App + Record Type + Profile match exists, Salesforce falls back to the assigned App Default for the current app.
3
Determine the winning page layout
Page 2 matches the current application context and displays successfully.
App Default takes precedence over Org Default when accessed within that app.

Key Concept

Lightning Record Page Activation Precedence (App + Record Type + Profile vs App Default vs Org Default)
Question 603Question

A Salesforce administrator at a maritime cargo management company is tasked with capturing a custom text field, 'Container Serial Code', on Lead records. The business requirement states that when a Lead is converted, the value stored in 'Container Serial Code' must automatically transfer to the newly created Account record. Which administrative action is required to ensure this custom field data transfers successfully during lead conversion?

Show answer & explanation

Answer: Create a matching custom field on the Account object, then use the 'Map Lead Fields' tool in the Lead Object Manager to map the Lead field to the Account field.

Answer

Create a matching custom field on the Account object, then use the 'Map Lead Fields' tool in the Lead Object Manager to map the Lead field to the Account field.
To preserve custom lead field data upon conversion, an administrator must create a destination custom field on the target object (Account, Contact, or Opportunity) with a compatible data type and explicitly map the source Lead field to the destination field using the 'Map Lead Fields' feature in the Lead Object Manager.

Step-by-Step Solution

1
Create target custom field
A custom text field exists on the Account object to receive the converted data.
Data must have a target destination field of a compatible type on the target object.
2
Access Lead Field Mapping
The administrator opens Object Manager > Lead > Fields & Relationships > Map Lead Fields.
This interface allows custom mappings between Lead fields and Account, Contact, or Opportunity fields.
3
Map the source Lead field to the target Account field
The 'Container Serial Code' Lead field is mapped to the corresponding Account custom field.
Ensures lead conversion automation populates the field value onto the Account record upon conversion.

Key Concept

Custom Lead Field Mapping during Lead Conversion
Question 604Question

A Salesforce Administrator at Meridian Global Logistics is configuring administrative access controls across various custom objects and user groups. Match each security requirement to the most appropriate Salesforce security feature.

Click a left item, then click its matching right item

Items

Restrict users assigned to a specific role from logging into Salesforce outside of official business hours (8:00 AM to 6:00 PM EST).
Completely hide the custom field Vendor_Tax_ID__c on Account records across all UI pages, reports, global search, and API integrations for non-Finance users.
Grant temporary edit access for the Contract_Status__c field to a single Operations Lead without modifying their assigned profile or affecting peers on the same profile.
Prevent an entire department from creating, reading, editing, or deleting any custom Audit_Log__c records regardless of record ownership.

Matches

Show answer & explanation

Answer

Matching pairings: 1) Restricting login times by role matches Profile Login Hours settings; 2) Hiding sensitive field data across UI, reports, and API matches Field-Level Security (FLS) settings; 3) Granting selective temporary field edit access to one user matches Permission Set assignment; 4) Preventing record creation/reading/editing/deletion for an entire object matches Profile Object Permissions (CRUD settings).
Each security mechanism is correctly paired according to its architectural purpose in Salesforce core administration: Profile Login Hours control login time restrictions; Field-Level Security enforces data access restriction at the field level globally across UI and API; Permission Sets allow flexible, additive permission assignment to individual users without profile alteration; and Profile Object Permissions control baseline CRUD capabilities for records of an object.

Step-by-Step Solution

1
Analyze access control requirements based on scope (user-specific vs profile-wide) and target (system access, object, field).
Identified four distinct security boundaries: authentication timing, field data visibility, individual user permission extension, and object baseline capabilities.
Salesforce security uses a layered security model where Profiles establish baseline object CRUD rights and login restrictions, FLS secures individual fields globally, and Permission Sets provide additive grants to individual users.
2
Map login time window restrictions to Profile Login Hours.
Profile Login Hours control when users assigned to that profile can authenticate.
Setting Login Hours on a profile denies login attempts made outside the designated timeframe.
3
Map comprehensive field privacy requirements across UI, reports, and API to Field-Level Security.
Field-Level Security (FLS) suppresses field access across all access channels.
Unlike page layouts, FLS enforces security at the data layer, ensuring fields cannot be queried or exposed in reports, list views, or APIs.
4
Map single-user permission additions without profile modifications to Permission Sets.
Permission Sets grant permissions to individual users without profile proliferation.
Permission Sets follow the principle of least privilege by extending access incrementally to specific users.
5
Map object-wide access restriction (preventing Create, Read, Edit, Delete) to Profile Object Permissions.
Profile Object Permissions control baseline CRUD settings for the target object.
Removing Read access on the profile prevents users from accessing any records of that object, overriding sharing rules.

Key Concept

Salesforce security architecture relies on Profiles for baseline system access (Login Hours) and Object CRUD permissions, Field-Level Security for universal field privacy, and Permission Sets for additive, individual user permissions.
Question 605Question

A Salesforce Administrator creates a new Record Type called 'Internal IT' on the Case object. After assigning the record type to the IT Support profile, users report seeing picklist options that belong strictly to customer service cases when creating an 'Internal IT' record. Which configuration step did the administrator omit during setup?

Show answer & explanation

Answer: Editing the field's available picklist values under the new Record Type settings to remove non-applicable options.

Answer

Editing the field's available picklist values under the new Record Type settings to remove non-applicable options.
When a new Record Type is created on an object, Salesforce automatically includes all master picklist values for every picklist field. The administrator must explicitly navigate to the Record Type detail page in Object Manager and edit the picklists for that Record Type to remove values that should not be selectable.

Step-by-Step Solution

1
Identify the root cause of seeing incorrect picklist values on a newly created Record Type.
Recognize that a newly created Record Type inherits all master picklist values by default until customized.
Record Types govern business processes by filtering picklist values, but this filtering requires manual configuration per field.
2
Navigate to Object Manager > Case > Record Types > Internal IT.
Access the 'Picklists Available for Editing' section for the Record Type.
Picklist value selections are managed directly under each specific Record Type detail page.
3
Edit the relevant picklist fields and move non-applicable customer service values to the 'Available Values' column, leaving only IT values in 'Selected Values'.
Only relevant picklist choices are displayed when creating an 'Internal IT' case.
This ensures clean data entry tailored to the specific business process.

Key Concept

Picklist Value Assignment per Record Type
Question 606Question

A company administrator needs to provision temporary access for a Customer Support Representative who is joining an internal audit task force for three months. The user must retain their current access to customer cases while gaining Read-only access to custom financial audit records. Which two actions should the administrator take to meet these requirements while adhering to the principle of least privilege?

Select all that apply

Show answer & explanation

Answer: Assign a permission set to the user that grants Read access to the custom financial audit objects.; Maintain the user's current Support Representative profile assignment.

Answer

The administrator should assign a permission set granting Read access to the custom financial audit objects and maintain the user's current Support Representative profile assignment.
In Salesforce, profiles define the core baseline permissions, while permission sets are used to grant additional permissions on an ad-hoc or temporary basis. Retaining the user's primary Support Representative profile maintains necessary ongoing case access, while applying a permission set grants the supplemental Read-only access to audit records in compliance with least privilege principles.

Step-by-Step Solution

1
Analyze baseline profile requirements
Identify that the user continues to require their primary job function access (Support Representative).
Profiles define standard baseline access per user role.
2
Determine mechanism for temporary/additional permissions
Select a permission set for the financial audit object access.
Permission sets allow flexible, additive access extensions without profile proliferation.

Key Concept

User Provisioning and Additive Access via Permission Sets
Estimated Time:1m 30s
Question 607Question

An administrator at a renewable energy company needs to ensure that data captured in a custom Lead field named 'Solar Equipment Preference' is automatically transferred to a custom field on the Account record when a lead is converted. Where in Salesforce Setup should the administrator configure this field mapping?

Show answer & explanation

Answer: The 'Map Lead Fields' button within the Fields & Relationships section of the Lead object

Answer

The administrator should perform this setup by navigating to Object Manager > Lead > Fields & Relationships and clicking the 'Map Lead Fields' button.
To map custom Lead fields to custom Account, Contact, or Opportunity fields during conversion, administrators must navigate to Object Manager > Lead > Fields & Relationships and select 'Map Lead Fields'. From there, each custom Lead field can be linked to a compatible target field.

Step-by-Step Solution

1
Navigate to Object Manager in Setup and select the Lead object.
Accesses the Lead object management setup settings.
Lead conversion field mapping rules are anchored to the Lead object as the source object.
2
Open 'Fields & Relationships' and click the 'Map Lead Fields' button.
Opens the field mapping user interface.
This interface allows custom Lead fields to be mapped to matching custom fields on Account, Contact, or Opportunity records.

Key Concept

Lead Conversion Field Mapping
Question 608Question

A financial services institution is auditing its Salesforce lead lifecycle process to ensure data integrity during lead conversion. Arrange the following execution events in the correct chronological sequence from the moment an administrator or sales rep clicks the 'Convert' button on a Lead record.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct chronological sequence is: (1) Salesforce evaluates validation rules on the Lead record, (2) Target Account, Contact, and optional Opportunity records are instantiated and saved, (3) Custom Lead field values populate corresponding mapped custom fields on the created target records, (4) The Lead record is set to converted status (IsConverted = TRUE) and becomes read-only, and (5) Triggers, Flow automations, and validation rules execute on the newly created Account, Contact, and Opportunity records.
The correct order follows Salesforce's internal execution model for lead conversion: Lead validation rules evaluate first to verify source data; next, destination Account, Contact, and Opportunity records are created; mapped custom Lead fields populate those target records; the original Lead record updates to IsConverted = TRUE and becomes read-only; and finally, automations and validation rules on the newly created target objects execute.

Step-by-Step Solution

1
Identify the initial pre-conversion validation phase
Lead validation rules run first to prevent conversion if mandatory Lead fields fail validation.
Salesforce ensures data quality on the source record prior to generating downstream destination records.
2
Identify destination object instantiation
Target Account, Contact, and Opportunity records are created or linked.
Core relational structures must exist in the database before field values can be populated.
3
Trace data transfer via custom field mapping
Mapped Lead fields write their values to Account, Contact, or Opportunity custom fields.
Custom Lead Field Mapping executes during target record field assignment.
4
Determine source record status transition
The Lead record is marked as converted and locked from editing.
The system flags `IsConverted = TRUE` to complete the Lead lifecycle stage transition.
5
Determine post-conversion automation execution
Target object automations (Flows, triggers, and validation rules) execute.
Newly created destination records fire their respective object-level execution logic upon insertion.

Key Concept

Salesforce Lead Conversion Order of Execution
Question 609Question

An enterprise software company has 50 Account Executives assigned to a baseline profile named 'Sales Representative'. To support an upcoming project, 5 of these Account Executives temporarily require Read and Edit access to a custom object named 'Compliance Audit Log' for 90 days. The administrator needs to grant this access while adhering to security best practices and minimizing administrative overhead. Which configuration approach should the administrator implement?

Show answer & explanation

Answer: Create a Permission Set granting Read and Edit permissions on the Compliance Audit Log object, assign it to the 5 Account Executives with an expiration date of 90 days, and leave the baseline profile unchanged.

Answer

Create a Permission Set granting Read and Edit permissions on the Compliance Audit Log object, assign it to the 5 Account Executives with an expiration date of 90 days, and leave the baseline profile unchanged.
Permission Sets are designed to grant additive permissions to specific users beyond what their baseline profile provides. By assigning a Permission Set with an expiration date, the administrator ensures principle of least privilege, avoids creating redundant profiles, and automates access revocation after 90 days.

Step-by-Step Solution

1
Analyze access requirements
Identify that 5 users require additive object permissions for a limited time (90 days).
Profiles define baseline access shared by all assigned users, whereas permission sets extend access to specific subsets of users.
2
Evaluate configuration tools
Select a Permission Set with an assigned expiration date.
Permission Sets provide additive security control without altering the shared profile or requiring manual cleanup after the temporary duration expires.

Key Concept

Using Permission Sets and Assignment Expiration for Additive and Temporary Access
Estimated Time:1m 30s
Question 610Question

A Salesforce administrator at a renewable energy firm is setting up Lead Custom Field Mapping to transfer lead data upon conversion. When attempting to map a custom text field from the Lead object to a target field on the Contact object, the administrator notices that the target Contact field does not appear in the mapping dropdown list. What is the most likely reason the target Contact field is missing from the selection list?

Show answer & explanation

Answer: The custom field on the Contact object has a data type that is incompatible with the custom Lead field.

Answer

The target Contact field is missing because its data type is incompatible with the source Lead field data type.
In Salesforce Lead Custom Field Mapping, target custom fields on Account, Contact, or Opportunity objects only appear in the dropdown list if their data types are compatible with the source custom Lead field.

Step-by-Step Solution

1
Identify the requirement for custom field mapping during Lead conversion.
Salesforce allows custom Lead fields to be mapped to custom fields on the Account, Contact, or Opportunity objects.
Data entered on a Lead record must cleanly transfer to converted records without data loss or truncation.
2
Evaluate data type compatibility rules in Salesforce setup.
Only custom fields with matching or strictly compatible data types appear in the mapping target dropdown lists.
If a source field is Text (80) and the target Contact field is Number or Date, Salesforce will exclude the target field from the mapping dropdown.

Key Concept

Lead Custom Field Mapping Type Compatibility
Question 611Question

A company is implementing a dedicated resolution path for high-priority outages on the Case object. The administrator creates a new Record Type named 'Critical Incident'. During user testing, support agents assigned to the 'Support Specialist' profile report two issues when working with these records: first, the 'Root Cause Analysis' value is missing from the 'Issue Type' picklist dropdown; second, the record displays the default 'Standard Case Layout' instead of the new 'Critical Incident Layout'. Which two administrative actions must be completed to resolve these issues for the 'Support Specialist' profile? (Select 2 answers.)

Select all that apply

Show answer & explanation

Answer: Edit the 'Critical Incident' Record Type detail page to explicitly add 'Root Cause Analysis' to the list of selected values for the 'Issue Type' picklist.; Navigate to Page Layout Assignments on the Case object and map the 'Support Specialist' profile and 'Critical Incident' Record Type combination to the 'Critical Incident Layout'.

Answer

To resolve both issues, the administrator must edit the 'Critical Incident' Record Type configuration to add 'Root Cause Analysis' to the available picklist values for 'Issue Type', and update the Case Page Layout Assignment matrix so that the 'Support Specialist' profile uses the 'Critical Incident Layout' when viewing 'Critical Incident' records.
When a new Record Type is created, an administrator must complete two separate configuration tasks: first, edit the Record Type details under Object Manager to select which picklist values (such as 'Root Cause Analysis') are active for that specific Record Type; second, access Page Layout Assignments to assign the desired Page Layout ('Critical Incident Layout') to the targeted Profile ('Support Specialist') for that Record Type.

Step-by-Step Solution

1
Configure Picklist Values per Record Type
'Root Cause Analysis' becomes available in the 'Issue Type' picklist for 'Critical Incident' records.
Creating a new Record Type does not automatically include all active picklist values; available values must be selected within the Record Type's picklist settings.
2
Update Page Layout Assignment Matrix
Users with the 'Support Specialist' profile see the 'Critical Incident Layout' on 'Critical Incident' records.
Salesforce determines page layout display using a two-dimensional matrix combining Profile and Record Type.

Key Concept

Page Layout and Picklist Assignment per Profile and Record Type
Estimated Time:2m 0s
Question 612Question

A Salesforce Administrator needs to configure a new product named 'Analytics Add-On' so that sales representatives can select it on opportunities using a custom price book named 'EMEA Government Pricing'. What is the correct sequence of steps required to successfully configure and use this product on an opportunity?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence of steps is: 1) Create the 'Analytics Add-On' Product record and set its status to Active; 2) Add a standard price entry for 'Analytics Add-On' in the Standard Price Book and activate it; 3) Create the 'EMEA Government Pricing' Custom Price Book record and set it to Active; 4) Add a custom list price entry for 'Analytics Add-On' within the 'EMEA Government Pricing' Custom Price Book; 5) Select the 'EMEA Government Pricing' price book on the Opportunity and add the 'Analytics Add-On' opportunity line item.
In Salesforce, product administration follows a strict hierarchy. First, the Product record must exist and be active. Second, the product must be given an active standard price entry in the Standard Price Book, as custom price books cannot reference products without a standard price baseline. Third, the custom price book must be created and activated. Fourth, the product can be added to the custom price book with a custom list price. Finally, sales users can select that price book on an opportunity and add the product as an opportunity line item.

Step-by-Step Solution

1
Define the base Product record in Salesforce
The product record 'Analytics Add-On' is created and active in the database
Price books and line items require an underlying product record to link against.
2
Establish the Standard Price Book entry
An active standard price entry exists for the product
Salesforce architecture strictly enforces that a product must have an active entry in the Standard Price Book before it can be added to any custom price books.
3
Create and activate the Custom Price Book record
The custom price book 'EMEA Government Pricing' becomes available for custom entries
A custom price book must be active to hold list price entries for specific target markets or currencies.
4
Create the Custom Price Book Entry
The product 'Analytics Add-On' has a custom price entry in 'EMEA Government Pricing'
This links the product to the specific custom price book with a localized list price.
5
Add the Opportunity Line Item
The product is added to the opportunity with its price book line item details
Users select the price book on the opportunity and pick products from that price book's active entry list.

Key Concept

Products, Price Books, and Opportunity Line Items Setup Dependency
Question 613Question

A Salesforce Administrator at a financial services firm needs to restrict access to a sensitive custom field, Credit_Score__c, on the Account object. Currently, 25 support representatives share a single custom Support profile that grants Read and Edit access to all Account fields. However, only 3 senior support representatives require access to view and edit Credit_Score__c. Which configuration solution should the administrator implement to meet this security requirement while maintaining maintainability?

Show answer & explanation

Answer: Remove Field-Level Security access for Credit_Score__c from the Support profile, create a Permission Set granting Read and Edit access to Credit_Score__c, and assign it to the 3 senior representatives.

Answer

Remove Field-Level Security access for Credit_Score__c from the Support profile, create a Permission Set granting Read and Edit access to Credit_Score__c, and assign it to the 3 senior representatives.
The correct solution enforces least privilege at the profile level by restricting Field-Level Security (FLS) for all support representatives, while using a Permission Set to additively grant access to the 3 senior representatives. This keeps profile administration clean and scalable.

Step-by-Step Solution

1
Evaluate the baseline security requirements across all users with the Support profile.
Since the majority of support representatives should not access Credit_Score__c, access must be removed at the profile level via Field-Level Security (FLS).
Profiles should establish least privilege baseline access.
2
Determine the optimal mechanism for granting elevated access to a subset of users.
A Permission Set granting Read and Edit access to Credit_Score__c is created and assigned to the 3 senior representatives.
Permission sets allow flexible, additive permission assignments without requiring redundant profiles.

Key Concept

Field-Level Security (FLS) baseline restrictions combined with Permission Sets for additive access control.
Question 614Question

A Salesforce Administrator at a software company tracks user access using two custom objects: Software_License__c (parent) and License_Assignment__c (child). The two objects are currently connected via a lookup relationship. The administrator receives a requirement to display the total count of active assignment records directly on each Software_License__c record page using a declarative field. When trying to create a new Roll-Up Summary field on Software_License__c, the administrator finds that the Roll-Up Summary field type option is disabled. Which action must the administrator take to allow the creation of a Roll-Up Summary field on the parent object?

Show answer & explanation

Answer: Convert the lookup relationship field on the License_Assignment__c object to a master-detail relationship after verifying all existing child records have a populated lookup value.

Answer

Convert the existing lookup field on the child object to a master-detail relationship after ensuring all child records contain populated lookup values.
Standard Roll-Up Summary fields in Salesforce are only supported on the parent object in a Master-Detail relationship. Converting the lookup field on the child object to a master-detail relationship (which requires ensuring all child records have populated lookup values) enables the Roll-Up Summary field type on the parent object.

Step-by-Step Solution

1
Identify the relationship requirement for native Roll-Up Summary fields.
Native Salesforce Roll-Up Summary fields can only be created on the master object in a Master-Detail relationship.
Lookup relationships do not support declarative roll-up summary fields on the parent object.
2
Prepare data for converting a lookup relationship to a master-detail relationship.
Ensure every existing License_Assignment__c record has a valid parent reference populated in the lookup field.
Master-Detail fields are mandatory on child records; converting a lookup field fails if any existing child record has a blank lookup field.
3
Change the field type of the relationship field on the child object to Master-Detail and create the Roll-Up Summary field on the parent.
The Roll-Up Summary field type becomes available on the parent object (Software_License__c) to count child records.
Once the Master-Detail relationship is established, master objects inherit roll-up capabilities.

Key Concept

Roll-Up Summary Field Relationship Requirements
Question 615Question

A Salesforce System Administrator at a manufacturing enterprise needs to change an existing Lookup relationship on the custom object Equipment_Maintenance__c (child) to a Master-Detail relationship with the standard Account object (parent) to enforce security inheritance and enable roll-up capabilities. When attempting to convert the field type in Object Manager, the system throws an error and prevents the modification. What prerequisite step must be completed before Salesforce will allow converting this Lookup relationship to a Master-Detail relationship?

Show answer & explanation

Answer: Populate a valid Account record reference in the lookup field for every existing Equipment_Maintenance__c record.

Answer

Populate a valid Account record reference in the lookup field for every existing Equipment_Maintenance__c record.
You can convert a Lookup relationship to a Master-Detail relationship only if the lookup field on all existing records contains a value. If any child record has an empty lookup field, Salesforce rejects the relationship type conversion until every record has a designated parent.

Step-by-Step Solution

1
Identify the technical requirement for converting a Lookup relationship to a Master-Detail relationship.
Master-Detail relationships strictly enforce mandatory parent references across all child records.
Unlike Lookup relationships which allow optional/null parent fields, Master-Detail fields are mandatory on every child record.
2
Analyze why the system error occurred during field conversion in Object Manager.
At least one existing Equipment_Maintenance__c record contains a blank (null) Account lookup field.
Salesforce validates data integrity during relationship conversion and blocks the change if any null values exist in the target field.
3
Determine the necessary remediation action.
Ensure all existing child records have a non-null Account lookup value populated before attempting field conversion.
Once all child records reference a parent, Salesforce allows converting the Lookup field to a Master-Detail relationship.

Key Concept

Converting Lookup Relationships to Master-Detail Relationships
Estimated Time:1m 30s
Question 616Question

A Salesforce administrator at Apex Financial needs to make a newly created product available for sales representatives to select on opportunities using a custom price book. Place the following configuration steps in the correct sequential order from first to last.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct order of steps is: 1) Create the new Product record in Salesforce and set it to Active; 2) Add a Standard Price to the Product in the Standard Price Book; 3) Add the Product to the Custom Price Book with a custom list price; 4) Add the Product as an Opportunity Line Item on an Opportunity associated with the Custom Price Book.
The correct sequence starts with creating the active Product record. Next, an active standard price entry must be created in the Standard Price Book because Salesforce enforces this prerequisite before allowing custom price book entries. After the standard price is defined, the product can be added to a Custom Price Book with custom list pricing. Finally, sales users can add the product as an Opportunity Line Item on an opportunity linked to that custom price book.

Step-by-Step Solution

1
Create the Product record.
The core Product record exists in Salesforce.
You must create the product definition before price book entries or opportunity line items can reference it.
2
Create a Standard Price Book entry.
The product has a base standard price entry.
Salesforce architecture mandates an active standard price in the Standard Price Book as an absolute prerequisite before adding the product to any custom price book.
3
Create a Custom Price Book entry.
The product is enabled in the specific custom price book.
With a standard price established, the product can now be listed in custom price books with custom pricing.
4
Add the Product to an Opportunity.
The product is added as an Opportunity Line Item.
Opportunities set to use a specific price book can now select this product as a line item.

Key Concept

Salesforce Product and Price Book setup sequence and prerequisites
Estimated Time:1m 0s
Question 617Question

Meridian Financial configured a Delegated Administration group to grant departmental team leads limited administrative capabilities over local staff and custom HR tracking processes. Which two capabilities can a system administrator grant using this Delegated Administration group? (Select 2 options)

Select all that apply

Show answer & explanation

Answer: Reset passwords and unlock user accounts for users assigned to specified role hierarchies.; Manage custom fields, page layouts, and validation rules for designated custom objects.

Answer

Delegated administrators can reset passwords and unlock accounts for users in specified roles, and they can manage custom fields, page layouts, and validation rules for specified custom objects.
Delegated Administration allows non-system administrators to perform user administration (such as password resets and unlocking accounts) for users within defined roles, as well as administer specific custom objects (including custom fields, page layouts, and validation rules).

Step-by-Step Solution

1
Identify user management capabilities supported under Delegated Administration.
Delegated administrators can unlock accounts and reset passwords for users within specified role hierarchies.
Salesforce allows delegating password resets and account unlocking scoped strictly by role hierarchy.
2
Identify schema and object customization capabilities supported under Delegated Administration.
Delegated administrators can manage fields, page layouts, custom tabs, and validation rules on specified custom objects.
Custom object administration can be explicitly delegated per custom object specified in the group.
3
Evaluate system and permission restrictions for delegated administrators.
Profile definitions cannot be edited by delegated administrators, and deactivated users subject to system references must be frozen rather than deactivated.
Editing profile definitions requires full 'Manage Users' and system admin privileges, and user deactivation limitations apply to all administrative roles.

Key Concept

Delegated Administration Scope and Privileges
Question 618Question

An enterprise health tech company automates its B2B qualification lifecycle. When a lead reaches a 'Qualified' state, an automated system process executes lead conversion. Place the following system processing phases and validation steps in the correct chronological sequence in which Salesforce executes lead conversion.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence of lead conversion execution is: 1) Validation rules and Apex triggers evaluate on the Lead record prior to conversion, 2) Target Account, Contact, and optional Opportunity record instances are populated using Lead custom and standard field mappings, 3) Validation rules, Apex triggers, and workflow logic execute on the newly generated target Account, Contact, and Opportunity records, 4) The original Lead record's Status field updates to a Converted picklist value and the Lead record becomes read-only.
During Salesforce lead conversion, system execution follows a strict sequence: pre-conversion Lead rules evaluate first to ensure conversion eligibility. Next, standard and custom field mappings populate target Account, Contact, and Opportunity record instances. Then, target object validation rules and automation fire upon insertion. Finally, once all target operations succeed, the Lead record status updates to Converted and becomes read-only.

Step-by-Step Solution

1
Evaluate Lead pre-conversion requirements
Lead validation rules and triggers verify that the Lead data is valid before conversion initiation can proceed.
If lead validation fails, conversion is halted before target records are initialized.
2
Perform Field Mapping and instantiate target objects
Salesforce applies custom and standard lead field mapping to populate attributes onto target Account, Contact, and Opportunity instances.
Target objects must be populated before database insertion and target object validation.
3
Execute Target Object Automation and Validation
Target records trigger their respective object-level automation (validation rules, triggers, flows) upon save.
Account, Contact, and Opportunity objects enforce their own system rules independently during creation.
4
Finalize Lead record conversion state
The originating Lead record is flagged as Converted and locked from further direct editing.
Lead lifecycle completion requires locking the lead to preserve data lineage and historical integrity.

Key Concept

Salesforce Lead Conversion Order of Execution
Estimated Time:3m 0s
Question 619Question

Match each Salesforce administration term related to record display and configuration with its correct functional capability.

Click a left item, then click its matching right item

Items

Record Type
Page Layout
Page Layout Assignment Matrix

Matches

Show answer & explanation

Answer

Record Type matches with defining available picklist values and business processes. Page Layout matches with controlling field placement and section layout. Page Layout Assignment Matrix matches with mapping layouts based on Profile and Record Type combination.
Each component performs a specific function in record display configuration: Record Types drive business processes and picklists, Page Layouts define visual arrangement, and the Assignment Matrix combines Profile and Record Type to determine which Page Layout is rendered.

Step-by-Step Solution

1
Identify the role of Record Types
Recognize that Record Types govern business processes and filter picklist choices per business unit.
Record Types segment picklist options and assign appropriate layouts across profiles.
2
Identify the role of Page Layouts
Recognize that Page Layouts structure the visual organization of fields and buttons on standard record pages.
Page Layouts define the content and ordering of fields, sections, and related lists.
3
Identify the role of the Assignment Matrix
Connect Profile + Record Type pairing to the selection of a specific Page Layout.
Salesforce uses the user's assigned Profile and the record's Record Type to determine which layout to render.

Key Concept

Page Layouts and Record Types Assignment
Question 620Question

A Salesforce Administrator is evaluating security requirements for different administrative requests. Match each security requirement on the left with the most appropriate Salesforce security mechanism on the right.

Click a left item, then click its matching right item

Items

Restrict access to a sensitive 'Tax Identification Number' field across all UI views, reports, list views, and API calls for users assigned to a specific profile.
Grant Read and Create permissions on the custom 'Audit Record' object to all users assigned to the Compliance Operations team.
Completely prevent users assigned to the Customer Support profile from logging into Salesforce when they are outside the corporate network.
Grant access to a restricted field for a single user without modifying the permissions of other users who share the same assigned profile.

Matches

Show answer & explanation

Answer

1. Field-Level Security on Profile controls field access across all entry points; 2. Object Permissions on Profile establish baseline object-level CRUD access; 3. Profile Login IP Ranges restrict login access based on network IP address; 4. Permission Sets grant incremental access to individual users.
Each business requirement aligns with a specific Salesforce security feature: Field-Level Security restricts field access everywhere across the platform; Object Permissions grant object CRUD rights for a profile; Profile Login IP Ranges enforce strict network restriction for users on that profile; and Permission Sets extend permissions to individual users without modifying shared profiles.

Step-by-Step Solution

1
Analyze field-level privacy requirements
Determined that securing a field across all UI, reporting, and API interfaces requires Field-Level Security (FLS).
Page layouts and dynamic forms only affect specific record pages, whereas FLS enforces data security at the database layer.
2
Evaluate object-level permission configuration for group access
Matched object Read/Create access across a department profile to Object Permissions (CRUD).
Profiles set baseline Create, Read, Edit, and Delete access for standard and custom objects.
3
Examine profile-based network security controls
Associated login restriction by IP address to Profile Login IP Ranges.
Profile login IP ranges strictly block logins from unapproved IP addresses, unlike Org-Wide Network Access which allows verification.
4
Address single-user exception management
Selected Permission Sets to grant specialized field access to a single user.
Permission Sets extend user permissions non-destructively without forcing profile cloning or profile sprawl.

Key Concept

Salesforce Security Architecture: Object Permissions, Field-Level Security, Profile Login Restrictions, and Permission Sets
PreviousPage 31 / 90Next
All practice questions — Salesforce Certified Administrator | Examkin