All practice questions

1784 questions

Question 781Question

A Salesforce Administrator at Cloud Real Estate Services needs to implement appropriate security and visibility controls for various business requirements. Match each business requirement to the correct Salesforce security or configuration feature.

Click a left item, then click its matching right item

Items

Restrict login access for all users assigned to the Customer Support Profile so they can only log in from specific corporate network IP ranges.
Dynamically hide a custom field on a Contact record page based on record status without modifying underlying access permissions.
Grant read and edit access for a sensitive custom field to 3 specific users across different profiles without altering their base profiles.
Prevent all users assigned to the Sales Representative profile from deleting Account records while allowing them to create and edit Accounts.

Matches

Show answer & explanation

Answer

Each business security requirement maps to its optimal Salesforce feature: restricting profile login locations maps to Profile Login IP Ranges; conditionally hiding fields on record pages without altering access maps to Dynamic Forms Component Visibility; granting selective field access across profiles maps to Permission Sets with FLS; and restricting object-level delete rights for a profile maps to Profile Object Permissions.
The solution accurately pairs each requirement with the correct Salesforce feature by distinguishing between network login restrictions (Profile Login IP Ranges), dynamic UI rendering (Dynamic Forms), additive user-specific field access (Permission Sets), and baseline object CRUD privileges (Profile Object Permissions).

Step-by-Step Solution

1
Identify the mechanism for profile-specific IP login enforcement.
Profile Login IP Ranges strictly enforce login boundaries per profile.
Profile Login IP Ranges block login requests originating outside the configured IP ranges for users on that profile.
2
Identify the mechanism for dynamic page layout visibility.
Dynamic Forms Component Visibility rules dynamically display or hide fields based on record field values.
Dynamic Forms manage user interface presentation rules dynamically without modifying global security controls.
3
Identify the mechanism for extending field-level access to selected individuals.
A Permission Set with Field-Level Security grants additive read/edit access to targeted users.
Permission sets allow administrators to grant extra field permissions selectively without profile proliferation.
4
Identify the mechanism for object-level operation controls.
Profile Object Permissions configure standard Create, Read, Edit, and Delete access at the object level.
Removing Delete permission from the profile object settings prevents all users with that profile from deleting records of that object.

Key Concept

Configuring security layers (Profile Object Permissions, Field-Level Security, Login IP Restrictions) vs. UI presentation tools (Dynamic Forms).
Question 782Question

Universal Containers built a customized Lightning Home page designed to display real-time service metrics specifically for customer support agents. The support executive requests that this tailored Home page appear only when support agents log into the Service Console application. Sales representatives using the exact same Service Console application must continue viewing their existing sales-focused Home page.

How should the administrator assign this new Lightning Home page to fulfill the requirement?

Show answer & explanation

Answer: Activate the page and assign it to the Service Console app, selecting only the Customer Support user profile.

Answer

Activate the page and assign it to the Service Console app, selecting only the Customer Support user profile.
Lightning App Builder Home pages support three activation assignment options: Org Default, App Default, and App and Profile assignments. When different user groups (profiles) working in the same Lightning App require distinct Home page experiences, the administrator must activate the page for that specific App and select the designated user Profile(s).

Step-by-Step Solution

1
Identify the type of Lightning page being assigned
The requirement specifies a Home page layout for a targeted group of users.
Home pages support three activation levels: Org Default, App Default, and App & Profile combination.
2
Evaluate the business constraint
Support agents and sales reps share the same app (Service Console), but need different Home pages.
Because users in the same app require different views, App Default is insufficient; an App & Profile assignment is required.
3
Select the correct activation scope
Assigning the Home page to the Service Console app for the Customer Support profile fulfills the exact requirement.
This leaves the existing Home page active for other profiles (such as Sales) operating within the same Service Console app.

Key Concept

Lightning Home Page Activation Precedence (App and Profile Assignment)
Question 783Question

A Salesforce administrator at a specialized medical equipment supply enterprise is setting up Lead Custom Field Mapping for sales operations. The team requires a custom picklist field on the Lead object named "Procurement Model" to automatically populate a corresponding field on the Account record whenever a lead is converted. While attempting to map the fields in Setup, the administrator finds that the target custom field on the Account object is missing from the mapping dropdown menu for the "Procurement Model" field.

