All practice questions

1784 questions

Question 721Question

An administrator is configuring a new Record Type called 'Specialized Partner Sales' on the Opportunity object to support a new business unit. Which two administrative actions must be completed so that users assigned to this Record Type see the correct page view and valid picklist selections? (Select 2 answers)

Select all that apply

Show answer & explanation

Answer: Assign the appropriate Page Layout for the new Record Type to the relevant user Profiles.; Edit the available picklist values specific to the new Record Type under Object Manager.

Answer

The administrator must assign the appropriate Page Layout to the target Profiles for the new Record Type and edit the available picklist values for that Record Type under Object Manager.
Configuring a new Record Type requires two key administration steps: setting the Page Layout assignment matrix for each profile and defining which picklist values are available for that specific Record Type.

Step-by-Step Solution

1
Map Page Layouts to Profiles
Ensure users with the designated profile see the correct fields and sections when working with records of this Record Type.
Page layout assignment matrix maps Profile + Record Type to a specific Page Layout.
2
Configure Record Type Picklist Values
Specify which picklist choices are selectable for opportunities using this Record Type.
Each Record Type can display a tailored subset of picklist values from object fields.

Key Concept

Page Layout and Record Type Assignment
Question 722Question

Meridian Global Logistics utilizes a custom object named Supplier_Contract__c with an Organization-Wide Default (OWD) set to Private. To prevent executive roles from automatically gaining access to sensitive operational records, the System Administrator deselects the 'Grant Access Using Hierarchies' option on Supplier_Contract__c. However, Regional Directors still require Read/Write access to Supplier_Contract__c records owned by Procurement Specialists who occupy roles below them. Which configuration should the administrator implement to meet this requirement?

Show answer & explanation

Answer: Create an owner-based sharing rule that shares Supplier_Contract__c records owned by the Procurement Specialist role with the Regional Director role.

Answer

Create an owner-based sharing rule that shares Supplier_Contract__c records owned by the Procurement Specialist role with the Regional Director role.
Creating an owner-based sharing rule specifically grants Read/Write access for records owned by the Procurement Specialist role to users in the Regional Director role. This satisfies the business requirement without re-enabling automatic hierarchy access or over-granting organization-wide record permissions through permission sets.

Step-by-Step Solution

1
Evaluate the current Organization-Wide Default (OWD) and hierarchy access settings.
The OWD is set to Private and 'Grant Access Using Hierarchies' is disabled on the custom object Supplier_Contract__c, meaning role hierarchy access propagation is turned off.
Disabling hierarchy access prevents roles higher up in the hierarchy from automatically inheriting record access from subordinate roles.
2
Identify the proper security mechanism to selectively open up record access.
An owner-based sharing rule can target records owned by users in the Procurement Specialist role and grant Read/Write access to the Regional Director role.
Sharing rules operate independently of the 'Grant Access Using Hierarchies' setting on custom objects, allowing targeted access without exposing records to top-level executives.

Key Concept

Disabling 'Grant Access Using Hierarchies' on custom objects stops automatic access rollout up the role hierarchy, but sharing rules can still explicitly share records between specific roles or groups.
Estimated Time:1m 30s
Question 723Question

An administrator at Pulse Health Systems is setting up a new medical software offering named 'CareSync Portal'. The sales team needs to add this product to opportunities using a custom price book named 'Enterprise Healthcare Pricing'. Which two actions must the administrator perform to make 'CareSync Portal' selectable in the custom price book?

Select all that apply

Show answer & explanation

Answer: Create an active standard price entry for the product in the Standard Price Book.; Add an active price entry for the product to the Enterprise Healthcare Pricing custom price book.

Answer

The administrator must create an active standard price entry in the Standard Price Book and add an active price entry for the product to the Enterprise Healthcare Pricing custom price book.
To make a product available on opportunities associated with a custom price book, an administrator must complete two main steps: first, create an active price entry for the product in the Standard Price Book (which serves as the architectural foundation), and second, create an active price entry for the product within the designated custom price book.

