All practice questions

1784 questions

Question 621Question

An administrator is designing a custom data structure to manage IT infrastructure assets for an enterprise client. The requirement calls for establishing a many-to-many relationship between a custom object named Server_Instance__c and another custom object named Software_License__c using a custom junction object named License_Assignment__c. Additionally, business rules specify that deleting a Server_Instance__c record must automatically delete all associated License_Assignment__c records, and total active license fees must be calculated directly on the Server_Instance__c record. Which two configuration steps must the administrator complete on the License_Assignment__c object to fulfill these requirements? (Choose 2 answers.)

Select all that apply

Show answer & explanation

Answer: Create a Master-Detail relationship field referencing the Server_Instance__c custom object.; Create a Master-Detail relationship field referencing the Software_License__c custom object.

Answer

The administrator must create two Master-Detail relationship fields on the License_Assignment__c junction object: one referencing Server_Instance__c and one referencing Software_License__c.
To build a many-to-many relationship that supports automatic record deletion cascade and Roll-Up Summary field calculations on the primary object, the administrator must configure two Master-Detail relationship fields on the custom junction object (License_Assignment__c): one pointing to Server_Instance__c and the second pointing to Software_License__c.

Step-by-Step Solution

1
Analyze relationship requirements between Server_Instance__c and License_Assignment__c.
Determined that automatic cascade deletion and Roll-Up Summary capabilities on Server_Instance__c necessitate a Master-Detail relationship.
Master-Detail relationships enforce tight coupling where child records inherit security and lifecycle behavior from the master, enabling native Roll-Up Summary fields.
2
Analyze many-to-many relationship architecture across both master entities.
Determined that establishing a functional junction object requires a second Master-Detail relationship pointing to Software_License__c.
A custom junction object in Salesforce requires two Master-Detail relationship fields to connect two master objects in a many-to-many structure.

Key Concept

Junction Objects and Master-Detail Relationship Behaviors
Estimated Time:2m 0s
Question 622Question

A Salesforce administrator at a biomedical equipment laboratory is configuring custom fields to track service metrics. The laboratory has a parent custom object, Equipment Model, and a child custom object, Calibration Inspection. These two objects are currently connected by a Lookup relationship. The operations manager requires a field on the Equipment Model record that automatically calculates the total count of related Calibration Inspection records. When attempting to create a new field on Equipment Model, the administrator finds that the Roll-Up Summary data type option is disabled. Which configuration action should the administrator take to meet this requirement?

Show answer & explanation

Answer: Convert the Lookup relationship on Calibration Inspection to a Master-Detail relationship, and then create the Roll-Up Summary field on Equipment Model.

Answer

Convert the Lookup relationship on Calibration Inspection to a Master-Detail relationship, and then create the Roll-Up Summary field on Equipment Model.
Roll-Up Summary fields are only supported on the parent (master) object in a Master-Detail relationship. Converting the existing Lookup relationship between the child object (Calibration Inspection) and parent object (Equipment Model) into a Master-Detail relationship removes the restriction, enabling the administrator to create the required COUNT Roll-Up Summary field.

Step-by-Step Solution

1
Identify the relationship constraint for Roll-Up Summary fields.
Recognize that Salesforce natively allows Roll-Up Summary fields only on the master side of a Master-Detail relationship.
Lookup relationships do not support native declarative roll-up summary functionality.
2
Change the relationship type on the child object.
Ensure all child records have a populated parent lookup field, then convert the lookup field on Calibration Inspection to a Master-Detail relationship.
Master-Detail relationships require every detail record to be linked to a parent master record.
3
Create the Roll-Up Summary field.
Create a new custom field of type Roll-Up Summary on Equipment Model, selecting COUNT of Calibration Inspection records.
Once the Master-Detail relationship is established, the Roll-Up Summary option becomes available on the master object.

Key Concept

Roll-Up Summary Field Capabilities and Relationship Requirements
Question 623Question

Ursa Major Solar recently launched a new line of commercial solar panels. The Salesforce Administrator created the product record and set its status to active. Next, the administrator created a custom price book named "Government Contracting Price Book" and marked it as active. However, when sales representatives edit an opportunity and select the "Government Contracting Price Book", the new solar panel product does not appear in the product search list. Which configuration step did the administrator omit?

Show answer & explanation

Answer: Creating an active entry with a standard price for the product in the Standard Price Book

Answer