Which configuration mismatch is preventing the custom Account field from appearing in the lead field mapping selection?

Show answer & explanation

Answer: The custom field created on the Account object has a Text data type rather than a Picklist data type.

Answer

The custom field created on the Account object has a Text data type rather than a Picklist data type.
In Salesforce Lead Custom Field Mapping, source custom fields on the Lead object can only be mapped to custom target fields on the Account, Contact, or Opportunity objects that share identical or compatible data types. Because the source field on the Lead is a picklist, the target Account field must also be created as a picklist. If the Account field was created with a different data type (such as Text), Salesforce will exclude it from the mapping dropdown menu for that picklist field.

Step-by-Step Solution

1
Identify the requirement for Lead Custom Field Mapping.
The requirement is to map a custom Lead picklist field ("Procurement Model") to a custom field on the Account object.
Lead conversion transfers qualified prospect data from Lead records to target Account, Contact, and Opportunity records.
2
Evaluate Salesforce platform rules for custom lead field mapping.
Salesforce mandates strict data type compatibility; custom Lead picklist fields can only map to custom Picklist fields on target objects.
Mismatched data types prevent the target field from appearing in the mapping selection dropdown list in Setup.
3
Determine the root cause of the missing target field.
Defining the target Account field as a Text data type instead of a Picklist data type causes Salesforce to hide it from the picklist mapping menu.
Correcting the Account field to a Picklist data type resolves the mismatch and allows successful mapping configuration.

Key Concept

Lead Custom Field Mapping Data Type Compatibility
Estimated Time:1m 30s
Question 784Question

A Salesforce administrator at an educational publishing company configures a Master-Detail relationship where the standard Account object serves as the master and a new custom object named Course_Offering__c serves as the detail. Which TWO statements accurately describe the security and data management capabilities resulting from this setup? (Select 2)

Select all that apply

Show answer & explanation

Answer: Roll-up summary fields can be created on the Account object to calculate aggregate counts and values from related Course_Offering__c records.; Deleting an Account record automatically deletes all associated Course_Offering__c child records in a cascade deletion.

Answer

The correct statements are that roll-up summary fields can be created on the Account object to aggregate data from related Course_Offering__c records, and deleting an Account record automatically deletes associated Course_Offering__c child records.
In Salesforce Core Administration, establishing a Master-Detail relationship enables two critical behaviors: first, native roll-up summary fields can be configured on the master object (Account) to aggregate data from child records; second, deleting a master record cascade-deletes all associated child records automatically.

Step-by-Step Solution

1
Analyze Master-Detail relationship data summary capabilities
Identify that Master objects in a Master-Detail relationship support roll-up summary fields (SUM, COUNT, MIN, MAX) on child records.
Roll-up summary fields are an exclusive feature of Master-Detail relationships and are placed on the master record.
2
Evaluate record deletion cascade behavior
Confirm that deleting the master Account record cascade-deletes all associated child Course_Offering__c records.
Child records in a Master-Detail relationship inherit access and existence entirely from the master record.
3
Review limitations and wrong options
Eliminate options proposing roll-up summaries over lookup relationships or automatic picklist configuration on record types.
Lookup relationships do not support native roll-up summary fields, and new record types require explicit picklist value configuration.

Key Concept

Master-Detail Relationship Capabilities and Limitations
Question 785Question

A System Administrator at Apex Financial Services is configuring distinct sales pipelines for two business divisions: Wealth Management and Corporate Advisory. Each division requires a different sequence of sales stages. The administrator creates two custom Opportunity record types named 'Wealth Management' and 'Corporate Advisory'. However, while attempting to assign specific Opportunity Stage picklist values to each record type in Object Manager, the administrator discovers that the Stage field is not available for editing under the Record Type picklist assignment page. Which administrative procedure must the administrator complete to enable distinct opportunity stage selections for each record type?

Show answer & explanation

Answer: Create two distinct Sales Processes, assign the appropriate stage picklist values to each Sales Process, and associate each Sales Process with its corresponding Opportunity Record Type.

Answer

