Examkin

All practice questions

1784 questions

All types1,784Multiple choice918Multiple select587Matching142Ordering137
Question 1361Question →

A Salesforce administrator is tasked with setting up an automated process to update a custom text field on a Contact record immediately when the record is created or updated. The update strictly affects fields on the triggering Contact record itself and does not require interacting with related records or executing external actions. Which flow configuration should the administrator select to accomplish this task with optimal system performance?

Show answer & explanation

Answer: A Fast Field Updates record-triggered flow (before-save)

Answer

The administrator should choose a Fast Field Updates record-triggered flow (before-save).
Fast Field Updates (before-save record-triggered flows) are specifically optimized to modify fields on the record that launched the flow before it is written to the Salesforce database. This avoids expensive additional database operations.

Step-by-Step Solution

1
Analyze the automation requirements.
The requirement is to update fields exclusively on the record that triggered the automation during creation or edit.
Identifying the target of the field update determines whether a before-save or after-save flow is required.
2
Evaluate flow trigger types for same-record updates.
Fast Field Updates (before-save) execute prior to database commit and update the triggering record without requiring an extra DML event.
Before-save flows offer optimal performance for updating fields on the triggering record.

Key Concept

Selecting optimal Record-Triggered Flow optimization types (Fast Field Updates vs. Actions and Related Records).
Estimated Time:45s
Question 1362Question →

An organization requires automated actions to occur immediately upon a user submitting a custom Vendor Contract record for evaluation. Specifically, the contract's status must automatically change to 'In Review', and a notification email must be sent to the contract management team. Which TWO configurable action types can be added directly to the Initial Submission Actions section of a Salesforce Approval Process to satisfy these requirements? (Select 2 options)

Select all that apply

Show answer & explanation

Answer: Field Update; Email Alert

Answer

Field Update and Email Alert can be added directly as Initial Submission Actions in a Salesforce Approval Process.
Salesforce approval processes allow four specific types of actions under Initial Submission Actions: Field Updates, Email Alerts, Tasks, and Outbound Messages. A Field Update changes field values such as Status upon entry, while an Email Alert sends automated notifications using email templates.

Step-by-Step Solution

1
Identify the automated actions supported directly within Salesforce Approval Process submission stages.
Salesforce Approval Processes natively support four types of actions: Field Update, Email Alert, Task, and Outbound Message.
Understanding native action capabilities ensures proper tool selection without redundant customization.
2
Map the business requirements to the supported action types.
Updating the status field requires a Field Update, and notifying the management team requires an Email Alert.
Both actions directly match native Initial Submission Action capabilities.
3
Differentiate native actions from system settings and unrelated automation tools.
Record locking occurs automatically via system settings upon submission rather than as a discrete selectable action item, and Flow invocations are not selectable actions within approval initial submission steps.
Confusing system properties or external trigger actions with initial submission actions leads to misconfiguration.

Key Concept

Approval Process Initial Submission Actions
Question 1363Question →

An administrator is configuring a multi-step automated approval process for high-value contract renewals. When an end-user initiates an approval request, Salesforce executes a strict sequence of system evaluations and action triggers. Place the automated system steps in the exact chronological order in which Salesforce processes them from initial user submission to final approval completion.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct chronological execution order is: 1) Evaluate process entry criteria, lock record, and run initial submission actions; 2) Evaluate Step 1 entry criteria; 3) Assign request and send step notification email; 4) Execute Step 1 approval actions; 5) Execute Final Approval Actions.
When a record is submitted for approval, Salesforce evaluates the top-level process entry criteria first. Once satisfied, the record is locked and initial submission actions execute. Next, step entry criteria are evaluated for Step 1. Upon satisfying step criteria, assignment and step notification emails are dispatched. Following approver action, step approval actions fire. Finally, after all steps are approved, Final Approval Actions execute to complete the lifecycle.

Step-by-Step Solution