The administrator omitted creating an active entry with a standard price in the Standard Price Book prior to attempting to use the product in custom price books.
In Salesforce, a product must have an active standard price in the Standard Price Book before it can be added to any custom price book or selected as an Opportunity Line Item. Because the administrator created the product and the custom price book without creating the standard price book entry first, the product remains unavailable in the custom price book.

Step-by-Step Solution

1
Identify the prerequisite hierarchy for Salesforce Products and Price Books.
Recognize that a Product record requires an active Standard Price entry in the Standard Price Book before it can be added to custom price books.
Salesforce enforces standard price book entries as the foundational pricing reference for all products.
2
Analyze why the product is missing from the custom price book search on the Opportunity.
Even though both the Product and the Custom Price Book are marked active, the missing Standard Price Book entry prevents the product from being available for selection.
Without a standard price entry, custom price book entries cannot be established or displayed.
3
Select the resolution that addresses the foundational configuration requirement.
Add an active Standard Price entry in the Standard Price Book for the solar panel product.
This fulfills the mandatory Salesforce data model dependency.

Key Concept

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

A Salesforce administrator is tasked with updating the Case object user interface to support complex compliance requirements. Tier 2 Support Agents using the Service Console app require a dedicated Lightning Record Page layout when working on 'Escalated' cases, while Tier 1 agents must retain their existing layout. Additionally, a specialized SLA Compliance component on the new record page must only be visible to users assigned a custom permission named 'View Escalations', regardless of whether users have Field-Level Security (FLS) access to the SLA fields. Which two configuration actions must the administrator execute within Lightning App Builder to satisfy these requirements? (Select 2 choices)

Select all that apply

Show answer & explanation

Answer: Activate the custom Lightning Record Page as App, Record Type, and Profile default for the Service Console app, Escalated record type, and Tier 2 Support profile.; Add a conditional component visibility filter to the SLA Compliance component evaluating User > Permissions > Custom Permission > View Escalations equals True.

Answer

To meet the requirements, the administrator must activate the page using the App, Record Type, and Profile assignment combination and apply a component visibility filter based on the user's assigned custom permission.
The combination of activating the page at the App, Record Type, and Profile level and setting a component visibility filter based on user custom permissions fully addresses both requirements. App, Record Type, and Profile is the most specific activation scope in Lightning App Builder, ensuring Tier 2 agents see the customized page while Tier 1 agents continue using their current page assignment. Furthermore, Lightning App Builder allows component visibility filters to check assigned Custom Permissions directly on the user context.

Step-by-Step Solution

1
Determine the required activation precedence level in Lightning App Builder.
Recognize that conflicting target requirements for different profiles (Tier 1 vs Tier 2) within the same app and record type require the highest assignment specificity.
App, Record Type, and Profile assignment overrides Org Default and App Default settings, isolating the new page to Tier 2 agents in the Service Console on Escalated cases.
2
Configure component visibility for the SLA Compliance component.
Add a filter criterion using User > Permissions > Custom Permission > View Escalations set to True.
Lightning App Builder supports dynamic component visibility based on Client Device, Record Fields, or User attributes (including Custom Permissions).

Key Concept

Lightning Record Page Activation Precedence and Dynamic Component Visibility Filters
Estimated Time:2m 0s
Question 625Question

Universal Containers configured a custom Lightning Record Page for the Case object designed specifically for Tier 2 escalation engineers. The management team requires this customized layout to display only when engineers view cases assigned to the 'Tier 2 Escalation' Record Type while working inside the Service Console application. Support representatives viewing cases in the standard Sales application must continue seeing their existing app assignment. Which activation assignment combination must be configured in Lightning App Builder to satisfy this business requirement?

Show answer & explanation

Answer: Assign the new Lightning page as App, Record Type, and Profile, specifying the Service Console app, the Tier 2 Escalation record type, and the Tier 2 Support profile.

Answer

Assign the new Lightning page at the App, Record Type, and Profile level, selecting the Service Console application, Tier 2 Escalation record type, and Tier 2 Support profile.
Activating the Lightning Record Page using the 'App, Record Type, and Profile' level allows admins to define specific combinations where the layout should apply. Because the business requirement demands targeting a specific app (Service Console), record type (Tier 2 Escalation), and user profile, this granular activation option is required.

Step-by-Step Solution