The administrator must create two distinct Sales Processes, select the active stage values for each process, and then assign each Sales Process to its corresponding Opportunity Record Type.
In Salesforce, the Opportunity object uses a Sales Process to determine which stage picklist values are available. Unlike standard custom picklists, Stage values cannot be assigned directly to Record Types under the Record Type picklist edit interface. Creating separate Sales Processes for Wealth Management and Corporate Advisory allows the administrator to select the relevant stages for each process and then associate each Sales Process with the appropriate Record Type.

Step-by-Step Solution

1
Identify the underlying Salesforce mechanism for Opportunity Stage control
Recognize that Opportunity Stage picklist values are governed by Sales Processes, not directly through Record Type picklist edit pages.
Salesforce requires a Sales Process to define the lifecycle of an opportunity stage progression.
2
Create and configure custom Sales Processes
Create one Sales Process for Wealth Management and one for Corporate Advisory, selecting the specific stage values needed for each.
Sales Processes allow filtering of stage values to fit specific sales methodologies.
3
Associate Sales Processes with Record Types
Link each Sales Process to its corresponding Opportunity Record Type during or after Record Type creation.
Linking a Sales Process to a Record Type enforces the defined stages whenever an opportunity of that record type is created or updated.

Key Concept

Opportunity Sales Processes and Stage Picklist Selection
Question 786Question

A Salesforce Administrator at a green energy enterprise needs to manually provision a new Regional Sales Director. The user requires base system access, proper record visibility through the role hierarchy, and specialized permissions granted via permission set groups. In which sequence should the administrator execute these setup steps to successfully provision the user?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct administrative sequence is: 1) Select the User License and minimal base Profile on the user creation form, 2) Assign the Role within the Role Hierarchy on the user edit page, 3) Save the User record to create the active user account, and 4) Navigate to the saved User record's related lists to assign the required Permission Set Groups.
Provisioning a Salesforce user requires creating the record with mandatory fields (User License, Profile) and organizational attributes (Role) first. Saving the record creates the database entry and generates a User ID. Only after the record exists can an administrator access related lists on the User detail page to assign Permission Sets or Permission Set Groups for extra permissions.

Step-by-Step Solution

1
Configure required base user attributes on the creation page.
The user license and base profile are designated.
Salesforce mandates a license and profile selection upon user record initiation.
2
Assign the user's Role assignment on the creation page.
The user is positioned within the organizational Role Hierarchy.
Role selection is available on the main user edit interface prior to record creation.
3
Save the new User record.
The user record is committed to the database and assigned a unique User ID.
Saving the user record creates the underlying entity, making related child lists accessible.
4
Grant supplemental access via Permission Set Groups.
The user is granted extended capabilities beyond the base profile.
Permission Set Group assignments are managed via related lists on an existing, saved User detail page.

Key Concept

Sequential User Provisioning & Feature Access Management
Estimated Time:1m 30s
Question 787Question

Global Logistics Inc. is setting up a specialized case handling workflow for its Freight Audit team. This team requires a custom set of Case Status picklist values distinct from the standard customer support lifecycle. The administrator attempts to configure these custom status picklist values directly on a new Case Record Type, but the desired values do not appear in the record type's picklist selection settings. What must the administrator do first to resolve this issue?

Show answer & explanation

Answer: Create a new Support Process selecting the required Case Status values, then assign the Support Process to the Case Record Type.

Answer

Create a new Support Process selecting the required Case Status values, then assign the Support Process to the Case Record Type.
In Salesforce, the Case Status field is governed by a Support Process. Before custom Case Status picklist values can be assigned to or filtered on a Case Record Type, an administrator must first create a Support Process that selects the desired status values and then link that Support Process when setting up the Case Record Type.

Step-by-Step Solution

1
Identify the relationship between Case Status picklist values and Case Record Types.
Recognize that Case Status is controlled specifically by Support Processes rather than standard picklist management.
Salesforce architecture mandates that a Support Process defines the lifecycle stages (Case Status values) for cases.
2
Navigate to Setup and create a new Support Process for the Freight Audit team.
Select and save the specific subset of Case Status picklist values required for this workflow.
Support Processes isolate specific status values for targeted business processes.
3
Associate the newly created Support Process with the new Case Record Type.
The Case Record Type enforces and displays the custom status picklist values defined in the Support Process.
A Case Record Type requires a valid Support Process assignment to govern its Case Status picklist.

Key Concept

Support Process Prerequisite for Case Record Types
Question 788Question