1
Evaluate top-level approval process entry criteria and execute initial submission actions
The record enters the approval process, becomes locked, and initial submission actions run.
Process-level entry criteria are evaluated prior to any individual step criteria.
2
Evaluate step entry criteria for Step 1
Salesforce determines if the record qualifies for Step 1 routing.
Step entry criteria determine whether the record enters Step 1 or moves to alternative step routing.
3
Route approval request to designated approver
The approval notification is dispatched and pending work item is created.
Once step entry is confirmed, assignment and notification occur synchronously.
4
Execute step-level approval actions
Step-specific automated actions (e.g., field updates, email alerts) trigger upon approver authorization.
Step approval actions occur immediately after the designated approver submits an affirmative decision.
5
Execute Final Approval Actions
Final approval actions trigger and record locking state transitions according to final approval configuration.
When all steps in the approval process path are completed, Salesforce executes final approval actions.

Key Concept

Salesforce Approval Process Evaluation Sequence and Action Lifecycle
Question 1364Question →

A renewable energy firm provides self-service support to its commercial installers using an Experience Cloud site. The external Organization-Wide Default (OWD) for the Case object is set to Private. The administrator needs to grant external users assigned Customer Community licenses access to view all cases submitted by any contact associated with their company's Account record.

Which configuration should the administrator implement to grant this record access efficiently?

Show answer & explanation

Answer: Configure a Sharing Set that grants Case access based on matching the user's Account with the Case's Account.

Answer

Configure a Sharing Set that grants Case access based on matching the user's Account with the Case's Account.
Because Customer Community licenses are high-volume portal licenses that do not support user roles, standard sharing rules cannot be used. Sharing Sets are designed specifically for high-volume community users to grant record access based on matching criteria, such as mapping the user's Account to the Account linked on Case records.

Step-by-Step Solution

1
Identify the license type and external sharing settings.
Customer Community users use high-volume community licenses, which do not utilize standard Salesforce user roles. The external OWD for Case is Private.
High-volume portal users cannot use standard role-based sharing rules.
2
Determine the appropriate automated sharing mechanism for high-volume community users.
Sharing Sets allow administrators to grant access to records where a lookup field on the record (e.g., Case.Account) matches a lookup field on the user record (e.g., User.Account).
Sharing Sets provide record-level access efficiently without requiring user roles.
3
Select the correct configuration approach.
Creating a Sharing Set configured to match the user's Account to the Case's Account enables all external users from that Account to view related Cases.
This meets the requirement while preserving external OWD security controls.

Key Concept

Experience Cloud Sharing Sets for High-Volume Portal Licenses
Estimated Time:1m 30s
Question 1365Question →

An administrator is designing an autolaunched flow to process a list of active Account records and create a follow-up Task for each Account's primary Contact. The flow will handle batch operations involving hundreds of records simultaneously. Which design pattern should the administrator implement within Flow Builder to successfully process all records without violating governor limits?

Show answer & explanation

Answer: Iterate through the Account collection using a Loop element, populate individual Task record variables, add each Task variable to a Task collection variable using an Assignment element inside the loop, and place a single Create Records element after the loop.

Answer

Iterate through the Account collection using a Loop element, populate individual Task record variables, add each Task variable to a Task collection variable using an Assignment element inside the loop, and place a single Create Records element after the loop.
The correct approach for bulkifying flows involves staging record updates or creations in a collection variable inside the loop using an Assignment element, followed by executing a single Create Records element outside of the loop. This consumes only 1 DML operation regardless of the number of records processed.

Step-by-Step Solution

1
Iterate over the incoming collection of Account records using a Loop element.
Each Account record is processed individually per iteration.
Allows inspection and mapping of fields for individual items in the collection.
2
Assign task field values to a record variable and add that record variable to a Task record collection variable using an Assignment element within the loop.
The Task collection accumulates all new records without executing database transactions inside the loop.
Staging records in a collection in memory avoids executing DML statements inside the loop.
3
Connect the 'After Last' path of the Loop element to a single Create Records element targeting the Task collection variable.
All staged Task records are inserted in a single bulkified DML operation.
Executes 1 DML statement for the entire collection, adhering to Salesforce governor limits.

Key Concept

Bulkification in Flow Builder using collection variables and placing DML elements outside loops
Question 1366Question →

A Salesforce administrator is designing a Custom Report Type with 'Volunteer Projects' as the primary object and 'Volunteer Assignments' as the secondary object. The business requirement states that reports using this report type must display all Volunteer Projects regardless of whether they have related Volunteer Assignments. Additionally, report builders need access to fields from the related Contact object linked via lookup on Volunteer Assignments. Which TWO setup steps must the administrator perform within the Custom Report Type configuration? (Select 2 options)

