All practice questions

1784 questions

Question 661Question

A Salesforce administrator at an electric vehicle battery recycling company is modifying custom field configurations on the Lead object and a custom object used to track battery health inspections. The administrator needs to convert an existing custom text field to a numeric field and establish custom Lead field mapping for converted records. Which two statements accurately describe the behaviors and considerations for these custom field modifications? (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 during lead conversion.; Changing a custom field's data type from Text to Number can result in data loss if existing records contain non-numeric characters.

Answer

The two correct statements are that custom Lead fields can only be mapped to custom fields on target objects (Account, Contact, or Opportunity) during lead conversion, and changing a custom field's data type from Text to Number can result in data loss if existing records contain non-numeric text.
Custom Lead field mapping allows mapping custom Lead fields exclusively to custom fields on target objects (Account, Contact, or Opportunity) of compatible data types. In addition, changing a field's data type from Text to Number carries a risk of data loss whenever existing values contain non-numeric characters.

Step-by-Step Solution

1
Evaluate Lead custom field mapping rules.
Confirm that custom fields on the Lead object can only map to custom fields on Account, Contact, or Opportunity.
Salesforce Lead conversion setup does not allow custom Lead fields to map to standard target fields.
2
Analyze data type conversion consequences for Text to Number.
Identify that data loss occurs when text fields with non-numeric content are converted to number data types.
Non-numeric characters cannot be converted into numbers, leading to data truncation or removal.
3
Evaluate distractor claims regarding roll-up summaries and master-detail behavior.
Verify that roll-up summary fields require master-detail relationships and deleting master records deletes detail records.
Lookup relationships do not support native roll-up summary fields and master deletion cascades to detail records.

Key Concept

Custom Field Data Type Conversion and Lead Field Mapping
Question 662Question

Apex Financial Services uses a custom object named Audit_Report__c with an Organization-Wide Default (OWD) set to Private. The Security Administrator must implement access controls to satisfy two operational requirements:
1. Managers must automatically inherit Read and Edit access to all Audit Report records owned by their subordinates in the role hierarchy.
2. Members of the Compliance Department must receive Read/Write access to any Audit Report record where the Risk_Rating__c field is set to 'High Risk', regardless of who owns the record.

Which TWO configuration steps should the System Administrator take to fulfill these requirements?

Select all that apply

Show answer & explanation

Answer: Ensure that the 'Grant Access Using Hierarchies' checkbox remains selected on the Audit_Report__c custom object definition.; Create a criteria-based sharing rule on Audit_Report__c to share records matching Risk_Rating__c = 'High Risk' with the Compliance Department public group with Read/Write access.

Answer

The System Administrator should ensure 'Grant Access Using Hierarchies' remains selected on the custom object and create a criteria-based sharing rule sharing records where Risk Rating equals 'High Risk' with the Compliance Department public group.
Keeping 'Grant Access Using Hierarchies' enabled allows managers higher in the role hierarchy to automatically inherit access to records owned by their subordinates. Creating a criteria-based sharing rule allows access to be conditionally extended to the Compliance Department based on specific field values like Risk Rating.

Step-by-Step Solution

1
Evaluate managerial access inheritance requirements.
Keeping 'Grant Access Using Hierarchies' enabled ensures higher-level roles automatically inherit read and edit access to records owned by direct and indirect subordinates.
Role hierarchy access inheritance operates automatically without needing extra sharing rules when OWD is Private.
2
Evaluate conditional record access requirements based on field values.
Define a criteria-based sharing rule on Audit_Report__c with criteria Risk_Rating__c = 'High Risk' and set access level to Read/Write for the Compliance group.
Criteria-based sharing rules allow access to be granted based on specific record data rather than record ownership.

Key Concept

Role Hierarchy Inheritance and Criteria-Based Sharing Rules
Question 663Question

A Salesforce Administrator at Vanguard Cyber Solutions is introducing a new software offering named ThreatShield Pro. The administrator created the Product record and marked it as Active. When attempting to add ThreatShield Pro to the custom Enterprise Price Book, Salesforce displays an error preventing the record from being saved. Which action must the administrator take first before ThreatShield Pro can be added to any custom price book?

Show answer & explanation

Answer: Create and activate an entry for ThreatShield Pro in the Standard Price Book.

Answer

The administrator must create and activate a entry in the Standard Price Book for the product before adding it to custom price books.
In Salesforce core administration, a product must have an active entry in the Standard Price Book before it can be assigned to custom price books. The standard price establishes the default baseline value required by the architecture.

Step-by-Step Solution

1
Identify the standard price prerequisite for products
Recognize that Salesforce requires a valid Standard Price Book entry prior to custom price book entries
Salesforce architecture mandates a standard price baseline for all active products across price books
2
Create the standard price entry
Add a price entry to the Standard Price Book for ThreatShield Pro and set its status to active
This satisfies the system constraint allowing custom price books to reference the product
3
Add to custom price books
Successfully save ThreatShield Pro in the custom Enterprise Price Book
The prerequisite standard price entry now exists

Key Concept

Standard Price Book Entry Prerequisite
Question 664Question

A Salesforce Administrator is customizing a record page using Dynamic Forms in Lightning App Builder. The administrator needs to configure a custom field named 'Discount Reason' so that it only appears on the record page when the 'Discount Applied' picklist field is set to 'Yes'. Which feature in Lightning App Builder should the administrator use to meet this requirement?

Show answer & explanation

Answer: Component visibility filters on the field component set to show when 'Discount Applied' equals 'Yes'

Answer

Component visibility filters on the field component set to show when 'Discount Applied' equals 'Yes'
With Dynamic Forms, administrators can break down record details into individual field components and set component visibility rules directly on any field. Filtering the 'Discount Reason' field based on the 'Discount Applied' picklist value equal to 'Yes' satisfies the business requirement directly within Lightning App Builder.

Step-by-Step Solution

1
Open the record page in Lightning App Builder and select the 'Discount Reason' field component within the Dynamic Forms layout.
The component properties panel opens on the right sidebar.
Individual fields placed in Dynamic Forms act as standalone components with configurable properties.
2
Add a Component Visibility Filter under the Set Component Visibility section.
A filter rule configuration prompt appears.
Visibility filters determine under what conditions the component is displayed to the user.
3
Define the filter criteria as Record Field 'Discount Applied' Equal 'Yes' and save the page.
The field dynamically renders only when 'Discount Applied' equals 'Yes'.
Dynamic Forms evaluates record values in real time to conditionally show or hide fields.

Key Concept

Dynamic Forms Component Visibility Filters
Estimated Time:1m 0s
Question 665Question

An administrator at Northern Trail Outfitters creates a new Product record for a consulting service. The administrator needs to make this product available for sales representatives to add to opportunities using custom price books. What prerequisite step must be completed before the product can be added to any custom price book?

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.
In Salesforce, creating an active price entry in the Standard Price Book is a mandatory prerequisite before a product can be associated with any custom price book.

Step-by-Step Solution

1
Determine the required sequence for product pricing configuration in Salesforce.
Salesforce architecture mandates that a product must have an active standard price in the Standard Price Book before it can be added to any custom price books.
The Standard Price Book serves as the baseline catalog entry for any product.

Key Concept

Standard Price Book entry requirement prior to custom price book assignment
Question 666Question

A Salesforce administrator is documenting the standard system execution sequence that occurs when a sales representative converts a Lead. Place the following Lead conversion execution steps in the correct chronological order from first to last.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct order of lead conversion steps is: 1) Validation rules and system checks evaluate on the Lead record; 2) Account and Contact records are created or matched; 3) Mapped custom Lead field values are written to designated target fields; 4) The Opportunity record is created and linked (unless suppressed); 5) The Lead status updates to Converted, marking the record read-only.
During Lead conversion, Salesforce executes validation rules on the Lead record first to verify data integrity. Once validated, the system creates or matches the destination Account and Contact records. Custom Lead field mapping then writes data into the respective target fields across the generated or matched objects. Next, the system creates an Opportunity (unless the representative chose not to create one). Finally, Salesforce updates the Lead status to Converted, locks the Lead record as read-only, and links it to the converted Account, Contact, and Opportunity records.