A Salesforce Administrator is tasked with converting an existing custom object record page to Dynamic Forms in the Lightning App Builder and applying a conditional visibility filter to a newly created sensitive field section. What is the correct chronological sequence of steps the administrator must perform from start to finish?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct procedural sequence is: First, open the page in Lightning App Builder and select the Record Detail component. Second, click 'Upgrade Now' in the properties panel to run the migration wizard. Third, organize fields into granular Field Section components on the canvas. Fourth, select the sensitive Field Section and configure the Component Visibility filter rule in the properties panel. Fifth, save and activate the Lightning Record Page.
The correct order requires starting in Lightning App Builder by selecting the legacy Record Detail component, which exposes the 'Upgrade Now' button. Running the wizard converts the monolithic layout into modular Dynamic Forms components. The administrator must then arrange fields into individual Field Sections so that granular visibility criteria can be isolated. Once the sensitive section is structured, the administrator configures the Component Visibility filter rules in the properties panel for that section. Finally, saving and activating the page deploys the dynamic experience to end users.

Step-by-Step Solution

1
Select the Record Detail component in Lightning App Builder.
The properties panel updates to display the Dynamic Forms upgrade options.
Dynamic Forms migration is initiated from the properties panel of the existing Record Detail component.
2
Execute the 'Upgrade Now' wizard and choose the page layout source.
Fields and sections from the legacy layout are converted into Dynamic Forms Field Section and Field components.
The migration wizard extracts fields into editable canvas components.
3
Structure fields into distinct Field Section components on the layout.
The layout is divided into manageable component blocks.
Visibility filter rules apply at the component (Field Section) level, requiring sensitive fields to be grouped separately.
4
Configure component visibility filter criteria on the sensitive Field Section.
The Field Section component is dynamically rendered based on evaluated user profile, role, or field value conditions.
Filter rules must be attached to the specific component's property settings.
5
Save changes and activate the Lightning Record Page.
The page assignment takes effect for target users across the organization.
Changes in Lightning App Builder are not exposed to end users until the page is saved and activated.

Key Concept

Dynamic Forms Migration Workflow and Component Visibility Configuration
Question 789Question

Apex Wealth Management is establishing a dedicated support channel for premier clients. This unit requires a specialized lifecycle containing unique Case Status values and dedicated case fields that standard support representatives should not see. Which configuration sequence must a Salesforce administrator follow to successfully implement this requirement?

Show answer & explanation

Answer: Create custom Case Status values, build a new Support Process selecting those status values, create a Case Record Type linked to the Support Process, and assign the custom Page Layout to the Record Type.

Answer

The correct sequence is to first create the required Case Status picklist values, build a new Support Process to select those specific status values, create a Case Record Type linked to the Support Process, and then assign the specialized Page Layout to the Record Type.
In Salesforce, the Case Status field is controlled by a Support Process. To implement custom status values alongside custom page layouts for a specific business unit, an administrator must first add the status values to the master picklist, create a Support Process containing those values, create a Case Record Type associated with that Support Process, and finally assign the corresponding Page Layout.

Step-by-Step Solution

1
Define Custom Field Picklist Values
Ensure all required custom Case Status values exist in the master Case Status field picklist.
Support processes can only select from existing master picklist values on the Case object.
2
Create a Support Process
Build a new Support Process and select the subset of Case Status values relevant for the premier support team.
Case Status is a special field whose available values per record type are governed strictly by an underlying Support Process.
3
Create Case Record Type & Assign Page Layout
Create the new Case Record Type, associate it with the created Support Process, and assign the premier team's custom Page Layout.
Record Types tie together the Support Process (controlling status values) and Page Layouts (controlling visible fields and layout).

Key Concept

Support Processes and Case Record Types Dependency
Question 790Question

An organization hosts an executive summit and adds several leads as Campaign Members. The sales director wants to convert these leads into contacts and opportunities while ensuring that historical campaign participation remains visible on the resulting contact records and that generated revenue is correctly attributed to the summit campaign. Which two actions should the administrator take to achieve this requirement? (Choose 2)

Select all that apply

Show answer & explanation

Answer: Rely on standard lead conversion functionality, which automatically relates existing Campaign Member records from the lead to the newly generated contact.; Populate the Primary Campaign Source field on the opportunity created during conversion so that opportunity amount is attributed to campaign ROI.