1
Analyze the activation scope requirements
The requirement specifies restrictions based on three criteria: App (Service Console), Record Type (Tier 2 Escalation), and User Role/Profile (Tier 2 Support Representatives).
Lightning App Builder supports three activation levels: Org Default, App Default, and App, Record Type, and Profile.
2
Evaluate activation hierarchy precedence
The App, Record Type, and Profile combination has the highest precedence in Salesforce page assignment evaluation.
When a record page is assigned at the App + Record Type + Profile level, it overrides App Default and Org Default assignments whenever all three criteria match.
3
Select the correct activation option
Activating the page specifically for Service Console + Tier 2 Escalation record type + Tier 2 Support profile satisfies all conditions without altering experience in the Sales app.
Users in the Sales app or viewing different record types will safely fall back to the existing App Default or Org Default assignments.

Key Concept

Lightning Record Page Activation Hierarchy and Precedence
Question 626Question

A financial services company enforces a strict compliance policy requiring customer service representatives to access Salesforce exclusively from the designated corporate VPN IP ranges. If a representative attempts to log in from any external or unrecognized IP address, Salesforce must immediately deny the login attempt. Which administration setting should the Salesforce Administrator configure to enforce this requirement?

Show answer & explanation

Answer: Define the allowed IP address range under Login IP Ranges on the Customer Service Profile.

Answer

Configure Login IP Ranges directly on the Customer Service Profile.
Specifying IP ranges in the Login IP Ranges section of a Profile strictly limits where users assigned to that Profile can log in from. Any attempt to log in from an IP address outside the specified range is blocked immediately.

Step-by-Step Solution

1
Identify the security policy requirement
Login attempts from unauthorized IP addresses must be strictly blocked.
The requirement calls for absolute restriction rather than simple multi-factor authentication (MFA) bypass.
2
Evaluate Salesforce IP restriction features
Profile-level Login IP Ranges explicitly enforce login restrictions and block access outside the listed ranges.
Org-wide Network Access only manages trusted IPs for bypassing verification codes, whereas Profile Login IP Ranges completely prohibit unauthorized IP logins.
3
Select the appropriate user administration control
Add the allowed corporate IP range to the target user Profile under Login IP Ranges.
This directly satisfies the requirement for profile-based users.

Key Concept

Profile Login IP Ranges vs. Network Access IP Ranges
Question 627Question

A commercial real estate management firm is configuring Salesforce access control for various user roles and operational scenarios. Match each administrative security requirement on the left with the most appropriate Salesforce permission feature on the right.

Click a left item, then click its matching right item

Items

Grant temporary elevated permissions to an external compliance auditor for a 14-day audit window, ensuring access automatically revokes upon completion.
Bundle multiple functional permission sets into a single administrative unit to streamline assignment for Regional Property Managers.
Disable Delete permissions on Lease Contract records for a specific subset of users who are assigned a broader permission set bundle.
Grant additive read and edit permissions for a custom field to select users across different departments without changing their base profile assignments.

Matches

Show answer & explanation

Answer

Temporary access requirements match with Permission Set Assignment Expiration Date. Bundling permission sets matches with Permission Set Group. Restricting specific permissions inside a group matches with Muting Permission Set. Additive custom field access across profiles matches with Standalone Permission Set.
Each administrative requirement corresponds directly to standard Salesforce security tools. Temporary elevated access utilizes Permission Set Assignment Expiration Date. Aggregating multiple permission sets uses Permission Set Groups. Suppressing specific permissions within a group uses Muting Permission Sets. Granting incremental field access across diverse profiles uses Standalone Permission Sets.

Step-by-Step Solution

1
Analyze requirement 1 (temporary elevated access with automatic revocation)
Identify that Salesforce allows setting an expiration date on Permission Set assignments.
Assigning an expiration date automates permission revocation for time-bound projects or audits.
2
Analyze requirement 2 (bundling multiple permission sets for single assignment)
Identify Permission Set Group as the feature designed to aggregate multiple permission sets.
Permission Set Groups simplify user management by consolidating distinct permission sets into one assignable group.
3
Analyze requirement 3 (disabling delete access within a bundled group)
Identify Muting Permission Set as the mechanism to suppress permissions granted inside a Permission Set Group.
Muting Permission Sets allow fine-grained access control by disabling specific permissions within a Permission Set Group without altering individual member permission sets.
4
Analyze requirement 4 (granting additive access to a custom field across profiles)
Identify Standalone Permission Set as the best practice implementation.
Profiles establish baseline access, while Standalone Permission Sets grant additive field-level permissions flexibly across user profiles.

Key Concept

Salesforce Permission Sets, Permission Set Groups, Muting Permission Sets, and Assignment Expirations
Question 628Question