Step-by-Step Solution

1
Evaluate Lead Record Integrity
Salesforce executes Lead validation rules and system checks to ensure all required conversion criteria are met.
If validation fails, conversion halts immediately before any target records are created or updated.
2
Instantiate Target Account and Contact Objects
Target Account and Contact records are identified through matching or newly created in the database.
Target records must exist prior to populating field values or linking child records.
3
Execute Lead Custom Field Mapping
Values from mapped custom Lead fields copy into designated Account, Contact, and Opportunity fields.
Data transfer takes place immediately after destination records are established.
4
Generate Opportunity Record
The Opportunity record is created and associated with the newly created or matched Account and Contact.
Opportunity generation occurs downstream of Account and Contact instantiation unless the user selected the option to suppress Opportunity creation.
5
Finalize Lead Status and Lock Record
The Lead status is updated to Converted, setting the Lead record to read-only state and establishing lookup relationships to the converted Account, Contact, and Opportunity records.
Updating Lead status and enforcing read-only permissions completes the lead conversion lifecycle.

Key Concept

Lead Conversion System Execution Sequence
Question 667Question

An administrator adds a custom component to an Account Record Page and applies component visibility filters so that it appears only for users with the Executive profile. A colleague suggests that this setting will also prevent non-executive users from seeing the underlying data in custom reports. Which statement accurately describes the security behavior of Lightning App Builder component visibility filters?

