Examkin

All practice questions

1784 questions

All types1,784Multiple choice918Multiple select587Matching142Ordering137
Question 941Question →

An administrator needs to configure a relationship between a custom object named Asset_Maintenance__c and the standard Account object. The business requires that Asset_Maintenance__c records can exist independently without requiring an Account to be assigned. Additionally, management requests a native summary count of all related maintenance records displayed on the Account record page. Which assessment of this design requirement is correct?

Show answer & explanation

Answer: A Lookup relationship must be used to allow independent records, but standard Roll-Up Summary fields will not be supported on the Account object.

Answer

A Lookup relationship must be used to allow independent records, but standard Roll-Up Summary fields will not be supported on the Account object.
Choosing a Lookup relationship satisfies the requirement that child records can exist without a parent Account. However, because native Roll-Up Summary fields in Salesforce require a Master-Detail relationship, the administrator cannot use a standard Roll-Up Summary field on Account for a Lookup relationship.

Step-by-Step Solution

1
Evaluate the requirement for record independence
Since child records must exist without a parent Account, a Lookup relationship is required because Master-Detail relationships mandate a parent record.
Master-Detail fields are mandatory on detail record creation.
2
Evaluate the Roll-Up Summary field requirement
Native Salesforce Roll-Up Summary fields are exclusively available on the master object in a Master-Detail relationship.
Lookup relationships do not support native Roll-Up Summary fields.
3
Synthesize the architecture limitations
To meet the independence requirement, a Lookup relationship must be chosen, acknowledging that native Roll-Up Summary functionality will not be natively supported on Account.
Salesforce object architecture rules prohibit native roll-ups over lookup fields.

Key Concept

Lookup vs. Master-Detail relationship capabilities and Roll-Up Summary field limitations
Question 942Question →

An administrator configured a new Record Type named "Government Account" on the Account object to support a public sector team. After assigning the new Record Type and Page Layout to the Sales Executive profile, users assigned to this profile report that the Industry picklist field still displays all global picklist values rather than the specific subset required for public sector records. Which administrative step did the administrator omit during configuration?

Show answer & explanation

Answer: Editing the Industry picklist settings within the Government Account Record Type detail page to select the allowable values.

Answer

Editing the Industry picklist settings within the Government Account Record Type detail page to select the allowable values.
When a new Record Type is created, Salesforce defaults to making all active picklist values available. To display only a specific subset of options, the administrator must edit the picklists available for editing within that specific Record Type configuration.

Step-by-Step Solution

1
Navigate to Object Manager > Account > Record Types and open the Government Account record type.
Displays the Record Type detail page and its configurable properties.
Record Types store custom picklist value assignments independently from page layout assignments.
2
Locate the Picklists Available for Editing section and click Edit next to the Industry field.
Opens the picklist selection interface showing Available Values and Selected Values.
Newly created Record Types inherit all active global picklist values by default until modified.
3
Move non-applicable industry values from Selected Values to Available Values and save.
Restricts visible options in the Industry drop-down exclusively to the designated subset when users view or edit records of this Record Type.
This enforces data consistency and ensures users only select valid values for public sector records.

Key Concept

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

A Salesforce administrator at Apex Renewable Energy is setting up case automation for inbound customer inquiries. In what sequence does Salesforce execute automation rules when a new case is created?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct order of execution for Salesforce case automation is: Validation rules evaluate the record, Case Assignment rules determine ownership, Case Auto-Response rules send automated customer emails, and Case Escalation rules schedule SLA actions.
Salesforce follows a strict standard order of execution for case automation when a new case is saved: Validation rules run first to ensure data integrity, followed by Assignment rules to establish ownership. Next, Auto-Response rules send targeted customer communications, and finally, Escalation rules schedule timers for unhandled cases.

Step-by-Step Solution