Step-by-Step Solution

1
Ensure the product record is active and create a standard price entry in the Standard Price Book.
Establishes the base standard price prerequisite required by Salesforce.
Custom price books cannot reference a product unless it has an active price in the Standard Price Book.
2
Add a new price book entry to the 'Enterprise Healthcare Pricing' custom price book for 'CareSync Portal' and mark it active.
Associates the product with the negotiated price for users assigned to that custom price book.
Opportunity line items can only draw from products that have active entries in the price book selected for that opportunity.

Key Concept

Standard Price Book Entry Prerequisite for Custom Price Books
Question 724Question

A Salesforce administrator needs to configure Lightning App Builder pages and component visibility for a custom object named Maintenance_Ticket__c. The business requires that a specialized component appears on the record page only when a ticket's status is set to 'In Progress' and the user is viewing the record within the Service Console app. Additionally, different customized record pages must be displayed to users based on their specific profile and the ticket record type. Which two administrative actions accurately fulfill these requirements using Lightning App Builder? (Select 2 choices)

Select all that apply

Show answer & explanation

Answer: Add component visibility filters based on the Status field value and the User Client/App context.; Activate the custom record page by assigning it at the App, Record Type, and Profile granular level.

Answer

The administrator should add component visibility filters based on record fields and User/App context, and activate the custom record page using the App, Record Type, and Profile assignment combination.
The correct statements are configuring component visibility filters using record fields and client context, and activating the record page at the App, Record Type, and Profile level. Component visibility rules support checking both record field values and current app context. App, Record Type, and Profile activation is the required mechanism when record pages must vary across specific business roles and record types within a given app.

Step-by-Step Solution

1
Analyze component visibility criteria
Dynamic component visibility in Lightning App Builder can filter component display based on Record Fields (Status = 'In Progress') and User/Client context (App = Service Console).
This allows conditional component rendering without requiring custom code.
2
Determine page activation precedence
To override record pages for specific profiles, applications, and record types, the administrator must choose the 'App, Record Type, and Profile' activation level.
This activation assignment offers the highest specificity for Lightning Record Page display.

Key Concept

Lightning App Builder Activation Assignments & Component Visibility
Question 725Question

An administrator at a commercial real estate firm is configuring a new custom object named Property_Inspection__c to track physical site audits linked to Account records. Which two statements are true regarding the standard features and limitations of custom objects? (Select 2)

Select all that apply

Show answer & explanation

Answer: Salesforce automatically creates standard system fields on the custom object, including Name, Created By, Last Modified By, and Owner.; Deleting the Property_Inspection__c custom object soft-deletes it for 15 days, during which the object, its data, and its relationships can be restored.

Answer

The correct statements are that Salesforce automatically provisions standard system fields (such as Name, Created By, Last Modified By, and Owner) upon custom object creation, and deleting a custom object places it into a soft-delete state for 15 days during which it can be restored.
Salesforce automatically includes core standard fields (Name, Created By, Last Modified By, Owner, Id) whenever a new custom object is created. Additionally, custom objects that are deleted enter a 15-day soft-delete grace period where they can be restored along with their fields, data, and relationship definitions.

Step-by-Step Solution

1
Analyze standard field provisions for custom objects
Confirm that Name, Created By, Last Modified By, Owner, and Record ID are automatically generated standard fields.
Salesforce requires built-in system metadata and ownership fields on all custom objects.
2
Evaluate object deletion lifecycle
Confirm that custom object deletion initiates a 15-day soft-deletion retention period.
Administrators have a 15-day grace period to undelete custom objects before permanent purge.
3
Evaluate relationship type constraints
Identify that Roll-up Summary fields cannot target Lookup relationships, and standard objects cannot be child/detail objects in Master-Detail relationships.
Salesforce architecture mandates Master-Detail relationships for native Roll-Up Summaries and prohibits standard objects from being child records in Master-Detail structures.

Key Concept