Show answer & explanation

Answer: Component visibility filters only control whether the component renders on the Lightning page; they do not restrict data access in reports, list views, or API calls.

Answer

Component visibility filters only control whether the component renders on the Lightning page; they do not restrict data access in reports, list views, or API calls.
Component visibility rules in Lightning App Builder are client-side UI display criteria. They control whether a component is visible on the screen but do not enforce security or restrict access to data accessed through reports, list views, or external APIs.

Step-by-Step Solution

1
Identify the purpose of Lightning App Builder component visibility filters.
Recognize that visibility filters dictate UI presentation conditions on a specific Lightning page.
Filters evaluate record fields, user attributes, or device factors strictly to display or hide components.
2
Evaluate the impact on data access mechanisms like reports, list views, and APIs.
Understand that visibility rules do not affect underlying data access controls such as Field-Level Security (FLS) or Object Permissions.
Security permissions must be configured in Profiles, Permission Sets, or Object Manager, not on Lightning page component settings.

Key Concept

Lightning App Builder Component Visibility vs. Data Security
Question 668Question

An administrator at Horizon Logistics adds a regional helpdesk lead to a Delegated Administration group configured to manage users in the 'EMEA Support' role hierarchy. The helpdesk lead needs to immediately restrict system access for an employee in the 'EMEA Support' role following a credential compromise. However, this employee is currently designated as the default case owner for incoming support requests. Which action can the delegated administrator take to immediately block access without breaking system configuration dependencies?

Show answer & explanation

Answer: Freeze the user account directly from the user detail page.

Answer

Freezing the user account directly from the user detail page is the correct action to immediately prevent login access while retaining record ownership and setup configuration dependencies.
Delegated administrators with user management permissions over a role hierarchy can freeze user accounts in those roles. Freezing immediately prevents user login without removing the user from default case ownership settings or active workflows.

Step-by-Step Solution

1
Identify the immediate requirement and system constraints.
The goal is to stop user login immediately for an employee who is set as a default owner in Case automation.
Deactivating a user assigned to automated process defaults (like default case owner) requires reassigning those processes first.
2
Evaluate administrative permissions granted to a Delegated Administrator.
Delegated administrators can freeze accounts of users in specified roles, but cannot alter org-wide security parameters or build new profiles.
Delegated administration scope is strictly limited to specified roles, profiles, and delegated tasks.
3
Select the capability that meets both security and operational needs.
Freezing the account blocks user authentication while leaving the account active for system setup dependencies.
User freezing was designed specifically to revoke access immediately when deactivation cannot be completed straight away due to system references.

Key Concept

Delegated User Management and User Freezing capabilities
Estimated Time:1m 30s
Question 669Question

A Salesforce Administrator at a consulting firm is designing data tracking capabilities between a custom parent object, Project__c, and a custom child object, Project_Task__c. The two objects are currently linked using a standard Lookup relationship. The administrator needs to display the total estimated hours from related Project_Task__c records on the Project__c record, as well as display parent Project__c budget details on each Project_Task__c record. Which two statements accurately reflect the capabilities and limitations of Roll-Up Summary and Formula fields in this setup? (Select 2 answers)

Select all that apply

Show answer & explanation