1
Evaluate record validity
Validation rules ensure case data integrity before processing automated rules.
If data is invalid, execution stops immediately to prevent assigning invalid cases.
2
Assign case ownership
Case Assignment rules route the case to the designated user or queue.
Ownership must be established before sending auto-responses or calculating escalation rules based on business hours.
3
Trigger auto-response communication
Case Auto-Response rules dispatch an automated confirmation email to the customer.
Auto-responses rely on the final assigned owner and initial case attributes.
4
Set up escalation monitoring
Case Escalation rules evaluate conditions and schedule SLA timers.
Escalation timers depend on the case owner, priority, and business hours configured in preceding steps.

Key Concept

Salesforce Order of Execution for Case Automation Rules
Question 944Question →

A support administrator at a financial technology firm needs to enable flexible collaboration on high-priority customer cases. The Organization-Wide Default (OWD) for Case is configured as Private. A temporary group of compliance officers and senior product specialists must be granted Read/Write access on an ad-hoc, per-case basis without changing ownership of the case or modifying the global role hierarchy. Additionally, members added to the case must receive email alerts when assigned. Which configuration should the Salesforce administrator implement to satisfy these requirements?

Show answer & explanation

Answer: Configure Case Team Roles with Read/Write access, set up Predefined Case Teams, and add the Case Teams related list to the Case page layout.

Answer

Configure Case Team Roles with Read/Write access, set up Predefined Case Teams, and add the Case Teams related list to the Case page layout.
Case Teams enable administrators and users to grant record-level access (Read Only or Read/Write) to specific users or predefined groups for individual case records. This satisfies the requirement of ad-hoc collaboration when Organization-Wide Defaults are set to Private, while keeping the original case ownership intact.

Step-by-Step Solution

1
Analyze access requirements
Identified that users require ad-hoc Read/Write record access on a per-case basis without changing record ownership or altering the standard role hierarchy.
When OWD is Private, Case Teams provide explicit record-level sharing grants tailored to specific roles on an individual case.
2
Evaluate Salesforce Case Collaboration tools
Selected Predefined Case Teams and Case Team Roles with Read/Write permissions.
Case Teams support predefined lists of users with configurable access rights (Read Only, Read/Write, Private) and optional notifications.
3
Examine page layout integration
Added the Case Teams related list to the Case page layout.
Adding the related list allows support agents to add predefined teams or individual team members directly on the case record.

Key Concept

Case Teams and Record-Level Sharing
Question 945Question →

Starlight Software Solutions maintains an Organization-Wide Default (OWD) setting of Private for the Case object. Support representatives frequently need to collaborate with specialized escalation engineers and external technical consultants on complex, high-priority cases. The administrator must implement a solution that enables case owners to invite specific internal and external specialists to individual case records on an ad-hoc basis, assign them functional responsibilities, and grant them explicit Read/Write access to the record. Which Salesforce feature should the administrator configure to satisfy these operational requirements?

Show answer & explanation

Answer: Case Teams with predefined roles and access levels

Answer

The administrator should configure Case Teams with predefined roles and access levels.
Configuring Case Teams allows case owners and administrators to add users and predefined groups of users to individual cases. Each Case Team Role defines the record-level access granted (Read Only or Read/Write), effectively overriding the Private Organization-Wide Default for those specific team members on that individual case.

Step-by-Step Solution

1
Analyze the access and collaboration requirements
The requirement calls for ad-hoc, record-level sharing (Read/Write) combined with role definition on individual case records where OWD is Private.
Standard organization-wide defaults prevent users from viewing cases unless explicitly shared or above the owner in the role hierarchy.
2
Evaluate Salesforce Case Collaboration tools
Case Teams directly provide ad-hoc record sharing (Private, Read Only, Read/Write) and role assignment on individual cases.
Case Teams allow case owners or administrators to manually or automatically add users to a case team and grant necessary data access.
3
Select the appropriate administrative configuration
Configure Case Team Roles and Predefined Case Teams under Support Settings / Case Teams.
This configuration satisfies both the functional role labeling and the granular security access requirement.

Key Concept