A Salesforce Administrator at a global telecommunications company has configured custom lead field mapping so that a custom picklist field on the Lead object, named Preferred SLA Tier, maps to a corresponding custom picklist field on the Account object, SLA Tier Level. During testing, sales representatives report that lead conversion fails with an error whenever they convert a lead into a new Account that uses the Enterprise Account Record Type. The lead conversion succeeds when converting leads into Accounts without a specific record type assignment. Which configuration issue is causing the conversion process to fail?

Show answer & explanation

Answer: The custom picklist value selected on the Lead is not enabled for the Enterprise Account Record Type on the Account object.

Answer

The custom picklist value selected on the Lead is not enabled for the Enterprise Account Record Type on the Account object.
The correct answer highlights a common platform edge case: during Lead conversion, if a target record (such as an Account) is created with a specific Record Type, any mapped custom picklist value from the Lead must be valid and enabled in the picklist settings for that target Record Type. If the value selected on the Lead is missing from the target Record Type's available picklist values, Salesforce generates a validation/conversion error.

Step-by-Step Solution

1
Analyze the lead conversion error symptoms
Conversion fails only when creating Accounts assigned to the 'Enterprise Account' Record Type, but succeeds for default/master record types.
This indicates that Record Type specific restrictions on the Account object are blocking data insertion.
2
Evaluate how custom field mapping interacts with target object Record Types
During conversion, Salesforce attempts to write the value from the Lead's custom picklist into the target Account custom picklist field.
If a Record Type is assigned during conversion, all picklist field values being set must be active and enabled in the picklist value set assigned to that Record Type.
3
Identify the root cause and required administrative resolution
The value on the Lead is missing from the Enterprise Account Record Type picklist selection list.
Enabling the picklist value for the Enterprise Account Record Type resolves the conversion error.

Key Concept

Lead Conversion Field Mapping and Target Record Type Picklist Validation
Question 629Question

A Salesforce administrator at a global logistics firm is setting up lead conversion settings to ensure prospect data transfers properly to downstream sales records. Which two statements correctly describe the platform behavior and constraints when configuring Lead Custom 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.; The data type of the target custom field must be compatible with the source custom Lead field being mapped.

Answer

Custom Lead fields can only be mapped to custom fields on the Account, Contact, or Opportunity objects, and the target custom field must have a compatible data type with the source Lead field.
Lead Custom Field Mapping allows administrators to map custom fields created on the Lead object specifically to custom fields on Account, Contact, or Opportunity records. Furthermore, the mapping tool enforces data type compatibility (e.g., matching text fields with text fields, or picklist fields with compatible text/picklist fields) to maintain data integrity during lead conversion.

Step-by-Step Solution

1
Review Lead Custom Field Mapping target object restrictions
Confirm that custom fields on the Lead object can only map to custom fields on Account, Contact, or Opportunity, and standard target fields cannot be selected.
Salesforce standard field mappings are pre-defined and fixed by system architecture.
2
Verify field data type mapping rules
Ensure source and target fields match compatible data types (e.g. Text to Text/Text Area, Picklist to Picklist/Text).
Data type mismatches will prevent mapping setup or lead conversion data population.

Key Concept

Salesforce Lead Custom Field Mapping rules and target data type compatibility constraints.
Question 630Question

An administrator is configuring Lightning Record Page activations for a custom object named Vendor_Contract__c. The page named 'Vendor Standard Page' is activated as the Org Default. Another page named 'Vendor Operations Page' is activated as the App Default for the Procurement app. Additionally, a third page named 'Vendor Executive Page' is activated for the Procurement app assigned specifically to the Executive profile and the Standard Contract record type. Which Lightning Record Page will a user with the Executive profile see when viewing a Vendor_Contract__c record assigned to the Standard Contract record type within the Sales Console app?

Show answer & explanation

Answer: Vendor Standard Page

Answer

The user will see the Vendor Standard Page because app-specific assignments only apply when working inside that specified application.
Lightning App Builder follows a strict activation evaluation order: App + Record Type + Profile > App Default > Org Default. However, app-specific assignments (including App Default and App + Record Type + Profile) are only evaluated when the user is navigating within that explicit Lightning app. Since the user is viewing the record within the Sales Console app, the Procurement app assignments are ignored, and Salesforce displays the Org Default ('Vendor Standard Page').

Step-by-Step Solution