Select all that apply

Show answer & explanation

Answer: Select the object relationship setting where 'A' records may or may not have related 'B' records.; Edit the field layout of the custom report type and use 'Add fields related via lookup' to reference Contact fields.

Answer

The administrator must select the object relationship where primary records ('A') may or may not have secondary records ('B'), and edit the field layout to add fields related via lookup.
To include primary object records without secondary records, the administrator must choose the 'with or without' outer join relationship. To include fields from a lookup object (Contact) on a report type, the administrator uses the 'Add fields related via lookup' option in the custom report type field layout editor.

Step-by-Step Solution

1
Define Object Relationships
Configure the relationship between Volunteer Projects (A) and Volunteer Assignments (B) using the 'with or without' option.
This establishes a left outer join so primary records are included even when no child records exist.
2
Customize Field Layout
Use the 'Add fields related via lookup' feature on the custom report type field layout editor to navigate from Volunteer Assignments to Contact.
This makes related Contact fields available for selection when users create reports using this report type.

Key Concept

Custom Report Type Layout & Relationship Definitions
Question 1367Question →

A Salesforce administrator at a renewable energy firm needs to enforce data quality on the Opportunity object. The business requirement dictates that whenever an Opportunity is set to the 'Closed Won' stage, the custom text field Project_Install_Address__c must not be left blank. Which validation rule formula correctly enforces this requirement?

Show answer & explanation

Answer: AND(ISPICKVAL(StageName, "Closed Won"), ISBLANK(Project_Install_Address__c))

Answer

The validation rule formula using AND(ISPICKVAL(StageName, "Closed Won"), ISBLANK(Project_Install_Address__c)) correctly evaluates to TRUE and blocks the record save whenever an Opportunity reaches 'Closed Won' status with an unpopulated installation address field.
The formula using AND(ISPICKVAL(StageName, "Closed Won"), ISBLANK(Project_Install_Address__c)) is correct because validation rules block record creation/updates when the formula evaluates to TRUE. Combining ISPICKVAL for the StageName picklist with ISBLANK for the text field properly catches records moving to Closed Won without the required address.

Step-by-Step Solution

1
Identify the field types and required condition criteria.
StageName is a picklist field requiring ISPICKVAL(), and Project_Install_Address__c is a text field requiring ISBLANK().
Salesforce formula syntax requires picklist values to be evaluated using specific functions rather than direct text comparison operator equality.
2
Combine the conditions into a single logical error expression.
Use the AND() function so both criteria must be met to trigger the validation error.
A validation rule triggers its error message when the overall formula evaluates to TRUE.

Key Concept

Salesforce Validation Rule Formulas and Null Field Handling
Question 1368Question →

An administrator is building a custom report on Opportunities grouped by Region (Primary Grouping) and Sales Rep (Secondary Grouping). The business requires two specific metrics in the report layout: first, calculating the exact duration in days between the Created Date and Close Date for each individual opportunity record; second, calculating the percentage contribution of each Sales Rep's total won amount compared to their overall Region's total won amount. Which combination of report formula features should the administrator implement?

Show answer & explanation

Answer: Create a Row-Level Formula to calculate the record duration in days, and a Summary Formula utilizing the PARENTGROUPVAL function for the regional percentage contribution.

Answer

The correct approach is to create a Row-Level Formula to calculate the duration in days for each individual opportunity record, and a Summary Formula using the PARENTGROUPVAL function to compute the percentage contribution of each Sales Rep relative to their parent Region total.
Row-Level Formulas operate on individual record rows to compute values such as elapsed time between two date fields on a record. In contrast, calculating the ratio of a subgroup total to its enclosing parent group total requires a Summary Formula using the PARENTGROUPVAL function, which specifically retrieves summary values from specified parent grouping levels.

Step-by-Step Solution

1
Identify the record-level calculation requirement
Determined that calculating duration per individual record requires evaluating fields on single rows before summary aggregation.
Row-Level Formulas allow single-record calculations directly within report outputs (e.g., CloseDate - DATEVALUE(CreatedDate)).
2
Identify the group-level aggregation requirement
Determined that comparing a subgroup total to a higher-level parent group total requires summary aggregation functionality.
The PARENTGROUPVAL summary function calculates values from a parent group level relative to a child group level in grouped reports.
3
Combine the appropriate formula types
Selected a Row-Level Formula for the record-by-record date subtraction and a Summary Formula using PARENTGROUPVAL for the group ratio.
This combination respects Salesforce reporting limits and capabilities for detailed versus aggregated calculations.