Case Teams and Access Level Assignment
Question 946Question →

An enterprise company uses a Private Organization-Wide Default (OWD) sharing model for both Account and Opportunity objects. A sales representative adds a technical specialist to an Opportunity Team with Read/Write access to help close a complex deal. Prior to being added to the team, the technical specialist had no access to the parent Account record. Which level of access to the parent Account record is automatically granted to the technical specialist upon joining the Opportunity Team?

Show answer & explanation

Answer: Implicit Read-Only access to the parent Account record.

Answer

The technical specialist is automatically granted implicit Read-Only access to the parent Account record.
In Salesforce built-in sharing architecture, adding a user to an Opportunity Team automatically grants that user implicit Read-Only access to the associated parent Account record. This ensures team members can view the account details necessary to collaborate on the deal without gaining unauthorized edit permissions on the account.

Step-by-Step Solution

1
Analyze the Organization-Wide Default (OWD) settings and initial sharing state.
Accounts and Opportunities are set to Private, meaning users only see records they own or records explicitly shared with them.
Establishing baseline visibility rules is necessary to determine what implicit access kicks in.
2
Evaluate the behavior of Opportunity Team sharing on related parent objects.
Adding a user to an Opportunity Team grants access to the Opportunity (Read-Only or Read/Write) and automatically grants implicit Read-Only access to the parent Account record if the user lacks access.
Salesforce architecture mandates implicit parent sharing so team members can view essential contextual account information.

Key Concept

Opportunity Team Implicit Sharing Behavior
Question 947Question →

A Salesforce Administrator is reviewing the order of execution for case creation automation within Service Cloud. Arrange the following rule evaluation and processing stages in the exact sequence in which Salesforce processes them upon case creation.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct order of execution for case creation processing is: Validation Rules evaluation, Case Assignment Rules evaluation, Case Auto-Response Rules evaluation, and Case Escalation Rules evaluation.
During case creation, Salesforce follows a deterministic order of execution for case automation rules. First, Validation Rules ensure data validity. Next, Case Assignment Rules determine case ownership (user or queue). Third, Case Auto-Response Rules send automatic email replies to the submitter. Finally, Case Escalation Rules evaluate criteria to schedule SLA escalation actions.

Step-by-Step Solution

1
Identify the record integrity stage.
Validation Rules are evaluated first.
If validation fails, case record creation is halted entirely, preventing invalid data from triggering downstream automation.
2
Identify the ownership routing stage.
Case Assignment Rules are evaluated second.
Case ownership must be established so that subsequent communications and SLA tracking refer to the correct owner or queue.
3
Identify the customer communication stage.
Case Auto-Response Rules are evaluated third.
Auto-response rules evaluate initial case attributes and assignment context to dispatch targeted automated emails to the customer.
4
Identify the SLA monitoring stage.
Case Escalation Rules are evaluated fourth.
Escalation rules determine SLA tracking entries and schedule future escalation actions after initial assignment and customer auto-response processing complete.

Key Concept

Salesforce Case Automation Rules Execution Order
Estimated Time:2m 0s
Question 948Question →

Vanguard Commercial Real Estate uses a custom object named Property_Lease__c to manage leasing agreements. The Organization-Wide Default (OWD) for Property_Lease__c is set to Private. To prevent intermediate managers from automatically inheriting access to records owned by subordinate leasing agents, the administrator deselects the 'Grant Access Using Hierarchies' option on the Property_Lease__c object. However, executive directors still require Read-Only visibility into all lease agreements owned by agents assigned to the East Coast Leasing role. Which configuration should the system administrator implement to satisfy this security requirement?

Show answer & explanation

Answer: Create an owner-based sharing rule that shares Property_Lease__c records owned by members of the East Coast Leasing role with users in the Executive Directors role with Read-Only access.

Answer