1
Evaluate the context of the user request
User is operating in the Sales Console app, holds the Executive profile, and is viewing a record with the Standard Contract record type.
Lightning Record Page activation resolution depends on the current app context, record type, and user profile.
2
Check for matching App + Record Type + Profile activation
Vendor Executive Page is assigned to Procurement app + Executive profile + Standard Contract record type, which does NOT match the current app (Sales Console).
App-specific profile assignments require the user to be inside the designated app.
3
Check for matching App Default activation and fall back to Org Default
No App Default is defined for the Sales Console app, so Salesforce falls back to the Org Default ('Vendor Standard Page').
When no matching app-specific or record type/profile assignment exists for the active app, the Org Default page is displayed.

Key Concept

Lightning Record Page Activation Hierarchy and Precedence
Question 631Question

A Salesforce administrator at a logistics firm creates a new product record for premium freight services. The administrator attempts to add this new product to a custom price book named 'EMEA Enterprise Price Book', but Salesforce does not permit the addition. What prerequisite step must the administrator complete before adding the product to any custom price book?

Show answer & explanation

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

Answer

The administrator must create an active standard price entry for the product in the Standard Price Book before it can be added to any custom price book.
In Salesforce, every product must have an active standard price entry in the Standard Price Book before it can be associated with any custom price book. This ensures a master baseline price exists across the organization.

Step-by-Step Solution

1
Identify the dependency rule for Salesforce price books.
Products require a Standard Price Book entry to establish a baseline price.
Salesforce architecture mandates that the Standard Price Book acts as the master price record for all products.
2
Add an active Standard Price entry to the product record.
The product becomes available for inclusion in custom price books.
A valid, active standard price entry fulfills the prerequisite requirement for custom price book entries.

Key Concept

Standard Price Book prerequisites for Custom Price Books
Estimated Time:45s
Question 632Question

An administrator at a renewable energy company creates a new product record for 'Solar Optimizer Pro' and attempts to add it directly to a newly created custom price book named 'EMEA Commercial Sales'. However, the system throws an error and prevents the product from being added to the price book. What must the administrator do to resolve this issue?

Show answer & explanation

Answer: Create an active price entry for the product in the Standard Price Book before adding it to the custom price book.

Answer

The administrator must create an active price entry for the product in the Standard Price Book before adding it to the custom price book.
In Salesforce, the Standard Price Book contains the master list of all products and their default standard prices. A product MUST have an active entry in the Standard Price Book before it can be added to any custom price book. Creating and activating the standard price entry satisfies this architectural dependency.

Step-by-Step Solution

1
Identify the prerequisite for adding products to custom price books in Salesforce.
Salesforce architecture mandates that every product must have a Standard Price entry in the Standard Price Book prior to creating any Custom Price Book entries.
The Standard Price serves as the foundational baseline price for the product across the organization.
2
Verify product activation and standard price entry configuration.
Create a price entry in the Standard Price Book and check the 'Active' checkbox.
Without an active standard price entry, Salesforce restricts adding the product to any custom price books.
3
Add the product to the custom price book.
The product can now be added to 'EMEA Commercial Sales' with its custom price.
The standard price prerequisite has been fulfilled.

Key Concept

Standard Price Book entry requirement prior to custom price book entry creation
Estimated Time:1m 15s
Question 633Question

An administrator wants to display a custom field on an Opportunity Lightning record page only when the Opportunity Stage is set to 'Closed Won'. The administrator wants to achieve this directly on the page layout without modifying Field-Level Security or creating separate page layouts. Which feature should the administrator use?

Show answer & explanation

Answer: Component visibility rules on a field within Dynamic Forms

Answer

Component visibility rules on a field within Dynamic Forms
Dynamic Forms allow administrators to upgrade standard page layouts into flexible components in the Lightning App Builder and set component visibility rules on individual fields or sections based on record values such as Opportunity Stage.

Step-by-Step Solution

1
Identify the requirement
The requirement asks for dynamically showing a field on a Lightning Record Page based on a record field value (Stage = 'Closed Won') without changing Field-Level Security or page layouts.
Understanding the constraint helps rule out profile-level security changes and backend validation rules.
2
Evaluate Lightning App Builder capabilities
Dynamic Forms allow breaking record detail pages into individual field components and applying conditional component visibility filters.
Component visibility rules evaluate record criteria in real time to show or hide components on the page.

Key Concept

Dynamic Forms allow administrators to configure conditional visibility for individual fields and field sections directly within the Lightning App Builder based on record values, user profiles, or device factors.
Estimated Time:45s
Question 634Question