Key Concept

Distinction between Row-Level Formulas (individual record evaluations) and Summary Formulas with PARENTGROUPVAL (group-level aggregations).
Estimated Time:2m 0s
Question 1369Question →

A sales director at a growing software company requests that 15 account executives have their Microsoft 365 emails and calendar events automatically captured on Salesforce record timelines. The Salesforce administrator opens the account executives' user profile settings to enable Einstein Activity Capture (EAC), but finds that EAC access cannot be enabled directly through profile permissions. Which administrative action should the administrator take to successfully grant Einstein Activity Capture access to these users?

Show answer & explanation

Answer: Assign the Standard Einstein Activity Capture permission set to the individual users.

Answer

Assign the Standard Einstein Activity Capture permission set to the individual users.
Einstein Activity Capture (EAC) access is managed using permission sets. Assigning the Standard Einstein Activity Capture permission set (or a permission set containing the EAC user permission) to the targeted users provisions their access to EAC configuration settings and enables automatic email and event sync capabilities.

Step-by-Step Solution

1
Identify the mechanism required to provision Einstein Activity Capture (EAC) user licensing and feature access in Salesforce.
EAC access is granted through permission sets rather than standard profile permission settings.
Salesforce uses permission sets to assign feature-specific licenses (like EAC) to targeted subsets of users flexibly.
2
Select the appropriate permission set to assign to the 15 account executives.
Assign the Standard Einstein Activity Capture permission set (or a custom permission set including the EAC user permission).
This grants the necessary rights for Salesforce to connect with the users' Microsoft 365 accounts and stream activities to record timelines.

Key Concept

Einstein Activity Capture Permission Set Assignment
Question 1370Question →

Apex Global Financials is introducing a new Wealth Advisory division alongside its established Retail Brokerage operations. The Wealth Advisory team requires a unique set of sales stages and probability metrics for their opportunities, while Retail Brokerage will retain the standard sales cycle. Which TWO configuration steps must an administrator complete to fulfill this requirement?

Select all that apply

Show answer & explanation

Answer: Create a new Sales Process and select the subset of Opportunity Stage picklist values specific to Wealth Advisory.; Create a new Opportunity Record Type and assign the newly defined Wealth Advisory Sales Process to it.

Answer

To establish distinct sales stages for different business divisions, an administrator must first create a dedicated Sales Process containing the required stage picklist values, and then create a new Opportunity Record Type associated with that Sales Process.
On the Opportunity object, stage availability is governed by Sales Processes. An administrator must first create a custom Sales Process selecting the appropriate stage picklist values, and then create an Opportunity Record Type to link that Sales Process to users.

Step-by-Step Solution

1
Define the stage picklist values in a Sales Process.
A customized lifecycle is created containing only the stages relevant to Wealth Advisory.
Salesforce requires Opportunity stages to be grouped into a Sales Process before they can be linked to a record type.
2
Create an Opportunity Record Type and assign the Sales Process.
The Record Type links the custom Sales Process to user profiles and layout assignments.
Record Types drive page layout assignment and picklist values, but on Opportunities, the stage picklist is governed specifically by the linked Sales Process.

Key Concept

Sales Process and Record Type Linkage for Opportunities
Estimated Time:1m 30s
Question 1371Question →

An administrator needs to update multiple Contact records associated with an Account using a Flow. To prevent exceeding Salesforce governor limits during execution, what is the recommended placement of the Update Records element when iterating through a collection of records?

Show answer & explanation

Answer: Outside of the Loop element, executing a single update on the modified record collection after the loop completes

Answer

Place the Update Records element outside the Loop element, executing the DML update on the entire collection variable once after all assignments are complete.
Salesforce enforces strict governor limits on data manipulation language (DML) statements (150 per transaction). To ensure flows are bulkified, data manipulation elements like Update Records should always be placed outside the Loop element on the 'After Last Item' path. Records should be modified in memory via Assignment elements and stored in a collection variable before performing a single bulk DML update.