Standard and Custom Object Management
Estimated Time:1m 30s
Question 726Question

A Salesforce Administrator at a non-profit organization is setting up custom objects to track funding grants using a parent object named Grant__c and a child object named Grant_Payment__c. The two objects are currently connected using a Lookup relationship. The administrator needs to calculate and display the total sum of all payment amounts directly on each Grant__c record, but finds that the Roll-Up Summary field type option is disabled when creating a new field on Grant__c. Which configuration change will allow the administrator to create the required summary field?

Show answer & explanation

Answer: Convert the Lookup relationship field on Grant_Payment__c to a Master-Detail relationship.

Answer

Convert the Lookup relationship field on Grant_Payment__c to a Master-Detail relationship.
In Salesforce, native Roll-Up Summary fields are exclusively supported on the master object of a Master-Detail relationship. Converting the existing Lookup relationship on the child object (Grant_Payment__c) to a Master-Detail relationship fulfills this requirement, allowing the administrator to create a Roll-Up Summary field using the SUM function on the parent object (Grant__c).

Step-by-Step Solution

1
Identify relationship requirements for Roll-Up Summary fields
Native Roll-Up Summary fields can only be created on the master object in a Master-Detail relationship.
Salesforce platform declarative roll-up engine requires the tight data coupling and cascading data control provided by Master-Detail relationships.
2
Evaluate the current object relationship
The Grant__c and Grant_Payment__c objects are linked via a Lookup relationship, which prevents Roll-Up Summary field creation.
Lookup relationships maintain independent lifecycle management and do not support native Roll-Up Summary field functionality.
3
Determine the necessary conversion step
Converting the existing Lookup relationship field on Grant_Payment__c to a Master-Detail relationship enables the Roll-Up Summary field type on Grant__c.
Ensure all child Grant_Payment__c records have a populated parent lookup value prior to conversion so the field type can be converted successfully.

Key Concept

Roll-Up Summary Field Relationship Requirements
Question 727Question

A Salesforce administrator is documenting the standard lead conversion process for newly onboarded sales representatives. What is the correct chronological sequence of steps that occur when converting a qualified lead record in Salesforce?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence begins when the user clicks the Convert button, continues with specifying or creating target Account, Contact, and Opportunity records, executes standard and custom field mapping, and concludes by setting the Lead status to Converted and locking the record.
The lead conversion process starts when a user clicks the Convert button on a Lead. Next, the user configures destination records by choosing to create new or select existing Account, Contact, and Opportunity records. Salesforce then transfers Lead data to these records using standard and custom field mappings. Finally, Salesforce updates the Lead status to Converted and locks the original Lead record as read-only.

Step-by-Step Solution

1
Initiate conversion
The user triggers the Convert action on the Lead record.
The conversion workflow is started by the user action on the lead record interface.
2
Define target objects
The user chooses existing target records or opts to create new Account, Contact, and Opportunity records.
Target destination objects must be determined so data can be routed properly.
3
Execute data mapping
Lead fields map to their corresponding Account, Contact, and Opportunity target fields.
Data transfer occurs during object creation/update execution.
4
Lock lead record
The Lead record is updated to Converted status and becomes read-only.
Successful completion updates the lead lifecycle status to preserve historical reporting integrity.

Key Concept

Standard Salesforce Lead Conversion Execution Order
Estimated Time:45s
Question 728Question

Northern Ridge University uses a custom object named Scholarship Application. All 17 team members in the admissions department are assigned the custom profile Admissions Counselor, which provides Read, Create, and Edit permissions on the object. The university requires that a sensitive custom field, Financial_Audit_Notes__c, be completely hidden from 15 general counselors, but remain fully viewable and editable by 2 senior compliance officers. Which configuration should the Salesforce Administrator implement to meet this requirement following security best practices?

Show answer & explanation

Answer: Restrict Field-Level Security for Financial_Audit_Notes__c on the Admissions Counselor profile to Visible = False, create a permission set granting Read and Edit access to the field, and assign it to the two senior compliance officers.