Create an owner-based sharing rule that shares Property_Lease__c records owned by members of the East Coast Leasing role with users in the Executive Directors role with Read-Only access.
When 'Grant Access Using Hierarchies' is deselected for a custom object, vertical record access propagation up the role hierarchy is disabled. To grant access to a specific group of users (Executive Directors) for records owned by another specific group (East Coast Leasing), an owner-based sharing rule is the precise configuration required. It selectively opens up access without altering OWD or re-enabling hierarchy inheritance for intermediate managers.

Step-by-Step Solution

1
Analyze the Organization-Wide Default (OWD) baseline and custom hierarchy setting.
The baseline OWD is Private, and 'Grant Access Using Hierarchies' is disabled for Property_Lease__c, meaning automatic vertical access up the role hierarchy is turned off.
Disabling hierarchy access ensures intermediate managers above leasing agents do not inherit record access.
2
Determine the targeted sharing mechanism needed.
Selective Read-Only access is needed specifically for executive directors for records owned by the East Coast Leasing role.
Owner-based sharing rules allow admins to share records owned by members of a specific role with another designated role.
3
Evaluate why alternative administrative sharing tools are unsuitable.
Permission set 'View All' grants org-wide access across all owners, OWD Public Read-Only exposes records to all users, and re-enabling hierarchy access breaks the manager restriction constraint.
Only an owner-based sharing rule satisfies the exact target criteria under the principle of least privilege.

Key Concept

Owner-based Sharing Rules vs. Role Hierarchy Access Control
Estimated Time:1m 30s
Question 949Question →

A system administrator at a medical technology firm needs to grant senior support leads the ability to create, edit, and publish Salesforce Knowledge articles. Which two settings or configuration steps are required to enable article publishing capabilities for these users? (Select 2 options.)

Select all that apply

Show answer & explanation

Answer: Select the Knowledge User feature license checkbox on each user's detail page.; Assign a permission set containing article action permissions such as Publish Articles to the users.

Answer

To allow users to create and publish Salesforce Knowledge articles, an administrator must check the Knowledge User feature license on their User detail records and grant article management permissions (such as Publish Articles) via a permission set or profile.
To publish Knowledge articles in Salesforce, a user must have both the Knowledge User feature license enabled on their user record and the appropriate article action permission (such as Publish Articles) granted via a permission set or profile.

Step-by-Step Solution

1
Verify feature license requirement.
The Knowledge User feature license checkbox on the User record is enabled.
The Knowledge User checkbox grants the baseline capability to create, edit, and manage Knowledge articles in Salesforce.
2
Assign specific article management permissions.
Grant Publish Articles permission through a permission set or profile.
Administrative article action permissions are required to perform publishing actions on articles.

Key Concept

Salesforce Knowledge User License and Article Publishing Permissions
Question 950Question →

Universal Containers uses a custom object named Performance_Review__c to track employee evaluations. The administrator needs to restrict access to a sensitive custom field, Overall_Rating__c, so that only three Executive Team members can view and edit it. All other users assigned to the Standard User profile must continue to create and edit Performance Review records without having any access to the Overall_Rating__c field. Which configuration should the administrator implement to satisfy this security requirement?

Show answer & explanation

Answer: Set Field-Level Security on Overall_Rating__c to restricted (Read and Edit unchecked) for the Standard User profile, and assign a Permission Set granting Read and Edit access to the Executive Team members.

Answer

Restrict Field-Level Security on the Overall_Rating__c field for the Standard User profile by unchecking Read and Edit, and create a Permission Set granting Read and Edit access on Overall_Rating__c assigned specifically to the Executive Team members.
The correct approach enforces Field-Level Security (FLS) by removing Read and Edit access from the base profile (Standard User) and using a Permission Set to grant the required access to specific individual users. This follows Salesforce security best practices by providing true data security across UI, reports, and APIs while preventing profile maintenance bloat.

Step-by-Step Solution