Step-by-Step Solution

1
Iterate through the record collection using a Loop element and update field values in memory using an Assignment element.
Individual items are updated in temporary memory without invoking DML statements.
Prevents database operations within loop iterations.
2
Add the updated current item from the loop to a new record collection variable using a second Assignment element.
A collection of modified records is constructed.
Gathers all modified records into a single bulk resource.
3
Place an Update Records element after the loop finishes (connected to the 'After Last Item' path) pointing to the collection variable.
All records in the collection are updated in a single bulk DML statement.
Adheres to Salesforce governor limits by executing only one DML operation.

Key Concept

Flow Bulkification and Governor Limits
Estimated Time:1m 0s
Question 1372Question →

An administrator is tasked with updating the entitlement status and expiration dates on hundreds of custom Contract Line Item records whenever a parent Contract status changes to 'Expired'. The solution must update all related records reliably while adhering to Salesforce governor limits.

Which design pattern should the administrator implement in Flow Builder to perform this data manipulation efficiently?

Show answer & explanation

Answer: Loop through the retrieved Contract Line Items, use an Assignment element inside the loop to update the field values on the current item and append that item to a new Record Collection Variable, and place an Update Records element outside the loop referencing the new collection.

Answer

Iterate through the line item collection using a Loop element, use an Assignment element inside the loop to update the current item variable and add it to a target Record Collection Variable, then execute a single Update Records element outside the loop.
The correct approach follows Salesforce bulkification best practices. By updating field values on the loop item variable and assigning that item to a separate Record Collection Variable within the loop, all record changes are staged in memory. A single Update Records element placed after the loop processes the entire collection in one database transaction, ensuring scalability and compliance with governor limits.

Step-by-Step Solution

1
Query related child records prior to entering the loop.
Obtain a Record Collection Variable containing all target Contract Line Item records.
Retrieving data in bulk before processing avoids running SOQL queries inside the loop.
2
Iterate over the collection using a Loop element.
Pass each individual record to the current item loop variable.
Allows field assignment logic to execute on one record at a time in memory.
3
Use an Assignment element inside the loop to update fields and add the loop variable to a secondary Record Collection Variable.
The modified record is stored in memory within the secondary collection.
Accumulates all updated records without issuing immediate database commits.
4
Place a single Update Records element after the loop finishes and pass the secondary Record Collection Variable.
Salesforce performs a single bulkified DML operation for all records in the collection.
Prevents hitting the governor limit of 150 DML statements per transaction.

Key Concept

Bulkification in Flow Builder using Assignment elements and Record Collection Variables
Question 1373Question →

A company requires automated record processing when a custom object record, Asset_Maintenance__c, is updated to a status of 'Urgent Repair Required'. The system must perform two specific operations: create a new follow-up Task assigned to the asset owner, and send a SOAP-based outbound web service message to an external inventory tracking system. Which TWO statements accurately describe the capabilities and limitations of Process Builder in fulfilling these requirements? (Select TWO answers.)

Select all that apply

Show answer & explanation

Answer: Process Builder can natively create the follow-up Task record as an immediate action without writing custom code.; Process Builder cannot directly invoke outbound SOAP messages natively, requiring an Apex callout or a launched Flow to handle external messaging.

Answer

Process Builder can natively create new records such as Tasks, but it cannot natively execute outbound SOAP messages or delete records, requiring Apex or Flow for outbound messaging.
The correct options accurately identify Process Builder capabilities: Process Builder natively supports record creation (such as generating a Task record) as an immediate action. However, it lacks native support for outbound SOAP web service messaging, meaning administrators must invoke custom Apex or launch a Flow to handle outbound callouts.

Step-by-Step Solution

1
Evaluate record creation capability in Process Builder
Process Builder includes 'Create a Record' as a standard immediate action, allowing automatic generation of Task records.
Creating related or standalone records is a core declarative capability of Process Builder.
2
Evaluate outbound web service/SOAP capabilities
Process Builder does not have a direct 'Outbound Message' action component.
Outbound SOAP messaging is available natively in legacy Workflow Rules, whereas Process Builder requires calling an Apex method or Flow to send external HTTP/SOAP callouts.
3
Evaluate record deletion limitations
Deleting records is not supported in Process Builder.
Declarative record deletion is a Flow feature, not a Process Builder capability.