Answer

Restrict Field-Level Security for Financial_Audit_Notes__c on the Admissions Counselor profile to Visible = False, create a permission set granting Read and Edit access to the field, and assign it to the two senior compliance officers.
Field-Level Security (FLS) controls data visibility at the platform level, ensuring that users without access cannot view or edit the field in the UI, reports, or APIs. Setting FLS to hidden on the profile establishes the secure baseline, and creating a permission set allows the administrator to additively grant access to the two senior compliance officers without creating redundant profiles.

Step-by-Step Solution

1
Set base field access via Field-Level Security
Field-Level Security (FLS) for Financial_Audit_Notes__c on the Admissions Counselor profile is modified so both Visible and Read-Only checkboxes are cleared.
This establishes a baseline where all users assigned to the Admissions Counselor profile cannot read or edit the field.
2
Create a custom Permission Set
A new Permission Set is created with Read and Edit access enabled for Financial_Audit_Notes__c.
Permission sets are designed to grant additive permissions to specific users without altering their underlying profile.
3
Assign the Permission Set to targeted users
The Permission Set is assigned specifically to the two senior compliance officers.
This ensures only the required individuals gain field access while maintaining least-privilege security for the rest of the team.

Key Concept

Field-Level Security and Permission Sets
Question 729Question

A sales administrator at Astra Freight Logistics is creating a custom price book named 'EMEA Enterprise' for a newly created freight auditing service. When attempting to add the service product to the 'EMEA Enterprise' custom price book, the product does not appear in the selection list. What is the most likely cause of this issue?

Show answer & explanation

Answer: The product does not have an active price entry defined in the Standard Price Book.

Answer

The product does not have an active price entry defined in the Standard Price Book.
Before a product can be added to any custom price book in Salesforce, it must first be added to the Standard Price Book with an active standard price. Without an active standard price entry, the product will not be selectable when adding price book entries to a custom price book.

Step-by-Step Solution

1
Identify the relationship between products, standard price books, and custom price books.
Realize that standard price entries serve as the prerequisite pricing foundation in Salesforce.
Salesforce enforces that every product must have an active standard price entry before it can be assigned to custom price books.
2
Determine why the product is missing from the custom price book selection screen.
The administrator omitted adding the product to the Standard Price Book first.
Without an active standard price book entry, Salesforce hides the product from custom price book entry selection lists.

Key Concept

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

Universal Containers wants to set up a new Case Record Type specifically for handling customer warranty claims. The administrator needs to restrict and customize the available Case Status picklist values for this record type. What must the administrator create first before configuring the custom Case Status values for the new Case Record Type?

Show answer & explanation

Answer: A Support Process containing the required subset of Case Status values

Answer

A Support Process containing the required subset of Case Status values must be created first before it can be linked to a Case Record Type.
A Support Process must be created first because Case Status picklist values are governed by Support Processes in Salesforce. Once a Support Process defines the appropriate lifecycle stages, it is selected during Case Record Type creation to enforce those specific status values.

Step-by-Step Solution

1
Identify the prerequisite dependency for Case Status picklist customization.
Recognize that Case Status picklist values are controlled by Support Processes in Salesforce.
Unlike standard custom picklists, Case Status is tied to business processes and lifecycle stages.
2
Create a new Support Process.
Select and save the specific subset of Case Status values needed for warranty claims.
The Support Process acts as the master list of available status values for cases using that lifecycle.
3
Associate the Support Process with the new Case Record Type.
The new Case Record Type displays only the selected Case Status picklist values.
A Case Record Type requires an associated Support Process to determine which Case Status choices are presented to users.

Key Concept

Support Process and Case Record Type Dependency
Estimated Time:1m 0s
Question 731Question

An administrator is configuring Campaign Management to track marketing performance for a company. The marketing team requires accurate reporting on campaign member engagement, custom member statuses, and historical campaign involvement when leads progress through the sales pipeline. Which two statements describe correct system behaviors and administrative considerations for Campaign Members? (Select 2 answers)