1
Analyze baseline profile permissions
Recognize that the Standard User profile currently grants access to the object, but the field needs to be restricted for most users.
Security in Salesforce follows the principle of least privilege at the profile level.
2
Restrict Field-Level Security (FLS) at the profile level
Deselect Read and Edit access for Overall_Rating__c on the Standard User profile.
FLS ensures the field is secure across all access vectors including UI, API, reports, and search.
3
Grant additive access using a Permission Set
Create a Permission Set with Read and Edit access to Overall_Rating__c and assign it to the three Executive Team users.
Permission sets allow targeted, additive privilege assignment without creating redundant profiles.

Key Concept

Field-Level Security (FLS) restriction on profiles combined with additive access via Permission Sets
Estimated Time:1m 30s
Question 951Question →

An administrator is configuring asset management and security options in Salesforce Files. Match each business requirement on the left to the corresponding Salesforce Files capability or configuration setting on the right.

Click a left item, then click its matching right item

Items

Restrict a specific file attached to a Case record so that other users with record access cannot share the file further or attach it to other records.
Organize enterprise sales collateral into centralized repositories with custom member permission levels (such as Viewer, Author, or Library Administrator).
Send a web-based URL of a presentation to external prospects that enforces password protection, sets an expiration date, and records view analytics.
Update a proposal document with new revisions while retaining complete audit history of previous iterations and maintaining existing record associations.

Matches

Show answer & explanation

Answer

Restricting further sharing of a file on a record corresponds to File Privacy on Records ('Prevent others from sharing and unsharing'). Organizing collateral with member permission levels corresponds to Salesforce CRM Content Libraries. Sending password-protected links with expiration and analytics corresponds to Content Deliveries. Maintaining document revision history across record attachments corresponds to Salesforce Files Versioning.
Each feature precisely fulfills the operational and security requirement: File Privacy on Records blocks unauthorized resharing of record attachments, Salesforce CRM Content Libraries manage folder/workspace permissions, Content Deliveries handle expiring password-protected external links with analytics, and Files Versioning manages updates across linked records while preserving prior versions.

Step-by-Step Solution

1
Analyze file security restriction requirement
Identify that restricting non-owners from sharing attached files requires setting File Privacy on Records to 'Prevent others from sharing and unsharing'.
By default, users with access to a record inherit file access; setting explicit file privacy overrides this inherited sharing behavior.
2
Analyze repository and workspace permissions requirement
Map structured repositories with roles like Viewer and Author to Salesforce CRM Content Libraries.
Libraries provide workspace-level governance and role-based permissions independent of object record sharing.
3
Analyze external link tracking and security requirement
Map password-protected, expiring external links with viewing metrics to Content Deliveries.
Content Deliveries create tracked online versions of files specifically designed for external delivery.
4
Analyze file update and history requirement
Map uploading new iterations without breaking record links to Salesforce Files Versioning.
Uploading a new version replaces the active file across all attached records while preserving historical versions.

Key Concept

Salesforce Files Security, Libraries, Content Deliveries, and Version Control
Estimated Time:2m 0s
Question 952Question →

Horizon Solar Energy needs to implement a dedicated Field Service Escalation workflow for handling on-site equipment failures alongside its standard Customer Inquiries process. The Field Service Escalation workflow requires a customized lifecycle with a unique set of Case Status values. Which two configuration steps must the Salesforce Administrator complete to implement this requirement? (Choose 2 answers.)

Select all that apply

Show answer & explanation

Answer: Create a new Support Process that selects the specific Case Status picklist values required for the escalation lifecycle.; Create a new Case Record Type and associate it with the newly created Support Process.

Answer

To configure a customized Case lifecycle with distinct Case Status values, the administrator must first create a Support Process containing the required status values, and then create a Case Record Type that references that Support Process.
On the Case object, the Case Status field values are driven by a Support Process. Creating a dedicated Support Process allows administrators to select the specific status values for a given business lifecycle. Once the Support Process is established, a Case Record Type must be created and linked to that Support Process so users can apply it when creating or editing cases.

Step-by-Step Solution