Answer: A Roll-Up Summary field cannot be created on Project__c unless the relationship to Project_Task__c is converted from a Lookup to a Master-Detail relationship.; Cross-object formula fields on Project_Task__c can reference fields on Project__c regardless of whether the relationship is a Lookup or a Master-Detail relationship.

Answer

Roll-Up Summary fields require a Master-Detail relationship to function on the parent object, whereas cross-object formula fields can span across both Lookup and Master-Detail relationships.
Standard Salesforce Roll-Up Summary fields require a Master-Detail relationship on the parent object to aggregate child values (COUNT, SUM, MIN, MAX). In contrast, cross-object formula fields on child objects can freely reference fields from parent objects across both Lookup and Master-Detail relationships.

Step-by-Step Solution

1
Evaluate Roll-Up Summary field prerequisites
Identify that standard declarative Roll-Up Summary fields are exclusively supported on the master object of Master-Detail relationships.
Salesforce platform constraints prevent standard roll-up calculations on parent records linked strictly via Lookup relationships.
2
Evaluate Cross-Object Formula field capabilities
Confirm that child objects can reference parent field attributes using cross-object formula syntax over Lookup or Master-Detail links.
Formula fields pull data upward along relationship paths up to 10 levels deep regardless of relationship strength.

Key Concept

Roll-Up Summary Relationship Requirements and Cross-Object Formula Capabilities
Question 670Question

An administrator recently created a new Record Type for Support Cases named 'Tier 3 Incident'. However, support agents report that when creating a 'Tier 3 Incident' case, they can still select picklist values that apply only to standard Tier 1 support cases. What administrative action was omitted during configuration?

Show answer & explanation

Answer: Modifying and assigning the selected picklist values specifically available for the new Record Type.

Answer

The administrator omitted editing the picklist values for the newly created Record Type in Object Manager.
When a new Record Type is created on an object, Salesforce automatically includes all existing values from master picklists. To display only relevant picklist options, the administrator must explicitly edit the picklists available under that Record Type's configuration page.

Step-by-Step Solution

1
Identify the cause of irrelevant picklist options appearing on a newly created Record Type.
When a new Record Type is created, Salesforce automatically includes all values from the master picklist.
Record Types allow administrators to restrict available picklist values for specific business processes.
2
Determine the necessary administrative step to resolve the issue.
The administrator must open the Record Type in Object Manager and edit the picklist field settings to remove unneeded values.
Configuring available picklist values per Record Type ensures users only select values relevant to that specific record type.

Key Concept

Record Type Picklist Value Assignment
Question 671Question

A Salesforce Administrator is configuring a Lightning Record Page for a custom object named Contract_Review__c. The compliance team outlines two strict requirements:
1. The sensitive field Risk_Audit_Notes__c must only appear on the record page layout when the Contract_Value__c is greater than $1,000,000 and the viewing user possesses the specific permission set Risk_Auditor_Access.
2. Users who do not meet these criteria must be entirely prevented from accessing Risk_Audit_Notes__c data across all interfaces, including Reports, Dashboards, Global Search, and API integrations.

Which combination of administrative configurations must be implemented to fulfill both requirements?

Show answer & explanation

Answer: Restrict Field-Level Security (FLS) on Risk_Audit_Notes__c so that read and edit access are granted exclusively through the Risk_Auditor_Access permission set, and configure a Dynamic Forms component visibility rule on the Lightning Record Page using the Contract_Value__c field filter.

Answer

Restrict Field-Level Security (FLS) on the target field to the permission set for underlying data protection, and use Dynamic Forms component visibility rules on the Lightning Record Page for contextual UI display.
The correct solution enforces a multi-layered security and UI strategy. Restricting Field-Level Security (FLS) via the Risk_Auditor_Access permission set ensures that unauthorized users cannot view data in Risk_Audit_Notes__c through reports, dashboards, global search, or API integrations. Concurrently, using Dynamic Forms component visibility rules on the Lightning Record Page ensures the field dynamically appears only when the Contract_Value__c meets the $1,000,000 threshold for qualified users.

Step-by-Step Solution