Select all that apply

Show answer & explanation

Answer: When a Lead is converted, existing Campaign Member records linked to that Lead are automatically updated to relate to the newly created Contact.; Setting the 'Responded' checkbox on a custom Campaign Member Status includes members assigned that status in the Campaign's summary metrics for responses.

Answer

The two correct statements are that converting a Lead automatically updates associated Campaign Member records to relate to the newly created Contact, and flagging a custom Campaign Member Status as 'Responded' counts those members in campaign response summary metrics.
When a Lead converts, Salesforce maintains full campaign history by re-linking the Lead's existing Campaign Member records to the newly created Contact. Additionally, selecting the 'Responded' checkbox on a Campaign Member Status configuration ensures members holding that status are included in campaign response totals.

Step-by-Step Solution

1
Evaluate campaign member status behavior in campaign hierarchies and reporting
Campaign member statuses are configured per campaign and do not retroactively propagate down existing campaign hierarchies. Enabling the 'Responded' setting on a status controls whether assigned members contribute to campaign response totals.
Salesforce calculates campaign response totals specifically by evaluating the 'Responded' flag attached to each campaign member status.
2
Evaluate Lead conversion mechanics concerning Campaign Members and custom field mapping
Campaign Member records automatically transfer relationship pointers from the Lead to the new Contact upon conversion to preserve engagement history. Custom field mapping setup applies to Lead fields, not Campaign Member fields.
Lead conversion field mapping rules link Lead object fields to target Account, Contact, and Opportunity fields.

Key Concept

Campaign Member behavior during Lead conversion and Campaign Member Status configuration
Question 732Question

A system administrator is provisioning access for a new cohort of remote customer service representatives. Security policy requires that these users be strictly blocked from logging into Salesforce whenever they are outside the corporate VPN IP address range. If a representative attempts to log in from an unapproved IP address, access must be completely denied rather than prompting for identity verification. Which setting should the administrator configure to enforce this requirement?

Show answer & explanation

Answer: Add the corporate VPN IP address range to the Login IP Ranges section of the custom profile assigned to the representatives.

Answer

Add the corporate VPN IP address range to the Login IP Ranges section of the custom profile assigned to the representatives.
Specifying IP ranges within the Login IP Ranges section of a user's Profile enforces strict location-based access control. Any authentication attempt originating outside these defined profile IP boundaries is restricted and denied immediately.

Step-by-Step Solution

1
Identify the authentication security requirement
The requirement demands immediate denial of login outside specified IP ranges rather than identity verification prompts.
Salesforce evaluates profile-level Login IP Ranges strictly by blocking authentication attempts outside the defined range.
2
Compare Profile Login IP Ranges with Org-Wide Network Access
Profile IP Ranges restrict and deny access outside the range, whereas Org-Wide Network Access merely establishes trusted IPs to skip MFA/device verification.
Configuring profile-level Login IP Ranges fulfills the strict security blocking requirement.

Key Concept

Profile Login IP Ranges enforcement vs. Organization-Wide Network Access trusted IPs
Question 733Question

A Salesforce Administrator at AeroSpire Aviation Technologies is configuring a newly created product named 'AvioTrack Pro' to be sold under a specialized custom price book called 'Government Defense Contracts'. The administrator successfully creates the product record and marks it as active. However, when attempting to add 'AvioTrack Pro' to the 'Government Defense Contracts' price book, the system throws an error and prevents the entry creation. Which prerequisite configuration step was omitted?

Show answer & explanation

Answer: An active price entry for the product must first be created in the Standard Price Book before it can be added to any custom price book.

Answer

An active price entry for the product must first be created in the Standard Price Book before it can be added to any custom price book.
In Salesforce, the Standard Price Book acts as the master pricing repository. Before a product can be added to any custom price book (such as a regional or segment-specific price book), an active price entry for that product must exist in the Standard Price Book. Once the standard price entry is created and active, administrators can add the product to any custom price books with custom list prices.