1
Create the Support Process
Defines the specific lifecycle stages (Case Status values) needed for Field Service Escalations.
Case Status values are controlled exclusively by Support Processes on the Case object.
2
Create and link the Case Record Type
Associates page layouts and business processes to the record type.
Record types for Cases require a designated Support Process during creation.

Key Concept

Support Processes and Case Record Types Dependency
Question 953Question →

Quantum Grid Systems is launching a specialized Grid Architecture Services division alongside its existing Hardware Licensing business. The new division requires a distinct sequence of Opportunity stages with tailored probability values and a customized page layout for sales representatives. Which TWO administrative actions must a Salesforce administrator perform to successfully implement this requirement?

Select all that apply

Show answer & explanation

Answer: Create a new Sales Process containing only the subset of Opportunity stage values required for the Grid Architecture Services division.; Create a new Opportunity Record Type, associate it with the new Sales Process, and assign the customized page layout to the appropriate user profiles.

Answer

The administrator must create a dedicated Sales Process selecting the required stage values and then create a new Opportunity Record Type associated with that Sales Process while assigning the customized page layout.
To implement separate sales pipelines with different stage picklists and page layouts on the Opportunity object, an administrator must first build a Sales Process to filter the active stage picklist values. Next, the administrator creates an Opportunity Record Type linked to that Sales Process and assigns the corresponding page layout to the appropriate user profiles.

Step-by-Step Solution

1
Create the custom Sales Process
Defines the specific set of Opportunity stages and probabilities available for the new sales pipeline.
Opportunity stages on standard opportunity objects are controlled by Sales Processes, not directly by record types.
2
Create the Opportunity Record Type and associate the Sales Process
Links the sales pipeline stages to a specific record type for administration and access.
Record types require a Sales Process to determine which stage picklist values are available.
3
Assign Page Layout and Profile Access
Ensures reps in the Grid Architecture Services division see the correct fields and page layout.
Page layouts are assigned to user profiles via Record Type configuration.

Key Concept

Sales Process and Record Type Linkage for Opportunity Stage Management
Question 954Question →

A sales administrator at a commercial aviation charter firm is documenting the standard Salesforce lead conversion process for newly onboarded sales representatives. Arrange the following steps of the lead conversion lifecycle in the correct chronological order from initial lead qualification to final record creation.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct chronological sequence is: 1) Update Lead Status to 'Qualified', 2) Click the 'Convert' action button on the Lead record, 3) Configure target Account, Contact, and Opportunity settings in the conversion modal, 4) Salesforce validates data and creates target records using Lead Custom Field Mapping, and 5) The source Lead status changes to 'Converted' and becomes read-only.
The standard lead conversion process begins when a representative qualifies a lead. Clicking the Convert button opens a prompt modal where target Account, Contact, and Opportunity options are designated. Once submitted, Salesforce validates data, applies custom lead field mappings, creates or updates target records, and finally updates the lead status to Converted while locking it as read-only.

Step-by-Step Solution

1
Identify the initial qualification trigger in the lead lifecycle.
The Lead Status picklist is set to 'Qualified'.
Business rules require verifying lead eligibility before initiating conversion.
2
Launch the lead conversion interface.
Clicking the 'Convert' button opens the conversion user interface.
User action is required to invoke the conversion modal.
3
Specify target object parameters.
The user selects whether to create new records or merge into existing Accounts and Contacts, and sets Opportunity preferences.
Salesforce requires user confirmation on how target destination records should be structured.
4
Execute system conversion and data mapping.
Salesforce creates or updates the target Account, Contact, and Opportunity records and maps mapped custom fields.
Backend transaction handling processes field mapping rules and database record creation.
5
Finalize source lead status.
The original Lead record status changes to 'Converted' and becomes read-only.
Converted leads are retained for historical reporting but protected from further direct edits.

Key Concept

Standard Salesforce Lead Conversion Execution Order
Question 955Question →