1
Evaluate data security requirements across APIs, Reports, and Search.
Dynamic Forms component visibility only controls presentation on Lightning record pages; it does not secure data across APIs or Reports.
Field-Level Security (FLS) is necessary to restrict read/edit access system-wide.
2
Configure Field-Level Security (FLS) using Permission Sets.
Remove profile-level read access and grant read/edit access to Risk_Audit_Notes__c solely via the Risk_Auditor_Access permission set.
Follows the principle of least privilege and additive permission management.
3
Configure Dynamic Forms for conditional UI presentation.
Add a component visibility rule on the field or field section in Lightning App Builder filtering by Contract_Value__c > 1000000.
Dynamically shows or hides the field on the Lightning page based on real-time record state.

Key Concept

Field-Level Security (FLS) vs. Dynamic Forms Component Visibility
Question 672Question

A Salesforce administrator at a renewable energy infrastructure firm is troubleshooting a lead conversion issue. Custom picklist field mapping has been established from the Lead object field System_Type__c to the Opportunity object field System_Type__c. When sales representatives attempt to convert qualified leads while creating a new Opportunity assigned to the 'Commercial Solar' Record Type, the system displays an error indicating that the selected picklist value 'Microgrid Utility' is invalid for the destination record type, causing lead conversion to fail. Both custom picklist fields contain identical active picklist values. Which administrative configuration change will resolve this lead conversion failure?

Show answer & explanation

Answer: Edit the 'Commercial Solar' Opportunity Record Type settings and add the 'Microgrid Utility' picklist value to the list of available values for the System_Type__c field.

Answer

The administrator must edit the 'Commercial Solar' Opportunity Record Type settings and enable the 'Microgrid Utility' picklist value for the System_Type__c field.
When leads are converted into Accounts, Contacts, or Opportunities with specific Record Types assigned, any custom fields populated via Lead Custom Field Mapping must adhere to the picklist value constraints of the target record type. If a mapped picklist value is active on the field definition level but disabled for the chosen target Record Type, Salesforce enforces record type validity and blocks record creation during conversion. Adding the value to the target Record Type's picklist selection resolves the issue.

Step-by-Step Solution

1
Analyze the lead conversion error message
Identify that lead field mapping successfully pushes the Lead value 'Microgrid Utility' to the Opportunity object, but the target Opportunity Record Type rejects the value.
When converting leads into records assigned to specific record types, target fields must allow the mapped value within that specific record type's picklist selection.
2
Navigate to Object Manager > Opportunity > Record Types > Commercial Solar
Locate the picklist assignment configuration for the custom field System_Type__c on the Commercial Solar record type.
Record Type configurations control which picklist values are valid and visible for records assigned to that record type.
3
Add 'Microgrid Utility' from Available Values to Selected Values for the record type
The target Opportunity record type now accepts 'Microgrid Utility' upon lead conversion.
Enabling the picklist value on the target record type resolves the validation conflict during lead conversion.

Key Concept

Lead Field Mapping and Target Record Type Picklist Constraints
Estimated Time:2m 0s
Question 673Question

Cloud Solar Solutions manages utility-scale installations using a custom object named Project Site. All members of the Operations department are assigned to a custom profile named 'Operations Specialist'. Management requires that only three specific Operations team members have Read and Edit access to a sensitive custom field, Environmental_Impact_Score__c, while all other Operations users must not see or edit this field. Furthermore, all users assigned to the Operations Specialist profile must be strictly restricted from logging in outside the corporate network IP range, while users on other profiles should not be affected.

Which TWO configuration actions should the Salesforce Administrator take to fulfill these requirements? (Choose 2 answers)

Select all that apply

Show answer & explanation

Answer: Set Field-Level Security for Environmental_Impact_Score__c to hidden on the Operations Specialist profile, create a Permission Set with Read and Edit access for the field, and assign it to the three specific users.; Define the allowed IP boundaries under Login IP Ranges directly on the Operations Specialist profile settings.

Answer

The correct actions are: setting Field-Level Security for the field to hidden on the profile and assigning a Permission Set with Read and Edit access to the three designated users, and defining the allowed IP address ranges under Login IP Ranges directly on the profile.
Field-Level Security at the profile level sets the most restrictive baseline. Applying FLS (hidden) on the Operations Specialist profile prevents unauthorized viewing. A Permission Set is then used to grant additive Read and Edit access to the target subset of users. Simultaneously, configuring Login IP Ranges on the Operations Specialist profile strictly restricts login access to designated IP ranges for users assigned to that profile.