Step-by-Step Solution

1
Analyze the pricing architecture requirements for Salesforce Products and Price Books.
Identified that products must establish a baseline standard price entry.
Salesforce enforces object dependency where custom price books reference the Standard Price Book as the baseline.
2
Evaluate the error context during product assignment to a custom price book.
The product has been marked active, but lacks a standard price book entry.
Without an active entry in the Standard Price Book, custom price book entries for that product cannot be created.
3
Determine the necessary administrative resolution step.
Add an active Standard Price to the product record in the Standard Price Book.
This fulfills the database prerequisite and allows subsequent custom price book entry creation.

Key Concept

Standard Price Book Entry Prerequisite
Question 734Question

A Salesforce Administrator at Astraea Biopharma is setting up a new line of specialized laboratory reagents. The administrator creates active Product records for each reagent and builds a custom price book named "EMEA Enterprise Rates". However, when sales representatives attempt to add these new products to an opportunity using the "EMEA Enterprise Rates" price book, the products are unavailable for selection. Which two configuration steps must the administrator complete to allow sales reps to select and add these products to opportunities using the custom price book? (Select 2)

Select all that apply

Show answer & explanation

Answer: Create an active price entry for each product in the Standard Price Book.; Ensure the "EMEA Enterprise Rates" custom price book is marked as Active.

Answer

The administrator must create an active standard price entry for each product in the Standard Price Book and ensure the custom price book status is set to Active.
To make products available for selection on opportunities via a custom price book, two critical prerequisites must be met: first, each product must have an active standard price entry in the Standard Price Book; second, the custom price book itself must be set to Active. Without an active standard price entry, Salesforce prevents adding the product to any custom price book. Without an active custom price book, sales reps cannot select the price book on opportunities.

Step-by-Step Solution

1
Verify prerequisite requirements for custom price book entries.
Identified that Salesforce requires a product to exist as an active entry in the Standard Price Book before it can be assigned to any custom price book.
Standard price entries serve as the baseline pricing architecture for products across all sales channels.
2
Verify the operational state of the custom price book.
Identified that custom price books must explicitly have their 'Active' checkbox selected.
Inactive price books are hidden from end users when picking price books on opportunities.
3
Evaluate and eliminate incorrect configuration options.
Rule out lead conversion field mapping and sales process stage assignments as unrelated administrative functions.
Field mapping applies strictly to lead conversion, while sales processes govern stage lifecycle picklists.

Key Concept

Standard price book entry prerequisites and custom price book activation rules
Question 735Question

A Salesforce administrator at a heavy equipment rental enterprise is setting up Lead Custom Field Mapping to support lead conversion. The sales operations team specifies that a custom picklist field on the Lead object named 'Equipment Class' must populate a custom field on the target Account record upon conversion. However, when configuring the field mapping under Lead Settings, the administrator observes that the desired custom Account field is missing from the target picklist field dropdown menu. What is the root cause preventing the Account field from appearing as a mapping target?

Show answer & explanation

Answer: The target custom field on the Account object was created as a Text data type instead of a Picklist data type.

Answer

The target custom field on the Account object was created as a Text data type instead of a Picklist data type.
In Salesforce Lead Custom Field Mapping, custom fields on the Lead object can only be mapped to custom fields on the target Account, Contact, or Opportunity objects if their data types match. Specifically, a custom Picklist field on the Lead object must be mapped to a custom Picklist field on the target object. If the target Account field was defined as a Text data type, Salesforce automatically excludes it from the selection list for the Lead Picklist field.

Step-by-Step Solution