An administrator configures Dynamic Forms on a custom object record page and sets a component visibility rule to hide a sensitive financial field from users with a specific job role. A user with that role notes that although the field is hidden when viewing the record page in Lightning Experience, they can still view the field value when executing a custom report or querying data via the API. What is the root cause of this behavior?

Show answer & explanation

Answer: Dynamic Forms component visibility controls UI display on Lightning pages only and does not enforce Field-Level Security across reports, list views, or API access.

Answer

Dynamic Forms component visibility controls UI display on Lightning pages only and does not enforce Field-Level Security across reports, list views, or API access.
Dynamic Forms component visibility rules determine whether a field component is rendered on a Lightning record page. However, they do not restrict data access at the database level. If a user has Read permission for a field defined in their Profile or Permission Sets (Field-Level Security), they can still query and view the field via reports, list views, export tools, or API endpoints. To completely restrict access to a field, administrators must modify Field-Level Security.

Step-by-Step Solution

1
Analyze the scope of Dynamic Forms component visibility rules.
Dynamic Forms allow administrators to show or hide fields and sections on Lightning Record Pages based on defined criteria.
Component visibility is strictly a user-interface presentation layer feature.
2
Evaluate how data security is enforced in Salesforce.
Field-Level Security (FLS) on profiles or permission sets governs whether a user can read or edit a field across all access channels, including reports, list views, flows, and API integrations.
Hiding a field on a page layout or via Dynamic Forms does not remove FLS Read access.
3
Identify the cause of data exposure in reports and API.
Because the user still has Read access granted via Field-Level Security, the field remains accessible in tools outside the specific Lightning record page.
Proper data security requires restricting Field-Level Security directly on the Profile or via Permission Sets.

Key Concept

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

Helios Solar Solutions configured a Delegated Administration group allowing regional team leads to manage users within the 'EMEA Sales' role hierarchy. A delegated administrator needs to immediately prevent a departing sales representative from logging into Salesforce. However, attempting to deactivate the user fails because the account is currently designated as the default recipient in an active automated workflow alert. Which action should the delegated administrator take to immediately prevent system access while the system administrator updates the workflow configuration?

Show answer & explanation

Answer: Freeze the user account from the user detail page to prevent login access immediately without removing workflow references.

Answer

Freeze the user account to immediately block login access while leaving active workflow recipient references intact until a primary administrator can update the configuration.
Freezing a user account stops the user from logging in immediately while leaving the account active in the background. This allows delegated administrators to secure the organization when deactivation is temporarily blocked by active workflow dependencies or custom field references.

Step-by-Step Solution

1
Identify the administrative limitation preventing immediate user deactivation.
Deactivating a user who is tied to active custom field hierarchies, email alerts, or workflow actions triggers a system restriction error.
Salesforce enforces referential integrity so automated system processes do not fail upon referencing deactivated users.
2
Evaluate administrative capabilities available to Delegated Administrators.
Delegated administrators with user management rights can manage user details, reset passwords, assign specified profiles/permission sets, and freeze or unfreeze user accounts in their assigned roles.
Delegated administrators cannot modify profiles or clear workflow dependencies that require full system setup access.
3
Select the appropriate user management function to achieve immediate access restriction.
Freezing the user account disables login capability immediately without breaking automated workflow references.
Freezing stops access at the authentication level without altering underlying object relationships or automated rule configurations.

Key Concept

Delegated User Management and Freezing Users
Question 636Question

A Salesforce Administrator needs to aggregate financial metrics on a custom parent object, Hotel_Property__c, using values from child Guest_Reservation__c records. The requirement is to display the total revenue of completed stays directly on the Hotel_Property__c record.

Which two requirements or considerations apply when configuring a Roll-Up Summary field for this scenario?

Select all that apply

Show answer & explanation

Answer: A Master-Detail relationship must exist between Hotel_Property__c and Guest_Reservation__c, with Hotel_Property__c designated as the master object.; All Roll-Up Summary fields on Hotel_Property__c that reference Guest_Reservation__c must be deleted before converting the relationship from Master-Detail to Lookup.

Answer

The administrator must ensure a Master-Detail relationship exists with Hotel_Property__c as the master object, and must delete any existing Roll-Up Summary fields before converting the relationship to a Lookup relationship in the future.
Standard Roll-Up Summary fields are exclusively available on the master object of a Master-Detail relationship. Furthermore, Salesforce schema integrity rules mandate that any existing Roll-Up Summary fields referencing a detail object must be removed before converting that Master-Detail relationship into a Lookup relationship.