Step-by-Step Solution

1
Evaluate field accessibility requirements for specific users on a shared profile.
Identify that profiles set baseline access, and permission sets add permissions for specific users.
Restricting FLS on the profile ensures non-authorized users cannot view the field, while a Permission Set grants additive Read/Edit access to the three specific team members.
2
Evaluate profile-specific login IP restriction requirements.
Determine that profile-level Login IP Ranges enforce strict login boundaries per profile.
Configuring Login IP Ranges on the profile denies login access outside specified ranges for users on that profile without impacting other profiles.

Key Concept

Profiles establish baseline access restrictions (such as Profile Login IP Ranges and default FLS), while Permission Sets extend object and field access to specific users additively.
Question 674Question

A sales representative at a commercial solar energy provider is preparing to convert a qualified lead in Salesforce. Which standard record creation can be optionally bypassed during the lead conversion process?

Show answer & explanation

Answer: Opportunity

Answer

Opportunity record creation is optional during lead conversion by selecting the option to not create a new opportunity.
In standard Salesforce Lead conversion, users can select a checkbox labeled 'Don't create a new opportunity upon conversion' (or 'Do not create a new opportunity upon conversion'), making the Opportunity record optional. Account and Contact records are required.

Step-by-Step Solution

1
Identify the standard records involved in Salesforce Lead conversion.
Lead conversion evaluates Account, Contact, and Opportunity records.
Converting a qualified lead always relates candidate data to business account and individual contact structures.
2
Determine mandatory versus optional record generation settings on the conversion screen.
Account and Contact records (or existing record selections) are required, while Opportunity creation features a checkbox to omit creation.
Salesforce allows administrators and users to skip Opportunity creation when immediate deal pipeline tracking is not needed.

Key Concept

Lead Conversion Record Creation Rules
Question 675Question

A Salesforce Administrator at Nexus Telecom is introducing a new fiber-optic enterprise product line across multiple international business units. The administrator created the new Product record with active status and established custom schedules for revenue installment billing. However, when trying to add this product to the newly created 'LATAM Enterprise Custom Price Book', the system prevents the administrator from saving the price book entry. What mandatory configuration step did the administrator omit prior to adding the product to the custom price book?

Show answer & explanation

Answer: Creating and activating a price entry for the product in the Standard Price Book.

Answer

The administrator must first create and activate a price entry for the product in the Standard Price Book before adding it to any custom price book.
In Salesforce, the Standard Price Book serves as the foundational master price list. A product must have an active standard price entry in the Standard Price Book before it can be added to any custom price books (such as regional or segment-specific price books).

Step-by-Step Solution

1
Identify the core relationship between Products, Standard Price Books, and Custom Price Books in Salesforce.
Salesforce architecture mandates that the Standard Price Book acts as the master repository for product pricing.
A product cannot exist in a custom price book without a baseline standard price entry.
2
Analyze the error encountered when creating a custom price book entry.
The attempt failed because no active entry exists in the Standard Price Book for the newly created product.
Salesforce enforces standard price book entry existence and activation as a system requirement.
3
Determine the required administrative resolution step.
Add the product to the Standard Price Book with an active standard price.
Once the standard price book entry is created and activated, the product becomes eligible for insertion into custom price books.

Key Concept

Standard Price Book Entry Requirement for Custom Price Books
Question 676Question

An administrator created a new Record Type named 'Vendor Support' on the Case object and assigned the 'Vendor Case Layout' to the 'Tier 2 Support' profile for this Record Type. However, users assigned to the 'Tier 2 Support' profile report two unexpected behaviors: 1) When creating a 'Vendor Support' case, the Priority picklist still displays the value 'Critical - Emergency', which is meant only for internal system outages. 2) Users who were granted access to the 'Vendor Support' Record Type solely through a Permission Set (while remaining assigned to the 'Standard User' profile) see the default 'Standard Case Layout' instead of the 'Vendor Case Layout' when viewing 'Vendor Support' records. Which statement accurately explains the root causes of these behaviors and the correct configuration steps to resolve them?

Show answer & explanation

Answer: Available picklist values must be configured explicitly for each Record Type in Object Manager, and Page Layout assignments are strictly determined by a user's Profile, not by Permission Sets.

Answer