Answer

The administrator should rely on standard lead conversion to automatically transfer Campaign Member records to the newly created contact, and populate the Primary Campaign Source field on the resulting opportunity for revenue attribution.
Standard lead conversion automatically moves existing Campaign Member records from the converted lead to the newly created or matched contact record, ensuring participation history is preserved. Furthermore, placing the campaign in the Primary Campaign Source field on the opportunity directly links opportunity value to the campaign for accurate ROI tracking.

Step-by-Step Solution

1
Analyze campaign member behavior during lead conversion
Confirm that standard Salesforce lead conversion preserves campaign engagement by reassociating Campaign Members from the lead to the contact record.
Understanding out-of-the-box Salesforce behavior prevents unnecessary custom automation or invalid lead field mapping configurations.
2
Configure campaign revenue attribution
Ensure that the Primary Campaign Source field on the opportunity is populated with the summit campaign during lead conversion.
Primary Campaign Source is required to feed opportunity values into standard Campaign ROI and campaign influence reporting.

Key Concept

Campaign Member Behavior during Lead Conversion and Revenue Attribution
Question 791Question

A Salesforce Administrator at a renewable energy firm needs to calculate and display the total power generation capacity from all installed solar units on the parent custom object, Solar_Park__c. Currently, the child object, Solar_Unit__c, is connected to Solar_Park__c using a Lookup relationship. When attempting to create a new field on Solar_Park__c, the Administrator discovers that the Roll-Up Summary field type is unavailable. Which action should the Administrator take to enable the creation of the Roll-Up Summary field?

Show answer & explanation

Answer: Convert the existing Lookup relationship on Solar_Unit__c to a Master-Detail relationship after ensuring all child records have a populated parent lookup value.

Answer

Convert the existing Lookup relationship on Solar_Unit__c to a Master-Detail relationship after ensuring all child records have a populated parent lookup value.
Roll-Up Summary fields can only be created on the master object in a Master-Detail relationship. Converting the Lookup relationship on Solar_Unit__c to a Master-Detail relationship (after populating the field on all existing child records) enables the Roll-Up Summary field type on Solar_Park__c.

Step-by-Step Solution

1
Identify the relationship constraints for Roll-Up Summary fields
Recognize that Roll-Up Summary fields require a Master-Detail relationship between the parent and child objects.
Salesforce standard functionality prohibits Roll-Up Summary fields on parent objects linked strictly via standard Lookup relationships.
2
Prepare the child records for relationship conversion
Ensure every existing Solar_Unit__c record has a valid Solar_Park__c parent selected.
A Lookup field cannot be converted to a Master-Detail field if any child records contain a null/blank lookup field.
3
Change field type of the relationship field
Convert the field type of the lookup field on Solar_Unit__c to Master-Detail.
Converting the field structure enables Roll-Up Summary creation on the parent object Solar_Park__c.

Key Concept

Roll-Up Summary Field Relationship Requirements
Question 792Question

An organization uses Opportunity Teams to facilitate sales collaboration on high-value deals. When an opportunity owner grants access to a team member by adding them to the Opportunity Team, which two access levels can be assigned to that opportunity record for the new team member?

Select all that apply

Show answer & explanation

Answer: Read Only; Read/Write

Answer

The two access levels that can be assigned directly to an Opportunity Team member for an opportunity record are Read Only and Read/Write.
When adding members to an Opportunity Team, Salesforce allows explicitly specifying record access level for the opportunity as either Read Only or Read/Write, giving team members appropriate visibility and edit capabilities.

Step-by-Step Solution

1
Identify the available record-level sharing access settings configurable via Opportunity Teams.
Salesforce Opportunity Teams allow opportunity owners and administrators to assign either Read Only access or Read/Write access to individual team members for the specific opportunity.
Opportunity Teams act as a manual sharing mechanism tailored for opportunity collaboration, exposing only Read Only and Read/Write options directly on the team member entry.
2
Evaluate system-level and owner-level permissions against Opportunity Team choices.
Full Access is restricted to record ownership/hierarchy privileges, Modify All is an object-level permission set/profile permission, and Private is an Organization-Wide Default model rather than a team sharing privilege.
Distinguishing object-level and ownership permissions from record sharing levels ensures accurate security model implementation.