Key Concept

Process Builder Action Capabilities and System Limitations
Question 1374Question →

A system administrator is configuring a complex multi-step Approval Process for custom Service Level Agreement (SLA) Exception records. The business requirement mandates that immediately upon submission, the record's status field must update to 'Under Review' and submitters must be prevented from modifying any record details while the request is evaluated. During testing, the administrator configures an Initial Submission Action to update the status field, but discovers that submitters are still able to edit the SLA Exception fields after submitting the record. Which configuration setting must the system administrator modify to enforce the required edit restriction upon submission?

Show answer & explanation

Answer: Modify the Approval Process Editability Properties from allowing edit by administrators and the submitter to only allowing edit by administrators.

Answer

The administrator must update the Approval Process Editability settings so that only administrators (or assigned approvers, as appropriate) can edit records while locked in the approval process, preventing submitters from making modifications.
When a record enters an approval process, Salesforce automatically locks the record. However, who can edit the locked record depends on the process's 'Record Editability Properties' setting (configured during approval process setup). To prevent the submitter from modifying fields during approval, the editability setting must be set so that only administrators (or administrators and currently assigned approvers) can edit locked records, rather than allowing submitter edits.

Step-by-Step Solution

1
Analyze approval process locking mechanics in Salesforce.
Recognize that Salesforce automatically locks a record upon initial submission into an approval process.
Initial submission automatically triggers the native record lock.
2
Evaluate edit permission properties configured on the approval process definition.
Identify that record editability settings determine who can modify locked records during the approval cycle.
If the editability setting is misconfigured to permit edits by the submitter or record owner, locking will not prevent submitter edits.
3
Determine the correct administrative adjustment.
Set editability properties to restrict edit permissions strictly to administrators.
This satisfies the business requirement of locking out submitter edits during evaluation.

Key Concept

Approval Process Record Locking & Editability Settings
Estimated Time:2m 0s
Question 1375Question →

A financial services firm wants to enable self-service support for policyholders using an Experience Cloud site built on the Customer Service template. Policyholders holding standard Customer Community licenses need to view and manage cases associated with their personal contact record. Currently, the organization's internal sharing model for Cases is set to Private, and internal visibility must remain restricted.

Which two configuration actions should the administrator perform to fulfill these security and access requirements?

Select all that apply

Show answer & explanation

Answer: Set the External Organization-Wide Default (OWD) for Cases to Private.; Create a Sharing Set that maps the User's Contact to the Contact on the Case object.

Answer

The administrator should set the External Organization-Wide Default (OWD) for Cases to Private and create a Sharing Set that maps the User's Contact record to the Contact field on Case records.
To grant Customer Community users access to their own cases while keeping internal and external access restricted, the administrator must establish an External Organization-Wide Default of Private for Case. Because standard Customer Community users do not have roles, traditional sharing rules do not apply; instead, a Sharing Set must be used to map user attributes (User.Contact) to record attributes (Case.Contact).

Step-by-Step Solution

1
Configure External Sharing Model
Setting the External OWD for Case to Private establishes a secure base level of access specifically for external users without altering internal OWD settings.
Salesforce allows separate internal and external OWDs so that external community user access can be restricted independently of internal sharing settings.
2
Configure Sharing Set for Community Users
A Sharing Set is defined to match User.Contact = Case.Contact, granting Read/Write access to the community user.
Standard Customer Community licenses use roleless high-volume community architecture and rely on Sharing Sets rather than traditional role-based sharing rules to grant record access.

Key Concept

Experience Cloud External Sharing Models and Sharing Sets for High-Volume Portal Licenses
Question 1376Question →

A company uses an approval process for discount authorization requests. The sales management team requires that assigned approvers are able to edit specific record fields to adjust proposed pricing terms while the record is undergoing review, whereas the submitting user remains prevented from modifying the record. Which setting should the administrator configure within the approval process properties to meet this requirement?

Show answer & explanation

Answer: Set the Record Editability Properties to allow both Administrators and the currently assigned approver to edit records during the approval process.

Answer