Cloud Kicks is setting up a distinct revenue stream that requires a unique set of stage picklist values on the Opportunity object. Which administrative component must a Salesforce administrator create first to select the available opportunity stages before associating them with an Opportunity record type?

Show answer & explanation

Answer: A Sales Process

Answer

A Sales Process must be created first to define the set of opportunity stage picklist values before associating them with an Opportunity record type.
In Salesforce, the Opportunity Stage field is controlled by a Sales Process. An administrator must first create a Sales Process containing the desired stages and then assign that Sales Process to the corresponding Opportunity Record Type.

Step-by-Step Solution

1
Identify the relationship between Opportunity Record Types and Opportunity Stages
Recognize that Opportunity stages cannot be filtered directly on the record type level.
Salesforce uses a Sales Process as an intermediate layer to map stage picklist values to Opportunity record types.
2
Determine the initial setup requirement
Create a Sales Process and select the active stage picklist values for the sales channel.
Creating the Sales Process makes it available for selection when configuring the Opportunity record type.

Key Concept

Sales Process and Record Type Linkage for Opportunity Stages
Question 956Question →

A customer service manager at a telecommunications provider wants all newly created cases to be automatically routed to specific support queues based on the geographic region selected on the case record. Which Salesforce automation feature should the system administrator configure to meet this requirement?

Show answer & explanation

Answer: Case Assignment Rules

Answer

Case Assignment Rules
Case Assignment Rules allow administrators to define rule entries that evaluate case attributes (such as geographic region) when a case is created, automatically assigning ownership to designated support queues or individual users.

Step-by-Step Solution

1
Identify the primary requirement
The requirement asks for automatically routing newly created cases to queues based on case field criteria (geographic region).
Understanding the functional objective determines the appropriate Salesforce automation tool.
2
Evaluate Salesforce Case Automation features
Case Assignment Rules are designed specifically to determine initial case ownership and route records to users or queues.
Assignment rules trigger during case creation to evaluate rule entries and assign ownership accordingly.

Key Concept

Case Assignment Rules define automated routing conditions to assign case records to individual users or support queues based on record criteria.
Question 957Question →

An administrator at Cloud Kicks is configuring the standard Asset object to support two operational teams: Hardware Maintenance and Software Subscriptions. The administrator has already created two Record Types ('Hardware' and 'Software') and built two corresponding Page Layouts. Which two configuration actions must the administrator take to complete the setup for users assigned to these record types? (Select 2 answers)

Select all that apply

Show answer & explanation

Answer: Configure Page Layout Assignments by Profile to map each Record Type to its intended Page Layout.; Edit the available picklist values under each Record Type detail page to restrict options for fields like Status.

Answer

The administrator must configure Page Layout Assignments by Profile to map each Record Type to its corresponding Page Layout, and edit the available picklist values under each Record Type detail page to restrict options for fields like Status.
Completing a Record Type implementation requires two distinct administrative steps: configuring Page Layout Assignments across profiles so users see the correct layout for each record type, and editing the picklist values assigned to each record type so users only see valid options for their business process.

Step-by-Step Solution

1
Map Page Layouts to Profiles and Record Types
Each profile sees the appropriate page layout when accessing a record of a specific Record Type.
Salesforce uses a matrix of Profile x Record Type to determine page layout assignment.
2
Configure Picklist Values per Record Type
Only relevant picklist values are selectable for each Record Type.
Creating a record type inherits all master picklist values by default; administrators must edit the picklist selections for each record type to enforce business logic.

Key Concept

Page Layouts and Record Types Assignment
Estimated Time:1m 15s
Question 958Question →

An administrator at a logistics enterprise needs to temporarily prevent a user from logging into Salesforce while they are on extended administrative leave. The user is currently assigned as the running user for several active scheduled Apex jobs and automated process flows. Which action should the administrator take to stop the user from logging in without causing background automation failures?

Show answer & explanation

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

Answer