1
Analyze Lead Custom Field Mapping data type compatibility requirements in Salesforce.
Salesforce mandates that custom fields mapped from the Lead object to Account, Contact, or Opportunity objects must share the exact same data type (or compatible length for text fields).
Data type mismatches prevent target fields from showing up in the mapping setup interface.
2
Evaluate the data type of the source field on the Lead object.
The source field 'Equipment Class' is a Picklist field.
Source picklist fields require target fields on Account, Contact, or Opportunity to also be Picklist data types.
3
Identify why the target Account field is omitted from the administrative drop-down list.
If the custom Account field was configured as a Text field rather than a Picklist field, Salesforce filters it out of the available target choices.
Converting a picklist into a text field directly via mapping is unsupported in standard Lead field mapping.

Key Concept

Lead Custom Field Mapping Data Type Restrictions
Estimated Time:2m 0s
Question 736Question

A sales representative at an industrial equipment manufacturer has finished qualifying a prospect and needs to convert the Lead record. Place the standard steps of the Salesforce Lead conversion wizard process in the correct chronological order from start to finish.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct chronological order for converting a Lead is: 1) Navigate to the qualified Lead record and click the Convert button, 2) Select an existing Account or create a new Account record, and verify Contact details, 3) Specify Opportunity details or check the box to convert without creating a new Opportunity, and 4) Click the Convert button in the modal to complete record creation and set the Lead status to Converted.
The standard Salesforce lead conversion process flows logically from launching the wizard on the Lead record, selecting or creating the Account and Contact, specifying whether to create an Opportunity, and finally submitting the conversion modal to commit record changes and mark the Lead status as Converted.

Step-by-Step Solution

1
Initiate conversion from the Lead record
The Lead conversion wizard modal opens
The Convert action must be launched from the detail page of the active Lead.
2
Configure target Account and Contact records
Account and Contact destination targets are established
Salesforce requires associating the converted lead data with an Account and Contact record before proceeding.
3
Configure Opportunity creation preferences
Opportunity creation settings are populated or suppressed
Users must decide whether an Opportunity is appropriate for this qualified lead prior to final execution.
4
Execute conversion submit action
Account, Contact, and optional Opportunity records are created/updated and the Lead is marked Converted
Submitting the modal triggers Salesforce system execution of field mapping, record creation, and status updates.

Key Concept

Standard Lead Conversion Workflow Sequence
Estimated Time:1m 30s
Question 737Question

A System Administrator needs to provide sales reps with a way to quickly create a related Contact record directly from an Account record page in Lightning Experience. The action must automatically set the Account Name and Billing Address on the new Contact record. Which feature should the administrator configure to meet this requirement?

Show answer & explanation

Answer: An Object-Specific Quick Action on the Account object with Predefined Field Values

Answer

An Object-Specific Quick Action on the Account object with Predefined Field Values is the correct tool because it operates within the context of the host Account record to create related records and pre-populate field data.
An Object-Specific Quick Action on the Account object allows administrators to create related Contact records while automatically populating target fields using Predefined Field Values derived from the host Account record.

Step-by-Step Solution

1
Analyze the business requirement for record context and automation.
The requirement asks to create a child Contact record directly from a parent Account record page while inheriting parent field values.
Object-specific actions are bound to the host object, providing access to host record fields.
2
Select the appropriate action type and field configuration.
Create an object-specific Quick Action of type 'Create a Record' on the Account object, selecting Contact as the target object, and configure Predefined Field Values for the new record.
Predefined Field Values automatically populate fields on the target record upon action invocation.

Key Concept

Object-Specific Quick Actions and Predefined Field Values
Question 738Question

An administrator at a global media distribution company needs to create a custom data model to link Media Content (Media_Content__c) records with Distribution Territory (Distribution_Territory__c) records. Each media content item can be released in multiple territories, and each territory can host multiple content items. The requirements specify that deleting a media content item or a territory record must automatically delete its corresponding relationship records. Additionally, executives want to view a real-time total count of associated territories directly on each Media Content record. Which two configuration steps should the administrator take to fulfill these requirements? Choose 2 answers.

Select all that apply

Show answer & explanation

Answer: Create a custom junction object that includes a Master-Detail relationship field to Media Content and a Master-Detail relationship field to Distribution Territory.; Create a Roll-Up Summary field of type COUNT on the Media Content object referencing the junction object records.