Key Concept

Opportunity Team Sharing Access Levels
Estimated Time:45s
Question 793Question

A Salesforce Administrator is setting up a corporate summit campaign. The marketing team needs to measure prospect engagement by tracking who attended the session, while also ensuring that campaign membership history is preserved when leads are converted. Which two administrative actions should be taken to meet these requirements?

Select all that apply

Show answer & explanation

Answer: Add a custom Campaign Member Status value of 'Attended' and check the 'Responded' box for that status.; Associate leads with the campaign prior to conversion so campaign member records automatically transfer to the converted contact.

Answer

The administrator must create the custom Campaign Member Status 'Attended' with the 'Responded' checkbox enabled, and ensure leads are associated as Campaign Members before lead conversion so their history transfers to the Contact.
To accurately measure campaign success, custom status values representing positive engagement (such as attending an event) must have the 'Responded' setting enabled. Additionally, standard Salesforce behavior automatically links a Lead's Campaign Member history to the resulting Contact record upon lead conversion.

Step-by-Step Solution

1
Configure custom campaign member statuses
Create the 'Attended' status and check the 'Responded' flag.
Tracking engagement metrics relies on campaign member statuses having the 'Responded' checkbox enabled.
2
Verify lead conversion campaign history transfer
Ensure leads belong to the campaign before converting them.
Salesforce natively shifts Campaign Member record association from the Lead to the new Contact upon conversion.

Key Concept

Campaign Member Status response tracking and Campaign Member behavior during Lead Conversion
Question 794Question

Universal Containers maintains Private Organization-Wide Defaults for both Account and Opportunity objects. An administrator enables Team Selling and configures a Default Opportunity Team for a Senior Sales Executive, adding a Solution Architect with Read/Write Opportunity Access. However, when the Senior Sales Executive creates a new opportunity record, the Solution Architect cannot view or access it. The administrator verifies that the Default Opportunity Team member configuration is active and accurate. What is the most likely cause of this issue?

Show answer & explanation

Answer: The Senior Sales Executive has not enabled the user setting to automatically add their default opportunity team to newly created opportunities.

Answer

The Senior Sales Executive has not enabled the user setting to automatically add their default opportunity team to newly created opportunities.
Defining a Default Opportunity Team establishes a reusable team structure for a user, but Salesforce requires the user to explicitly check the setting 'Automatically add my default opportunity team to opportunities that I create or open' in their personal user settings. If this checkbox is unchecked, the default team is not added automatically upon record creation and must be added manually using the Add Default button.

Step-by-Step Solution

1
Analyze Team Selling default automation requirements in Salesforce.
Configuring a Default Opportunity Team creates the team template, but automatic assignment requires an active user preference.
Salesforce allows users flexibility so they can decide whether team members are automatically assigned to every deal or manually added using the 'Add Default' button on demand.
2
Check individual user personal settings under Advanced User Details.
The setting 'Automatically add my default opportunity team to opportunities that I create or open' must be enabled for the record owner.
Without this checkbox enabled, newly created opportunities will not inherit the Default Opportunity Team automatically.

Key Concept

Default Opportunity Team Automation Settings
Estimated Time:1m 30s
Question 795Question

An administrator needs to configure a new Case Record Type to handle internal IT requests, which follow a different lifecycle than standard customer inquiry cases. Which administrative element must be created first to define the allowed Case Status picklist values for this new record type?

Show answer & explanation

Answer: Support Process

Answer

A Support Process must be created first to select and define the Case Status picklist values that will be associated with the new Case Record Type.
In Salesforce, the Case object uses Support Processes to define the lifecycle and selectable values of the Case Status field. An administrator must create a Support Process containing the desired status values before associating it with a new Case Record Type.

Step-by-Step Solution

1
Identify the prerequisite for configuring custom Case Status picklist values across different case lifecycles.
Recognize that Case Status is controlled by a Support Process on the Case object.
Unlike standard objects where record types map picklist values directly, the Case object requires a Support Process to select which Case Status values are available before associating them with a Record Type.
2
Select the correct setup configuration component.
The administrator creates the Support Process first, then links it during Case Record Type creation.
Creating a Support Process is a strict prerequisite step prior to Case Record Type assignment.