Available picklist values must be configured explicitly for each Record Type in Object Manager, and Page Layout assignments are strictly determined by a user's Profile, not by Permission Sets.
The correct answer accurately identifies that Record Type picklist availability is configured under each specific Record Type in Object Manager, and that Page Layout assignment is governed strictly by a user's Profile combined with the Record Type. Permission Sets can grant access to a Record Type, but they cannot assign Page Layouts.

Step-by-Step Solution

1
Analyze the picklist restriction issue
Creating a Record Type does not automatically filter picklist values; available values must be edited explicitly under Object Manager > Case > Record Types > [Record Type Name] > Picklists Available for Editing.
Page Layouts display fields, but Record Types govern which picklist values are selectable for records assigned to that Record Type.
2
Analyze the Page Layout assignment behavior for Permission Set users
Permission Sets grant visibility to Record Types, but Page Layout assignment matrix entries are strictly mapped per Profile and Record Type.
Users assigned to the 'Standard User' profile will see whichever Page Layout is mapped to 'Standard User' for that Record Type in the Page Layout Assignment matrix, regardless of how Record Type access was granted.
3
Synthesize the resolution requirement
Edit the 'Vendor Support' Record Type picklist settings to remove 'Critical - Emergency', and update the Page Layout Assignment for the 'Standard User' profile to map the 'Vendor Support' Record Type to 'Vendor Case Layout' if desired.
This correctly resolves both the picklist value availability and profile-based layout display requirements.

Key Concept

Page Layout Assignment Matrix and Record Type Picklist Value Selection
Estimated Time:2m 0s
Question 677Question

A sales operations team at NovaTech Systems is launching a multi-currency software suite for regional sales reps. The administrator needs to configure a newly created 'APAC Regional Custom Price Book' containing the new software product so reps can add it as an Opportunity Line Item. Which two configuration steps or rules must the administrator ensure are completed for this setup to function properly? (Select 2 options)

Select all that apply

Show answer & explanation

Answer: The product record itself must have its 'Active' checkbox selected.; Every currency price intended for the custom price book must first exist as an active entry within the Standard Price Book.

Answer

The product must be marked as Active, and an active price entry in the Standard Price Book must exist for each currency before adding the product to a Custom Price Book.
To successfully make a product available for selection on opportunities via a Custom Price Book, two key requirements must be satisfied: the Product record must be set to Active, and an active entry for each desired currency must exist in the Standard Price Book before adding the product to any Custom Price Book.

Step-by-Step Solution

1
Verify product active status
Ensure the product record's Active checkbox is set to true.
Inactive products cannot be added as Opportunity Line Items.
2
Create Standard Price Book entries
Add an active standard price for each required currency in the Standard Price Book.
Salesforce requires a product to have a standard price in a given currency before it can be added to any custom price book in that currency.
3
Add to Custom Price Book
Add the product entries to the 'APAC Regional Custom Price Book'.
With active standard entries present, custom price book entries can now be created and activated.

Key Concept

Product and Price Book Entry Prerequisites
Question 678Question

A system administrator at a commercial solar energy provider is setting up a streamlined lead conversion process for enterprise prospects. To ensure data integrity, custom qualification details from qualified leads must automatically map to custom fields on the Account, Contact, and Opportunity records generated during conversion, while respecting validation rules. What is the correct sequence of administrative steps required to configure and verify this custom lead field mapping workflow?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence starts with creating compatible target custom fields on Account, Contact, and Opportunity, navigating to Map Lead Fields under Object Manager, mapping source fields to destination fields across object tabs, setting target validation rules, and finally executing a test lead conversion to verify data population.
Configuring Lead Custom Field Mapping requires establishing destination custom fields on target objects before mapping them in the Lead object settings. Following mapping setup, target record validation rules ensure incoming mapped data conforms to quality requirements, and testing the lead conversion completes the verification cycle.

Step-by-Step Solution