Step-by-Step Solution

1
Verify object relationship prerequisites for Roll-Up Summary fields.
Roll-Up Summary fields are native only to the master side of a Master-Detail relationship.
Standard declarative roll-up summaries require tight master-detail coupling to maintain data integrity.
2
Evaluate relationship conversion constraints and deletion behaviors.
Converting Master-Detail to Lookup requires deleting all Roll-Up Summary fields first; deleting a master record cascades deletion to all detail records.
Salesforce enforces schema integrity dependency rules during relationship conversions and deletions.

Key Concept

Roll-Up Summary Field Capabilities and Relationship Constraints
Question 637Question

An administrator created a new Record Type named 'Warranty Return' on the custom object Equipment_Return__c and assigned it to users with the Customer Support profile. However, support agents report two issues when working with 'Warranty Return' records: the 'Return Reason' picklist displays options that belong strictly to standard trade-ins, and the user interface displays fields and sections meant for hardware refurbishments. Which combination of administrative steps must be performed to resolve both issues?

Show answer & explanation

Answer: Edit the picklist availability settings under the 'Warranty Return' record type configuration to remove irrelevant values, and update the Page Layout Assignment matrix to assign the Warranty Return Page Layout to the Customer Support profile for that record type.

Answer

The administrator must edit the picklist availability settings under the 'Warranty Return' record type detail page to specify available picklist values, and update the Page Layout Assignment matrix to pair the Customer Support profile and 'Warranty Return' record type with the appropriate page layout.
To resolve both issues, the administrator must configure the two distinct settings that control picklist choice availability and visual field arrangement. Picklist values must be explicitly selected and edited under the specific Record Type detail settings in Object Manager. Simultaneously, the correct page layout must be mapped to the profile and record type combination using the Page Layout Assignment tool.

Step-by-Step Solution

1
Navigate to Object Manager > Equipment_Return__c > Record Types > Warranty Return.
Access the specific record type configuration page.
Picklist values must be filtered per record type to ensure only relevant values appear.
2
Edit the 'Return Reason' picklist field under the Record Type setup to remove trade-in values.
Only valid warranty return reasons remain selected for this record type.
Record types govern which picklist values are available when creating or editing records of that type.
3
Navigate to Object Manager > Equipment_Return__c > Page Layouts > Page Layout Assignment.
Open the assignment matrix mapping Profiles, Record Types, and Page Layouts.
Page layout assignment determines which layout users see based on their profile and the record's record type.
4
Assign the 'Warranty Return Page Layout' to the Customer Support profile for the 'Warranty Return' record type.
Support agents see the correct fields and sections when viewing or creating Warranty Return records.
Modifying the matrix ensures profile-specific and record-type-specific page display.

Key Concept

Page Layout and Record Type Assignment Matrix with Picklist Value Filtering
Question 638Question

Apex Medical Devices tracks field service activities using a custom object named Device_Maintenance_Log__c. The Organization-Wide Default (OWD) for this object is set to Private, and the Grant Access Using Hierarchies option has been deselected to prevent managers from automatically seeing draft logs created by technicians. Once a maintenance log status is set to 'Submitted', field service managers must be able to view and edit all submitted logs created by technicians within their branch. Which configuration should the administrator implement to meet this requirement?

Show answer & explanation

Answer: Create a criteria-based sharing rule on Device_Maintenance_Log__c that grants Read/Write access to the Field Service Managers role when the status equals 'Submitted'.

Answer

Create a criteria-based sharing rule on Device_Maintenance_Log__c that grants Read/Write access to the Field Service Managers role when the status equals 'Submitted'.
Creating a criteria-based sharing rule is the correct solution because it evaluates field values (Status = 'Submitted') and grants Read/Write record access specifically to the designated role (Field Service Managers). This leaves draft records private to technicians while fulfilling the requirement for submitted logs.

Step-by-Step Solution

1
Analyze the baseline security model and restrictions
The custom object has an OWD of Private and 'Grant Access Using Hierarchies' is unchecked, meaning no automatic upward role hierarchy access occurs.
When hierarchy access is disabled, implicit record access propagation up the role tree is turned off.
2
Evaluate the conditional sharing requirement
Managers need access only when record Status = 'Submitted'. Draft records must remain unshared.
Owner-based sharing rules share all records regardless of field values, whereas criteria-based sharing rules can evaluate field values like Status.
3
Select the appropriate sharing mechanism
Construct a criteria-based sharing rule matching Status = 'Submitted' that grants Read/Write access to the Field Service Managers role.
Criteria-based sharing rules selectively open up access to target roles/groups without altering object-level permissions or re-enabling broad hierarchy inheritance.