Key Concept

Support Process prerequisite requirement for Case Record Types
Question 796Question

Solstice Energy Corp is introducing a new commercial solar inverter, 'HelioGrid 500', into Salesforce. The Salesforce Administrator creates the new product record and marks it as active. Next, the administrator attempts to add 'HelioGrid 500' to a custom price book named 'Commercial Regional Pricing', but the product does not appear in the list of available products to select.

Which configuration step must the administrator complete first to resolve this issue?

Show answer & explanation

Answer: Create and activate a standard price entry for 'HelioGrid 500' in the Standard Price Book.

Answer

Create and activate a standard price entry for the product in the Standard Price Book before adding it to custom price books.
In Salesforce product architecture, a product must have an active standard price entry in the Standard Price Book before it can be added to any custom price book. Once the standard price is created and activated, the product becomes available to add to custom price books like 'Commercial Regional Pricing'.

Step-by-Step Solution

1
Identify the prerequisite requirement for custom price book entries in Salesforce.
Salesforce architecture dictates that every product must have an active entry in the Standard Price Book prior to being added to any custom price book.
The standard price serves as the baseline price entry for product management across all price books.
2
Navigate to the product record and add a Standard Price.
An active standard price entry is established for 'HelioGrid 500' in the Standard Price Book.
This unlocks the product so that administrators can assign it to custom price books with custom list prices.
3
Add the product to the custom price book ('Commercial Regional Pricing').
The product is now selectable and can be successfully added to the custom price book.
The prerequisite standard price entry requirement has been satisfied.

Key Concept

Standard Price Book Entry Prerequisite
Question 797Question

A Salesforce Administrator is designing a custom data model for an IT department to link Workstations (`Workstation__c`) and Software Applications (`Software_App__c`). A workstation can host multiple software applications, and a software application can be installed on multiple workstations. The business requires calculating the total licensing cost of all installed applications directly on each Workstation record. Additionally, deleting a Workstation record must automatically remove its installation association records without deleting the Software Application records. Which configuration satisfies these requirements?

Show answer & explanation

Answer: Create a custom junction object with two Master-Detail relationship fields referencing Workstation and Software Application, then create a Roll-Up Summary field on the Workstation object.

Answer

Create a custom junction object with two Master-Detail relationship fields referencing Workstation and Software Application, then create a Roll-Up Summary field on the Workstation object.
To model a many-to-many relationship while supporting declarative Roll-Up Summary fields and cascading deletion of junction records, a custom junction object with two Master-Detail relationships is required. Creating a Master-Detail field to Workstation allows native Roll-Up Summary fields on Workstation, and deleting a Workstation record will delete only the junction records associated with it while leaving the Software Application master records intact.

Step-by-Step Solution

1
Analyze relationship requirements
Since one workstation can host multiple applications and one application can be installed on multiple workstations, a Many-to-Many relationship using a custom junction object is required.
Salesforce implements many-to-many relationships by placing a junction object between two parent objects.
2
Determine relationship types on the junction object
Use Master-Detail relationship fields pointing to Workstation and Software Application.
Master-Detail relationships allow native Roll-Up Summary fields on the master object and automatically cascade record deletion to junction records without deleting the opposite master object.
3
Configure data aggregation
Create a Roll-Up Summary field on the Workstation object to sum licensing costs from the junction object records.
Roll-Up Summary fields calculate values from child detail records directly on a master record.

Key Concept

Many-to-Many Relationships and Roll-Up Summary Field Capabilities
Question 798Question

An administrator creates a custom object named Audit_Request__c and configures a new Record Type called 'Enterprise Audit' to support compliance reviews. After assigning the new Page Layout and Record Type to the Compliance Officer profile, users report that when creating an Enterprise Audit record, the custom picklist field 'Audit Scope' only displays legacy values rather than the newly required enterprise values. Which administrative action will resolve this issue?

Show answer & explanation

Answer: Navigate to the Enterprise Audit Record Type detail page, edit the 'Audit Scope' picklist configuration, and move the required values into the Selected Values list.

Answer

Navigate to the Enterprise Audit Record Type detail page, edit the 'Audit Scope' picklist configuration, and move the required values into the Selected Values list.
In Salesforce Administration, creating a new Record Type requires administrators to configure which specific picklist values are available for each picklist field on the object. Even if values exist on the main object picklist definition, they must be moved to the 'Selected Values' list under the specific Record Type settings to be visible to users.