Answer

The administrator should create a custom junction object with two Master-Detail relationship fields pointing to Media Content and Distribution Territory, and create a Roll-Up Summary field of type COUNT on the Media Content object referencing the junction object.
To fulfill a many-to-many requirement with cascading deletion behavior, an administrator must construct a junction object linked by two Master-Detail relationships. Because the Media Content object acts as a master in one of these Master-Detail relationships, the administrator can build a Roll-Up Summary field of type COUNT on Media Content to calculate the total number of associated records.

Step-by-Step Solution

1
Analyze the relationship structure requirements.
Since both entities require a multi-directional link (many-to-many), a custom junction object is required.
Salesforce achieves many-to-many relationships using a junction object situated between two master objects.
2
Evaluate deletion cascade and security inheritance rules.
Select Master-Detail relationships for both sides of the junction object.
Master-Detail relationships ensure that deleting either parent record automatically cascade-deletes the junction record.
3
Determine how to calculate the total count of related territories on Media Content.
Create a Roll-Up Summary field with the COUNT aggregate function on the Media Content master object.
Roll-Up Summary fields are only natively supported on the parent/master side of a Master-Detail relationship.

Key Concept

Many-to-Many Relationships and Roll-Up Summary Requirements
Question 739Question

A Salesforce administrator recently configured a new Record Type for high-priority Tier 3 support cases on the Case object. However, support agents assigned to this record type report that an obsolete picklist value still appears in the Case Reason drop-down menu when creating new cases. Which configuration action should the administrator take to remove this specific picklist value for Tier 3 cases without affecting other record types?

Show answer & explanation

Answer: Edit the available picklist values directly within the Tier 3 Case Record Type setup.

Answer

Edit the available picklist values directly within the Tier 3 Case Record Type setup.
Configuring picklist values within the specific Record Type settings under Object Manager allows administrators to customize which picklist values are available to users for that exact record type without modifying master field definitions or affecting other record types.

Step-by-Step Solution

1
Navigate to Object Manager and select the Case object.
Accesses the object-level settings for Cases.
Record types and picklist settings are configured at the object level.
2
Select Record Types and open the Tier 3 Case record type configuration.
Displays the picklists available for editing for this specific record type.
Each record type maintains its own independent list of enabled picklist values for standard and custom picklist fields.
3
Edit the Case Reason picklist field for this record type and move the obsolete value to the unselected values list.
Removes the obsolete picklist value exclusively from the Tier 3 Case record type.
This updates the available choices for users creating records under this specific record type without impacting other record types or global field definitions.

Key Concept

Record Type Picklist Value Assignment
Question 740Question

An administrator at Cloud Kicks needs to enable a sales representative to grant a technical specialist Read/Write access to a specific opportunity record they are collaborating on. The organization-wide default sharing setting for Opportunities is set to Private. Which feature should the administrator configure to meet this requirement?

Show answer & explanation

Answer: Opportunity Teams

Answer

Opportunity Teams enable sales reps to add team members to specific opportunity records and assign them Read Only or Read/Write access to collaborate on the deal.
Opportunity Teams allow opportunity owners or administrators to add team members to an opportunity and define their record-level access (Read Only or Read/Write), facilitating collaboration on a specific deal without altering organization-wide defaults or assigning broad object permissions.

Step-by-Step Solution

1
Analyze the sharing requirement
The requirement calls for ad-hoc, record-level sharing of a specific opportunity while keeping the baseline OWD Private.
Global access expansion must be avoided.
2
Evaluate record collaboration features
Opportunity Teams allow opportunity owners to grant specific users access to individual opportunities based on assigned team roles.
Opportunity Teams are designed specifically for team selling scenarios on single opportunity records.

Key Concept

Opportunity Teams and Team Selling Access
Estimated Time:45s
PreviousPage 37 / 90Next
All practice questions — Salesforce Certified Administrator | Examkin