1
Create custom target fields on destination objects.
Destination objects (Account, Contact, Opportunity) possess matching fields capable of receiving data.
Salesforce requires target custom fields to exist before they can be selected in the Lead Custom Field Mapping configuration interface.
2
Open Lead Custom Field Mapping in Object Manager.
The administrator views the mapping matrix for Account, Contact, and Opportunity target tabs.
Field mapping is managed under the Lead object settings within Object Manager.
3
Establish field-to-field mapping pairings.
Custom Lead fields are linked to target object custom fields.
Data type compatibility must be maintained across mapped fields (e.g., text to text, picklist to picklist).
4
Activate data quality validation rules on target objects.
Target records will validate mapped incoming values during conversion.
Target object validation rules evaluate mapped Lead data when converted records are saved.
5
Execute a test conversion of a qualified Lead record.
Converted Account, Contact, and Opportunity records display properly mapped custom values.
Functional testing confirms seamless execution of data mapping and rules without system exceptions.

Key Concept

Lead Custom Field Mapping Configuration Sequence
Estimated Time:2m 0s
Question 679Question

A Salesforce administrator at a renewable energy company is configuring Lead Custom Field Mapping to ensure qualified prospect preferences transfer during conversion. The administrator creates a custom picklist field on the Lead object named 'Installation Type'. However, when attempting to map this field in Lead Conversion Settings, the expected target custom field on the Contact object does not appear in the dropdown menu. What is the most likely cause of this issue?

Show answer & explanation

Answer: The custom field on the Contact object has a different data type than the custom picklist field on the Lead object.

Answer

The custom field on the Contact object has a different data type than the custom picklist field on the Lead object.
In Salesforce Lead Custom Field Mapping, target custom fields on Account, Contact, or Opportunity objects must have matching data types with the source custom field on the Lead object. If a custom Picklist field on Lead is being mapped, only custom Picklist fields on the target objects will appear in the mapping dropdown.

Step-by-Step Solution

1
Identify the lead conversion field mapping requirement in Salesforce.
Lead Custom Field Mapping requires target fields on Account, Contact, or Opportunity to match the data type of the source Lead field.
Data type alignment ensures seamless data transfer without corruption during conversion.
2
Analyze why a created field would be excluded from the Lead field mapping dropdown.
If the Contact field was created as Text or another data type rather than Picklist, Salesforce filters it out from the mapping options for the Lead Picklist field.
Mismatch in field data types prevents mapping setup in Salesforce Setup.

Key Concept

Lead Custom Field Mapping Rules
Estimated Time:1m 15s
Question 680Question

A Salesforce Administrator at Apex Bio-Tech is preparing to launch a new hardware product line called 'BioSensor Pro'. The sales team requires a custom price book with specialized European regional pricing before sales representatives can quote this item on open sales deals. What is the correct sequence of configuration steps the administrator must perform to successfully enable reps to add this product to an Opportunity?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence begins with creating the active Product record, followed by establishing an active Standard Price Book entry. Next, the Custom Price Book is created and activated, after which the Product is added to the Custom Price Book with an active custom price entry. Finally, the Custom Price Book is selected on the Opportunity and the Product is added as an Opportunity Line Item.
In Salesforce, product administration follows a strict relational dependency model. First, the Product record must be created and activated. Second, a Standard Price Book Entry must be created and set to active; without an active standard price, Salesforce will block any attempts to add the product to custom price books. Third, the custom price book must be created and activated. Fourth, the product is added to the custom price book with an active custom price entry. Finally, sales reps can associate the custom price book with an opportunity and add the product as an opportunity line item.

Step-by-Step Solution

1
Create the Product record.
Product record 'BioSensor Pro' is created and marked Active in Salesforce.
Products serve as the catalog items upon which all pricing entries and line items are built.
2
Add a Standard Price to the Product.
An active Standard Price Book entry is created.
Salesforce data model architecture mandates an active standard price book entry before any custom price book entries can be assigned.
3
Create and activate the Custom Price Book.
The 'European Regional Custom Price Book' is active and available.
Custom price books hold currency-specific or segment-specific prices distinct from the standard price.
4
Create the Custom Price Book Entry.
An active price book entry links 'BioSensor Pro' to the European Custom Price Book with custom pricing.
Products cannot be selected from a custom price book on opportunities without an active price book entry in that specific price book.
5
Associate the Price Book with the Opportunity and add the Opportunity Line Item.
'BioSensor Pro' is successfully added as an Opportunity Line Item.
Sales reps can only pick products from the price book currently associated with the Opportunity.

Key Concept

Salesforce Price Book Architecture and Order of Setup Dependencies
PreviousPage 34 / 90Next
All practice questions — Salesforce Certified Administrator | Examkin