Freeze the user account from the user detail page.
Freezing a user account prevents the user from logging into Salesforce while preserving background execution contexts. This allows scheduled Apex jobs, workflow rules, and process flows where the user is designated as the running user to continue operating without disruption.

Step-by-Step Solution

1
Identify the primary administrative objective and technical constraints.
Login access must be blocked immediately, but background jobs executing under this user must remain functional.
Deactivating a user assigned as a running user for active scheduled Apex jobs will cause system runtime errors.
2
Evaluate the functional difference between freezing and deactivating a user.
Freezing blocks login access without freeing up the user license or disrupting running user dependencies.
Freezing is specifically designed for scenarios where deactivation cannot immediately occur due to background operational dependencies.

Key Concept

User Freezing vs Deactivation Dependencies
Question 959Question →

An administrator is configuring a Lightning Record Page for a custom Asset Management object using Dynamic Forms and Dynamic Actions in Lightning App Builder. Which two features or capabilities accurately describe this configuration?

Select all that apply

Show answer & explanation

Answer: Individual fields and field sections can be placed directly onto the page canvas with custom multi-column layouts.; Action visibility can be conditionally controlled based on user attributes, record field values, or client device factors.

Answer

Individual fields and field sections can be placed directly onto the page canvas with custom multi-column layouts, and action visibility can be conditionally controlled based on user attributes, record field values, or client device factors.
Dynamic Forms allows administrators to place individual fields and field sections directly onto the Lightning App Builder canvas. Additionally, Dynamic Actions allow administrators to conditionally display actions using filters based on record data, user attributes, or device type.

Step-by-Step Solution

1
Evaluate the layout capabilities of Dynamic Forms.
Dynamic Forms breaks record detail components into discrete Field and Field Section components that can be dragged directly onto the Lightning page canvas.
This removes reliance on traditional monolithic page layout components and offers flexible layout structuring.
2
Evaluate the capability of Dynamic Actions.
Dynamic Actions allow administrators to set component visibility filters on quick actions based on user criteria, record field values, or device types.
This provides granular control over which actions appear in specific record contexts.
3
Analyze security boundaries and administrator best practices.
UI component visibility in Dynamic Forms does not replace Field-Level Security (FLS) for API/report access, and layout customization should not rely on creating extra user profiles.
Component visibility is purely a UI display mechanism, whereas FLS enforces schema-level data security.

Key Concept

Dynamic Forms and Dynamic Actions capabilities and security boundaries
Question 960Question →

A Salesforce administrator at an aviation charter company is designing a custom object named Flight Reservation to track client trips associated with Account records. The management team requires that all flight reservations are automatically removed if their parent Account record is deleted, and that total charter expenditure is automatically aggregated and displayed on the Account record. Which configuration fulfills these requirements?

Show answer & explanation

Answer: Create a Master-Detail relationship on Flight Reservation pointing to Account, and create a Roll-Up Summary field on Account.

Answer

Create a Master-Detail relationship on Flight Reservation pointing to Account, and create a Roll-Up Summary field on Account.
Establishing a Master-Detail relationship with Account as the master object ensures that deleting an Account automatically deletes associated Flight Reservation records. Furthermore, Master-Detail relationships natively support Roll-Up Summary fields on the master object, allowing the administrator to calculate aggregate expenditure metrics directly on Account records.

Step-by-Step Solution

1
Analyze relationship requirements for cascading deletion
Master-Detail relationship is required because deleting the parent Account must cascade to delete child Flight Reservation records.
Lookup relationships do not perform cascading deletions by default, whereas Master-Detail relationships enforce parent ownership and automatic detail record deletion.
2
Analyze aggregation requirements on the parent record
A Roll-Up Summary field on the Account object will calculate total expenditure.
Native Roll-Up Summary fields require a Master-Detail relationship between the parent (Account) and child (Flight Reservation) objects.

Key Concept

Master-Detail vs. Lookup Relationship Capabilities
PreviousPage 48 / 90Next
All practice questions — Salesforce Certified Administrator | Examkin