The administrator should set the Record Editability Properties to allow both Administrators and the currently assigned approver to edit records during the approval process.
In Salesforce approval processes, administrators configure the Record Editability option in the approval process properties. Choosing to allow both Administrators and the currently assigned approver ensures that the approver can edit the record while it remains locked for the submitter and other standard users.

Step-by-Step Solution

1
Identify the requirement for record editability during an active approval process.
Assigned approvers need permission to edit records while they are locked in the approval cycle.
By default, Salesforce locks records upon entry into an approval process so that only System Administrators can edit them.
2
Evaluate the native Approval Process detail settings.
The Record Editability setting specifies edit rights for locked records.
Selecting 'Administrators ONLY' or 'Administrators OR the currently assigned approver' controls editing access during approval evaluation.
3
Select the appropriate setting option.
Choose 'Administrators OR the currently assigned approver'.
This allows the assigned approver to edit the record without unlocking it for the submitter or other users.

Key Concept

Approval Process Record Editability Settings
Question 1377Question →

Global Freight Solutions requires an automated solution on the custom object Freight_Shipment__c when a record's status is updated to 'Dispatched'. The solution must fulfill three operational requirements:
1. Standardize and populate the custom field Formatted_Routing_Code__c on the triggering Freight_Shipment__c record prior to the database commit.
2. Update the Status__c field on all associated child Shipment_Item__c records to 'In Transit'.
3. Execute an HTTP callout to send shipment payload details to an external third-party logistics REST API.

Which combination of flow trigger configurations adheres to Salesforce performance and architecture best practices?

Show answer & explanation

Answer: Implement a Before-Save Record-Triggered Flow (Fast Field Updates) to populate Formatted_Routing_Code__c on the triggering record, and a separate After-Save Record-Triggered Flow (Actions and Related Records) utilizing an Asynchronous Path to update child Shipment_Item__c records and execute the external HTTP callout.

Answer

Implement a Before-Save Record-Triggered Flow (Fast Field Updates) for same-record updates, alongside an After-Save Record-Triggered Flow with an Asynchronous Path for related record updates and external callouts.
The solution properly separates responsibilities according to Salesforce architectural guidelines. A Before-Save (Fast Field Updates) flow optimizes same-record updates by setting values in memory before saving to the database without additional DML calls. An After-Save flow using an Asynchronous Path allows related record updates and handles external HTTP callouts in a background thread, preventing callout governor limit exceptions.

Step-by-Step Solution

1
Evaluate same-record field update requirements
Identify that Formatted_Routing_Code__c must be populated on the triggering record prior to database commit.
Fast Field Updates (Before-Save record-triggered flows) are optimized for modifying the triggering record because values are set directly in memory without firing additional DML statements or trigger re-entry.
2
Evaluate related record updates and external callout requirements
Determine that updating child Shipment_Item__c records and executing external HTTP callouts require post-save processing.
Before-Save flows cannot perform DML on related records or invoke external callout actions. Related record DML and HTTP callouts must occur in an After-Save flow.
3
Determine transaction boundary requirements for callouts
Assign callout and related record processing to an Asynchronous Path within an After-Save flow.
Executing HTTP callouts after DML in the same synchronous transaction causes uncommitted work pending exceptions. The Asynchronous Path runs in a separate thread, permitting callouts and database operations to execute safely.

Key Concept

Record-Triggered Flow Trigger Optimization & Asynchronous Execution Architecture
Question 1378Question →

An administrator at a medical device company is configuring custom fields on the Lead object and a custom object named Equipment_Service_Contract__c. The administrator must ensure custom field data captured on prospects is properly transferred during lead conversion and that field availability and relationship behaviors are configured correctly across object record types. Which TWO administration considerations and data type behaviors are accurate for these custom field configurations?

Select all that apply

Show answer & explanation

Answer: Custom lead fields must be explicitly mapped to custom fields on the Account, Contact, or Opportunity object in Lead Field Mapping settings to transfer data upon lead conversion.; When adding a custom picklist field to an object with existing record types, the new picklist values must be assigned to each record type to be available to users.

Answer

The two correct requirements are: 1) Custom lead fields require explicit Lead Field Mapping setup to pass data to converted Account, Contact, or Opportunity custom fields, and 2) Custom picklist values must be explicitly assigned to individual Record Types on the object before users can select them.
Custom lead fields require explicit Lead Field Mapping in Salesforce setup to map values to target custom fields on Account, Contact, or Opportunity records upon lead conversion. Additionally, when an object uses Record Types, creating a new custom picklist field requires the administrator to assign which picklist values are enabled for each specific Record Type so users can see and select them on page layouts.