Key Concept

Criteria-Based Sharing Rules vs. Hierarchy Access
Estimated Time:1m 30s
Question 639Question

A Salesforce administrator at a global telecommunications enterprise configures Lead Custom Field Mapping to transfer data from a custom Lead picklist field, Service_Region__c, to a custom Account picklist field, Account_Region__c, upon lead conversion. During user acceptance testing, a sales representative converts a Lead into an Account assigned to a specific custom Record Type named 'Enterprise Account'. The conversion succeeds without throwing a platform error, but the Account_Region__c field on the resulting Account record is left blank, even though the Lead record had a valid value selected for Service_Region__c prior to conversion. Which of the following is the most likely cause of this issue?

Show answer & explanation

Answer: The picklist value selected on the Lead is not configured as an available value for the 'Enterprise Account' Account Record Type.

Answer

The picklist value selected on the Lead is not configured as an available value for the 'Enterprise Account' Account Record Type.
When converting a Lead into an Account, Contact, or Opportunity that uses Record Types, Salesforce validates mapped picklist values against the allowed picklist values for the target record's Record Type. If the value populated on the Lead is not selected as an active picklist value for the target Record Type (in this case, 'Enterprise Account'), Salesforce clears the field value on the newly created or updated record rather than throwing an explicit system exception.

Step-by-Step Solution

1
Analyze the lead conversion behavior and data outcome
Lead conversion completed without an error, but the custom mapped picklist field on the target Account record resulted in a blank value.
Understanding why the platform silently cleared the field value requires evaluating how Salesforce handles picklist value validation during record creation across Record Types.
2
Evaluate record type picklist assignment rules during lead conversion
Salesforce checks the available picklist values assigned to the target record's Record Type.
If a value passed from a source Lead picklist field is not enabled for the target Account Record Type, Salesforce automatically clears the field to prevent saving an invalid picklist value for that record type.
3
Identify the administrative resolution
Add the missing picklist value to the 'Enterprise Account' Record Type configuration for the Account_Region__c field.
Ensuring value alignment between Lead picklists and Account Record Type picklist definitions allows the mapped value to persist post-conversion.

Key Concept

Lead Conversion Field Mapping and Record Type Picklist Restrictions
Estimated Time:2m 0s
Question 640Question

A Salesforce Administrator at Quantum Logistics needs to make a newly launched subscription service available to sales teams using a custom EMEA Price Book. Place the required configuration and execution steps in the correct chronological sequence from start to finish.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence starts with creating and activating the Product record, followed by establishing an active Standard Price entry in the Standard Price Book. Next, the administrator creates and activates the EMEA Custom Price Book, then adds the product as an entry to the EMEA Custom Price Book with a custom list price. Finally, the EMEA Price Book is selected on an Opportunity to add the product as an Opportunity Line Item.
To enable product selection on opportunities using a custom price book, an administrator must follow Salesforce's required setup order: First, create and activate the Product record. Second, create an active Standard Price entry in the Standard Price Book. Third, create and activate the custom Price Book record. Fourth, add the Product to the custom Price Book with a custom list price entry. Fifth, select the custom Price Book on the Opportunity and add the Opportunity Line Item.

Step-by-Step Solution

1
Create and activate the master Product record.
Product is created in the organization's product catalog.
Price book entries cannot be created without an existing target Product record.
2
Add an active Standard Price entry in the Standard Price Book.
Standard price baseline is established for the product.
Salesforce enforces a business rule requiring an active standard price before custom price book entries can be created.
3
Create and activate the EMEA Custom Price Book.
Custom price book record becomes available for regional pricing.
Custom price book entries require an active custom price book container.
4
Add a Custom Price Book Entry linking the product to the EMEA Custom Price Book.
Product is assigned a list price within the EMEA Price Book.
Associates the specific currency and list price for the regional sales process.
5
Assign the EMEA Price Book to an Opportunity and add the product line item.
Opportunity Line Item is successfully added to the opportunity.
End-user opportunity management relies on all prerequisite product and price book configurations being complete and active.

Key Concept

Prerequisite setup hierarchy for Products, Standard Price Books, Custom Price Books, and Opportunity Line Items.
Estimated Time:2m 0s
PreviousPage 32 / 90Next
All practice questions — Salesforce Certified Administrator | Examkin