Step-by-Step Solution

1
Identify the cause of missing picklist options on a Record Type.
Recognize that creating a Record Type requires explicit mapping of accessible picklist values for every custom picklist on the object.
When a new Record Type is created, picklist fields retain default or unassigned value selections until explicitly edited under the Record Type configuration.
2
Access Object Manager and locate the target object and Record Type.
Open Object Manager > Audit Request > Record Types > Enterprise Audit.
Picklist value availability is configured directly on the Record Type detail page.
3
Edit the picklist field assignment.
Locate 'Audit Scope' under Picklists Available for Editing, select Edit, and move the desired enterprise values to the Selected Values list.
This updates the available choices displayed in the UI for users assigned to this Record Type.

Key Concept

Record Type Picklist Value Assignment
Estimated Time:1m 30s
Question 799Question

An administrator is designing a custom Lightning Record Page for a custom object named Service_Contract__c. The business requires that a specific high-value metrics component on the record page only appears to managers who are viewing contracts with a status of 'Active'. Additionally, the administrator must ensure that this custom page serves as the default layout specifically for the Customer Support application without overriding the record page for other applications across the organization. Which two configuration steps must the administrator complete to satisfy these requirements?

Select all that apply

Show answer & explanation

Answer: Set a Component Visibility rule on the high-value metrics component based on the user profile title and the contract Status field.; Activate the Lightning Record Page and assign it as the App Default for the Customer Support application.

Answer

The administrator must set component visibility rules based on the user's profile and record fields, and activate the page as the App Default for the Customer Support application.
To meet the requirement of showing a component conditionally based on user role and record state, Lightning App Builder provides component visibility filters that evaluate both record fields and user context. To restrict the custom page layout default to a single application without altering global defaults, the activation must be set to App Default for that targeted Lightning App.

Step-by-Step Solution

1
Analyze component visibility requirement
Dynamic component visibility criteria allow filtering components using both record field criteria (Status = Active) and user attribute criteria (User Profile/Title).
This dynamically hides or displays components without modifying field permissions or object schema.
2
Analyze activation assignment requirement
Activating the page as an App Default scopes the custom Lightning record page to a specific application while keeping the standard Org Default intact for other apps.
Org Default applies globally, whereas App Default targets specific application contexts as requested.

Key Concept

Lightning App Builder Activation Hierarchy and Dynamic Component Visibility Rules
Question 800Question

Northern Trail Outfitters is configuring distinct case handling procedures for Hardware Support, Software Licensing, and Billing Inquiries. Match each Salesforce administration component on the left with its corresponding configuration role on the right when establishing these customized case workflows.

Click a left item, then click its matching right item

Items

Support Process
Case Record Type
Case Page Layout
Record Type Picklist Value Selection

Matches

Show answer & explanation

Answer

Support Process matches defining Case Status picklist values; Case Record Type matches associating a Support Process and Page Layout to profiles; Case Page Layout matches controlling field organization and layout properties; Record Type Picklist Value Selection matches restricting standard and custom picklist values excluding Case Status.
Each component serves a specific administrative function in Salesforce Case setup: Support Processes control Case Status values; Case Record Types link the Support Process and Page Layout to profiles; Case Page Layouts specify page field organization and properties; and Record Type Picklist Value Selection handles all picklist filtering other than Case Status.

Step-by-Step Solution

1
Identify the role of a Support Process.
Recognize that Support Processes uniquely govern the Case Status picklist values.
Case Status cannot be filtered directly at the Record Type level without a pre-existing Support Process.
2
Identify the role of a Case Record Type.
Recognize that Record Types tie the Support Process and Page Layout together.
Record Types allow administrators to assign specific processes and layouts to different user profiles.
3
Identify the role of a Page Layout and Picklist Selection.
Match Page Layout to visual structure and Picklist Selection to non-status picklist values.
Page Layouts handle UI field organization, whereas Record Type picklist settings manage non-status custom/standard picklists.

Key Concept

Salesforce Case Lifecycle and Record Type Architecture
PreviousPage 40 / 90Next
All practice questions — Salesforce Certified Administrator | Examkin