Step-by-Step Solution

1
Analyze Lead conversion mapping requirements for custom fields.
Confirm that custom lead fields require explicit administrative mapping under Object Manager > Lead > Fields & Relationships > Map Lead Fields.
Automatic field mapping by matching API name does not occur in Salesforce.
2
Evaluate picklist field creation behavior when Record Types exist.
Recognize that creating a picklist field does not automatically enable its values on existing object record types.
Picklist value visibility and selection availability are controlled per record type.
3
Verify relationship and roll-up constraints.
Confirm roll-up summaries are exclusive to Master-Detail relationships, and deleting a Master record deletes detail children.
Lookup relationships do not support native roll-up summary fields.

Key Concept

Custom Field Administration, Picklist Record Type Assignment, and Lead Mapping
Estimated Time:1m 30s
Question 1379Question →

An administrator receives reports that customer submissions from an online form generated via Web-to-Case are intermittently failing to appear in Salesforce. Troubleshooting reveals that a recently implemented validation rule on the Case object causes certain submissions to fail background processing. How does Salesforce handle Web-to-Case submissions that fail custom validation rules?

Show answer & explanation

Answer: Salesforce prevents case creation and emails the error details along with the submitted form data to the Default Case Owner.

Answer

Salesforce prevents case creation and emails the error details along with the submitted form data to the Default Case Owner.
When a Web-to-Case submission fails database validation rules or required field checks, Salesforce prevents the case record from being created. To ensure customer inquiries are not lost, Salesforce packages the submitted form data along with the specific validation error message into an email and sends it directly to the designated Default Case Owner (or Default Web-to-Case Creator).

Step-by-Step Solution

1
Identify how Web-to-Case processes incoming HTML POST requests.
Salesforce evaluates incoming field values against database constraints, required fields, and active validation rules.
Web-to-Case must adhere to data quality rules configured on the Case object.
2
Determine the outcome when a validation rule fails during background web submission processing.
Because no user session exists on the external form to display inline errors, record insertion is rejected.
Salesforce avoids creating invalid data in the database while capturing the customer's data for administrative review.
3
Identify the notification mechanism for rejected Web-to-Case submissions.
Salesforce sends an automated email containing all submitted form key-value pairs and error log details to the configured Default Case Owner.
This ensures customer inquiry data is not permanently lost and allows administrators to manually re-enter or address the case.

Key Concept

Web-to-Case Validation Failure Notification
Question 1380Question →

An IT hardware manufacturer recently launched a self-service Experience Cloud site for its commercial customers using the Customer Service template. Customer Community users report that while they can log and view their own support cases, they are unable to see any published Knowledge articles on the portal. The administrator confirms that the articles are published and set to be visible in the internal knowledge base and customer channel. Which configuration step should the administrator check to resolve this visibility issue?

Show answer & explanation

Answer: Verify that Data Category Visibility is configured on the portal user profile or assigned permission sets.

Answer

Verify that Data Category Visibility is configured on the portal user profile or assigned permission sets.
In Salesforce Knowledge, publishing an article to the Customer channel makes it eligible for Experience Cloud sites, but user access is governed by Data Category Visibility. If Data Category groups are not mapped to the portal user profile or permission set (or set to Default/All Categories), users cannot view the articles.

Step-by-Step Solution

1
Analyze Knowledge Visibility Requirements
Articles are published and available in the customer channel, but users cannot view them.
Knowledge visibility relies both on channel publication and Data Category exposure.
2
Evaluate Access Controls for Knowledge
Data Category group visibility determines which articles users with a given profile or permission set can read.
If Data Category Visibility is set to None or restricted on the user profile/permission set, published articles remain hidden.
3
Select Correct Configuration Action
Ensure Data Category Visibility grants access to the relevant category groups for community user profiles or permission sets.
This grants the appropriate article access without changing object-level permissions.

Key Concept

Data Category Visibility in Experience Cloud Knowledge
PreviousPage 69 / 90Next
All practice questions — Salesforce Certified Administrator | Examkin